4k BD Rip - Failing with Error "The Volume Key is Unknown for this Disc - video can't be decrypted"

Question

4k BD Rip - Failing with Error "The Volume Key is Unknown for this Disc - video can't be decrypted"

alexandrenobrega1 opened this issue a year ago · comments

As per the title, having issues with 4k discs that I was able to decrypt with my drive previously while connected directly to PC - moved it to external enclosure and been having great success with regular BR discs - However for the few 4k Discs that I have, it is failing.

Happy to share more info as needed.

Jocelyn Le Sage · Answer 1 · Wed Feb 15 2023 01:30:40 GMT+0800 (China Standard Time)

This is not really an issue, but this is how MakeMKV works: it needs a key to decrypt the disc. It seems that no key is available yet for your disc.

More details on the MakeMKV forum:

https://forum.makemkv.com/forum/viewtopic.php?t=24711
https://forum.makemkv.com/forum/viewtopic.php?f=12&t=16883

If the container has access to the internet, you did not disabled internet access in MakeMKV settings and you don't see other errors, you probably need to send the dump.

alexandrenobrega1 · Answer 2 · Wed Feb 15 2023 01:41:41 GMT+0800 (China Standard Time)

As I mentioned, i was able to decrypt those previously with regular makemkv, so keys are def. available. I'm checking the internet connection from the container next, setting is enabled in makemkv but did not check if container has proper connectivity yet.

…

On Tue, Feb 14, 2023, 18:30 Jocelyn Le Sage ***@***.***> wrote: This is not really an issue, but this is how MakeMKV works: it needs a key to decrypt the disc. It seems that no key is available yet for your disc. More details on the MakeMKV forum: https://forum.makemkv.com/forum/viewtopic.php?t=24711 https://forum.makemkv.com/forum/viewtopic.php?f=12&t=16883 If the container has access to the internet, you did not disabled internet access in MakeMKV settings and you don't see other errors, you probably need to send the dump. — Reply to this email directly, view it on GitHub <#168 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AG6BYK2MPQAAMA7FMHLZKHLWXO6MVANCNFSM6AAAAAAU3YQP4A> . You are receiving this because you authored the thread.Message ID: ***@***.***>

Adam White · Answer 3 · Wed Feb 15 2023 01:44:18 GMT+0800 (China Standard Time)

How is the external enclosure connected? USB?

Jocelyn Le Sage · Answer 4 · Wed Feb 15 2023 01:45:18 GMT+0800 (China Standard Time)

MakeMKV should clearly tell you if keys failed to be downloaded.

alexandrenobrega1 · Answer 5 · Wed Feb 15 2023 02:05:59 GMT+0800 (China Standard Time)

It is an ICY BOX IB-550STU3S connected to a QNAP TS464 via USB. With this config: DVD Rip: OK BR: OK 4k BR: Fail With the error mentioned. Moved Enclosure to my PC, Was able to open disc w/o Issues: [image: image.png] With container: [image: image.png] I reviewed the output and indeed I don't see any mention of keys failing; Will further TS on this later and provide more as I move along. If there are any specifics or if someone else could confirm 4K BR rips should be fine, would be great :)

…

On Tue, Feb 14, 2023 at 6:44 PM Adam White ***@***.***> wrote: How is the external enclosure connected? USB? — Reply to this email directly, view it on GitHub <#168 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AG6BYK5AGIPHLJBMZY4PES3WXO77ZANCNFSM6AAAAAAU3YQP4A> . You are receiving this because you authored the thread.Message ID: ***@***.***>

Adam White · Answer 6 · Wed Feb 15 2023 02:07:40 GMT+0800 (China Standard Time)

@alexandrenobrega1, the images didn't attach because of the email reply. Could you try putting them directly on GitHub?

And yes, I can confirm that I rip 4K UHD with this container regularly

alexandrenobrega1 · Answer 7 · Wed Feb 15 2023 02:09:34 GMT+0800 (China Standard Time)

Apologies - images as follows:

C4Wiz · Answer 8 · Wed Feb 15 2023 02:10:33 GMT+0800 (China Standard Time)

the error code means there is no decryption key for the disc. do you have connect to internet disabled?

C4Wiz · Answer 9 · Wed Feb 15 2023 02:11:23 GMT+0800 (China Standard Time)

