Topic: DegradedArray event - Notifications

[ReetP]

Code: [Select]

(wiki extract)
md2 : active raid1 hdb2[1]        <-- missing partition   
     1048704 blocks [2/1] [_U]    <-- failed

I think this section of the Wiki is incorrect. I think that it shows that hda2 is missing and that hdb2 is now active. If you read a little further down :

Code: [Select]

Determine the missing physical partition, Look carefully, and fill in the gap,
in this example, it's hda2, the device being /dev/hda2

md1 : active raid1 hda3[0] hdb3[1]
md2 : active raid1 hda2[0] hdb2[1]
md0 : active raid1 hda1[0] hdb1[1]

In any event you can see in the log that is was SDA2 that was kicked:

Oct 17 09:58:26 sme-server kernel: md: kicking non-fresh sda2 from array!

You should run a proper disk check as well to be sure the drive is OK

[piran]

I wanted clarification... the two didn't seem to add up, so
that when I get a similar report I know exactly what to do;~)

[Stefano]

Code: [Select]

(wiki extract)
md2 : active raid1 hdb2[1]        <-- missing partition   
     1048704 blocks [2/1] [_U]    <-- failed

I think this section of the Wiki is incorrect. I think that it shows that hda2 is missing and that hdb2 is now active.

please raise a bug for it or create a wiki account and correct yourself, thank you

[ReetP]

please raise a bug for it or create a wiki account and correct yourself, thank you

I used to have a wiki account but I didn't use it enough to justify my 'wikiship' and I think it was withdrawn.

I have put in a request. If that fails I'll post a bug.

[ReetP]

All Wiki'ed up. Edit done - Hope it's a) correct & b) little clearer !!

[davidpfox]

Water under the bridge I know but it may have been your
sdb (not sda) that was the more likely one to be suspect?
http://wiki.contribs.org/Raid#Resynchronising_a_Failed_RAID

Perhaps my message was worded incorrectly, but what you have stated above is what I want to be cautious about 'sdb'. By the looks of this article (feels like i have read this 100 times), only if this issue arises again should I be concerned and look at using SMART.

Can someone confirm this for me?

Cheers

[piran]

All Wiki'ed up. Edit done - Hope it's a) correct & b) little clearer !!

Much, thank you;~) Will be helpful when the inevitable occurs.

[piran]

Can someone confirm this for me?

The wiki was in error, it is more correct now, please follow Stefano.

[ReetP]

Much, thank you;~) Will be helpful when the inevitable occurs.

Know the feeling

After that brain strain it must be time for a

[purvis]

Hi Piran


from the report below, i would of thought sda was the drive with issues and i still believe it is sda


Personalities : [raid1]
md2 : active raid1 sdb2[1]                 -----> i, paul,  see sda is missing here
      156183808 blocks [2/1] [_U]
     
md1 : active raid1 sda1[0] sdb1[1]
      104320 blocks [2/2] [UU]
     
unused devices: <none>

and if i where you making a 9 hour trip, i would just  upgrade and replace both drives, and grow the drives if running raid1.
when buying the drives, look over the serial/product id/ and anything else you can when selecting drives to get the two most perfect drives.

go ahead and yank out sda drive, in a raid1 you, you can always afford to be safer than sorry, then use sdb for rebuilding

after replacing the drives, you can always use the drives you removed in another system(possibly a workstation or usb backup) after fill comfortable about the new drives, if you feel they are still good to use. Plus you get a backup if you keep the sdb drive on a shelf.

[janet]

davidpfox

.... only if this issue arises again should I be concerned and look at using SMART.
Can someone confirm this for me?

No. You should run extensive hard drive diagnostic tests on sda NOW, and while you are doing it also fully test sdb.

Being tossed out of an array could be a sign of a faulty drive.
Use smartctl and the manufacturers test software eg for Seagate drives use Seatools etc etc.
You can get a lot of test software on the Ultimate Boot CD (UBCD), google for it.

Also if one drive is showing signs of being faulty, then it's quite possible the other drive is showing signs of age too, and may fail soon, so best to check them both. If you feel it appropriate or convenient to do so, then go ahead and replace the drives. They are cheap compared to your running around time, and downtime & inconvenience for end users etc.

Another possible area that can affect drives and cause them to be spat out from an array is mother board incompatibilities. Some not so old m/b's did not support the faster SATA speeds, so it was necessary to slow the drives down by jumpering them so they were compatible with the m/b.

[davidpfox]

Mary ..... awesome reply and very valuable.

Thanks!