The device, \Device\Harddisk2\DR2, has a bad block.

[AdamK47]

The device, \Device\Harddisk2\DR2, has a bad block.

Had this friendly message waiting for my eyes to cross it in event viewer. Noticed this on Sunday night. It happened on Friday. Didn't notice anything odd at the time and it went unnoticed. This is apparently one of five 1TB SSDs in my 5TB RAID-0 array.

The timestamp for the event is 01/16/2015 at 07:41:24 PM. This is the time the system was starting up. It's also the exact same time the Intel Management Engine Interface driver starts. Not sure if that means anything.

I looked at the SMART data on all of the drives. All of them have zero Reallocated Sector Counts (SMART 05), zero Runtime Bad Block (SMART 183), and zero Uncorrectable Error Count (SMART 187). Nothing shows as being wrong on any drive from the SMART data.

I then ran a full chkdsk on the array. It took nearly 2 hours to complete. There were no bad clusters/blocks/files/whatever. It was a totally clean scan. No errors.

I have started the PC about half a dozen times since the event. The event hasn't shown up since.

I went ahead and did a new full backup just in case.

What's the dealio, yo?

 

[siveld]

Hi Adam

I recently had a Seagate 4TB external hard drive fail. This event was preceded by recurring event log messages on the Everest program:
The device \Device\Harddisk3\D has a bad block

As this PC is a 10 year old Dell I suspected that the PC itself was on the way out.

I also had been getting a few "cyclic redundancy errors" in uTorrent, but I ran a complete scan of the relevant 4TB Seagate external hard drive using a program called TuneUp Doctor, which took 2 days, and found zero errors.

I also got pop-up messages asking if I wanted to format the G drive (the one that subsequently died) and I said no.

The drive is approx 20 months old and made no clicks etc.

I could get no info on any drive from My Computer with the G drive still connected; it showed as being there but I could not click on it to see properties etc.

When I disconnected the drive (using the safely remove harddrive function, which still worked), My Computer worked fine for the remaining drives.

Prior to the failure I got a boot-up message:
The driver has detected that device \Device\Harddisk0\DRO has predicted that it will fail. Immediately back up your data and replace your hard disk drive. A failure may be imminent."

Adam, I guess you were smart to do the full back-up, as it is likely your hard drive will die like mine did. I have approx half the data on the 4TB drive backed up on an older 2TB drive, but I really want to retrieve the rest.

I have read a bit about HD docks and duplicators but have no expertise about this stuff. What is the likelihood that the data on the 4TB drive can be retrieved, what method could I try? I don't want to pay someone hundreds of dollars, with no guarantee of success, if I can avoid it.

Any help would be appreciated.

Thanks
Dave

 

[dave_the_nerd]

Eroor could also be caused by a bad cable.

Keep an eye on it, I guess. If it's gonna fail it's gonna fail.

 

[AdamK47]

I'll keep using it and doing backups. I don't think the drive will die, but you never know. I'll buy a new one and restore from backup if it does.

I thought about the SATA cable. The cable is a few months old. It came with the Rampage V Extreme. All five of the SSDs in the array use a cable that came with the board.

 

[dave_the_nerd]

I thought about the SATA cable. The cable is a few months old. It came with the Rampage V Extreme. All five of the SSDs in the array use a cable that came with the board.

All that's irrelevant. Still could be a bad cable. Things happen.

 

[AdamK47]

yep

 

[AdamK47]

A week later and the event hasn't come back.

 

[AdamK47]

The problem happened again. This time the drive could not be detected at boot. The Intel boot manager showed the array as failed with the drive missing. Windows event viewer showed the bad block errors after boot.

I tried to disconnect and reconnect the SATA cable at the motherboard, but it didn't fix it. I then disconnected the power and SATA cable at the drive and reconnected them. This time the system detected the drive correctly. The array is intact. No bad block errors shown in event viewer.

So it could have been a loose connection at the drive. It could also be that the drive is on it's way out and that I knocked something that brought it back to life. I'll just keep monitoring it. If it dies, it dies. I'll buy a new one and rebuild the array.

 

[dave_the_nerd]

So did you replace the cable with a new one?

 

[AdamK47]

Same cable.