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