Public KeyDB Disc Submissions

[BulldogK9]

Well that's just F***in bizarre. I've never had this problem with Libredrive before. It's enabled on the drive (see attached screenshot), but I got that error for every one and assumed it was a missing key. I didn't have this problem a few days ago when I ripped two other UHD discs.

Screenshot 2026-04-01 184531.png

I took your advice and waited until the OS (Windows 11) had recognized Godzilla in the drive and I was able to get MakeMKV to decrypt it. I deselected everything but the movie and had it start ripping it, but it never actually started writing anything to the hard drive.

I restarted the PC, because...sometimes that works.

Tried again. I'm back to my original situation. I can't get MakeMKV to read the thing at all. It's "Parsing file: /AACS/Content001.cer" and "Decrypting". At the 7 minute mark, the drive starts spinning again. Now it's parsing "/AACS/ContentHash001.tbl". it "times out" and I get the errors and it sends me back to the starting screen with the same dump file.

Try again, and I'm getting this:

MakeMKV v1.18.3 win(x64-release) started
Using LibreDrive mode (v06.3 id=866A98CB9C4E)
Error 'Scsi error - NOT READY:LOGICAL UNIT IS IN PROCESS OF BECOMING READY' occurred while reading 'BD-RE HL-DT-ST BD-RE BU40N 1.03 MO3P41F3338' at offset '33366145024'
udf: node fe/efe failed!
Error 'Scsi error - UNIT ATTENTION:NOT READY TO READY CHANGE, MEDIUM MAY HAVE CHANGED' occurred while reading 'BD-RE HL-DT-ST BD-RE BU40N 1.03 MO3P41F3338' at offset '655360'
udf: UDF mount: disc not properly formatted or damaged disc (rootdirs failing)
Failed to open disc

Right about now, I'm thinking that the drive (which is maybe 6 months old) is bad. Good thing I bought a backup at the same time. So, I put it in the second drive. (Note: Both have been jailbroken and have libredrive.) But it doesn't appear to be the drive. I'm having the same issue. (Changed the USB cable, no difference. Plugged it directly into the PC, rather than the powered USB hub, no difference.) Again, didn't have the problem on Saturday when I ripped the UHD of Rambo: Last Blood.

Maybe this drive just doesn't like Godzilla?!?

[BulldogK9]

Tried a different computer. Same symptoms.

Maybe these are just bad discs. I was able to load and start ripping King Kong: Skull Island. But the rip didn't happen. It never started writing data to the hard drive and the disc just sat there for 10+ minutes before I pulled the plug.

Put in one of the discs I ripped last weekend. It spun right up and behaved as expected.

Not sure whether to do a return/replacement of the 4k, or maybe just buy the bluray version and live with that.

[MartyMcNuts]

Tried a different computer. Same symptoms.

Maybe these are just bad discs. I was able to load and start ripping King Kong: Skull Island. But the rip didn't happen. It never started writing data to the hard drive and the disc just sat there for 10+ minutes before I pulled the plug.

Put in one of the discs I ripped last weekend. It spun right up and behaved as expected.

Not sure whether to do a return/replacement of the 4k, or maybe just buy the bluray version and live with that.

Did you clean the discs? This resolves most read errors unless the drive isn't getting enough power. Use UBS-C if possible and ports direct from the motherboard (not case ports) or an AC self-powered USB hub of at least 24w.

[MKVDUDE]

Another please -

Disc type: UHD
Disc dump filename:MKB20_v82_The_Nightcomers_827C.tgz
Drive: BD-RE BU40N
Drive firmware: 1.03
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: N/A
Disc dumps link: https://we.tl/t-FWsRwgsGfpOXYNGo

Many thanks!

[FootFungus07]

Runaway Train Kino Lorber Studio Classics 4K UHD

Disc type: UHD
Disc dump filename: MKB20_v82_Runaway_Train_5E40.tgz
Drive: BD-RE BP60NB10
Drive firmware: Enabled 2120-05-07 09:35
LibreDrive status: Enabled 1.02
Did you sync the public keydb within the last 15 minutes?: yes
Google Drive Link:
https://drive.google.com/file/d/1Q4lpop ... drive_link

Thanks again!

[frameloose]

https://drive.google.com/drive/folders/ ... axLWRmwquf

MKB20_v77_Se7en_4BC1
MKB20_v82_Greenland_2_586A

[Pipo_93]

Disc type: UHD
Disc: Battleship
Disc ID: 0x7FCAC1809A9CDE02A152C422B9B848300FC30462
MKB version: 61
Disc dump filename: MKB20_v61_Battleship_AAD3.tgz
LibreDrive status: Enabled
Did you sync the public keydb within the last 15 minutes?: Yes
Disc dump link: https://gofile.io/d/9aHuqx

[BulldogK9]

Did you clean the discs? This resolves most read errors unless the drive isn't getting enough power. Use UBS-C if possible and ports direct from the motherboard (not case ports) or an AC self-powered USB hub of at least 24w.

Discs are brand new and pristine. Didn't spot a single mark on them.

My first attempt was on a high-powered USB hub. The laptop I tried it on was plugged in and fully-juiced. I had no problem popping in other UHD discs and burning them again, just to test the drive. I think that this is just a bad pressing.

[Woodstock]

Discs are brand new and pristine. Didn't spot a single mark on them.

