Created attachment 461377 [details]
lvmdump output

Description of problem:

Installed F14 / to fresh Logical Volume on an existing desktop system running F12. Upon reboot existing RAID1 array containing an LVM PV with the /home LV was degraded. Adding the missing disk with mdadm went just fine, but on subsequent reboot the array was again degraded. Fixed the problem by replacing "rd_NO_MD" with "rd_MD_UUID=c81691b0:7d6755ff:bfe78010:bc810f04" on the kernel line in /boot/grub/grub.conf, it now survives a reboot correctly. I should not have had to do this, Anaconda should have configured grub.conf correctly for the existing RAID1 array when I chose to utilize it in the custom partitioning dialog. 
  

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

anaconda-14.22-1


How reproducible: 

Install system utilizing an existing RAID1 array. Upon reboot the RAID array will be degraded. 

  
Actual results:

Existing RAID1 array is degraded upon initial reboot. If rebuilt, it will again be degraded upon subsequent reboot.  


Expected results:

The RAID1 array should run normally and survive a reboot intact. 


Additional info:

The system has 3 disks configured as follows: 

[root@fasterbox ~]# fdisk -l

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000e4741

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1              63  1953520064   976760001   fd  Linux raid autodetect

Disk /dev/sdb: 300.1 GB, 300069052416 bytes
255 heads, 63 sectors/track, 36481 cylinders, total 586072368 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x260327c9

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *          63      530144      265041   83  Linux
/dev/sdb2          530145      755054      112455    7  HPFS/NTFS
/dev/sdb3          755055    17542979     8393962+  82  Linux swap / Solaris
/dev/sdb4        17542980   586067264   284262142+   5  Extended
/dev/sdb5        17543043   269217269   125837113+   7  HPFS/NTFS
/dev/sdb6       269217271   586067263   158424996+  8e  Linux LVM

Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000eea15

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1              63  1953520064   976760001   fd  Linux raid autodetect


[root@fasterbox ~]# mdadm -D /dev/md0
/dev/md0:
        Version : 0.90
  Creation Time : Thu Mar  4 01:20:39 2010
     Raid Level : raid1
     Array Size : 976759936 (931.51 GiB 1000.20 GB)
  Used Dev Size : 976759936 (931.51 GiB 1000.20 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Thu Nov 18 14:32:31 2010
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

           UUID : c81691b0:7d6755ff:bfe78010:bc810f04
         Events : 0.2103802

    Number   Major   Minor   RaidDevice State
       0       8        1        0      active sync   /dev/sda1
       1       8       33        1      active sync   /dev/sdc1



[root@fasterbox ~]# mount
/dev/mapper/VolGrp00-LogVol03 on / type ext4 (rw)
/dev/sdb1 on /boot type ext3 (rw)
/dev/mapper/VolGrp01-LogVol00 on /home type xfs (rw)


Notes: See attached lvmdump file for lvm configuration info. 
       /dev/mapper/VolGrp00-LogVol00 is the old F12 / partition
       /dev/mapper/VolGrp00-LogVol01 is utilized as a disk drive for a KVM VM  
       /dev/mapper/VolGrp00-LogVol02 is utilized as a disk drive for a KVM VM