Bonz™

Hey,

First I just want to state my configuration: 6x1TB WD Blacks in RAID5 on Perc 5/i. Now onto the post.

This morning when I got to work, I logged into my file server at home only to see about 8 error messages up on my screen. They all said something about ID:0 referring to my PERC controller.

So I logged into the Dell SAS Admin panel to have a look. I saw the disk on channel 0 was being rebuilt. How do I know if it's a failed drive? Could something just have gotten corrupted and it was forced to rebuild?

In the middle of looking I got another error, then it said there was a problem during rebuild. I looked, and it was rebuilding again. So far it's at 22% rebuild and still going.

Should I go ahead and take it out and RMA it? Should I just wait it out and see what happens? Here is the log from the second time it errored out and started to rebuild.

__________________
Bonz::Asmodian Templar of Zikel

Total Available Storage
Currently: 8,377 GB (useable)

Tator Tot

It looks to me like a failed drive.
But it could be a "failing drive" aka, not 100% dead, but going there.

I would just take the drive out and start an RMA unless you really want to wait on the rebuild process.

__________________
Check Out My Sammich!Aumotocnic"An unfortunate member of the overclock.net insomnia club"
Missouri Overclockers
The ß₤ứə Çřёώ
The Red Tide ATi Owners Unite
nVidia's Gr33N Machine

Manyak

Take the drive out and stick it in another PC, out of a RAID array, and test it with HDTune.


Also, one other thing to consider - how much headroom do you have with your PSU? I only ask because capacitor aging can change a computer's power draw (and reduce a PSU's possible output) over time, so if there's not enough headroom then it might be hitting the limit and just not powering the HDD anymore.

Either way, you'll find out when you move the drive to another PC to try it.

__________________
For Sale: [Conus] CM Storm Scout, TEC, WC, Laptop, A900, Model M, GPU, Audio, and a ton more!!

Bonz™

I automatically rebuilt while I was at work. I never received any smart errors or anything. Hoping it was just a random mess up or controller glitch. Ran a consistency check and the array is at OPTIMAL status now.

__________________
Bonz::Asmodian Templar of Zikel

Total Available Storage
Currently: 8,377 GB (useable)

BLinux

it looks to me that PD 0 is having communication issues.. it goes offline, but then re-appears, so the controller starts a rebuild.. but then goes offline again, hence the "target failure" ... i would also check that the cables to PD 0 are secure, no nicks in the cables, etc.... a loose cable can result in intermittent communication problems like this.

if it was an electronic drive failure, usually you'd just see the drive go into failed state. if it was a media error (bad blocks on the platter), you would get I/O errors with corresponding timeouts as it waits for the failed I/O operation to abort. so, i don't think it's a failed drive, not yet at least.

__________________

Bonz™

Thanks. That was my thought after diagnosing the issue. I haven't had a problem since, and that was the first time. So I'm hoping it was some sort of freak occurrence.

__________________
Bonz::Asmodian Templar of Zikel

Total Available Storage
Currently: 8,377 GB (useable)