Description of problem: Intel storage matrix raid array visible on live media. Not detected upon install. Commenting out isw_* filter in fedorage-storage-init allows array to be activated and mounted by fstab. Suspect mdadm not detecting and mounting intel fake raid as needed. Found mdadm is not even installed on system. Version-Release number of selected component (if applicable): How reproducible: DVD and cd installs both effected. Steps to Reproduce: 1. Boot live media 2. Inspect hard drives visible to os (all arrays visible) 3. Install and reboot: No arrays visible, only individual disks. Reproducible: Steps to Reproduce:
Some additional info: cat /proc/stat shows: Personalities : [raid1] md124 : active (auto-read-only) raid1 sdc[1] sdd[0] 488383488 blocks super external:/md127/0 [2/2] [UU] md125 : active (auto-read-only) raid1 sdb[1] sda[0] 625129472 blocks super external:/md126/0 [2/2] [UU] md126 : inactive sdb[1](S) sda[0](S) 4520 blocks super external:imsm md127 : inactive sdd[1](S) sdc[0](S) 5928 blocks super external:imsm While blkid shows: /dev/md124p1: UUID="31632D4D784933D3" TYPE="ntfs" Which I mounted via fstab using uuid to /mnt/Videos. This appears to have worked in terms of data is visible at /mnt/Videos. Mount shows: /dev/md124p1 on /mnt/Videos type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096) df shows: /dev/md124p1 466G 101M 466G 1% /mnt/Videos Whats concerning is that diskdrake DOES NOT show the array, but continues to show individual disks, with no raid arrays.
Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 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 Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD