Re: startsec problem?
Alexey Toptygin [EMAIL PROTECTED] wrote: On Mon, 24 Apr 2006, Joerg Schilling wrote: Alexey Toptygin [EMAIL PROTECTED] wrote: OK, I have built cdrecord from this source: ftp://ftp.berlios.de/pub/cdrecord/cdrtools-2.01.tar.bz2 and I have changed the drive specification in /etc/default/cdrecord to ATA:0,1,0. I read 2 known-good pressed audio CD with official readcd -clone and wrote them with official cdrecord -clone. Both times I got the same error, which is the same as with the unofficial Debian version. The coasters produced cause the drive to take too long when trying to cdrecord -toc or cdrecord -atip, and the bus is reset, and DMA turned off. Here is the output of cdrecord: What error are you talking of? This is what I called an error, it is the only indication that anything is wrong until I try to read the CD that was just burned: YOu did absolutely not give any indication for a problem. How should I help you? If you like help, you would need to give us the reason why you cannot use the resulting CD. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: startsec problem?
Maik Zumstrull [EMAIL PROTECTED] wrote: Joerg Schilling wrote: Alexey Toptygin [EMAIL PROTECTED] wrote: cdrecord: WARNING: Drive returns wrong startsec (0) using -150 This is from a buggy firmware. Most of the drives I have access to do this. A drive that makes it wrong will be unable to write a second session in SAO. The main problem is that the OP did not yet send any indication on a problem. Is the SCSI spec somehow unclear at that point? Why do many manufacturers think they should return 0? It's probably intentional, given how many drives do it. Many people from asian locations have problems to read the standard. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: startsec problem?
Joerg Schilling wrote: Alexey Toptygin [EMAIL PROTECTED] wrote: On Mon, 24 Apr 2006, Joerg Schilling wrote: Alexey Toptygin [EMAIL PROTECTED] wrote: OK, I have built cdrecord from this source: ftp://ftp.berlios.de/pub/cdrecord/cdrtools-2.01.tar.bz2 and I have changed the drive specification in /etc/default/cdrecord to ATA:0,1,0. I read 2 known-good pressed audio CD with official readcd -clone and wrote them with official cdrecord -clone. Both times I got the same error, which is the same as with the unofficial Debian version. The coasters produced cause the drive to take too long when trying to cdrecord -toc or cdrecord -atip, and the bus is reset, and DMA turned off. Here is the output of cdrecord: What error are you talking of? This is what I called an error, it is the only indication that anything is wrong until I try to read the CD that was just burned: YOu did absolutely not give any indication for a problem. How should I help you? If you like help, you would need to give us the reason why you cannot use the resulting CD. He did, you deleted and ignored it: As I said, the burn results in a coaster that causes some drives to take a very long time to respond to commands, and some drives to act as if there's no media. -- E. Robert Bogusta It seemed like a good idea at the time -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: startsec problem?
Rob Bogus [EMAIL PROTECTED] wrote: If you like help, you would need to give us the reason why you cannot use the resulting CD. He did, you deleted and ignored it: As I said, the burn results in a coaster that causes some drives to take a very long time to respond to commands, and some drives to act as if there's no media. If you definitely did follow the instructions in the man page and the drive does not write correct data in raw mode, throw the drive away and get a non-broken drive. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: startsec problem?
Alexey Toptygin [EMAIL PROTECTED] wrote: OK, I have built cdrecord from this source: ftp://ftp.berlios.de/pub/cdrecord/cdrtools-2.01.tar.bz2 and I have changed the drive specification in /etc/default/cdrecord to ATA:0,1,0. I read 2 known-good pressed audio CD with official readcd -clone and wrote them with official cdrecord -clone. Both times I got the same error, which is the same as with the unofficial Debian version. The coasters produced cause the drive to take too long when trying to cdrecord -toc or cdrecord -atip, and the bus is reset, and DMA turned off. Here is the output of cdrecord: What error are you talking of? Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: startsec problem?
On Mon, 24 Apr 2006, Joerg Schilling wrote: Alexey Toptygin [EMAIL PROTECTED] wrote: OK, I have built cdrecord from this source: ftp://ftp.berlios.de/pub/cdrecord/cdrtools-2.01.tar.bz2 and I have changed the drive specification in /etc/default/cdrecord to ATA:0,1,0. I read 2 known-good pressed audio CD with official readcd -clone and wrote them with official cdrecord -clone. Both times I got the same error, which is the same as with the unofficial Debian version. The coasters produced cause the drive to take too long when trying to cdrecord -toc or cdrecord -atip, and the bus is reset, and DMA turned off. Here is the output of cdrecord: What error are you talking of? This is what I called an error, it is the only indication that anything is wrong until I try to read the CD that was just burned: ./official/cdrtools-2.01/cdrecord/OBJ/i686-linux-cc/cdrecord: WARNING: Drive returns wrong startsec (0) using -11849 from ATIP Writing lead-in at sector -11849 As I said, the burn results in a coaster that causes some drives to take a very long time to respond to commands, and some drives to act as if there's no media. Alexey -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: startsec problem?
Alexey Toptygin [EMAIL PROTECTED] wrote: You misunderstand. I both cloned and ripped with cdparanoia from the same master (in parallel, not in series). The master plays fine, and is apparently scratch-free. The copy made by readcd -clone from the master and then cdrecord -clone -raw96r causes the drive to get very confused when it tries to read it, leading to bus resets and the drive being forced into PIO mode. The only error reported by cdrecord is the startsec one. The copy made from the master with cdparanoia and burned with cdrecord -dao -audio plays fine, but cdrecord still reports a startsec error. You look confused cdparanoia is not able to create a clone image. The more I read from this thread, the more I believe that you are using just commands and options in a bad combination that cause your problems. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: startsec problem?
On Mon, 24 Apr 2006, Joerg Schilling wrote: Alexey Toptygin [EMAIL PROTECTED] wrote: You misunderstand. I both cloned and ripped with cdparanoia from the same master (in parallel, not in series). The master plays fine, and is apparently scratch-free. The copy made by readcd -clone from the master and then cdrecord -clone -raw96r causes the drive to get very confused when it tries to read it, leading to bus resets and the drive being forced into PIO mode. The only error reported by cdrecord is the startsec one. The copy made from the master with cdparanoia and burned with cdrecord -dao -audio plays fine, but cdrecord still reports a startsec error. You look confused cdparanoia is not able to create a clone image. The more I read from this thread, the more I believe that you are using just commands and options in a bad combination that cause your problems. No, no, no! I used cdparanoia to grab tracks that I burned with cdrecord -dao -audio, and that worked! On the same drive, ripping the same CD with readcd -clone and writing it with cdrecord -clone fails, and I'm reporting that failure. The only reason I mentionaed cdparanoia at all is that I wanted to show a case which, by contrast, worked. Please believe me when I say I'm not just throwing random junk on the command line. Alexey -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: startsec problem?
Joerg Schilling wrote: Alexey Toptygin [EMAIL PROTECTED] wrote: cdrecord: WARNING: Drive returns wrong startsec (0) using -150 This is from a buggy firmware. Most of the drives I have access to do this. Is the SCSI spec somehow unclear at that point? Why do many manufacturers think they should return 0? It's probably intentional, given how many drives do it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: startsec problem?
On Sun, 9 Apr 2006, Bill Davidsen wrote: I took an audio CD, cloned it with readcd, and grabbed the tracks with cdparanoia. Then, I tried to burn the cloned image: Let's start with why you didn't do the rip on the original media... cloning usually creates an ectype (a true and faithful copy of an original), so if there were defects in the original you wind up with a shiny new defective copy :-( For instance if you clone a CD with a scratch you can get a copy which has no physical defect but returns the same data a the CD with the scratch. This is generally not an improvement. You misunderstand. I both cloned and ripped with cdparanoia from the same master (in parallel, not in series). The master plays fine, and is apparently scratch-free. The copy made by readcd -clone from the master and then cdrecord -clone -raw96r causes the drive to get very confused when it tries to read it, leading to bus resets and the drive being forced into PIO mode. The only error reported by cdrecord is the startsec one. The copy made from the master with cdparanoia and burned with cdrecord -dao -audio plays fine, but cdrecord still reports a startsec error. Alexey -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: startsec problem?
OK, I have built cdrecord from this source: ftp://ftp.berlios.de/pub/cdrecord/cdrtools-2.01.tar.bz2 and I have changed the drive specification in /etc/default/cdrecord to ATA:0,1,0. I read 2 known-good pressed audio CD with official readcd -clone and wrote them with official cdrecord -clone. Both times I got the same error, which is the same as with the unofficial Debian version. The coasters produced cause the drive to take too long when trying to cdrecord -toc or cdrecord -atip, and the bus is reset, and DMA turned off. Here is the output of cdrecord: $ sudo ./official/cdrtools-2.01/cdrecord/OBJ/i686-linux-cc/cdrecord -v -clone -raw96r cdimage Cdrecord-Clone 2.01 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling ./official/cdrtools-2.01/cdrecord/OBJ/i686-linux-cc/cdrecord: Warning: Running on Linux-2.6.15-1-686 ./official/cdrtools-2.01/cdrecord/OBJ/i686-linux-cc/cdrecord: There are unsettled issues with Linux-2.5 and newer. ./official/cdrtools-2.01/cdrecord/OBJ/i686-linux-cc/cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris. TOC Type: 1 = CD-ROM scsidev: 'ATA:0,1,0' devname: 'ATA' scsibus: 0 target: 1 lun: 0 Warning: Using badly designed ATAPI via /dev/hd* interface. Linux sg driver version: 3.5.27 Using libscg version 'schily-0.8'. Driveropts: 'burnfree' SCSI buffer size: 64512 atapi: -1 Device type: Removable CD-ROM Version: 0 Response Format: 3 Capabilities : Vendor_info: 'PLEXTOR ' Identifikation : 'DVDR PX-740A ' Revision : '1.00' Device seems to be: Generic mmc2 DVD-R/DVD-RW. Current: 0x0009 Profile: 0x002B Profile: 0x001B Profile: 0x001A Profile: 0x0016 Profile: 0x0015 Profile: 0x0014 Profile: 0x0011 Profile: 0x0010 Profile: 0x000A Profile: 0x0009 (current) Profile: 0x0008 ./official/cdrtools-2.01/cdrecord/OBJ/i686-linux-cc/cdrecord: This version of cdrecord does not include DVD-R/DVD-RW support code. ./official/cdrtools-2.01/cdrecord/OBJ/i686-linux-cc/cdrecord: If you need DVD-R/DVD-RW support, ask the Author for cdrecord-ProDVD. ./official/cdrtools-2.01/cdrecord/OBJ/i686-linux-cc/cdrecord: Free test versions and free keys for personal use are at ftp://ftp.berlios.de/pub/cdrecord/ProDVD/ Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). Driver flags : MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96R RAW/R16 RAW/R96R Drive buf size : 1073152 = 1048 KB FIFO size : 4194304 = 4096 KB Encoding speed : 126x (9440 sectors/s) for libedc from Heiko Eißfeldt Track 01: data 513 MB Total size: 492 MB (48:50.13) = 219760 sectors Lout start: 493 MB (48:52/10) = 219760 sectors Current Secsize: 2048 ATIP info from disk: Indicated writing power: 4 Is not unrestricted Is not erasable Disk sub type: Medium Type A, high Beta category (A+) (3) ATIP start of lead in: -11849 (97:24/01) ATIP start of lead out: 359847 (79:59/72) Disk type:Long strategy type (Cyanine, AZO or similar) Manuf. index: 25 Manufacturer: Taiyo Yuden Company Limited Blocks total: 359847 Blocks current: 359847 Blocks remaining: 140087 Starting to write CD/DVD at speed 48 in real RAW/RAW96R mode for single session. Last chance to quit, starting real write0 seconds. Operation starts. Waiting for reader process to fill input buffer ... input buffer ready. BURN-Free is ON. Turning BURN-Free off Performing OPC... ./official/cdrtools-2.01/cdrecord/OBJ/i686-linux-cc/cdrecord: WARNING: Drive returns wrong startsec (0) using -11849 from ATIP Writing lead-in at sector -11849 Lead-in write time: 12.945s Writing pregap for track 1 at -150 Starting new track at sector: 0 Track 01: 513 of 513 MB written (fifo 100%) [buf 91%] 41.7x. Track 01: Total bytes read/written: 537972480/537972480 (219760 sectors). Writing time: 115.883s Average write speed 28.5x. Min drive buffer fill was 86% Writing Leadout... Fixating... Fixating time: 39.324s ./official/cdrtools-2.01/cdrecord/OBJ/i686-linux-cc/cdrecord: fifo had 8453 puts and 8453 gets. ./official/cdrtools-2.01/cdrecord/OBJ/i686-linux-cc/cdrecord: fifo was 0 times empty and 3831 times full, min fill was 92%. Alexey
Re: startsec problem?
Alexey Toptygin [EMAIL PROTECTED] wrote: I originally sent this to [EMAIL PROTECTED] as cdrecord instructs, but I've not heard anything back, and I'm unable to locate archives for that (list? or does it forward to the package maintainer?) so I'm reposting it here. Any help would be appreciated; I'm willing to test/troubleshoot. I'm not on the list, so please Cc: me. Debian package maintainers seem to be very slow and my impression is that something is wrong at Debian: - cdrtools did get it's last update on Debian in januray 2006, but they used a version from May 2005 2.01.01a03. The current version is a07! - star did get it's last update on Debian in september 2005. I did publish 6 new versions since then. - smake did get it's last update on Debian in july 2004. I did publish 11 new versions since then. I took an audio CD, cloned it with readcd, and grabbed the tracks with cdparanoia. Then, I tried to burn the cloned image: Both methods are a very bad idea! cloning defective by intention audio CDs clones the defects cdparanois is unmaintained since 5 years. Better use cdda2wav which gives better results than cdparanoia. Start reading the man pages there are examples for your use case. $ sudo cdrecord -v -clone -raw96r cdimage Cdrecord-Clone 2.01.01a03 (i686-pc-linux-gnu) Copyright (C) 1995-2005 Joerg Schilling NOTE: this version of cdrecord is an inofficial (modified) release of cdrecord and thus may have bugs that are not present in the original version. Please send bug reports and support requests to [EMAIL PROTECTED]. The original author should not be bothered with problems of this version. cdrecord: Warning: Running on Linux-2.6.15-1-686 cdrecord: There are unsettled issues with Linux-2.5 and newer. cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris. TOC Type: 1 = CD-ROM scsidev: '/dev/hdb' devname: '/dev/hdb' scsibus: -2 target: -2 lun: -2 Warning: Open by 'devname' is unintentional and not supported. If you did read the man page, you did know the right way to specify SCSI addresses. Linux sg driver version: 3.5.27 Using libscg version 'debian-0.8debian2'. cdrecord: Warning: using inofficial version of libscg (debian-0.8debian2 '@(#)scsitransp.c 1.91 04/06/17 Copyright 1988,1995,2000-2004 J. Schilling'). SCSI buffer size: 64512 atapi: 1 Device type: Removable CD-ROM Version: 0 Response Format: 3 Capabilities : Vendor_info: 'PLEXTOR ' Identifikation : 'DVDR PX-740A ' Revision : '1.00' Device seems to be: Generic mmc2 DVD-R/DVD-RW. Current: 0x0009 Profile: 0x002B Profile: 0x001B Profile: 0x001A Profile: 0x0016 Profile: 0x0015 Profile: 0x0014 Profile: 0x0011 Profile: 0x0010 Profile: 0x000A Profile: 0x0009 (current) Someone did add a bug, this should be on separate lines... Profile: 0x0008 cdrecord: This version of cdrecord does not include DVD-R/DVD-RW support code. cdrecord: See /usr/share/doc/cdrecord/README.DVD.Debian for details on DVD support. Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). Driver flags : MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96R RAW/R16 RAW/R96R Drive buf size : 1073152 = 1048 KB FIFO size : 4194304 = 4096 KB Encoding speed : 101x (7543 sectors/s) for libedc from Heiko Eißfeldt Track 01: data 419 MB Total size: 403 MB (39:56.76) = 179757 sectors Lout start: 403 MB (39:58/57) = 179757 sectors Current Secsize: 2048 ATIP info from disk: Indicated writing power: 4 Is not unrestricted Is not erasable Disk sub type: Medium Type A, high Beta category (A+) (3) ATIP start of lead in: -11849 (97:24/01) ATIP start of lead out: 359847 (79:59/72) Disk type:Long strategy type (Cyanine, AZO or similar) Manuf. index: 25 Manufacturer: Taiyo Yuden Company Limited Blocks total: 359847 Blocks current: 359847 Blocks remaining: 180090 Starting to write CD/DVD at speed 48 in real RAW/RAW96R mode for single session. Last chance to quit, starting real write0 seconds. Operation starts. Waiting for reader process to fill input buffer ... input buffer ready. BURN-Free is ON. Turning BURN-Free off Performing OPC... cdrecord: WARNING: Drive returns wrong startsec (0) using -11849 from ATIP Writing lead-in at sector -11849 Lead-in write time: 12.928s Writing pregap for track 1 at -150 Starting new track at sector: 0 Track 01: 419 of 419 MB written (fifo 100%) [buf 91%] 37.8x. Track 01: Total bytes read/written: 440045136/440045136 (179757 sectors). Writing time: 99.595s Average write speed 27.7x. Min drive buffer fill was 26% Writing Leadout... Fixating... Fixating time: 37.845s cdrecord: fifo had 6914 puts and 6914 gets. cdrecord: fifo was 0 times empty and 3299 times full, min fill was 92%. This produced a coaster; when I tried to do anything with it, the drive
Re: startsec problem?
It certainly could be documented better so people would see how to do
it. AFAIK it's It certainly could be documented better so people would
see how to do it. AFAIK it's Alexey Toptygin wrote:
I originally sent this to [EMAIL PROTECTED] as cdrecord
instructs, but I've not heard anything back, and I'm unable to locate
archives for that (list? or does it forward to the package maintainer?)
so I'm reposting it here. Any help would be appreciated; I'm willing
to test/troubleshoot. I'm not on the list, so please Cc: me.
I took an audio CD, cloned it with readcd, and grabbed the tracks with
cdparanoia. Then, I tried to burn the cloned image:
Let's start with why you didn't do the rip on the original media...
cloning usually creates an ectype (a true and faithful copy of an
original), so if there were defects in the original you wind up with a
shiny new defective copy :-( For instance if you clone a CD with a
scratch you can get a copy which has no physical defect but returns the
same data a the CD with the scratch. This is generally not an improvement.
$ sudo cdrecord -v -clone -raw96r cdimage
Cdrecord-Clone 2.01.01a03 (i686-pc-linux-gnu) Copyright (C) 1995-2005
Joerg Schilling
NOTE: this version of cdrecord is an inofficial (modified) release of
cdrecord
and thus may have bugs that are not present in the original version.
Please send bug reports and support requests to
[EMAIL PROTECTED].
The original author should not be bothered with problems of this version.
cdrecord: Warning: Running on Linux-2.6.15-1-686
cdrecord: There are unsettled issues with Linux-2.5 and newer.
cdrecord: If you have unexpected problems, please try Linux-2.4 or
Solaris.
TOC Type: 1 = CD-ROM
scsidev: '/dev/hdb'
devname: '/dev/hdb'
scsibus: -2 target: -2 lun: -2
Warning: Open by 'devname' is unintentional and not supported.
Linux sg driver version: 3.5.27
Using libscg version 'debian-0.8debian2'.
cdrecord: Warning: using inofficial version of libscg
(debian-0.8debian2 '@(#)scsitransp.c 1.91 04/06/17 Copyright
1988,1995,2000-2004 J. Schilling').
SCSI buffer size: 64512
atapi: 1
Device type : Removable CD-ROM
Version : 0
Response Format: 3
Capabilities : Vendor_info : 'PLEXTOR '
Identifikation : 'DVDR PX-740A '
Revision : '1.00'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Current: 0x0009
Profile: 0x002B Profile: 0x001B Profile: 0x001A Profile: 0x0016
Profile: 0x0015 Profile: 0x0014 Profile: 0x0011 Profile: 0x0010
Profile: 0x000A Profile: 0x0009 (current)
Profile: 0x0008 cdrecord: This version of cdrecord does not include
DVD-R/DVD-RW support code.
cdrecord: See /usr/share/doc/cdrecord/README.DVD.Debian for details on
DVD support.
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET
SAO SAO/R96R RAW/R16 RAW/R96R
Drive buf size : 1073152 = 1048 KB
FIFO size : 4194304 = 4096 KB
Encoding speed : 101x (7543 sectors/s) for libedc from Heiko Ei�feldt
Track 01: data 419 MB Total size: 403 MB (39:56.76) = 179757 sectors
Lout start: 403 MB (39:58/57) = 179757 sectors
Current Secsize: 2048
ATIP info from disk:
Indicated writing power: 4
Is not unrestricted
Is not erasable
Disk sub type: Medium Type A, high Beta category (A+) (3)
ATIP start of lead in: -11849 (97:24/01)
ATIP start of lead out: 359847 (79:59/72)
Disk type: Long strategy type (Cyanine, AZO or similar)
Manuf. index: 25
Manufacturer: Taiyo Yuden Company Limited
Blocks total: 359847 Blocks current: 359847 Blocks remaining: 180090
Starting to write CD/DVD at speed 48 in real RAW/RAW96R mode for
single session.
Last chance to quit, starting real write 0 seconds. Operation starts.
Waiting for reader process to fill input buffer ... input buffer ready.
BURN-Free is ON.
Turning BURN-Free off
Performing OPC...
cdrecord: WARNING: Drive returns wrong startsec (0) using -11849 from
ATIP
Writing lead-in at sector -11849
Lead-in write time: 12.928s
Writing pregap for track 1 at -150
Starting new track at sector: 0
Track 01: 419 of 419 MB written (fifo 100%) [buf 91%] 37.8x.
Track 01: Total bytes read/written: 440045136/440045136 (179757 sectors).
Writing time: 99.595s
Average write speed 27.7x.
Min drive buffer fill was 26%
Writing Leadout...
Fixating...
Fixating time: 37.845s
cdrecord: fifo had 6914 puts and 6914 gets.
cdrecord: fifo was 0 times empty and 3299 times full, min fill was 92%.
This produced a coaster; when I tried to do anything with it, the
drive took forever to respond, so DMA got disabled, and the bus was
reset:
Apr 5 19:10:00 rain kernel: hdb: status error: status=0x00 { }
Apr 5 19:10:01 rain kernel: ide: failed opcode was: unknown
Apr 5 19:10:01 rain kernel: hdb: status error: status=0x00 { }
Apr 5 19:10:01 rain kernel: ide: failed opcode was: unknown
Apr 5 19:10:01 rain kernel: hdb: status error: status=0x00 { }
Apr 5 19:10:01 rain kernel: ide: failed opcode was: unknown
Apr 5 19:10:01 rain kernel: hdb: status error: status=0x00 { }
Apr 5
startsec problem?
I originally sent this to [EMAIL PROTECTED] as cdrecord
instructs, but I've not heard anything back, and I'm unable to locate
archives for that (list? or does it forward to the package maintainer?)
so I'm reposting it here. Any help would be appreciated; I'm willing to
test/troubleshoot. I'm not on the list, so please Cc: me.
I took an audio CD, cloned it with readcd, and grabbed the tracks with
cdparanoia. Then, I tried to burn the cloned image:
$ sudo cdrecord -v -clone -raw96r cdimage
Cdrecord-Clone 2.01.01a03 (i686-pc-linux-gnu) Copyright (C) 1995-2005 Joerg
Schilling
NOTE: this version of cdrecord is an inofficial (modified) release of cdrecord
and thus may have bugs that are not present in the original version.
Please send bug reports and support requests to
[EMAIL PROTECTED].
The original author should not be bothered with problems of this version.
cdrecord: Warning: Running on Linux-2.6.15-1-686
cdrecord: There are unsettled issues with Linux-2.5 and newer.
cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris.
TOC Type: 1 = CD-ROM
scsidev: '/dev/hdb'
devname: '/dev/hdb'
scsibus: -2 target: -2 lun: -2
Warning: Open by 'devname' is unintentional and not supported.
Linux sg driver version: 3.5.27
Using libscg version 'debian-0.8debian2'.
cdrecord: Warning: using inofficial version of libscg (debian-0.8debian2
'@(#)scsitransp.c 1.91 04/06/17 Copyright 1988,1995,2000-2004 J.
Schilling').
SCSI buffer size: 64512
atapi: 1
Device type: Removable CD-ROM
Version: 0
Response Format: 3
Capabilities : Vendor_info: 'PLEXTOR '
Identifikation : 'DVDR PX-740A '
Revision : '1.00'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Current: 0x0009
Profile: 0x002B Profile: 0x001B Profile: 0x001A Profile: 0x0016 Profile: 0x0015
Profile: 0x0014 Profile: 0x0011 Profile: 0x0010 Profile: 0x000A Profile: 0x0009
(current)
Profile: 0x0008 cdrecord: This version of cdrecord does not include
DVD-R/DVD-RW support code.
cdrecord: See /usr/share/doc/cdrecord/README.DVD.Debian for details on DVD
support.
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO
SAO/R96R RAW/R16 RAW/R96R
Drive buf size : 1073152 = 1048 KB
FIFO size : 4194304 = 4096 KB
Encoding speed : 101x (7543 sectors/s) for libedc from Heiko Ei?feldt
Track 01: data 419 MB Total size: 403 MB (39:56.76) = 179757 sectors
Lout start: 403 MB (39:58/57) = 179757 sectors
Current Secsize: 2048
ATIP info from disk:
Indicated writing power: 4
Is not unrestricted
Is not erasable
Disk sub type: Medium Type A, high Beta category (A+) (3)
ATIP start of lead in: -11849 (97:24/01)
ATIP start of lead out: 359847 (79:59/72)
Disk type:Long strategy type (Cyanine, AZO or similar)
Manuf. index: 25
Manufacturer: Taiyo Yuden Company Limited
Blocks total: 359847 Blocks current: 359847 Blocks remaining: 180090
Starting to write CD/DVD at speed 48 in real RAW/RAW96R mode for single
session.
Last chance to quit, starting real write0 seconds. Operation starts.
Waiting for reader process to fill input buffer ... input buffer ready.
BURN-Free is ON.
Turning BURN-Free off
Performing OPC...
cdrecord: WARNING: Drive returns wrong startsec (0) using -11849 from ATIP
Writing lead-in at sector -11849
Lead-in write time: 12.928s
Writing pregap for track 1 at -150
Starting new track at sector: 0
Track 01: 419 of 419 MB written (fifo 100%) [buf 91%] 37.8x.
Track 01: Total bytes read/written: 440045136/440045136 (179757 sectors).
Writing time: 99.595s
Average write speed 27.7x.
Min drive buffer fill was 26%
Writing Leadout...
Fixating...
Fixating time: 37.845s
cdrecord: fifo had 6914 puts and 6914 gets.
cdrecord: fifo was 0 times empty and 3299 times full, min fill was 92%.
This produced a coaster; when I tried to do anything with it, the drive took
forever to respond, so DMA got disabled, and the bus was reset:
Apr 5 19:10:00 rain kernel: hdb: status error: status=0x00 { }
Apr 5 19:10:01 rain kernel: ide: failed opcode was: unknown
Apr 5 19:10:01 rain kernel: hdb: status error: status=0x00 { }
Apr 5 19:10:01 rain kernel: ide: failed opcode was: unknown
Apr 5 19:10:01 rain kernel: hdb: status error: status=0x00 { }
Apr 5 19:10:01 rain kernel: ide: failed opcode was: unknown
Apr 5 19:10:01 rain kernel: hdb: status error: status=0x00 { }
Apr 5 19:10:01 rain kernel: ide: failed opcode was: unknown
Apr 5 19:10:01 rain kernel: hdb: DMA disabled
Apr 5 19:10:01 rain kernel: hdb: ATAPI reset complete
Then, I tried to just burn the tracks in dao mode; I think the fifo is so low
because the drive is in PIO mode (but the source hard drive was on a different
bus...):
$ sudo cdrecord -v -dao -audio track*
Cdrecord-Clone 2.01.01a03 (i686-pc-linux-gnu) Copyright (C) 1995-2005 Joerg
Schilling
NOTE: this version of cdrecord is an inofficial (modified) release
