Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Glossary
MoreInfo
Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
FAQ
Copyright Info
Terms of Use
Privacy Info
Disclaimer
WorkBoard
Thanks
Donations
Advertising
Masthead / Impressum
Your Account

Communication
Feedback
Forums
Private Messages
Surveys

Features
HOWTOs
News Archive
Submit News
Topics
User Articles
Web Links

Google
Google


The Web
linux-tutorial.info

Who's Online
There are currently, 209 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here

  

scgcheck



SYNOPSIS

       scgcheck [ options ]


DESCRIPTION

       Scgcheck  is  used  to  check  and  verify the Application
       Binary Interface of libscg.

       The device refers to scsibus/target/lun of the drive. Com­
       munication  on  SunOS is done with the SCSI general driver
       scg.  Other operating systems are using a library  simula­
       tion  of  this  driver.   Possible  syntax  is: dev= scsi­
       bus,target,lun or dev= target,lun.  In  the  latter  case,
       the  drive  has to be connected to the default SCSI bus of
       the machine.  Scsibus, target and lun are integer numbers.
       Some  operating  systems or SCSI transport implementations
       may require to specify a filename in  addition.   In  this
       case  the  correct  syntax for the device is: dev= device­
       name:scsibus,target,lun or dev= devicename:target,lun.  If
       the  name  of  the  device node that has been specified on
       such a system refers to exactly one SCSI device, a  short­
       hand  in  the  form  dev=  devicename:@  or  dev=  device­
       name:@,lun may be used instead  of  dev=  devicename:scsi­
       bus,target,lun.

       To  access  remote  SCSI  devices, you need to prepend the
       SCSI device name by a remote device indicator. The  remote
       device   indicator   is   either   REMOTE:user@host:  or
       REMOTE:host:
       A valid remote SCSI device name may be:  REMOTE:user@host:
       to     allow     remote     SCSI     bus    scanning    or
       REMOTE:user@host:1,0,0 to access the SCSI device  at  host
       connected to SCSI bus # 1,target 0 lun 0.

       To  make readcd portable to all UNIX platforms, the syntax
       dev=  devicename:scsibus,target,lun  is  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 a way to specify scsi­
       bus,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 con­
       figuration  of your machine.  If you have problems to fig­
       ure out what values for scsibus,target,lun should be used,
       try the -scanbus option of cdrecord.

              fication,  the filename is implementation specific.
              The correct filename in this case can be  found  in
              the system specific manuals of the target operating
              system.  On a FreeBSD system without  CAM  support,
              you   need   to   use   the  control  device  (e.g.
              /dev/rcd0.ctl).  A correct device specification  in
              this case may be dev=/dev/rcd0.ctl:@ .

              On  Linux,  drives  connected  to  a  parallel port
              adapter are mapped to a virtual SCSI bus. Different
              adapters  are  mapped  to different targets on this
              virtual SCSI bus.

              If no dev option is present, cdrecord will  try  to
              get the device from the CDR_DEVICE environment.

              If the argument to the dev= option does not contain
              the characters ',', '/', '@' or ':', it  is  inter­
              preted  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 sending SCSI commands.  If
              a  SCSI command fails due to a timeout, you may try
              to raise the default SCSI command timeout above the
              timeout  value  of the failed command.  If the com­
              mand runs correctly with a raised command  timeout,
              please report the better timeout value and the cor­
              responding 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
              increment the 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 -debug slows down the process and may
              be the reason for a buffer underrun.

       kdebug=#, kd=#
              Tell the scg-driver  to  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.


EXAMPLES


FILES


SEE ALSO

       cdrecord(1), readcd(1), mkisofs(1), scg(7).


NOTES

       When using scgckeck with the  broken  Linux  SCSI  generic
       driver.   You  should note that scgcheck uses a hack, that
       tries to emulate the  functionality  of  the  scg  driver.
       Unfortunately,  the  sg driver on Linux has several severe
       bugs:

       ·      It cannot see if a SCSI command could not  be  sent
              at all.

       ·      It  cannot  get the SCSI status byte.  Scgcheck for
              that reason cannot report failing SCSI commands  in
              some situations.

       ·      It cannot get real DMA count of transfer.  Scgcheck
              cannot tell you if there is an DMA residual  count.

       ·      It  cannot  get number of bytes valid in auto sense
              data.  Scgcheck cannot 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 error
              CDB:  00 20 00 00 00 00
              status: 0x2 (CHECK CONDITION)
              Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 25 00 00 00 00 00
              Sense Key: 0x5 Illegal Request, Segment 0
              Sense Code: 0x25 Qual 0x00 (logical unit not supported) Fru 0x0
              Sense 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 call from the view of  the  ker­
       nel.  It  usually is: I/O error unless other problems hap­
       pen. The next words contain a short  description  for  the
       SCSI command that fails. The rest of the line tells you if
       there were any problems for the transport of  the  command
       The fifth line is the error text  for  the  sense  key  if
       available,  followed  by  the  segment number that is only
       valid if the command was a copy command. If the error mes­
       sage  is  not directly related to the current command, the
       text deferred error is 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 tables  in
       scsierrs.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  command and text for several error flags.
       The block number may not be valid.

       The eight line reports the timeout set up for this command
       and the time that the command realy needed to complete.


BUGS


CREDITS


MAILING LISTS


AUTHOR

       Joerg Schilling
       Seestr. 110
       D-13353 Berlin
       Germany

       Additional information can be found on:
       http://www.fokus.fhg.de/usr/schilling/cdrecord.html

       If you have support questions, send them to:

       cdrecord-support@berlios.de
       or other-cdwrite@lists.debian.org

       If you have definitely found a bug, send a mail to:

       cdrecord-developers@berlios.de
       or schilling@fokus.fhg.de

       To subscribe, use:

       http://lists.berlios.de/mailman/listinfo/cdrecord-develop­
       ers
       or  http://lists.berlios.de/mailman/listinfo/cdrecord-sup­
       port

Joerg Schilling            Version 2.0                SCGCHECK(1)
  
Show your Support for the Linux Tutorial

Purchase one of the products from our new online shop. For each product you purchase, the Linux Tutorial gets a portion of the proceeds to help keep us going.


Login
Nickname

Password

Security Code
Security Code
Type Security Code


Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!


Amazon Wish List

Did You Know?
You can help in many different ways.


Friends



Tell a Friend About Us

Bookmark and Share



Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.09 Seconds