Resolved - Different hashes for the same disc

[DeepSpace]

As promted, I create a new thread for it.

List of UHDs currently UN-supported in AnyDVD

Weird, the new hash is d7a405cfdd45ba103e14595f173f83a2. Is that due to a difference in the new update or is indeed something wrong? Maybe you can see it in the OPD already, if AnyDVD sends enough information. Maybe I just confused everything after dealing with so many different files.

forum.redfox.bz

You should open a new troubleshooting thread, with logfiles and the whole story...

True, but there is no story. I just ripped it three times by now, with three different hashes inside the .md5 files (opened them via Editor, maybe it is not able to open them properly? But no error.). The UHD .iso is playable, (except the menu but VLC seems to have issues with all of the discs even so Java is installed), so everything should be fine. I am just curious why the hashes are different then.
Because if it successfully ripped the same disc twice, it should give me two identical hashes, or not?

The logfiles all have the same hash stuff added to the filename and AnyDVD does not complain about a corrupted .iso.

Hash .iso 1 Sherlock 1: (on my 16TB drive)
afc828e99cdda1bb582493a614eb1e66

Hash .iso 2 Sherlock 1: (on the Laptop SSD)
a7a1235b463cb0c283d000c3de1d351f

Hash .iso 3 Sherlock 1: (on my Archive drive)
d7a405cfdd45ba103e14595f173f83a2

Also, I accidentally ripped the BD twice as I had an empty folder on one drive. Seems I just copied it there and forgot that I already ripped it or whatever. But they also have different hashes.
Hash BD (Archive)
82df4b55acf0043b1c83b833b74aff93

Hash BD (Laptop SSD)
aeb4a8eb6c95e7f9e139949e54b99ef6




When I tried to scan the original disc again to give you a log to compare to, I catched the LibreDrive issue and AnyDVD successfully complained about it! Thank you very much for adding this!

ERROR: LibreDrive bus decryption failed! Please reinsert disc!

I added the logfile from it in case there is more information about the issue now in the new version. But it just says that LibreDrive is not supported with this drive, as it did before. So I hope there is more information for you in other files.


However, it now entirely refuses to scan the disc, even when I unplugged it. Guess I have to reboot my PC.
So I attached a working log from an older version. Hope it is enough.

 

[James]

Unfortunately there is not much to see in the logs.
You can run a file compare

cmd.exe
fc /b file1.iso file2.iso

to check how much and where the files differ.

Does AnyDVD complain about verify errors, if you create an unprotected iso?

 

[James]

Another question: Did you create the isos with the "sparse" option checked or unchecked?

 

[DeepSpace]

You can run a file compare

I will do that, not sure if today.

Does AnyDVD complain about verify errors, if you create an unprotected iso?

I haven't tried that, will do so as well.

Did you create the isos with the "sparse" option checked or unchecked?

I never used it. I tried it once many years ago to see what happens but the size was the same so I ditched it. Also, I want to have a 1:1 copy anyways.

 

[James]

I never used it.

Good, one thing to rule out.

Also, I want to have a 1:1 copy anyways.

The content of the file is (should) be the same, sparse is 1:1, too.

 

[DeepSpace]

I currently fc them and it looks to be different.
This is the current progress, I will post the rest when it's done.

00000006FF4A9FF6: BB 71
00000006FF4A9FF7: 3B 36
00000006FF4A9FF8: E6 E7
00000006FF4A9FF9: F0 72
00000006FF4A9FFA: 54 78
00000006FF4A9FFB: 72 08
00000006FF4A9FFC: 73 8A
00000006FF4A9FFD: F7 19
00000006FF4A9FFE: DF 7B
00000006FF4A9FFF: 64 04

 

[DeepSpace]

Well, it appears the cmd couldn't hold all these lines, so I need to do it again and set output to a .txt file.
Unless you say these few lines are enough.

I could start an unprotected copy from both the Laptop SSD .iso and the Archive HDD .iso without AnyDVD complaining. But I cancelled it after 2 or 3% since I don't need it. And both are playable when mounted and decrypted by AnyDVD.

 

[DrXenos]

This is just a guess, but do the ISOs contain headers with time/date information, or do any of the files contained within? If so, the hashes will never been equivalent.

 

[James]

This is just a guess, but do the ISOs contain headers with time/date information, or do any of the files contained within? If so, the hashes will never been equivalent.

On a protected iso no, I don't think so.

 

[ryley]

The UHD .iso is playable, (except the menu but VLC seems to have issues with all of the discs even so Java is installed), so everything should be fine. I am just curious why the hashes are different then.
Because if it successfully ripped the same disc twice, it should give me two identical hashes, or not?

The user Rupan posted a Python script a few years ago which validates the content of Blu-ray discs (both UHD and regular). It might be worth using this to determine which, if any, of your similar-ish ISO files is entirely correct according to the AACS content hash information.

For what it is worth, the only time I can recall getting different ISO files for the same disc was when my cross-flashed BH16NS55 returned all zeroes for some problematic sectors on one or two discs. The location was consistent and the bad output was never non-zero.

 

[DeepSpace]

I will try it out later that day. Hope it works as it didn't for the OP

It didn't work for me on Windows when I tried it

 

[James]

