The volume key is unknown for this disc - video can't be decrypted

[xesegik]

MakeMKV can't read the Mandalorian disk 1 and quits with this error:

The volume key is unknown for this disc - video can't be decrypted

I already updated my keydb

Code: Select all

~/.config/aacs/keydb.cfg

... and for good measure ...

Code: Select all

~/.config/aasc/KEYDB.cfg

Doesn't work though. I'm not even sure, MakeMKV actually uses those files.

What can I do to solve this?

[Sayaka]

If it's the 4K version, you need a UHD-compatible drive and LibreDrive : viewtopic.php?t=18856 and viewtopic.php?t=19634

With UHD discs (EDIT : and even some unsupported regular Blu-ray discs when you don't have LibreDrive, as tomty89 pointed out below), when the disc is not yet supported you may also need to send a dump file to svq@makemkv.com and/or post in the following thread, following the instructions : viewtopic.php?t=38293

If you have a Windows machine/virtual machine, this tool can also help with UHDs : viewtopic.php?p=166510#p166510

If it's a regular Blu-ray, having LibreDrive is still recommended, although usually not necessary. First, "keydb.cfg" should be renamed to "KEYDB.cfg", as Linux is case-sensitive. Secondly, it should also be placed inside ~/.MakeMKV/

If it's a regular Blu-ray and it's still not working after placing KEYDB.cfg inside ~/.MakeMKV/, unless you have a Windows machine that you can use FindVUK (https://forum.doom9.org/showthread.php?t=172472) and DVDFab with, your best bet is LibreDrive.

You may also wish to post your MakeMKV drive information so we can provide further assistance. It should look like this, roughly :

Drive Information
OS device name: /dev/sr0
Manufacturer: HL-DT-ST
Product: BD-RE BU40N
Revision: 1.00
Serial number: [redacted]
Firmware date: 2116-12-20 15:28
Bus encryption flags: 17
Highest AACS version: 82

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

No disc inserted

If you can copy & paste the information while the Mandalorian disc is inserted, that would be even better.

[tomty89]

See viewtopic.php?t=38293. Make sure that your read the first post and follow the template btw.

But before you do, maybe you should run bd_info on the disc and report back (to this thread) with the output first. I can see a few "Mandalorian disk 1" entries (for season 1 to 3) in the current KeyDB. (EDIT: I'm assuming you also have libaacs installed.)

I'm not even sure, MakeMKV actually uses those files.

I think you need to copy it into ~/.MakeMKV, but I don't remember for sure and can't test at the moment. (Should probably be named as KEYDB.cfg.)

[xesegik]

Well, my drive might not support it. It's indeed 4k

Code: Select all

Drive Information
OS device name: /dev/sr0
Current profile: BD-ROM
Manufacturer: HL-DT-ST
Product: BD-RE WH16NS60
Revision: 1.02
Serial number: [...]
Firmware date: 2118-10-29 19:36
Bus encryption flags: 17
Highest AACS version: 82

LibreDrive Information
Status: Enabled
Drive platform: MT1959
Firmware type: Patched (microcode access re-enabled)
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: THE_MANDALORIAN_S1_D1
Timestamp: 2023-11-17 14:14:05
Protection: AACS2.0/C v77
Data capacity: 82.21 Gb
Disc type: BD-ROM UHD
Number of layers: 3
Bus encryption flags: 80

[Sayaka]

So you do have a UHD capable drive as well as the correct firmware. It's definitely worth doing this :

Download the latest version of KEYDB.cfg (https://fvonline-db.bplaced.net/), then :

First, "keydb.cfg" should be renamed to "KEYDB.cfg", as Linux is case-sensitive. Secondly, it should also be placed inside ~/.MakeMKV/

Try opening the disc with MakeMKV again after doing that. If it still doesn't work, please open the ~/.MakeMKV/ folder and e-mail the tgz dump file to svq@makemkv.com

See also :

Once submitted, the turnaround can be pretty fast, between 12 to 48 hours. However, it can also sometimes take several days or longer.
When you submit a dump, ensure that:
- You are using the latest version of MakeMKV.
- You are using a LibreDrive-enabled drive (be it "friendly" or "official", but it must be LibreDrive enabled).
- You have "Enable Internet access" enabled in Preferences (in the General tab), so that MakeMKV will check for updated keys when you try to open the disc again.
- You are opening the original disc (not a backup, not ISO).
- You are opening the disc using a real disc drive natively (no elby clonedrive, no vmware, no dvdfab or discsoft virtual, etc).

Also, you may wish to follow the instructions in the following thread so that you can get the needed Volume Unique Key faster : viewtopic.php?t=38293

EDIT :

Well, my drive might not support it.

To clarify, your drive does support it. It's MakeMKV that's currently missing the correct VUK, so you have to help people gain access to it if you want the disc to be supported. We literally cannot do this for you unless we also happen to have the same disc with the same VUK.

[tomty89]

It's MakeMKV that's currently missing the correct VUK

Could also be just HK downlaoding failed due to geoblocking. (Should have been hinted in the log if that's the case.)

[Sayaka]

Very true, thank you for mentioning that.

(I just thought that wouldn't be the case, since xesegik probably would have told us about it given that they posted an error message in the first post of this thread. But it certainly doesn't hurt to mention this, especially since other people might stumble upon this topic.)

[xesegik]

@Sayaka

Thank you for those detailed instructions. I followed them and checked everything. Unfortunately unsuccessful, so far. I ended up sending that email.

@tomty89

That's an interesting point. If it is geoblocking, I'm not aware of it. The logs don't indicate anything like that.

Logs (from today)

Code: Select all

MakeMKV v1.18.4 linux(x64-release) started
Using LibreDrive mode (v06.3 id=7FA2657C7667)
Using direct disc access mode
Loaded content hash table, will verify integrity of M2TS files.
Saved AACS dump file as
/home/[...]/.MakeMKV/MKB20_v77_THE_MANDALORIAN_SEASON_1_DISC_1_9993.tgz
The volume key is unknown for this disc - video can't be decrypted
Failed to open disc

[Sayaka]

I ended up sending that email.

Good idea. You can also follow the instructions in the first post of the following thread and then post inside said thread, as I said : viewtopic.php?t=38293

This may help you get your disc decrypted a *lot* faster.

Hi everyone, I've created this thread to act as a central location for posting disc dump file submissions for the public keydb. Thank you to the moderation team for allowing this thread to be trialed.

Please include the disc ID in your submission template. The disc ID is the SHA-1 hash of the Unit_Key_RO.inf file in your discs AACS folder. Many tools can calculate this hash, please google the instructions for your specific platform.

Submission template:

Code: Select all

Disc type:
Disc ID:
Disc dump filename:
Drive:
Drive firmware:
LibreDrive status:
Did you sync the public keydb within the last 15 minutes?
Have you verified that all submission links are accessible in incognito/private browsing?
MKB_RO.inf link (Do not just extract the MKB_RO.inf file from the disc dump file - copy it from the disc):
Disc dump link:

Submission example:
Disc type: UHD
Disc ID: 0x3107C2E7A9E653308559C7ED8E261D9702F4C5F4
Disc dump filename: MKB20_v77_The_Sound_of_Music_BCE8
Drive: BW-16D1HT
Drive firmware: 3.10MK
LibreDrive status: Enabled
Did you sync the public keydb within the last 15 minutes? Yes
Have you verified that all submission links are accessible in incognito/private browsing? Yes
MKB_RO.inf link: <Link>
Disc dump link: <Link>

I hope this will lead to less issues caused by large file attachments and reduce confusion regarding the state of native title support in MakeMKV.

Please stop posting links which are either broken, unavailable or not publicly accessible. Before posting a link in this thread open up incognito mode and verify that your disc dump file can actually be downloaded.

What is the public keydb?
The public keydb (key database) is a community run initiative which provides a database of keys for decrypting Blu-ray discs. The public keydb is independent of MakeMKV but if configured properly MakeMKV can utilise the public keydb to decrypt discs which it does not yet natively support.

Emailing disc dump files to the MakeMKV team is still recommended to assist with native title support.

What is the benefit of providing disc dump files?
If you can provide a suitable disc dump file in this thread, it will be supported by the public keydb within 12 hours. Otherwise you may need to wait days or even weeks for MakeMKV to natively support your disc.

Link to instructions for configuring MakeMKV to utilise the public keydb

Link to the public keydb homepage

Link to SamuriHL's KeyDBTool for Windows

How can UHD discs be added to the public keydb?
Upload your disc dump file produced by one of the aforementioned drives to any file host and post the link in this thread.
Please do not directly attach disc dump files as this causes storage quota issues and a maintenance hassle for the forum administrators.

Partial disc dumps
UHD disc dump files are generally 3-8MB. If your disc dump is less than 1MB, you will need to manually include the MKB_RO.inf file when uploading your disc dump file. You can find this file within the AACS folder on your disc. The MKB_RO.inf file may be ~128MB so feel free to zip it before uploading it.

Do not just extract the ~56 byte MKB_RO.inf file from a partial disc dump file and upload it separately. This is not helpful. Instead, copy the MKB_RO.inf file from the AACS folder on your disc and upload it separately. If your MKB_RO.inf file is not several megabytes in size, it is probably not useful for UHD discs.

Please ensure that all file links are publicly accessible before posting in this thread.

Don't forget to try out the latest public keydb before posting to this thread. Remember, even if MakeMKV doesn't natively support your disc it may already be supported by the public keydb

If you don't know how to get the SHA-1 hash of Unit_Key_RO.inf, simply open a terminal inside your disc's AACS folder and use the following command :

Code: Select all

sha1sum ./Unit_Key_RO.inf