NAME | SYNOPSIS | DESCRIPTION | DEVICE SPECIAL FILES | IOCTLS | ERRORS | FILES | ATTRIBUTES | SEE ALSO | DIAGNOSTICS | NOTES
storage@unit-address
The scsa2usb driver is a USBA (Solaris USB architecture) compliant nexus driver that supports the USB Bulk Only Mass Storage Specification 1.0. It supports bus-powered and self-powered USB mass storage devices. This nexus driver is a USB client driver. The scsa2usb driver only supports disk devices that utilize the Bulk Only protocol and the SCSI sub class.
The scsa2usb nexus driver maps SCSA target driver requests to USBA client driver requests.
The scsa2usb driver creates a child device info node for each logical unit (LUN) on the mass storage device. The standard Solaris SCSI disk driver is attached to those nodes. Refer to sd(7D).
This driver supports multiple LUN devices and creates a separate child device info node for each LUN. All child LUN nodes attach to sd(7D).
The mass storage device can be managed by rmformat(1). With or without Volume Manager, you can mount, eject, hot remove and hot insert a mass storage device, as the following sections explain.
Mass storage devices are managed by Volume Manager. vold(1M) creates a device nickname which can be listed with eject(1). The device is mounted using volrmmount(1) under /rmdisk/label.
See volrmmount(1) to unmount the device and eject(1) to eject the media. If the device is ejected while it is mounted, vold(1M) unmounts the device before ejecting it. It also kills any active applications that are accessing the device.
Hot removing a mass storage device with vold(1M) will fail with a console warning. To hot remove or insert a USB storage device first stop vold(1M) by issuing the command /etc/init.d/volmgt stop. After the device has been removed or inserted, restart vold(1M) by issuing the command /etc/init.d/volmgt start.
You can also permanently disable vold for removable devices by commenting out the rmscsi line in vold.conf. See the System Administration Guide, Volume I and Solaris Common Desktop Environment: User's Guide for details on how to manage a removable device with CDE and Removable Media Manager. See dtfile(1M) under CDE for using Removable Media Manager.
Use mount(1M) to mount the device and umount(1M) to unmount the device. Use eject(1) to eject the media. No vold nicknames can be used.
Removing the storage device while it is being accessed or mounted will fail with a console warning. To hot remove the storage device from the system, unmount the file system, then kill all applications accessing the device. Next, hot remove the device. A storage device can be hot inserted at any time.
The following (non-bootable) USB mass-storage devices are compatible with this driver:
DEVICE NAME | MEDIUM CAPACITY |
---|---|
Iomega Zip USB 100/Zip USB 250 | 100MB/250MB Zip disks |
Iomega Jaz 1GB/2GB drive with Jaz USB adapter | 1GB/2GB Jaz disks |
Iomega USB Clik! PC Card Doc | 40MB Clik! disks |
Iomega USB Zip CD CD-RW | CD-R, CD-RW media |
Castlewood ORB 2.2GB external USB drive | 2.2GB ORB disks |
Hagiwara Sys-Com FlashGate (SmartMedia Reader/Writer USB version) | 2MB/4MB (5V) 2MB/4MB/8MB/16MB/32MB/64MB (3.3V) |
Hagiwara Sys-Com FlashGate CF (CompactFlash Reader/Writer USB Version) | 8/16/32/48/64/96/128 MB in 3.3V and 5V systems |
SCM Microsystems Inc. SCSI to USB Converter | N/A |
Sony Spressa USB Plus CRX 100E/X2 (CD-RW) | CD-R, CD-RW media |
Block special file names are located in /dev/dsk; raw file names are located in /dev/rdsk. Input/output requests to the devices must follow the same restrictions as those for SCSI disks. Refer to sd(7D).
Refer to sd(7D).
The device special files for the USB mass storage device are created like those for a SCSI disk. Refer to sd(7D).
Block files
Raw files
Symbolic link to the character device for the media in Zip drive 0
Symbolic link to the character device for the media in Jaz drive 0
Symbolic link to the character device for the media in removable drive 0. This is a generic removable media device
32-bit ELF kernel module
64-bit ELF kernel module
See attributes(5) for descriptions of the following attributes:
ATTRIBUTE TYPE | ATTRIBUTE VALUE |
---|---|
Architecture | PCI-based systems |
Availability | SUNWusb, SUNWusbx |
cfgadm_scsi(1M), dtfile(1M), eject(1), fdisk(1M), mount(1M), rmformat(1), umount(1M), vold(1M), volrmmount(1), scsi(4), ohci(7D), sd(7D), uhci(7D), usba(7D), usb_mid(7D), pcfs(7FS), dkio(7I)
Writing Device Drivers
System Administration Guide, Volume I
Solaris Common Desktop Environment: User's Guide
Universal Serial Bus Specification 1.1
Universal Serial Bus Mass Storage Class Specification Overview 1.0
Universal Serial Bus Mass Storage Class Bulk-Only Transport 1.0
System Administration Guide: Basic Administration
Refer to sd(7D).
In addition to being logged, the following messages may appear on the system console. All messages are formatted in the following manner:
Warning: <device path> (scsa2usb<instance number>): Error Message... |
Cannot access device. Please reconnect <name>. |
There was an error in accessing the mass-storage device during reconnect. Please reconnect the device.
Device reported incorrect luns (adjusting to 1). |
The mass-storage device reported that it supports invalid number of LUNs. The driver has adjusted the number of LUNs supported to 1.
Device reported <number> luns (adjusting to 1). |
The mass-storage device reported that it supports invalid number of LUNs. The driver has adjusted the number of LUNs supported to 1.
Device is busy and cannot be suspended. Please close files, unmount and eject. |
The system wide suspend failed because the mass-storage device is busy. Close the device, unmount the file system and eject the media before retrying the suspend.
Device is not identical to the previous one on this port. Please disconnect and reconnect. |
Another USB device has been inserted on the port that housed a mass-storage device. Please disconnect the USB device and reconnect the mass-storage device back into its port.
Disconnected device was busy, please reconnect. |
Disconnection of the mass-storage device failed because the device is busy. Please reconnect the device.
Reinserted device is accessible again. |
The mass-storage device that was hot-removed from its USB slot has been re-inserted again to the same slot. It is available for access.
Syncing not supported. |
System panic. A file system is mounted on the mass-storage media. Syncing is not supported by scsa2usb driver.
The Zip 100 drive does not comply with Universal Serial Bus Specification 1.0 and cannot be power managed. Power Management support for Zip 100 has been disabled.
If the system panics while a UFS file system is mounted on the mass storage media, no syncing will take place for the mass-storage device. (Syncing is not supported by the scsa2usb driver.) As a result, the file system on the media will not be consistent on reboot.
If a PCFS file system is mounted, no syncing is needed and the filesystem will be consistent on reboot.
If a mass-storage device is busy, system suspend cannot proceed and the system will immediately resume again.
Attempts to remove a mass-storage device from the system will fail. The failure will be logged to the console. An attempt to replace the removed device with some other USB device will also fail. To succesfully remove a USB mass-storage device you must "close" all references to it.
An Iomega Zip 100Mb disk cannot be formatted on an Iomega Zip250 drive. See the Iomega web site at http://www.iomega.com for details.
Concurrent I/O to devices with multiple LUNs on the same device is not supported.
NAME | SYNOPSIS | DESCRIPTION | DEVICE SPECIAL FILES | IOCTLS | ERRORS | FILES | ATTRIBUTES | SEE ALSO | DIAGNOSTICS | NOTES