KEY NOT PRESENT error

The place to discuss linux version of MakeMKV
Post Reply
cryox
Posts: 5
Joined: Mon Sep 25, 2023 6:42 pm

KEY NOT PRESENT error

Post by cryox »

I'm receiving a lot of 'KEY NOT PRESENT' and some 'KEY NOT ESTABLISHED' errors using the linux version:

Code: Select all

MakeMKV v1.17.8 linux(x64-release) started
Backing up disc into folder ...
Error 'Scsi error - ILLEGAL REQUEST:COPY PROTECTION KEY EXCHANGE FAILURE - KEY NOT PRESENT' occurred while issuing SCSI command A30..0020..03F to device 'SG:dev_21:0'
...
Error 'Scsi error - ILLEGAL REQUEST:COPY PROTECTION KEY EXCHANGE FAILURE - KEY NOT ESTABLISHED' occurred while issuing SCSI command AD010..080002400 to device 'SG:dev_21:0'
...
Can't read AACS VID from disc - most likely current AACS host certificate is revoked by your drive
Saved AACS dump file as ...
LibreDrive compatible drive is required to open this disc - video can't be decrypted.
Backup failed
What I tried so far (always the same drive with the same BluRay):
Machine A (Arch) -> MakeMKV from AUR -> fails
Machine A (Arch) -> MakeMKV from Flatpak -> fails
Machine A (Arch) -> Ubuntu VM -> MakeMKV built as described here -> fails
Machine A (Arch) -> Windows VM -> MakeMVK from the website -> works
Machine B (Windows) -> MakeMVK from the website -> works

So I'm pretty confident there is something wrong with the Linux version. Also, since running it on a vanilla Ubuntu 24.10 VM using the manual as described doesn't work.

Has anyone faced a similar issue and was able to solve it?
dcoke22
Posts: 3775
Joined: Wed Jul 22, 2020 11:25 pm

Re: KEY NOT PRESENT error

Post by dcoke22 »

Is your drive LibreDrive compatible? Have you flashed it to enable LibreDrive?
hobbified
Posts: 1
Joined: Mon Feb 17, 2025 8:47 pm

Re: KEY NOT PRESENT error

Post by hobbified »

Same thing here. Yes it's a compatible drive, a BRUHD-PU3-BK that I flashed. Rips work okay on MakeMKV 1.17.9 for Windows, but if I take the same drive and same disc and plug them into my Linux machine the copying process will start, then after a few seconds the drive spins down and there are a bunch of SCSI NOT READY errors, then when it spins up again it shows the KEY NOT PRESENT error several times. It continues copying data but the results are garbage. Kernel logs show

Code: Select all

sr 7:0:0:0: Power-on or device reset occurred
at the same time. So it seems like it's essentially crashing the drive.
Woodstock
Posts: 10574
Joined: Sun Jul 24, 2011 11:21 pm

Re: KEY NOT PRESENT error

Post by Woodstock »

Another possibility is that it powered down, due to an over-speed condition. If the USB port isn't a "fully compatible" USB3 port, a drive can run out of power with only one plug inserted. This would tend to happen on a long read.

If it's happening right after the read starts, it would be strange.
cryox
Posts: 5
Joined: Mon Sep 25, 2023 6:42 pm

Re: KEY NOT PRESENT error

Post by cryox »

Thanks for your suggestions! As indicated in the original post, the same drive, with the same firmware, same disc, same PC and same USB-Port works just fine when using Windows.

I can't really find any other reason than there is something missing or broken with the Linux version.
cryox
Posts: 5
Joined: Mon Sep 25, 2023 6:42 pm

Re: KEY NOT PRESENT error

Post by cryox »

Problem still present in 1.17.9

Code: Select all

Saved AACS dump file as ...
The volume key is unknown for this disc - video can't be decrypted
I could further narrow it down: It works with normal Blu-rays (tested with AACS v28), but not with UHD Blu-rays (tested with AACS2.0/C v77).

The issue is probably related to how MakeMKV handles UHD decryption on Linux.

Can anyone give further hints to where to look for insights?
HeyQuitThat
Posts: 1
Joined: Mon Mar 03, 2025 1:33 am

Re: KEY NOT PRESENT error

Post by HeyQuitThat »

Just to jump on this bandwagon, I'm seeing the same thing. Linux Mint 22.1 on x86_64. I'm running an LG BU40N with patched firmware 1.03MK. It rips DVDs OK in Linux but chokes on UHD. Same exact setup works in Windows. I'm running registered Make MKV 1.17.9.
dcoke22
Posts: 3775
Joined: Wed Jul 22, 2020 11:25 pm

Re: KEY NOT PRESENT error

Post by dcoke22 »

I've seen it suggested on this forum that a BU40N needs to be flashed to firmware 1.00 to work the best on Linux.

https://forum.makemkv.com/forum/viewtopic.php?p=154090#p154090
bernie
Posts: 2
Joined: Sun Jul 13, 2025 6:29 pm

Re: KEY NOT PRESENT error

Post by bernie »

Has there been any update to this issue?

I am experiencing the same problem on Linux. My system is Ubuntu 24.04.

I have tried multiple variants of the customized firmware, including version 1.03 from "The all you need firmware pack", as well as the DE 1.00 version suggested before. Both firmware versions result in this same error.

I've also tried both versions 1.18.1 and 1.17.7 without success. Version 1.17.7 is the only version which does not hang when flashing the firmware (issue appears to be reported here: viewtopic.php?p=174231#p174231).

The drive info on MakeMKV shows the drive as being LibreDrive enabled:
Drive Information
OS device name: /dev/sr0
Manufacturer: HL-DT-ST
Product: BD-RE BU40N
Revision: 1.03
Serial number: . . .
Firmware date: 2118-10-24 19:34
Bus encryption flags: 17
Highest AACS version: 66

LibreDrive Information
Status: Enabled
Drive platform: MT1959
Firmware type: Patched (microcode access re-enabled)
Firmware version: 1.03
DVD all regions: Yes
BD raw data read: Yes
BD raw metadata read: Yes
Unrestricted read speed: Yes
I have no trouble with traditional blu-ray discs, it is only 4k UHD discs that have this error. Unfortunately, I do not any Windows or Mac systems which I can try. Any ideas of any other next steps worth trying to see if I can get 4k UHD discs working in Linux?
bernie
Posts: 2
Joined: Sun Jul 13, 2025 6:29 pm

Re: KEY NOT PRESENT error

Post by bernie »

Actually, I think I figured out my issue. Much like many others, I was able to get it to work with the older 1.00 firmware. The mistake I made before was flashing the firmware as encrypted (with the 'enc' flag). Apparently this flag was required when flashing to the original 1.03 firmware, but when going from 1.03 to 1.00, I suppose this is incorrect.

When I flashed the drive to use the 1.00 without the encrypted flag, it appears to work without issue.
Post Reply