Disc type: UHD
Disc ID: 0x8E8E794C75D80CA8417BC855E7A2DD22A8D8F867
Disc dump filename: MKB20_v82_La_La_Land_462A
Drive: BW-16D1HT
Drive firmware: 3.10
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
Is your MKB_RO.inf file size at least 2MB? Yes
MKB_RO.inf link: (must be at least 2MB - copy it directly from the AACS folder on the original disc, do not extract it from the disc dump file) https://drive.google.com/file/d/1zJSaQF ... drive_link
Disc dump link: https://drive.google.com/file/d/1qNDgz_ ... drive_link
Public KeyDB Disc Submissions
-
MartyMcNuts
- Posts: 5199
- Joined: Wed Nov 22, 2017 11:45 pm
Re: Public KeyDB Disc Submissions
Do not use v2.0.0. Use v1.18.4turbov6camaro wrote: Sat Nov 21, 2026 8:49 pm SUBJECT: Fury 4K (AACS 2.1) - complete, validated keydb record, but rip fails at offset 71454720 in 00001.fmts with no read errors
Hi all,
I have one UHD that will not rip even though the key record looks complete, and I would appreciate a pointer on what is missing.
Disc: Fury - 4K Ultra HD (Sony, disc date 2018-02-21)
Disc type: UHD Blu-ray, AACS 2.1, MKB v61
Volume label: FURY
Disc ID: B3D29EF69DFF0FAABB5A747A3317847BF1180AC7
Volume size: 97,737,768,960 bytes
MakeMKV: v2.0.0 win(x64-release)
Drive: LG BP60NB10, firmware 1.02
LibreDrive status: Enabled
Synced keydb in the last 15 minutes: Yes
What happens
The disc opens and scans normally. MakeMKV finds the main title (title 0, 2:14:38, 70 GB, HEVC 2160p, TrueHD Atmos). The rip then fails about 30 seconds after "Saving 1 titles":
Why I do not think it is the disc or the driveCode: Select all
Downloading latest HK to C:\Users\...\.MakeMKV ... Automatic HK downloading is disabled or failed. Operation successfully completed Saving 1 titles into directory file://C:\Rips\Staging\Fury (2014) The source file '/BDMV/STREAM/00001.fmts' is corrupt or invalid at offset 71454720, attempting to work around (repeated many times) Too many AV synchronization issues in file '/BDMV/STREAM/00001.fmts' (title #-) , future messages will be printed only to log file LIBMKV_TRACE: Exception: Error in p->FetchFrames(1,false) 0 titles saved, 1 failed
- There are no SCSI read errors at all. No L-EC UNCORRECTABLE, no MEDIUM ERROR, no TIMEOUT.
- It fails at exactly the same offset (71454720) every time, 5 attempts so far.
- Same result in two different drives.
- The disc is brand new and clean.
- The same drives ripped 25 other UHDs in the same two days without trouble, including 80 to 91 GB triple-layer discs.
Key status
- The keydb has a complete record for this disc ID (M, I, V and U all present), created by FindVUK 2.08, MKBv61.
- KeyDB Helper reports: Database: (VALIDATED), Status: complete.
- It also prints "Unit Key validation failed with 3 aligned units", but it prints that for my other discs too, and those rip fine.
My question
Mike's "AACS versions and revisions" post says AACS 2.0 and 2.1 are independent key-wise and that 2.1 is supported from 1.14.6. Is a normal keydb record (MK / VID / VUK / UK) enough for an AACS 2.1 disc like Fury, or does 2.1 need something more that I do not have, for example working hashed keys? HK download has never worked on my setup, and until now it has not mattered.
MKB_RO.inf is at least 2MB: Yes, 128 MB (copied straight from the disc)
Links verified in incognito: Yes
MKB_RO.inf link: https://drive.google.com/file/d/1QdJWcE ... 6fXwN/view
Disc dump link: No dump exists. MakeMKV did not create one because it treats the key as known. The zip above holds MKB_RO.inf and the disc ID. If a dump would help, tell me how to produce one for a disc MakeMKV thinks it can already open, and I will add it.
Thanks for any help.
Cheers
----------------------------------------------------------------------------------------------------------------------------
** NEW Single Drive Flasher ** available worldwide! https://payhip.com/b/MyeJ9
Email: martymcnuts@outlook.com
----------------------------------------------------------------------------------------------------------------------------
** NEW Single Drive Flasher ** available worldwide! https://payhip.com/b/MyeJ9
Email: martymcnuts@outlook.com
-
turbov6camaro
- Posts: 38
- Joined: Sun Oct 18, 2026 3:27 pm
Re: Public KeyDB Disc Submissions
disk is brand new - but yes i did wipe it just in caseMrPenguin wrote: Sat Nov 21, 2026 10:24 pmMakeMKV doesn't use KEYDB.cfg for AACS 2.1 disks, and the KEYDB.cfg doesn't contain the extra keys that AACS 2.1 needs, even if it did.turbov6camaro wrote: Sat Nov 21, 2026 8:49 pm SUBJECT: Fury 4K (AACS 2.1) - complete, validated keydb record, but rip fails at offset 71454720 in 00001.fmts with no read errors
Your problem is with either MakeMKV, or your disk itself. Have you tried cleaning your disk?
-
turbov6camaro
- Posts: 38
- Joined: Sun Oct 18, 2026 3:27 pm
Re: Public KeyDB Disc Submissions
Thanks. I tried v1.18.4 (unpacked side by side, same key and keydb).MartyMcNuts wrote: Sat Nov 21, 2026 11:15 pmDo not use v2.0.0. Use v1.18.4turbov6camaro wrote: Sat Nov 21, 2026 8:49 pm SUBJECT: Fury 4K (AACS 2.1) - complete, validated keydb record, but rip fails at offset 71454720 in 00001.fmts with no read errors
Hi all,
I have one UHD that will not rip even though the key record looks complete, and I would appreciate a pointer on what is missing.
Disc: Fury - 4K Ultra HD (Sony, disc date 2018-02-21)
Disc type: UHD Blu-ray, AACS 2.1, MKB v61
Volume label: FURY
Disc ID: B3D29EF69DFF0FAABB5A747A3317847BF1180AC7
Volume size: 97,737,768,960 bytes
MakeMKV: v2.0.0 win(x64-release)
Drive: LG BP60NB10, firmware 1.02
LibreDrive status: Enabled
Synced keydb in the last 15 minutes: Yes
What happens
The disc opens and scans normally. MakeMKV finds the main title (title 0, 2:14:38, 70 GB, HEVC 2160p, TrueHD Atmos). The rip then fails about 30 seconds after "Saving 1 titles":
Why I do not think it is the disc or the driveCode: Select all
Downloading latest HK to C:\Users\...\.MakeMKV ... Automatic HK downloading is disabled or failed. Operation successfully completed Saving 1 titles into directory file://C:\Rips\Staging\Fury (2014) The source file '/BDMV/STREAM/00001.fmts' is corrupt or invalid at offset 71454720, attempting to work around (repeated many times) Too many AV synchronization issues in file '/BDMV/STREAM/00001.fmts' (title #-) , future messages will be printed only to log file LIBMKV_TRACE: Exception: Error in p->FetchFrames(1,false) 0 titles saved, 1 failed
- There are no SCSI read errors at all. No L-EC UNCORRECTABLE, no MEDIUM ERROR, no TIMEOUT.
- It fails at exactly the same offset (71454720) every time, 5 attempts so far.
- Same result in two different drives.
- The disc is brand new and clean.
- The same drives ripped 25 other UHDs in the same two days without trouble, including 80 to 91 GB triple-layer discs.
Key status
- The keydb has a complete record for this disc ID (M, I, V and U all present), created by FindVUK 2.08, MKBv61.
- KeyDB Helper reports: Database: (VALIDATED), Status: complete.
- It also prints "Unit Key validation failed with 3 aligned units", but it prints that for my other discs too, and those rip fine.
My question
Mike's "AACS versions and revisions" post says AACS 2.0 and 2.1 are independent key-wise and that 2.1 is supported from 1.14.6. Is a normal keydb record (MK / VID / VUK / UK) enough for an AACS 2.1 disc like Fury, or does 2.1 need something more that I do not have, for example working hashed keys? HK download has never worked on my setup, and until now it has not mattered.
MKB_RO.inf is at least 2MB: Yes, 128 MB (copied straight from the disc)
Links verified in incognito: Yes
MKB_RO.inf link: https://drive.google.com/file/d/1QdJWcE ... 6fXwN/view
Disc dump link: No dump exists. MakeMKV did not create one because it treats the key as known. The zip above holds MKB_RO.inf and the disc ID. If a dump would help, tell me how to produce one for a disc MakeMKV thinks it can already open, and I will add it.
Thanks for any help.
Same result: the scan is fine, then it fails 7 seconds after "Saving 1 titles":
The source file '/BDMV/STREAM/00001.fmts' is corrupt or invalid at offset 71454720, attempting to work around
(repeated)
Too many AV synchronization issues in file '/BDMV/STREAM/00001.fmts'
LIBMKV_TRACE: Exception: Error while reading input
0 titles saved, 1 failed
So that is the same offset (71454720) on v2.0.0 and v1.18.4, in two drives, with no SCSI read errors on any attempt.
The same v1.18.4 folder is ripping another UHD (Twister) normally right now, so the install itself is good.
Is there anything else I can collect that would help? I can run a decrypted backup instead of an MKV rip, or post a full debug log, if either is useful.
-
MartyMcNuts
- Posts: 5199
- Joined: Wed Nov 22, 2017 11:45 pm
Re: Public KeyDB Disc Submissions
This is an AACS 2.1 title so does not use the KeyDB. MakeMKV can decrypt it natively but fails during the rip. Clean the disc before trying again. A brand new in the box disc means nothing. In fact, brand new often means it needs to be cleaned as they often have a layer of film on them from the manufacturing process.turbov6camaro wrote: Sun Nov 22, 2026 12:31 amThanks. I tried v1.18.4 (unpacked side by side, same key and keydb).MartyMcNuts wrote: Sat Nov 21, 2026 11:15 pmDo not use v2.0.0. Use v1.18.4turbov6camaro wrote: Sat Nov 21, 2026 8:49 pm SUBJECT: Fury 4K (AACS 2.1) - complete, validated keydb record, but rip fails at offset 71454720 in 00001.fmts with no read errors
Hi all,
I have one UHD that will not rip even though the key record looks complete, and I would appreciate a pointer on what is missing.
Disc: Fury - 4K Ultra HD (Sony, disc date 2018-02-21)
Disc type: UHD Blu-ray, AACS 2.1, MKB v61
Volume label: FURY
Disc ID: B3D29EF69DFF0FAABB5A747A3317847BF1180AC7
Volume size: 97,737,768,960 bytes
MakeMKV: v2.0.0 win(x64-release)
Drive: LG BP60NB10, firmware 1.02
LibreDrive status: Enabled
Synced keydb in the last 15 minutes: Yes
What happens
The disc opens and scans normally. MakeMKV finds the main title (title 0, 2:14:38, 70 GB, HEVC 2160p, TrueHD Atmos). The rip then fails about 30 seconds after "Saving 1 titles":
Why I do not think it is the disc or the driveCode: Select all
Downloading latest HK to C:\Users\...\.MakeMKV ... Automatic HK downloading is disabled or failed. Operation successfully completed Saving 1 titles into directory file://C:\Rips\Staging\Fury (2014) The source file '/BDMV/STREAM/00001.fmts' is corrupt or invalid at offset 71454720, attempting to work around (repeated many times) Too many AV synchronization issues in file '/BDMV/STREAM/00001.fmts' (title #-) , future messages will be printed only to log file LIBMKV_TRACE: Exception: Error in p->FetchFrames(1,false) 0 titles saved, 1 failed
- There are no SCSI read errors at all. No L-EC UNCORRECTABLE, no MEDIUM ERROR, no TIMEOUT.
- It fails at exactly the same offset (71454720) every time, 5 attempts so far.
- Same result in two different drives.
- The disc is brand new and clean.
- The same drives ripped 25 other UHDs in the same two days without trouble, including 80 to 91 GB triple-layer discs.
Key status
- The keydb has a complete record for this disc ID (M, I, V and U all present), created by FindVUK 2.08, MKBv61.
- KeyDB Helper reports: Database: (VALIDATED), Status: complete.
- It also prints "Unit Key validation failed with 3 aligned units", but it prints that for my other discs too, and those rip fine.
My question
Mike's "AACS versions and revisions" post says AACS 2.0 and 2.1 are independent key-wise and that 2.1 is supported from 1.14.6. Is a normal keydb record (MK / VID / VUK / UK) enough for an AACS 2.1 disc like Fury, or does 2.1 need something more that I do not have, for example working hashed keys? HK download has never worked on my setup, and until now it has not mattered.
MKB_RO.inf is at least 2MB: Yes, 128 MB (copied straight from the disc)
Links verified in incognito: Yes
MKB_RO.inf link: https://drive.google.com/file/d/1QdJWcE ... 6fXwN/view
Disc dump link: No dump exists. MakeMKV did not create one because it treats the key as known. The zip above holds MKB_RO.inf and the disc ID. If a dump would help, tell me how to produce one for a disc MakeMKV thinks it can already open, and I will add it.
Thanks for any help.
Same result: the scan is fine, then it fails 7 seconds after "Saving 1 titles":
The source file '/BDMV/STREAM/00001.fmts' is corrupt or invalid at offset 71454720, attempting to work around
(repeated)
Too many AV synchronization issues in file '/BDMV/STREAM/00001.fmts'
LIBMKV_TRACE: Exception: Error while reading input
0 titles saved, 1 failed
So that is the same offset (71454720) on v2.0.0 and v1.18.4, in two drives, with no SCSI read errors on any attempt.
The same v1.18.4 folder is ripping another UHD (Twister) normally right now, so the install itself is good.
Is there anything else I can collect that would help? I can run a decrypted backup instead of an MKV rip, or post a full debug log, if either is useful.
Cheers
----------------------------------------------------------------------------------------------------------------------------
** NEW Single Drive Flasher ** available worldwide! https://payhip.com/b/MyeJ9
Email: martymcnuts@outlook.com
----------------------------------------------------------------------------------------------------------------------------
** NEW Single Drive Flasher ** available worldwide! https://payhip.com/b/MyeJ9
Email: martymcnuts@outlook.com
-
keydb_helper
- Posts: 1115
- Joined: Fri Sep 06, 2024 4:47 pm
Re: Public KeyDB Disc Submissions
drwh65 wrote: Sat Nov 21, 2026 4:41 pm Disc type: UHD
Disc ID: 0xf39fb2ad8ed2e5deef66023b9c329c1084767dc1
Disc dump filename: MKB20_v82_THE_MAN_WHO_FELL_TO_EARTH_3CDC.tgz
Thanks for the submissions drwh65 and macdev. Your discs have been added to the public keydb.macdev wrote: Sat Nov 21, 2026 10:55 pm Disc type: UHD
Disc ID: 0x8E8E794C75D80CA8417BC855E7A2DD22A8D8F867
Disc dump filename: MKB20_v82_La_La_Land_462A
As MrPenguin and Marty mentioned, the public keydb is not utilised when processing AACS 2.1 titles. It sounds like you have observed a read error and/or a MakeMKV bug.turbov6camaro wrote: Sat Nov 21, 2026 8:49 pm If a dump would help, tell me how to produce one for a disc MakeMKV thinks it can already open, and I will add it.
There is only one error message which can be addressed by disc dump files and the public keydb:
Code: Select all
The volume key is unknown for this disc - video can't be decrypted
Public KeyDB Disc Submissions
KeyDB Lower Priority Disc List
- The MKB_RO.inf file from the original disc is required
- Place the extracted keydb.cfg file in the same directory as your disc dump files
KeyDB Lower Priority Disc List
-
DQduck
- Posts: 9
- Joined: Wed Dec 17, 2025 12:29 pm
Re: Public KeyDB Disc Submissions
Disc type: BD-ROM UHD
Disc ID: 0x3CC63051EDA1EA18AF27659A6B399DED9D9CC4E5
Disc dump filename: I don't have one MakeMKV didn't create one, but the MK is also absent?!?
Drive: BD-RE BU40N
Drive firmware: 1.00 with OmniDrive
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
Is your MKB_RO.inf file size at least 2MB? yes
MKB_RO.inf link: https://workupload.com/file/tLsQ499Xav8
Disc dump link: https://workupload.com/file/uUAYKJSwK8c
Disc ID: 0x3CC63051EDA1EA18AF27659A6B399DED9D9CC4E5
Disc dump filename: I don't have one MakeMKV didn't create one, but the MK is also absent?!?
Drive: BD-RE BU40N
Drive firmware: 1.00 with OmniDrive
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
Is your MKB_RO.inf file size at least 2MB? yes
MKB_RO.inf link: https://workupload.com/file/tLsQ499Xav8
Disc dump link: https://workupload.com/file/uUAYKJSwK8c
Last edited by DQduck on Sun Nov 22, 2026 9:26 pm, edited 1 time in total.
-
keydb_helper
- Posts: 1115
- Joined: Fri Sep 06, 2024 4:47 pm
Re: Public KeyDB Disc Submissions
Hey DQduck, creating a keydb record requires a disc dump file. If MakeMKV didn't create a disc dump file, you can create your own 'synthetic' disc dump file by following the process I outlined here or by using one of SamuriHL's scripts from here.DQduck wrote: Sun Nov 22, 2026 3:44 pm Disc type: BD-ROM UHD
Disc ID: 0x3CC63051EDA1EA18AF27659A6B399DED9D9CC4E5
Disc dump filename: I don't have one MakeMKV didn't create one, but the MK is also absent?!?
Public KeyDB Disc Submissions
KeyDB Lower Priority Disc List
- The MKB_RO.inf file from the original disc is required
- Place the extracted keydb.cfg file in the same directory as your disc dump files
KeyDB Lower Priority Disc List
-
Warbington
- Posts: 25
- Joined: Sat Jul 12, 2025 12:33 am
Synthetic dump
Media Key missing
Disc ID : 0x05B909D37919B3C1F829F5C0D13F09AD53B753F5
Volume : DRACULA_DISC1
Title : Dracula - UHD Disc 1
https://drive.google.com/drive/folders/ ... sp=sharing
Disc ID : 0x05B909D37919B3C1F829F5C0D13F09AD53B753F5
Volume : DRACULA_DISC1
Title : Dracula - UHD Disc 1
https://drive.google.com/drive/folders/ ... sp=sharing
-
DQduck
- Posts: 9
- Joined: Wed Dec 17, 2025 12:29 pm
Re: Public KeyDB Disc Submissions
@keydb_helper have edited my post and added a synthetic disc dump file
-
DQduck
- Posts: 9
- Joined: Wed Dec 17, 2025 12:29 pm
Re: Public KeyDB Disc Submissions
Disc type: UHD
Disc ID: 0xE2AF74AA89A8FA15E251A9FB8457979B370B2641
Disc dump filename:
Drive: BU40N
Drive firmware: 1.00 with OmniDrive 1.0.4
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
Is your MKB_RO.inf file size at least 2MB? yes
MKB_RO.inf link: https://workupload.com/archive/nLXamB2MAM
Disc dump link: https://workupload.com/archive/nLXamB2MAM
MK in DB may be false. I tried by using the MK of the regular blu-ray version for this one and I got to the menu but playback had a lot of artifacts.
Would be great if someone could check if these here are actually correct:
* Media Key: 4741D5B3D2A96AB326FFB2794FDD1352
* Volume ID: A0325CA9C81AD92341412E8BAEAA3D8E
* Volume Unique Key: EE9766A93BE8D40E0C3BFD9B1E7718F3
Disc ID: 0xE2AF74AA89A8FA15E251A9FB8457979B370B2641
Disc dump filename:
Drive: BU40N
Drive firmware: 1.00 with OmniDrive 1.0.4
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
Is your MKB_RO.inf file size at least 2MB? yes
MKB_RO.inf link: https://workupload.com/archive/nLXamB2MAM
Disc dump link: https://workupload.com/archive/nLXamB2MAM
MK in DB may be false. I tried by using the MK of the regular blu-ray version for this one and I got to the menu but playback had a lot of artifacts.
Would be great if someone could check if these here are actually correct:
* Media Key: 4741D5B3D2A96AB326FFB2794FDD1352
* Volume ID: A0325CA9C81AD92341412E8BAEAA3D8E
* Volume Unique Key: EE9766A93BE8D40E0C3BFD9B1E7718F3