1hpsa(4) Kernel Interfaces Manual hpsa(4)
2
3
4
6 hpsa - HP Smart Array SCSI driver
7
9 modprobe hpsa [ hpsa_allow_any=1 ]
10
12 hpsa is a SCSI driver for HP Smart Array RAID controllers.
13
14 Options
15 hpsa_allow_any=1: This option allows the driver to attempt to operate
16 on any HP Smart Array hardware RAID controller, even if it is not ex‐
17 plicitly known to the driver. This allows newer hardware to work with
18 older drivers. Typically this is used to allow installation of operat‐
19 ing systems from media that predates the RAID controller, though it may
20 also be used to enable hpsa to drive older controllers that would nor‐
21 mally be handled by the cciss(4) driver. These older boards have not
22 been tested and are not supported with hpsa, and cciss(4) should still
23 be used for these.
24
25 Supported hardware
26 The hpsa driver supports the following Smart Array boards:
27
28 Smart Array P700M
29 Smart Array P212
30 Smart Array P410
31 Smart Array P410i
32 Smart Array P411
33 Smart Array P812
34 Smart Array P712m
35 Smart Array P711m
36 StorageWorks P1210m
37
38 Since Linux 4.14, the following Smart Array boards are also supported:
39
40 Smart Array 5300
41 Smart Array 5312
42 Smart Array 532
43 Smart Array 5i
44 Smart Array 6400
45 Smart Array 6400 EM
46 Smart Array 641
47 Smart Array 642
48 Smart Array 6i
49 Smart Array E200
50 Smart Array E200i
51 Smart Array E200i
52 Smart Array E200i
53 Smart Array E200i
54 Smart Array E500
55 Smart Array P400
56 Smart Array P400i
57 Smart Array P600
58 Smart Array P700m
59 Smart Array P800
60
61 Configuration details
62 To configure HP Smart Array controllers, use the HP Array Configuration
63 Utility (either hpacuxe(8) or hpacucli(8)) or the Offline ROM-based
64 Configuration Utility (ORCA) run from the Smart Array's option ROM at
65 boot time.
66
68 Device nodes
69 Logical drives are accessed via the SCSI disk driver (sd(4)), tape
70 drives via the SCSI tape driver (st(4)), and the RAID controller via
71 the SCSI generic driver (sg(4)), with device nodes named /dev/sd*,
72 /dev/st*, and /dev/sg*, respectively.
73
74 HPSA-specific host attribute files in /sys
75 /sys/class/scsi_host/host*/rescan
76 This is a write-only attribute. Writing to this attribute will
77 cause the driver to scan for new, changed, or removed devices
78 (e.g., hot-plugged tape drives, or newly configured or deleted
79 logical drives, etc.) and notify the SCSI midlayer of any
80 changes detected. Normally a rescan is triggered automatically
81 by HP's Array Configuration Utility (either the GUI or the com‐
82 mand-line variety); thus, for logical drive changes, the user
83 should not normally have to use this attribute. This attribute
84 may be useful when hot plugging devices like tape drives, or en‐
85 tire storage boxes containing preconfigured logical drives.
86
87 /sys/class/scsi_host/host*/firmware_revision
88 This attribute contains the firmware version of the Smart Array.
89
90 For example:
91
92 # cd /sys/class/scsi_host/host4
93 # cat firmware_revision
94 7.14
95
96 HPSA-specific disk attribute files in /sys
97 /sys/class/scsi_disk/c:b:t:l/device/unique_id
98 This attribute contains a 32 hex-digit unique ID for each logi‐
99 cal drive.
100
101 For example:
102
103 # cd /sys/class/scsi_disk/4:0:0:0/device
104 # cat unique_id
105 600508B1001044395355323037570F77
106
107 /sys/class/scsi_disk/c:b:t:l/device/raid_level
108 This attribute contains the RAID level of each logical drive.
109
110 For example:
111
112 # cd /sys/class/scsi_disk/4:0:0:0/device
113 # cat raid_level
114 RAID 0
115
116 /sys/class/scsi_disk/c:b:t:l/device/lunid
117 This attribute contains the 16 hex-digit (8 byte) LUN ID by
118 which a logical drive or physical device can be addressed.
119 c:b:t:l are the controller, bus, target, and lun of the device.
120
121 For example:
122
123 # cd /sys/class/scsi_disk/4:0:0:0/device
124 # cat lunid
125 0x0000004000000000
126
127 Supported ioctl() operations
128 For compatibility with applications written for the cciss(4) driver,
129 many, but not all of the ioctls supported by the cciss(4) driver are
130 also supported by the hpsa driver. The data structures used by these
131 ioctls are described in the Linux kernel source file in‐
132 clude/linux/cciss_ioctl.h.
133
134 CCISS_DEREGDISK, CCISS_REGNEWDISK, CCISS_REGNEWD
135 These three ioctls all do exactly the same thing, which is to
136 cause the driver to rescan for new devices. This does exactly
137 the same thing as writing to the hpsa-specific host "rescan" at‐
138 tribute.
139
140 CCISS_GETPCIINFO
141 Returns PCI domain, bus, device, and function and "board ID"
142 (PCI subsystem ID).
143
144 CCISS_GETDRIVVER
145 Returns driver version in three bytes encoded as:
146
147 (major_version << 16) | (minor_version << 8) |
148 (subminor_version)
149
150 CCISS_PASSTHRU, CCISS_BIG_PASSTHRU
151 Allows "BMIC" and "CISS" commands to be passed through to the
152 Smart Array. These are used extensively by the HP Array Config‐
153 uration Utility, SNMP storage agents, and so on. See
154 cciss_vol_status at ⟨http://cciss.sf.net⟩ for some examples.
155
157 cciss(4), sd(4), st(4), cciss_vol_status(8), hpacucli(8), hpacuxe(8)
158
159 ⟨http://cciss.sf.net⟩, and Documentation/scsi/hpsa.txt and Documenta‐
160 tion/ABI/testing/sysfs-bus-pci-devices-cciss in the Linux kernel source
161 tree
162
163
164
165Linux man-pages 6.04 2022-10-30 hpsa(4)