MAN page from Other cdrecord-1.11.a28-33.i586.rpm
SCGCHECK
Section: Schily\'s USER COMMANDS (1)
Updated: Version 1.10
Index NAME
scgcheck - check and validate the ABI of libscg
SYNOPSIS
scgcheck[
options]
DESCRIPTION
Scgcheckis used to check and verify the Application Binary Interface of libscg.
Thedevicerefers toscsibus/target/lunof the drive. Communication on SunOSis done with the SCSI general driverscg.Other operating systems are using a library simulation of this driver.Possible syntax is:dev=scsibus,target,lunordev=target,lun.In the latter case, the drive has to be connected to the default SCSI bus of the machine.Scsibus,target and lunare integer numbers. Some operating systems or SCSI transport implementations may require tospecify a filename in addition.In this case the correct syntax for the device is:dev=devicename:scsibus,target,lunordev=devicename:target,lun.If the name of the device node that has been specified on such a systemrefers to exactly one SCSI device, a shorthand in the formdev=devicename:@ordev=devicename:@,lunmay be used instead ofdev=devicename:scsibus,target,lun.
To access remote SCSI devices, you need to prepend the SCSI device name bya remote device indicator. The remote device indicator is eitherREMOTE:userAATThost:or.BIREMOTE:host:
A valid remote SCSI device name may be:REMOTE:userAATThost:to allow remote SCSI bus scanning orREMOTE:userAATThost:1,0,0to access the SCSI device at hostconnected to SCSI bus # 1,target 0 lun 0.
To make readcdportable to all UNIX platforms, the syntaxdev=devicename:scsibus,target,lunis preferred as is hides OS specific knowledge about device names from the user.A specific OS must not necessarily support a way to specify a real device file name nor away to specify scsibus,target,lun.
Scsibus 0 is the default SCSI bus on the machine. Watch the boot messages for more information or look into /var/adm/messages for more information about the SCSI configuration of your machine.If you have problems to figure out what values for scsibus,target,lunshould be used, try the -scanbusoption of cdrecord.
OPTIONS
- -version
- Print version information and exit.
- dev=target
- Sets the SCSI target default for SCSI Bus scanning test, see notes above.This allows e.g. to specify to use Solaris USCSI or remote SCSI for the bus scanning case.
For the non bus scanning case, a typical device specification isdev=6,0.If a filename must be provided together with the numerical target specification, the filename is implementation specific.The correct filename in this case can be found in the system specificmanuals of the target operating system.On a FreeBSDsystem without CAMsupport, you need to use the control device (e.g./dev/rcd0.ctl).A correct device specification in this case may bedev=/dev/rcd0.ctl:@.
On Linux, drives connected to a parallel port adapter are mappedto a virtual SCSI bus. Different adapters are mapped to differenttargets on this virtual SCSI bus.
If no devoption is present, cdrecordwill try to get the device from the CDR_DEVICEenvironment.
If the argument to thedev=option does not contain the characters ',', '/', '@' or ':',it is interpreted as an label name that may be found in the file/etc/default/cdrecord (see FILES section).
- timeout=#
- Set the default SCSI command timeout value to # seconds.The default SCSI command timeout is the minimum timeout used for sendingSCSI commands.If a SCSI command fails due to a timeout, you may try to raise thedefault SCSI command timeout above the timeout value of the failed command.If the command runs correctly with a raised command timeout,please report the better timeout value and the corresponding command to the author of the program.If no timeout option is present, a default timeout of 40 seconds is used.
- debug=#, -d
- Set the misc debug value to # (with debug=#) or incrementthe misc debug level by one (with -d). If you specify-dd,this equals to debug=2.This may help to find problems while opening a driver for libscg.as well as with sector sizes and sector types.Using-debugslows down the process and may be the reason for a buffer underrun.
- kdebug=#, kd=#
- Tell the scg-driverto modify the kernel debug value while SCSI commands are running.
- -silent, -s
- Do not print out a status report for failed SCSI commands.
- -v
- Increment the level of general verbosity by one.This is used e.g. to display the progress of the process.
- -V
- Increment the verbose level with respect of SCSI command transport by one.This helps to debug problemsduring the process, that occur in the CD-Recorder. If you get incomprehensible error messages you should use this flagto get more detailed output.-VVwill show data buffer content in addition.Using-Vor-VVslows down the process.
- f=file
- Specify the log file to be used instead of check.log.
EXAMPLES
FILES
SEE ALSO
cdrecord(1),
readcd(1),
mkisofs(1),
scg(7).
NOTES
When using scgckeckwith the broken Linux SCSI generic driver.You should note that scgcheckuses a hack, that tries to emulate the functionality of the scg driver.Unfortunately, the sg driver on Linuxhas several severe bugs:
- *
- It cannot see if a SCSI command could not be sent at all.
- *
- It cannot get the SCSI status byte. Scgcheckfor that reason cannot report failing SCSI commands in somesituations.
- *
- It cannot get real DMA count of transfer. Scgcheckcannot tell you if there is an DMA residual count.
- *
- It cannot get number of bytes valid in auto sense data.Scgcheckcannot tell you if device transfers no sense data at all.
- *
- It fetches to few data in auto request sense (CCS/SCSI-2/SCSI-3 needs >= 18).
DIAGNOSTICS
A typical error message for a SCSI command looks like:
readcd: I/O error. test unit ready: scsi sendcmd: no errorCDB: 00 20 00 00 00 00status: 0x2 (CHECK CONDITION)Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 25 00 00 00 00 00Sense Key: 0x5 Illegal Request, Segment 0Sense Code: 0x25 Qual 0x00 (logical unit not supported) Fru 0x0Sense flags: Blk 0 (not valid)cmd finished after 0.002s timeout 40s
The first line gives information about the transport of the command.The text after the first colon gives the error text for the system callfrom the view of the kernel. It usually is:
I/O errorunless other problems happen. The next words contain a short description forthe SCSI command that fails. The rest of the line tells you if there wereany problems for the transport of the command over the SCSI bus.
fatal errormeans that it was not possible to transport the command (i.e. no device presentat the requested SCSI address).
The second line prints the SCSI command descriptor block for the failed command.
The third line gives information on the SCSI status code returned by the command, if the transport of the command succeeds. This is error information from the SCSI device.
The fourth line is a hex dump of the auto request sense information for the command.
The fifth line is the error text for the sense key if available, followedby the segment number that is only valid if the command was acopycommand. If the error message is not directly related to the current command,the textdeferred erroris appended.
The sixth line is the error text for the sense code and the sense qualifier if available.If the type of the device is known, the sense data is decoded from tablesinscsierrs.c .The text is followed by the error value for a field replaceable unit.
The seventh line prints the block number that is related to the failed commandand text for several error flags. The block number may not be valid.
The eight line reports the timeout set up for this commans and the timethat the command realy needed to be finished.
BUGS
CREDITS
MAILING LISTS
AUTHOR
Joerg SchillingSeestr. 110D-13353 BerlinGermany
Additional information can be found on:
http://www.fokus.gmd.de/usr/schilling/cdrecord.html
If you have support questions, send them to:
cdrecord-supportAATTberlios.de
orother-cdwriteAATTlists.debian.org
Of you definitly found a bug, send a mail to:
cdrecord-developersAATTberlios.de
orschillingAATTfokus.gmd.de
To subscribe, use:
http://lists.berlios.de/mailman/listinfo/cdrecord-developers
orhttp://lists.berlios.de/mailman/listinfo/cdrecord-support
Index
- NAME
- SYNOPSIS
- DESCRIPTION
- OPTIONS
- EXAMPLES
- FILES
- SEE ALSO
- NOTES
- DIAGNOSTICS
- BUGS
- CREDITS
- MAILING LISTS
- AUTHOR
This document was created byman2html,using the manual pages.