Ignoring a broken clock results in infinite reboots; not ignoring results in fsck failure; no solution to this problem
Bug #563618 reported by
Oliver Grawert
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
e2fsprogs |
Unknown
|
Unknown
|
|||
e2fsprogs (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Lucid |
Won't Fix
|
Undecided
|
Unassigned | ||
flash-kernel (Ubuntu) |
Fix Released
|
High
|
Oliver Grawert | ||
Lucid |
Fix Released
|
High
|
Oliver Grawert | ||
initramfs-tools (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Lucid |
Fix Released
|
High
|
Unassigned | ||
mountall (Ubuntu) |
Invalid
|
High
|
Unassigned | ||
Lucid |
Invalid
|
High
|
Unassigned |
Bug Description
Binary package hint: util-linux
while e2fsck has the optioon to add an e2fsck.conf with an option to ignore broken system clocks, fsck does not have the ability to override this.
that behavior together with a mountall bug which does not give the user a maintenance shell when fsck exits but makes it go into an endless loop renders many ARM platforms we support unbootable (we have several development boards that either come with an unloaded (imx51) or without battery at all (omap beagleboard)).
the only workaround in this case is to edit both fstab files on the rootfs (/etc/fstab and /lib/init/fstab) and change the pass number for the root filesystem from 1 to 0
Changed in mountall (Ubuntu Lucid): | |
milestone: | ubuntu-10.04 → none |
affects: | util-linux (Ubuntu Lucid) → initramfs-tools (Ubuntu Lucid) |
To post a comment you must log in.
bug #501801 and #562898 seem to be related mountall bugs