verify command validates GameCube and Wii disc images and computes cryptographic hashes for verification and identification.
Usage
Options
Path to the disc image file to verify.Supported formats:
- ISO/GCM
- GCZ
- WIA
- RVZ
- WBFS
Compute and print only the specified hash algorithm, then exit.Available algorithms:
crc32- CRC-32 checksum (fast)md5- MD5 hashsha1- SHA-1 hash (commonly used for disc verification)rchash- RetroAchievements hash (if compiled with RetroAchievements support)
User folder path for temporary processing files.Will be automatically created if not set.
Output Formats
Full Report (No Algorithm Specified)
Without-a, verify outputs a comprehensive report:
Single Hash Output (Algorithm Specified)
With-a, only the hash value is printed:
Examples
Verify Image Integrity
Check for problems and compute all hashes:Compute SHA-1 Hash Only
For Redump verification:Compute CRC32 Checksum
Fast checksum for quick verification:Compute MD5 Hash
Verify with Custom User Directory
Hash Algorithms
CRC32
Use case: Quick integrity checks, error detection- Fast computation
- 32-bit checksum
- Good for detecting corruption
- Not cryptographically secure
MD5
Use case: File identification, legacy compatibility- 128-bit hash
- Widely supported
- Cryptographically broken (use SHA-1 instead)
- Still useful for non-security purposes
SHA-1
Use case: Disc verification, Redump database matching- 160-bit hash
- Standard for disc image verification
- Used by Redump and other preservation databases
- Recommended for verification
RetroAchievements Hash
Use case: RetroAchievements game identification- Specific to RetroAchievements platform
- Only available if compiled with RetroAchievements support
- Used for achievement tracking
Problem Detection
The verifier checks for various issues:Severity Levels
- None - Informational only
- Low - Minor issues, game likely works
- Medium - Potential problems, may affect gameplay
- High - Serious issues, game may not work
Common Problems
- Invalid disc headers
- Corrupted partitions
- Missing or invalid encryption
- Partition table errors
- File system inconsistencies
- Hash mismatches (for signed content)
Verification Workflow
1. Verify After Download
2. Verify After Conversion
3. Compare with Known Hash
Scripting Examples
Verify Multiple Files
Check Against Database
Generate Hash Database
Parallel Verification
Performance
Verification speed depends on:- Storage speed - SSD much faster than HDD
- Image size - Larger files take longer
- Format - Compressed formats (RVZ, GCZ) slower than ISO
- Algorithm - CRC32 fastest, SHA-1 slower
| Format | Size | CRC32 | SHA-1 | Full Report |
|---|---|---|---|---|
| ISO | 4.3 GB | 15s | 25s | 30s |
| RVZ | 1.8 GB | 30s | 45s | 60s |
| GCZ | 2.1 GB | 25s | 40s | 50s |
Exit Codes
0- Success (verification completed)1- Failure (could not verify)
0 means verification completed, not that the image is valid. Check the output for problems.
Troubleshooting
”Unable to open input file”
Check:- File exists and path is correct
- You have read permissions
- File is not corrupted or truncated
”No hash computed”
Occurs when:- Algorithm is not supported
- Image format is invalid
- File is too corrupted to process
Slow Verification
To speed up:- Use CRC32 instead of SHA-1 for quick checks
- Use SSD storage
- Verify ISO instead of compressed formats
Integration with Redump
Redump.org maintains verified disc image databases using SHA-1 hashes.Verify Against Redump Database
-
Compute SHA-1 hash:
- Search hash on Redump.org
- Match confirms authentic dump
See Also
- Convert Command - Format conversion
- Header Command - Inspect metadata
- DolphinTool Overview - Other utilities