Hp Smart Array P400i Driver

Posted on by
  1. Hp Smart Array P400 Driver Linux
  2. Hp Smart Array P400i Controller

Where to download the latest HP smart Array configuration utility for HP Proliant DL380 G5 server - controller is HP Smart Array P400.

HP ProLiant Smart Array SAS/SATA Controller Driver for Windows Server 2012 By downloading, you agree to the terms and conditions of the Hewlett Packard Enterprise Software License Agreement. Note: Some software requires a valid warranty, current Hewlett Packard Enterprise support contract, or a license fee. I have a HP ProLiant ML110 G4 with a HP Smart Array P400 (eBay purchase) RAID controller. HP Smart Array CCISS driver. It will support P400i too, both PCI IDs. Provided by: manpages_3.54-1ubuntu1_all NAME cciss - HP Smart Array block driver SYNOPSIS modprobe cciss [ cciss_allow_hpsa=1 ] DESCRIPTION cciss is a block driver for older HP Smart Array RAID controllers. Cciss - HP Smart Array block driver SYNOPSIS. Smart Array 6400 Smart Array 6400 EM Smart Array 6i Smart Array P600 Smart Array P400i Smart Array E200i Smart Array E200 Smart Array E200i Smart Array E200i Smart Array E200i Smart Array E500 Supported hardware The cciss driver supports the. HP Smart Array P800 Controller. Manage an HP Smart Array directly from VMware ESXi Posted on October 18, 2012 December 4, 2016 by Luca Dell'Oca 0 Flares Twitter 0 Facebook 0 Google+ 0 LinkedIn 0 Email -- 0 Flares ×.

Epson Easy Photo Fix technology makes it possible to restore faded color photos to their original brilliance. Epson stylus cx6400 software.

cciss: HP Smart Array block driver

Read cciss man page on Linux: $ man 4 cciss


cciss - HP Smart Array block driver



Note:This obsolete driver was removed from the kernel in version 4.14,as it is superseded by thehpsa(4)driver in newer kernels.

ccissis a block driver for older HP Smart Array RAID controllers.


cciss_allow_hpsa=1:This option prevents theccissdriver from attempting to drive any controllers that thehpsa(4)driver is capable of controlling, which is to say, theccissdriver is restricted by this option to the following controllers:

Supported hardware

Theccissdriver supports the following Smart Array boards:

Configuration details

To configure HP Smart Array controllers,use the HP Array Configuration Utility(eitherhpacuxe(8)orhpacucli

Hp Smart Array P400 Driver Linux

(8))or the Offline ROM-based Configuration Utility (ORCA)run from the Smart Array's option ROM at boot time.


Device nodes

The device naming scheme is as follows:

Files in /proc

The files/proc/driver/cciss/cciss[0-9]+contain information aboutthe configuration of each controller.For example:

$ cd /proc/driver/cciss$ ls -ltotal 0-rw-r--r-- 1 root root 0 2010-09-10 10:38 cciss0-rw-r--r-- 1 root root 0 2010-09-10 10:38 cciss1-rw-r--r-- 1 root root 0 2010-09-10 10:38 cciss2$ cat cciss2cciss2: HP Smart Array P800 ControllerBoard ID: 0x3223103cFirmware Version: 7.14IRQ: 16Logical drives: 1Current Q depth: 0Current # commands on controller: 0Max Q depth since init: 1Max # commands on controller since init: 2Max SG entries since init: 32Sequential access devices: 0

cciss/c2d0: 36.38GB RAID 0

Files in /sys

kdump)is honored by this controller.A value of 0 indicates that the'reset_devices=1' kernel parameter will not be honored.Some models of Smart Array are not able to honor this parameter.
Displays the 8-byte LUN ID used to address logical driveYof controllerX.
Displays the RAID level of logical driveYof controllerX.
Displays the usage count (number of opens) of logical driveYof controllerX.

SCSI tape drive and medium changer support

SCSI sequential access devices and medium changer devices are supported andappropriate device nodes are automatically created (e.g.,/dev/st0,/dev/st1,etc.; seest(4)for more details.)You must enable 'SCSI tape drive support for Smart Array 5xxx' and'SCSI support' in your kernel configuration to be able to use SCSItape drives with your Smart Array 5xxx controller.

Additionally, note that the driver will not engage the SCSI core atinit time.The driver must be directed to dynamically engage the SCSI core via the/procfilesystem entry,which the 'block' side of the driver creates as/proc/driver/cciss/cciss*at run time.This is because at driver init time,the SCSI core may not yet be initialized (because the driver is a blockdriver) and attempting to register it with the SCSI core in such a casewould cause a hang.This is best done via an initialization script(typically in/etc/init.d,but could vary depending on distribution).For example:

