public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* ittle problems with /dev/sr0 with 2.4.19-rc1
@ 2002-07-07 10:07 Christian Robert
  2002-07-07 10:13 ` Erik Andersen
  0 siblings, 1 reply; 4+ messages in thread
From: Christian Robert @ 2002-07-07 10:07 UTC (permalink / raw)
  To: linux-kernel


Problem with read back a fresh written cdrom.

[root@X-home:/btemp] # uname -a
Linux X-home 2.4.19-rc1 #2 Sat Jul 6 03:10:16 EDT 2002 i686 unknown


[root@X-home:/btemp] # ls -ld rescue.iso 
-rw-r--r--    1 root     root      6881280 May 19 22:26 rescue.iso

[root@X-home:/btemp] # cdrecord dev=0,0 speed=4 -v rescue.iso 
Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001 Jörg Schilling
TOC Type: 1 = CD-ROM
scsidev: '0,0'
scsibus: 0 target: 0 lun: 0
Linux sg driver version: 3.1.24
Using libscg version 'schily-0.5'
atapi: 1
Device type    : Removable CD-ROM
Version        : 0
Response Format: 1
Vendor_info    : 'SONY    '
Identifikation : 'CD-RW  CRX160E  '
Revision       : '1.0e'
Device seems to be: Generic mmc CD-RW.
Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
Driver flags   : SWABAUDIO
Drive buf size : 4183552 = 4085 KB
FIFO size      : 4194304 = 4096 KB
Track 01: data    6 MB        
Total size:       7 MB (00:44.82) = 3362 sectors
Lout start:       7 MB (00:46/62) = 3362 sectors
Current Secsize: 2048
ATIP info from disk:
  Indicated writing power: 3
  Reference speed: 6
  Is not unrestricted
  Is erasable
  Disk sub type: High speed Rewritable (CAV) media (1)
  ATIP start of lead in:  -11625 (97:27/00)
  ATIP start of lead out: 333750 (74:12/00)
  speed low: 4 speed high: 8
  power mult factor: 1 5
  recommended erase/write power: 5
  A2 values: 26 B2 4A
Disk type:    Phase change
Manuf. index: 0
Manufacturer: Illegal Manufacturer code
Blocks total: 333750 Blocks current: 333750 Blocks remaining: 330388
RBlocks total: 336246 RBlocks current: 336246 RBlocks remaining: 332884
Starting to write CD/DVD at speed 4 in write mode for single session.
Last chance to quit, starting real write in 0 seconds. Operation starts.
Waiting for reader process to fill input buffer ... input buffer ready.
Performing OPC...
Starting new track at sector: 0
Track 01:   6 of   6 MB written (fifo 100%).
Track 01: Total bytes read/written: 6881280/6881280 (3360 sectors).
Writing  time:   18.307s
Fixating...
Fixating time:   61.619s
cdrecord: fifo had 109 puts and 109 gets.
cdrecord: fifo was 0 times empty and 7 times full, min fill was 89%.

[root@X-home:/btemp] # md5sum /dev/sr0
md5sum: /dev/sr0: Input/output error         <- oups, it failed

[root@X-home:/btemp] # dd if=/dev/sr0 | md5sum
dd: reading `/dev/sr0': Input/output error   <- failed here too
13440+0 records in
13440+0 records out
5ec08b6fa7bf09741d1310e5baa800de  -          <- but md5sum is OK

[root@X-home:/btemp] # md5sum rescue.iso 
5ec08b6fa7bf09741d1310e5baa800de  rescue.iso

[root@X-home:/btemp] # cat /dev/sr0 > xxx

[root@X-home:/btemp] # diff xxx rescue.iso

[root@X-home:/btemp] # cksum /dev/sr0
3592423142 6881280 /dev/sr0

[root@X-home:/btemp] # cksum rescue.iso
3592423142 6881280 rescue.iso

[root@X-home:/btemp] # dd if=/dev/sr0 | md5sum     <- Note this one do not get input/output error
13440+0 records in
13440+0 records out
5ec08b6fa7bf09741d1310e5baa800de  -

[root@X-home:/btemp] # md5sum /dev/sr0
5ec08b6fa7bf09741d1310e5baa800de  /dev/sr0

[root@X-home:/btemp] # md5sum /dev/sr0 rescue.iso 
5ec08b6fa7bf09741d1310e5baa800de  /dev/sr0
5ec08b6fa7bf09741d1310e5baa800de  rescue.iso

