I just bought a brand new 1TB RE4 drive WD1003FBYX and when I tried to run diagnostic SW DLGDIAG ver 5.20 under DOS, running qeuick or extended test it didn’t started but immediatelly displayed this error message:
Error 0229: Missing Test Tracks
I also ran another SW like HDTune and it reported SMART status OK. What does this error mean? Is there available some firmware update to fix it? It seems to me it’s not a HW failure.
I hoped that people from WD know their tools they created and it’s diagnostic codes
I don’t understand the question…
I bought the drive in regular shop as end user in Czech Republic and I’m using it in my workstatioon PC.
The error code was returned from DlgDiag 5.20 that I downloaded from WD site and run it under DOS.
I got a brand new WD1003FBYX drive as a temporal replacement from local store and it also suffers with error Error 0229: Missing Test Tracks. What does this mean? The serial number is not +1 but ~ + 67000, this is quite wide range of drives…
Hard drives have a reserved System Area (SA) on the platters. The SA is also sometimes referred to as the negative cylinders. This area stores the bulk of the drive’s firmware, SMART data, defect lists (G-list and P-list), plus manufacturing test logs.
I expect that there would also be test tracks reserved for read and write testing or calibration. Part of Data LifeGuard’s diagnostic testing involves checking the read and write elements of each head. In order to test these components, I would think that the drive would need to write on a “scratch” area within the SA. Perhaps there was a manufacturing oversight that has rendered this area inaccessible???
Are there any differences on the labels of the “good” and “bad” drives, aside from the serial number?
I have the same error. I replaced the dlgdiag5.exe (5.04, see link) with the new dlgdiag5.exe (5.20) in my bootable CD, burn cd and start the diagnostic programms. When i hit R to start “Quickt Test” i get the error "Missing test tracks Error/Status code 0229 "
Yes, I tried older version 5.04f and it works for me.
My story ended today that I got the same disk returned back - RMA was refused the replacement and they claimed the disk is OK. I have to belive it. Probably it’s problem of dldiag 5.20 but it’s still confusing that it has different behavior for 2 drives of exactly same type and FW version. In your case it’s two different drives.
We have passed this information to the development team in charge of your product. Please disregard the error message that you got since this was caused by the software and not an error from the hard drive itself.