Maxtor USB Hard Drive Not responding to W2K

  • Thread starter Thread starter Steve
  • Start date Start date
S

Steve

I have a 250 GB drive, and it shows up under disk drives in the device
list. Any time it's connected, though, Explorer gets really sluggish
and frequently hangs. I can't get into drive manager to attempt to
partition it. An attempt to format from the command prompt failed,
although it looked like it was going thru the whole format (about an
hour) and then asked for a volume label before reporting failure. The
Maxtor-supplied software mostly just hangs when attempting to access
the drive. Has anyone else seen anything similar? No obvious help on
the Maxtor website. I think I've had the drive for about a year, so
likely no hope of a warranty return. I'm completely comfortable
spelunking about in the registry, etc., but need a hint as to where to
look.

This drive also fails when connected via either USB or FireWire, to
W2K or WinXP, or even to the USB slave port of my network storage
server (Buffalo).

Steve Hendrix
 
Steve said:
I have a 250 GB drive, and it shows up under disk drives in the device
list. Any time it's connected, though, Explorer gets really sluggish
and frequently hangs. I can't get into drive manager to attempt to
partition it. An attempt to format from the command prompt failed,
although it looked like it was going thru the whole format (about an
hour) and then asked for a volume label before reporting failure. The
Maxtor-supplied software mostly just hangs when attempting to access
the drive. Has anyone else seen anything similar? No obvious help on
the Maxtor website. I think I've had the drive for about a year, so
likely no hope of a warranty return. I'm completely comfortable
spelunking about in the registry, etc., but need a hint as to where to
look.
Click to expand...
Try chkdsk /f [drive letter\:] from your C:\ drive
 
Use Maxtor utility, available on their site to check the hd
Click to expand...

The Maxtor utilities just hang, no help there. Chkdsk f: /f /r is very
sluggish, but eventually reports a bunch of messages starting with
"File record segment 4 is unreadable.". Segments 4 thru 7, 24 thru 27,
and then some 5-digit ones. Any more hints?
 
Back
Top