[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: mdadm gives segmentatin fault on wheezy. RAID array now incomplete.



On Thu, 10 Oct 2013 01:59:21 +0000, Hendrik Boom wrote:

> On Wed, 09 Oct 2013 10:59:48 -0600, Shane Johnson wrote:
> 
>> On Wed, Oct 9, 2013 at 10:50 AM, Hendrik Boom <hendrik@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
>>>
>>>
...
...
> 
> Thanks, but I'm not out of the woods yet.
> 
> I've found a relevant bug report:
> 
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718896
> 
> And the version of mdadm available in Debian isn't the most recent.
> Version 3.2.6 has been announced on http://git.neil.brown.name/?
> 
p=mdadm.git;a=blob;f=ANNOUNCE-3.2.6;h=f5cfd4920576fba77c7162c331b87873f8bfa5ef;hb=HEAD
> 
> The second item on its git log says
> 
> 0d478e2 mdadm: Fix Segmentation fault.
> 
> I have no idea whether this is the same segmentation fault I'm runnin
> into.  But it might be.
> 
> And apparently upstream development is already at version mdadm=3.3. 
> Not sure if I can really wait for Debian to migrate the relevant bug fix
> into wheezy to rebuild my RAID array.  Assuming there is a relevant bug
> fix,
> of course.
> 
> -- hendrik
> 
> 
> -- hendrik

The problem seems to be related to a hard drive connectivity problem.
I shut down my system, and wiggled all the SATA cables connecting the 
drives to the electronics.  They seemed to be firmly connected.
But after that, when I rebooted, I could repair the RAID with no problems.

Still, mdadm shouldn't be giving a segmentation fault on hard drive 
connectivity problems.

-- hendrik


Reply to: