[mythtv-users] mdadm help, please

John Drescher drescherjm at gmail.com
Fri Apr 24 13:52:24 UTC 2009


On Fri, Apr 24, 2009 at 12:04 AM, Joel Means <means.joel at gmail.com> wrote:
>
> Thanks for the response.  I have answered your questions below.
>
>>
>>
>> Can you post the output of cat /proc/mdstat?
>
> # cat /proc/mdstat
> Personalities : [raid6] [raid5] [raid4]
> md0 : active (auto-read-only) raid5 sdb1[7](S) sdf1[5] sda1[4] sdd1[3]
> sde1[2] sdg1[1] sdc1[0]
>       782819968 blocks level 5, 64k chunk, algorithm 2 [7/6] [UUUUUU_]
>
> unused devices: <none>
>
>>
>> How did you assemble the array? With the force option? And no you
>> array probably is not hosed although I am worried why the spare is not
>> being added automatically.
>
> I did not use the force option.  I just did a 'mdadm -A /dev/md0
> /dev/sd{a,b,c,d,e,f,g}1
>>
>> Is the output of
>>
>> sfdisk -d /dev/sda
>>
>> the same as all other disks?
>
> All of the drives show the same:
>
> # sfdisk -d /dev/sda
> # partition table of /dev/sda
> unit: sectors
>
> /dev/sda1 : start=       63, size=976768002, Id=fd
> /dev/sda2 : start=        0, size=        0, Id= 0
> /dev/sda3 : start=        0, size=        0, Id= 0
> /dev/sda4 : start=        0, size=        0, Id= 0
>
>>
>> Do you have mdadm 2.6.4 or greater installed?
>>
> # mdadm --version
> mdadm - v2.6.7.2 - 14th November 2008
>

I have 20+ arrays in use at work for 5 years and I have never seen
anything like this. I do have ideas how to recover but I think its
best to ask the folks at the linux-raid mailing list first.

http://vger.kernel.org/vger-lists.html

John


More information about the mythtv-users mailing list