A dependent hardware iSCSI adapter is a third-party adapter that depends on VMware networking, and iSCSI configuration and management interfaces provided by VMware. Configure the Software iSCSI Adapter With the software-based iSCSI implementation, you can use standard NICs to connect your host to a remote iSCSI target on the IP network.
- SCSI DISK USB DEVICE 64-BITS DRIVER. Us7870225b2, disk system adapted to be directly attached. Easeus data recovery wizard. Scsi disk device, toshiba boot feature. Usb pendrive mass storage device, scsi usb device driver software. Scsi mass storage devices. Mvs formatted direct access, ram disk drivers, usb windows explorer, sata external hard drive, dvd download tool.
- Emulex HBA Capture Utility. Gathers system, adapter, HBA driver & application info into a single file to send to Emulex Technical Support for analysis.
- Re: Looking for drivers for AMD-RAID Configuration SCSI Processor Device First of all, that's a typo on my part, it's actually the Alienware 15 R3. That said, things did finally get worked out, but not without a bit of pain and suffering.
- SCSI errors might occur on deletion of vPorts or PCI Hot Unplug. On occasion, the kernel might report the following SCSI errors when deleting vPorts through the sysfs interface or performing a PCI Hot Unplug of an Emulex adapter: kernel: Synchronizing SCSI cache for disk kernel: FAILED Or: SCSI error: return code = 0x00010000 Workaround None.
05:0d.0 Fibre Channel: Emulex Corporation LP9802 Fibre Channel Host Adapter (rev 01)
# cat /sys/class/scsi_host/host0/fwrev
# cat /sys/class/scsi_host/host0/node_name
# cat /sys/class/scsi_host/host0/port_name
# cat /sys/class/scsi_host/host0/lpfc_drvr_version
Emulex LightPulse Fibre Channel SCSI driver 18.104.22.168
# cat /sys/class/scsi_host/host0/serialnum
# cat /sys/class/scsi_host/host0/speed
# cat /sys/class/scsi_host/host0/state
Link Up - Ready:
[[email protected] ~]# cd /sys/class/scsi_host/host1/device/fc_host:host1/
[[email protected] fc_host:host1]# more port_name
How to identify/get QLogic WWN on Red Hat Enterprise Linux 5 (RHEL5).
First identify your installed or recognized
# lspci grep -i fibre
04:00.0 Fibre Channel: QLogic Corp. ISP2432-based 4Gb Fibre Channel to PCI Express HBA (rev 03)
04:00.1 Fibre Channel: QLogic Corp. ISP2432-based 4Gb Fibre Channel to PCI Express HBA (rev 03)
05:00.0 Fibre Channel: QLogic Corp. ISP2432-based 4Gb Fibre Channel to PCI Express HBA (rev 03)
05:00.1 Fibre Channel: QLogic Corp. ISP2432-based 4Gb Fibre Channel to PCI Express HBA (rev 03)
On Red Hat Enterprise Linux 5 (5.x) is on /sys/class/fc_host/hostX/port_name
(X is your device 1,2,3,…N)
For get use:
Sample with multiple HBA (Fibre) QLogic
# ls /sys/class/fc_host/
host3 host4 host5 host6
# cat /sys/class/fc_host/host[3-6]/port_name
On Red Hat Enterprise Linux 4 (AS/ES) is on /proc/scsi/qla2xxx/1 (1,2,3,..N)
# egrep [node port] /proc/scsi/qlx2xxx/0
# ls /sys/class/fc_host
host0 host1 host2 host3
fdisk -l 2>/dev/null egrep '^Disk' egrep -v 'dm-' wc -l
echo '1' > /sys/class/fc_host/host0/issue_lip
echo '- - -' > /sys/class/scsi_host/host0/scan
echo '1' > /sys/class/fc_host/host1/issue_lip
echo '- - -' > /sys/class/scsi_host/host1/scan
echo '1' > /sys/class/fc_host/host2/issue_lip
echo '- - -' > /sys/class/scsi_host/host2/scan
echo '1' > /sys/class/fc_host/host3/issue_lip
echo '- - -' > /sys/class/scsi_host/host3/scan
cat /proc/scsi/scsi egrep -i 'Host:' wc -l
fdisk -l 2>/dev/null egrep '^Disk' egrep -v 'dm-' wc -l
#echo 1 > /sys/block/sdb/device/delete
#echo 1 > /sys/block/sdd/device/delete
How to rescan LINUX OS for new Storage with Emulex HBA card
by Kumar on September 9, 2011
1.How to rescan the new Storage in RHEL4/RHEL5 with Emulex HBA Cards
In order to get the fiber channel adapters detail to rescan, list the /sys/class/fc_host directory. In old RHEL 4 host you will not be getting this listing. In this case you can use the /sys/class/scsi_host directory but it will list all internal adapters too.
# ls -l /sys/class/fc_host
drwxr-xr-x 3 root root 0 Jul 9 02:37 host0
drwxr-xr-x 3 root root 0 Jul 9 02:37 host1
#echo '1' > /sys/class/fc_host/host1/issue_lip
#echo '1' > /sys/class/fc_host/host2/issue_lip
#echo '- - -' > /sys/class/scsi_host/host1/scan
#echo '- - -' > /sys/class/scsi_host/host2/scan
2. After rescanning, confirm whether you are seeing the new storage disks[LUN] by listing the content under proc
cat /proc/scsi/scsi or cat /proc/scsi/scsi grep scsi uniq
3. If you are using powerpath for multipathing, run the below command to scan the powerpath to get the newly added storage devices under powerpath control
4. Then Check the newly added device under powerpath using the below command.
powermt display dev=all
5.If you are using device mapper multipathing, run the below command to scan the DMP to get the newly added storage devices under Linux DMP control
6.Then Check the newly added device under Linux DMP using the below command.
How to scan newly added LUN using rescan-scsi-bus.sh ?
ENV : RHEL 5.4 and later
I suggest you NOT to scan the existing LUNs since I/O operations are still in use and if you scan them it will/may corrupt the file system.
So, I always suggest you to scan the new added device or storage. Once you add it,
HBA will detect the device and then you can scan this non-existent LUNs to the HBA. As an example you can execute the command like :
#rescan-scsi-bus.sh --hosts=1 --luns=2
Note : I assume that on host 1/or on HBA 1, lun 2 doesn't exist.
For more details please get help from :
Here are outputs for commands:
# uname -a
Linux 64-cncrclinrpts 2.6.38-11-generic-pae #48-Ubuntu SMP Fri Jul 29 20:51:21 UTC 2011 i686 i686 i386 GNU/Linux
Emulex Scsi Connector# file jasperreports-server-cp-4.1.0-linux-x64-installer.run
jasperreports-server-cp-4.1.0-linux-x64-installer.run: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.4.0, stripped
# ldd -r jasperreports-server-cp-4.1.0-linux-x64-installer.run
not a dynamic executable
cpio -idmu < ./program/RM/HP-UX/RMHORC
This version supports hot adding new luns, etc. Please see text below on how
to perform the lun hot add procedure. The latest driver-v7.00.60-fo has the
mechanism which allows the user to force the driver to do re-scan of the
devices to allow a new device to be added. This triggers the driver to
initiate lun discovery process.
To do this from the command line:
#echo 'scsi-qlascan' > /proc/scsi/<driver-name>/<adapter-id> (qlogic
driver will re-scan)
Where <driver-name> can be either one : qla2100/qla2200/qla2300 <adapter-id>
~ is the instance number of the HBA.
Once that has been done , user then can force the scsi mid layer to do
its own scan
and build the device table entry for the new device:
# echo 'scsi add-single-device 0 1 2 3' >/proc/scsi/scsi
(scsi mid layer will re-scan) with '0 1 2 3'
replaced by your 'Host Channel Id Lun'. The scanning has to be done in
the above mentioned order.
First the driver (qla2300/qla2200 driver etc) and then the Linux scsi
You take a look into 'dmesg less' and search for the information about
'Host Channel Id Lun', the Lun you have to know, from the Storage
echo 'scsi-qlascan' > /proc/scsi/qla2200/1
echo 'scsi-qlascan' > /proc/scsi/qla2200/2
echo 'scsi add-single-device 1 0 0 6' >/proc/scsi/scsi
than take a look into 'cat /proc/partions' if the pation is not there
you can do a 'partprobe' (man partprobe).
+ Multi Path
# multipath -ll
tuan (360060e80105425e0056fcaee0000000d) dm-2 HITACHI,DF600F
_ round-robin 0 [prio=1][active]
_ 1:0:0:0 sdb 8:16 [active][ready]
_ round-robin 0 [prio=0][enabled]
_ 2:0:0:0 sdc 8:32 [active][ready]
Third-Party Disk Controllers
Mass storage technology has evolved over the years, with each new mechanical storage product quickly becoming obsolete after just a few years of being on the market. For the hobbyist, like myself, this makes resurrecting old computers more difficult. I have little interest in owning a pair of RL02 disk systems, or an RA80 drive. These are large, noisy units and are all beyond their useful life. About the only storage standard that has some usefulness left is SCSI.
A number of manufacturers made fast, narrow, high-voltage SCSI controllers for the Q-bus line of machines. These controllers can still be adapted to support modern storage technologies, through the use of bridge controllers. The table below contains a comparison of some of these controllers. Many of these controllers are difficult to find, as is their documentation, in some cases.
|Async Transfer Rate||2 MB/s||2 MB/s||2 MB/s||2 MB/s|
|Sync Transfer Rate||N/A||2 MB/s||2 MB/s||2 MB/s|
|Largest Disk||8 GB||8 GB||8 GB||8 GB|
|AC Bus Load||2.5||2.5||2.5||2.5|
|DC Bus Load||1||1||1||1|
|+5V Load||2.6 A||2.3 A||2.3 A||4.5 A|
1 The SCSI bus cannot simultaneously support disk and tape devices.
2 The SCSI buses themselves cannot simultaneously support disk and tape devices, but one bus can be configured for disk devices and the other for tape devices.
Emulex Oce11102 Driver
California Micro Devices (CMD)
|Async Transfer Rate||3 MB/s||3 MB/s||7 MB/s||7 MB/s|
|Sync Transfer Rate||N/A||4.8 MB/s||10 MB/s||10 MB/s|
|AC Bus Load|
|DC Bus Load|
|+5V Load||2.0 A||2.0 A||2.0 A4||3.5 A|
1 Only the /M and /TM models.
2 Only the /T and /TM models.
3 Partitions are equal size.
4 Differential mode. 1.5 A in sigle-ended mode.
The Emulex UC04 is an early version of the UC07 and is generally considered to be buggy. The UC06, UC07 and UC08 controllers are solid, about 95% comaptible with existing software, and somewhat versatile. Based on personal experience, these controllers only have 24-bits of LBA addressing, which limits them to 8GB per disk.
The CMD controllers are very popular, and extremely simple to setup and use. These controllers have more compatability issues than the Emulex controllers, but work extremely well, otherwise.
- Emulex UC04 Intelligent Host Adapter Technical Manual, February 1986 (UC0351002, Rev A)
- Emulex UC06, UC07 and UC08 Intelligent Host Adapter Technical Manual, November 1990 (UC0751001-00, Rev H)
- CMD CQD-200/203 Qbus Controller Installation Guide, April 1996
- CMD CQD-220/223 High Performance Q-Bus Sync/Async SCSI Host Adapter User's Manual, Rev 2.5, November 1990
- CMD CQD-220A/223A High Performance Q-Bus SCSI-2 Smart Host Adapter User's Manual, Rev 1.1, December 1993 (MAN-00220A-000)
- CMD CQD-420/423 High Performance Q-bus FAST SCSI-2 Smart Host Adapter User's Manual, Rev 1.5, May 1994 (MAN-000420-000)
Emulex Scsi Interface
- MicroNote 12 - DMA on the Q-bus
Emulex Scsi Driver
Copyright © 2020 by The Frain Research Group.