This is a Windows error and is in response to the ReadFile Windows API when reading the disk directly or from the volume shadow copy. Since I can't find any disk issues, not even remapped sectors/block within my disk allocation tables, or reported as such by my SSD tools, and Windows says there haven't been any disk read errors, I must assume the problem is Macrium Reflect Home 7.2. On my system, there is no such disk read error logged. ![]() If indeed it is Windows throwing the error, one would expect Windows Event Logs to record it. I have another observation regarding this phantom read error. Windows Home Premium 64-bit, homemade computer. The critical SMART attributes are good, and it passes the short SMART self-test. I believe the formerly RAW disk is physically sound. The last imaging attempt was done through an eSATA cable. That's when I got the above error message, which I also got several times during the last few days, while I was trying to solve this RAW problem, when trying to backup on my other external disk. However, Macrium said the backup failed, because it could not be verified.Īt that point, I decided to do a full format of the drive. Fulls and differentials could be mounted and browsed, hower incrementals could not. Right now, I have regained access to my external backup disk, through CHKDSK /F. Right now, my last attempt was unsuccessful.Įach time, it happens shortly after (or before) one of my external backup disks, linked by USB 3, becomes RAW and unreadable.Įach time, this is accompanied at some point by blue screens. ![]() I don't know whether it's relevant, but it might.Įach time, imaging attempts fail repeatedly. ![]() I cannot vouch the error message was the same the last time, but the rest of the context was. ![]() One is over the last days, and the other one was 2 years ago. This error message often occurs a short while after an image is launched.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |