Download Inquisitor for free. Mature and proven hardware testing and certification system, suitable for both enterprise and home use, customizable, modular and available in both serverless Live CD/DVD format and server-controlled network boot production system. Contains: Web-based SentriLock SentriCard® Utility v4.0.18, latest SCR USB Card reader driver SentriLock SentriCard® Utility v4 Installation Guide for Windows® (1 MB) This PDF file contains the installation instructions for the SentriLock SentriCard® Utility v4.

1. Driver Download Nvidia
2. Inq Driver Download Windows 10
3. Inq Driver Download Windows 10
4. Inq Driver Download App
5. Inq Driver Download Pc
6. Driver Downloads For Windows 7

Coverage of breaking news and current headlines from the Philippines and around the world. Top stories, photos, videos, detailed analysis and in-depth reporting.

Introduction
Utilities
1. dd variants
2. Scanning and mapping
3. SCSI support
4. Timing and testing
5. Example programs
6. Miscellaneous
Notes
Download
Programs from other sources

Introduction

The sg3_utils and sg_utils are two closely related packages ofutilitiesthat send SCSI commands to Linux devices. As well as devices on SCSItransports (e.g. Fibre channel and the SCSI parallel interface) manyother devices use SCSI command sets. Examples are ATAPI cd/dvd writersand sATA disks (typically via a translation layer or bridge device).The SCSI command set is divided into what are called 'primary' commands(e.g. SPC-3) and device class specific sets (e.g. SBC-2 for disks andMMC-4 for cd/dvd devices). SCSI command sets and transportsdefinitions can be found at www.t10.org.
The maindifference between the two packages is the linux kernel series thatthey target:sg_utils for the lk 2.2 (with some support for the lk 2.0 series);sg3_utils for the lk 2.4 and 2.6 series. The sg3_utils package is stillin active development while sg_utils is in maintenance mode. Thisdocument describesversion 1.12 for sg3_utils and version 1.02 for sg_utils.
In the linux kernel 2.0, 2.2 and 2.4 series these utilities must beused with the SCSI generic (sg) driver device names (e.g. /dev/sg0). Inthe lk 2.6 series almost all of the utilities can be used with theprimary device names as well (e.g. /dev/sda, /dev/sdc0, /dev/st0 and/dev/hdd (if it is an ATAPI device)). The SCSI generic (sg) interfacestill represents a cleaner interface than the primary device names.This occurs since the drivers behind primary device names have theirown policies and may interfere with error processing and run their ownstate machines (e.g. the cdrom driver interferes with attempts toprevent media removal with sg_prevent).

SCSI utility programs for Linux from other sources are listed andbriefly described inthe final section.

Utilities

Here is a (somewhat arbitrary) categorization of the utilities includedin the sg_utils and sg3_utils packages:

1. dd variants: sg_dd, sgp_dd, sgm_dd and sgq_dd
2. scanning and mapping: sg_scan, sg_map andscsi_devfs_scan
3. SCSI support: sg_inq, scsi_inquiry, sginfo,sg_readcap, sg_start, sg_whoami, sg_modes,sg_logs, sg_senddiag,sg_reset, sg_persist, sg_opcodes,sg_write_long, sg_read_long, sg_ses, sg_requests, sg_verify,sg_emc_trespass, sg_luns, sg_sync, sg_prevent, sg_get_config,sg_wr_mode, sg_rtpg and sg_reassign
   
4. timing and testing: sg_rbuf, sg_test_rwbuf, sg_read, sg_turs,and sg_debug
5. example programs: sg_simple1, sg_simple2,sg_simple3, sg_simple4, sg_runt_ex and sg_simple16
6. miscellaneous programs: isosize

Those utilities that are in bold typeface are in both sg_utils andsg3_utils; those in normal typeface are only found in sg3_utils; andthose in italics are only found in sg_utils. All utilitiesin the main directory have man pages; some utilities in thesubdirectories (e.g. archive,examples and utils) have man pages. In somecases the information in the man pages will be more up to date thaninformation in this page.

There is a brief description of each utility in the followingsections.

1. dd variants

The dd(1) command in Unix is used to copy data between filesand optionally convert it in the process. In Linux various types ofdevice files (e.g. /dev/sda and /dev/hda3) may beone (or both) of the files given to dd. Raw devices (in lk2.4 and a patch in the lk 2.2 series) can also be used with recent ddimplementations (that meet the alignment requirements). dd isvery useful for copying data and timing disk performance but cannottake a sg device as one of its files. Therefore there are severalvariants of dd in these packages that can interact with sgdevices. These utilities mimic the syntax and semantics of the ddcopy functionality but not its ability to convert data.

The dd variants support these command line arguments:
bs=<n> typically 512or 2048, must match device
ibs=<n> ifgiven must be the same as 'bs'
obs=<n> ifgiven must be the same as 'bs'
if=<name> read from thisfile or device, '-' (read from stdin)
of=<name> write to thisfile or device, '-' (write to stdout)
skip=<n> blockoffset to start reading 'if'
seek=<n> blockoffset to start writing 'of'
count=<n> number of 'bs' sized blocks tocopy from 'if' to 'of'

Extra options:
bpt=<n> blocks per transfer [per SCSI command] (default 128)
coe=<n> continue on error, 0->exit (def), 1->zero + continue
dio=<n> 1->select Direct IO, 0->indirect IO [sg3_utils only]
time=0|1 1->timetransfer and calculate throughput
cdbsz=6|10|12|16 select size of SCSI READ andWRITE command
blocks (default 10) [sg3_utils only]
sync=0|1 1-> doSYNCHRONIZE CACHE after transfer

All numeric arguments can be in decimal or hexadecimal (only insg3_utils). Hexadecimal values are prefixed with either '0x' or'0X'.Decimal argument accept these suffix multipliers:
'c', 'C' * 1
'b', 'B' * 512
'k' * 1024 [2 ^10]
'K' * 1000 [10^ 3]
'm' * 1048576 [2 ^ 20]
'M' * 1000000 [10 ^ 6]
'g' * 1073741824 [2 ^ 30]
'G' * 1000000000 [10 ^ 9]
't' * 1099511627776 [2 ^ 40] <skip, seek and countonly in sg3_utils>
'T' * 1000000000000 [10 ^ 12] <skip, seek and count only insg3_utils>

The 'skip' and 'seek' options lead to the use of the system commandlseek() to a byte offset when used on raw devices and normal files.For sg devices 64 bit block addresses are used in sg3_utils (32 bitblock addresses for sg_utils thus limiting accesses on disks with 512byte blocks to 1 TB). On 32 bit architectures the normal lseek() islimited to a signed 32 bit byte offset (i.e. 2 GB). These dd variantsbypass this limit by using Linux's _llseek() [while modern dd commandsuse read loops to 'walk' around the limit]. If 'count' is not giventhen the SCSI READ CAPACITY command (and, if necessary, its 16 bytevariant in sg3_utils)will be used (on sg devices) if appropriate.Alternatively (in sg3_utils version 1.07 and later) if 'count' is notgiven and a block device (or partition) is specified (e.g. /dev/hdb or /dev/sda2) then the blockdevice (or partition) sector count is used. Diskpartition information can be found with a command like 'fdisk -ul/dev/sda'.

The dd variants are careful to send all informative and error outputto stderr so that it doesn't interfere with stdout which may beselected for output (by either not giving a 'of=' argument or giving'of=-'). Since the outputfile is often /dev/null,a '.' is taken asmeaning /dev/null: hencethese two arguments are synonymous:'of=/dev/null' and 'of=.'.

sg_dd

This utility will accept sg and raw devices as well as any file typesthat dd will accept as its input or output file. It isimplemented in a similar fashion to dd in that it reads from theinput file and then writes to the output file in sequence and in asingle thread of execution.

Driver Download Nvidia

sg_dd requires that the 'bs'argument matches the block size of the physical device. [For disksthis is usually 512 bytes.] It has an additional argument forcontrolling the number of blocks read or written per transfer called'bpt' whose default is 128.

A command such as:
$ dd if=/dev/sda skip=278 of=raw.dat bs=512count=45
is equivalent to:
$ sg_dd if=/dev/sg0 skip=278 of=raw.dat bs=512count=45
if /dev/sda and /dev/sg0 refer to the same device.

sgp_dd

This utility uses POSIX threads to run multiple worker threads eachdoing repeated read write sequences. There is synchronization to makesure that IO operations on the input and output files are started insequence. In cases where the input and output file are SCSI disks withthe similar IO speeds this utility can give speed benefits.

The sgp_dd utility has these command line arguments inaddition to those accepted by sg_dd:
Extra options:
thr=<n> is number of threads, mustbe > 0, default 4, max 16
deb=<n> 0->none (def), >0-> varying degrees of debug

The sg_dd and sgp_dd commands are also very usefulforstress testing and measuring performance. Timing a 100 Megabyte readtime from block 0 of a disk becomes:
$ time sg_dd if=/dev/sg0 of=/dev/null bs=512 count=200K

sgm_dd

This program is very similar to sg_dd and takes the same arguments.The only difference is that it uses mmap-ed IO instead of indirect IO.Since mmap-ed IO was introduced in sg version 3.1.22 (lk 2.4.17) thenthis command will not work on earlier versions. If either 'if' or 'of'is a sg device then mmap-ed IO will be use on it. If both 'if' and 'of'are sg devices then mmap-ed IO is used on the 'if' sg device and normal(indirect) IO is used on the 'of' sg device. The program is onlyavailable in sg3_utils.

sgq_dd

This program is very similar to sgp_dd and takes the same arguments.Instead of using POSIX threads for parallelism, sgq_dd usesnon-blocking file descriptors, polling and a state machine.Performance is similar. The program is only available in the archivedirectory of sg3_utils (and needs to be build separately - it is notnormally built or installed).

2. Scanning and mapping

sg_scan

This rather simple but useful program scans the sg devices and outputsinformation about each device found and optionally does an INQUIRY. Itis roughly similar to the command: 'cat /proc/scsi/scsi'. Both of thesecommands will show the same number of devices in the same order. [Anexception to the last statement occurs when 'add-single-device' and'remove-single-device' are used.]

Example: given these 3 SCSI devices:
$ cat /proc/scsi/scsi
Attached devices:
Host: scsi1 Channel: 00 Id: 00 Lun: 00
Vendor: SEAGATE Model:ST318451LW Rev: 0003
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi2 Channel: 00 Id: 04 Lun: 00
Vendor: PIONEER Model: DVD-ROM DVD-303 Rev: 1.10
Type: CD-ROM ANSI SCSI revision: 02
Host: scsi2 Channel: 00 Id: 06 Lun: 00
Vendor: YAMAHA Model:CRW4416S Rev: 1.0g
Type: CD-ROM ANSI SCSI revision: 02

then the output from sg_scan is thus:
$ sg_scan
/dev/sg0: scsi1 channel=0 id=0 lun=0 type=0
/dev/sg1: scsi2 channel=0 id=4 lun=0 type=5
/dev/sg2: scsi2 channel=0 id=6 lun=0 type=5

INQUIRY data can be added to that output with the '-i' option

sg_map

This utility shows the mapping of the available sg device names to thecorresponding name of the sd, sr, st or osst device. Some sg devicessuch as scanners don't have a corresponding sd, sr, st or osst devicename. The sg_map output for the SCSI devices shown in the previoussection is probably:
$ sg_map
/dev/sg0 /dev/sda
/dev/sg1 /dev/scd0
/dev/sg2 /dev/scd1

scsi_devfs_scan

This is a utility for doing a directory scan on a system running devfsto identify SCSI (and optionally IDE) devices. Various information(including an INQUIRY) can be listed for each found device. Insg3_utils this utility ha been moved to the archive directory.

3. SCSI support

sg_inq

