Bug 7050 - mageia2 not compatible with mdadm-builded raid
Summary: mageia2 not compatible with mdadm-builded raid
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: Release (media or process) (show other bugs)
Version: 2
Hardware: x86_64 Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-14 10:08 CEST by alain deraedt
Modified: 2013-11-23 16:16 CET (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description alain deraedt 2012-08-14 10:08:38 CEST
Description of problem:mageia2 doesn't recognize mdadm-builded RAID volumes
I have installed  mageia2-x86_64 from nothing (this means It's not an upgrading of an already existing mageia1) on a LVM lying itself on a mdadm-builded raid volume (metadata=0.9, level=5, #devices=4); the system involves also a back-up raid6 volume.
The first time I have booted, everything was OK, and KDesktop environment didn't freeze (see bug 7000).
But the second time, splash stopped at midboot, saying it didn't recognize md5, md6, md1, md127
Here below is the /etc/mdadmconf file

ARRAY /dev/md5 level=raid5 num-devices=4 UUID=30b3de45:455285d8:0037686d:9fe88fa7
   devices=/dev/sdd2,/dev/sdc2,/dev/sdb2,/dev/sda2 auto=yes
ARRAY /dev/md6 level=raid5 num-devices=4 UUID=1da98178:3c812ec8:c03ac0ef:38b69865
   devices=/dev/sdd3,/dev/sdc3,/dev/sdb3,/dev/sda3 auto=yes
ARRAY /dev/md1 level=raid5 num-devices=4 UUID=6d8457a0:23583d9e:217904e6:da58c8b3
   devices=/dev/sdd7,/dev/sdc7,/dev/sdb7,/dev/sda7 auto=yes
ARRAY /dev/md/stock level=raid6 metadata=1.2 num-devices=6 UUID=2e823ba0:121359f8:9c8a5fc5:979774ce name=common:stock
   devices=/dev/sdf9,/dev/sde9,/dev/sdd9,/dev/sdc9,/dev/sdb9,/dev/sda9 auto=yes

I had the same problem with mandriva 2011, I never could use.


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


How reproducible:install mageia2 on system where exits mdadm-build raid volumes; if possible install it on a LVM lying on a raid volume


Steps to Reproduce:
1.
2.
3.
Comment 1 Richard Giroux 2012-09-21 03:14:38 CEST
Hi,
Same here, second disk of 2-disk LVM managed RAID1 not recognized under a freshly installed Mageia 2.  

I have no problem to boot up because Mageia is installed on a third drive.

I won't be able to use Mga2 if raid isn't functional.

CC: (none) => nrgiroux

Comment 2 alain deraedt 2012-09-21 14:34:23 CEST
RAID on Mageia2 is functional; avoid raid name as /dev/md/stock; I have simply renamed this raid volume /dev/md125 (metadata=1.2) and everything now fine works.
Amazingly the system needs an adaptation delay, as it has to learn the things.
Be patient.
alder
Comment 3 Richard Giroux 2012-09-21 17:43:25 CEST
I really don't know what "learn" means but yes my RAID array worked on the third or fourth boot sequence without my intervention !

To close the question where should I use the simpler naming convention ?  In mdamd.conf ?

Merci !
Comment 4 Manuel Hiebel 2013-10-22 12:20:56 CEST
This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad
Comment 5 Manuel Hiebel 2013-11-23 16:16:28 CET
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 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 => RESOLVED
Resolution: (none) => OLD


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