This is a good hard drive
Prompt when loading SA HDD has unknown capacity. SA CHS access may operates wrongly
Create a head bitmap in Data Extractor, tips Error execute=LBA->CHS conversion error (0) Device Error Detected: "VSC ERR UNSUP ACTION CODE"
WD40NMZW-59GX6S1 Cannot create head bitmap
Moderator: Maxim_TS
- huangmiaofang
- Newbie
- Posts: 23
- Joined: 18.07.15
- Reputation: 1 / (10)
Re: WD40NMZW-59GX6S1 Cannot create head bitmap
huangmiaofang, it's a new SpyGlass family and if it starts without SED error, it's partially supported in PC-3000.
With best regards
ACELab technical support
ts.acelaboratory.com
blog.acelab.eu.com
ACELab technical support
ts.acelaboratory.com
blog.acelab.eu.com
- DataMedics
- Advanced user
- Posts: 619
- Joined: 14.12.15
- Reputation: 18 / (177)
Re: WD40NMZW-59GX6S1 Cannot create head bitmap
Did you do the slow responding patch?
Re: WD40NMZW-59GX6S1 Cannot create head bitmap
For anyone that is not familiar with the WD SMR drives and their new translator type, here is a primer with some references to help bring you up to speed. I would just like to warn against rushing to apply the slow responding fix or rebuilding the translator, you might just find yourself with, what appears to be, a drive full of zeros. Consider these newish WD SMR drives to be the "Rosewood" of Western Digital. Don't just rush into the same old methods of recovery. As always, backup every module. You need to save the modules with errors too. If you have a backup and accidentally "zero" the drive it can usually be recovered. For the drives that you receive with all zeros, I do not know of a solution. I am interested to know if anyone else is working on a solution to recover these drives when they are blank upon arrival, which will probably become more common soon.
Last edited by Blizzard on 11.01.19, 02:07, edited 1 time in total.
- DataMedics
- Advanced user
- Posts: 619
- Joined: 14.12.15
- Reputation: 18 / (177)
Re: WD40NMZW-59GX6S1 Cannot create head bitmap
Blizzard wrote:Source of the post As always, backup every module.
Absolutely this. Never try anything until this is done.
Blizzard wrote:Source of the post rushing to apply the slow responding fix or rebuilding the translator, you might just find yourself with, what appears to be, a drive full of zeros.
I'd certainly be cautious about clearing the reloc list. But, it still might be beneficial to turn off auto-reallocation using the slow responding option. That may improve speed some.
Who is online
Users browsing this forum: No registered users and 15 guests
