What kind of error is this?
Posted: Tue Dec 01, 2020 1:23 pm
I've recently been trying to rip (full disc) the UHD of Black Hawk Down (UK release) and finally made a copy but this is what the program log showed:
Loaded content hash table, will verify integrity of M2TS files.
File "dummy_f.dat" was skipped
Encountered 1 errors of type 'Read Error' - see http://makemkv.com/errors/read/
Backup done.
Unfortunately I wasn't running in debug log mode so don't have anything more thorough.
I'm just wondering what kind of error this is and if I've got a good rip or not. Usually the program gives more info on problem discs, usually in the form of hash check errors (with offset numbers) or full on 'Scsi error/uncorrectable error'. It usually states which playlist file the error occurred on also which is very helpful.
I've noticed with hash check errors, if there are not too many and the drive gets past the problem area the rip continues, but with the other types it usually stops and backup failed comes up.
What I'm trying to figure out is if the encountered read error but backup complete message I got above means I got a good copy with no corrupt data (but maybe at some point it had encountered a problem area but managed to re-read) or whether it's another form of failed copy and I need to re-rip.
Loaded content hash table, will verify integrity of M2TS files.
File "dummy_f.dat" was skipped
Encountered 1 errors of type 'Read Error' - see http://makemkv.com/errors/read/
Backup done.
Unfortunately I wasn't running in debug log mode so don't have anything more thorough.
I'm just wondering what kind of error this is and if I've got a good rip or not. Usually the program gives more info on problem discs, usually in the form of hash check errors (with offset numbers) or full on 'Scsi error/uncorrectable error'. It usually states which playlist file the error occurred on also which is very helpful.
I've noticed with hash check errors, if there are not too many and the drive gets past the problem area the rip continues, but with the other types it usually stops and backup failed comes up.
What I'm trying to figure out is if the encountered read error but backup complete message I got above means I got a good copy with no corrupt data (but maybe at some point it had encountered a problem area but managed to re-read) or whether it's another form of failed copy and I need to re-rip.