Page 1 of 1

Dump submitted for Wolf Creek

Posted: Tue May 27, 2025 6:46 pm
by murx75
Will soon submit the dumps for Wolf Creek UHD (Turbine)

https://www.mediafire.com/file/35eldlqi ... G.tgz/file
https://www.mediafire.com/file/v1c86h07 ... r.tgz/file

Not sure if I read somewhere that Pioneer dumps would not work, but I created both, one from the LG drive and on from the Pioneer drive. ;-)

Thanks!

Re: Dump submitted for Wolf Creek

Posted: Tue May 27, 2025 7:10 pm
by MrPenguin
murx75 wrote:
Tue May 27, 2025 6:46 pm
Not sure if I read somewhere that Pioneer dumps would not work, but I created both, one from the LG drive and on from the Pioneer drive. ;-)
You read correctly ;). The Powers That KEYDB cannot read some of a TGZ dump file's metadata if that dump was created using a Pioneer drive. Another problem can be if MakeMKV has truncated the AACS/MKB_RO.inf file inside the TGZ dump file to only 56 bytes, which makes it unusable for KEYDB. This other problem can happen with any UHD drive, not just Pioneers. However, sometimes multiple different disks can use the same AACS/MKB_RO.inf file, which means that it might not be insurmountable.

Also, you might find SamuriHL's tool useful.

Re: Dump submitted for Wolf Creek

Posted: Fri May 30, 2025 3:36 pm
by murx75
Was able to backup the disc successfully yesterday evening.

Don't know if it was the KeyDB update that I did or MakeMKV natively.

Thanks to whoever did make it happen! :D

Re: Dump submitted for Wolf Creek

Posted: Fri May 30, 2025 11:19 pm
by MrPenguin
murx75 wrote:
Fri May 30, 2025 3:36 pm
Don't know if it was the KeyDB update that I did or MakeMKV natively.
If you remove the KEYDB.cfg file from your .MakeMKV/ directory, and MakeMKV can still decrypt your disk, then MakeMKV must have added your key to its "hashed keys" database. Otherwise MakeMKV must have decrypted your disk using KEYDB.cfg instead.