also upgrade the container to the latest version

alexandrenobrega1 · Answer 10 · Wed Feb 15 2023 02:14:39 GMT+0800 (China Standard Time)

Internet is enabled on *makemkv settings:

From Container seems that I am able to get out - tho I am not sure if this would be the right command to test this on docker (still new on docker, sadly)
]$ sudo docker exec makemkv ping 8.8.8.8
Password:
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=115 time=18.942 ms
64 bytes from 8.8.8.8: seq=1 ttl=115 time=12.158 ms
64 bytes from 8.8.8.8: seq=2 ttl=115 time=10.721 ms
64 bytes from 8.8.8.8: seq=3 ttl=115 time=10.619 ms
64 bytes from 8.8.8.8: seq=4 ttl=115 time=14.359 ms

And Container created today, so I'm pretty sure this is the latest version?>*

C4Wiz · Answer 11 · Wed Feb 15 2023 02:15:36 GMT+0800 (China Standard Time)

submit this file: Saved AACS dump file as /config/data/MKB20 v76 Eric Clapton • The Lady In The Balcony 771.tgz to svq@makemkv.com and wait for it to be added.

Since MakeMKV doesn't contain any BD+ keys it requires either generic or disc-specific SVQ file to process BD+ protected disc. If no disc-specific SVQ is available or BD+ version is too new for a generic svq, and "BD+ dump directory" is set in preferences then program will create a "BD+ dump file". We will produce and make available for download disc-specific SVQ files from all dump files sent to svq@makemkv.com . Sending us a dump file will help to analyze new versions of BD+ protection and expand the generic svq support.

C4Wiz · Answer 12 · Wed Feb 15 2023 02:16:43 GMT+0800 (China Standard Time)

from your screenshot above, it shows MakeMKV Version 1.17.2 and the current container is Version 1.17.3

alexandrenobrega1 · Answer 13 · Wed Feb 15 2023 02:18:19 GMT+0800 (China Standard Time)

@C4Wiz 1.17.2 is from my PC where I am able to decrypt the disc just fine:

Container is running *latest version as a matter of fact.

C4Wiz · Answer 14 · Wed Feb 15 2023 02:21:12 GMT+0800 (China Standard Time)

ok, not sure why you are posting screenshots from 2 different machines together. post the screenshot from the container with the failing to decrypt message. the full screenshot

alexandrenobrega1 · Answer 15 · Wed Feb 15 2023 02:23:38 GMT+0800 (China Standard Time)

@C4Wiz posting both screenshots to rule out the "this is a new disc and we don't have the keys to decrypt it yet" theory. As you can see, outside of the container, the disc is decrypted just fine.

Screenshot from Container's logs where I tried to open the same disc twice:

C4Wiz · Answer 16 · Wed Feb 15 2023 02:26:38 GMT+0800 (China Standard Time)

yea, there is no key for the disc, it clearly states it right below the hyperlink.
submit the dump and check again in a few days.

if you have sucesfully opened this EXACT PHYSICAL DISC on the other machine, then your docker container is not reaching the server to download the keys

C4Wiz · Answer 17 · Wed Feb 15 2023 02:33:58 GMT+0800 (China Standard Time)

just a fyi 2 of the same disc could need a different key

C4Wiz · Answer 18 · Wed Feb 15 2023 02:35:15 GMT+0800 (China Standard Time)

connect the usb enclosure to your pc and open the disc with makemkv on your pc, if it opens it's your container not reaching the server, if it doesnt then there is no key for it yet, submit the dump and wait

alexandrenobrega1 · Answer 19 · Wed Feb 15 2023 03:14:15 GMT+0800 (China Standard Time)

@C4Wiz Perhaps I am not being clear enough in all that I wrote so far, so a quick summary:

WITH THE EXACT SAME PHYSICAL DISC (4K Blu-ray):

1 - Enclosure connected to NAS, with docker container, Fails with the errors already presented;
2 - EXACT same enclosure, moved to PC, Makemkv app running on windows 10, Disc is decrypted and converted w/o any issues.

