Blog | G5 Cyber Security

Verify Disc Burns: Data Integrity Checks

TL;DR

Yes! You can check if a burned disc has copied data correctly using checksums (like MD5, SHA-256) or disc imaging tools. This guide shows you how.

How to Verify Disc Burns: Data Integrity Checks

  1. Understand the Problem
  2. Burning discs isn’t always perfect. Errors can happen, leading to corrupted files. Checking verifies the burn matched the original data.

  3. Checksums – The Quick Method
  4. Checksums create a unique ‘fingerprint’ of your files. Compare the fingerprint before and after burning.

Get-FileHash "pathtoyourfile.iso" -Algorithm MD5

Or for multiple files in a folder:

(Get-ChildItem "pathtoyourfolder" | Get-FileHash -Algorithm MD5).Hash

On Linux/macOS, use the md5sum command:

md5sum path/to/your/file.iso

For SHA-256 (more secure): replace MD5 with SHA256 in the commands above.

  • Step 2: Calculate the Checksum After Burning
  • Repeat Step 1, but this time point it at the files on your burned disc. Make sure to mount the disc first if necessary.

  • Step 3: Compare the Results
  • The checksums *must* match exactly. If they don’t, the burn is faulty and you should try again with a different disc or lower burning speed.

  • Disc Imaging – The More Thorough Method
  • This creates an exact copy of your disc as a single file (an image). You can then verify this image against the original source.

    sudo dd if=/dev/diskX of=disc.iso bs=2048 status=progress

    (Replace /dev/diskX with your disc drive – use lsblk or diskutil list to find it!)

  • Step 2: Verify the Image
  • Calculate the checksum of both the original source data and the created image file (as in Step 1 of the Checksum method). If they match, your image is good.

  • Step 3: Burn from the Verified Image
  • Burn the verified image file to a new disc. This significantly reduces errors compared to burning files directly.

  • Software Recommendations
  • Troubleshooting
  • Exit mobile version