OVH Community, your new community space.

MD Fail Event...

11-06-2009, 08:13
Quote Originally Posted by Myatu
SMART shows 8 bad sectors, 8 pending:
I'd boot 'sdb1' out of the mirror and do:

# dd if=/dev/zero bs=1M of=/dev/sdb1
This will re-write the whole of 'sdb1' with zeros and will allow theses bad sectors to be re-allocated by the disk. If you get the same problems again in the future then I'd suspect the disk, but assuming this is the first time you've seen this problem, I'd leave it for now.

Could you post the temperature of your drives please? We're having a discussion with OVH about appropriate temperatures for our drives and would like to know what other people see in their dedicated servers.

$ sudo hddtemp /dev/sd?
/dev/sda: ST3750330AS: 51C
/dev/sdb: ST3750330AS: 47C

07-06-2009, 17:17
I've got this from mdadm:

This is an automatically generated mail message from mdadm
running on ashanti

A Fail event had been detected on md device /dev/md1.

It could be related to component device /dev/sdb1.

Faithfully yours, etc.

P.S. The /proc/mdstat file currently contains the following:

Personalities : [raid1] [raid0] [raid6] [raid5] [raid4] [linear] [multipath] [raid10] 
md1 : active raid1 sda1[0] sdb1[2](F)
      20482752 blocks [2/1] [U_]
      [=======>.............]  check = 38.4% (7884480/20482752) finish=20.9min speed=10033K/sec
md2 : active raid1 sda2[0] sdb2[1]
      711044864 blocks [2/2] [UU]
unused devices: 
SMART shows 8 bad sectors, 8 pending:

# smartctl  -A /dev/sdb
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       8
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       8
Time to put in a ticket, you think?