WD My Passport not accessible

[DerpyTurtle]

Hey everyone, so tonight I am working on a family computer to upgrade to Windows 7 and I decided to run Boot Nuke, I didnt realize that my external that contains all of the info and backups was still plugged in when I started the process, I noticed it quickly and removed it before Boot Nuke was at 0.01% but now when I am using my personal computer to try to access the drive it always times out when its trying to read the drive, the indicator light and everything on the drive works fine and is telling me the drive is okay, I can feel it spinning so its still alive. When I try to connect it to my computer I get a message that says...

Code: [Select]

E:\ is not accessible. The parameter is incorrect.
Have any of you seen this before? Could Boot Nuke really have wiped that drive that quickly or damaged it enough to not be accessible?
I am researching it online as I am posting this, but if anyone has any advice on what I can do I would appreciate it! Thanks guys!

[techb]

Hey everyone, so tonight I am working on a family computer to upgrade to Windows 7 and I decided to run Boot Nuke, I didnt realize that my external that contains all of the info and backups was still plugged in when I started the process, I noticed it quickly and removed it before Boot Nuke was at 0.01% but now when I am using my personal computer to try to access the drive it always times out when its trying to read the drive, the indicator light and everything on the drive works fine and is telling me the drive is okay, I can feel it spinning so its still alive. When I try to connect it to my computer I get a message that says...

Code: [Select]

E:\ is not accessible. The parameter is incorrect.
Have any of you seen this before? Could Boot Nuke really have wiped that drive that quickly or damaged it enough to not be accessible?
I am researching it online as I am posting this, but if anyone has any advice on what I can do I would appreciate it! Thanks guys!

I haven't come across this before cause I have never used Boot Nuke. But here is what I will give advice on:

1) You may be fucked, cause after googling Boot Nuke, I doubt it even cares to can files before ridding them. If it where to see what it was about to nuke and put it into some database or something then act (referring to the 1% if it did that kinda of thing). But it looks like this program was meant for NUKING shit.... Sorry bro, it might be the only "scan" it might have done was look for drives to fry. Externals being first option cause of reasons. In this "new" user kind of since, you could attempt a disk recovery with a bootable CD or something, but I really doubt it would work.

2) Next option is trying something like BinWalk to see if a file structure is even in tact, or other means of checking if indexing and other shit is still there. Rebuilding can be an option from there, or at least grabbing data you need. Since you stopped  it so early [lol], the data you want/need should/might be there. Just google around and if said programs and such don't fix it, google more. Data isn't gone till it's gone off a drive.

ALSO, fuckin loose Windows.... Use Linux, your going to need it if your ever to see your data again bro.

[DerpyTurtle]

I did some research last night as I said in my post and decided the first option would be to utilize the tools I already have available so I ran

Code: [Select]

chkdsk /F /R /X

I started it last night around 8:00 and it is just now getting close to finishing. So far the output has been positive, I havent seen any errors or failed attempts. Which is nice the output I am getting is saying

Code: [Select]

Bad links in lost chain at cluster ******** corrected

It is being very thorough which is nice and not so nice, it is taking forever and this was just supposed to be a simple upgrade than seems to have been hit by a train... I know after running chkdsk there is still a chance of data loss but I am hoping for most or at least a good majority of my files to be intact. Thanks for your help man! All I can do is hope for the best.

ALSO, fuckin loose Windows.... Use Linux, your going to need it if your ever to see your data again bro.

I personally use Linux but this is a family members computer I am working on. They wouldnt have the slightest clue what to do with Linux, even Ubuntu... I am just giving them what theyre used to so they dont freak out about too much change.

[vezzy]

Try running a file carver like Foremost or Scalpel to salvage any missing data from disk sectors that haven't been overwritten, in case chkdsk didn't solve the issue.

[DerpyTurtle]

Does anyone know of a DOS tool I can use to see the number of tracks,sectors, and cluster, etc? Because this has been running for way too long it seems, damn near 24 hours. Any help would be mych appreciated!

[techb]

Does anyone know of a DOS tool I can use to see the number of tracks,sectors, and cluster, etc? Because this has been running for way too long it seems, damn near 24 hours. Any help would be mych appreciated!

Code: (bash) [Select]

