[gentoo-user] Damaged CD medium

[Mick]

Hi All,

I was given a CD with some pictures, but I am not able to mount it. This is
what dmesg reveals:

[ 7791.880206] sr 1:0:0:0: [sr0]
[ 7791.880211] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 7791.880215] sr 1:0:0:0: [sr0]
[ 7791.880217] Sense Key : Hardware Error [current]
[ 7791.880224] sr 1:0:0:0: [sr0]
[ 7791.880229] Add. Sense: Timeout on logical unit
[ 7791.880233] sr 1:0:0:0: [sr0] CDB:
[ 7791.880236] Read(10): 28 00 00 00 00 00 00 00 02 00
[ 7791.880252] blk_update_request: I/O error, dev sr0, sector 0
[ 7800.424417] sr 1:0:0:0: [sr0]
[ 7800.424422] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 7800.424427] sr 1:0:0:0: [sr0]
[ 7800.424429] Sense Key : Hardware Error [current]
[ 7800.424436] sr 1:0:0:0: [sr0]
[ 7800.424440] Add. Sense: Timeout on logical unit
[ 7800.424445] sr 1:0:0:0: [sr0] CDB:
[ 7800.424447] Read(10): 28 00 00 00 00 00 00 00 02 00
[ 7800.424463] blk_update_request: I/O error, dev sr0, sector 0
[ 7800.424468] Buffer I/O error on dev sr0, logical block 0, async page read
[ 7809.051719] sr 1:0:0:0: [sr0]
[ 7809.051725] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 7809.051729] sr 1:0:0:0: [sr0]
[ 7809.051731] Sense Key : Hardware Error [current]
[ 7809.051738] sr 1:0:0:0: [sr0]
[ 7809.051743] Add. Sense: Timeout on logical unit
[ 7809.051748] sr 1:0:0:0: [sr0] CDB:
[ 7809.051750] Read(10): 28 00 00 00 00 00 00 00 02 00
[ 7809.051766] blk_update_request: I/O error, dev sr0, sector 0
[ 7809.051771] Buffer I/O error on dev sr0, logical block 0, async page read
[ 7817.681141] sr 1:0:0:0: [sr0]
[ 7817.681146] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 7817.681150] sr 1:0:0:0: [sr0]
[ 7817.681152] Sense Key : Hardware Error [current]
[ 7817.681159] sr 1:0:0:0: [sr0]
[ 7817.681164] Add. Sense: Timeout on logical unit
[ 7817.681168] sr 1:0:0:0: [sr0] CDB:
[ 7817.681170] Read(10): 28 00 00 00 00 00 00 00 02 00
[ 7817.681187] blk_update_request: I/O error, dev sr0, sector 0
[ 7817.681192] Buffer I/O error on dev sr0, logical block 0, async page read


I tried on different PCs and I am getting the same error. Shall I forget
about it, or is there some means by which I can recover the files on it?

--
Regards,
Mick

[David W Noon]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, 13 Mar 2015 16:30:59 +0000, Mick (michael...@gmail.com)
wrote about "[gentoo-user] Damaged CD medium" (in
<201503131631.0286...@gmail.com>):

[snip]

> I tried on different PCs and I am getting the same error. Shall I
> forget about it, or is there some means by which I can recover the
> files on it?

I bought a CD/DVD cleaner from Maplins a few years ago and it recovers
damaged discs quite nicely. It uses an abrasive to clean and polish
the surface, so it can be used only a limited number of times on any
given disc -- it will eventually grind through the plastic to the foil.

The nearest I could find on the Web, also from Maplins, was this:

<http://www.maplin.co.uk/p/cddvd-cleaner-and-restorer-polish-qm13p>

It's visually different from the one I bought, and appears to be
rather less aggressive.
- --
Regards,