The Docker container has the internet access enabled in the configs (screenshot above) and I ran the command below from CLI so internet access seems to be fine:

]$ sudo docker exec makemkv ping 8.8.8.8
Password:
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=115 time=18.942 ms
64 bytes from 8.8.8.8: seq=1 ttl=115 time=12.158 ms
64 bytes from 8.8.8.8: seq=2 ttl=115 time=10.721 ms

C4Wiz · Answer 20 · Wed Feb 15 2023 03:18:40 GMT+0800 (China Standard Time)

Ok, well im telling you the docker IS NOT reaching the server to download keys.
Copy your private_data.tar and sdf.bin from your pc to your docker and see if it works. If it does it proves my point.

C4Wiz · Answer 21 · Wed Feb 15 2023 03:20:07 GMT+0800 (China Standard Time)

Im running the same docker on my unraid server and it works fine. So it’s not the container

Jocelyn Le Sage · Answer 22 · Wed Feb 15 2023 06:01:30 GMT+0800 (China Standard Time)

@C4Wiz, did you remove the downloaded data and confirmed that it was re-downloaded ?

C4Wiz · Answer 23 · Wed Feb 15 2023 07:11:42 GMT+0800 (China Standard Time)

i do not have a encrypted disc to test with at the moment

Accalia Elementia · Answer 24 · Wed Feb 15 2023 09:24:26 GMT+0800 (China Standard Time)

I'll confirm this issue.

Using identical 4k bluray that i've previously ripped on the exact host machine receiving identical behavior to alexandre in the opening upon trying to read the disk with the docker image.

As suggested above verified that internet access is reported as enabled, container can ping both 8.8.8.8 and google.com resolves as host name.

Attempting to open the 4k bluray in the container results in the following output to the information window:

Happy to provide more information or make attempts at diagnosis if it will assist.

Jocelyn Le Sage · Answer 25 · Wed Feb 15 2023 09:29:16 GMT+0800 (China Standard Time)

Can you try (the older) version 1.22.2 of the Docker image ?

Accalia Elementia · Answer 26 · Wed Feb 15 2023 09:40:44 GMT+0800 (China Standard Time)

sure. updated my docker-compose image to pull that tag, restarted container and.....

Success.

I notice that this info screen mentions downloading latest SDF on startup where the prior version did not, and on opening the disk and loading the content hash table it mentions downloading the HK so I suspect something in the new image is preventing that?

Let me know if you would like further diagnosis steps to be taken, or beta images to be tried to test fixes.

-Accalia

Jocelyn Le Sage · Answer 27 · Wed Feb 15 2023 11:45:48 GMT+0800 (China Standard Time)

Thanks for the info.
Could you try the Docker image tag issue168 ?

alexandrenobrega1 · Answer 28 · Wed Feb 15 2023 15:23:50 GMT+0800 (China Standard Time)

@jlesage thank you so much for actually looking into the issue here and @AccaliaDeElementia for also actually double-checking :)

I just ran tests with container tagged as issue168 and it was a great success:

Accalia Elementia · Answer 29 · Wed Feb 15 2023 19:41:17 GMT+0800 (China Standard Time)

I'll also confirm. tag issue168 is also able to read and decrypt 4k blurays. I cleared config and storage volumes to ensure no false positives from already having the keys downloaded and it worked. Thanks for looking into this and for getting a fix out so quickly.

…

On Wed, Feb 15, 2023 at 2:24 AM alexandrenobrega1 ***@***.***> wrote: @jlesage <https://github.com/jlesage> thank you so much for actually looking into the issue here and @AccaliaDeElementia <https://github.com/AccaliaDeElementia> for also actually double-checking :) I just ran tests with container tagged as issue168 and it was a great success: [image: image] <https://user-images.githubusercontent.com/29105195/218959748-593e18e8-ab5c-4ac1-a788-34fb7034eeb8.png> — Reply to this email directly, view it on GitHub <#168 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGKQJEH73OJJCXEPGIY62DWXSABFANCNFSM6AAAAAAU3YQP4A> . You are receiving this because you were mentioned.Message ID: ***@***.***>

Jocelyn Le Sage · Answer 30 · Wed Feb 15 2023 20:14:29 GMT+0800 (China Standard Time)

Thanks for confirming. I will prepare and publish an official image with the fix.

Jocelyn Le Sage · Answer 31 · Thu Feb 16 2023 02:53:17 GMT+0800 (China Standard Time)

