Maxtor 6v160e0 Trouble shooter.

[prawnstar3000]

Greetings!!!

I have stumbled upon a problem with a HDD being the maxtor 6v160e0(yep thats right utter crap).

Now I will outline the problem that occured, this drive was being used by a user as a backup drive containing various files and things, but the drive was installed by the user and all the drive letters were all about the place.

So I tried to sort out the paths correctly, upon changing a drive letter the drive suddenly and for no apparent reason froze the pc, then system disc would not boot because the maxtor was still attached to the system(making strange knocking noises), so the maxtor was disconnected and the system booted, I then formatted the master boot record, but still the same outcome.

I then closed down the pc and re-attached the maxtor to a different SATA port, but after the windows splash screen the maxtor started making a re-occuring knocking noise, and the system disc would not load.

So I created a bootable cd with maxblast on it to see if that would help bring the disc back to life, but upon trying to access the disc I was given an error explaining: Kernel panic - not syncing VFS: unable to mount root fs on unkown block (1,0), can someone please give me a heads up on why the disc will not read, and why something like this should happen because a partioned drive on the disc had its drive letter changed.

My guess would be that somehow the firmware has become corrupt and rendered the disc unreadable, this would explain why the disc has started knocking and why the kernel is all muffed up.

DO any of you people have a bone fide way of sorting the disc out to recover the data from it without having to pay through the nose to get it done?

 

[vacunita]

Sounds more like a coincidence to me. The Drive just coincidentally failed when you changed the drive letter. Changing drive letters is just a logical change that should have no effect on the drive itself. As that's just an organizational scheme used by operating system. at the Hardware level the hard drive is not aware of drive letters.



I would try out Seatools for DOS it works for both Seagate and Maxtor Drives, instead of Maxblast.

http://www.seagate.com/www/en-us/support/downloads/seatools/

It should let you run some diagnostics tests on the drive.





----------------------------------
Ignorance is not necessarily Bliss, case in point:
Unknown has caused an Unknown Error on Unknown and must be shutdown to prevent damage to Unknown.

 

[BadBigBen]

I agree with Vacunita, that it is just a coincidence that the drive started to muck up...

from the noise and the symptoms, I would say that the drive has gone south on you...


Ben

"If it works don't fix it! If it doesn't use a sledgehammer..."