www.makemkv.com

MakeMKV v1.10.6 win(x64-release) started
Debug logging enabled, log will be saved as C:\Users\MakeMKV_log.txt
Backing up disc into folder "RINGS FELLOWSHIP"
Evaluation version, 30 day(s) out of 30 remaining
Loaded content hash table, will verify integrity of M2TS files.
DEBUG: Code 233 at uECtLLqrhTCkc3zjFgM0zQLr:0
DEBUG: Code 233 at cyvZ25lg04Npw6KNQMQ2mepL:0
DEBUG: Code 233 at XrySfdvodnEimyUv2aOEHoVU:0
DEBUG: Code 233 at HHXuYFo54R4iaM7STJ2pDEZM:0
DEBUG: Code 233 at VfCyWFeKn8KcH8hnE94mcAJ6:0
DEBUG: Code 233 at o0ZMsC0+ccBqTmy2rbr9x454:0
DEBUG: Code 233 at 81XJVYuFd3VStr5vDvwPbXjQ:0
DEBUG: Code 233 at +4SXnztBW8FyGpAExOMJYsDF:0
DEBUG: Code 233 at 5XRWEpMSyAW6ZG16rO4eIXZm:0
DEBUG: Code 233 at bDLkZs117LHgk47AkXHgUqFH:0
Backup done
Backing up disc into folder "_TOWERS"
Evaluation version, 30 day(s) out of 30 remaining
Loaded content hash table, will verify integrity of M2TS files.
Backup done
Backing up disc into folder "_KING"
Evaluation version, 30 day(s) out of 30 remaining
Loaded content hash table, will verify integrity of M2TS files.
Backup done
Backing up disc into folder "_FUZZ"
Evaluation version, 30 day(s) out of 30 remaining
Loaded content hash table, will verify integrity of M2TS files.

This is my log so far this session - 3 discs afterwards didnt output any of the code 223's. Does this mean my rip will have some corrupted portions or are these code 223's harmless?

If MakeMKV did not say "backup failed", the debug codes can be considered harmless, and the backup succeeded.

Best I've been able to determine is that the debug codes are output when the drive returns unexpected data, and MakeMKV needs to do some work-arounds. Mike has said that some drives do not return errors if they can "mostly" read a disk, but the data can be "out of specification". This is one reason for the hash checks being run.

Most likely cause is a fingerprint on the disk, and it took multiple retries to get the data.

Oh ok. It's just a bit odd since the disc(s) are brand new and shrink wrapped. The first and only time it was handled was by me moving it to the drive.

Another disc that I purchased new gave these:

MakeMKV v1.10.6 win(x64-release) started
Debug logging enabled, log will be saved as C:\Users\MakeMKV_log.txt
Backing up disc into folder "V:/Rips/Moonraker/MOONRAKER"
Evaluation version, 30 day(s) out of 30 remaining
DEBUG: Code 0 at 0&m?n#pRZqPGzxI8[Q:121265453
Automatic SVQ downloading is disabled or failed.
Processing BD+ code, please be patient - this may take up to few minutes
Processing BD+ code using generic SVQ from builtin/generic.svq
DEBUG: Code 6 at ^fm})tN!\InPxN>EXe:213133756
DEBUG: Code 6 at ^fm})tN!\InPxN>EXe:213133756
DEBUG: Code 0 at w!+y@la)L{'{|m8f:213130835
DEBUG: Code 0 at w!+y@la)L{'{|m8f:213130835
DEBUG: Code 6 at ^fm})tN!\InPxN>EXe:213133756
DEBUG: Code 6 at ^fm})tN!\InPxN>EXe:213133756
DEBUG: Code 0 at w!+y@la)L{'{|m8f:213130835
Saved BD+ dump file as C:\Users\.MakeMKV/dump_MOONRAKER_2610C39CDE713B40.tgz
BD+ code processed, got 1 FUT(s) for 1 clip(s)
Loaded content hash table, will verify integrity of M2TS files.
----

I'll assume they're good for now but I guess I'll have to watch these movies to make sure. Nothing spoils a good uncompressed BD rip like 5 second skips or green artifact blocks ruining a scene.