[root@X-home:/btemp] # md5sum /dev/sr0 rescue.iso  <- it now work every time
5ec08b6fa7bf09741d1310e5baa800de  /dev/sr0
5ec08b6fa7bf09741d1310e5baa800de  rescue.iso

[root@X-home:/btemp] # eject

After re-insertion...

[root@X-home:/btemp] # md5sum /dev/sr0 rescue.iso 
md5sum: /dev/sr0: Input/output error               <- inout/output error on /dev/sr0
5ec08b6fa7bf09741d1310e5baa800de  rescue.iso


Can someone reproduce the "Input/output error" I get sometimes with "dd" and  with "md5sum" on /dev/sr0 
after burning a new CD ?

I'm pretty sure it was not doing that with 2.4.18
Looks like it fix itself after several minutes or many trys.
 

running 2.4.19-rc1

Xtian.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: ittle problems with /dev/sr0 with 2.4.19-rc1
  2002-07-07 10:07 ittle problems with /dev/sr0 with 2.4.19-rc1 Christian Robert
@ 2002-07-07 10:13 ` Erik Andersen
  2002-07-07 12:58   ` Admin
  0 siblings, 1 reply; 4+ messages in thread
From: Erik Andersen @ 2002-07-07 10:13 UTC (permalink / raw)
  To: Christian Robert; +Cc: linux-kernel

On Sun Jul 07, 2002 at 06:07:44AM -0400, Christian Robert wrote:
> [root@X-home:/btemp] # md5sum /dev/sr0
> md5sum: /dev/sr0: Input/output error         <- oups, it failed
> 
> [root@X-home:/btemp] # dd if=/dev/sr0 | md5sum
> dd: reading `/dev/sr0': Input/output error   <- failed here too
> 13440+0 records in
> 13440+0 records out
> 5ec08b6fa7bf09741d1310e5baa800de  -          <- but md5sum is OK

Looks like a read ahead bug to me...  Out of curiousity,
did you use "-no-pad" with mkisofs?

 -Erik

--
Erik B. Andersen             http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: ittle problems with /dev/sr0 with 2.4.19-rc1
  2002-07-07 10:13 ` Erik Andersen
@ 2002-07-07 12:58   ` Admin
  0 siblings, 0 replies; 4+ messages in thread
From: Admin @ 2002-07-07 12:58 UTC (permalink / raw)
  To: linux-kernel

On Domingo 07 Julio 2002 12:13, Erik Andersen wrote:
> On Sun Jul 07, 2002 at 06:07:44AM -0400, Christian Robert wrote:
> > [root@X-home:/btemp] # md5sum /dev/sr0
> > md5sum: /dev/sr0: Input/output error         <- oups, it failed
> >
> > [root@X-home:/btemp] # dd if=/dev/sr0 | md5sum
> > dd: reading `/dev/sr0': Input/output error   <- failed here too
> > 13440+0 records in
> > 13440+0 records out
> > 5ec08b6fa7bf09741d1310e5baa800de  -          <- but md5sum is OK
>
> Looks like a read ahead bug to me...  Out of curiousity,
> did you use "-no-pad" with mkisofs?
>
>  -Erik
Hi, I get same error with /dev/hdc, when I try the same on /dev/sr0, box 
freeze, kernel 2.4.17-xfs

