CleanRip always giving bad rips

[einsteinsci]

For some reason, I always get bad rips of discs from CleanRip on my Wii. CleanRip says the MD5 is verified, but when I verify the same checksum on my computer, I get a completely different checksum, and sure enough, I reach a spot in the game where it always will freeze (and dolphin verifying the partition integrity will always have trouble on one of the partitions). While most games are still playable (Brawl), other games (Sonic Colors, Super Mario Galaxy) freeze somewhere towards the beginning of the game. I've tried updating to CleanRip 2.0.0, with the same freeze occuring in SMG (intro clip). The CleanRip ZIP had the same SHA1 checksum from the site. I've formatted my USB as NTFS (Quick format is OFF) so that I don't have the file split into chunks. Where do I go from here?

[Shonumi]

Your discs may be in bad condition, or the disk drive in your Wii may be malfunctioning to some extent. Can you give us an example MD5 hash from a Wii game? Which games (list all that you can remember) have you tried dumping in CleanRip?

[tueidj]

If cleanrip says the MD5 is verified, the disc was read correctly (it's almost impossible to get a bad rip regardless; the drive returns errors for bad reads) and the issue is something to do with how the image data is being written. I would suggest not using NTFS and/or using a different USB drive.

[einsteinsci]

(11-16-2014, 09:47 AM)Shonumi Wrote: Your discs may be in bad condition, or the disk drive in your Wii may be malfunctioning to some extent. Can you give us an example MD5 hash from a Wii game? Which games (list all that you can remember) have you tried dumping in CleanRip?

Some games are mostly playable, like Brawl and Super Paper Mario. Super Mario Galaxy, when I last ripped it, was said to have an MD5 of F99A97F9AE4DCCD1DB45E9AAAB9CEBD8. When I scanned it with an MD5 hasher, I got 330364134EA67BD52740343BEDA30D7C. My discs are working just fine on the Wii itself. It's in dolphin that the games freeze.

(11-16-2014, 10:06 AM)tueidj Wrote: If cleanrip says the MD5 is verified, the disc was read correctly (it's almost impossible to get a bad rip regardless; the drive returns errors for bad reads) and the issue is something to do with how the image data is being written. I would suggest not using NTFS and/or using a different USB drive.

I will try FAT32 again. I switched to NTFS because CleanRip would always stop in the middle, with no message or anything. That was before I updated to 2.0.0.

[tueidj]

When you hash them with the PC is the ISO still on the USB drive or do you copy it from the USB to the hard drive first? It's possible for large files to be corrupted while copying if you have faulty RAM (and also possible for non-corrupted files to appear corrupted).

[einsteinsci]

(11-16-2014, 11:06 AM)tueidj Wrote: When you hash them with the PC is the ISO still on the USB drive or do you copy it from the USB to the hard drive first? It's possible for large files to be corrupted while copying if you have faulty RAM (and also possible for non-corrupted files to appear corrupted).

I thought about that. I hashed the file both before it was copied, and after. In both instances the checksum is wrong (and the same), so thankfully it's not my RAM.

I got a write error when I tried with FAT32 on MAX chunk size. I've kind of hit a dead end here. Is there an alternative to CleanRip I can try?

[JMC47]

make the chunks 3GB and join them on your PC.

[tueidj]

The latest version doesn't do that, it knows not to use chunks larger than 4GB on FAT32.

[einsteinsci]

If I do use chunks, how do I join them together to a single ISO?

[JMC47]

go into command prompt, "COPY /b iso.part1+iso.part2 Fullisoname.iso"