Bug 5506 - Unable to mount root fs after upgrade.
Unable to mount root fs after upgrade.
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
i386 Linux
high Severity high
: ---
: ---
Assigned To: Jay Turner
Depends On:
  Show dependency treegraph
Reported: 1999-10-04 15:49 EDT by Stijn Jonker
Modified: 2015-01-07 18:38 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-02-04 12:56:54 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Stijn Jonker 1999-10-04 15:49:15 EDT

Tried to upgrade from 6.0 to 6.1 today.

Have a dual pII board with onboard aic78XX.

No ide. After upgrade system won't boot.

Msg from kmod about an error not be able to load

Then unable to mount rootfs.

Think not loading initrd. but had no time. Put back old
2.2.12 kernelby boot flop. Rebooted. worked fine until now.

------- Additional Comments From   10/07/99 08:59 -------
I had a similar problem, the upgrade changed the mount options in my
/etc/fstab file, change the mount options to defaults or add auto to
the list.  Worked for me.
Comment 1 piller 1999-10-07 09:02:59 EDT
For me the upgrade changed the mount options in /etc/fstab so the
filesystem does not automount.  Change your mount options to
"defaults" or add "auto" to the list.
Worked for me.
Comment 2 Stijn Jonker 1999-10-09 13:10:59 EDT

I'm the one origanly opening the bug. But this isn't a case from a
changed fstab. It was a problem with not loading the adaptec driver.

On a second reboot i got a message that an adaptec scsi card was
found. a little late in my opinion ;-)
Comment 3 Jay Turner 2000-02-04 12:56:59 EST
Am closing out this bug, as the source of the problem has been found.  Sounds
like your Adaptec card was in some weird state when the boot operation tried to
query it, and therefore it was not able to reply and the system was not able to
find your root disk.

Note You need to log in before you can comment on or make changes to this bug.