Bug 57228 - Upgrade to Red Hat 7.2 fails on system running 7.0
Summary: Upgrade to Red Hat 7.2 fails on system running 7.0
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: installer   
(Show other bugs)
Version: 7.2
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2001-12-07 11:16 UTC by Toralf
Modified: 2007-04-18 16:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 18:48:17 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
/proc/scsi/scsi (335 bytes, text/plain)
2001-12-13 08:16 UTC, Toralf
no flags Details
/proc/partitions (337 bytes, text/plain)
2001-12-13 08:18 UTC, Toralf
no flags Details
/proc/scsi/modules (967 bytes, text/plain)
2001-12-13 08:20 UTC, Toralf
no flags Details

Description Toralf 2001-12-07 11:16:40 UTC
Description of Problem:
Installation of Red Hat Linux 7.2 fails on one of our systems which is
happily running Red Hat 7.0 today. The harware is:

Mainboard: Asus PDB-DS
Disk: Seagate ST16403LW (36Gb Cheetah)
SCSI controller: Tekram DC-390 U2B or on-board Adaptec AIC-7890; have tried
connecting the disk to both, whith the same result

How Reproducible:
Every time

Steps to Reproduce:
1. Start installer; I'm assuming you know how. 
2. Select "Custom" or "Upgrade Existing System" 
3. Select "Disk Druid" for "Custom" partitions.

Actual Results:
"Upgrade Existing System" says:

You don't have any Linux partitions. You can't
upgrade this system

"Custom" says:

An error has occured - no valid devices
were found on which to create new
filesystems. Please check you hardware
for the cause of this problem.

Expected Results:
Installation started.

Additional Information:
If I go to VC-2, I can access the root file system by doing:

# mknod /dev/sda6 b 8 6
# mount /dev/sda6 <somewhere>

Note that the disk was NOT automatically mounted on /mnt/sysimage.

As you can see, I know *everything* there is to know about the disk and its

Comment 1 Jeremy Katz 2001-12-12 20:13:26 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?

Comment 2 Toralf 2001-12-13 08:16:57 UTC
Created attachment 40468 [details]

Comment 3 Toralf 2001-12-13 08:18:47 UTC
Created attachment 40469 [details]

Comment 4 Toralf 2001-12-13 08:20:46 UTC
Created attachment 40470 [details]

Comment 5 Toralf 2001-12-13 08:28:05 UTC
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.

Comment 6 Toralf 2002-01-11 13:22:34 UTC
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...

Comment 7 Jeremy Katz 2002-03-01 06:09:01 UTC
If you run parted on /dev/sda after creating the device node in the installer
environment, do you get any sort of errors?

Comment 8 Michael Fulbright 2002-04-10 18:20:30 UTC
Closing due to inactivity, please reopen if you contine to have problems.

Comment 9 Red Hat Bugzilla 2006-02-21 18:48:17 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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