Lucid boot failed to complete after fsck
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux Mint |
New
|
Undecided
|
Unassigned | ||
mountall (Ubuntu) |
Confirmed
|
High
|
Unassigned | ||
Bug Description
Binary package hint: sysvinit
When the time required for file system check the boot process stopped at 70%:
"Checking disk 1 of 1 (71% complete)"
I allowed it to "run" for 10-20 minutes without completion. Then I opened another VTY (Alt+Crtl+F1) and issued a:
ps -F -C mountall:
UID PID PPID C SZ RSS PSR STIME TTY TIME CMD
root 246 1 0 1238 3464 1 08:44 ? 00:00:03 mountall --daemon --force--check
===
e2fsck version= 1.41.11 (14-Mar-2010)
===
I was able to reboot, but when I issued a 'sudo touch /forcechk' to force a fs check, it also never completed.
I was then left with the file "/forcechk" always on the root directory. I needed to boot using livecd and delete that file
in order for it to complete booting. Also using livecd running fsck on the questionable fs, I got this error:
/dev/sda7: recovering journal
Clearing orphaned inode 133461 (uid=1000, gid=1000, mode=0100644, size=32768)
Clearing orphaned inode 133459 (uid=1000, gid=1000, mode=0100600, size=492)
/dev/sda7: clean, 136513/447920 files, 558645/1791239 blocks
Next fsck showed clean.
===
"/var/log/
(Nothing has been logged yet.)
This is the second occurrence of this problem. Using daily-live for both MAR31st and APR2nd. I also updated to current level and re-tried. Same problem.
No matter what partition Lucid is put on, a fsck at boot fails.
Here's a copy of my fstab:
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda7 during installation
UUID=a5be502d-
# swap was on /dev/sda6 during installation
UUID=3c09b1da-
===
P4-2.65ghz, 1gig ram, Intel i865 video chip.
Changed in sysvinit (Ubuntu): | |
status: | New → Confirmed |
tags: | added: lucid |
Changed in sysvinit (Ubuntu): | |
status: | Confirmed → In Progress |
status: | In Progress → Confirmed |
I also noticed that on the Lucid install that does work I get the following message
when I forcechk that partition :
"Your disk needs to be checked for errors, this may take some time"
"press C to skip this test"
On the Lucid install that fails I only get:
"Checking disk 1 of 1 (71% complete)"
I never see the press C to skip.
Both installs have the same mountall and esfsck version numbers.