Bug 395881

Summary: Anaconda makes a RAID 1 system upgrade to Fedora Core 8 unbootable
Product: [Fedora] Fedora Reporter: Solaus Galti <solaus>
Component: anacondaAssignee: Joel Andres Granados <jgranado>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 8CC: bugzilla
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-01-31 10:48:40 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 Flags
fstab
none
mdadm.conf with the part created by anaconda and the part added by me to enable booting
none
create the file using mdadm none

Description Solaus Galti 2007-11-22 17:04:01 UTC 
Description of problem:

The booting stops with a kernel panic immediately after the upgrade of my Fedora
7 on a x64_86 system with 2 disks in Linux RAID 1.

The symptom was clearly indicating that the kernel cannot mount the root
directory. Suspecting that the RAID kernel modules were not included in the
initrd image I booted in the repair mode the installation cd and recreated the
initrd image. It didn't help.

After some further investigation I figure out what was the problem. The system
did not have previously a /etc/mdadm.conf file. Fedora 7 was every time matching
the physical raid volume between themselves.

For some reason during the upgrade process anaconda created the /etc/mdadm.conf
file but decided to list there only the volumes that where listed nominally in
my /etc/fstab: /dev/md1 and /dev/md2. For the rest of the md volumes anaconda
did not create entries in the new /etc/mdadm.conf file.  Among those volumes was
 /dev/md4 which was hosting a LVM on which the root partition actually was.

During the boot because the /etc/mdadm.conf file existing, I assume the kernel
was not doing anymore the discovery and thus never finding the LVM on which the
root was.

Version-Release number of selected component (if applicable):
Official Fedora 8 installation disk

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Solaus Galti 2007-11-22 17:04:01 UTC 
Created attachment 267111 [details]
fstab
Comment 2 Solaus Galti 2007-11-22 18:04:23 UTC 
Created attachment 267181 [details]
mdadm.conf with the part created by anaconda and the part added by me to enable booting
Comment 3 Rolf Fokkens 2007-12-10 18:43:45 UTC 
Same problem here. After the upgrade /etc/mdadm.conf seems to be incomplete,
missing the root partition. The last entry was missing after the upgrade, being
a raid5 array:

# mdadm.conf written out by anaconda
DEVICE partitions
MAILADDR root
ARRAY /dev/md3 level=raid1 num-devices=2 uuid=ece6ee77:b276bc1d:0239ad48:694e45d0
ARRAY /dev/md2 level=raid1 num-devices=2 uuid=713dcb38:131f75e0:ceada547:9ddc1617
ARRAY /dev/md4 level=raid5 num-devices=3 uuid=58698548:5f378ab7:fed52f1c:7cd4a3fd

Boot failed as this was the root partition
Comment 4 Joel Andres Granados 2008-01-28 20:25:37 UTC 
fresh fc7 installs have the /etc/mdadm.conf.  did you upgrade from fc6 to fc7
and then to fc8?  maybe anaconda is overwriting said file.  running some tests...
Comment 5 Joel Andres Granados 2008-01-28 21:09:21 UTC 
yep, as I suspected.  the file gets overwriten.  Anaconda thinks that fstab is
god :)
Comment 6 Joel Andres Granados 2008-01-30 20:06:17 UTC 
Created attachment 293478 [details]
create the file using mdadm

This is the patch for rawhide.	posted on the devel list to see what the
community says.