[mythtv-users] OT Help: mdadm segfault
Steve MacLaren
scram69 at gmail.com
Tue Sep 25 04:26:10 UTC 2007
On 9/24/07, f-myth-users at media.mit.edu <f-myth-users at media.mit.edu> wrote:
>
> > Date: Fri, 21 Sep 2007 23:47:21 -0700
> > From: "Steve MacLaren" <scram69 at gmail.com>
>
> > On 9/21/07, Steve MacLaren <scram69 at gmail.com> wrote:
> > > But it looks like I will just have to ignore the obvious
> contradictions
> > > and forge ahead trying to mount and access a 3-drive array by
> messing with
> > > /sys/block/md0/md/array_state, then wiping and re-adding the
> fourth drive...
>
> > Finally, some good news. Before I went ahead picking 3 disks at
> random and
> > assembling, I re-read through all of the posts on this thread. The
> one that
> > caught my eye was in f-myth's PPS:
> > "for each drive, try dd if=/dev/sdaN of=/dev/null bs=1M count=1000
> and see
> > if you can read the first gig of the device"
>
> > I hadn't yet tried that, so I gave it a try. Sure enough, /dev/sdd1
> cause a
> > reboot when I tried the read. Not being hardware-savvy enough to
> know which
> > of my physical drives was _actually_ /dev/sdd, I ran through a
> process of
> > elimination, removing power to one drive at a time until I could
> > successfully read from the three remaining drives.
> > Identifying the bad drive, I yanked it, replaced it with a brand new
> spare I
> > had fortuitously purchased some months ago, and restarted.
> > Upon restart, in dmesg, mdadm gave the same complaints about "dirty"
> drives
> > and the array status remained inactive. But I tried
> > mdadm -S /dev/md0
> > mdadm -Af /dev/md0 /dev/sda1 /dev/sdb1 /dev/sdc1
> > "mdadm: /dev/md0 has been started with 3 drives (out of 4)." - hey,
> that
> > looks good!
>
> Aha!
>
> You're welcome. :)
>
> (I would have tried that before the new power supply, but you can
> probably return the one you bought if you feel want to go back to
> the old one. Otherwise, you now have a fast-swap spare.
I went kinda cheap ($25) on the original PSU and have always had a nagging
feeling it might be a weak link, so I don't feel so bad about replacing it
with a beefier one - and like you say, it's never a bad idea to have a
working spare lying around.
Anyway, thanks again for your help. Samsung just sent me an RMA# for the
drive. Don't know how I would have figured this mess out without the help
from this board-
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-users/attachments/20070924/c6606acb/attachment-0001.htm
More information about the mythtv-users
mailing list