the disk in D drive a is not formatted

[leeland]

Originally posted by: Smilin

One last thing:

I've given you a big-ole stack of to-do items. This is your drive and your decision. If it were my drive I would fool with it for quite some time but that's just me.

I have seen quite a few threads (as well as suggestiosn here) regarding data recovery software tools. If you want to go that route it won't hurt my feelings Quite a few people have had some great luck with those tools. I've never used them myself though simply because I've got some "built in" tools so to speak that most dont have.

I will be doing the steps you listed...for two reasons...one and primary I want to see if I can actually get the drive to respond again and I like to mess around with stuff. lets face it I am not going to break it further.

TwoA it is fun to learn....


TwoB...I have it backed up on a different drive....so not that big of a deal (UNLESS THE OTHER DRIVE PUKES...then I am driving over to your house )

When I get a moment i will sit down and start on your task list...

On a different note...I am not sure about the third drive...BUT...when I ran the WD utility, it recognized my printer of all things...maybe because it has a card reader...not sure...but it listed it in the device list...so maybe that could be the third drive you wrote about...

Otherwise I have no friggin' idea what that could be.

I will get back to you when I have something....thanks again...

 

[leeland]

Originally posted by: Doh!
Try the HDD Regenerator as previously mentioned. It's a slow process but it works surely works. Instead of booting from a floppy, make a bootable cd with the application (runs much faster).

Thanks for the link...I will keep that as a last option if I can't figure it out...

 

[Smilin]

one other thought... A bad file system filter driver could cause us some similar symptoms as well.

See if you have the same problem in Safemode. If you do, post that "*_filters.txt" file that was generated down in the \windows\mpsreports folder when you ran that mps report utility.

 

[leeland]

Originally posted by: Smilin
one other thought... A bad file system filter driver could cause us some similar symptoms as well.

See if you have the same problem in Safemode. If you do, post that "*_filters.txt" file that was generated down in the \windows\mpsreports folder when you ran that mps report utility.

will do

 

[leeland]

Originally posted by: Smilin

One last thing:

I've given you a big-ole stack of to-do items. This is your drive and your decision. If it were my drive I would fool with it for quite some time but that's just me.

I have seen quite a few threads (as well as suggestiosn here) regarding data recovery software tools. If you want to go that route it won't hurt my feelings Quite a few people have had some great luck with those tools. I've never used them myself though simply because I've got some "built in" tools so to speak that most dont have.

OK I downloaded the mounted_devices key and will post it. I enabled both the recover consules but have not booted the recover consule as of yet.

I deleted the drive and will reboot and see what the log shows and also post that information.

 

[Smilin]

k, your mounted devices key definately shows some excessive entries but this is not entirely unusual and doesn't indicate an error state.

The important part is that your drive signature (found in line 0x01b0 in the ftdump) aligns properly with the mountedevices entry for the D: drive (64 59 21 92 or 0x92215964). Same thing with your C: drive. You could safely whack everything in mounted devices except the (default) entry (and perhaps leave C: in there as well) and it would rebuild, thereby clearing out all the extra junk. I don't think it would buy us anything though. Since mounteddevices lies outside the control sets a lastknowngood wouldn't help if something went wrong so getting your windows\repair\regback folder updated with your registry first would be prudent. Again, lets not go there though.. it could be done very safely but It would be a pain and don't think it will help any.


Go ahead and get me that setupapi after you reinstall the disk but unless it says something to the effect of your hardware just crapping everywhere I think it's time to stop beating around the bush: I think your MFT is shot.

I'm gonna PM you my home and work email. Go ahead and just email the entire mps report .CAB file to me at both places. I'll shoot you back a copy of disk probe and some instructions to 'walk the disk' so we can jump out to the sector where your MFT starts and have a peek.

In the same way that boot sectors are visibly identifiable (in that ftdumpnt output you'll see the blahblahNTFS or eb 52 90 4e 54 46 53 stuff in the first line) MFTs are visibly identifiable by a "FILE0" or 46 49 4c 45 45 30 as well as some $MFT stuff. If we get out to that sector and find it full of junk or zero's we can break off troubleshooting.

 

[leeland]

I sent you the information

Thanks Smilin

 

[Smilin]

replied back.

not good