/forcefsck is ignored in Lucid
Bug #538810 reported by
ingo
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 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
NULL Project |
Invalid
|
Undecided
|
Unassigned | ||
Plymouth |
New
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Lucid-amd64, ext4 root-filesystem, grub2
creating /forcefsck is sometimes ignored and no fsck performed on next reboot.
If fsck is run however, file /forcefsck is not removed, and Lucid does not boot up correctly, so fsck is still due for next reboot.
In way the fsck is never recorded under /var/log/fsck/*
tags: | added: kernel-series-unknown |
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
Changed in linux (Ubuntu): | |
status: | Confirmed → Invalid |
To post a comment you must log in.
$ uname -a
Linux lucid 2.6.32-16-generic #25-Ubuntu SMP Tue Mar 9 16:33:12 UTC 2010 x86_64 GNU/Linux
It is the latest kernel as available for Lucid.