Fail to open Batman vs Superman

[BobLSL]

Hi,

While trying to open this disk:

https://www.amazon.fr/gp/product/B01G5W ... UTF8&psc=1

I get:

Error 'Scsi error - ILLEGAL REQUEST:INVALID FIELD IN CDB' occurred while issuing SCSI command A40..002000800 to device 'SPTI:\Device\CdRom0'
Error 'Scsi error - ILLEGAL REQUEST:INVALID FIELD IN CDB' occurred while issuing SCSI command 28080..001 to device 'SPTI:\Device\CdRom0'
Can't read AACS VID from disc - most likely current AACS host certificate is revoked by your drive

The drive (samsung BH16NS55) works with other BRs.

I'm using MakeMKV 1.17.6.

Thanks.

[MrPenguin]

Your Amazon link is for a 4K disk, but you are posting in the "regular" BluRay section. Can you post the SHA1 hash of the problem disk's AACS/Unit_Key_RO.inf file please, just to confirm which disk it is?

Problems with 4K disks are best discussed in the "UHD discs" section.

[BobLSL]

My apologies, it's been a while since I scanned a physical disk.
How do I generate the Unit_Key_RO.inf file?
Also, I set up a custom MakeMKV/Data directory, but when I browse it, the keys_hashed.txt file dates from 2018.
Shouldn't MakeMKV update it automatically?
I did do that:

MakeMKV now updates automatically. Go to View / Preferences / General and ensure that "Enable Internet access" is checked.

I also read:

MakeMKV produces an AACS .tgz dump file whenever you try to open a disc for which the key is unknown, and will report that the dump has been created. Email the dump file to svq@makemkv.com.

But I did not get the notification.

[MrPenguin]

How do I generate the Unit_Key_RO.inf file?

You don't generate it, it's one of the files on the disk's filesystem, in its AACS/ directory. This link describes how to compute its SHA1 hash.

Also, I set up a custom MakeMKV/Data directory, but when I browse it, the keys_hashed.txt file dates from 2018.
Shouldn't MakeMKV update it automatically?

These days, the hashed keys are inside the .MakeMKV/_private_data.tar file. So as long as this file has been updated, your keys are probably OK.

MakeMKV produces an AACS .tgz dump file whenever you try to open a disc for which the key is unknown, and will report that the dump has been created. Email the dump file to svq@makemkv.com.

But I did not get the notification.

I would imagine that MakeMKV would first need to create the .tgz dump file before logging that message. Does the .tgz file exist?

[BobLSL]

Here is the SHA1 hash:

579B5A307C31AB13B14F55A001E560DFAD17044F

These days, the hashed keys are inside the .MakeMKV/_private_data.tar file. So as long as this file has been updated, your keys are probably OK

Yes, that's up to date.

I would imagine that MakeMKV would first need to create the .tgz dump file before logging that message. Does the .tgz file exist?

No recent one for the UHD that failed to open.

[MrPenguin]

Here is the SHA1 hash:

579B5A307C31AB13B14F55A001E560DFAD17044F

OK, KEYDB.cfg confirms that this disk is indeed a UHD disk (MKBv61). So the obvious question now is "Does MakeMKV say that LibreDrive is enabled?". You need LibreDrive to be enabled before MakeMKV can rip a UHD disk, or even generate a .tgz dump file for it. Perhaps just post whatever MakeMKV says about your drive, its firmware, and your disk, except without your drive's serial number?

[BobLSL]

Here is the SHA1 hash:

579B5A307C31AB13B14F55A001E560DFAD17044F

OK, KEYDB.cfg confirms that this disk is indeed a UHD disk (MKBv61). So the obvious question now is "Does MakeMKV say that LibreDrive is enabled?". You need LibreDrive to be enabled before MakeMKV can rip a UHD disk, or even generate a .tgz dump file for it. Perhaps just post whatever MakeMKV says about your drive, its firmware, and your disk, except without your drive's serial number?

I have been able to scan another UHD movie, MakeMKV saying:

Using LibreDrive mode (v06.3 id=067EFCA8EA7E)

Wiith the disk that fails, I have:

Drive Information
OS device name: Z:
Current profile: BD-ROM
Manufacturer: HL-DT-ST
Product: BD-RE BH16NS55
Revision: 1.02
Serial number: xxxxxxxx
Firmware date: 2115-12-11 14:40
Bus encryption flags: 17
Highest AACS version: 76

LibreDrive Information
Status: Enabled
Drive platform: MT1959
Firmware type: Original (unpatched)
Firmware version: 1.02
DVD all regions: Yes
BD raw data read: Yes
BD raw metadata read: Yes
Unrestricted read speed: Yes

Disc Information
Label: BATMAN_V_SUPERMAN_UE
Timestamp: 2016-06-10 21:51:23
Protection: AACS2.0/C v61
Data capacity: 91.16 Gb
Disc type: BD-ROM UHD
Number of layers: 3
Bus encryption flags: 80

The firmware looks quite advanced, it's from 2115!

[BobLSL]

I tried a straight backup that failed.
So, I cleaned the disk (which was playing fine on an Oppo player), and this time, I could start to decrypt it.
It's not finished yet, but I did not want to waste more of your time.
Thanks for your help.

[BobLSL]

Well, I got read errors this time:

Error 'Scsi error - ILLEGAL REQUEST:INVALID FIELD IN CDB' occurred while reading '/BDMV/STREAM/00000.m2ts' at offset '2987194368'
Error 'OS error - The specified request is not a valid operation for the target device' occurred while reading '\Device\CdRom0' at offset '2987194368'
Error 'OS error - The specified request is not a valid operation for the target device' occurred while reading '\Device\CdRom0' at offset '2987194368'
Error 'OS error - The specified request is not a valid operation for the target device' occurred while reading '\Device\CdRom0' at offset '2987194368'
Error 'OS error - The specified request is not a valid operation for the target device' occurred while reading '\Device\CdRom0' at offset '2987194368'
Error 'OS error - The specified request is not a valid operation for the target device' occurred while reading '\Device\CdRom0' at offset '2987194368'

The FAQ says that the drive is damaged, even though it plays on a regular player.
I'll follow the steps:

The simple workaround is to copy all files from the disc to the hard drive manually, without MakeMKV running. If you succeed in this, there is a fast and simple way to convert such copy into encrypted MakeMKV backup that can be opened by MakeMKV later. See our forum for details.

[Peppins]

I have a friend that have same issue with same movie (but different region, it) with different drive and also with makemkv and different programs too. So there is something strange with this particular movie imo.

[BobLSL]

I have a friend that have same issue with same movie (but different region, it) with different drive and also with makemkv and different programs too. So there is something strange with this particular movie imo.

Glad to know it's not me!