Description of problem: When I boot from Fedora 21 Workstation Live, no RAID device is created for the IMSM volume that I am using in Fedora 20. Version-Release number of selected component (if applicable): mdadm-3.3.2-1.fc21.x86_64 Steps to Reproduce: 1. Create live USB from Fedora 21 Workstation Live iso. 2. Boot live USB. Actual results: [root@localhost liveuser]# cat /proc/mdstat Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] md127 : inactive sda[0](S) 2828 blocks super external:imsm unused devices: <none> Expected results: There should be a RAID 1 device. Additional info: [root@localhost liveuser]# fdisk -l /dev/sda Disk /dev/sda: 149 GiB, 160000000000 bytes, 312500000 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 Disklabel type: dos Disk identifier: 0x000cc5af Device Boot Start End Sectors Size Id Type /dev/sda1 * 2048 1026047 1024000 500M 83 Linux /dev/sda2 1026048 2050047 1024000 500M 83 Linux /dev/sda3 2050048 312494079 310444032 148G 8e Linux LVM [root@localhost liveuser]# fdisk -l /dev/sdb Disk /dev/sdb: 149 GiB, 160000000000 bytes, 312500000 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 Disklabel type: dos Disk identifier: 0x000cc5af Device Boot Start End Sectors Size Id Type /dev/sdb1 * 2048 1026047 1024000 500M 83 Linux /dev/sdb2 1026048 2050047 1024000 500M 83 Linux /dev/sdb3 2050048 312494079 310444032 148G 8e Linux LVM [root@localhost liveuser]#
Intel Matrix Storage Manager option ROM v8.5.2.1002 ICH 10R/DO
I'm also not finding a RAID 1 volume on a newer computer: Intel Rapid Storage Technology - Option ROM - 12.7.0.1936 I previously installed F21 Beta onto this volume but now I can't seem to find it when booting with the final Live image.
On the newer computer, I deleted the RAID 1 volume and then re-created it. After that, when I booted from the Fedora 21 Live image, the RAID 1 device (/dev/md126) was created as expected.
I have noticed that the default kernel command line for Fedora Live Workstation 21 includes the following: rd.md=0 Is it OK to edit the kernel command line at boot time and remove that parameter?
(In reply to Aram Agajanian from comment #4) > I have noticed that the default kernel command line for Fedora Live > Workstation 21 includes the following: > > rd.md=0 > > Is it OK to edit the kernel command line at boot time and remove that > parameter? You should be fine removing that line for the live image. Does this still happen with F22? Jes
(In reply to Jes Sorensen from comment #5) > (In reply to Aram Agajanian from comment #4) > > I have noticed that the default kernel command line for Fedora Live > > Workstation 21 includes the following: > > > > rd.md=0 > > > > Is it OK to edit the kernel command line at boot time and remove that > > parameter? > > You should be fine removing that line for the live image. > > Does this still happen with F22? > Using Intel Rapid Storage Technology (12.7.0.1936). There is an existing Fedora 21 installation on a RAID1 volume that has been created from Physical Device IDs 0 and 1. Looking at /proc/mdstat, I would expect to see a device named md126 for the RAID1 device. In Fedora 21 Live: no device is created whether or not rd.md=0 is present In Fedora 22 Live: no device is created whether or not rd.md=0 is present I then deleted the RAID1 volume (which contained the existing Fedora 21 installation) and created a new RAID 1 volume. In Fedora 21 Live: raid1 md126 device is created whether or not rd.md=0 is present In Fedora 22 Live: raid1 md126 device is created whether or not rd.md=0 is present
It seems that F22 Live doesn't create an md126 device if there is a GPT on the RAID1 volume. F22 Live will create an md126 device if there is an MBR (i.e. disklabel type: dos) on the RAID1 volume. It took a little effort to get Anaconda to install onto a raid1 device with an MBR since the disk size is 2.73 TB. I created the partitions with fdisk before running Anaconda.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.