Dave [RLU #314465]
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
dwn...@ntlworld.com (David W Noon)
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlUDFrIACgkQRQ2Fs59Psv+MfgCgmZZESWyTwVOlFjBSzyQoXqO/
LBIAoMHClLFAKHUVg/S01kCCxIE0TMxc
=3GJD
-----END PGP SIGNATURE-----

[wabe...@gmail.com]

Mick <michael...@gmail.com> wrote:

> Hi All,
>
> I was given a CD with some pictures, but I am not able to mount it.
> This is what dmesg reveals:
>
> [ 7791.880206] sr 1:0:0:0: [sr0]
> [ 7791.880211] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
> [ 7791.880215] sr 1:0:0:0: [sr0]
> [ 7791.880217] Sense Key : Hardware Error [current]
> [ 7791.880224] sr 1:0:0:0: [sr0]
> [ 7791.880229] Add. Sense: Timeout on logical unit
> [ 7791.880233] sr 1:0:0:0: [sr0] CDB:
> [ 7791.880236] Read(10): 28 00 00 00 00 00 00 00 02 00
> [ 7791.880252] blk_update_request: I/O error, dev sr0, sector 0

[...]

> I tried on different PCs and I am getting the same error. Shall I

Have you tried it with different CD drives or have you used always the
same (external) drive? If you are testing several CD drives you maybe
will find one that is able to read the damaged CD.

> forget about it, or is there some means by which I can recover the
> files on it?

This depends on how the CD is damaged. If it is damaged by scratches
then you maybe can polish them away. Many years ago I've seen CD polish
sets available in some online shop, but I never tried this out.

If there are no scratches and it is a self burned CD then I fear you
will have no chance to restore the data.

I don't know if there is a way to restore the data with some special
software program. Maybe you should search for that on google.

Good luck.

--
Regards
wabe

[Mick]

On Friday 13 Mar 2015 17:10:36 wabe...@gmail.com wrote:
> Mick <michael...@gmail.com> wrote:
> > Hi All,
> >
> > I was given a CD with some pictures, but I am not able to mount it.
> > This is what dmesg reveals:
> >
> > [ 7791.880206] sr 1:0:0:0: [sr0]
> > [ 7791.880211] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
> > [ 7791.880215] sr 1:0:0:0: [sr0]
> > [ 7791.880217] Sense Key : Hardware Error [current]
> > [ 7791.880224] sr 1:0:0:0: [sr0]
> > [ 7791.880229] Add. Sense: Timeout on logical unit
> > [ 7791.880233] sr 1:0:0:0: [sr0] CDB:
> > [ 7791.880236] Read(10): 28 00 00 00 00 00 00 00 02 00
> > [ 7791.880252] blk_update_request: I/O error, dev sr0, sector 0
>
> [...]
>
> > I tried on different PCs and I am getting the same error. Shall I
>
> Have you tried it with different CD drives or have you used always the
> same (external) drive? If you are testing several CD drives you maybe
> will find one that is able to read the damaged CD.

Each PC has its own (internal) drive. No success so far. :-(

> > forget about it, or is there some means by which I can recover the
> > files on it?
>
> This depends on how the CD is damaged. If it is damaged by scratches
> then you maybe can polish them away. Many years ago I've seen CD polish
> sets available in some online shop, but I never tried this out.
>
> If there are no scratches and it is a self burned CD then I fear you
> will have no chance to restore the data.
>
> I don't know if there is a way to restore the data with some special
> software program. Maybe you should search for that on google.
>
> Good luck.

David mentioned in his post that there are products to clean and polish the
plastic surface (thanks David!) I can't see any significant scratches and I
tried cleaning it with spirit to remove any grease or dirt from its surface.
I will try to ask the person who gave it to me to use a different make of CD
next time, but this could take some time.

--
Regards,
Mick

[Joerg Schilling]

Grant Edwards <grant.b...@gmail.com> wrote:

> On 2015-03-13, Mick <michael...@gmail.com> wrote:
> > Hi All,
> >
> > I was given a CD with some pictures, but I am not able to mount it. This is
> > what dmesg reveals:
>

> Here's what I recommend.
>
> 1) Use ddrescue to read as many data blocks as you can off the CD.
>
> http://www.gnu.org/software/ddrescue/

This will ot really help.

If you like to do real read-retries at low level better check "readcd".

Jörg

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

[Grant Edwards]

On 2015-03-13, Mick <michael...@gmail.com> wrote:

> Hi All,
>
> I was given a CD with some pictures, but I am not able to mount it. This is
> what dmesg reveals:

Here's what I recommend.

1) Use ddrescue to read as many data blocks as you can off the CD.