I currently fc them and it looks to be different.
This is the current progress, I will post the rest when it's done.

00000006FF4A9FF6: BB 71
00000006FF4A9FF7: 3B 36
00000006FF4A9FF8: E6 E7
00000006FF4A9FF9: F0 72
00000006FF4A9FFA: 54 78
00000006FF4A9FFB: 72 08
00000006FF4A9FFC: 73 8A
00000006FF4A9FFD: F7 19
00000006FF4A9FFE: DF 7B
00000006FF4A9FFF: 64 04

This is inside the main movie stream 00004.m2ts. It would be interesting to see, if AnyDVD complains if you create an unprotected iso from the protected isos.

 

[DeepSpace]

It would be interesting to see, if AnyDVD complains if you create an unprotected iso from the protected isos.

I could start an unprotected copy from both the Laptop SSD .iso and the Archive HDD .iso without AnyDVD complaining. But I cancelled it after 2 or 3% since I don't need it. And both are playable when mounted and decrypted by AnyDVD.

 

[DeepSpace]

The user Rupan posted a Python script a few years ago

When I open python, give it the path to the script and then paste the two paths to the two images, it gives me

SyntaxError: (unicode error) 'unicodeescape' codec can't decode bytes in position 2-3: truncated \UXXXXXXXX escape

In other words:
Path/script.py (Enter)
"path1.iso" "path2.iso" (Enter)

 

[James]

But I cancelled it after 2 or 3% since I don't need it.

?

 

[DeepSpace]

?

I don't need the output and AnyDVD did not complain when I started the copy so I cancelled it. Or do you need to know if the copy would run entirely till 100%, because AnyDVD could also complain in the middle and not just directly at the beginning?

 

[James]

Or do you need to know if the copy would run entirely till 100%, because AnyDVD could also complain in the middle and not just directly at the beginning?

Yes.

 

[DeepSpace]

And you were right. (Laptop SSD .iso)


Edit: The content of the .txt file that opened at the end.

Lesefehler auf Laufwerk F:!
Verify Error Sectors: 2602455-2602469
Verify Error Sectors: 2602470-2602484
Verify Error Sectors: 6729165-6729179
Verify Error Sectors: 6729180-6729194
Verify Error Sectors: 14674245-14674259
Verify Error Sectors: 14674260-14674274
Verify Error Sectors: 29225595-29225609
Verify Error Sectors: 29225610-29225624

 

[James]

And you were right. (Laptop SSD .iso)
View attachment 75117

Edit: The content of the .txt file that opened at the end.

Lesefehler auf Laufwerk F:!
Verify Error Sectors: 2602455-2602469
Verify Error Sectors: 2602470-2602484
Verify Error Sectors: 6729165-6729179
Verify Error Sectors: 6729180-6729194
Verify Error Sectors: 14674245-14674259
Verify Error Sectors: 14674260-14674274
Verify Error Sectors: 29225595-29225609
Verify Error Sectors: 29225610-29225624

Now you know the image is corrupt. The question "why?" remains unanswered.
Now you can check the other isos...

 

[DeepSpace]

The question "why?" remains unanswered.

I think it is the cable, which could also explain why the LibreDrive issue that has been fixed now occured in the first place. I mean it is a good thing because you could improve AnyDVD by it, but for me it's bad because it potentially means that all .isos ever created using the Pioneer are corrupt.
To verify if it is the cable, I currently re-rip the disc using the BU40N inside my laptop twice (to compare these hashes against each other) and then a third time using the Pioneer with another cable to see what hash that will give me. I haven't told you yet since I wanted to wait till these are done. I am currently on the second .iso with BU40N, then I do the third with Pioneer and other cable.

I already created an unprotected .iso from the first BU40N rip and AnyDVD did not complain (and of course, got another has again, starting with 4c). But as said, I haven't informed you about this yet as I wanted to wait until the other rips are done so I can verify it.


Regardless what the issue is, is there a way for AnyDVD to identify if these .isos are corrupt (without the need to copy the disc again or create an unprotected .iso, maybe just virtually copying the .iso to RAM or trying to read it to check the data but not actually saving it anywhere to not waste my drives)? Because it did not complain until I copied the .iso to unprotected as you wanted. It only complained about the .iso of Sherlock 2 UHD. Or is there another tool that I could now scan the .isos and then let it scan the discs to compare the hashes, but without copying anything? It would be sad if I need to re-rip all discs, because even though I made screenshots, they are everywhere and I have no clue which of the four drives I used for which disc. The new screenshot tool adds the program name to the filename, so I can just search the folder for all AnyDVD screenshots, but I only use it for a certain time and had another that only saved the current date and time into the filename. So there is no way I can ever search all AnyDVD screenshots there.
Or doesn't it make any sense, since scanning the entire disc might take the same time than just ripping it a second time? And then I can just compare the hashes to see if the first one is valid or not.

That reminds me of a feature request I never posted: In addition to the other stuff, could AnyDVD also save the program version and the drive name + FW the disc has been ripped with?
For example:
Asus BW-16D1HT (3.10 (+if MK?) )
Pioneer UD04 (1.11)
AnyDVD 8.6.6.7

That way I could now just look into the .dvd files of each .iso and pick out all discs I ripped using the Pioneer.