public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joerg Schilling <Joerg.Schilling@fokus.fraunhofer.de>
To: <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Software for checking CDs and DVDs for errors?
Date: Fri, 14 Dec 2018 11:31:01 +0100	[thread overview]
Message-ID: <5c138665.gRZr7EA3clfDJjMT%Joerg.Schilling@fokus.fraunhofer.de> (raw)
In-Reply-To: <9f7a8ff6-d431-1deb-132c-f6e78ff4cfa9@gentoo.org>

Steve Dibb <beandog@gentoo.org> wrote:

> On 12/3/18 9:27 AM, 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.
> >
> > - Lasse
> >
>
> For DVDs, I use ddrescue. Keep a log of it as well in case you want to 
> do a second pass or just see where it's puking. Use its blocksize of 2048:
>
> ddrescue -b 2048 /dev/sr0 dvd.iso ddrescue.log

readcd is better for any optical media as it is able to directly send SCSI 
commands. Note that readcd implements the error recovery from sdd(1), that 
exists since 35 years and I also prefer for normal disks.

With software that operates at block driver level, you depend on the error 
recovery features from the OS driver.

Use the options -noerror and retries= (the latter makes sense with a retry 
count > 128 as 128 is the default) and set up a low read speed as this reduces 
media flitting.

Jörg

-- 
 EMail:joerg@schily.net                    (home) Jörg Schilling D-13353 Berlin
    joerg.schilling@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
 URL: http://cdrecord.org/private/ http://sf.net/projects/schilytools/files/'


  reply	other threads:[~2018-12-14 10:31 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
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 [this message]
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=5c138665.gRZr7EA3clfDJjMT%Joerg.Schilling@fokus.fraunhofer.de \
    --to=joerg.schilling@fokus.fraunhofer.de \
    --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