I see this on occasion:
Error 'OS error - The end-of-file marker has been reached.
But the backup completes. Does that error have any impact on the backup?
Thanks in advance
Benign error? Error 'OS error - The end-of-file marker has been reached.
Re: Benign error? Error 'OS error - The end-of-file marker has been reached.
I have encountered this error several times. After looking into the documentation and in the forums for information about it, I found that the message means that the software, sort of, reached -- you know -- the end of the, like, file... and... ummm... so, it's kind-of, uhh...
In other words, one of those vague, hand-wavey errors that MakeMKV displays without proper explanation of what it means to users.
Another such "error" is the dialogue box at the end of a copy process that indicates "Read Error" with some number of errors. This does >>NOT<< mean that files in the copy are either missing or corrupt (as implied by a "Read Error" dialogue box). I think it just means that the software encountered flakey parts of the optical disc which >>initially<< produced read errors, then were retried, and possibly eventually produced good data. The important thing to check is whether MakeMKV reports hash errors and files not saved. If files were not saved, then you have a problem of missing material. If all files were saved, with some percentage corrupt, then you have imperfect copies of some material. If there is not mention of hash errors, then you probably have a good copy, regardless of ambiguous, poorly-communicated "errors".
Each time I have encountered a "Read Error" dialogue box or an "Error 'OS error - The end-of-file marker has been reached. There is no valid data in the file beyond this marker' occurred while reading..." error, absent actual hash errors, the resulting copy has been fine, without no exception.
The log pane of the MakeMKV window for a successful copy operation should have these lines without mention of hash errors, and a dialogue box displayed about the backup being done but no mention of files not being saved:
Loaded content hash table, will verify integrity of M2TS files.
.....
Backup done
In other words, one of those vague, hand-wavey errors that MakeMKV displays without proper explanation of what it means to users.
Another such "error" is the dialogue box at the end of a copy process that indicates "Read Error" with some number of errors. This does >>NOT<< mean that files in the copy are either missing or corrupt (as implied by a "Read Error" dialogue box). I think it just means that the software encountered flakey parts of the optical disc which >>initially<< produced read errors, then were retried, and possibly eventually produced good data. The important thing to check is whether MakeMKV reports hash errors and files not saved. If files were not saved, then you have a problem of missing material. If all files were saved, with some percentage corrupt, then you have imperfect copies of some material. If there is not mention of hash errors, then you probably have a good copy, regardless of ambiguous, poorly-communicated "errors".
Each time I have encountered a "Read Error" dialogue box or an "Error 'OS error - The end-of-file marker has been reached. There is no valid data in the file beyond this marker' occurred while reading..." error, absent actual hash errors, the resulting copy has been fine, without no exception.
The log pane of the MakeMKV window for a successful copy operation should have these lines without mention of hash errors, and a dialogue box displayed about the backup being done but no mention of files not being saved:
Loaded content hash table, will verify integrity of M2TS files.
.....
Backup done