Re: cdrecord and "get performance" scsi errors
On 5/16/07, Thomas Schmitt <scdbackup@gmx.net> wrote:
Do you have rw-permission on /dev/sg4 ?
I run all command as root, just to be safe:
crw-rw---- 1 root disk 21, 4 Sep 9 2004 /dev/sg4
Maybe one could learn more from
cdrskin/cdrskin -vvv dev=/dev/scd1 -atip
cdrskin 0.3.6 : limited cdrecord compatibility wrapper for libburn
cdrskin: DEBUG : burn_drive_convert_fs_adr( /dev/scd1 )
cdrskin: DEBUG : burn_drive_find_scsi_equiv( /dev/scd1 ) : (4),4,0,0,0
cdrskin: DEBUG : burn_drive_convert_scsi_adr( -1,4,0,0,0 )
cdrskin: DEBUG : burn_drive_convert_scsi_adr() found /dev/sg4
cdrskin: NOTE : greying out all drives besides given dev='/dev/sg4'
cdrskin: scanning for devices ...
ò
UNIX-SIGNAL: SIGINT errno= 2
cdrskin: ABORT : Handling started. Please do not press CTRL+C now.
cdrskin: ABORT : Trying to ignore any further signals
cdrskin: ABORT : Abort processing depends on speed and buffer size
cdrskin: ABORT : Usually it is done with 4x speed after about a MINUTE
cdrskin: URGE : But wait at least the normal burning time before any kill -9
cdrskin: ABORT : Drive is released and library is shut down now.
cdrskin: ABORT : Program done. Even if you do not see a shell prompt.
report its SCSI commands to a log file named
/tmp/libburn_sg_command_log
..I notice that it would be better to insert
fflush(fp);
before the two occurences of
fpcount++;
telltoc test:
-----------------------------------------
12 00 00 00 ff 00 00 00 00 00
5a 00 2a 00 00 00 00 10 00 00
46 00 00 00 00 00 00 10 00 00
cdrskin test:
-----------------------------------------
12 00 00 00 ff 00 00 00 00 00
5a 00 2a 00 00 00 00 10 00 00
46 00 00 00 00 00 00 10 00 00
1e 00 00 00 00 00 ff bf 76 87
I understand this stall can be interrupted by Ctrl+C ?
Yes.
--
giulioo@pobox.com
Reply to: