Failed Rip of Taking of Pelham 123

[Zatar]

Debug log started at Sun May 23 01:30:28 2010 , written by MakeMKV v1.5.5 beta linux(x86-release)
Using 515328KB for read cache.
001005:0000 MakeMKV v1.5.5 beta linux(x86-release) started
001004:0000 Debug logging enabled, log will be saved as /home/Zatar/MakeMKV_log.txt
001003:0020 DEBUG: Code 0 at g#c6?\H}|z8iV]9Rr8)M:213130122
003007:0000 Using direct disc access mode
DISCID=4F4D172E6E810BF714CE2BFF72EEF5EABF34373E
003025:0000 Title #00099.mpls has length of 98 seconds which is less than minimum title length of 120 seconds and was therefore skipped
001003:0020 DEBUG: Code 2560 at m$[nDH.u]_:0;3)LH)h<y:213132077
001003:0020 DEBUG: Code 2560 at m$[nDH.u]_:0;3)LH)h<y:213132077
001003:0020 DEBUG: Code 2560 at m$[nDH.u]_:0;3)LH)h<y:213132077
001003:0020 DEBUG: Code 2560 at m$[nDH.u]_:0;3)LH)h<y:213132077
001003:0020 DEBUG: Code 2560 at m$[nDH.u]_:0;3)LH)h<y:213132077
001003:0020 DEBUG: Code 2560 at m$[nDH.u]_:0;3)LH)h<y:213132077
001003:0020 DEBUG: Code 2560 at m$[nDH.u]_:0;3)LH)h<y:213132077
001003:0020 DEBUG: Code 2560 at m$[nDH.u]_:0;3)LH)h<y:213132077
001003:0020 DEBUG: Code 2560 at m$[nDH.u]_:0;3)LH)h<y:213132077
001003:0020 DEBUG: Code 2560 at m$[nDH.u]_:0;3)LH)h<y:213132077

The system gets sluggish, and I get tons more of these lines. I finally killed makemkv when the log file topped 500kb in size. Any ideas?

[mike admin]

Is this a regular commercial blu-ray disc?

[Zatar]

To be honest, I'm not sure. The local Movie Gallery (aka Hollywood Video) is going out of business and selling off their inventory. I purchased this movie and a number of others from their going out of business sale. Several others I purchased from them ripped without issue. I know some of the larger chains use rental specific discs, but every one I've gotten from the sale looks like a "normal" commercial disc. I know that doesn't answer the question definitively, but it's the best answer I have. :-/

That said, after posting last night, I noticed I had some patches missing, so I patched my box which included a kernel update. After rebooting, everything "just works" again today, so maybe something had gotten a little sideways in hardware or maybe they made some updates to the drivers. Either way, everything works again, so I'm sorry to have wasted your time.