ADFS bug?
Chris Hall (132) 3567 posts |
A momentary ‘drive not ready’ error (08) during a disc access (which should resolve itself as the OS repeats the drive access before reporting an error) is also not resolved by a ‘retry’ selection by the user and then persists for every subsequent disc access to any ADFS drive until the user does a ‘*RMReInit ADFS’ command after which it all works (perhaps for several hours) until another momentary DNR occurs. Note that ‘*RmReInit SATADriver’ is guaranteed to produce a DNR error on the next ADFS access of any drive (which then persists until RMReInit ADFS). However if you follow it immediately with a RmReInit ADFS, then all is well. Note also that a reset (which is just a bit more drastic than RMReInit ADFS) also clears the persistent error. The ADFS module is ADFS 4.00 (28-Aug-2015). The consequence of the error is sometimes presented as ‘broken directory’ or ‘bad map’ and sometimes a disc access appears to succeed due to cacheing but no disc corruption actually occurs. |
Chris Hall (132) 3567 posts |
I am coming to the conclusion that the original ‘08’ error may be power supply related (power budget on 3.3V supply is 9.835A and my power supply is rated at 10A) but this does not really explain why the error persists until a RMReInit ADFS. I’ll do some testing with a DVM. Edit: DVM shows solid 3.30 volts, so it’s not that. |