mdadm can't start RAID0 volume after power failure
Looking at your mdadm.conf file, and at the results of your mdadm -QE --scan, I can see that the UUID numbers are different. Which UUID numbers do you get when you run mdadm -E /dev/sd{e,f,g,h,i,j,k}1? I tried to follow the web page link in your post and I couldn't get to it. Are you trying to start your array with the wrong UUID number by chance?
Regards,
Andy Liebman
Quoted 8 lines
# cat /etc/mdadm/mdadm.confDEVICE /dev/sd[efghijk]1
ARRAY/dev/md0level=raid0 num-devices=7
UUID=46c66ef8:8acf2810:48adb2d3:85b04900Still, every # mdadm -E /dev/sd[efghijk]1 looks ok, output can be found
here: >http://philou.org/mdadm.log
Quoted 5 lines
mdadm.conf is here : http://philou.org/mdadm.conf
# mdadm -QE --scan ARRAY /dev/md0 level=raid0 num-devices=7 UUID=3c1ad678:d3a7a1ed:1112143d:68b4e569
Hello Andy,
On Fri, 17 Dec 2004 12:44:20 EST
[email protected] wrote:
| Looking at your mdadm.conf file, and at the results of your mdadm -QE --scan,
| I can see that the UUID numbers are different. Which UUID numbers do you get
| when you run mdadm -E /dev/sd{e,f,g,h,i,j,k}1?| I tried to follow the web page link in your post and I couldn't get to it.
The link is ok and works.
| Are you trying to start your array with the wrong UUID number by chance?
Indeed !! starting it with the detected UUID allowed me to start it:
# mdadm -v -A /dev/md0 --uuid=3c1ad678:d3a7a1ed:1112143d:68b4e569 mdadm: looking for devices for /dev/md0 mdadm: /dev/sdk1 is identified as a member of /dev/md0, slot 6. mdadm: /dev/sdj1 is identified as a member of /dev/md0, slot 5. mdadm: /dev/sdi1 is identified as a member of /dev/md0, slot 4. mdadm: /dev/sdh1 is identified as a member of /dev/md0, slot 3. mdadm: /dev/sdg1 is identified as a member of /dev/md0, slot 2. mdadm: /dev/sdf1 is identified as a member of /dev/md0, slot 1. mdadm: /dev/sde1 is identified as a member of /dev/md0, slot 0. mdadm: added /dev/sdf1 to /dev/md0 as 1 mdadm: added /dev/sdg1 to /dev/md0 as 2 mdadm: added /dev/sdh1 to /dev/md0 as 3 mdadm: added /dev/sdi1 to /dev/md0 as 4 mdadm: added /dev/sdj1 to /dev/md0 as 5 mdadm: added /dev/sdk1 to /dev/md0 as 6 mdadm: added /dev/sde1 to /dev/md0 as 0 mdadm: /dev/md0 has been started with 7 drives.
and it mounted fine !
Still, this is the first time that such a thing happens to me. What could be the reason that UUID would be changed ?
Thanks much,
Philippe
| | Regards, | Andy Liebman | | ># cat /etc/mdadm/mdadm.conf | > | >DEVICE /dev/sd[efghijk]1 | >ARRAY /dev/md0 level=raid0 num-devices=7 | >UUID=46c66ef8:8acf2810:48adb2d3:85b04900 | > | | >Still, every # mdadm -E /dev/sd[efghijk]1 looks ok, output can be found | here: >http://philou.org/mdadm.log | >mdadm.conf is here : http://philou.org/mdadm.conf | > | ># mdadm -QE --scan | >ARRAY /dev/md0 level=raid0 num-devices=7 | >UUID=3c1ad678:d3a7a1ed:1112143d:68b4e569 | - | To unsubscribe from this list: send the line "unsubscribe linux-raid" in | the body of a message to [email protected] | More majordomo info at http://vger.kernel.org/majordomo-info.html | |