Bug 5662
Summary: | 6.1 upgrade causes fsck error on boot | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | piller |
Component: | installer | Assignee: | Matt Wilson <msw> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.1 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 1999-10-22 18:27:25 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
piller
1999-10-07 01:08:01 UTC
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 |