for x in /proc/driver/cciss/cciss[0-9]*do
echo 'engage scsi' > $xdone

Once the SCSI core is engaged by the driver, it cannot be disengaged(except by unloading the driver, if it happens to be linked as a module.)

Note also that if no sequential access devices or medium changers aredetected, the SCSI core will not be engaged by the action of the abovescript.

Hot plug support for SCSI tape drives

Hot plugging of SCSI tape drives is supported, with some caveats.Theccissdriver must be informed that changes to the SCSI bushave been made.This may be done via the/procfilesystem.For example:

echo 'rescan' > /proc/scsi/cciss0/1

This causes the driver to:

query the adapter about changes to thephysical SCSI buses and/or fibre channel arbitrated loop, and
make note of any new or removed sequential access devicesor medium changers.

The driver will output messages indicating whichdevices have been added or removed and the controller, bus, target, andlun used to address each device.The driver then notifies the SCSI midlayerof these changes.

Hp Smart Array P400i Controller

Note that the naming convention of the/procfilesystem entriescontains a number in addition to the driver name(e.g., 'cciss0'instead of just 'cciss', which you might expect).

Note:Onlysequential access devices and medium changers are presentedas SCSI devices to the SCSI midlayer by theccissdriver.Specifically, physical SCSI disk drives arenotpresented to the SCSI midlayer.The only disk devices that are presented to the kernel are logicaldrives that the array controller constructs from regions onthe physical drives.The logical drives are presented to the block layer(not to the SCSI midlayer).It is important for the driver to prevent the kernel from accessing thephysical drives directly, since these drives are used by the arraycontroller to construct the logical drives.

SCSI error handling for tape drives and medium changers

The Linux SCSI midlayer provides an error-handling protocol thatis initiated whenever a SCSI command fails to complete within acertain amount of time (which can vary depending on the command).Theccissdriver participates in this protocol to some extent.The normal protocol is a four-step process:
If that doesn't work, the SCSI bus is reset.
If that doesn't work, the host bus adapter is reset.

Theccissdriver is a blockdriver as well as a SCSI driver and only the tape drives and mediumchangers are presented to the SCSI midlayer.Furthermore, unlike morestraightforward SCSI drivers, disk I/O continues through the blockside during the SCSI error-recovery process.Therefore, theccissdriver implements only the first two of these actions,aborting the command, and resetting the device.Note also that most tape drives will not obligein aborting commands, and sometimes it appears they will not evenobey a reset command, though in most circumstances they will.If the command cannot be aborted and the device cannot bereset, the device will be set offline.

In the event that the error-handling code is triggered and a tape drive issuccessfully reset or the tardy command is successfully aborted, thetape drive may still not allow I/O to continue until some commandis issued that positions the tape to a known position.Typically you must rewind the tape (by issuingmt -f /dev/st0 rewindfor example) before I/O can proceed again to a tape drive that was reset.



andDocumentation/blockdev/cciss.txtandDocumentation/ABI/testing/sysfs-bus-pci-devices-ccissin the Linux kernel source tree


This page is part of release 4.15 of the Linuxman-pagesproject.A description of the project,information about reporting bugs,and the latest version of this page,can be found athttps://www.kernel.org/doc/man-pages/.Linux man pages generated by: SysTutorials
Linux Man Pages Copyright Respective Owners. Site Copyright © SysTutorials. All Rights Reserved.


I have a HP ProLiant ML110 G4 with a HP Smart Array P400 (eBay purchase) RAID controller. I am hoping to use ESXi 5.0. Canon bjc 85 driver windows 10. The problem is that for RAID LUN's larger than 2TB there is an issue with the cciss driver as detailed http://communities.vmware.com/thread/326902?start=0&tstart=0 and http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2006942. I noticed however that http://cciss.sourceforge.net/ states the cciss driver is deprecated in favour of hpsa which is now included in the mainline Linux kernel. http://downloads.vmware.com/d/details/dt_esxi50_hp_hpsa_500240/dHRAYnRAZWpiZHAlJQ makes me think that hpsa driver is available and possibly might even be a solution to the aforementioned problem. However, when I installed ESXi (by setting up a <2TB LUN, not desirable) and checked the driver that is loading, it appears to be cciss, with no mention of hpsa. Is there a way to remove the cciss driver and/or force the hpsa driver to load?