public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Davyd McColl <davydm@gmail.com>
To: <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Software for checking CDs and DVDs for errors?
Date: Tue, 04 Dec 2018 06:16:42 +0200	[thread overview]
Message-ID: <167776eb010.278f.83c5c26c404a765ed2e55e3ab0c1c65d@gmail.com> (raw)
In-Reply-To: <RBEGE7SI.SLDTPXEJ.UDEFWZXV@AF2RF5Q4.B42AYBYM.WJ2CMCCU>



On December 3, 2018 11:32:46 PM Jack <ostroffjh@users.sourceforge.net> wrote:

> On 2018.12.03 11:27, Pouru Lasse wrote:
>> I've got a bunch of scratched disc-based games (PS2, Xbox 360) that
>> I'd
>> like to check for errors. Is there any program for Linux that does
>> this?
>> I found and tried dvdisaster, but it only works for CDs, not
>> DVDs. Everything else seems to be Windows-only.
>
> I have not installed dvdisaster, but I'd be really surprised if it
> won't check dvd's.  The ebuild description is "Tool for creating error
> correction data (ecc) for optical media (DVD, CD, BD)" so if it really
> balks at a dvd, I'd file a bug.
>
> Also - what is your criteria for finding an error?  Could you just read
> the entire disk or copy to /dev/null and just look for any read
> errors?  (I'm not sure if I'd try cp or dd or some variant on dd.)
>
> Jack

Not so much just for verification, but I'd also check out ddrescue. If the 
tool dumps your media easily, it's probably good. If it struggles, you may 
at least still have a workable image by the time it is done.

IIRC, some game discs may also throw a curve-ball here: they had 
intentional errors introduced near the end of the disc to prevent image 
dumping for copy protection. I'm sure I ran across a ps2 game or two like this.

-d




  parent reply	other threads:[~2018-12-04  4:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-03 16:27 [gentoo-user] Software for checking CDs and DVDs for errors? Pouru Lasse
2018-12-03 18:31 ` Francesco Turco
2018-12-04 10:28   ` Joerg Schilling
2018-12-03 21:32 ` Jack
2018-12-03 22:50   ` Dale
2018-12-04  2:16     ` Andrew Udvare
2018-12-04  2:47       ` Dale
2018-12-04  7:51         ` Pouru Lasse
2018-12-04 18:48           ` Jack
2018-12-04 10:31         ` Joerg Schilling
2018-12-20 17:19           ` Steve Dibb
2018-12-20 17:26             ` Joerg Schilling
2018-12-04 10:39       ` Joerg Schilling
2018-12-04  4:16   ` Davyd McColl [this message]
2018-12-04  5:21     ` Andrew Udvare
2018-12-04 10:27 ` Joerg Schilling
2018-12-13 23:29 ` Steve Dibb
2018-12-14 10:31   ` Joerg Schilling
2018-12-20 17:10     ` Steve Dibb
2018-12-20 17:12       ` Joerg Schilling

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=167776eb010.278f.83c5c26c404a765ed2e55e3ab0c1c65d@gmail.com \
    --to=davydm@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox