Red Hat Bugzilla – Bug 5662
6.1 upgrade causes fsck error on boot
Last modified: 2008-05-01 11:37:52 EDT
I have upgraded 3 machines from RH 6.0 to RH 6.1 and two of the machines now fail the boot up process with a warning about a partition or fsck error and kick me into a shell to allow me to fix the problem (which so far I have not). I run fsck on all of my paritions (/, /home/, /usr, /opt, /tmp, /var) and they are clean with no problem. I can manually mount each partition and run the machine as root user, network, you name it but when I reboot I get the same error. I need to figure this out quick or save my data and do a fresh install.
I posted this one, have now fixed problem. Apparently the upgrade changed the filesystem mount options in /etc/fstab so the filesystems do not auto mount at boot. To fix change the mount options to "defaults" or add "auto" to the mount option list in /etc/fstab.
I had the same problem: false fsck error occurring on bootup after having upgraded from RH 5.2 to 6.1. I fixed it by adding the -s option to the second call to fsck in rc.sysinit: initlog -c "fsck -C -T -R -A -a -s $fsckoptions" Works like a charm, but at the cost of parallel fsck checks on my drives.
This issue has been assigned to a developer for further action.
Not able to replicate in test lab. Send more information if you are able to provide more specific examples.
After upgrade to 6.1, and following several successful configurations and reboots, on one reboot it refused to mount /var; althopugh fsck reported 'clean', it also reported 'failed' and dropped me into root logi