http://www.gnu.org/software/ddrescue/

ddrescue will retry failing blocks and then skip over them. You
can rerun ddrescue to try to fill in missing blocks. dd or cat
will generally just stop when it hits the first bad block.

I would do something like:

a) Run several passes of ddrescue using a few different optical
drives.

b) Polish the CD.

c) Repeat until you stop getting new data off the CD.


2) Use something like photorec to try to scavange any reconizable
JPEGs (or other file types as desired) from the data image file
you created with ddrescue.

http://www.cgsecurity.org/wiki/PhotoRec

IIRC, there are ebuilds for ddrescue, photorec, and testdisk.

--
Grant Edwards grant.b.edwards Yow! I like the way ONLY
at their mouths move ... They
gmail.com look like DYING OYSTERS

[Fernando Rodriguez]

You can try sticking it into a DVD player and see if it plays. Also check that
all CD/DVD Filesystem options (including MS extensions) are enabled on your
kernel.


--
Fernando Rodriguez

[Neil Bothwick]

On Fri, 13 Mar 2015 17:54:01 +0000 (UTC), Grant Edwards wrote:

> IIRC, there are ebuilds for ddrescue, photorec, and testdisk.

There's also app-cdr/dvdisaster.


--
Neil Bothwick

A consultant is a person who borrows your watch, tells you what time it
is, pockets the watch, and sends you a bill for it.

[Mick]

On Friday 13 Mar 2015 22:24:32 Neil Bothwick wrote:
> On Fri, 13 Mar 2015 17:54:01 +0000 (UTC), Grant Edwards wrote:
> > IIRC, there are ebuilds for ddrescue, photorec, and testdisk.
>
> There's also app-cdr/dvdisaster.

Thank you all. dd and ddrescue don't work, because the block device is not
recognised. I had already tried this with not success.

dvddisaster requires to have created a file with error correction ("ecc") data
in advance of the hardware failure, then use that to recover the lost bits.

readcd is great - thanks Joerg! However, this is what I got in my first
attempt:
=================================================================
$ readcd dev=1,0,0 -v
scsidev: '1,0,0'
scsibus: 1 target: 0 lun: 0
Linux sg driver version: 3.5.36
readcd: Input/output error. set cd speed: scsi sendcmd: no error
CDB: BB 00 FF FF FF FF 00 00 00 00 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 04 01 00 00
Sense Key: 0x2 Not Ready, Segment 0
Sense Code: 0x04 Qual 0x01 (logical unit is in process of becoming ready) Fru
0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.042s timeout 40s
Read speed: 11080 kB/s (CD 62x, DVD 8x, BD 2x).
Write speed: 0 kB/s (CD 0x, DVD 0x, BD 0x).
0:read 1:veri 2:erase 3:read buffer 4:cache 5:ovtime 6:cap
7:wne 8:floppy 9:verify 10:checkcmds 11:read disk 12:write disk
13:scsireset 14:seektest 15: readda 16: reada 17: c2err
18:readcd 19: lin 20: full toc
Enter selection: 0 (0 - 20)/<cr>:
0:read 1:veri 2:erase 3:read buffer 4:cache 5:ovtime 6:cap
7:wne 8:floppy 9:verify 10:checkcmds 11:read disk 12:write disk
13:scsireset 14:seektest 15: readda 16: reada 17: c2err
18:readcd 19: lin 20: full toc
Enter selection: 4 (0 - 20)/<cr>:5 <==Not sure if I entered the correct No.
Doing 1000 'TEST UNIT READY' operations.
Time total: 0.296sec
Doing 1000 'SEEK_G1 (0)' operations.
Time total: 418.463sec
0:read 1:veri 2:erase 3:read buffer 4:cache 5:ovtime 6:cap
7:wne 8:floppy 9:verify 10:checkcmds 11:read disk 12:write disk
13:scsireset 14:seektest 15: readda 16: reada 17: c2err
18:readcd 19: lin 20: full toc
Enter selection: 10 (0 - 20)/<cr>:
=================================================================


