raid md126, md127 problem after reboot, howto fix?
Hi List
I have no deep unterstand about raids, beside setting them up initially and replacing disks if needed. So this error has never happened to me before:
After a reboot i have a really strange behaviour on my server. Disks are not marked faulty, but raid is "fallend apart".
/proc/mdstat shows me:
md126 : active raid1 sda1[0]
10485696 blocks [2/1] [U_]
md127 : active raid1 sda2[0]
721558464 blocks [2/1] [U_]
md1 : active raid1 sdb1[1]
10485696 blocks [2/1] [_U]
md2 : active raid1 sdb2[1]
721558464 blocks [2/1] [_U]
wished would be something similar to:
md1 : active raid1 sdb1[1] sda1[0]
10238912 blocks [2/2] [UU]
md2 : active raid1 sdb2[1] sda2[0]
1942746048 blocks [2/2] [UU]
Currently only md1, md2 are running. nmon shows me, that only disks sdb is active, sda is not doing anything.
I run debian squeeze.
I am a bit concerned what to do, because at the moment i run on one disk only and if things go wrong i end up with a server not running (downtime) and possible data loss (beside backups).
Any ideas what i should do? Howto put the raid back together, possibly in live mode, without rebooting in rescue mode and risk long downtime?
Any help would be greatly appreciated as by now the only thing i had to do was resyncing a disk after usual hd crash.
Best
marc
Quoted 26 lines · Marc Widmer
Hi List
I have no deep unterstand about raids, beside setting them up initially and replacing disks if needed. So this error has never happened to me before:
After a reboot i have a really strange behaviour on my server. Disks are not marked faulty, but raid is "fallend apart".
/proc/mdstatshows me:md126 : active raid1 sda1[0]
10485696 blocks [2/1] [U_]md127 : active raid1 sda2[0]
721558464 blocks [2/1] [U_]md1 : active raid1 sdb1[1]
10485696 blocks [2/1] [_U]md2 : active raid1 sdb2[1]
721558464 blocks [2/1] [_U]wished would be something similar to:
md1 : active raid1 sdb1[1] sda1[0]10238912 blocks [2/2] [UU]
Quoted 7 lines
md2 : active raid1 sdb2[1] sda2[0]
1942746048 blocks [2/2] [UU]Currently only md1, md2 are running. nmon shows me, that only disks sdb is active, sda is not doing anything.
I run debian squeeze.
What version of mdadm are you running? 3.2.6 or thereabouts?
Quoted 11 lines
I am a bit concerned what to do, because at the moment i run on one disk only and if things go wrong i end up with a server not running (downtime) and possible data loss (beside backups).
Any ideas what i should do? Howto put the raid back together, possibly in live mode, without rebooting in rescue mode and risk long downtime?
Any help would be greatly appreciated as by now the only thing i had to do was resyncing a disk after usual hd crash.
The reason I ask is this looks like a bug I had - if I'm right it's a known problem and you need to upgrade mdadm.
Cheers,
Wol
Quoted 41 lines · Wols Lists
Quoted 26 lines · Marc Widmer
Hi List
I have no deep unterstand about raids, beside setting them up initially and replacing disks if needed. So this error has never happened to me before:
After a reboot i have a really strange behaviour on my server. Disks are not marked faulty, but raid is "fallend apart".
/proc/mdstatshows me:md126 : active raid1 sda1[0]
10485696 blocks [2/1] [U_]md127 : active raid1 sda2[0]
721558464 blocks [2/1] [U_]md1 : active raid1 sdb1[1]
10485696 blocks [2/1] [_U]md2 : active raid1 sdb2[1]
721558464 blocks [2/1] [_U]wished would be something similar to:
md1 : active raid1 sdb1[1] sda1[0]10238912 blocks [2/2] [UU]Quoted 7 lines
md2 : active raid1 sdb2[1] sda2[0]
1942746048 blocks [2/2] [UU]Currently only md1, md2 are running. nmon shows me, that only disks sdb is active, sda is not doing anything.
I run debian squeeze.
What version of mdadm are you running? 3.2.6 or thereabouts?
Quoted 5 lines
I am a bit concerned what to do, because at the moment i run on one disk only and if things go wrong i end up with a server not running (downtime) and possible data loss (beside backups).
Quoted 8 lines
Quoted 6 lines
Any ideas what i should do? Howto put the raid back together, possibly in live mode, without rebooting in rescue mode and risk long downtime?
Any help would be greatly appreciated as by now the only thing i had to do was resyncing a disk after usual hd crash.
The reason I ask is this looks like a bug I had - if I'm right it's a known problem and you need to upgrade mdadm.
Yeah, pretty much sounds like the bad udev rules with Squeeze and old mdadm. E.g. deactivation of the MD udev rules and assembling via init scripts is a way to workaround this.
I have some test VMs providing MD RAID-1 on iSCSI targets and have seen the same issue when logging in to the targets. Deactivation of the udev rules and manual assembly helped.
Cheers,
Sebastian
Quoted 32 lines · Marc Widmer
Hi List
I have no deep unterstand about raids, beside setting them up initially and replacing disks if needed. So this error has never happened to me before:
After a reboot i have a really strange behaviour on my server. Disks are not marked faulty, but raid is "fallend apart".
/proc/mdstatshows me:md126 : active raid1 sda1[0]
10485696 blocks [2/1] [U_]md127 : active raid1 sda2[0]
721558464 blocks [2/1] [U_]md1 : active raid1 sdb1[1]
10485696 blocks [2/1] [_U]md2 : active raid1 sdb2[1]
721558464 blocks [2/1] [_U]wished would be something similar to:
md1 : active raid1 sdb1[1] sda1[0]10238912 blocks [2/2] [UU]md2 : active raid1 sdb2[1] sda2[0]
1942746048 blocks [2/2] [UU]Currently only md1, md2 are running. nmon shows me, that only disks sdb is active, sda is not doing anything.
Quoted 8 lines
I run debian squeeze.
I am a bit concerned what to do, because at the moment i run on one disk only and if things go wrong i end up with a server not running (downtime) and possible data loss (beside backups).
Any ideas what i should do? Howto put the raid back together, possibly in live mode, without rebooting in rescue mode and risk long downtime?
Just stop all arrays which aren't in use at the moment and assemble them manually. If they are already running degraded, then add the now unassociated disks to their respective running arrays.
$ mdadm --stop /dev/md126 $ mdadm --stop /dev/md127 $ mdadm /dev/md1 --add /dev/sda1 $ mdadm /dev/md2 --add /dev/sda2
This could require some syncing but then everything should be normal again.
Cheers,
Sebastian
Quoted 6 lines · Sebastian Parschauer
Quoted 2 lines
Quoted 2 lines
Any ideas what i should do? Howto put the raid back together, possibly in live mode, without rebooting in rescue mode and risk long downtime?
Just stop all arrays which aren't in use at the moment and assemble them manually. If they are already running degraded, then add the now unassociated disks to their respective running arrays.
Quoted 6 lines
$ mdadm --stop /dev/md126 $ mdadm --stop /dev/md127 $ mdadm /dev/md1 --add /dev/sda1 $ mdadm /dev/md2 --add /dev/sda2This could require some syncing but then everything should be normal again.
This isn't just a Debian/Ubuntu problem - I run gentoo.
And isn't there a re-add option? That will hopefully just require a recovery rather than a total resync.
Cheers,
Wol
Quoted 7 lines · Wols Lists
Quoted 6 lines · Sebastian Parschauer
Quoted 2 lines
Quoted 2 lines
Any ideas what i should do? Howto put the raid back together, possibly in live mode, without rebooting in rescue mode and risk long downtime?
Just stop all arrays which aren't in use at the moment and assemble them manually. If they are already running degraded, then add the now unassociated disks to their respective running arrays.
Quoted 8 lines
Quoted 6 lines
$ mdadm --stop /dev/md126 $ mdadm --stop /dev/md127 $ mdadm /dev/md1 --add /dev/sda1 $ mdadm /dev/md2 --add /dev/sda2This could require some syncing but then everything should be normal again.
This isn't just a Debian/Ubuntu problem - I run gentoo.
Okay.
Quoted 2 lines
And isn't there a re-add option? That will hopefully just require a recovery rather than a total resync.
Yes, sure, --re-add should be tried first. If it doesn't work, then the --add option will definitely work.
Cheers,
Sebastian