1 '\" te
   2 .\" Copyright (c) 2009 Sun Microsystems, Inc.  All Rights Reserved.
   3 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License").  You may not use this file except in compliance with the License. You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.
   4 .\"  See the License for the specific language governing permissions and limitations under the License. When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE.  If applicable, add the following below this CDDL HEADER,
   5 .\" with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
   6 .TH SD 7D "Jan 10, 2020"
   7 .SH NAME
   8 sd \- SCSI disk and ATAPI/SCSI CD-ROM device driver
   9 .SH SYNOPSIS
  10 .nf
  11 \fBsd@target,lun:partition\fR
  12 .fi
  13 
  14 .SH DESCRIPTION
  15 To open a device without checking if the vtoc is valid, use the O_NDELAY flag.
  16 When the device is opened using O_NDELAY, the first read or write to the device
  17 that happens after the open results in the label being read if the label is not
  18 currently valid. Once read, the label remains valid until the last close of the
  19 device. Except for reading the label, O_NDELAY has no impact on the driver.
  20 .SS "SPARC"
  21 The \fBsd\fR \fBSCSI\fR and \fBSCSI/ATAPI\fR driver supports embedded
  22 \fBSCSI\fR-2 and \fBCCS\fR-compatible \fBSCSI\fR disk and CD-ROM drives,
  23 \fBATAPI \fR 2.6 (SFF-8020i)-compliant CD-ROM drives, SFF-8090-compliant
  24 \fBSCSI/ATAPI\fR DVD-ROM drives, IOMEGA \fBSCSI/ATAPI\fR ZIP drives, \fBSCSI
  25 JAZ\fR drives, and USB mass storage devices (refer to \fBscsa2usb\fR(7D)).
  26 .sp
  27 .LP
  28 To determine the disk drive type, use the \fBSCSI/ATAPI\fR inquiry command and
  29 read the volume label stored on block 0 of the drive. (The volume label
  30 describes the disk geometry and partitioning and must be present for the disk
  31 to be mounted by the system.) A volume label is not required for removable,
  32 re-writable or read-only media.
  33 .SS "x86 Only"
  34 The \fBsd\fR driver supports embedded \fBSCSI\fR-2 and \fBCCS\fR-compatible
  35 \fBSCSI \fRdisk and CD-ROM drives, \fBATAPI \fR2.6 (SFF-8020i)-compliant CD-ROM
  36 drives, SFF-8090-compliant \fBSCSI/ATAPI\fR DVD-ROM drives, IOMEGA
  37 \fBSCSI/ATAPI\fR ZIP drives\fB, and SCSI JAZ\fR drives.
  38 .sp
  39 .LP
  40 The x86 BIOS legacy requires a master boot record (MBR) and \fBfdisk\fR table
  41 in the first physical sector of the bootable media. If the x86 hard disk
  42 contains a Solaris disk label, it is located in the second 512-byte sector of
  43 the FDISK partition.
  44 .SH DEVICE SPECIAL FILES
  45 Block-files access the disk using normal buffering mechanism and are read-from
  46 and written-to without regard to physical disk records. A \fBraw\fR interface
  47 enables direct transmission between the disk and the user's read or write
  48 buffer. A single \fBread\fR or \fBwrite\fR call usually results in a single I/O
  49 operation, therefore raw I/O is more efficient when many bytes are transmitted.
  50 Block files names are found in \fB/dev/dsk\fR; raw file names are found in
  51 \fB/dev/rdsk\fR.
  52 .sp
  53 .LP
  54 I/O requests to the raw device must be aligned on a 512-byte (\fBDEV_BSIZE\fR)
  55 boundary and all I/O request lengths must be in multiples of 512 bytes.
  56 Requests that do not meet these requirements will trigger an \fBEINVAL\fR
  57 error. There are no alignment or length restrictions on I/O requests to the
  58 block device.
  59 .SH CD-ROM DRIVE SUPPORT
  60 A CD-ROM disk is single-sided and contains approximately 640 megabytes of data
  61 or 74 minutes of audio. When the CD-ROM is opened, the eject button is disabled
  62 to prevent manual removal of the disk until the last \fBclose()\fR is called.
  63 No volume label is required for a CD-ROM. The disk geometry and partitioning
  64 information are constant and never change. If the CD-ROM contains data recorded
  65 in a Solaris-aware file system format, it can be mounted using the appropriate
  66 Solaris file system support.
  67 .SH DVD-ROM DRIVE SUPPORT
  68 DVD-ROM media can be single or double-sided and can be recorded upon using a
  69 single or double layer structure. Double-layer media provides parallel or
  70 opposite track paths. A DVD-ROM can hold from between 4.5 Gbytes and 17 Gbytes
  71 of data, depending on the layer structure used for recording and if the DVD-ROM
  72 is single or double-sided.
  73 .sp
  74 .LP
  75 When the DVD-ROM is opened, the eject button is disabled to prevent the manual
  76 removal of a disk until the last \fBclose()\fR is called. No volume label is
  77 required for a DVD-ROM. If the DVD-ROM contains data recorded in a
  78 Solaris-aware file system format, it can be mounted using the appropriate
  79 Solaris file system support.
  80 .SH ZIP/JAZ DRIVE SUPPORT
  81 \fBZIP/JAZ\fR media provide varied data capacity points; a single \fBJAZ
  82 \fRdrive can store up to 2 GBytes of data, while a ZIP-250 can store up to
  83 250MBytes of data. \fBZIP/JAZ\fR drives can be read-from or written-to using
  84 the appropriate drive.
  85 .sp
  86 .LP
  87 When a \fBZIP/JAZ\fR drive is opened, the eject button is disabled to prevent
  88 the manual removal of a disk until the last \fBclose()\fR is called. No volume
  89 label is required for a \fBZIP/JAZ\fR drive. If the \fBZIP/JAZ\fR drive
  90 contains data recorded in a Solaris-aware file system format, it can be mounted
  91 using the appropriate Solaris file system support.
  92 .SH DEVICE STATISTICS SUPPORT
  93 Each device maintains I/O statistics for the device and for partitions
  94 allocated for that device. For each device/partition, the driver accumulates
  95 reads, writes, bytes read, and bytes written. The driver also initiates
  96 hi-resolution time stamps at queue entry and exit points to enable monitoring
  97 of residence time and cumulative residence-length product for each queue.
  98 .sp
  99 .LP
 100 Not all device drivers make per-partition IO statistics available for
 101 reporting. \fBsd\fR and \fBssd\fR(7D) per-partition statistics are enabled by
 102 default but may be disabled in their configuration files.
 103 .SH IOCTLS
 104 Refer to \fBdkio\fR(7I), and \fBcdio\fR(7I)
 105 .SS "ERRORS"
 106 .ne 2
 107 .na
 108 \fB\fBEACCES\fR\fR
 109 .ad
 110 .RS 10n
 111 Permission denied
 112 .RE
 113 
 114 .sp
 115 .ne 2
 116 .na
 117 \fB\fBEBUSY\fR\fR
 118 .ad
 119 .RS 10n
 120 The partition was opened exclusively by another thread
 121 .RE
 122 
 123 .sp
 124 .ne 2
 125 .na
 126 \fB\fBEFAULT\fR\fR
 127 .ad
 128 .RS 10n
 129 The argument features a bad address
 130 .RE
 131 
 132 .sp
 133 .ne 2
 134 .na
 135 \fB\fBEINVAL\fR\fR
 136 .ad
 137 .RS 10n
 138 Invalid argument
 139 .RE
 140 
 141 .sp
 142 .ne 2
 143 .na
 144 \fB\fBENOTTY\fR\fR
 145 .ad
 146 .RS 10n
 147 The device does not support the requested ioctl function
 148 .RE
 149 
 150 .sp
 151 .ne 2
 152 .na
 153 \fB\fBENXIO\fR\fR
 154 .ad
 155 .RS 10n
 156 During opening, the device did not exist. During close, the drive unlock failed
 157 .RE
 158 
 159 .sp
 160 .ne 2
 161 .na
 162 \fB\fBEROFS\fR\fR
 163 .ad
 164 .RS 10n
 165 The device is read-only
 166 .RE
 167 
 168 .sp
 169 .ne 2
 170 .na
 171 \fB\fBEAGAIN\fR\fR
 172 .ad
 173 .RS 10n
 174 Resource temporarily unavailable
 175 .RE
 176 
 177 .sp
 178 .ne 2
 179 .na
 180 \fB\fBEINTR\fR\fR
 181 .ad
 182 .RS 10n
 183 A signal was caught during the execution of the \fBioctl()\fR function
 184 .RE
 185 
 186 .sp
 187 .ne 2
 188 .na
 189 \fB\fBENOMEM\fR\fR
 190 .ad
 191 .RS 10n
 192 Insufficient memory
 193 .RE
 194 
 195 .sp
 196 .ne 2
 197 .na
 198 \fB\fBEPERM\fR\fR
 199 .ad
 200 .RS 10n
 201 Insufficient access permission
 202 .RE
 203 
 204 .sp
 205 .ne 2
 206 .na
 207 \fB\fBEIO\fR\fR
 208 .ad
 209 .RS 10n
 210 An I/O error occurred. Refer to notes for details on copy-protected DVD-ROM
 211 media.
 212 .RE
 213 
 214 .SH CONFIGURATION
 215 The \fBsd\fR driver can be configured by defining properties in the
 216 \fBsd.conf\fR file. The \fBsd\fR driver supports the following properties:
 217 .sp
 218 .ne 2
 219 .na
 220 \fB\fBenable-partition-kstats\fR\fR
 221 .ad
 222 .RS 27n
 223 The default value is 1, which causes partition IO statistics to be maintained.
 224 Set this value to zero to prevent the driver from recording partition
 225 statistics. This slightly reduces the CPU overhead for IO, mimimizes the amount
 226 of \fBsar\fR(1) data collected and makes these statistics unavailable for
 227 reporting by \fBiostat\fR(1M) even though the \fB-p\fR/\fB-P\fR option is
 228 specified. Regardless of this setting, disk IO statistics are always
 229 maintained.
 230 .RE
 231 
 232 .sp
 233 .ne 2
 234 .na
 235 \fB\fBqfull-retries\fR\fR
 236 .ad
 237 .RS 27n
 238 The supplied value is passed as the \fBqfull-retries\fR capability value of the
 239 HBA driver. See \fBscsi_ifsetcap\fR(9F) for details.
 240 .RE
 241 
 242 .sp
 243 .ne 2
 244 .na
 245 \fB\fBqfull-retry-interval\fR\fR
 246 .ad
 247 .RS 27n
 248 The supplied value is passed as the \fBqfull-retry interval\fR capability value
 249 of the HBA driver. See \fBscsi_ifsetcap\fR(9F) for details.
 250 .RE
 251 
 252 .sp
 253 .ne 2
 254 .na
 255 \fB\fBallow-bus-device-reset\fR\fR
 256 .ad
 257 .RS 27n
 258 The default value is 1, which allows resetting to occur. Set this value to
 259 \fB0\fR (zero) to prevent the \fBsd\fR driver from calling \fBscsi_reset\fR(9F)
 260 with a second argument of \fBRESET_TARGET\fR when in error-recovery mode. This
 261 \fBscsi_reset\fR(9F) call may prompt the HBA driver to send a SCSI Bus Device
 262 Reset message. The \fBscsi_reset\fR(9F) call with a second argument of
 263 \fBRESET_TARGET\fR may result from an explicit request via the \fBUSCSICMD\fR
 264 \fBioctl\fR. Some high-availability multi-initiator systems may wish to
 265 prohibit the Bus Device Reset message; to do this, set the
 266 \fBallow-bus-device-reset\fR property to \fB0\fR.
 267 .RE
 268 
 269 .sp
 270 .ne 2
 271 .na
 272 \fBoptical-device-bind\fR
 273 .ad
 274 .RS 27n
 275 Controls the binding of the driver to non self-identifying SCSI target optical
 276 devices. (See \fBscsi\fR(4)). The default value is 1, which causes \fBsd\fR to
 277 bind to DTYPE_OPTICAL devices (as noted in \fBscsi\fR(4)).  Setting this value
 278 to 0 prevents automatic binding. The default behavior for the SPARC-based
 279 \fBsd\fR driver prior to Solaris 9 was not to bind to optical devices.
 280 .RE
 281 
 282 .sp
 283 .ne 2
 284 .na
 285 \fB\fBpower-condition\fR\fR
 286 .ad
 287 .RS 27n
 288 Boolean type, when set to \fBFalse\fR, it indicates that the disk does not
 289 support \fBpower condition\fR field in the \fBSTART STOP UNIT\fR command.
 290 .RE
 291 
 292 .sp
 293 .LP
 294 In addition to the above properties, some device-specific tunables can be
 295 configured in \fBsd.conf\fR using the \fBsd-config-list\fR global property. The
 296 value of this property is a list of duplets. The formal syntax is:
 297 .sp
 298 .in +2
 299 .nf
 300 sd-config-list = <duplet> [, <duplet> ]* ;
 301 
 302 where
 303 
 304 <duplet>:= "<vid+pid>" , "<tunable-list>"
 305 
 306 and
 307 
 308 <tunable-list>:= <tunable>  [, <tunable> ]*;
 309 <tunable> = <name> : <value>
 310 
 311 The <vid+pid> is the string that is returned by the target device
 312 on a SCSI inquiry command.
 313 
 314 The <tunable-list> contains one or more tunables to apply to
 315 all target devices with the specified <vid+pid>.
 316 
 317 Each <tunable> is a <name> : <value> pair. Supported
 318 tunable names are:
 319 
 320    delay-busy: when busy, nsecs of delay before retry.
 321 
 322    retries-timeout: retries to perform on an IO timeout.
 323 .fi
 324 .in -2
 325 
 326 .sp
 327 .ne 2
 328 .na
 329 \fB\fBmmc-gesn-polling\fR\fR
 330 .ad
 331 .RS 20n
 332 For optical drives compliant with \fBMMC-3\fR and supporting the \fBGET EVENT
 333 STATUS NOTIFICATION\fR command, this command is used for periodic media state
 334 polling, usually initiated by the \fBDKIOCSTATE\fR \fBdkio\fR(7I) ioctl. To
 335 disable the use of this command, set this boolean property to \fBfalse\fR. In
 336 that case, either the \fBTEST UNIT READY\fR or zero-length \fBWRITE(10)\fR
 337 command is used instead.
 338 .RE
 339 
 340 .SH EXAMPLES
 341 .in +2
 342 .nf
 343 The following is an example of a global sd-config-list property:
 344 
 345    sd-config-list =
 346       "SUN     T4", "delay-busy:600, retries-timeout:6",
 347       "SUN     StorEdge_3510", "retries-timeout:3";
 348 .fi
 349 .in -2
 350 
 351 .SH FILES
 352 .ne 2
 353 .na
 354 \fB\fB/kernel/drv/sd.conf\fR\fR
 355 .ad
 356 .RS 23n
 357 Driver configuration file
 358 .RE
 359 
 360 .sp
 361 .ne 2
 362 .na
 363 \fB\fB/dev/dsk/cntndnsn\fR\fR
 364 .ad
 365 .RS 23n
 366 Block files
 367 .RE
 368 
 369 .sp
 370 .ne 2
 371 .na
 372 \fB\fB/dev/rdsk/cntndnsn\fR\fR
 373 .ad
 374 .RS 23n
 375 Raw files
 376 .RE
 377 
 378 .sp
 379 .LP
 380 Where:
 381 .sp
 382 .ne 2
 383 .na
 384 \fBcn\fR
 385 .ad
 386 .RS 6n
 387 controller n
 388 .RE
 389 
 390 .sp
 391 .ne 2
 392 .na
 393 \fBtn\fR
 394 .ad
 395 .RS 6n
 396 SCSI target id n (0-6)
 397 .RE
 398 
 399 .sp
 400 .ne 2
 401 .na
 402 \fBdn\fR
 403 .ad
 404 .RS 6n
 405 SCSI LUN n (0-7 normally; some HBAs support LUNs to 15 or 32. See the specific
 406 manpage for details)
 407 .RE
 408 
 409 .sp
 410 .ne 2
 411 .na
 412 \fBsn\fR
 413 .ad
 414 .RS 6n
 415 partition n (0-7)
 416 .RE
 417 
 418 .SS "x86 Only"
 419 .ne 2
 420 .na
 421 \fB\fB/dev/rdsk/cntndnpn\fR\fR
 422 .ad
 423 .RS 22n
 424 raw files
 425 .RE
 426 
 427 .sp
 428 .LP
 429 Where:
 430 .sp
 431 .ne 2
 432 .na
 433 \fBpn\fR
 434 .ad
 435 .RS 6n
 436 Where \fIn\fR=0 the node corresponds to the entire disk.
 437 .RE
 438 
 439 .SH SEE ALSO
 440 \fBsar\fR(1), \fBcfgadm_scsi\fR(1M), \fBfdisk\fR(1M), \fBformat\fR(1M),
 441 \fBiostat\fR(1M), \fBclose\fR(2), \fBioctl\fR(2), \fBlseek\fR(2),
 442 \fBread\fR(2), \fBwrite\fR(2), \fBdriver.conf\fR(4), \fBscsi\fR(4),
 443 \fBfilesystem\fR(5), \fBscsa2usb\fR(7D), \fBssd\fR(7D), \fBhsfs\fR(7FS),
 444 \fBpcfs\fR(7FS), \fBudfs\fR(7FS), \fBcdio\fR(7I), \fBdkio\fR(7I),
 445 \fBscsi_ifsetcap\fR(9F), \fBscsi_reset\fR(9F)
 446 .sp
 447 .LP
 448 \fIANSI Small Computer System Interface-2 (SCSI-2)\fR
 449 .sp
 450 .LP
 451 \fIATA Packet Interface for CD-ROMs, SFF-8020i\fR
 452 .sp
 453 .LP
 454 \fIMt.Fuji Commands for CD and DVD, SFF8090v3\fR
 455 .SH DIAGNOSTICS
 456 .in +2
 457 .nf
 458 Error for Command:\fI<command name>\fR
 459 Error Level: Fatal
 460 Requested Block: \fI<n>\fR
 461 Error  Block: \fI<m>\fR
 462 Vendor:'\fI<vendorname>\fR\&'
 463 Serial Number:'\fI<serial number>\fR\&'
 464 Sense Key:\fI<sense key name>\fR
 465 .fi
 466 .in -2
 467 .sp
 468 
 469 .sp
 470 .ne 2
 471 .na
 472 \fBASC: 0x<a> (<ASC name>), ASCQ: 0x<b>, FRU: 0x<c>\fR
 473 .ad
 474 .sp .6
 475 .RS 4n
 476 The command indicated by <command name> failed. The Requested Block is the
 477 block where the transfer started and the Error Block is the block that caused
 478 the error. Sense Key, \fBASC\fR, and \fBASCQ\fR information is returned by the
 479 target in response to a request sense command.
 480 .RE
 481 
 482 .sp
 483 .ne 2
 484 .na
 485 \fBCaddy not inserted in drive\fR
 486 .ad
 487 .sp .6
 488 .RS 4n
 489 The drive is not ready because no caddy has been inserted.
 490 .RE
 491 
 492 .sp
 493 .ne 2
 494 .na
 495 \fBCheck Condition on REQUEST SENSE\fR
 496 .ad
 497 .sp .6
 498 .RS 4n
 499 A REQUEST SENSE command completed with a check condition. The original command
 500 will be retried a number of times.
 501 .RE
 502 
 503 .sp
 504 .ne 2
 505 .na
 506 \fBLabel says <m> blocks Drive says <n> blocks\fR
 507 .ad
 508 .sp .6
 509 .RS 4n
 510 There is a discrepancy between the label and what the drive returned on the
 511 \fBREAD CAPACITY\fR command.
 512 .RE
 513 
 514 .sp
 515 .ne 2
 516 .na
 517 \fBNot enough sense information\fR
 518 .ad
 519 .sp .6
 520 .RS 4n
 521 The request sense data was less than expected.
 522 .RE
 523 
 524 .sp
 525 .ne 2
 526 .na
 527 \fBRequest Sense couldn't get sense data\fR
 528 .ad
 529 .sp .6
 530 .RS 4n
 531 The \fBREQUEST SENSE\fR command did not transfer any data.
 532 .RE
 533 
 534 .sp
 535 .ne 2
 536 .na
 537 \fBReservation Conflict\fR
 538 .ad
 539 .sp .6
 540 .RS 4n
 541 The drive was reserved by another initiator.
 542 .RE
 543 
 544 .sp
 545 .ne 2
 546 .na
 547 \fBSCSI transport failed: reason \fB\&'xxxx'\fR: {retrying|giving up}\fR
 548 .ad
 549 .sp .6
 550 .RS 4n
 551 The host adapter has failed to transport a command to the target for the reason
 552 stated. The driver will either retry the command or, ultimately, give up.
 553 .RE
 554 
 555 .sp
 556 .ne 2
 557 .na
 558 \fBUnhandled Sense Key<\fIn\fR>\fR
 559 .ad
 560 .sp .6
 561 .RS 4n
 562 The REQUEST SENSE data included an invalid sense.
 563 .RE
 564 
 565 .sp
 566 .ne 2
 567 .na
 568 \fBUnit not ready. Additional sense code 0x\fR
 569 .ad
 570 .sp .6
 571 .RS 4n
 572 \fI<n>\fR The drive is not ready.
 573 .RE
 574 
 575 .sp
 576 .ne 2
 577 .na
 578 \fBCan't do switch back to mode 1\fR
 579 .ad
 580 .sp .6
 581 .RS 4n
 582 A failure to switch back to read mode 1.
 583 .RE
 584 
 585 .sp
 586 .ne 2
 587 .na
 588 \fBCorrupt label - bad geometry\fR
 589 .ad
 590 .sp .6
 591 .RS 4n
 592 The disk label is corrupted.
 593 .RE
 594 
 595 .sp
 596 .ne 2
 597 .na
 598 \fBCorrupt label - label checksum failed\fR
 599 .ad
 600 .sp .6
 601 .RS 4n
 602 The disk label is corrupted.
 603 .RE
 604 
 605 .sp
 606 .ne 2
 607 .na
 608 \fBCorrupt label - wrong magic number\fR
 609 .ad
 610 .sp .6
 611 .RS 4n
 612 The disk label is corrupted.
 613 .RE
 614 
 615 .sp
 616 .ne 2
 617 .na
 618 \fBDevice busy too long\fR
 619 .ad
 620 .sp .6
 621 .RS 4n
 622 The drive returned busy during a number of retries.
 623 .RE
 624 
 625 .sp
 626 .ne 2
 627 .na
 628 \fBDisk not responding to selection\fR
 629 .ad
 630 .sp .6
 631 .RS 4n
 632 The drive is powered down or died
 633 .RE
 634 
 635 .sp
 636 .ne 2
 637 .na
 638 \fBFailed to handle UA\fR
 639 .ad
 640 .sp .6
 641 .RS 4n
 642 A retry on a Unit Attention condition failed.
 643 .RE
 644 
 645 .sp
 646 .ne 2
 647 .na
 648 \fBI/O to invalid geometry\fR
 649 .ad
 650 .sp .6
 651 .RS 4n
 652 The geometry of the drive could not be established.
 653 .RE
 654 
 655 .sp
 656 .ne 2
 657 .na
 658 \fBIncomplete read/write - retrying/giving up\fR
 659 .ad
 660 .sp .6
 661 .RS 4n
 662 There was a residue after the command completed normally.
 663 .RE
 664 
 665 .sp
 666 .ne 2
 667 .na
 668 \fBNo bp for direct access device format geometry\fR
 669 .ad
 670 .sp .6
 671 .RS 4n
 672 A bp with consistent memory could not be allocated.
 673 .RE
 674 
 675 .sp
 676 .ne 2
 677 .na
 678 \fBNo bp for disk label\fR
 679 .ad
 680 .sp .6
 681 .RS 4n
 682 A bp with consistent memory could not be allocated.
 683 .RE
 684 
 685 .sp
 686 .ne 2
 687 .na
 688 \fBNo bp for fdisk\fR
 689 .ad
 690 .sp .6
 691 .RS 4n
 692 A bp with consistent memory could not be allocated.
 693 .RE
 694 
 695 .sp
 696 .ne 2
 697 .na
 698 \fBNo bp for rigid disk geometry\fR
 699 .ad
 700 .sp .6
 701 .RS 4n
 702 A bp with consistent memory could not be allocated.
 703 .RE
 704 
 705 .sp
 706 .ne 2
 707 .na
 708 \fBNo mem for property\fR
 709 .ad
 710 .sp .6
 711 .RS 4n
 712 Free memory pool exhausted.
 713 .RE
 714 
 715 .sp
 716 .ne 2
 717 .na
 718 \fBNo memory for direct access device format geometry\fR
 719 .ad
 720 .sp .6
 721 .RS 4n
 722 Free memory pool exhausted.
 723 .RE
 724 
 725 .sp
 726 .ne 2
 727 .na
 728 \fBNo memory for disk label\fR
 729 .ad
 730 .sp .6
 731 .RS 4n
 732 Free memory pool exhausted.
 733 .RE
 734 
 735 .sp
 736 .ne 2
 737 .na
 738 \fBNo memory for rigid disk geometry\fR
 739 .ad
 740 .sp .6
 741 .RS 4n
 742 The disk label is corrupted.
 743 .RE
 744 
 745 .sp
 746 .ne 2
 747 .na
 748 \fBNo resources for dumping\fR
 749 .ad
 750 .sp .6
 751 .RS 4n
 752 A packet could not be allocated during dumping.
 753 .RE
 754 
 755 .sp
 756 .ne 2
 757 .na
 758 \fBOffline\fR
 759 .ad
 760 .sp .6
 761 .RS 4n
 762 Drive went offline; probably powered down.
 763 .RE
 764 
 765 .sp
 766 .ne 2
 767 .na
 768 \fBRequeue of command fails\fR
 769 .ad
 770 .sp .6
 771 .RS 4n
 772 Driver attempted to retry a command and experienced a transport error.
 773 .RE
 774 
 775 .sp
 776 .ne 2
 777 .na
 778 \fBsdrestart transport failed()\fR
 779 .ad
 780 .sp .6
 781 .RS 4n
 782 Driver attempted to retry a command and experienced a transport error.
 783 .RE
 784 
 785 .sp
 786 .ne 2
 787 .na
 788 \fBTransfer length not modulo\fR
 789 .ad
 790 .sp .6
 791 .RS 4n
 792 Illegal request size.
 793 .RE
 794 
 795 .sp
 796 .ne 2
 797 .na
 798 \fBTransport of request sense fails()\fR
 799 .ad
 800 .sp .6
 801 .RS 4n
 802 Driver attempted to submit a request sense command and failed.
 803 .RE
 804 
 805 .sp
 806 .ne 2
 807 .na
 808 \fBTransport rejected()\fR
 809 .ad
 810 .sp .6
 811 .RS 4n
 812 Host adapter driver was unable to accept a command.
 813 .RE
 814 
 815 .sp
 816 .ne 2
 817 .na
 818 \fBUnable to read label\fR
 819 .ad
 820 .sp .6
 821 .RS 4n
 822 Failure to read disk label.
 823 .RE
 824 
 825 .sp
 826 .ne 2
 827 .na
 828 \fBUnit does not respond to selection\fR
 829 .ad
 830 .sp .6
 831 .RS 4n
 832 Drive went offline; probably powered down.
 833 .RE
 834 
 835 .SH NOTES
 836 DVD-ROM media containing DVD-Video data may follow/adhere to the requirements
 837 of content scrambling system or copy protection scheme. Reading of
 838 copy-protected sector will cause I/O error. Users are advised to use the
 839 appropriate playback software to view video contents on DVD-ROM media
 840 containing DVD-Video data.