Bug 76365 - installer aborts during upgrade with RAID error
Summary: installer aborts during upgrade with RAID error
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda   
(Show other bugs)
Version: 8.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
Depends On:
TreeView+ depends on / blocked
Reported: 2002-10-20 22:19 UTC by adam.huffman
Modified: 2007-04-18 16:47 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-03-25 23:54:55 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
output of tune2fs -l on /dev/md0 (under 7.3) (1.34 KB, text/plain)
2002-10-21 11:27 UTC, adam.huffman
no flags Details

Description adam.huffman 2002-10-20 22:19:05 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2b) Gecko/20021017

Description of problem:
When I try to upgrade a &.3 system to 8.0, the installer stops and reboots the
system when it tries to mount the software raid device /dev/md0.  This device
uses partitions /dev/hda1 and /dev/hdc1.  The installer firstly complains about
/dev/hda1 and then that it cannot mount /dev/md0 and then it forces a reboot. 
/dev/md0 (and /dev/md1) mount with no problems in 7.3

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Boot to 8.0 CDs
2. Select "upgrade existing system"

Actual Results:  Installer aborts

Expected Results:  Installer should mount /dev/md0 and continue

Additional info:

Comment 1 Jeremy Katz 2002-10-21 04:24:31 UTC
Are there are any errors listed on tty3 or tty4?

Comment 2 adam.huffman 2002-10-21 11:25:46 UTC
When the first installer error appears - "Error mounting file system on hda1:
Invalid argument" - the following appears on the console:

JBD: no valid journal superblock found
EXT3-fs: error loading journal

Later another error appears in the installer - "Error mounting device md0 as
/mnt/raid: Invalid argument. This most likely means this partition has not been
formatted".  The console output is:

EXT3-fs: unable to read superblock

Comment 3 adam.huffman 2002-10-21 11:27:08 UTC
Created attachment 81304 [details]
output of tune2fs -l on /dev/md0 (under 7.3)

Comment 4 Jeremy Katz 2002-10-24 19:02:42 UTC
What does your /etc/fstab look like?

Comment 5 adam.huffman 2002-10-25 08:06:54 UTC
LABEL=/                /                       ext3    defaults        1 1
LABEL=/boot            /boot                   ext3    defaults        1 2
none                    /dev/pts                devpts  gid=5,mode=620  0 0
LABEL=/home          /home                   ext3    defaults        1 2
none                    /proc                   proc    defaults        0 0
none                    /dev/shm                tmpfs   defaults        0 0
LABEL=/tmp             /tmp                    ext3    defaults        1 2
LABEL=/usr             /usr                    ext3    defaults        1 2
LABEL=/usr/local      /usr/local              ext3    defaults        1 2
LABEL=/var             /var                    ext3    defaults        1 2
/dev/hdg8               swap                    swap    defaults        0 0
/dev/fd0                /mnt/floppy             auto    noauto,owner,kudzu 0 0
/dev/md0		/mnt/raid		ext3	defaults,user	0 0	
/dev/md1		/mnt/raid1		ext3	defaults,user	0 0	
/dev/sda2		/mnt/firewire		auto	defaults,noauto,user	
0 0
/dev/sda1		/mnt/firewire-win	vfat	defaults,noauto,user	
0 0
/dev/sdb1		/mnt/fw160		ext3	defaults,noauto,user	
0 0
/dev/hde1		/mnt/ibm-root		auto	defaults,noauto,user	
0 0
/dev/hde2		/mnt/ibm-2    		auto	defaults,noauto,user	
0 0
/dev/cdrom              /mnt/cdrom              iso9660 noauto,owner,kudzu,ro 0 0

Comment 6 Jeremy Katz 2002-10-31 23:36:06 UTC
What do you get if you run 'raidstart /dev/md0' from tty2?

Comment 7 adam.huffman 2002-11-04 22:27:08 UTC
I get the following:

"could not find devices associated with raid device md0"

This happens even if I copy over raidtab from the existing / partition to the
installation /etc

Comment 8 Jeremy Katz 2003-01-03 07:35:42 UTC
Could you attach your raidtab?

Comment 9 adam.huffman 2003-01-06 15:47:36 UTC
The partitions comprising /dev/md1 are being used for something else at the moment.

raiddev /dev/md0
         raid-level      0
         nr-raid-disks   2
         nr-spare-disks  0
         chunk-size      64
         persistent-superblock 1
         device          /dev/hda1
         raid-disk       0
         device          /dev/hdc1
         raid-disk       1

#raiddev        /dev/md1
#       raid-level      1
#       nr-raid-disks   2
#       nr-spare-disks  0
#       chunk-size      4
#       persistent-superblock   1
#       device          /dev/hda2
#       raid-disk       0
#       device          /dev/hdc2
#       raid-disk       1

Comment 10 Roland Roberts 2003-03-20 16:56:45 UTC
FYI: I had a similar problem while trying to upgrade a 7.2 system which appeared
to be fixed by running fdisk and modifying the partition type to fd.  Some of my
RAID partitions were set at type 83.

Comment 11 Jeremy Katz 2003-03-24 17:24:03 UTC
Could you copy the /tmp/syslog and /tmp/anaconda.log from your system when it
fails to mount?

Comment 12 adam.huffman 2003-03-24 17:42:48 UTC
In the end I copied the data elsewhere and deleted the RAID device, so I can't
provide that information.

Comment 13 Jeremy Katz 2003-03-25 23:54:55 UTC
Hmm... I don't see anything obvious and haven't been able to reproduce it
myself, but we've improved the error code for our next release somewhat, so
hopefully if there's a problem in the future, we can get more information out of it.

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