Configure Adaptec 6805 and PMC PM8060/8068 RAID with Ctrl+A
This archived OEM guide combines several historical hardware/firmware examples. Retained English screens are original; translated bitmap labels are English instructional illustrations, not captured official English UI. Identify the actual controller, disks and required data before any destructive configuration. No controller or disk operation was performed to prepare this article.
Special Note!
PM8060 RAID cards differ from other Ctrl-A series RAID cards (e.g., 6805/5805, etc.) in JBOD and Hot Spare configuration methods. The differences are as follows:
1) The PM8060 RAID card configuration interface does not have a Create JBOD option; instead, JBOD is achieved by uninitializing the hard drives.
2) The PM8060 RAID card configuration interface does not have a Global Hotspare option; Hot Spares must be configured under BIOS or via the RAID card management tool.
Please refer to the detailed content of this manual for specifics.
I. RAID Card Array Configuration
1.1 View RAID Status
After the server powers on and reaches the logo screen, the next step is the RAID card self-test process. At this time, a Ctrl -A prompt will appear on the monitor, as shown below:
Optimal, Degraded and Offline describe the actual logical drive state. Do not infer a fixed number of failed disks from the label alone: fault tolerance depends on RAID level, member grouping and which disks failed. The source mixes an Adaptec 6805 POST/utility with separate PMC PM8060 examples. Press Ctrl+A when prompted to enter the applicable configuration utility.
Select Array Configuration Utility to enter the main configuration interface.
Select Manage Arrays; at this point, the currently configured RAID information will appear on the right side.
Use the Up/Down arrow keys to select the RAID VD to view, then press Enter to select. The array status is displayed within the red box. OPTIMAL is the normal status. The array size is displayed after Array Size.
1.2 Delete RAID Array
First, refer to the View RAID section to enter the RAID configuration interface, then press Enter on Manage Array.
Pressing Delete will pop up the deletion interface. Select Delete, and the array will be removed.
View again to confirm there is no RAID information.
1.3 RAID Configuration Suggestions for Large Storage
When storage capacity is large and Windows 2008 R2 is being installed, it is recommended to first configure a smaller Virtual Disk (VD) to install the operating system. After installation is complete, configure another larger Virtual Disk (VD).
For example, when creating a RAID 5 (refer to subsequent RAID configuration chapters for specific steps), the size configuration during VD creation displays the default size (maximum usable space).
The source proposes a 100–200 GB OS virtual drive for its Windows Server 2008 R2 example. Check both the numeric value and selected unit: the pictured PM8060 example shows 10.913 TB followed by input 300 while TB is still selected in the unit menu. It is not an instruction to create a 300 TB virtual drive; select and verify the intended supported capacity and unit before submitting.
A separate data virtual drive may use the remaining supported capacity. Actual boot/data limits depend on the OS, GPT/MBR layout, Legacy/UEFI boot mode, controller firmware and driver. A small OS volume does not automatically bypass every 2 TB limit or prove that the OS will recognize another volume.
1.4 RAID 0 Configuration
First, refer to the View RAID section to enter the RAID configuration interface. Select Create Array to enter the RAID configuration interface.
If the intended new disks cannot be selected, inspect their actual state, existing metadata and compatibility first. Initialization can destroy required array metadata or data; it is not a general repair for a missing/failed disk. Initialize only verified disposable target disks under the applicable procedure.
1) Select hard drives. In this example, four hard drives are used; press the Spacebar to select.
2) Select RAID 0 (Note: If you need single-drive RAID 0 configuration, select volume here).
3) Enter Array Label, e.g., volume1.
4) Enter Array Size (Volume Size); the default capacity is the maximum capacity.
5) Select Stripe Size; the default is 256KB.
6) Select Read Caching (Read Policy); the default is enabled:
7) Select Write Caching for the actual protection hardware and policy. These historical screenshots show Enable always and warnings about absent/low ZMM or battery protection. Forcing write-back without working protection risks acknowledged data on power loss; do not treat the displayed selection as a recommended default.
Read the write-cache protection warning. Confirm only after deliberately choosing an appropriate policy and accepting its actual data-protection implications.
Read the next warning and verify the intended target and action before confirming.
8) Select the intended creation method using the controller documentation. Quick Init, Skip Init, Clear and Build/Verify have different effects. The RAID 5/6 source dropdowns highlight Skip Init although the prose recommends Quick Init; the RAID 10 example shows Quick Init. Neither a quick nor skipped initialization is evidence of a full media/parity verification.
9) Finally, select [Done] and press Enter. When the completion prompt appears, press any key to exit.
After completing the configuration, you can check the array status in Manage Array. Optimal indicates normal status, Degraded indicates a degraded array (meaning a drive has gone offline), and Offline indicates a failed array.
1.5 RAID1 Configuration
The source’s initial RAID 1 form and final form use different size values; the completed example shows two 465 GB members and 465 GB logical capacity. Retain the figures as separate stages rather than treating every displayed capacity as the final value.
First, refer to the "View RAID" section to enter the RAID configuration interface. Select Create Array to access the RAID configuration interface.
If the intended new disks cannot be selected, inspect their actual state, existing metadata and compatibility first. Initialization can destroy required array metadata or data; it is not a general repair for a missing/failed disk. Initialize only verified disposable target disks under the applicable procedure.
1) Select 2 drives, press the Spacebar to select them
2) Select RAID Level
3) Enter Array Label (Volume Label), e.g., volume1
4) Enter Array Size (Volume Size). The default capacity is the maximum capacity.
5) Stripe Size is a separate field from Array Size. RAID 1 shows N/A; the RAID 5 and RAID 6 examples show 256 KB. The original prose incorrectly calls these fields the same and repeats N/A for parity arrays.
6) Select Read Caching (Read Policy). Default is enabled:
7) Select Write Caching for the actual protection hardware and policy. These historical screenshots show Enable always and warnings about absent/low ZMM or battery protection. Forcing write-back without working protection risks acknowledged data on power loss; do not treat the displayed selection as a recommended default.
Read the write-cache protection warning. Confirm only after deliberately choosing an appropriate policy and accepting its actual data-protection implications.
Read the next warning and verify the intended target and action before confirming.
8) Select the intended creation method using the controller documentation. Quick Init, Skip Init, Clear and Build/Verify have different effects. The RAID 5/6 source dropdowns highlight Skip Init although the prose recommends Quick Init; the RAID 10 example shows Quick Init. Neither a quick nor skipped initialization is evidence of a full media/parity verification.
9) Finally, select [Done] and press Enter. When the completion prompt appears, press any key to exit. Then, check the RAID status in Manage Array to ensure it is configured correctly. Optimal indicates normal status, Degraded indicates a degraded array (meaning a drive has gone offline), and Offline indicates a failed array.
1.6 RAID5 Configuration
First, refer to the "View RAID" section to enter the RAID configuration interface. Select Create Array to access the RAID configuration interface.
If the intended new disks cannot be selected, inspect their actual state, existing metadata and compatibility first. Initialization can destroy required array metadata or data; it is not a general repair for a missing/failed disk. Initialize only verified disposable target disks under the applicable procedure.
1) Select at least 3 drives. This example uses 3 drives. Press the Spacebar to select them.
2) Select RAID Level:
3) Enter Array Label (Volume Label), e.g., volume5
4) Enter Array Size (Volume Size). The default capacity is the maximum capacity.
5) Stripe Size is a separate field from Array Size. RAID 1 shows N/A; the RAID 5 and RAID 6 examples show 256 KB. The original prose incorrectly calls these fields the same and repeats N/A for parity arrays.
6) Select Read Caching (Read Policy). Default is enabled:
7) Select Write Caching for the actual protection hardware and policy. These historical screenshots show Enable always and warnings about absent/low ZMM or battery protection. Forcing write-back without working protection risks acknowledged data on power loss; do not treat the displayed selection as a recommended default.
Read the write-cache protection warning. Confirm only after deliberately choosing an appropriate policy and accepting its actual data-protection implications.
Read the next warning and verify the intended target and action before confirming.
8) Select the intended creation method using the controller documentation. Quick Init, Skip Init, Clear and Build/Verify have different effects. The RAID 5/6 source dropdowns highlight Skip Init although the prose recommends Quick Init; the RAID 10 example shows Quick Init. Neither a quick nor skipped initialization is evidence of a full media/parity verification.
9) Finally, select [Done] and press Enter. When the completion prompt appears, press any key to exit. Then, check the RAID status in Manage Array to ensure it is configured correctly. Optimal indicates normal status, Degraded indicates a degraded array (meaning a drive has gone offline), and Offline indicates a failed array.
1.7 RAID6 Configuration
The illustrated RAID6-RS example uses four 465 GB drives, 930 GB logical capacity, 256 KB strip and label volume6. The source prose repeats volume5 and N/A from another section; those are not the displayed final RAID 6 values.
First, refer to the "View RAID" section to enter the RAID configuration interface. Select Create Array to access the RAID configuration interface.
If the intended new disks cannot be selected, inspect their actual state, existing metadata and compatibility first. Initialization can destroy required array metadata or data; it is not a general repair for a missing/failed disk. Initialize only verified disposable target disks under the applicable procedure.
1) Select at least 4 drives. Press the Spacebar to select them.
2) Select RAID Level:
3) Enter Array Label (Volume Label), e.g., volume5
4) Enter Array Size (Volume Size). The default capacity is the maximum capacity.
5) Stripe Size is a separate field from Array Size. RAID 1 shows N/A; the RAID 5 and RAID 6 examples show 256 KB. The original prose incorrectly calls these fields the same and repeats N/A for parity arrays.
6) Select Read Caching (Read Policy). Default is enabled:
7) Select Write Caching for the actual protection hardware and policy. These historical screenshots show Enable always and warnings about absent/low ZMM or battery protection. Forcing write-back without working protection risks acknowledged data on power loss; do not treat the displayed selection as a recommended default.
Read the next warning and verify the intended target and action before confirming.
8) Select the intended creation method using the controller documentation. Quick Init, Skip Init, Clear and Build/Verify have different effects. The RAID 5/6 source dropdowns highlight Skip Init although the prose recommends Quick Init; the RAID 10 example shows Quick Init. Neither a quick nor skipped initialization is evidence of a full media/parity verification.
9) Finally, select [Done] and press Enter. When the completion prompt appears, press any key to exit, then check the RAID status in Manage Array. Optimal indicates normal status, Degraded indicates a degraded array (representing a disconnected drive), and Offline indicates an offline array.
1.8 RAID10 Configuration
First, refer to the View RAID section to enter the RAID configuration interface. Select Create Array to enter the RAID configuration interface.
If the intended new disks cannot be selected, inspect their actual state, existing metadata and compatibility first. Initialization can destroy required array metadata or data; it is not a general repair for a missing/failed disk. Initialize only verified disposable target disks under the applicable procedure.
1) Select at least 4 drives; the number must be even. Press the Spacebar to select.
2) Select the RAID level:
3) Subsequent steps are the same as creating RAID5 and RAID6 arrays; they are not repeated here.
Finally, check the RAID status in Manage Array. Optimal indicates normal status, Degraded indicates a degraded array (representing a disconnected drive), and Offline indicates an offline array.
1.9 JBOD Configuration
1.9.1 6805 RAID Card
Changing an existing RAID member to JBOD/uninitialized state or deleting its array can destroy required metadata/data. The following is an intended reconfiguration example, not a recovery step; preserve required data and verify the target before any such operation.
The 6805 RAID card configuration interface has a Create JBOD option. Press Enter to enter the JBOD configuration interface.
Enter the following interface. Use the Up/Down arrow keys to select the disks to configure as JBOD, and press the Insert key to select (if selected incorrectly, press the Del key to deselect). After selection, press Enter to confirm.
Press Y to confirm.
Return to the RAID configuration interface and select Manage JBOD to view all JBOD disks.
Here, pressing Del can delete JBODs. You can also press Ctrl+V to convert JBODs to Volumes (single-disk RAID0). The converted Volume is shown in the figure below:
1.9.2 PM8060 RAID Card
Changing an existing RAID member to JBOD/uninitialized state or deleting its array can destroy required metadata/data. The following is an intended reconfiguration example, not a recovery step; preserve required data and verify the target before any such operation.
For the illustrated PM8060 firmware, the source uses Uninitialize Drives rather than Create JBOD. This clears configuration metadata; use only for an intended conversion after checking required data. The list shows selectable drives, not proof that uninitialization completed.
Enter the following interface. Use the Up/Down arrow keys to select the disks to configure as JBOD, and press the Insert key to select (if selected incorrectly, press the Del key to deselect). After selection, press Enter to confirm.
1.10 Hotspare Configuration
1.10.1 6805 RAID Card
An eligible hot spare can replace a failed member and rebuild a redundant logical drive. Assignment does not immediately restore redundancy or guarantee recovery; compatibility, sufficient surviving data and successful rebuilding still matter.
The 6805 RAID card configuration interface has a Global Hotspare option. Press Enter to enter the hot spare configuration interface.
A prompt message will appear; press any key to continue.
The left list displays all current drives. Drives available for hot spare configuration are highlighted in white, while disks already configured for RAID are grayed out and unavailable.
Press Space to select the drive.
After pressing Enter, a prompt asking whether to save will appear. Press Y to confirm.
1.10.2 PM8060 RAID Card
An eligible hot spare can replace a failed member and rebuild a redundant logical drive. Assignment does not immediately restore redundancy or guarantee recovery; compatibility, sufficient surviving data and successful rebuilding still matter.
The PM8060 RAID card configuration interface does not have a Global Hotspares option. It can be configured using the arcconf tool under the operating system. Some models also support configuration in BIOS (NF84XX/TS8xx servers do not support configuration in BIOS).
BIOS interfaces for different models may vary; there are two interface configuration methods.
BIOS Interface 1 (This configuration method currently works normally for dual-processor platform machines. NF84XX/TS8xx servers require tool-based configuration under the OS due to different BIOS settings.)
Enter BIOS — Advanced — CSM Configuration menu, set the Storage option to UEFI, then press F10 to save and exit.
After rebooting, enter BIOS — Advanced — PMC maxView Storage Manager menu again:
After the BIOS scans for the RAID card, the following menu will appear. Enter Logical Device Configuration — Global Hotspare menu:
Enable unconfigured drives, then press Enter on [ADD], followed by Submit to confirm. After receiving a success prompt, press any key to return.
If the system originally used Legacy Storage and this temporary change is required for the documented platform, restore that previous setting after configuration. Do not impose Legacy on an existing UEFI installation; boot-mode changes can prevent the installed OS from booting.
BIOS Interface 2 (This configuration method is not applicable to NF84XX/TS8xx servers. NF84XX/TS8xx servers require tool-based configuration under the OS due to different BIOS settings.)
Restart and enter BIOS. Under Boot, change Boot Type to "UEFI Boot Type".
Press F10 to save and exit.
After the server restarts, press DEL at the following interface to enter the Setup interface.
The Setup interface at this time is different from the previous one; it now includes a "Device Management" option. Select this option.
Select "PMC maxView Storage Management" to configure storage.
Press Enter to select "Scan For Controllers".
Press Enter to select the RAID controller.
Select "Logical Device Configuration".
Select "Global Hotspares" to configure global hot spares.
Press Enter to confirm the alert.
Select "Add Spares".
Use the Spacebar to select the hot spare disk. After selection, the disk status changes to "X". Move to the "ADD" item and press Enter.
Press Enter to confirm the alert.
Hot spare disk added successfully.
Restore the original Boot Type only when appropriate for this particular server and installed OS. The source returns its own example to Legacy Boot Type; that is not a required final mode for every installation.
Configure hot spares in the operating system using the arcconf tool.
Under Windows:
1. First decompress, then run cmd in the directory. Open the cmd command and cd to the directory where arcconf.exe is located.
2. Check disk status to confirm the channel number and device number of the physical disk that needs to be configured as a hot spare.
arcconf.exe getconfig 1 pd
The number 1 indicates RAID card 1.
Check the returned information: if the disk status is ready, it means the disk is unused. Record the channel number and device number of the disk you want to configure as a hot spare.
3. Configure hot spare: arcconf.exe setstate 1 device <Channel#> <Device#> hsp
Use the actual channel and device identity from getconfig, not an assumed slot. The source command ending in device 0 2 hsp is an illustrative example, while its Ready-drive screenshot shows channel 0, device 3. These differ; substitute the verified intended unused disk. No ARCCONF state-changing command was executed while preparing this guide.
You can verify if the disk status is configured successfully by running: arcconf.exe getconfig 1 pd.
2. Commands under Linux:
Check disks: ./arcconf getconfig 1 pd
Configure hot spare: ./arcconf setstate 1 device <Channel#> <Device#> hsp
1.11 Controller Attribute Configuration
The example Alarm Control value is Disabled. Enable, Disable and Silence below describe available actions, not a recommended new alarm policy.
In the RAID configuration interface, select "Controller Settings" to configure controller attributes.
Select "Controller Configuration".
At this point, the RAID controller attribute configuration interface is displayed, allowing you to view and modify settings.
Common Configuration Items
Alarm Control: Array card alarm settings
Enable: Normal beep on fault
Disable: No beep on fault
Silence: No beep for this instance
II. Fault Recovery for Common Issues
Important Note: Server RAID technology can effectively enhance data security, but implementing RAID does not guarantee that problems will never occur. Therefore, regular data backups are still essential!
A red drive light or controller alarm requires checking the actual disk state and platform-specific indicator meaning. It is not by itself proof of a particular drive failure or permission to force a disk online. The source lists possible causes below, without proving them for an individual system.
1. The hard drive was manually plugged or unplugged.
2. Hard drive not seated properly or poor contact
3. Unexpected power outage affecting array information
4. Logical I/O error on the hard drive
5. Hardware failure of the hard drive itself
The source speculates about shipping/seating issues, logical errors and dust/static as causes. It provides no diagnostic evidence establishing those causes or their frequency. Read actual drive/link/controller events and the server-specific indicator definitions before deciding on a remedy.
2.1 Single Drive Offline and Troubleshooting Steps
Taking RAID 5 as an example, if one drive goes offline, the RAID array enters a degraded state, but data remains readable and writable.
A supported replacement may trigger rebuild when the surviving array and replacement are suitable. The illustrated rebuild is a separate volume5 example at 1%, not a completed reconstruction of the earlier degraded df volume.
After an actual successful rebuild, verify the intended logical drive returns to Optimal and check required data. The source does not picture that completed endpoint.
2.2 Multiple Drives Offline and Troubleshooting Steps
RAID 5 cannot tolerate two unavailable members. Preserve original member order, metadata and event evidence; avoid initialization, blind state forcing or recreation. A qualified recovery assessment may be required; this guide does not guarantee data restoration.
2.3 Initialize Hard Drive
A replacement with old/foreign metadata needs investigation of its actual identity and contents. Initialization is destructive and is not automatically required whenever a drive is unavailable.
Initialize Drives prepares selected disks for the applicable controller configuration and may erase metadata for existing arrays. It is not a universal prerequisite for every controller, drive state or recovery operation.
Refer to the 'View RAID' section first to enter the RAID configuration interface. Select Initialize Drives.
Select the drive(s) to initialize.
Press the Spacebar to select the drive(s).
Read the warning that selected drives may belong to existing arrays and that initialization can lose those arrays. Proceed only for verified disposable intended targets, never to recover required member data.
Confirm again.
Initialization successful.
2.4 Verify Hard Drive
To detect hard drive issues, you can verify the drive to check for bad sectors.
From the main interface, select Disk Utilities to view the physical hard drive list.
Select the drive to verify and press Enter.
The pictured options are Format Disk, Verify Disk Media and Identify Drive. Format Disk is a separate destructive operation, not a verification step. If a formatting operation is already running, consult its controller-specific procedure; the source does not establish that every interruption physically damages a drive.
Select Verify Disk Media.
After confirmation, enter the verification interface.
The example proceeds from 0% to Disk Verification Complete. This is the reported media verification result, not proof that every file, array or application is healthy. Investigate any reported defects using the controller/drive procedure; the source describes possible remapping of recoverable defects, not guaranteed repair of all failures.
English references and source scope
- https://www.ieisystem.com/qa/raid/14635.html
- https://ask.adaptec.com/app/answers/detail/a_id/10062
- https://onlinedocs.microchip.com/oxy/GUID-A735A5E3-4456-4763-9EA6-B7AE0E5FE7E8-en-US-19/GUID-FBAE3544-95EF-4EB2-86F2-1B7FB1DCA1C1.html
No exact English edition of this OEM QA was verified from its language navigation. The English manufacturer references clarify terminology and policy distinctions; newer Microchip guides do not certify PM8204/PM8060 OEM firmware support, and Broadcom documentation does not make every displayed OEM model interchangeable. All original sections and working image references are retained, with source inconsistencies identified above.