This utility executes a SCSI INQUIRY command on the given device andinterprets the results according to SPC-3 document. The term 'standardINQUIRY' refers to a INQUIRY cdb that neither requests a Vital ProductData (VPD) page nor Command Detail information (via the CmdDtbit). Here is the output from a standard INQUIRY. Actually the lastentry ('Unit serial number') comes from the VPD page [0x80] of the samename if it is available. Older SCSI devices often put a serial numberin a vendor specific area of a standard INQUIRY response (typicallybetween bytes 36 and 55 inclusive).
$ sg_inq /dev/sda
standard INQUIRY:
PQual=0 Device_type=0 RMB=0 version=0x03 [SPC]
[AERC=0] [TrmTsk=0] NormACA=0 HiSUP=1 Resp_data_format=2
SCCS=0 ACC=0 TGPS=0 3PC=0 Protect=0
BQue=0 EncServ=0 MultiP=0 MChngr=0 [ACKREQQ=0] Addr16=1
[RelAdr=0] WBus16=1 Sync=1 Linked=1 [TranDis=1] CmdQue=1
Clocking=0x3 QAS=0 IUS=0
length=144(0x90) Peripheral device type: disk
Vendor identification:SEAGATE
Product identification:ST318451LW
Product revision level: 0003
Unit serial number:xxxxxxxxx
VPD pages are available from an INQUIRY, either in hex (e.g. with theoption '-p=<vpd_page_hex>') or, in some cases, in decoded form.The importance of VPD pages is illustrated by two being made mandatoryin latter versions of SPC-3: Supported VPD pages [0x0] and the DeviceIdentification page [0x83]. Several VPD pages are now decoded. The'Supported VPD pages' page [0x0] is decoded when the '-e' option isgiven [without the '-p=<vpd_page_hex>' option] (sg3_utils >=v1.08). The Device Identification page [0x83] is decoded when the '-i'option is given (sg3_utils >= v1.07). The Extended INQUIRY page[0x86] is decoded when the '-x' option is given (sg3_utils >=v1.09). The SCSI Ports page [0x88] is decoded when the '-s' option isgiven (sg3_utils >= v1.11). The EMC (i.e. vendor) specific Unit PathReport page [0xc0] is decoded when the '-P' option is given (sg3_utils>= v1.09). Here is an example of the output from requesting the'Supported VPD pages' page:
$ sg_inq -e /dev/sg1
VPD INQUIRY, page code=0x00:
[PQual=0 Peripheral device type: disk]
Supported VPD pages:
0x0 Supported VPD pages
0x80 Unit serial number
0x83 Device identification
There are still many (older and non-native) SCSI devices that ignorethe EVPD bit (enable VPD in the INQUIRY cdb) and simply return astandard INQUIRY response. Various checks are made on the response whena VPD page is requested and if they fail an appropriate message isoutput.

Inq Driver Download Windows 10

The '-c' and '-cl' options permit supported SCSI commands to belistedby using the CmdDt bit in an INQUIRY request. However SPC-3 hasobsoleted this feature and introduced the new REPORT SUPPORTEDOPERATIONCODES SCSI command (see the sg_opcodesutility introduced in sg3_utils version 1.07). Not many SCSI devicessupport the new command yet.
In sg3_utils version 1.08 a '-d' switch has been added to decodeversion descriptors. A standard INQUIRY response optionally contains upto 8 of these. For example a SCSI disk might have 4 versiondescriptors: SAM-2, SPC-2, SBC and SPI-4. SAM-2 is generalarchitectural compliance, SPC-2 for SCSI primary (i.e. common) commandssupported, SBC for SCSI block command set and SPI-4 indicates Ultra 320support. Here is an example of the version descriptors on a disk:
$ sg_inq -d /dev/sdb
standard INQUIRY:
PQual=0 Device_type=0 RMB=0 version=0x03 [SPC]
[AERC=0] [TrmTsk=0] NormACA=0 HiSUP=0 Resp_data_format=2
SCCS=0 ACC=0 TGPS=0 3PC=0 Protect=0
BQue=0 EncServ=0 MultiP=0 MChngr=0 [ACKREQQ=0] Addr16=1
[RelAdr=0] WBus16=1 Sync=1 Linked=1 [TranDis=1] CmdQue=1
Clocking=0x0 QAS=0 IUS=0
length=96(0x60) Peripheral device type: disk
Vendor identification:FUJITSU
Product identification:MAM3184MP
Product revision level: 0106
Unit serial number:xxxxxxxxx
Version descriptors:
SAM-2 (noversion claimed)
SPI-3T10/1302-D revision 10
SPC ANSIX3.301:1997
SBC T10/0996-Drevision 08c