Official image now available!

kapratt · Answer 32 · Wed Oct 11 2023 11:55:53 GMT+0800 (China Standard Time)

This issue seems to have popped up for me in the latest version. My logs appear as below:

001011:0000 Using LibreDrive mode (v06.3 id=F046CEB2F3AB)
003007:0000 Using direct disc access mode
005085:0000 Loaded content hash table, will verify integrity of M2TS files.
DEBUG: Code 2147483648 at v,`=g{&=n3FORp$%:121265499
001003:0020 DEBUG: Code 0 at Dba&0i#r_n[Z|</K]|d_@P:29393631
001003:0020 DEBUG: Code 0 at v,`=g{&=n3FORp$%:29399956
003332:0000 Saved AACS dump file as file:///config/data/MKB20_v77_MARVEL_STUDIOS'_LOKI_SEASON_1_DISC_2_2A52.tgz
003303:0000 The volume key is unknown for this disc - video can't be decrypted
001003:0020 DEBUG: Code 0 at ,pDYX3_ZfOf\9%`k:213132721
001003:0020 DEBUG: Code 0 at ,pDYX3_ZfOf\9%`k:213131341
005010:0000 Failed to open disc

The network setting is set and I'm fairly positive that the server is reachable as I can use MakeMKV on my own machine. I don't know if this might cause this, but this is running on a Raspberry Pi CM4.

C4Wiz · Answer 33 · Wed Oct 11 2023 12:36:31 GMT+0800 (China Standard Time)

This issue seems to have popped up for me in the latest version. My logs appear as below:

001011:0000 Using LibreDrive mode (v06.3 id=F046CEB2F3AB)
003007:0000 Using direct disc access mode
005085:0000 Loaded content hash table, will verify integrity of M2TS files.
DEBUG: Code 2147483648 at v,`=g{&=n3FORp$%:121265499
001003:0020 DEBUG: Code 0 at Dba&0i#r_n[Z|</K]|d_@P:29393631
001003:0020 DEBUG: Code 0 at v,`=g{&=n3FORp$%:29399956
003332:0000 Saved AACS dump file as file:///config/data/MKB20_v77_MARVEL_STUDIOS'_LOKI_SEASON_1_DISC_2_2A52.tgz
003303:0000 The volume key is unknown for this disc - video can't be decrypted
001003:0020 DEBUG: Code 0 at ,pDYX3_ZfOf\9%`k:213132721
001003:0020 DEBUG: Code 0 at ,pDYX3_ZfOf\9%`k:213131341
005010:0000 Failed to open disc

The network setting is set and I'm fairly positive that the server is reachable as I can use MakeMKV on my own machine. I don't know if this might cause this, but this is running on a Raspberry Pi CM4.

It means makemkv does not have a decryption key for the disc, submit the dump and wait. A quick search on the makemkv forum would have answered this question

kapratt · Answer 34 · Wed Oct 11 2023 12:45:32 GMT+0800 (China Standard Time)

I’m well aware of what the error means. I posted in this issue because I am having the exact same issue as the original issue.

I am able to rip this UHD disc on my main laptop if I take the drive to that machine as the hash keys are available for download. However the docker version is not downloading the already available hash keys. If you would like manual proof I can provide logs but I believe the error causing this that was fixed in February appears to be present again, at least in the ARM version of the docker container.

kapratt · Answer 35 · Wed Oct 11 2023 23:44:33 GMT+0800 (China Standard Time)

The following log was from the Docker machine. I tried loading the disc and it failed. Then I SSHed in the HK file from my computer where I had successfully loaded the blu ray 5 minutes earlier and the docker container was successfully able to load the disc.

Debug log started at Wed Oct 11 15:29:03 2023 , written by MakeMKV v1.17.5 linux(arm64-release)
001005:0000 MakeMKV v1.17.5 linux(arm64-release) started
001004:0000 Debug logging enabled, log will be saved as file:///config/MakeMKV_log.txt
Using 262272KB for read cache.
001003:0020 DEBUG: Code 0 at Dba&0i#r_n[Z|</K]|d_@P:29393631
001003:0020 DEBUG: Code 0 at v,`=g{&=n3FORp$%:213144750
SDF  v097: BUFFALO_Optical_Drive_BU10_211705301728_MOAKACA4523
SDF  v097: BUFFALO_Optical_Drive_BU10_211705301728_MOAKACA4523
001003:0020 DEBUG: Code 0 at Dba&0i#r_n[Z|</K]|d_@P:29393631
SDF  v097: BUFFALO_Optical_Drive_BU10_211705301728_MOAKACA4523
001011:0000 Using LibreDrive mode (v06.3 id=F046CEB2F3AB)
003007:0000 Using direct disc access mode
005085:0000 Loaded content hash table, will verify integrity of M2TS files.
DEBUG: Code 2147483648 at v,`=g{&=n3FORp$%:121265499
001003:0020 DEBUG: Code 0 at v,`=g{&=n3FORp$%:29399956
003332:0000 Saved AACS dump file as file:///config/data/MKB20_v77_MARVEL_STUDIOS'_LOKI_SEASON_1_DISC_2_2A52.tgz
003303:0000 The volume key is unknown for this disc - video can't be decrypted
001003:0020 DEBUG: Code 0 at ,pDYX3_ZfOf\9%`k:213132721
001003:0020 DEBUG: Code 0 at ,pDYX3_ZfOf\9%`k:213131341
005010:0000 Failed to open disc
001011:0000 Using LibreDrive mode (v06.3 id=F046CEB2F3AB)
003007:0000 Using direct disc access mode
005085:0000 Loaded content hash table, will verify integrity of M2TS files.
DEBUG: Code 2147483648 at v,`=g{&=n3FORp$%:121265499
001003:0020 DEBUG: Code 0 at v,`=g{&=n3FORp$%:29399956
Found java version=1.8.0.372 path=/usr/lib/jvm/java-1.8-openjdk/bin/java
Found java version=1.8.0.372 path=/usr/bin/java
003344:0000 Using Java runtime from /usr/lib/jvm/java-1.8-openjdk/bin/java
DISCID=91AB806257021684C68017D7F65F9489CC8FFFFE
003025:0000 Title #00152.mpls has length of 5 seconds which is less than minimum title length of 120 seconds and w...

Then, I renamed the new HK file to force a new download, and the docker container did not download and therefore failed.

SDF  v097: BUFFALO_Optical_Drive_BU10_211705301728_MOAKACA4523
001011:0000 Using LibreDrive mode (v06.3 id=F046CEB2F3AB)
003007:0000 Using direct disc access mode
005085:0000 Loaded content hash table, will verify integrity of M2TS files.
DEBUG: Code 2147483648 at v,`=g{&=n3FORp$%:121265499
001003:0020 DEBUG: Code 0 at v,`=g{&=n3FORp$%:29399956
003332:0000 Saved AACS dump file as file:///config/data/MKB20_v77_MARVEL_STUDIOS'_LOKI_SEASON_1_DISC_2_2A52.tgz
003303:0000 The volume key is unknown for this disc - video can't be decrypted
001003:0020 DEBUG: Code 0 at ,pDYX3_ZfOf\9%`k:213132721
001003:0020 DEBUG: Code 0 at ,pDYX3_ZfOf\9%`k:213131341
005010:0000 Failed to open disc

Finally, here is the lookup for the HK download location, showing that the server can be reached from the docker machine.

Non-authoritative answer:
Name:	hkdata.fairuse.org
Address: 185.84.108.20

So, again, this appears to be a very similar issue as the original issue that appears to be popping up again in the new version.

Jocelyn Le Sage · Answer 36 · Fri Oct 20 2023 23:22:51 GMT+0800 (China Standard Time)

Is it working if you use the previous version ?

kapratt · Answer 37 · Sat Oct 28 2023 03:51:50 GMT+0800 (China Standard Time)

I actually cannot as this is on an arm64 system and the prior versions of makemkv bundled with the docker version do not work.

kapratt · Answer 38 · Thu Dec 07 2023 02:25:07 GMT+0800 (China Standard Time)

I just want to state that this problem is still occurring. Every so often I have to move my drive to a regular PC, open a disc (usually a 4k disc) to download the new keys, and then manually transfer the key file to the docker container on my ripping computer. And then move the drive back to the ripping / docker computer. Newer versions of the docker container installed in the last month have not fixed this issue either.