i think my maxtor onetouch is fried: HELP
 

problem is I have my life worth of pictures on there as well :/
And a gazillion movies I have yet to see and music to burn.


The weird names should be regular directories with my damn files ...
http://adultjobscenter.com/maxtorfried.jpg


Anybody had this kind of drama as well?

try doing a complete scan with the windows harddrive scanner. that might help

ho shit, you got backup of all this shit ?

No, Maxtor is my backup drive. Movies and music I do not backup, just store them there as this drive is huge.

Damn, you have the whole internet on drive F?

LOL, yeah ... I downloaded it the other day :winkwink:

Strat -> Run -> Type "cmd" -> press <Enter> -> type: "chkdsk k:"

I had the same exact thing happen to mine... a 250G one..

I ended up having to reformat it.

Oh boy ...

Windows is verifying files and folders...
Windows found errors on the disk, but will not fix them
because disk checking was run without the /F (fix) parameter.
\SRChaha9658;.D0D Invalid time stamp.
\SRChaha9658;.D0D Invalid time stamp.
\SRChaha9658;.D0D Folder has non-zero file size.
\SRChaha9658;.D0D first allocation unit is not valid. The entry will be truncated.
\MIRhaha9658;.D0D Invalid time stamp.
\MIRhaha9658;.D0D Invalid time stamp.
\MIRhaha9658;.D0D Folder has non-zero file size.
\MIRhaha9658;.D0D first allocation unit is not valid. The entry will be truncated.
\TGT0.D0D Invalid time stamp.
\TGT0.D0D Invalid time stamp.
\TGT0.D0D Folder has non-zero file size.
\TGT0.D0D first allocation unit is not valid. The entry will be truncated.
\SRChaha9658;.D0D Invalid time stamp.
\SRChaha9658;.D0D Invalid time stamp.
\SRChaha9658;.D0D Folder has non-zero file size.
\SRChaha9658;.D0D first allocation unit is not valid. The entry will be truncated.
\MIRhaha9658;.D0D Invalid time stamp.
\MIRhaha9658;.D0D Invalid time stamp.
\MIRhaha9658;.D0D Folder has non-zero file size.
\MIRhaha9658;.D0D first allocation unit is not valid. The entry will be truncated.
\TGT0.D0D Invalid time stamp.
\TGT0.D0D Invalid time stamp.
\TGT0.D0D Folder has non-zero file size.
\TGT0.D0D first allocation unit is not valid. The entry will be truncated.
\TXT haha8593;Ähaha9792;haha9570;.D0D Invalid time stamp.
\TXT haha8593;Ähaha9792;haha9570;.D0D Invalid time stamp.
\TXT haha8593;Ähaha9792;haha9570;.D0D Folder has non-zero file size.
\TXT haha8593;Ähaha9792;haha9570;.D0D first allocation unit is not valid. The entry will be truncated.
\SRChaha9658;.D0D Invalid time stamp.
\SRChaha9658;.D0D Invalid time stamp.
\SRChaha9658;.D0D Folder has non-zero file size.
\SRChaha9658;.D0D first allocation unit is not valid. The entry will be truncated.
\MIRhaha9658;.D0D Invalid time stamp.
\MIRhaha9658;.D0D Invalid time stamp.
\MIRhaha9658;.D0D Folder has non-zero file size.
\MIRhaha9658;.D0D first allocation unit is not valid. The entry will be truncated.
\TGT0.D0D Invalid time stamp.
\TGT0.D0D Folder has non-zero file size.
\TGT0.D0D first allocation unit is not valid. The entry will be truncated.
Removing trailing folder entries from \
File and folder verification is complete.
Lost chain cross-linked at cluster 804863. Orphan truncated.
Lost chain cross-linked at cluster 804881. Orphan truncated.
Lost chain cross-linked at cluster 804880. Orphan truncated.
Bad links in lost chain at cluster 804896 corrected.
Bad links in lost chain at cluster 804897 corrected.
Lost chain cross-linked at cluster 804990. Orphan truncated.
Lost chain cross-linked at cluster 804991. Orphan truncated.
Convert lost chains to files (Y/N)?

Now what? Quit and run with the /F, or press Y here?

You're just saying that because of your nickname right?

Try to get a program called easy recovery pro, that program saved my ass many times... As long as the bios detects your hd it's not fried.

Now we're talking.

Rocovery - Not fried: Goooooddd

Format: Baaadddd

same here.. was 2 of them... the 250 gig maxtors.

Mine is a 200, so I hope I am safe.

In any case, what do I do with the chkdsk question?

"Convert lost chains to files (Y/N)?"

Now what? Press Y or N here?

Press yes. Two things can happen, it's all fixed or Windows fucks up the File Allocation Table a little more, but that doesn't matter since it all can be recovered with a disaster recovery programm.

Sounds like your tables are fucked up. There are programs you can get that will set everything right.

I had 2 disks I thought were toast. Ran a recovery program and everything was intact and fine.

In the worst case if its extremely important or valuable data you can take or send it to a recovery service and they'll disassemble the drive in a clean room and pull the data off the drives for you.

Usually costs about $1,000 and up.

Fuck, I wished I read your reply first. I got impatient and pressed "n", this is what followed:

Convert lost chains to files (Y/N)? n

27139008 KB of free disk space would be added.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.
199,085,024 KB total disk space.
160 KB in 5 hidden files.
64 KB in 2 folders.
32 KB in 1 files.
171,945,728 KB are available.

32,768 bytes in each allocation unit.
6,221,407 total allocation units on disk.
5,373,304 allocation units available on disk.


Now, I do not want 27 Gigs to be added, I want it there, in data. Shall I do as suggested and do the chkdsk /F k: ?

Yeah, I'm in queue for the easy recovery pro 6.0.
If it works I'll buy it.

Can you remember how much data you had available before the crash?

Yes, the numbers are correct there, so all data should be there.

Well, in that case I can't help you further, my data recovery software can only recover to a second drive. Maybe you have Norton Utilities/Systemworks?

Easy Recovery Pro should do the trick...short of a platter dump, that should get any data you have (that hasn't been trashed).

Defrag & scandisk on a regular basis kids...I know this doesn't help you now...once you have recovered...weekly...scandisk, then defrag...religiously.

I do that very often, just haven't done it to my external HDD yet, as it is very new and only used to store files. I'm sure there's nothing to defrag there :-)