MakeMKV with iSCSI drive

[jollyrgrs]

I have an LG BD SATA drive (BD-RE HL-DT-ST BD-RE WH16NS60 1.02 KLBN46E1603) in a USB3 enclosure. This works fine directly connected to my Windows 11 desktop. However, I am using ARM (Automatic Ripping Machine) mostly for audio discs but sometimes to rip the accompanying DVD that came with the album. For this, I have ARM in a proxmox VM and I am using an rpi to share the USB CD-ROM via iSCSI. This works for some, but not DVDs.
Below is an example of what the log looks like where it is successful (USB directly attached to my desktop PC).

Code: Select all

MakeMKV v1.17.7 win(x64-release) started
Debug logging enabled, log will be saved as C:\Users\Jollyrgrs/MakeMKV_log.txt
DEBUG: Code 101019395 at 8)gN3IM7_1@BG-`Ird:121263429
DEBUG: Code 101019395 at 8)gN3IM7_1@BG-`Ird:121262302
Error 'Scsi error - ILLEGAL REQUEST:READ OF SCRAMBLED SECTOR WITHOUT AUTHENTICATION' occurred while reading 'BD-RE HL-DT-ST BD-RE WH16NS60 1.02 KLBN46E1603' at offset '1048576'
Using LibreDrive mode (v06.3 id=7FA2657C7667)
Using direct disc access mode
Cells 1-7 were removed from title start
Title #1 was added (2 cell(s), 0:03:03)
Title #2 was added (9 cell(s), 0:24:25)
Title #3 has length of 13 seconds which is less than minimum title length of 120 seconds and was therefore skipped
The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 110592, attempting to work around
The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 110592, attempting to work around
Operation successfully completed
Saving 2 titles into directory F:/Video/FLYLEAF
The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 110592, attempting to work around
The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 110592, attempting to work around
AV synchronization issues were found in file 'F:/Video/FLYLEAF/B9_t00.mkv' (title #1)
AV sync issue in stream 1 at 0:00:00 with duration of 32ms : 1 frame(s) dropped to reduce audio skew to +17.9ms
AV sync issue in stream 1 at 0:00:00 with duration of 49.9ms : encountered overlapping frame, audio skew is +17.9ms

over ISCSI (on the same Windows PC), it fails to get past the

Code: Select all

The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 110592, attempting to work around

line and just sits there. The disc drive's status LED is blinking but the disc is not spinning and there is no activity in the makemkv logs (Debug on).

So, my question is, I assume this is due to some missing access to the device that is not being provided via iSCSI. Is this extra access a known thing and more importantly, is there a way to provide it over iSCSI? I am sharing the entire device, not just the contents.
Here is the target configuration:

Code: Select all

jollyrgrs@rpiscsi:~ $ cat /etc/tgt/conf.d/targets.conf
<target rpiscsi.localdomain.tld:vdvd>
    backing-store /dev/sg0
    bs-type sg
    device-type pt
</target>

And on the ripping VM:

Code: Select all

jollyrgrs@arm:~$ sudo iscsiadm -m session
tcp: [1] 10.0.0.76:3260,1 rpiscsi.localdomain.tld:vdvd (non-flash)

I know this is a bit of a complicated setup but it would be great if I were able to handle this kind of disc without having to unplug the entire setup and move it over to plug directly into my desktop when needed.

[Woodstock]

The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 110592, attempting to work around
The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 110592, attempting to work around

There is an error reading the disk. MakeMKV will complain about that. Try cleaning the disk.

[jollyrgrs]

The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 110592, attempting to work around
The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 110592, attempting to work around

There is an error reading the disk. MakeMKV will complain about that. Try cleaning the disk.

Thanks for the suggestion. The disc is pristine (I'd put more smudge on it trying to clean it with a microfiber cloth). It read fine when connected directly to my PC via USB instead of iSCSI, so I believe this removes the disc's physical condition from playing a factor in this.