fsck required on boot for raids-1 hangs

Bug #137624 reported by Harald Rudell
2
Affects Status Importance Assigned to Milestone
e2fsprogs (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I was trying to boot a raid-1 system with errors on the root partition.

bootup process, right after the "mdadm error exit" message said something like "need to fsck, file system will be writeable during,... bla"

However, fsck never starts. System hung and nothing happens. (may be waiting for udev or something) Only reset effective.

I had to boot from another partition and run fsck -f there.

Revision history for this message
Michael Nagel (nailor) wrote :

is this still an issue?

Changed in e2fsprogs:
status: New → Incomplete
Revision history for this message
Theodore Ts'o (tytso) wrote :

Um, this is much more likely a boot scripts issue than an e2fsprogs issue....

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

No response to the request for information

Changed in e2fsprogs (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.