On Wed, Oct 9, 2013 at 10:50 AM, Hendrik Boom <hend...@topoi.pooq.com> wrote: > I ran > > mdadm /dev/md1 --add /dev/sdd2 > > and got a segmentation fault. > > > april:/farhome/hendrik# cat /proc/mdstat > Personalities : [raid1] > md1 : active raid1 sdb2[1] > 2391295864 blocks super 1.2 [2/1] [_U] > > md0 : active raid1 sda4[0] sdc4[1] > 706337792 blocks [2/2] [UU] > > unused devices: <none> > april:/farhome/hendrik# mdadm /dev/md1 --add /dev/sdd2 > Segmentation fault > april:/farhome/hendrik# > > > /dev/sdd2 used to be part of the /dev/md1 RAID1 array, but it went bad, > presumably becaues of a hard reset. > > I did a > > mdadm /dev/md1 --fail /dev/sdd2 --remove /dev/sdd2 > > which appeared to work correctly, and after that > > april:/farhome/hendrik# cat /proc/mdstat > Personalities : [raid1] > md1 : active raid1 sdb2[1] > 2391295864 blocks super 1.2 [2/1] [_U] > > md0 : active raid1 sda4[0] sdc4[1] > 706337792 blocks [2/2] [UU] > > unused devices: <none> > april:/farhome/hendrik# mdadm /dev/md1 --add /dev/sdd2 > Segmentation fault > april:/farhome/hendrik# > > > What now? > > -- hendrik > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: http://lists.debian.org/l341hd$6pp$1...@ger.gmane.org > Hendrik, You might look in the logs to see if they give more detail otherwise I would try removing the failed device and replacing it with another that is as close as possible to the same size and see if you can add it. I have also seen on the duct tape raid I had for a while where I would have to power cycle the box in order for it to reactivate the flaky drive. Just a couple of suggestions.
Shane -- Shane D. Johnson IT Administrator Rasmussen Equipment -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAPLO1L6wtGZSXR_Y=ek6okdj4qevv5cr6ijxnrbapjtzvdw...@mail.gmail.com