Here I tried different values, none of which produced anything until:
=================================================================
Enter selection: 10 (0 - 20)/<cr>:11
Capacity: 2295104 Blocks = 4590208 kBytes = 4482 MBytes = 4700 prMB
Sectorsize: 2048 Bytes
Ignore disk size? y
Copy from SCSI (1,0,0) disk to file
Enter filename [disk.out]: disk.out
Enter starting sector for copy: 0 (0 - 9999999)/<cr>:0
Enter number of sectors to copy: 10000000 (1 - 10000000)/<cr>:
Enter number of sectors per copy: 64 (1 - 64)/<cr>:
end: 10000000
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: 70 00 04 00 00 00 00 0A 00 00 00 00 3E 02 00 00
Sense Key: 0x4 Hardware Error, Segment 0
Sense Code: 0x3E Qual 0x02 (timeout on logical unit) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 10.414s timeout 40s
readcd: Input/output error. Cannot read source disk
readcd: Retrying from sector 0.
.~~-readcd: Input/output error. test unit ready: scsi sendcmd: no error
CDB: 00 00 00 00 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 3A 00 00 00
Sense Key: 0x2 Not Ready, Segment 0
Sense Code: 0x3A Qual 0x00 (medium not present) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.009s timeout 40s
~readcd: Input/output error. test unit ready: scsi sendcmd: no error
CDB: 00 00 00 00 00 00
status: 0x2 (CHECK CONDITION)
=================================================================


This repeated itself for a while, until:
=================================================================
readcd: Input/output error. Error on sector 0 not corrected. Total of 1
errors.
readcd: Input/output error. read_g1: scsi sendcmd: no error
CDB: 28 00 00 00 00 00 00 00 01 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 3A 00 00 00
Sense Key: 0x2 Not Ready, Segment 0
Sense Code: 0x3A Qual 0x00 (medium not present) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.009s timeout 40s

Time total: 156.756sec
Read 0.00 kB at 0.0 kB/sec.
Max corected retry count was 0 (limited to 128).
The following 1 sector(s) could not be read correctly:

0
readcd: Input/output error. test unit ready: scsi sendcmd: no error
CDB: 00 00 00 00 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 3A 00 00 00
Sense Key: 0x2 Not Ready, Segment 0
Sense Code: 0x3A Qual 0x00 (medium not present) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.010s timeout 40s
readcd: Device not ready.
$
=================================================================

Does this above mean that the first sector is damaged? How to proceed from
here?

--
Regards,
Mick

[Mick]

On Saturday 14 Mar 2015 00:24:30 Mick wrote:
> On Friday 13 Mar 2015 22:24:32 Neil Bothwick wrote:
> > On Fri, 13 Mar 2015 17:54:01 +0000 (UTC), Grant Edwards wrote:
> > > IIRC, there are ebuilds for ddrescue, photorec, and testdisk.
> >
> > There's also app-cdr/dvdisaster.
>
> Thank you all. dd and ddrescue don't work, because the block device is not
> recognised. I had already tried this with not success.
>
> dvddisaster requires to have created a file with error correction ("ecc")
> data in advance of the hardware failure, then use that to recover the lost
> bits.
>
> readcd is great - thanks Joerg! However, this is what I got in my first
> attempt:
> =================================================================

[snip ...]

> =================================================================
>
> Does this above mean that the first sector is damaged? How to proceed from
> here?

I tried various options and I invariably end up with a sector 0 error:

Enter selection: 9 (0 - 20)/<cr>:11
Capacity: 250000 Blocks = 500000 kBytes = 488 MBytes = 512 prMB
Sectorsize: 2048 Bytes
Ignore disk size? yes
Copy from SCSI (0,0,0) disk to file
Enter filename [disk.out]: disk5.out

Enter starting sector for copy: 0 (0 - 9999999)/<cr>:

Enter number of sectors to copy: 10000000 (1 - 10000000)/<cr>:
Enter number of sectors per copy: 64 (1 - 64)/<cr>:
end: 10000000
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: 70 00 03 00 00 00 00 12 00 00 00 00 11 00 00 00
Sense Key: 0x3 Medium Error, Segment 0
Sense Code: 0x11 Qual 0x00 (unrecovered read error) Fru 0x0

Sense flags: Blk 0 (not valid)

cmd finished after 1.964s 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.

