416:, and use the Linux tooling from Adaptec, potentially compromising the stability, reliability and security of their setup, especially when taking the long term view in mind. However, this greatly depends on the controller, and whether appropriate hardware documentation is available in order to write a driver, and some controllers do have open-source versions of their configuration utilities, for example,
260:
478:, the feature set is intentionally kept to a minimum, so that each controller can be supported by the tool in the same way; the initial configuration of the controller is meant to be performed through card BIOS, but after the initial configuration, all day-to-day monitoring and repair should be possible with unified and generic tools, which is what bioctl is set to accomplish.
337:
ATA drives make it possible to build RAID systems at lower cost than with SCSI, but most ATA RAID controllers lack a dedicated buffer or high-performance XOR hardware for parity calculation. As a result, ATA RAID performs relatively poorly compared to most SCSI RAID controllers. Additionally, data
297:
in their more upmarket motherboards, giving control over 4 devices and an additional 2 SATA connectors, and totalling 6 SATA connections (3 Gbit/s each). For backward compatibility one IDE connector able to connect 2 ATA devices (100 Mbit/s) is also present.
439:
Some other operating systems have implemented their own generic frameworks for interfacing with any RAID controller, and provide tools for monitoring RAID volume status, as well as facilitation of drive identification through LED blinking, alarm management,
197:
Those external disk arrays are usually purchased as an integrated subsystem of RAID controllers, disk drives, power supplies, and management software. It is up to controllers to provide advanced functionality (various vendors name these differently):
333:
utilization) the first ATA RAID controllers were introduced as PCI expansion cards. Those RAID systems made their way to the consumer market, where the users wanted the fault-tolerance of RAID without investing in expensive SCSI drives.
397:, without a need for any third-party tools, each manufacturer of each RAID controller usually provides their own proprietary software tooling for each operating system that they deem to support, ensuring a
381:
configuration utilities are available from the manufacturer of each controller, because the exact feature set of each controller may be specific to each manufacturer and product. Unlike the
310:
hard drives and aimed at the server and high-end computing market. SCSI technology advantages include allowing up to 15 devices on one bus, independent data transfers,
358:
aren't strictly required to implement the complete configuration and assembly for each controller. Very often only the basic features are implemented in the
735:
989:
152:
use different protocols for back-end and for front-end communication. Many enterprise controllers use FC on front-end and SATA on back-end.
979:
268:
111:
one of ATA, SATA, SCSI, FC; these are popular protocols used by disks, so by using one of them a controller may transparently
974:
764:
82:
994:
955:
382:
448:
from within the operating system without having to reboot into card BIOS. For example, this was the approach taken by
241:
236:
495:
463:
utility, which provide volume status, and allow LED/alarm/hotspare control, as well as the sensors (including the
853:
187:
389:, which can be usually be configured and serviced entirely through the common operating system paradigms like
899:
984:
714:
921:
710:
703:
Constantine A. Murenin (2010-05-21). "1.1. Motivation; 4. Sensor
Drivers; 7.1. NetBSD envsys / sysmon".
339:
843:
378:
359:
326:
183:
98:
432:
since 2015, each supporting only their respective device drivers, this latter fact contributing to
39:
660:
629:
598:
848:
757:
191:
306:
While hardware RAID controllers were available for a long time, they always required expensive
69:
which can also refer to the circuitry responsible for managing internal disk drive operations.
294:
135:
81:
The back-end interface communicates with the controlled disks. Hence, its protocol is usually
54:
718:
374:
355:
879:
874:
789:
782:
685:
65:
820:
805:
445:
441:
398:
271:
247:
175:
1004:
999:
968:
884:
810:
750:
681:
467:) for health monitoring; this approach has subsequently been adopted and extended by
456:
94:
869:
825:
311:
279:
105:
282:(HBA) functionality itself to save physical space. Hence it is sometimes called a
166:
In a modern enterprise architecture disk array controllers (sometimes also called
906:
835:
363:
275:
35:
77:
A disk array controller provides front-end interfaces and back-end interfaces.
17:
944:
911:
894:
797:
785:
464:
433:
259:
179:
161:
139:
86:
131:
659:"mpsutil, mprutil -- Utility for managing LSI Fusion-MPT 2/3 controllers".
889:
390:
386:
210:
203:
112:
512:
589:
554:
546:
542:
520:
449:
413:
409:
405:
722:
267:
A simple disk array controller may fit inside a computer, either as a
929:
475:
468:
460:
453:
647:
616:
581:
706:
OpenBSD Hardware
Sensors — Environmental Monitoring and Fan Control
939:
322:
290:
206:
to another controller (transparent to computers transmitting data)
127:
123:
119:
118:
somewhat less popular dedicated protocols for specific solutions:
934:
773:
597:"mfiutil -- Utility for managing LSI MegaRAID SAS controllers".
394:
370:
369:
Normally, RAID controllers can be fully configured through card
351:
315:
307:
90:
46:
43:
746:
648:"mpsutil — Utility for managing LSI Fusion-MPT 2/3 controllers"
628:"mptutil -- Utility for managing LSI Fusion-MPT controllers".
424:
is available for FreeBSD since FreeBSD 8.0 (2009), as well as
330:
582:"mfiutil — Utility for managing LSI MegaRAID SAS controllers"
496:"Storage Basics - Part V: Controllers, Cache and Coalescing"
617:"mptutil — Utility for managing LSI Fusion-MPT controllers"
704:
563:
350:
Because the hardware RAID controllers present assembled
742:
342:
backup to finish writes interrupted by a power outage.
104:
The front-end interface communicates with a computer's
362:
driver, with extended features being provided through
377:
is booted, and after the operating system is booted,
228:
Removing a disk from a RAID set (rare functionality)
920:
862:
834:
796:
562:"aac -- Adaptec AdvancedRAID Controller driver".
547:"aac(4) — Adaptec AdvancedRAID Controller driver"
725:. Document ID: ab71498b6b1a60ff817b29d56997a418.
231:Partitioning a RAID set to separate volumes/LUNs
686:"RAID management support coming in OpenBSD 3.8"
412:RAID controllers, users are required to enable
676:
674:
329:, which enabled fast data-transfers with less
758:
8:
507:
505:
765:
751:
743:
736:Storage Basics: Choosing a RAID Controller
408:, in order to access the configuration of
401:, and contributing to reliability issues.
209:Long-running operations performed without
53:. It also often provides additional disk
258:
487:
366:directly by the hardware manufacturer.
321:Around 1997, with the introduction of
263:Promise Technology ATA RAID controller
174:) are parts of physically independent
49:, thus it is sometimes referred to as
34:is a device that manages the physical
278:. Such a controller usually provides
38:and presents them to the computer as
7:
108:(HBA, Host Bus Adapter) and uses:
63:is often ambiguously shortened to
25:
513:"3.8: "Hackers of the Lost RAID""
225:Adding a disk to online RAID set
990:Fault-tolerant computer systems
222:RAID set (after a disk failure)
27:Device that manages disk drives
338:safety suffers if there is no
293:started integrating their own
42:. It almost always implements
1:
738:, May 7, 2004, By Ben Freeman
383:network interface controllers
956:Non-RAID drive architectures
250:with a remote controller....
242:Business continuance volumes
73:Front-end and back-end side
1021:
446:data scrubbing § RAID
289:As of February 2007
159:
953:
780:
414:Linux compatibility layer
980:Computer storage devices
692:(Mailing list). OpenBSD.
188:network-attached storage
715:University of Waterloo
295:Matrix RAID controller
264:
215:Forming a new RAID set
156:Enterprise controllers
115:a disk for a computer.
975:Computer data storage
816:Disk array controller
517:OpenBSD Release Songs
274:or just built onto a
262:
61:Disk array controller
32:disk array controller
662:FreeBSD Manual Pages
631:FreeBSD Manual Pages
600:FreeBSD Manual Pages
565:FreeBSD Manual Pages
360:open-source software
184:storage area network
148:A single controller
995:Integrated circuits
652:BSD Cross Reference
621:BSD Cross Reference
586:BSD Cross Reference
551:BSD Cross Reference
265:
255:Simple controllers
168:storage processors
962:
961:
471:in 2007 as well.
452:in 2005 with its
444:designations and
356:operating systems
136:ATA over Ethernet
16:(Redirected from
1012:
767:
760:
753:
744:
727:
726:
700:
694:
693:
678:
669:
666:
655:
644:
638:
635:
624:
613:
607:
604:
593:
578:
572:
569:
558:
538:
532:
531:
529:
528:
509:
500:
499:
498:. 23 March 2010.
492:
431:
427:
423:
419:
404:For example, in
375:operating system
327:Ultra-DMA-Mode 0
280:host bus adapter
21:
1020:
1019:
1015:
1014:
1013:
1011:
1010:
1009:
965:
964:
963:
958:
949:
916:
880:Data redundancy
875:Fault tolerance
858:
830:
792:
788:of independent
776:
771:
741:
731:
730:
702:
701:
697:
680:
679:
672:
658:
646:
645:
641:
627:
615:
614:
610:
596:
580:
579:
575:
561:
540:
539:
535:
526:
524:
511:
510:
503:
494:
493:
489:
484:
459:driver and the
429:
425:
421:
417:
348:
304:
257:
218:Reconstructing
164:
158:
85:(a.k.a. PATA),
75:
66:disk controller
51:RAID controller
28:
23:
22:
18:RAID controller
15:
12:
11:
5:
1018:
1016:
1008:
1007:
1002:
997:
992:
987:
982:
977:
967:
966:
960:
959:
954:
951:
950:
948:
947:
942:
937:
932:
926:
924:
918:
917:
915:
914:
909:
904:
903:
902:
897:
892:
887:
882:
877:
866:
864:
860:
859:
857:
856:
851:
846:
840:
838:
832:
831:
829:
828:
823:
821:Disk mirroring
818:
813:
808:
806:Data scrubbing
802:
800:
794:
793:
781:
778:
777:
772:
770:
769:
762:
755:
747:
740:
739:
732:
729:
728:
695:
684:(2005-09-09).
670:
668:
667:
639:
637:
636:
608:
606:
605:
573:
571:
570:
533:
501:
486:
485:
483:
480:
442:hot spare disk
399:vendor lock-in
347:
344:
325:(and thus the
314:, much higher
303:
300:
272:expansion card
256:
253:
252:
251:
245:
239:
234:
233:
232:
229:
226:
223:
216:
207:
160:Main article:
157:
154:
146:
145:
144:
143:
116:
102:
74:
71:
26:
24:
14:
13:
10:
9:
6:
4:
3:
2:
1017:
1006:
1003:
1001:
998:
996:
993:
991:
988:
986:
985:AT Attachment
983:
981:
978:
976:
973:
972:
970:
957:
952:
946:
943:
941:
938:
936:
933:
931:
928:
927:
925:
923:
919:
913:
910:
908:
905:
901:
898:
896:
893:
891:
888:
886:
885:Degraded mode
883:
881:
878:
876:
873:
872:
871:
868:
867:
865:
861:
855:
852:
850:
847:
845:
842:
841:
839:
837:
833:
827:
824:
822:
819:
817:
814:
812:
811:Data striping
809:
807:
804:
803:
801:
799:
795:
791:
787:
784:
779:
775:
768:
763:
761:
756:
754:
749:
748:
745:
737:
734:
733:
724:
720:
716:
712:
708:
707:
699:
696:
691:
687:
683:
682:Theo de Raadt
677:
675:
671:
664:
663:
657:
656:
653:
649:
643:
640:
633:
632:
626:
625:
622:
618:
612:
609:
602:
601:
595:
594:
591:
587:
583:
577:
574:
567:
566:
560:
559:
556:
552:
548:
544:
537:
534:
522:
518:
514:
508:
506:
502:
497:
491:
488:
481:
479:
477:
472:
470:
466:
462:
458:
457:pseudo-device
455:
451:
447:
443:
437:
435:
415:
411:
407:
402:
400:
396:
392:
388:
384:
380:
376:
372:
367:
365:
361:
357:
353:
345:
343:
341:
335:
332:
328:
324:
319:
317:
313:
309:
301:
299:
296:
292:
287:
285:
281:
277:
273:
270:
261:
254:
249:
246:
243:
240:
238:
235:
230:
227:
224:
221:
217:
214:
213:
212:
208:
205:
201:
200:
199:
195:
193:
189:
185:
181:
177:
173:
169:
163:
155:
153:
151:
141:
137:
133:
129:
125:
121:
117:
114:
110:
109:
107:
103:
100:
96:
92:
88:
84:
80:
79:
78:
72:
70:
68:
67:
62:
58:
56:
52:
48:
45:
41:
40:logical units
37:
33:
19:
870:Availability
854:Non-standard
826:Parity drive
815:
705:
698:
689:
661:
651:
642:
630:
620:
611:
599:
585:
576:
564:
550:
543:Adaptec, Inc
541:Scott Long;
536:
525:. Retrieved
523:. 2005-11-01
516:
490:
473:
465:drive sensor
438:
403:
368:
364:binary blobs
349:
336:
320:
312:hot-swapping
305:
288:
284:RAID adapter
283:
266:
219:
196:
182:placed in a
171:
167:
165:
149:
147:
106:host adapter
76:
64:
60:
59:
50:
31:
29:
907:Scalability
900:Replication
836:RAID levels
798:Disk arrays
717:: UWSpace.
379:proprietary
276:motherboard
248:Replication
180:disk arrays
36:disk drives
969:Categories
945:Oracle ZFS
922:Interfaces
912:Throughput
895:Parity bit
863:Principles
723:10012/5234
654:. FreeBSD.
623:. FreeBSD.
527:2019-03-23
482:References
434:code bloat
373:before an
346:OS support
202:Automatic
178:, such as
176:enclosures
162:Disk array
140:InfiniBand
783:Redundant
713:thesis).
354:volumes,
237:Snapshots
186:(SAN) or
132:HyperSCSI
890:Failover
844:Standard
545:(2000).
391:ifconfig
387:Ethernet
220:degraded
211:downtime
204:failover
44:hardware
590:FreeBSD
555:FreeBSD
521:OpenBSD
450:OpenBSD
430:mprutil
426:mpsutil
422:mptutil
418:mfiutil
410:Adaptec
406:FreeBSD
340:battery
323:ATAPI-4
302:History
192:servers
113:emulate
930:bioctl
849:Nested
476:bioctl
469:NetBSD
461:bioctl
454:bio(4)
190:(NAS)
940:mdadm
790:disks
786:array
711:MMath
690:misc@
474:With
291:Intel
244:(BCV)
170:, or
128:iSCSI
124:ESCON
120:FICON
55:cache
1005:SCSI
1000:RAID
935:geom
774:RAID
420:and
395:Unix
385:for
371:BIOS
352:RAID
316:MTBF
308:SCSI
91:SCSI
87:SATA
47:RAID
719:hdl
393:in
331:CPU
269:PCI
172:SPs
150:may
138:or
99:SAS
97:or
83:ATA
971::
688:.
673:^
650:.
619:.
588:.
584:.
553:.
549:.
519:.
515:.
504:^
436:.
318:.
286:.
194:.
134:,
130:,
126:,
95:FC
93:,
89:,
57:.
30:A
766:e
759:t
752:v
721::
709:(
665:.
634:.
603:.
592:.
568:.
557:.
530:.
428:/
142:.
122:/
101:.
20:)
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.