public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Damaged CD medium
Date: Mon, 16 Mar 2015 16:26:00 +0000	[thread overview]
Message-ID: <201503161626.18854.michaelkintzios@gmail.com> (raw)
In-Reply-To: <5506ae2a.LukiKjpOj5KWAOWA%Joerg.Schilling@fokus.fraunhofer.de>

[-- Attachment #1: Type: Text/Plain, Size: 3769 bytes --]

On Monday 16 Mar 2015 10:19:22 Joerg Schilling wrote:

> Try to read the man page and use the direct access to the related
> functions.
> 
> From your printout, I cannot even tell whether the device argument was
> correct.
> 
> Start with readcd -scanbus


Thank you Joerg, I had two CD drives in the PC I tried previously.  readcd was 
clever enough to identify the drive with the CD in it, but I specified the 
device on the command line just to be sure, following the man page.

This time I tried using a different PC with a single CD drive:

 # readcd -scanbus
scsibus0:
	0,0,0	  0) 'ATA     ' 'OCZ-ARC100      ' '1.00' Disk
	0,1,0	  1) *
	0,2,0	  2) *
	0,3,0	  3) *
	0,4,0	  4) *
	0,5,0	  5) *
	0,6,0	  6) *
	0,7,0	  7) *
scsibus1:
	1,0,0	100) 'ATA     ' 'WDC WD30EFRX-68E' '0A82' Disk
	1,1,0	101) *
	1,2,0	102) *
	1,3,0	103) *
	1,4,0	104) *
	1,5,0	105) *
	1,6,0	106) *
	1,7,0	107) *
scsibus2:
	2,0,0	200) 'PIONEER ' 'BD-RW   BDR-209D' '1.10' Removable CD-ROM
	2,1,0	201) *
	2,2,0	202) *
	2,3,0	203) *
	2,4,0	204) *
	2,5,0	205) *
	2,6,0	206) *
	2,7,0	207) *


> If you continue with readcd dev=xxx (only needed at all if you have more
> than one CD like drive), you could e.g. try readcd f=out-file -noerror
> 
> If your drive cannot read the toc or otherwise believes there is no medium,
> readcd cannot help. You need to check why the toc cannot be read. If the CD
> ic scratched, then try to use Plexiglass polishing paste. Be carefull to
> prevent polishing paste to slip to the paint side and to let the CD move
> on the paint side.
> 
> Jörg


Running 'readcd f=cd_test.out -noerror' gives me an ever increasing number of 
errors, on each sector (currently up to sector 6 and still going strong):

# readcd f=cd_test.out -noerror
No target specified, trying to find one...
Using dev=2,0,0.
Read  speed: 22160 kB/s (CD 125x, DVD 16x, BD  4x).
Write speed: 22160 kB/s (CD 125x, DVD 16x, BD  4x).
Capacity: 250000 Blocks = 500000 kBytes = 488 MBytes = 512 prMB
Sectorsize: 2048 Bytes
Copy from SCSI (2,0,0) disk to file 'cd_test.out'
end:    250000
readcd: Input/output error. read_g1: scsi sendcmd: no error
CDB:  28 00 00 00 00 00 00 00 40 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: F0 00 03 00 00 00 00 0E 00 00 00 00 11 05 00 00
Sense Key: 0x3 Medium Error, Segment 0
Sense Code: 0x11 Qual 0x05 (l-ec uncorrectable error) Fru 0x0
Sense flags: Blk 0 (valid) 
cmd finished after 7.030s timeout 40s
readcd: Input/output error. Cannot read source disk
readcd: Retrying from sector 0.
.~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-
~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~
readcd: Input/output error. Error on sector 0 not corrected. Total of 1 
errors.
readcd: -noerror set, continuing ...
.~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-
~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~
readcd: Input/output error. Error on sector 1 not corrected. Total of 2 
errors.
readcd: -noerror set, continuing ...
.~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-
~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~
readcd: Input/output error. Error on sector 2 not corrected. Total of 3 
errors.
readcd: -noerror set, continuing ...
.~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-
~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~
[snip ...]


There are no visible scratches on the disk, so I am thinking this is not a 
mechanical fault, but something to do with the burner.  I am glad that I 
learned about readcd, but given the above results shall I give up hope and ask 
the guy to burn me a new CD using a different burner this time?

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2015-03-16 16:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13 16:30 [gentoo-user] Damaged CD medium Mick
2015-03-13 16:56 ` David W Noon
2015-03-13 17:10 ` wabenbau
2015-03-13 17:37   ` Mick
2015-03-13 17:54 ` [gentoo-user] " Grant Edwards
2015-03-13 17:55   ` Joerg Schilling
2015-03-13 22:24   ` Neil Bothwick
2015-03-14  0:24     ` Mick
2015-03-14  7:56       ` Mick
2015-03-16 10:20         ` Joerg Schilling
2015-03-16 10:19       ` Joerg Schilling
2015-03-16 16:26         ` Mick [this message]
2015-03-16 16:51           ` Joerg Schilling
2015-03-16 20:05             ` Mick
2015-03-17 16:40               ` Mick
2015-03-19 10:41                 ` Joerg Schilling
2015-03-19 10:28               ` Joerg Schilling
2015-03-13 17:59 ` [gentoo-user] " Fernando Rodriguez

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=201503161626.18854.michaelkintzios@gmail.com \
    --to=michaelkintzios@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