That wasn't the question. "NEW" DISKS CAN HAVE CONTAMINATION ON THEM.

If the disk was in its packaging for more than 6 months before you tried ripping it, it could have accumulated a film that is difficult to see, but interferes with laser reading.

That's why it is standard practice to recommend cleaning a disk if it's giving trouble with reading.

[MrPenguin]

Disc ID: 0x7FCAC1809A9CDE02A152C422B9B848300FC30462
MKB version: 61
Disc dump filename: MKB20_v61_Battleship_AAD3.tgz

Thanks, and can you also provide the complete MKB_RO.inf file from your actual UHD disk please? The copy of this file inside the TGZ dump has been truncated to only 56 bytes, which makes it unusable to anyone except MakeMKV itself.

[keydb_helper]

Thanks to everyone who followed the template and provided new disc dump files. The following UHD discs have been processed but the public keydb seems to be having a submission issue:

Code: Select all

*MKB20_v61_Push_F861
*MKB20_v82_Greenland_2_586A
*MKB20_v82_Marty_Supreme_3204
*MKB20_v82_MUBIUS008U_1854
*MKB20_v82_POINT_BLANK_3F66
*MKB20_v82_Runaway_Train_5E40
*MKB20_v82_The_Nightcomers_827C

Until the submission issue is resolved, you can grab the keydb entries from this pastebin link and manually append them to your local keydb file.

Disc type: UHD
Disc: Battleship
Disc ID: 0x7FCAC1809A9CDE02A152C422B9B848300FC30462
MKB version: 61
Disc dump filename: MKB20_v61_Battleship_AAD3.tgz
LibreDrive status: Enabled
Did you sync the public keydb within the last 15 minutes?: Yes

MKB20_v77_Se7en_4BC1
MKB20_v82_Greenland_2_586A

Please follow the submission template detailed in the opening post instead of omitting required fields and adding new ones. If you don't include the full MKB_RO.inf file there are essentially two possible outcomes:
1. Your discs media key is already known to the public keydb, so the absence of the MKB_RO.inf isn't terminal but your discs keys could've been derived with SamuriHL's KeyDB tool
2. Your discs media key isn't known to the public keydb and it can't be calculated because you failed to include the full MKB_RO.inf file

Well that's just F***in bizarre. I've never had this problem with Libredrive before. It's enabled on the drive (see attached screenshot), but I got that error for every one and assumed it was a missing key. I didn't have this problem a few days ago when I ripped two other UHD discs.

Whilst MakeMKV describes the LibreDrive status as 'Enabled' a more accurate label would probably be 'Capable' or 'Supported'. LibreDrive requires microcode extensions to run on your drive. If a drive encounters a firmware issue, certain timeouts or transient power faults, they can effectively self-reboot and end up in the non-LibreDrive state that you observed.

[polskasubie]

Disc type: UHD
Disc ID:
Disc dump filename: MKB20_v82_The_Sword_and_the_Sorcerer_02DA
Drive:
Drive firmware:
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
Disc dump link: https://drive.google.com/file/d/14A-KH7 ... sp=sharing

[keydb_helper]

Disc dump filename: MKB20_v82_The_Sword_and_the_Sorcerer_02DA

Thanks for the submission polskasubie, the 02DA variant of The Sword and the Sorcerer has been added to the public keydb.

The following UHD discs have also been added to the public keydb (new media keys are indicated with an asterisk):

Code: Select all

*MB20_v77_PREDATOR_BADLANDS (0x17EA1505F533CEF4965A68D62CE1DA0F3E38D33E)
*MKB20_v82_PIRATI_450A
*MKB20_v82_UFOria (0x5360363407DE9439BDB960F0B6E3002F801BD8EF)

[userhou4]

Hi, I sent you some information about decrypting a CD, but you replied that the MKB_RO.inf file size is incorrect. I tried decrypting the UHD CD I have, but the Disc dump file size is always the same, and the MKB_RO.inf file is only 56 bytes each time. Could you please help me decrypt this CD?Thanks
Disc type:UHD
Disc ID:
Disc dump filename:MKB20_v76_BDROM_3C87
Drive:BU40N
Drive firmware:1.03MK
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 (Do not just extract the MKB_RO.inf file from the disc dump file - copy it from the disc):https://drive.google.com/file/d/1hXziE5 ... drive_link

Disc dump link:https://drive.google.com/file/d/10QM1Qq ... drive_link

[keydb_helper]

Hi, I sent you some information about decrypting a CD, but you replied that the MKB_RO.inf file size is incorrect. I tried decrypting the UHD CD I have, but the Disc dump file size is always the same, and the MKB_RO.inf file is only 56 bytes each time. Could you please help me decrypt this CD?Thanks

I didn’t receive any message from you so I can’t comment on your prior discussions. But as I noted in the opening post you need to copy the MKB_RO.inf file from the folder on the disc. Extracting the partial file from the disc dump is absolutely useless. Everyone involved in the public keydb is more than capable of extracting files from disc dumps so there is no point in extracting the file yourself. The template you copied explicitly noted this requirement.

You need to browse the disc structure in Windows file explorer, macOS Finder or a Linux equivalent, then open the AACS folder, and copy the MKB_RO.inf file.

For AACS2/UHD discs, if your MKB_RO.inf file isn’t several megabytes in size it is useless.