scsi_inquiry

This program demonstrates the use of the SCSI_IOCTL_SEND_COMMAND ioctlto send a SCSI INQUIRY command. That ioctl() is supported by the SCSIsub system mid level and so is common to all sd, sr, st (osst) and sgdevices. In sg3_utils this utility has been moved to the archive directory.

sginfo

This is a program for reporting MODE SENSE information about a SCSIdevice. It is a rework of the scsiinfo program written by EricYoungdale. The difference is that sginfo obtains theinformation using the sg interface. The 'sginfo -l' command shows allSCSI block and character devices (i.e. sg devices) and the mappingbetween them. Disk defect sector lists are also available. [Theoriginal scsiinfo program can only report the first 4 KB (i.e.page size) of a defect list).]

sg_readcap

This call performs a READ CAPACITY command on the given device. For adisk this should yield the sector size and the number of sectors. Thegiven name may be any SCSI device (i.e. not just sg devices).

sg_start

This is a program that has been provided by Kurt Garloff<garloff@suse.de> for spinning up (or down) disks.

sg_modes

Outputs MODE SENSE pages and does some decoding (mainly into hex).

sg_logs

Outputs LOG SENSE pages. These pages contain error counters, start-stopcycle counters, the current device temperature and the 'informationalexception' log. 'Informational Exception' is SCSI standardese for'S.M.A.R.T.' information.

sg_senddiag

This utility is mainly used to request the device to perform aself-test. Later devices can do both foreground and background, shortand extended self tests. An option of this command list the time takenby the previous extended self test.

sg_whoami

This program prints out the scsi adapter number, channel, scsi id andlun (and optionally does a read capacity) on the given sg device. Itis only available in the sg_utils package.

sg_reset

This program exercises the SCSI device/bus/host reset capability. It issupported by the sg driver in lk 2.2.16 and beyond but associatedSCSI mid level driver changes have not been accepted into thestandard kernel at this time (but may be shortly: lk 2.4.18). Somedistributions contain the patch to the mid level that activates thisfeature (see the FAQ on the main page for these patches).

sg_persist

This utility accesses the Persistent Reservation In and Out SCSIcommands. Persistent reservations are defined in SPC-3 and replace theReserve and Release SCSI commands. This is a relatively low levelfacility that could be used to probe a storage network that alreadyuses persistent reservations.

sg_opcodes

This utility invokes the REPORT SUPPORTED OPERATION CODES SCSI commandto list all commands that a logical unit supports or to examine thesupport for a specific command. This relatively new SPC-3 commandwas introduced in February 2002. It replaces the now obsolete 'CmdDt'facility in the INQUIRY command. When the '-t' command line option isused it invokes the REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS SCSIcommand and outputs the response.

sg_write_long

This utility invokes the WRITE LONG(10) SCSI command. This will writethe given data (by default 0xff bytes)to the given logical block address on a disk. This will overwrite theuser data component (typically 512 bytes), ECC and associated data.This can beuseful for creating MEDIUM ERRORs for testing purpose. A normalwrite (e.g. with sg_dd) to thesame logical block address will remove the MEDIUM ERROR condition.

sg_read_long

This utility invokes the READ LONG(10) SCSI command. This utility canbe used to view damaged blocks; also it can be used in conjunction withsg_write_long. The '--correct'option can be used to (attempt to) correct the returned data componentgiven the associated ECC data.

sg_ses

