2

This is the latest stage in a long running chain of events that has seen me cross the seven circles of HDD hell only to arrive at these depths of virtual inferno.

My Hard Drive is a 750GB Seagate Barracuda. At the point it is now, Hard drive is still recognized in BIOS and is able to be recognized in the Device Manager, where it shows as a drive with no partitions nor label, but says Unallocated.

Disk in CrystalDiskInfo Disk in Windows Disk Management Disk in AOMEI Partition Assistant

There is nothing physically wrong with the HD, no strange noises, no abnormal temperature differences during operation. What's led here has been a step by step series of losses, first of the MBR, then File Table and now possibly, the firmware is corrupted. The HDD is recognized in Disk Management, but when I try to assign a label or initialize, it returns a Device I/O Error popup:

Error message: The request could not be performed because of a I/O device error.

Last thing done in the steps of troubleshooting so far was type Clear in DiskPart, hoping the drive would be able to be re-initialized and labeled again. That's when the I/O error popup started to appear. Added to that, though visible in DM, drive is not visible in DiskPart:

List of volumes in DiskPart

I've tried to make a raw copy of the drive using an imaging tool, but it won't do that either:

HDD Raw Copy Tool: Unable to lock source device

Meanwhile, the drive is still recognized in the BIOS at startup. All this leads me to think perhaps the firmware or some important functionality software may be corrupted now.

How do I find out for certain and if true, how do I get the HDD initialized and working again after both the MBR and File Table was cleared?

What I have: By now I've gathered a vast array of drive software tools to work with, including Seagate's SeaTools. I appreciate feedback from anyone who has used these tools before and can guide me or give me tips on their use. I also have a image copy of the drive when it was new and working properly and a copy of the original functional MBR.

Note: I have hotplugged and unplugged the drive while power has been on, which may cause a firmware problem which causes an I/O error, like discussed here. I've also seen some youtube vids that talk about error codes and inputting commands directly to the HD somehow, not sure if all that is relevant in this case though, least not yet.

I'd really appreciate expert help with this, if anyone has ventured this far before, please read the history of this issue at the discussion room here and please leave me as much or little info as you can. At this point, any little clue might help!

xCare
  • 807
  • 3
  • 8
  • 18

2 Answers2

7

"Knowing the drive as I do" You don't. an I/O error is typically PRETTY bad.

Just for the heck of it, I'd suggest reseating or replacing your cable. That's about the only thing short of gradual drive failure that would do this.

Also take a look at the event logs to see if there's any errors there. As ramhound pointed out, smart isn't infallible It only tells you what the drive detects, and there's some failure modes it misses.

Bad news? I think your drive is dying. Lucky there's no data to lose. Lets make sure though.

Lets talk to the drive. Luckily, unlike data recovery, this isn't highly skilled rocket surgery.

Unfortunately (or is that fortunately?) I no longer have any semi functional faulty drives to simulate an error. I can only walk you through the process.

gsmartcontrol is my favoured way of doing smart tests. Install it, run it, and doubleclick on the drive you want to check. If this won't run at all, your drive's likely dead. This runs at a lower level than volumes and 'drives'

enter image description here

This is a happy disk... as far as we know... or is it?
enter image description here

lets go to the error log first. Happily this will show you the exact error and you can look it up.

enter image description here

But maybe I haven't checked it in a while...

enter image description here

But its in lifetime hours. Luckily, you can check in the same place where you'd find most of the useful stuff about a disk - the attributes tab

enter image description here

About a thousand hours ago? Ok... Nothing here's red highlighted or anything, so as far as we know, the disk is still happy.

Lets check again. Lets go to the "Perform Tests" Tab

enter image description here

Run the short test. If anything fails, you need a new drive. If anything dosen't, run the long test. If anything fails, you need a new drive.

Journeyman Geek
  • 133,878
0

Excellent answer of Journeyman Geek.

Since my drive is failing and I have these i/o errors, I post the S.M.A.R.T results of my WD20EARS with a whopping 91 hours of lifetime. External Backup Drive.

First lets see CrystalDiskMark results:

WD20EARS_CrystalDiskMark

and the results of a normal hdd:

Normal_Benchmark

Here the smart-data:

smart

and the error log:

error-log

and the self-test:

self-test