1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
|
<table class="head">
<tr>
<td class="head-ltitle">ARCMSR(4)</td>
<td class="head-vol">Device Drivers Manual</td>
<td class="head-rtitle">ARCMSR(4)</td>
</tr>
</table>
<div class="manual-text">
<section class="Sh">
<h1 class="Sh" id="NAME"><a class="permalink" href="#NAME">NAME</a></h1>
<p class="Pp"><code class="Nm">arcmsr</code> — <span class="Nd">Areca
Technology Corporation SATA/SAS RAID controller</span></p>
</section>
<section class="Sh">
<h1 class="Sh" id="SYNOPSIS"><a class="permalink" href="#SYNOPSIS">SYNOPSIS</a></h1>
<p class="Pp"><code class="Cd">arcmsr* at pci? dev ? function ?</code></p>
</section>
<section class="Sh">
<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1>
<p class="Pp">The <code class="Nm">arcmsr</code> driver provides support for the
PCI-X and PCI Express RAID controllers from Areca Technology
Corporation:</p>
<p class="Pp"></p>
<ul class="Bl-dash Bd-indent Bl-compact">
<li>ARC-1110 PCI-X 4 Port SATA RAID Controller</li>
<li>ARC-1110ML PCI-X 4 Port SATA RAID Controller</li>
<li>ARC-1120 PCI-X 8 Port SATA RAID Controller</li>
<li>ARC-1120ML PCI-X 8 Port SATA RAID Controller</li>
<li>ARC-1130 PCI-X 12 Port SATA RAID Controller</li>
<li>ARC-1130ML PCI-X 12 Port SATA RAID Controller</li>
<li>ARC-1160 PCI-X 16 Port SATA RAID Controller</li>
<li>ARC-1160ML PCI-X 16 Port SATA RAID Controller</li>
<li>ARC-1170 PCI-X 24 Port SATA RAID Controller</li>
<li>ARC-1200 Rev A PCI Express 2 Port SATA RAID Controller</li>
<li>ARC-1202 PCI Express 2 Port SATA RAID Controller</li>
<li>ARC-1210 PCI Express 4 Port SATA RAID Controller</li>
<li>ARC-1220 PCI Express 8 Port SATA RAID Controller</li>
<li>ARC-1230 PCI Express 12 Port SATA RAID Controller</li>
<li>ARC-1230ML PCI Express 12 Port SATA RAID Controller</li>
<li>ARC-1231ML PCI Express 12 Port SATA RAID Controller</li>
<li>ARC-1260 PCI Express 16 Port SATA RAID Controller</li>
<li>ARC-1260ML PCI Express 16 Port SATA RAID Controller</li>
<li>ARC-1261ML PCI Express 16 Port SATA RAID Controller</li>
<li>ARC-1280 PCI Express 24 Port SATA RAID Controller</li>
<li>ARC-1280ML PCI Express 24 Port SATA RAID Controller</li>
<li>ARC-1680 PCI Express 8 Port SAS RAID Controller</li>
<li>ARC-1680LP PCI Express 8 Port SAS RAID Controller</li>
<li>ARC-1680i PCI Express 8 Port SAS RAID Controller</li>
<li>ARC-1680x PCI Express 8 Port SAS RAID Controller</li>
<li>ARC-1681 PCI-X 8 Port SAS RAID Controller</li>
</ul>
<p class="Pp">These controllers support RAID levels 0, 1, 1E, 3, 5, 6, and JBOD
using either SAS or SATA II drives.</p>
<p class="Pp"><code class="Nm">arcmsr</code> supports management and monitoring
of the controller through the <a class="Xr">bioctl(8)</a> and
<a class="Xr">envstat(8)</a> commands.</p>
<p class="Pp" id="password">Please note, however, that to use some features that
require special privileges, such as creating/removing hot-spares,
pass-through disks or RAID volumes will require to have the
<a class="permalink" href="#password"><i class="Em">password</i></a>
disabled in the firmware; otherwise a
<a class="permalink" href="#Permission"><i class="Em" id="Permission">Permission
denied</i></a> error will be reported by <a class="Xr">bioctl(8)</a>.</p>
<p class="Pp">When a RAID 1 or 1+0 volume is created, either through the
<a class="Xr">bioctl(8)</a> command or controller's firmware, the volume
won't be accessible until the initialization is done. A way to get access to
the <a class="Xr">sd(4)</a> device that corresponds to that volume without
rebooting, is to issue the following command (once the initialization is
finished):</p>
<div class="Bd Pp Li">
<pre>$ scsictl scsibus0 scan any any</pre>
</div>
<p class="Pp">The <code class="Nm">arcmsr</code> driver will also report to the
kernel log buffer any error that might appear when handling firmware
commands, such as used by the <a class="Xr">bioctl(8)</a> command.</p>
</section>
<section class="Sh">
<h1 class="Sh" id="EVENTS"><a class="permalink" href="#EVENTS">EVENTS</a></h1>
<p class="Pp">The <code class="Nm">arcmsr</code> driver is able to send events
to <a class="Xr">powerd(8)</a> if a volume or any drive connected to the
volume is not online. The
<a class="permalink" href="#state-changed"><i class="Em" id="state-changed">state-changed</i></a>
event will be sent to the
<span class="Pa">/etc/powerd/scripts/sensor_drive</span> script when such
condition happens.</p>
</section>
<section class="Sh">
<h1 class="Sh" id="SEE_ALSO"><a class="permalink" href="#SEE_ALSO">SEE
ALSO</a></h1>
<p class="Pp"><a class="Xr">intro(4)</a>, <a class="Xr">pci(4)</a>,
<a class="Xr">scsi(4)</a>, <a class="Xr">sd(4)</a>,
<a class="Xr">bioctl(8)</a>, <a class="Xr">envstat(8)</a>,
<a class="Xr">powerd(8)</a>, <a class="Xr">scsictl(8)</a></p>
</section>
<section class="Sh">
<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1>
<p class="Pp">The <code class="Nm">arcmsr</code> driver first appeared in
<span class="Ux">NetBSD 5.0</span>.</p>
</section>
<section class="Sh">
<h1 class="Sh" id="AUTHORS"><a class="permalink" href="#AUTHORS">AUTHORS</a></h1>
<p class="Pp">The <code class="Nm">arcmsr</code> driver was originally written
for <span class="Ux">OpenBSD</span> by <span class="An">David Gwynne</span>.
It was ported to <span class="Ux">NetBSD</span> and extended by
<span class="An">Juan Romero Pardines</span>.</p>
</section>
</div>
<table class="foot">
<tr>
<td class="foot-date">March 3, 2008</td>
<td class="foot-os">NetBSD 10.1</td>
</tr>
</table>
|
