Bug 57228
Summary: | Upgrade to Red Hat 7.2 fails on system running 7.0 | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Toralf <bugzilla> | ||||||||
Component: | installer | Assignee: | Jeremy Katz <katzj> | ||||||||
Status: | CLOSED NOTABUG | QA Contact: | Brock Organ <borgan> | ||||||||
Severity: | medium | Docs Contact: | |||||||||
Priority: | medium | ||||||||||
Version: | 7.2 | ||||||||||
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: | 2006-02-21 18:48:17 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: | |||||||||||
Attachments: |
|
Description
Toralf
2001-12-07 11:16:40 UTC
Can you get the output of /proc/scsi/scsi, /proc/partitions, and /proc/modules from the installer environment by copying them to a floppy from the shell on tty2 and attach them to this bug report? Created attachment 40468 [details]
/proc/scsi/scsi
Created attachment 40469 [details]
/proc/partitions
Created attachment 40470 [details]
/proc/scsi/modules
The requested files have been attached. Once again, note that I have tried various different variants of the SCSI setup; I have disabled the Adaptec, removed the Tekram and connected the disk to the Adaptec, disconnected the CD-ROM etc. (and started installation via ftp), all with the same result. In other words, the configuration outlined in the /proc files is only one of a number of similar ones where the installation fails. I tried connecting the harddisk to a different host, and got the same result there. Looks like the installer has a problem with the particular hard drive I'm using - it's a Seagate ST136403LW. I have installated successfully on at least one other unit of the same model, though. I have now given up using anaconda, and upgraded the system via "live" package installation (exactly how bad is that, by the way?), and it seems to work quite well after that. In other words, it is just the installer that has problems with my hardware, not Linux itself. (Just as I thought.) BTW, I'm used a custom front-end that will resolve dependencies etc. to do the actual installation. I wrote it a while back because I couldn't find any standard utilities that would do quite what I wanted... If you run parted on /dev/sda after creating the device node in the installer environment, do you get any sort of errors? Closing due to inactivity, please reopen if you contine to have problems. Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |