Is it possible for a Content Hash Table to be corrupt?

Please post here for issues related to Blu-ray discs
Post Reply
Message
Author
Radiocomms237
Posts: 405
Joined: Mon Oct 18, 2021 12:23 am

Is it possible for a Content Hash Table to be corrupt?

#1 Post by Radiocomms237 » Sat Apr 08, 2023 3:07 am

As the title says, is it possible for a Content Hash Table to be corrupt?

I'm ripping the Jack Irish TV Series and all was going well until I reached S3D1...

Code: Select all

Using LibreDrive mode (v01.0 id=FCF253697C55)
Backing up disc into folder "P:/TV Shows - In Progress/Jack Irish franchise/FULL DISC BACKUP(S)/JACK_IRISH_SEASON_3_DISC_1"
Downloading latest HK to P:/VideoPad Cache ...
Loaded content hash table, will verify integrity of M2TS files.
Hash check failed for file 00004.m2ts at offset 190464, file is corrupt.
Hash check failed for file 00004.m2ts at offset 387072, file is corrupt.
Hash check for /BDMV/STREAM/00004.m2ts : 86.48% corrupt, 0% correct, 86.48% checked.
Hash check failed for file 00009.m2ts at offset 190464, file is corrupt.
Hash check failed for file 00009.m2ts at offset 387072, file is corrupt.
Hash check failed for file 00009.m2ts at offset 583680, file is corrupt.
Hash check failed for file 00009.m2ts at offset 780288, file is corrupt.
Hash check failed for file 00009.m2ts at offset 976896, file is corrupt.
Too many hash check errors in file 00009.m2ts.
Hash check for /BDMV/STREAM/00009.m2ts : 97.32% corrupt, 0% correct, 97.32% checked.
Hash check failed for file 00008.m2ts at offset 190464, file is corrupt.
Hash check failed for file 00008.m2ts at offset 387072, file is corrupt.
Hash check failed for file 00008.m2ts at offset 583680, file is corrupt.
Hash check failed for file 00008.m2ts at offset 780288, file is corrupt.
Hash check failed for file 00008.m2ts at offset 976896, file is corrupt.
Too many hash check errors in file 00008.m2ts.
Hash check for /BDMV/STREAM/00008.m2ts : 99.49% corrupt, 0% correct, 99.49% checked.
Hash check failed for file 00022.m2ts at offset 190464, file is corrupt.
Hash check failed for file 00022.m2ts at offset 387072, file is corrupt.
Hash check failed for file 00022.m2ts at offset 583680, file is corrupt.
Hash check failed for file 00022.m2ts at offset 780288, file is corrupt.
Hash check failed for file 00022.m2ts at offset 976896, file is corrupt.
Too many hash check errors in file 00022.m2ts.
Hash check for /BDMV/STREAM/00022.m2ts : 99.87% corrupt, 0% correct, 99.87% checked.
Hash check failed for file 00021.m2ts at offset 190464, file is corrupt.
Hash check failed for file 00021.m2ts at offset 387072, file is corrupt.
Hash check failed for file 00021.m2ts at offset 583680, file is corrupt.
Hash check failed for file 00021.m2ts at offset 780288, file is corrupt.
Hash check failed for file 00021.m2ts at offset 976896, file is corrupt.
Too many hash check errors in file 00021.m2ts.
Hash check for /BDMV/STREAM/00021.m2ts : 99.94% corrupt, 0% correct, 99.94% checked.
Hash check failed for file 00020.m2ts at offset 190464, file is corrupt.
Hash check failed for file 00020.m2ts at offset 387072, file is corrupt.
Hash check failed for file 00020.m2ts at offset 583680, file is corrupt.
Hash check failed for file 00020.m2ts at offset 780288, file is corrupt.
Hash check failed for file 00020.m2ts at offset 976896, file is corrupt.
Too many hash check errors in file 00020.m2ts.
Hash check for /BDMV/STREAM/00020.m2ts : 99.94% corrupt, 0% correct, 99.94% checked.
Hash check failed for file 00001.m2ts at offset 190464, file is corrupt.
Hash check failed for file 00001.m2ts at offset 387072, file is corrupt.
Hash check failed for file 00001.m2ts at offset 583680, file is corrupt.
Hash check failed for file 00001.m2ts at offset 780288, file is corrupt.
Hash check failed for file 00001.m2ts at offset 976896, file is corrupt.
Too many hash check errors in file 00001.m2ts.
Hash check for /BDMV/STREAM/00001.m2ts : 95.63% corrupt, 0% correct, 95.63% checked.
Hash check failed for file 00006.m2ts at offset 190464, file is corrupt.
Hash check failed for file 00006.m2ts at offset 387072, file is corrupt.
Hash check failed for file 00006.m2ts at offset 583680, file is corrupt.
Hash check failed for file 00006.m2ts at offset 780288, file is corrupt.
Hash check failed for file 00006.m2ts at offset 976896, file is corrupt.
Too many hash check errors in file 00006.m2ts.
Hash check for /BDMV/STREAM/00006.m2ts : 96.70% corrupt, 0% correct, 96.70% checked.
Hash check failed for file 00010.m2ts at offset 190464, file is corrupt.
Hash check failed for file 00010.m2ts at offset 387072, file is corrupt.
Hash check failed for file 00010.m2ts at offset 583680, file is corrupt.
Hash check failed for file 00010.m2ts at offset 780288, file is corrupt.
Hash check failed for file 00010.m2ts at offset 976896, file is corrupt.
Too many hash check errors in file 00010.m2ts.
Hash check for /BDMV/STREAM/00010.m2ts : 96.70% corrupt, 0% correct, 96.70% checked.
Hash check failed for file 00005.m2ts at offset 190464, file is corrupt.
Hash check failed for file 00005.m2ts at offset 387072, file is corrupt.
Hash check failed for file 00005.m2ts at offset 583680, file is corrupt.
Hash check failed for file 00005.m2ts at offset 780288, file is corrupt.
Hash check failed for file 00005.m2ts at offset 976896, file is corrupt.
Too many hash check errors in file 00005.m2ts.
Hash check for /BDMV/STREAM/00005.m2ts : 99.99% corrupt, 0% correct, 99.99% checked.
Hash check failed for file 00002.m2ts at offset 190464, file is corrupt.
Hash check failed for file 00002.m2ts at offset 387072, file is corrupt.
Hash check failed for file 00002.m2ts at offset 583680, file is corrupt.
Hash check failed for file 00002.m2ts at offset 780288, file is corrupt.
Hash check failed for file 00002.m2ts at offset 976896, file is corrupt.
Too many hash check errors in file 00002.m2ts.
Hash check for /BDMV/STREAM/00002.m2ts : 99.99% corrupt, 0% correct, 99.99% checked.
Hash check failed for file 00011.m2ts at offset 190464, file is corrupt.
Hash check failed for file 00011.m2ts at offset 387072, file is corrupt.
Hash check failed for file 00011.m2ts at offset 583680, file is corrupt.
Hash check failed for file 00011.m2ts at offset 780288, file is corrupt.
Hash check failed for file 00011.m2ts at offset 976896, file is corrupt.
Too many hash check errors in file 00011.m2ts.
Hash check for /BDMV/STREAM/00011.m2ts : 99.99% corrupt, 0% correct, 99.99% checked.
Encountered 179576 errors of type 'HashCheck Error' - see http://www.makemkv.com/errors/hashcheck/...
Backup done but 12 files failed hash check
What does "Downloading latest HK" mean, I don't think I've ever seen that before, but it seems to have screwed everything up?

dcoke22
Posts: 3060
Joined: Wed Jul 22, 2020 11:25 pm

Re: Is it possible for a Content Hash Table to be corrupt?

#2 Post by dcoke22 » Sat Apr 08, 2023 2:04 pm

Radiocomms237 wrote:
Sat Apr 08, 2023 3:07 am
What does "Downloading latest HK" mean, I don't think I've ever seen that before, but it seems to have screwed everything up?
4K UHDs are decrypted using a set of downloaded 'hashed keys'. MakeMKV checks for an updated list of keys and downloads them in the background automatically.

Fixing Volume Key is Unknown

That process is unrelated to your disc's hash check errors. Try gently cleaning the disc.

Radiocomms237
Posts: 405
Joined: Mon Oct 18, 2021 12:23 am

Re: Is it possible for a Content Hash Table to be corrupt?

#3 Post by Radiocomms237 » Sat Apr 08, 2023 10:21 pm

Thanks. Yes, I tried "gently" cleaning the disc and it made no difference, I guess I'll try not-so-gently cleaning it with some white vinegar and see if anything changes.

It's just that I've ripped thousands of discs and I've never seen one before with hash errors in EVERY SINGLE FILE!

dcoke22
Posts: 3060
Joined: Wed Jul 22, 2020 11:25 pm

Re: Is it possible for a Content Hash Table to be corrupt?

#4 Post by dcoke22 » Sat Apr 08, 2023 10:36 pm

i prefer liquid dish soap and plenty of water for cleaning discs. If there's a film or oil on the disc, the dish soap seems to do a good job removing it. I dry the data side of the disc with a can of air.

It is certainly possible there's a problem with that disc's content hash table. Users occasionally report discs with mastering errors on this forum. But looking at the entry on blu-ray.com (https://www.blu-ray.com/movies/Jack-Iri ... ay/299094/) I don't see a forum discussion about a bad batch of discs. I also didn't notice a bunch of complaints about bad discs in a quick scan of the Amazon.com comments.

Radiocomms237
Posts: 405
Joined: Mon Oct 18, 2021 12:23 am

Re: Is it possible for a Content Hash Table to be corrupt?

#5 Post by Radiocomms237 » Sat Apr 08, 2023 10:53 pm

Looking in the (decrypted) backed-up folder, under MAKEMKV/AACS/, there are two distinct content hash tables ("ContentHash000.tbl" & "ContentHash001.tbl") and I've CRC'd both of them with their counterparts in the MAKEMKV/AACS/DUPLICATE/ folder and both are identical, respectively.

So I doubt the hash table is actually corrupt, unless, as you say, it's a mastering problem. I wonder why there are two very different hash tables (one is a fair bit bigger than the other)?

I suppose it's just a damaged disc?

Thanks again!

dcoke22
Posts: 3060
Joined: Wed Jul 22, 2020 11:25 pm

Re: Is it possible for a Content Hash Table to be corrupt?

#6 Post by dcoke22 » Mon Oct 16, 2023 4:06 am

On blu-rays, the content hash tables are per layer. Your disc in question must've been a dual layer disc.

https://aacsla.com/wp-content/uploads/2 ... ed.921.pdf

See section 2.3.1 on page 8.

Krawk
Posts: 276
Joined: Thu Jul 02, 2015 12:10 am

Re: Is it possible for a Content Hash Table to be corrupt?

#7 Post by Krawk » Sat Oct 28, 2023 10:50 pm

CSI: Season 1 has corrupt hash tables.

dcoke22
Posts: 3060
Joined: Wed Jul 22, 2020 11:25 pm

Re: Is it possible for a Content Hash Table to be corrupt?

#8 Post by dcoke22 » Sun Oct 29, 2023 3:20 pm

Krawk wrote:
Sat Oct 28, 2023 10:50 pm
CSI: Season 1 has corrupt hash tables.
Out of curiosity, how do you know?

Post Reply