Jul  7 14:29:24 iceberg kernel: hdc: command error: status=0x51 { DriveReady 
SeekComplete Error }
Jul  7 14:29:24 iceberg kernel: hdc: command error: error=0x50
Jul  7 14:29:24 iceberg kernel: end_request: I/O error, dev 16:00 (hdc), 
sector 1331600
Jul  7 14:29:24 iceberg kernel: hdc: command error: status=0x51 { DriveReady 
SeekComplete Error }
Jul  7 14:29:24 iceberg kernel: hdc: command error: error=0x50
Jul  7 14:29:24 iceberg kernel: end_request: I/O error, dev 16:00 (hdc), 
sector 1331604
Jul  7 14:29:24 iceberg kernel: hdc: command error: status=0x51 { DriveReady 
SeekComplete Error }
Jul  7 14:29:24 iceberg kernel: hdc: command error: error=0x50
Jul  7 14:29:24 iceberg kernel: end_request: I/O error, dev 16:00 (hdc), 
sector 1331608
Jul  7 14:29:24 iceberg kernel: hdc: command error: status=0x51 { DriveReady 
SeekComplete Error }
Jul  7 14:29:24 iceberg kernel: hdc: command error: error=0x50
Jul  7 14:29:24 iceberg kernel: end_request: I/O error, dev 16:00 (hdc), 
sector 1331612
Jul  7 14:29:28 iceberg kernel: hdc: command error: status=0x51 { DriveReady 
SeekComplete Error }
Jul  7 14:29:28 iceberg kernel: hdc: command error: error=0x50
Jul  7 14:29:28 iceberg kernel: end_request: I/O error, dev 16:00 (hdc), 
sector 1331616
Jul  7 14:29:31 iceberg kernel: hdc: command error: status=0x51 { DriveReady 
SeekComplete Error }
Jul  7 14:29:31 iceberg kernel: hdc: command error: error=0x50
Jul  7 14:29:31 iceberg kernel: end_request: I/O error, dev 16:00 (hdc), 
sector 1331620
Jul  7 14:29:31 iceberg kernel: hdc: command error: status=0x51 { DriveReady 
SeekComplete Error }
Jul  7 14:29:31 iceberg kernel: hdc: command error: error=0x50
Jul  7 14:29:31 iceberg kernel: end_request: I/O error, dev 16:00 (hdc), 
sector 1331624
Jul  7 14:29:31 iceberg kernel: hdc: command error: status=0x51 { DriveReady 
SeekComplete Error }
Jul  7 14:29:31 iceberg kernel: hdc: command error: error=0x50
Jul  7 14:29:31 iceberg kernel: end_request: I/O error, dev 16:00 (hdc), 
sector 1331628
Jul  7 14:29:32 iceberg kernel: hdc: command error: status=0x51 { DriveReady 
SeekComplete Error }
Jul  7 14:29:32 iceberg kernel: hdc: command error: error=0x50
Jul  7 14:29:32 iceberg kernel: end_request: I/O error, dev 16:00 (hdc), 
sector 1331632
Jul  7 14:29:32 iceberg kernel: hdc: command error: status=0x51 { DriveReady 
SeekComplete Error }
Jul  7 14:29:32 iceberg kernel: hdc: command error: error=0x50
Jul  7 14:29:32 iceberg kernel: end_request: I/O error, dev 16:00 (hdc), 
sector 1331636


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: ittle problems with /dev/sr0 with 2.4.19-rc1
@ 2002-07-13 12:33 Tony Spinillo
  0 siblings, 0 replies; 4+ messages in thread
From: Tony Spinillo @ 2002-07-13 12:33 UTC (permalink / raw)
  To: linux-kernel

I think I also hit this. Kernel 2.4.19-rc1-ac3. I tried the
-no-pad option. I also tried readcd dev=2,0,0 f=/test.iso,
that failed also.

The latest cdrdao seems to read and make good copies though.

from /var/log/messages:
Jul 13 07:50:14 251 kernel: scsi2: ERROR on channel 0, id 0, lun

0,CDB: Request Sense 00 00 00 40 00
Jul 13 07:50:14 251 kernel: Info fld=0x50698 (nonstd), Current
sd0b:00: sense key Medium Error
Jul 13 07:50:14 251 kernel: Additional sense indicates 
Unrecovered read error

I will test later with some other media, a different build
of cdrecord, and I will run a cleaner through the drive.

Thanks,

Tony



>>On Sun Jul 07, 2002 at 06:07:44AM -0400, Christian Robert
wrote:
>> [root@X-home:/btemp] # md5sum /dev/sr0
>> md5sum: /dev/sr0: Input/output error         <- oups, it 
failed
>> 
>> [root@X-home:/btemp] # dd if=/dev/sr0 | md5sum
>> dd: reading `/dev/sr0': Input/output error   <- failed here
too
>> 13440+0 records in
>> 13440+0 records out
>> 5ec08b6fa7bf09741d1310e5baa800de  - <- but md5sum is 
>OK

>Looks like a read ahead bug to me...  Out of curiousity,
>did you use "-no-pad" with mkisofs?

> -Erik

__________________________________________________
Do You Yahoo!?
Yahoo! Autos - Get free new car price quotes
http://autos.yahoo.com

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2002-07-13 12:30 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-07-07 10:07 ittle problems with /dev/sr0 with 2.4.19-rc1 Christian Robert
2002-07-07 10:13 ` Erik Andersen
2002-07-07 12:58   ` Admin
  -- strict thread matches above, loose matches on Subject: below --
2002-07-13 12:33 Tony Spinillo

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox