DWreck1995
-
Posts
4 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by DWreck1995
-
-
10 hours ago, LIGHTNING UK! said:
It switches back to reading a block at a time pretty quickly, so any slowness is just where your drive is really struggling to read the disc.
You should probably save images of them or burn to another disc ASAP, in case they’re eventually totally unreadable.
Hard to know where the fault lies without trying to read those same discs in another drive.
I don’t recall having seen that other error you mentioned before. That in itself probably isn’t a good sign!
4 hours ago, dbminter said:Yes, that error message came as a surprise to me, too.
Since you haven't seen that second error before, I managed to get a log that has it. I've attached it here if you're interested. I'm also getting another drive to confirm if it's the discs or the drive once and for all.
PS: The log shows I'm running Win 8, I'm not. I'm running Win 10.
-
2 minutes ago, LIGHTNING UK! said:
That means the drive initially failed to read the block of sectors, but then managed to read them all when the program switched to reading them one at a time.
Thanks for explaining. Other than it taking significantly longer to finish, there's nothing wrong with letting it continue like that is there?
Also, is this type or error suggestive of a drive failing if it happens often? I also get "Retry Failed - Reason: Logical Unit has not Self-Configured Yet" sometimes.
-
Hi,
I'm curious about when I get read errors showing up in the log window but not in the program window? ImgBurn seems to continue reading the disc (albeit very slowly) when this happens. Does this mean it was able to successfully read the sectors and move on at some point?
I'm sorry I don't have a log file since it's a random occurrence. But I did manage to get a screenshot once, so I've attached it since it shows what I'm talking about.
Read Errors in log, but not in program window?
in ImgBurn Support
Posted
For some reason it still appears even after AnyDVD has been "disabled". It only goes away if you exit the app. But yeah, I did try that.
Glad to hear that'll get fixed in the upcoming release. I'll make note of it in my "when Hell freezes over" list lol.