Re: Raid1 recovery problem - need help!

3 messages, 3 authors, 2003-10-09 · open the first message on its own page

Re: Raid1 recovery problem - need help!

From: Neil Brown <hidden>
Date: 2003-09-26 07:45:31

On Friday September 26, tomimo+linux-raid@ncircle.nullnet.fi wrote:
quoted
superblock and allow you to access what is there.
Ok, now the status is after the following command:
quoted
mdadm -v --assemble /dev/md5 /dev/md3 /dev/md4
mdadm: looking for devices for /dev/md5
mdadm: /dev/md3 is identified as a member of /dev/md5, slot 0.
mdadm: /dev/md4 is identified as a member of /dev/md5, slot 1.
mdadm: added /dev/md4 to /dev/md5 as 1
mdadm: added /dev/md3 to /dev/md5 as 0
mdadm: /dev/md5 assembled from 1 drive - not enough to start the array.
Hmm. my guess is that if you "mdadm -E" /dev/md3 and /dev/md4, you
will find that the event numbers a different.  i.e. it things /dev/md4
is too out-of-date.
Presumably the mirror halves fell out-of-sync some time ago and for
some reason never rebuild properly.

You could try
   mdadm --assemble --force /dev/md5 /dev/md3 /dev/md4

It should assemble successfully, but I make not promises about what
sort of data will be on them.

NeilBrown

/proc/mdstat:

Personalities : [linear] [raid0] [raid1] [raid5]
read_ahead 1024 sectors
md5 : inactive md3[0] md4[1]
      0 blocks

md4 : active raid1 sdc2[0]
      60034880 blocks [2/1] [U_]

md3 : active raid1 hdg2[2] hde2[1]
      58616640 blocks [2/1] [_U]


Any ideas ? :)

Regards,
Tomi Orava

-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Raid1 recovery problem - need help!

From: Tomi Orava <hidden>
Date: 2003-09-26 08:14:54

Neil,

Thank you, the last command was able to get the RAID1+0 running
as needed. Unfortunately, the re-assembled disc is not functional.
However, I still wonder if I have made a mistake in figuring out the
proper failed disc (based on your comments) ... Therefore, I'll have
to switch the discs as soon as I get back to home and check if I can
get anything else from the raid-device with your incstructions
(as neither of the discs are absolutely dead, one of them just
hangs the machine completely sooner or later ie in 5mins or 1h).

I'm also wondering, how it can be that a single IDE-disc (in this
case IBM 60GXP or 75GXP don't know which one for sure) is able to
halt the whole machine ... I have 6 discs connected to that server
and they are all the only drives in their own channel (no slaves).
Four of the drives are connected to HPT374-chip and two more to
Sil680 PCI-card. I don't really expect any solution for this question,
I'm more or less just wondering if anyone else has had similar
problems with their hardware ?
It should assemble successfully, but I make not promises about what
sort of data will be on them.
Thank you for your time Neil!

Sincerely,
Tomi Orava

PS. I wonder if there exists any problem solving examples about real life
    cases in any of the docs (HOWTO, man-page etc).
    Perhaps it might be helpful to some one if I just gather up
    the mails related to this case and put them on the web for example ...
    even though every problem has little bit different environment &
    setup, but it might still help in deciding which commands to run
    and which ones to avoid (in order to not lose data by mistake).






raid resync

From: Bo Moon <hidden>
Date: 2003-10-09 01:36:04

Neil,

From md.c, there must be some changes or improvement to RAID1&5 resync code,
which enabled the request based resynchronization.

Does it mean we could enable or disable this resync?
If so, how could we make it(where in the code)?

Why do we have this feature the disk will be under no integrity if we
disable this resync?

Thanks in advance,

Bo
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help