This utility is designed primarily to query a processor (typically in astorage array) that supports SCSI Enclosure Services (see SES-2 at http://www.t10.org ). There is a crudefacility to send controls to a SES device.

sg_requests

This utility issues a SCSI REQUEST SENSE command to the given device.Optionally descriptor sense format can be requested.

sg_verify

This utility allows a SCSI block device (e.g. a disk) to be verified.It uses the SCSI VERIFY (10) command for this purpose.

sg_emc_trespass

This utility is specific to certain EMC products. It allows theownership of a LUN to be changes from some other service processor tothe processor issuing this utility.

sg_luns

This utility sends a SCSI REPORT LUNS command to the given device andlists the luns returned. If the '--decode' option is given then the 64bit luns are decoded according to section 4.9 of the SAM-3 (rev 14)draft standard.

sg_sync

This utility sends a SCSI SYNCHRONIZE CACHE command to the givendevice. This command is typically used before a storage device isremoved, taken offline or powered down.

sg_prevent

This utility sends a SCSI PREVENT ALLOW MEDIUM REMOVAL command to thegiven device. This command is currently defined in SPC-3 and the MMCseries which means that it has a slightly different meaning for cd/dvddevices from other SCSI devices that support removable media.

sg_get_config

This utility sends a SCSI GET CONFIGURATION command to the givendevice. This command is only defined for MMC devices (i.e. cd/dvddevices) and yields features and profiles of a device (e.g. whetherDVD+R DL discs can be written) and the media currently in the device.

sg_wr_mode

This utility modifies mode pages with the SCSI MODE SELECT command. Itcan use the existing contents of the mode page (fetched by a SCSI MODESENSE command) as a template than new values are masked into as the newmode page contents. Views mode pages as a series of bytes. [sginfo canalso modify mode pages but only standard one through an awkwardinterface.]

sg_rtpg

This utility sends a SCSI REPORT TARGET PORT GROUPS command to thegiven device.

sg_reassign

This utility sends a SCSI REASSIGN BLOCKS command to the given devicewhich should be a disk. Blocks that report unrecoverable errors can bereassigned (with potential loss of data). Blocks with recoverableerrors which are not automatically reassigned (by the AWRE and ARREbits in the 'read write error recovery' mode page) can also bereassigned (with no loss of data).

4. Timing and testing

sg_rbuf

This utility can be used to test SCSI bus throughput. It uses the SCSIRead Buffer command to get data from the data buffer on the SCSI deviceinto the user space. The author uses it on his mounted root partitiondisk without any ill effects. With the '-q' switch the final transferfrom the kernel DMA buffers to the user space is by-passed. There isalso a '-d' switch for direct IO and a '-m' switch for mmap-ed IO. A'-t' switch times the operation and calculates a MB/sec throughputfigure.

sg_test_rwbuf

This test program has been written by Kurt Garloff<garloff@suse.de>. It issues read and write commands to adevice's buffer (typically the disk cache in the drive electronics)and calculates checksums.

sg_read

This program reads multiple blocks of data starting at the same logicaladdress. It can time the transfers (potentially ignoring the firstissued command) and calculate a MB/sec figure. [In keeping with mostdisk manufacturers, 'MB' is 1,000,000 bytes in this context.] Itscommand line syntax is modelled on sg_dd. It allows SCSIdevice, SCSI bus bandwidth and the SCSI sub-system throughput to bemeasured. This can be done in 3 modes: normal transfer to user space,direct IO or mmap-ed IO.

sg_turs

This command executes a user specified number of TEST UNIT READYcommands on the given device. This can be used to time SCSI commandoverhead.

sg_debug

In the sg_utils package, this program prints out the internal state ofthe sg driver at the instant when it is called. In the sg3_utilspackage is simply prints out a short message advising the user toexecute the command 'cat /proc/scsi/sg/debug' (rather than call thisprogram).

5. Example programs

There are two simple programs for first time users that send SCSIINQUIRY and TEST UNIT READY commands to a sg device. They are called sg_simple1and sg_simple2. The latter program has simpler but more basicSCSI error processing while the former uses 'sg_err.[hc]' discussedbelow. The sg_simple3 program demonstrates user space scattergather offered by the sg_io_hdr interface in the sg version 3driver. The sg_simple4 program demonstrates mmap-ed IO onthe response of an INQUIRY. The sg_simple16 program does aREAD_16 (a 16 byte long SCSI
command) which is available on kernel >= lk 2.4.15 (and only onadapters that support it).

sg_runt_ex is a program demonstrating run time selection ofthe sg driver and using extra features when available. It is meantto be example code for those who base their applications on sg. Itperforms INQUIRY and TEST UNIT READY commands. Code compiled under2.0, 2.2 or 2.3 series kernels may be run on any of the 3 serieswith extra features available if the run time kernel is >= 2.2.6 .This program is only available in the sg_utils package.

6. Miscellaneous

isosize

This utility gives the number of bytes in an iso9660 file system. It isa rewrite by Andries Brouwer<Andries.Brouwer@cwi.nl> of autility that first appeared in the cdwrite package but is nowdifficult to obtain. Note that the value given by isosize is usually2 or more blocks less than the READ CAPACITY SCSI command yields ona CD-ROM (due to run out sectors). This utility has been placed in thearchive directory since it can now be found in the util-linux-2.10spackage (and later).

Notes

Starting with sg3_utils-1.09 a library called libsgutils is built andis required by all utilities. The library is made up of two sourcefiles: sg_lib.c and sg_cmds.h . The sg_lib.c file contains SCSIcommand,sense key and additional sense code strings and various related helperfunctions. The sg_cmds.c file contains low level wrapper functions forcommonly used SCSI commands. The library is built both as a sharedobject and a static library. The binary rpm package only contains theshared library while the sg3_utils-devel rpm package contains thestatic library, sg_lib.h and sg_cmds.h . If users do not want libraries(shared or static) than they can refer to the 'lib_no_lib' subdirectoryin the tarball which contains 'no_lib' versions of the Makefile and therpm 'spec' file.
Many of the utilities in the sg3_utils package use the SG_IO ioctl(rather than the older write()/read() interface) in the sg driver. Inthe lk 2.6 series the SG_IO ioctl (or at least a strippeddown version of it) has been implemented in the block subsystem. Thatmeans that commands that previously only worked on sg device names willnow work on block device names as well (e.g. 'sg_inq /dev/sda'). To usethis facility safely version sg3_utils-1.02 or later should be used.Note that SCSI tape devices (both st and osst device drivers) are chardevices and support the SG_IO ioctl from lk 2.6.6 onwards.

See the notes about header file problems in the README file insideeach package.

Inq Driver Download Windows 10

Download

Various tarballs that include the source, a README, CHANGELOG, INSTALLand a Makefile can be found in the sg_utils tables on the mainpage (link at the bottom of this page). There are also source andi386 binary rpm and deb packages available. Both sg3_utils and theolder sg_utils canbe found on http://freshmeat.net .

Programs from other sources

scu

The SCSI Command Utility (SCU) implements various SCSI commandsnecessary for normal maintenance and diagnostics of SCSIperipherals. Some of its features include: formatting, scanning for(and reassigning) bad blocks, downloading new firmware, executingdiagnostics and obtaining performance information. It is available onseveral Unix platforms (and NT), however it is only currently availablein binary form. See www.bit-net.com/~rmiller/scu.htmlfor more details.

dt

The Data Test (DT) program is modelled on dd's syntax but dt cando a lot more than sequential copies. It is a comprehensive data testprogram for SCSI devices such as disks, tapes and cdrom/dvds. It isavailable on several Unix platforms (and NT), and its source isavailable (unlike its stable mate scu discussed earlier). See www.bit-net.com/~rmiller/dt.htmlfor more details. Both scu and dt are written by RobinT. Miller <Robin.Miller@compaq.com>

scsidev

Kurt Garloff <garloff@suse.de> describes this utility thus: 'Thisprogram scans the SCSI bus and creates device nodes in /dev/scsi/,which have a naming corresponding to their SCSI IDs and LUNs, justlike with devfs. (The devfs has no notion of host adapter IDs,scsidev is better here.) Furthermore, the devices are inquired totell their names and serial numbers. Those can be compared with theentries in a database /etc/scsi.alias and device nodes correspondingto these entries are being built. So,this will even work if you changethe SCSI IDs of a device, where the devfs approach would fail'. Formore information see: www.garloff.de/kurt/linux/scsidev. He also has the useful rescan-scsi-bus.sh script at the samelocation.

ddrescue

This is another utility from Kurt Garloff <garloff@suse.de>for rescuing damage media. It is a variant of dd that will continuepassed errors on the input file. It is applicable to any device thatcan be read by dd (e.g. IDE and SCSI disks, cds and tapes). For moreinformation see: www.garloff.de/kurt/linux/ddrescue

mapscsi

Michael Clark <michael@metaparadigm.com> describes his utilitythus: 'mapscsi is a small utility that creates a consistent mappingto Linux scsi devices. mapscsi achieves this by creating symboliclinks to linux scsi disk devices after scanning all scsi disk devices,finding out their host, channel, id, lun, pci location (if available),Fibre Channel world wide node and port names, loop and port ids (withqla2x00 v4.46.5 driver) vendor, product and serial number details andusing this information plus a mapping rules file containing devicetemplates to dynamically create link names'. For more information see: http://gort.metaparadigm.com/mapscsi.

Inq Driver Download App

scsimap

Steve Cameron <smcameron@yahoo.com> has the following descriptionat his site:

This is a utility to create and maintain symbolic links mapping apredictable set of names to the rather unpredictable names used bylinux for disk devices. For example, you might map:
/dev/mydisk1 -> /dev/sda1
/dev/mydisk2 -> /dev/sdb1
/dev/mydisk3 -> /dev/sdc1
If you removed the disk corresponding to /dev/sdb1, then on reboot,/dev/sdc1 will become /dev/sdb1, and /dev/sdc1 will be gone. and yourfstab will be wrong, etc. (Especially problematic on a SAN). scsimapwill maintain the mapping so that after the reboot, /dev/mydisk3 ->will point to /dev/sdb1 and /dev/mydisk2 will be gone. scsimap alsohandles later generation Compaq array controllers (those which usethe cciss driver.)

See: www.geocities.com/smcameron.

smartsuite

Inq Driver Download Pc

This is a package that supports S.M.A.R.T. capabilities built intomodern IDE and SCSI-3 disks. Self-Monitoring, Analysis and ReportingTechnology (S.M.A.R.T.) is described at www.pc.ibm.com/us/infobrf/ibsmart.html.For smartsuite see sourceforge.net/projects/smartsuite.

smartmontools

This project seems to have taken over from the aforementionedsmartsuite which is currently not actively maintained. See http://smartmontools.sourceforge.net.

scsirastools

'This project includes changes that enhance the Reliability,Availability and Serviceability (RAS) of the drivers that arecommonly used in a Linux software RAID-1 configuration. Otherefforts have been made to enable various common hardware RAIDadapters and their drivers on Linux.' See http://scsirastools.sourceforge.net. The pacakage contains some low level scsi utilities including sgdskflto load disk firmware, sgmode to get and set mode pages, sgdefectsto read primary and grown defect lists and sgdiag to performformat and other test functions.

SeaTools

SeaTools is a freely available (binary, not source) utility for diskdiagnostics from Seagate which is a disk manufacturer. It can be foundat http://www.seagate.com undersupport. They have both a command line and a graphical utility. Some of the facilities will work on any SCSI disks while othersare Seagate specific. Selt tests, mode page settings and formats (todifferent block sizes) are amongst the facilities available.

devlabel

Driver Downloads For Windows 7

Devlabel is 'a small userspace app which maps symlinks to underlyingdisk names. It uses [INQUIRY VPD] Page83/Page80 data to track thetrue locations of disks even if their hd/sd name changes and simplyupdates the symlink to point to the right place.' Sysfs support for thelk 2.6 series and support for multi-path configurations is on theauthor's 'to do' list. See http://www.lerhaupt.com/linux.html.

plscsi

This utility allows arbitrary SCSI commands to be sent to a device. Seehttp://members.aol.com/plscsi.

Return to main page.

Last updated: 21st January 2005, 17:00