What tools support WD/HGST Black and Red Drives?

[br5409]

Hello,

What tools work on WD/HGST Black and Red Drives such as wd4005fzbx, wd2003fzex, wd6003fzbx, wd80efax, qd100ezaz, etc...?

[fzabkar]

The WD6003FZBX is a rebadged HGST (WWN = 5000CCA...):

https://i.ebayimg.com/images/g/tdAAAOSwYMFfKta9/s-l1600.jpg

The R/N is US7SAN6T0 which is used by several Ultrastar SATA models:

https://fccid.io/MSIP-REM-WDT-US7SAN6T0

HUS726T4TALE600, WD4003FYYZ-01TF7X0, WD4003VYYZ-02GP3X0, WD4003FYYZ-01TF7B0, WD4003FYYZ-31TF7X0, WD4003FRYZ-01F0DX0, WD4005FZBX-00K5WB0, HUS726T4TALA6L1, HUS726T6TALN6L1, WD6003FZBX-00K5WX0, HUS726T4TALE6L1, HUS726T6TALN601, WD6003FFBX-68MU3N0

WD's warranty checker URL identifies it as ...

WD6003FZBX-00K5WB0
WDVL6
7200
256M
SATA3
6GB/S
6.0 TB
8HD
STD
HGST

https://support-en.wd.com/app/warrantystatus

[br5409]

You are correct fzabkar. I believe all of the models I listed are HGST(now WD, they are labeled WD) drives. The wd100ezaz is a 10TB helium drive, I think it is SMR too.

I have 1 to 3 of each of these drives that are basically all doing the same thing. They spin up and click a few times, keep spinning and are recognized in PC BIOS but are not recognized in windows xp computer management. WD Marvel sees it, but of course can not do anything with it. I am needing to know what tools I need to attempt to work on these. Do I need a hardware/software solution (pc-3000) or will some of the software based programs work with them?

[br5409]

MHDD sees it, but when I init drive it says "recal fail."
Hdd Supertool sees it in ATA and SCSI passthrough and it will Identify it. Smart Info fails. If I try to Scan Device it, it gives all errors. I have not tried Direct mode yet, because even though I am having it boot off USB stick with no other hard drives connected but it, the program warns that the drive is available to OS and exits. Before I went through the trouble of "hiding it," I wanted to confirm if the program would work on the drive.

[maximus]

MHDD sees it, but when I init drive it says "recal fail."
Hdd Supertool sees it in ATA and SCSI passthrough and it will Identify it. Smart Info fails. If I try to Scan Device it, it gives all errors. I have not tried Direct mode yet, because even though I am having it boot off USB stick with no other hard drives connected but it, the program warns that the drive is available to OS and exits. Before I went through the trouble of "hiding it," I wanted to confirm if the program would work on the drive.

The only way to know if you can get any further in direct mode is to try. There is a slight possibility it could help, but the information given is not promising. With just the ATA passthrough mode, what are the return error and status register values? What are those values when trying to read a sector, and what are they when trying to get SMART?

[fzabkar]

SMART data are stored on the platters, so if the SMART attributes cannot be retrieved, then this points to an internal fault.

I don't believe any commercially available tool is yet able to handle this new firmware architecture.

[maximus]

SMART data are stored on the platters, so if the SMART attributes cannot be retrieved, then this points to an internal fault.

I don't believe any commercially available tool is yet able to handle this new firmware architecture.

The only reason I said there is a slight possibility of the direct mode helping is if the drive goes into device fault after the OS tries to read sectors at startup. When a drive goes into device fault (DF bit of status register set), it will respond to all commands with an abort. The fact that it was stated that it does still identify would likely (but not for sure) indicate it was not in fault, as even the identify command should fail if it was in DF. Like I said, slight possibility, but not very promising. I agree it is likely some other major issue that can't easily be resolved.

[br5409]

@maximus Not sure what you are asking so I took pictures, lol.

Attachments

[maximus]

Since you are using the 18.04 version of the live CD, the ATA registers are not returned in passthrough mode so we can't see what they are. I forgot that quit working around 16.04. The interpreted sense code returned is illegal command, which is both weird and probably not a good sign. To see the actual ATA registers would require either using the 32 bit 14.04 version of the live CD, or direct mode.

FYI Since you are using MHDD, I am guessing you have the BIOS in IDE mode. If you power on the drive AFTER you boot the live CD, it won't show to the OS and you can work with it in direct mode in HDDSuperTool.

[br5409]

I used HDDSuperTool, and applied power on the drive AFTER it booted the live CD. I selected direct mode and got similar results... If I need to try different options, please let me know and I will get you the results.

Attachments

[fzabkar]

The drive is reporting that security is locked. This implies that a password has been set.

[br5409]

@fzabkar I saw that also, but it has security_enabled=0 below that...so I did not comprehend if it was locked or not?

[fzabkar]

@fzabkar I saw that also, but it has security_enabled=0 below that...so I did not comprehend if it was locked or not?

I missed that. :-?

[maximus]

The status is an aborted command, but no device fault. Combine that with the security locked but not enabled, and you have a firmware issue, possibly caused by a bad head or heads. If it is not supported by commercial tools such as PC3000, then it would take a DR expert to deal with.

[br5409]

I did some more testing with HDDSuperTool.....

2=Red 4TB WD4003FFBX
2=Black 4TB WD4005FZBX
1=Black 6TB WD6003FZBX
1=Red 8TB WD80EFAX
1=White Label 10TB WD100EZAZ

ALL the above have the same symptoms as we have been discussing. The security_locked = 1, security_enabled =0.

NOW:

1=Black 2TB WD2003FZEX
1=Black 4TB WD4005FZBX

These worked with showing smart info, read sectors etc.....What is different? security_lock = 0! Now to figure out how to set the other 7 drives to security_lock=0. Pic attached of working 4TB.

Attachments

[maximus]

Do the working drives make the same clicks as the ones that don't work? If not, then the clicking of the other drives would indicate an internal (heads/media) issue. If the clicking is the same then it would indicate a firmware issue.

[br5409]

It is not really a click, more like a chirp... as stalker describes in this thread: https://forum.hddguru.com/viewtopic.php ... 9&start=20

[maximus]

Whatever it sounds like, do the non-working drives make any extra noises when powered on? Do they sound different from the working drives?

[pcimage]

The drive is reporting that security is locked. This implies that a password has been set.

With all these new HGST architecture drives, it the drive cannot read from SA then they report they're password locked.

If you just connect a PCB alone with HDA disconnected it will report as correct model and S/N but as password locked.

[fzabkar]

The drive is reporting that security is locked. This implies that a password has been set.

With all these new HGST architecture drives, it the drive cannot read from SA then they report they're password locked.

If you just connect a PCB alone with HDA disconnected it will report as correct model and S/N but as password locked.

Thanks, I now recall this thread:

https://forum.hddguru.com/viewtopic.php?f=1&t=40129