man fdisk
And yes, you can use fdisk with windows. IDK if it comes by default or not, but you can use it. If you can't figure out how to use it on windows, use a live *nix cd.

[proxx]

Hey everyone, so tonight I am working on a family computer to upgrade to Windows 7 and I decided to run Boot Nuke, I didnt realize that my external that contains all of the info and backups was still plugged in when I started the process, I noticed it quickly and removed it before Boot Nuke was at 0.01% but now when I am using my personal computer to try to access the drive it always times out when its trying to read the drive, the indicator light and everything on the drive works fine and is telling me the drive is okay, I can feel it spinning so its still alive. When I try to connect it to my computer I get a message that says...

Code: [Select]

E:\ is not accessible. The parameter is incorrect.
Have any of you seen this before? Could Boot Nuke really have wiped that drive that quickly or damaged it enough to not be accessible?
I am researching it online as I am posting this, but if anyone has any advice on what I can do I would appreciate it! Thanks guys!

Boot a rescue kit, dd the drive, Never Work On The Original Data.
Try mounting it, if not try to recover sectors/magic blocks.
Come back when that does not work.
There are some tools out there that can still extract lots of data.

[Darkshadow2913]

My first suggestion is to try rebuilding the mbr as usually in data destruction that is the first thing to be destroyed due to its location on the drive.

[iTpHo3NiX]

My first suggestion is to try rebuilding the mbr as usually in data destruction that is the first thing to be destroyed due to its location on the drive.

Yeah because you know, his external drive stores his master boot record 

[DerpyTurtle]

Thank you guys for all the helpful input! Now all I'm wondering is...
Has anyone had a chkdsk last for more than 24 hours?

[iTpHo3NiX]

Thank you guys for all the helpful input! Now all I'm wondering is...
Has anyone had a chkdsk last for more than 24 hours?

What switches did you use and how big is the hard drive. This will determine how long a chkdsk will take

[DerpyTurtle]

I used chkdsk /F /X /R and shouldve used /C also but I had to abandon ship with that process even though it was seemingly nearly done. Because my laptop is being troublesome and will not recognize the AC adapter being plugged in, I have an idea of when the problem may have occurred but for now I have live booted a linux system and am not liking my results, the chkdsk seemed to work great but now I ran a few commands on linux and it is the exact opposite

Code: [Select]

root@ubuntu:/home/ubuntu# fsck /dev/sdb1
fsck from util-linux 2.20.1
dosfsck 3.0.12, 29 Oct 2011, FAT32, LFN
There are differences between boot sector and its backup.
Differences: (offset:original/backup)
  65:01/00
1) Copy original to backup
2) Copy backup to original
3) No action
? 3
Both FATs appear to be corrupt. Giving up.
root@ubuntu:/home/ubuntu#


The GUI recognizes the drive but when I try to mount it, I get an error saying

Code: [Select]

Unable to mount HDD 3.0
Error mounting: mount: /dev/sdb1: can't read superblock

Any suggestions on where to go from here?

[iTpHo3NiX]

In winblowz can you go to the disk management and reformat it?

[proxx]

I used chkdsk /F /X /R and shouldve used /C also but I had to abandon ship with that process even though it was seemingly nearly done. Because my laptop is being troublesome and will not recognize the AC adapter being plugged in, I have an idea of when the problem may have occurred but for now I have live booted a linux system and am not liking my results, the chkdsk seemed to work great but now I ran a few commands on linux and it is the exact opposite

Code: [Select]

root@ubuntu:/home/ubuntu# fsck /dev/sdb1
fsck from util-linux 2.20.1
dosfsck 3.0.12, 29 Oct 2011, FAT32, LFN
There are differences between boot sector and its backup.
Differences: (offset:original/backup)
  65:01/00
1) Copy original to backup
2) Copy backup to original
3) No action
? 3
Both FATs appear to be corrupt. Giving up.
root@ubuntu:/home/ubuntu#


The GUI recognizes the drive but when I try to mount it, I get an error saying

Code: [Select]

Unable to mount HDD 3.0
Error mounting: mount: /dev/sdb1: can't read superblock

Any suggestions on where to go from here?

If you are going to ignore the suggestions then dont even bother to ask.
Never ever do that on the real data!!
Make a full byte copy of the entire drive first!

You can only mess it up twice.