[Bug 850007] Re: fsck not in initramfs, needed to boot (non-standard install)

[Adam Conrad]

I can't quite sort out a scenario where this would be true on a >=
precise armhf install on any of our supported platforms.  If you can
give me reproduction steps from a d-i-installed setup to show this still
being a problem, feel free to reopen the bug and smack me on IRC and
we'll sort it out.

** Changed in: initramfs-tools (Ubuntu)
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/850007

Title:
  fsck not in initramfs, needed to boot (non-standard install)

Status in “initramfs-tools” package in Ubuntu:
  Invalid

Bug description:
  On some non-standard installed arm boards, running both lucid and
  maverick, if the root disk has errors, then the machine does not boot
  until someone manually interrupts the boot, gets into the initramfs,
  copies /sbin/fsck.ext3 in, and fscks the root partition.  Clearly,
  this is suboptimal, and quite likely, it's something I missed in the
  install process to make it all happy.

  I'm told that fsck should not be needed to boot, though I suspect that
  the most direct solution would be for me to add an initramfs hook to
  make sure that fsck is present in the initramfs.

  looking for some guidance here on whether this is expected, and what
  solution would be cleanest.

  thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/850007/+subscriptions