[Bug] Input parameter is incorrect (489)

[Dashboy1998]

Current Behavior

While trying to rip The Super Mario Bros Movie UHD I get the following error causing the auto ripper to stop

Error 'Internal error - Input parameter is incorrect (489)' occurred while reading 'BD-RE HL-DT-ST BD-RE WH14NS40 1.03 K95E9GD2926' at offset '524288'
Error 'Internal error - Input parameter is incorrect (489)' occurred while reading 'BD-RE HL-DT-ST BD-RE WH14NS40 1.03 K95E9GD2926' at offset '1048576'
Error 'Internal error - Input parameter is incorrect (489)' occurred while reading 'BD-RE HL-DT-ST BD-RE WH14NS40 1.03 K95E9GD2926' at offset '34816'

If I disable auto ripper I can manually start the rip and it works as expected.

Expected Behavior

Would like it to ignore this error and rip same as manual.

Steps To Reproduce

No response

Environment

• OS: Manaro
• OS version: Rolling, Kernel 6.6.44-1-MANJARO
• CPU: Ryzen 5 5600X
• Docker version: Docker version 27.1.1, build 63125853e3
• Device model: WH14NS40, UHD Firmware from MakeMKV Forum
• Browser/OS: Vivaldi 6.8.3381.53

Container creation

Container log

[autodiscripper-0] [makemkvcon] Error 'Internal error - Input parameter is incorrect (489)' occurred while reading 'BD-RE HL-DT-ST BD-RE  WH14NS40 1.03 K95E9GD2926' at offset '524288'
[autodiscripper-0] Killed
[autodiscripper-0] Disc rip terminated with failure.
[autodiscripper-0] Ejecting disc from drive 0 (/dev/sr0)...
[autodiscripper-0] Disc ejected.

Container inspect

No response

Anything else?

No response

[jlesage]

Are you getting the same error when manually ripping the disc?

[Dashboy1998]

Are you getting the same error when manually ripping the disc?

After looking at it some more it appears the LG drive was causing errors and preventing the ASUS from running.

My LG drive is WH14NS40 (Non-UHD). ASUS is BW-16D1HT with UHD firmware.

Even trying to RIP an HD Bluray or a DVD failed in the ASUS using autorip. LG rips with no issues. Putting them into two separate containers fixed the issue with the auto ripping although the internal error message still appears in the container with the LG.

[Dashboy1998]

Closing as this seems to be an issue related to my hardware.