Home > Open Source-Free Software > RAID 1 software. When the array is in crisis ...

RAID 1 software. When the array is in crisis ...

This morning, just arrived in my office, I read the mail that my server sends the account administration and with great surprise, I learned that one of the hard drives configured in RAID 1 (mirroring) has abandoned me. The peculiarity of the error is "degradation" of all configured RAID 1 array. When an event happens like this, where they degrade arrays of an entire hard drive, it is highly likely that record will be ruined and is to be replaced. But here is what error I was notified in e-mail and as I proceeded to remedy.

On the email I received two messages containing this object:
"DegradedArray event on / dev / md1: server-studio.miodominio";
"DegradedArray event on / dev / md2: server-studio.miodominio";

Since there are only two on my server RAID array (md1 and md2), dealing respectively with the / boot partition and the /, and given that both arrays were degraded for fuoriscita by mirroring the partition residing on the second hard drive, it is highly it is likely that a terminally ill patient. Running the command "cat / proc / mdstat", in fact, were not present partitions hdc (second hard drive).

When this happens it is essential to proceed first with a nice full backup data. And 'what I did, transferring my few gigs on some DVDs and on a third hard drive. Then I attempted to repair the array in this way ...

With the command "fdisk -l" I checked out what were the partitions of the two hard drives to call into the mirror and found this:

Disk / dev / hda: 250.0 GB, 250 059 350 016 bytes
255 heads, 63 sectors / track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/ Dev / hda1 * 1 13 104 391 fd sensing raid Linux
/ Dev / hda2 14 30 401 244 091 610 fd sensing raid Linux
Disk / dev / hdc: 250.0 GB, 250 059 350 016 bytes
255 heads, 63 sectors / track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/ Dev / fd hdc1 * 1 13 104391 sensing raid Linux
/ Dev / fd 244 091 610 30 401 14 hdc2 sensing raid Linux

As you can see, paying attention to the parts shown in bold, hda1 and hdc1 must be part of the same array (identical sizes of the partitions); hda2 hdc2 and must be part of the same array.

I continued, then, using the mdadm command like this:

-add # Mdadm / dev / md1 / dev / hdc1

Then I ran the command:

-add # Mdadm / dev / md2 / dev / hdc2

RAID is currently under reconstruction:

# Cat / proc / mdstat
Personalities: [raid1]
md2: active raid1 hdc2 [2] hda2 [0]
244091520 blocks [2/1] [U_]
[=====> ...............] Recovery = 29.2% (71281408/244091520) finish = 97.6min speed = 29493K / sec
md1: active raid1 hdc1 [1] hda1 [0]
104320 blocks [2/2] [UU]

You may notice that the raid array md1 has been rebuilt, while the array md2 is under reconstruction.
The next step will be to see if the secondary hard drive (HDC) is suffering from some hardware problem. To do this I will use the software smartctl :)

  1. December 26, 2008 at 12:05 | # 1

    RAID 1 software. When the array is in crisis ......

    This morning, just arrived in my office, I read the mail that my server sends the account administration and with great surprise, I learned that one of the hard drives configured in RAID 1 (mirroring) has abandoned me. The special d ...

  1. May 30, 2008 at 15:41 | # 1
  2. May 30, 2008 at 15:41 | # 2
  3. May 30, 2008 at 15:47 | # 3
  4. December 26, 2008 at 12:03 | # 4