WD Blue 1TB Corrupt?

Reloaded2

New member
I have a WD 1TB Blue HDD and I decided to reformat it. So I took off all my data and stuck it on my SSD and begun the reformat on Windows. Then out of no where my PC restarted while the drive was formatting because of Logitech's gaming software (I think it was updating or something) so I booted back.

The drive wont format, its coming up as RAW and healthy. I've tried reformatting it using disk manager and after about 5 mins it comes up with an error of D:/ being invalid and then it says the drive was unable to format. I have ran a WD Data Lifeguard diagnostic and its coming up as a pass. I need to try and reformat the drive so I can get it working again from its corrupt state.

I am going to try and boot & nuke it to see what happens but advice would be appreciated
 
Last edited:
You are going to have to use something other than disc manager. I recommend Gpart or you can use Diskpart. I've had this happen myself, and Windows DM could not sort the drive out.

Do some Googling/reading up on using Diskpart from the command line fella.

Edit, make sure you use the clean command.
 
It is possible that partition table has gone kaput. In those cases i use Ubuntu stick and run GParted. Delete partition, create new, and format as NTFS. Maybe there is a Windows alternative software, but i don't personally use them. If GParted can't deal with it... it is dead.
 
Nasty. I'll keep an eye on LGS when I'm doing things. LGS is funky at the best of times but I need it for my steering wheel. I usually kill any unwanted software or processes when doing maintenance but it's a handy reminder. Hope you get it sorted.
 
You select partition, and delete it. Right click delete, or on button in menu. When you have only unallocated space then create new partition, and make it NTFS.
 
You select partition, and delete it. Right click delete, or on button in menu. When you have only unallocated space then create new partition, and make it NTFS.

The delete bit is greyed out. Okay it's coming up now so once I delete it and make a new partition and set it as NTFS after about 1 min in it says input/output error during write on /dev/sdb
 
Last edited:
Hm... usually that is gray when drive is mounted. See if there is unmount option.

So I have to mount it in windows first.

Okay it's coming up now so once I delete it and make a new partition and set it as NTFS after about 1 min in it says input/output error during write on /dev/sdb
 
No. you need it dismounted all the time. so first dismount, then delete partition, create...etc. when it is all finished you can then mount it. do not mount it during the process.
 
No. you need it dismounted all the time. so first dismount, then delete partition, create...etc. when it is all finished you can then mount it. do not mount it during the process.

Okay I did exacally that and when I tell it to create new and it runs, about 2 minutes in it comes up with a message "input/output error during write on /dev/sdb" and says retry or abort. I click retry a bunch of times and then I just cancel it
 
A professor brought an HDD because they couldn't write or read from it after a system restart during a format. (pretty much your case) turns out that the controller has locked up the drive for some reason, there's a way to solve this if you connect the drive via serial to usb and send low level commands to it.. It was a seagate drive though... Might be something similar for WD drives too :)
 
A professor brought an HDD because they couldn't write or read from it after a system restart during a format. (pretty much your case) turns out that the controller has locked up the drive for some reason, there's a way to solve this if you connect the drive via serial to usb and send low level commands to it.. It was a seagate drive though... Might be something similar for WD drives too :)

What do you guys recommend I do since that read error thing happens? I have changed the SATA cable now, Ill reattempt the format.

EDIT: I ran cmd and I'm using a long format fs=ntfs command to format the HDD. It will take all night so Ill update in the morning
 
Last edited:
That sounds like what used to be called a low level format which will rewrite the entire surface of the drive to 0. You used to be able to do that in BIOS many years ago and I rescued quite a few hard drives doing that.
 
That sounds like what used to be called a low level format which will rewrite the entire surface of the drive to 0. You used to be able to do that in BIOS many years ago and I rescued quite a few hard drives doing that.

Yea its re writing the whole surface to 0. If I just wanted a quick one I would add quick at the end of the command but I want to make sure its fully re written. Lets hope it works
 
Little update. It worked! I left it over night and when I came back I did a quick reformat and assigned it a new letter path and this time is changed to NTFS and healthy with 0 fragments.

Not even gparted or DBAN could bring it back to life but disk parted did.

Method:


Type cmd (Admin) into start. A CMD window will open.

Type "diskpart"and press Enter.

Type list disk and press Enter.

A list of all the storage devices connected to your computer will be displayed.
Type select disk "disk number" and press Enter. (Example: select disk 1).


Type "clean" and press Enter. Do that two times

Type "create partition primary" and hit Enter.

Type "active".

Type "select partition 1".

Type format fs=ntfs and press Enter. The format process will finish in a few minutes. You can write fat32 instead of ntfs if you want to carry files larger than 4 gigabytes - usually for USB sticks etc.

This "fs=ntfs" command will take many hours so leave it over night and maybe the next day too - just until it completes. This is because its rewriting everything to 0. Also the speed is inversely proportional to drive capacity so as the drive capacity increases, the speed will decrease.

Then once it reaches 100% type "exit" in cmd and open disk manager and select the drive and format as NTFS and click "quick format" and that's it.

And do not let LGS run in the background. That is what caused all this mess
 
Last edited:
Back
Top