The resultant disk5.out is 0 bytes. Even when I try to start from sector 1 or
2, I end up with 0 byte output file. Any other settings I could try?

--
Regards,
Mick

[Joerg Schilling]

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

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.

[Joerg Schilling]

Mick <michael...@gmail.com> wrote:

> The resultant disk5.out is 0 bytes. Even when I try to start from sector 1 or
> 2, I end up with 0 byte output file. Any other settings I could try?

did you try to read the man page?

[Mick]

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

[Joerg Schilling]

Mick <michael...@gmail.com> wrote:

> 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) *

Pioneer is a good manufacturer...

> 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

This is an error at the layer above the audio sector. You may try to use:

cdrecord -noerror -edc-corr

and see whether readcd is able to do better corrections than the drive.

> 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?

It may be that the firmware did not understand the media and used a wrong laser
calibration for writing.

I recommend to use Verbatim media if you like to do archiving.

Note that piles of 50+ CDs may have worse media than thos up to 25 per package.

You can check this with cdrecord -v -atip

verbatim e.g. sells cheap media from Moser Baer India (MBI) but still with
better quality than MBI labelled media. Better verbatim media identify as
Verbatim (DVDs and BluRays may use IDs from the business group).

[Mick]

On Monday 16 Mar 2015 16:51:34 Joerg Schilling wrote:
> Mick <michael...@gmail.com> wrote:
> > 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) *
>
> Pioneer is a good manufacturer...

Ah! Yes, I was paying attention when you mentioned this in an older thread.
I also checked online reviews to confirm that they were still making good
devices before I ordered this one.

> > 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
>
> This is an error at the layer above the audio sector. You may try to use:
>
> cdrecord -noerror -edc-corr

I think you meant to say:

readcd -noerror -edc-corr

This is was I am getting.

# readcd -noerror -edc-corr

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 '/dev/null'
end: 250000
readcd: Input/output error. read_cd: scsi sendcmd: no error
CDB: BE 00 00 00 00 00 00 00 37 F8 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 05 00 00 00 00 0E 00 00 00 00 64 00 00 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x64 Qual 0x00 (illegal mode for this track) Fru 0x0

Sense flags: Blk 0 (not valid)

cmd finished after 0.016s 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 ...
.

readcd: Input/output error. Error on sector 3 not corrected. Total of 4

errors.
readcd: -noerror set, continuing ...

The count of errors runs in the thousands, until I cancel the command.

> I recommend to use Verbatim media if you like to do archiving.
>
> Note that piles of 50+ CDs may have worse media than thos up to 25 per
> package.
>
> You can check this with cdrecord -v -atip
>
> verbatim e.g. sells cheap media from Moser Baer India (MBI) but still with
> better quality than MBI labelled media. Better verbatim media identify as
> Verbatim (DVDs and BluRays may use IDs from the business group).

Thanks again for your help (and software) Jörg. I usually buy memorex and
verbatim when I burn my own CDs with good results, but this sample was created
by a friend of mine, who's now a few thousand miles away. I will be using my
media and burner when I meet him next time, to avoid disappointment. ;-)

--
Regards,
Mick

[Mick]

I managed to recover the files on the CD! I used ddrescue which eventually
was able to read the media and then ran photorec to retrieve the jpeg photos
from the rescued image.

ddrescue could not read the CD every time, but reinserting a few times on my
laptop managed to start reading it.

--
Regards,
Mick

[Joerg Schilling]

Mick <michael...@gmail.com> wrote:

> > This is an error at the layer above the audio sector. You may try to use:
> >
> > cdrecord -noerror -edc-corr
>
> I think you meant to say:
>
> readcd -noerror -edc-corr

You are of course correct.

As mentioned, the high level error correction in readcd can only help when the
drive does not include a decent Reed Solomon implementation in it's firmware.

What you could do is to check other sector ranges to find out whether the hole
capacity of the CD is unreadable or whether there are readable parts inside.
Note however that if you come close to the outer edge of the CD (1-2cm) the
error rate usually increases.

check the sectors= option in the man page...

[Joerg Schilling]

Given the fact that readcd includes the best possible algorithm for recovering,
this sounds a bit surprising. I however know that it sometimes helps to cool
down the media a bit.