Description of problem: In rescue mode. All is well until Anaconda gets to
locating partitions. Message: Could not find any linux partitions. After
dropping into shell, I was able to mount / with no problems. It is /dev/sda3
and its ext3.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
What kind of controller is sda attached to, and did you see it load any SCSI
scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.3
The controller was recognized by Anaconda. The aic7xxx driver was loaded.
Could you try booting with 'linux upgradeany'?
I guess I wasn't clear on the sequence of events. The upgrade proceeded without
any problem, so I assume that upgradeany would work OK as well. It was the
_subsequent_ (ie after the upgrade was complete) of rescue mode where the
The 'upgradeany' option relaxes our checking of potential partitions containing
your '/' filesystem. If for example you have removed or changed the
Hmmmm ... forgive me for being somewhat anal here, but ...
is it not the case that "linux upgradeany" will try to upgrade my installation?
And how will that affect the operation of "linux rescue"?
Red Hat Linux release 9 (Shrike)
The 'upgradeany' option just influcences how strict we are when trying to
auto-detect existing installations. In rescue mode we use the same function to
find existing installations and offer to mount them for you. The 'upgradeany'
option DOES NOT start an upgrade process if you also pass the 'rescue' option.
We probably need to have an alias for 'upgradeany' that isn't as daunting
"linux rescue upgradeany" found the two disks with bootable partitions and found
the root partition on the one selected.
Current code automatically relaxes the restrictions for rescue mode (since you
can chroot into whatever install you want as far as I'm concerned :)