www.makemkv.com

Those errors would likely be a corruption on the disk, where the drive spent a LOT of time trying to read it. It then timed out. Possibility one is a disk defect, and possibly cleaning the disk will "fix" it. Possibility two is the drive started spinning faster than it had power for, and w...

Some information would be helpful... like what does the log say?

clarification - "LibreDrive" does NOT mean "can read UHD disks". A drive built before UHD was available (like this one) is not likely to support it just by having its firmware unlocked.

Ripping, I get all of them. Post-rip processing, I cut out a lot, based on my usage. Sometimes, I find that the 5.1 track is NOT the audio from the feature... that's only stereo.

"bombs near completion" indicates that the rip starts, but fails due to a read error. Is that what you're experiencing?

The fact that the rip started means MakeMKV was able to decode the encryption, but the read failed after a bit. It is likely you need to clean the disk.

I can think of one disk set that would screwed this over... ".hack" anime.

Send your information to support@makemkv.com to have Mike make the correction and get you the key information. Only he can make such a correction.

Internal drives usually do not have power issues (one hopes!), so the offset should not move about. Smudge is more likely, so cleaning the disk should help. Remember to use a non-scratching cloth, and wipe radially (not around, but across) to minimize scratches.

Do you have gobs of unused space that needs filling? Then doing ISOs is a good way to fill it. Not so much? Then preserving the original media is probably a better choice. I only have about 80TB of storage, so I don't store the ripped MKV files longer than it takes to encode them to storage, then pa...

Reading from the log, I see: 002003:0000 Error 'Scsi error - ILLEGAL REQUEST:ILLEGAL MODE FOR THIS TRACK' occurred while reading '/BDMV/STREAM/00705.m2ts' at offset '14157938688' 002003:0000 Error 'OS error - The specified request is not a valid operation for the target device' occurred while readin...

Generally speaking, MakeMKV gives error messages when it cannot rip a disk. It also generally creates files to use for resolving the issue. Are we allowed to know this, or are we to simply guess at why yours failed?

I don't know why the weird firmware date on mine. I wondered if my drive had been flashed by the vendor,

A lot of drives (mainly LG/Asus) have the firmware date a century ahead. They say "2117" but mean "2017".

There's an entire topic on it with links and such.

You can re-enter the current key, which will work through the end of the month, if you wish to rip now. Not everything has to wait...