Posted  by 

VIA SCSI & RAID Devices Driver Download


29 January 2021 Attention Canadian Customers - we now have a Canadian distributor, who stocks SCSI2SD V5.2 and V5.5.

ISCSI stands for Internet Small Computer Systems Interface. ISCSI is a transport layer protocol that works on top of the Transport Control Protocol (TCP). It enables block-level SCSI data transport between the iSCSI initiator and the storage target over TCP/IP networks. ISCSI supports encrypting the network packets, and decrypts upon arrival at. SCSI (sans i) has long served to connect a variety of peripherals to computer systems, but most commonly it appears in storage devices, such as hard drives or tape-backup drives. ISCSI builds upon.

24 November 2020 - SCSI2SD V5.2 is available for purchase today. Assembled in Canada

30 October 2020 - SCSI2SD V5.5 is available for purchase today, with a translucent/frosted, injection-molded ABS enclosure

European and UK Customers, we have a distributor of SCSI2SD V5.5 a nd V5.2 in the UK

Australian Customers, we have a new distributor of SCSI2SD V5.5 and V5.2, as of November, 2020.

SCSI2SD V6 boards in stock

SCSI2SD model
V5.1 (discontinued)

SD card slotfull sizemicroSDfull size
SD card interfaceTested up to 256GB. Communication is via the SPI protocol at 25MHz (3MB/s theoretical max)
SCSI InterfaceSCSI-2 Narrow 8-bit 50-pin IDC
Optional DB25 female socket
Supports asynchronous transfers only.
SCSI-2 Narrow 8-bit
50 IDC pin connector
Supports asynchronous transfers only.
Male DB-25 socket
Supports asynchronous transfers only.
SCSI-2 Narrow 8-bit 50 IDC pin connector
FAST10 (10MB/s) synchronous transfer.
SCSI TerminationSoftware controlled active termination, via scsi2sd-utilActive terminator, always on
Dimensions10cm x 9cm x 1.5cm7.5cm x 5.5cm x 1.8cm (External case)10cm x 9cm x 1.5cm
PerformanceUp to 2.6MB/s read, 2.3MB/s write
(1.1MB/s on most older SCSI hosts)
Up to 1MB/secUp to 10MB/s
USB InterfaceFirmware updates and configuration
USB 2.0 micro-B
Firmware updates, configuration, and mass-storage
USB 2.0 micro-B. Mass-storage at USB 2.0 FS speeds (1.2MB/s max)
Power5V via:
* standard 4-pin floppy-drive connector
* micro USB
* self-powered using the SCSI host termination power
5V via:
* standard 4-pin floppy-drive connector
* micro USB
* self-powered using the SCSI host termination power
* Regulated 5V via optional DC barrel jack.
Self-powered using the SCSI host termination power,
or via USB. 2.35W maximum (500mA)
To function without external power via USB, requires SCSI host that
supplies terminator power on pin 25 of the DB25 socket
5V via standard 4-pin floppy-drive connector, USB,
or self-powered using the SCSI host termination power
Current Draw2.35W maximum (500mA)

The latest SCSI2SD V5 firmware version 4.8.4 is now available for download at

Retrieved from ''
A step-by-step example of a Linux configuration to configure iSCSI diskless booting.
These steps can also be used for diskless NFS booting.
In our instructions, we will configure and load the IBM 8247-22L server, ppc64le architecture.
The OS we will be loading will be Ubuntu 14.04.
Fedora 18, x86 architecture will act as the OS on which the image connected via iSCSI (iscsi target) will live.
It is also possible to use Ubuntu 15.04 and any other new version of Fedora - 20, 21, 22, etc.
The instruction assumes that iscsi target will be on x86 architecture, and iscsi initiator on ppc64le,
it is better for you if you have everything the same.
We will follow these steps:
  1. Create a disk.
  2. Set up and run iSCSI target.
  3. Install Ubuntu on a USB flash drive.
  4. Let's take the data we need from the flash drive system.
  5. Install Ubuntu on a remote iSCSI drive.
  6. Create an initrd image with iSCSI support.
  7. Let's configure the PXE server as part of the DHCP server.
  8. Let's configure the PXE server in the TFTP server part.
  9. Finally, boot from PXE via iSCSI.

Configuring iSCSI target

We connect our server with a network cable to the machine where Fedora is installed, let the name of the network interface be em1 here.
Also, let the IP of this machine on em1 be
On this machine, create a 10GiB container:
Configuring, connecting and launching iSCSI target:
The latter command allows access to the address, this is the address of the server we connected.
The tgtadm utility lives in the scsi-target-utils package.
If we use complex iptables rules, redirection, masquerade, do not forget to allow packet forwarding:

Hint for loopback mount


Installing the OS on a USB flash drive

Download the Ubuntu 15.04 (or other) image for our server -- use PowerPC64 Little-Endian server install image.
* For POWER8 Little-Endian computers, such as Power Systems S8xxL Linux-only servers.
We will write this image to a USB flash drive or to a CD-ROM.
Then install the image from the CD-ROM to FLASH, or from one FLASH to another, from CD-ROM or FLASH to the hard disk.

Via Scsi & Raid Devices Driver Downloads

We will need this installation in order to:

Via Scsi & Raid Devices Driver Download Windows 10

  1. After loading into it to form initrd with iSCSI support.
  2. Also, get the kernel image from here.
  3. Also, get the pxelinux.0 file from here.

Create an initrd image with iSCSI support, copy the kernel image and the necessary data

To install packages, you need to bring the OS to the Internet.

Via Scsi & Raid Devices Driver Download Windows 7

Installing Ubuntu on a Remote iSCSI Disk

In the 'Ununut' installer, you can select the option to connect extended drives.
Having selected it, you need to specify the iSCSI target name as server1:disk1.
Specify as the IP address, as the port 3260.
After which, as usual, partition the remote disk and install Ubuntu again.

Set up a PXE server

We need to configure DHCP and TFTP server.
For Fedora, the names of the packages we need are:If for some reason you raise your iSCSI 'target' to Ubuntu, then:
You can listen to all the commands going to the TFTP server like this: tcpdump -nnn -i em1 port 69
Now PXE configuration:
In arguments, the adra may need to specify console=tty0 if you see the kernel loading, but you do not see initrd starting and loading the system.
You may need to change root=/dev/sda2 if you partitioned the drive using iSCSI differently.
Previously copied to flash drive into the /out/ files
initrd.img-3.13.0-24-generic pxelinux.0 vmlinux-3.13.0-24-generic
copy to: chmod 644 /var/lib/tftpboot/.
Then we set the world-readable rights:

We load the server on PXE from iSCSI disk

VIA SCSI & RAID Devices Driver Download

In the case of the IBM servers, when they start, a boot manager named Petitboot is loaded.It scans the network and local media for download sources, in our caseour network boot with the name Linux will be displayed, here is what it will look likesettings: