Bladerunner 2049

Please post here for issues related to UHD discs
Post Reply
Punished_Arbuckle
Posts: 4
Joined: Fri Aug 15, 2025 12:18 am

Bladerunner 2049

Post by Punished_Arbuckle »

Hi all,

I'm having trouble ripping the 4k UHD disc of Bladerunner 2049. I keep getting this error in the log window:

Error 'Scsi error - ILLEGAL REQUEST:INVALID FIELD IN CDB' occurred while reading '/BDMV/STREAM/00030.m2ts' at offset '38973665280'
DEBUG: Code 101000192 at A%oe?*<o<t0n{T~IVR:213131502

Relevant Info: I'm on Windows 11 and have a Verbatim 43888 drive which I flashed successfully. It has been ripping discs with MKV no problem and this Bladerunner 2049 disc is the first one to give me trouble. The disc itself has never been touched/removed from it's case, and it appears spotless under bright light. I've heard that sometimes discs can be faulty or have inherent errors in them when they come from the factory, so maybe that's an issue? I'm not sure.

I found this user who seems to be having a pretty similar issue: https://www.reddit.com/r/makemkv/commen ... k_despite/

I even have the same Verbatim 43888 drive. He states that he was able to resolve the issue by playing the disc (on his computer) in a media player, and then attempting to re-rip with MKV. That hasn't worked for me. What's interesting is that the menu screen and the disclaimers all ripped perfectly... just not the film.

I have the log file saved as well. I can post that if it's pertinent. I just chose not to because I'm not sure what's all in there and if it's safe to share etc.

Thank you for any and all help, it's much appreciated!
dcoke22
Posts: 3911
Joined: Wed Jul 22, 2020 11:25 pm

Re: Bladerunner 2049

Post by dcoke22 »

Have you ripped other 4K movies successfully?
Punished_Arbuckle
Posts: 4
Joined: Fri Aug 15, 2025 12:18 am

Re: Bladerunner 2049

Post by Punished_Arbuckle »

thanks for the reply! yep I've ripped a bunch of 4k UHD discs and also 1080p blurays as well. for some reason it's just this one disc.
dcoke22
Posts: 3911
Joined: Wed Jul 22, 2020 11:25 pm

Re: Bladerunner 2049

Post by dcoke22 »

The reason I asked is because those kind of errors are what people see if they try to rip a 4K UHD but their drive doesn't support LibreDrive. But if you've successfully ripped other 4K discs then, obviously, that's not the case.

In my experience, sometimes my optical drives get confused and need to by power cycled. With my LG based drives, it happens rather frequently. With my Pioneer based drives, it happens much less often, but it does happen. Try power cycling your whole setup, drive, computer, etc. and see if that makes a difference.

It doesn't hurt to gently clean the disc. The error you posted isn't the typical error when the drive can't correctly read a spot on the disc. And I know you said the disc is brand new, but occasionally I've taken brand new discs out of the case only the find that they won't rip until I gently clean them with warm water and dish soap to remove whatever nearly invisible deposits were affecting things.

Finally, I've found that some drives just don't like some discs. I have 4 drives on my desk. Most of the time, my 'main' drive rips everything. But occasionally, it stumbles on a disc. Most of the time, when I stick that disc in a different drive, it rips fine.
Punished_Arbuckle
Posts: 4
Joined: Fri Aug 15, 2025 12:18 am

Re: Bladerunner 2049

Post by Punished_Arbuckle »

interesting. ok thanks for the feedback. I tried taking a microfiber cloth and gently wiping the disc and that didn't help, but also I didn't do it with distilled water so maybe I'll try that. Any idea what the error means? I can always re-order the disc... but I'm not wild on doing that because that's another 20 bucks down the drain of course.
Punished_Arbuckle
Posts: 4
Joined: Fri Aug 15, 2025 12:18 am

Re: Bladerunner 2049

Post by Punished_Arbuckle »

I tried again with the distilled water and microfiber cloth, but got the same result as before (saved the title screen and copyright warnings, but not the film.) this time the activity log window repeatedly posted this over and over again (i don't think it ever stopped. eventually I just had to close the program to get it to stop.)Image
Post Reply