FSCK! bad drive

[skyking]

got this lovely email from my home server today:

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

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

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

Faithfully yours, etc.

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

Personalities : [raid1]
md2 : active raid1 sda3[0] sdb3[1]
gazillions of blocks [2/2] [UU]

md1 : active raid1 sda2[2](F) sdb2[1]
billions of blocks [2/1] [_U]

md0 : active raid1 sda1[0] sdb1[1]
not so many blocks [2/2] [UU]

I guess I'll take it down and send it off for warranty. Anybody have a spare 1TB WD green drive? 😛

 

[Paperlantern]

got this lovely email from my home server today:



I guess I'll take it down and send it off for warranty. Anybody have a spare 1TB WD green drive? 😛

Haha actually yes. Though its for my RAID 5 array of three drives I have here.

 

[skyking]

you better keep that. This the only array I have around here without a spare. Go figure.

 

[skyking]

When it rains, it pours. I got another Dear John email. This one is about 160 miles away.

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

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

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

Faithfully yours, etc.

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

Personalities : [raid1]
md2 : active raid1 sda3[2](F) sdb3[1]
485347648 blocks [2/1] [_U]

md1 : active raid1 sda2[0] sdb2[1]
1951808 blocks [2/2] [UU]

md0 : active raid1 sda1[0] sdb1[1]
240832 blocks [2/2] [UU]

unused devices: <none>

The box shut down Thursday morning, I can't find anything in the logs so it may have been a heat-induced or hardware induced shutdown. We started it back up and the remote person was going to take it out and blow out the dust Friday. That never happened 🙁
The temps and drive temps were OK. This morning I get this email, it took a couple of days to show up.

EDIT: I removed the failed partition and re-added it. So far no issues, it may have been a simple timeout. Smart had several errors writing to the same sector, but still marked the drive as OK.