Device hard disk has a bad block? Which drive ? 4

[UnknownEntity]

Hi everyone,

Quick question. I have an event ID error code 7 in event viewer in windows XP Pro. And reads as follows;

The device, \Device\Harddisk1\D, has a bad block.

I have 6 Drives in my rig. My 2 questions are these >>

1) Does D correlate to the drive assignment ( drive) ?
2) Will zero low level format fix the problem?

Any help is greatly appreciated.

Thank you!

Drakul.

 

[ski]

Run chkdsk on the D drive:

http://www.updatexp.com/windows-xp-chkdsk.html

 

[G0AOZ]

I'd expect \Device\Harddisk1\D to relate to your second hard drive. Harddisk0 would be your first hard drive.

A bad block is a physically bad area of the disk - once you've got one (or more), they're there to stay irrespective of formatting at whatever level.

ROGER - G0AOZ.

 

[UnknownEntity]

Hi Ski,

Done the chkdsk from DOS on my D drive and had shown no bad sectors. Any other suggestions ?

Drakul.

 

[ski]

If you did the /f and /r, then see if the event viewer updated the error.

 

[UnknownEntity]

Hi Ski and GOA02,

I have done that in dos prompt and still event viewer shows the same error. No bad blocks shown on chkdsk :d /f /r test. The only thing I can think of is whether that diagnostic cannot pick up that part of the disk or skips it and assumes its okay because it maybe as GOA02 suggests physical damage.

Or i may be looking at the wrong drive !

GOA02 when you say the second drive are you referring to the next drive assignment in alphanumeric order? My local drive is C: so nataurally the next disk, according to the error message is d: drive.

Thanks guys.

 

[ski]

Another option is to run the diagnostics that are at the HD manuf's site.

 

[Freestone]

XP's chkdsk performs a file system analysis not a disk surface analysis. I'd follow ski's advice and run the manufacturer's diagnostics.

 

[Glenn9999]

And back up the drive and do a overwrite if the rest of the manufacturer's diagnostics succeed. My last drive didn't show errors until I tried to run a drive wipe program on it.

 

[UnknownEntity]

Hi guys,

After mapping Drive 'D' from my 2nd networked PC, in the attempt to backup everything from the drive. I noticed a great delay in accessing the drive from the original PC in which Drive 'D' is local to. I checked event viewer and the message it said in relation to Drive 'D' transfer delay was the following;

Event ID 11: The driver detected a controller error on
\Device\Harddisk 2\D.

Which I checked this message out on MS help site. This points to a failing cable that the drive is connected to.

Does this mean the 2nd PC is detecting the connection within in the 1st PC, that is Drive D to the Motherboard. Or is it referring to the connection between the 2 PCs. My instincts tell me its the first. If so, why does windows provide a different error message in PC 2 than the first message in PC 1 that both point to the same drive? Can a faulty cable give a message of bad blocks?

I am truly baffled. I will run the manufacturers diagnostics program as ski recommended and give feedback soon. However I dont know why I get different messages. I will try changing the SATA cable first I think and see if any further messages occur.

Thanks guys for your valuable feedback I'll keep you posted.

 

[UnknownEntity]

Cable faulty was D: local to that machine (pc2), no connection to original error whatsoever.

Diagnostics app from shown from HD manufacturers site shows bad blocks! Looks like its gonna be melted

Thanks for help guys.