|Summary:||Installation confused by bad (ro) filesystem|
|Product:||[Retired] Red Hat Linux||Reporter:||Kenneth Corbin <kenc>|
|Component:||anaconda||Assignee:||Brent Fox <bfox>|
|Status:||CLOSED NOTABUG||QA Contact:||Brock Organ <borgan>|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2001-05-14 20:24:18 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description Kenneth Corbin 2001-05-02 06:37:22 UTC
Durring my upgrade installation, I was confused when the installer said I had a bad filesystem and that I should reboot linux to correct it before starting the install again. But rebooting my linux system didn't fix anything. Problem turned out to be a corrupt ext2 filesystem that I was keeping as a backup from a previous version. I have it flagged in fstab as readonly to protect it from being corrupted, and have the last field set to zero because it don't care overly much about it's integrity. So the installation kept saying that it was bad while the regualar linux boot just ignored it. The installer was obviously reading fstab and probably should have picked up on the last field being zero.
Comment 1 Brent Fox 2001-05-02 15:39:12 UTC
Did your backup partition have an /etc/fstab file in it?
Comment 2 Kenneth Corbin 2001-05-02 23:36:12 UTC
Yes, the backup partion would have had an /etc/fstab file that was identical to the one in the primary partition, that is the one that was being upgraded.
Comment 3 Brent Fox 2001-05-03 15:36:08 UTC
Oh, that's the problem...the installer scans the hard drive for linux partitions...any ones that have an /etc/fstab file are considered partitions that contain a "/" partition. If you rename the /etc/fstab on your backup partition to /etc/fstab.bak, do things work?
Comment 4 Brent Fox 2001-05-14 20:24:13 UTC
Closing due to inactivity. Please reopen if you have more information.