fsck froze while scanning second disk
Bug #555756 reported by
Reuben Firmin
This bug report is a duplicate of:
Bug #554737: ply_boot_client_flush() does not read replies (plymouth stuck during/after filesystem check or error).
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| e2fsprogs (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: e2fsprogs
vmlinuz-
I have 5 disks, and fsck decided that it needed to scan them all. After 30 minutes, the 2nd disk was 90% scanned; at that point, plymouth's dots stopped blinking, and the message stayed on "90% done." I left it this way for a further 30 minutes to see if it was working on something, and then alt sysrq eub'ed it. On the second boot, fsck didn't even kick in (I expected that it would rescan the 2nd, since it hadn't completed, and then scan the 3rd, 4th and 5th disks, as it had intended to on the first boot.)
To post a comment you must log in.
