Cli Manual

SATA & SAS RAID Controller
Command Line Interface
USER Guide
Version: 4.1
Issue Date: February, 2017
WARRANTY
Copyright and Trademarks
The information of the products in this manual is subject to change

without prior notice and does not represent a commitment on the part
of the vendor, who assumes no liability or responsibility for any errors
that may appear in this manual. All brands and trademarks are the
properties of their respective owners. This manual contains materials
protected under International Copyright Conventions. All rights
reserved. No part of this manual may be reproduced in any form or by
any means, electronic or mechanical, including photocopying, without
the written permission of the manufacturer and the author. All inquiries
should be addressed to Areca Technology Corporation.
Contents
1. Introduction................................................................. 8
1.1 Overview..........................................................................8
1.2 Supported Operating Systems..............................................9
2. Installing the Areca CLI.............................................. 10
2.1 CLI Installation............................................................... 10
2.1.1 For Windows............................................................... 10
2.1.2 For Linux, FreeBSD, Mac and Solaris.............................. 11
2.2 Accessing CLI.................................................................. 12
2.2.1 For Windows............................................................... 12
2.2.2 For Linux, FreeBSD, Mac and Solaris.............................. 12
3. CLI Command Line Configuration............................... 13
3.1 Configuring Raid Sets and Volume Sets............................... 13
3.2 Conventions.................................................................... 13
3.3 Working Mode.................................................................. 14
3.3.1 Interactive Mode......................................................... 14
3.3.2 Non-interactive Mode................................................... 15
3.4 Command Categories....................................................... 16
Main Command................................................................... 17
Set Commands.................................................................... 17
Rsf Commands.................................................................... 17
Vsf Commands.................................................................... 17
Disk Commands.................................................................. 18
Sys Commands................................................................... 18
Adsys Commands................................................................ 18
Hddpower Commands.......................................................... 18
Net Commands................................................................... 18
Hw Commands.................................................................... 19
Mail Commands................................................................... 19
SNMP Commands................................................................ 19
Exit Command.................................................................... 19
Help Command................................................................... 19
3.4.1 Main Commands......................................................... 20
3.4.2 Set Commands........................................................... 20
3.4.2.1 None..................................................................... 21
3.4.2.2 Save All Controller Information................................. 22
3.4.3 Rsf Commands............................................................ 23
3.4.3.1 Create Raid Set ..................................................... 24
3.4.3.2 Delete Raid Set...................................................... 24
3.4.3.3 Expand Raid Set..................................................... 25
3.4.3.4 Activate Incomplete Raid Set.................................... 26
3.4.3.5 Create Hot Spare.................................................... 27
3.4.3.6 Delete Hot Spare.................................................... 28
3.4.3.7 Offline Raid Set...................................................... 28
3.4.3.8 Raid Set Information............................................... 29
3.4.4 Vsf Commands............................................................ 29
3.4.4.1 Create Volume Set.................................................. 31
3.4.4.2 Create Raid50/60 (SAS Only)................................... 35
3.4.4.3 Delete Volume Set.................................................. 37
3.4.4.4 Modify Volume Set.................................................. 38
3.4.4.5 Check Volume Set................................................... 39
3.4.4.6 Stop Volume Set Check........................................... 39
3.4.4.7 Generate New Encrypted - Volume Key File (ARC-1883
Series, ARC-1882 Series and ARC-8050/8050T2)................... 39
3.4.4.8 Lock Volume (ARC-1883 Series, ARC-1882 Series and
ARC-8050/8050T2)............................................................ 41
3.4.4.9 Download an Encrypted - Volume Key File (ARC-1883
Series, ARC-1882 Series and ARC-8050/8050T2)................... 41
3.4.4.10 Display Volume Set Info......................................... 42
3.4.5 Disk Commands.......................................................... 43
3.4.5.1 Create Pass-Through Disk........................................ 44
3.4.5.2 Delete Pass-Through Disk........................................ 45
3.4.5.3 Modify Pass-Through Disk........................................ 45
3.4.5.4 Fail A Disk............................................................. 46
3.4.5.5 Activate A Fail Disk................................................. 46
3.4.5.6 Identify Selected Drive............................................ 47
3.4.5.7 Display Disk SMART Data......................................... 47
3.4.5.8 Self Test .............................................................. 47
3.4.5.9 View Drive Information ........................................... 48
3.4.5.10 SMART Off-line Data Collection (SATA Controller Only)
....................................................................................... 49
3.4.5.11 Specific Read/Write Test (SATA Controller Only)........ 50
3.4.5.12 Abort Read/Write Test (SATA Only).......................... 50
3.4.5.13 Check Read/Write Test (SATA Controller Only).......... 50
3.4.6 Raid System Function.................................................. 51
3.4.6.1 Mute The Alert Beeper ............................................ 52
3.4.6.2 Change Password................................................... 53
3.4.6.3 RAID/JBOD Function............................................... 54
3.4.6.4 Raid Rebuild Priority................................................ 54
3.4.6.5 Maximum SATA Mode (SATA Controller Only).............. 55
3.4.6.6 HDD SMART Status Polling (SATA Controller Only)....... 55
3.4.6.7 NCQ Support.......................................................... 56
3.4.6.8 HDD Queue Depth.................................................. 57
3.4.6.9 Set The SAS Mux (ARC-1680 Only)........................... 57
3.4.6.10 Set The SES2 Support (SAS Controller Only)............ 58
3.4.6.11 Set The Max Command Length............................... 58
3.4.6.12 Disk Cache........................................................... 59
3.4.6.13 HDD Read Ahead.................................................. 59
3.4.6.14 Capacity Truncation............................................... 60
3.4.6.15 Auto Activate Raid Set........................................... 60
3.4.6.16 Controller Fan Detection........................................ 61
3.4.6.17 Empty HDD slot HDD ............................................ 61
3.4.6.18 Volume Data Read Ahead....................................... 62
3.4.6.19 Write Same Configuration...................................... 63
3.4.6.20 Hot Plug Disk....................................................... 63
3.4.6.21 Smart Option....................................................... 64
3.4.6.22 Smart HDD Interval.............................................. 65
3.4.6.23 Update Firmware.................................................. 66
3.4.6.24 Show System Configuration.................................... 66
3.4.6.25 Save Bin.............................................................. 66
3.4.6.26 Restore Bin.......................................................... 67
3.4.6.27 System Information.............................................. 67
3.4.7 Advanced System........................................................ 68
3.4.7.1 HDD SMART Status Polling (SATA only) ..................... 69
3.4.7.2 Time-Limited Error Recovery.................................... 70
3.4.7.3 Time Out............................................................... 70
3.4.7.4 Retry Count........................................................... 71
3.4.7.5 Buffer Threshold..................................................... 71
3.4.7.6 Read Ahead Cache.................................................. 72
3.4.7.7 Audio/Video Stream Configuration............................ 73
3.4.7.8 Optimize Audio/Video Recording............................... 74
3.4.7.9 Optimize HD Edition Configuration............................ 75
3.4.7.10 Read Performance Margin...................................... 75
3.4.7.11 Write Performance Margin...................................... 76
3.4.7.12 Read And Discard Parity Data ................................ 76
3.4.7.13 Fail Disk For Any Timeout....................................... 77
3.4.7.14 SATA Speed......................................................... 77
3.4.7.15 System Information.............................................. 78
3.4.8 HDD Power Management ............................................. 79
3.4.8.1 Stagger Power On Control........................................ 79
3.4.8.2 Time To Hdd Low Power Idle.................................... 80
3.4.8.3 Time To Hdd Low RPM Mode..................................... 80
3.4.8.4 Spin Down Idle HDD............................................... 81
3.4.8.5 View HDD Power Management ................................. 81
3.4.9 Ethernet Configuration................................................. 82
3.4.9.1 DHCP Function....................................................... 82
3.4.9.2 Local IP address..................................................... 83
3.4.9.3 HTTP Port Number.................................................. 84
3.4.9.4 Telnet Port Number................................................. 84
3.4.9.5 SMTP Port Number.................................................. 85
3.4.9.6 Gateway IP Setting................................................. 85
3.4.9.7 Netmask Setting .................................................... 85
3.4.9.8 View Network information ....................................... 86
3.4.10 View System Events................................................... 87
3.4.11 Hardware Monitor...................................................... 88
3.4.12 Mail (Alert by Mail) Configuration ................................ 89
3.4.13 SNMP Configuration................................................... 91
3.4.14 NTP Configuration...................................................... 93
3.4.14.1 NTP server IP#1................................................... 95
3.4.14.2 NTP server IP#2................................................... 95
3.4.14.3 Time Zone........................................................... 96
3.4.14.4 Automatic Daylight Saving..................................... 96
3.4.14.5 View NTP Information............................................ 97
INTRODUCTION
1. Introduction
This user guide provides SATA or SAS RAID controller Command Line
Interface (CLI) intructions for configuring and maintaining your SATA
or SAS RAID controller.
Before using this CLI, we assumes that you have already installed your
controller in your system. If you have not yet installed SATA or SAS
RAID controller, see ARECA SATA or SAS RAID controller installation
user manual for instructions.
1.1 Overview
This Command Line Interface (CLI) is provided for you to configure
and manage the Areca SATA or SAS RAID controller components
in Windows, Linux and FreeBSD or more environments. The CLI is
useful in environments where a graphical user interface (GUI) is
not available. Through the CLI, you perform most of the storage
management tasks that you can perform with the McRAID storage
manager GUI. With CLI, you can also use the CLI commands in
both interactive and non-interactive (script) mode, providing higher
level API functionalities.
There are often multiple ways to accomplish the same storage

management for your Areca controller. While this manual includes
instructions for performing configurations using the command line
interface, four additional configuration methods are also available:
• McBIOS RAID manager

• Firmware-embed web browser McRAID storage manager
through ArcHttp proxy server
• Firmware-embed web browser McRAID storage manager
through on-controller LAN port
• Push Button and LCD display panel
The CLI contains the same functionality offered by Areca McRAID

Storage Manager – Browser Edition.
CLI commands enable you to:
• Create RAID set

• Expand RAID set
8
INTRODUCTION
• Define volume set
• Add physical drive
• Modify volume set
• Modify RAID level/stripe size
• Define pass-through disk drives
• Modify system function
• Designate drives as hot spares
1.2 Supported Operating Systems

• Windows: Windows 2000, Windows XP, and Windows Server
2003, Windows Vista, Windows 2008 and Windows 7.
• Linux: RedHat, SuSE, ……etc.
• FreeBSD
• Solaris 10/11
• Mac OS
CLI supports both 32-bit and 64-bit versions. Be sure you are in-
stalling the correct version.
9
SOFTWARE INSTALLATION
2. Installing the Areca CLI
This section describes the procedures for installing Command Line In-
terface (CLI).
2.1 CLI Installation
2.1.1 For Windows
Below screen in this section are taken from a Windows/XP instal-

lation. If you are running other Windows, your installing screen
may look different, but the CLI installation is essentially the
same.
1. Insert the RAID controller CD in the CD-ROM drive. You aslo

can download the CLI from the website: www.areca.com.tw
2. Run the setup.exe file that resides at: <CD-ROM>\http\win-
dows\setup.exe on the CD-ROM.
3. Click on the “Setup” file then the Welcome screen appears.

Follow the on-screen prompts to complete CLI installation.
4. A program bar appears that measures the progress of the CLI.
10
5. When this screen complete, you have completed the CLI soft-
ware setup.
6. After a successful installation, the “Setup Complete” dialog
box of the installation program is displayed.
Click the “Finish” button to complete the installation.
2.1.2 For Linux, FreeBSD, Mac and Solaris
Areca CLI can be installed from the Areca shipping software CD,
or downloaded from the web site: www.areca.com.tw
The following is the CLI installation procedure in the Linux, Free-

BSD, Mac and Solaris.
1. Insert the SATA or SAS RAID controller CD in the CD-ROM

drive.
2. Copy the file CLI to the installation directory from which you
want to run the program.
11
2.2 Accessing CLI
2.2.1 For Windows
This section discusses the methods for accessing the CLI in Win-
dows.
To access the CLI:

1. Click on the “Start” button in the Windows 2000/XP/2003/
Vista/2008/7 task bar and then click “Program”.
2. CLI screen appears.
The CLI prompt is displayed in a DOS console window.
2.2.2 For Linux, FreeBSD, Mac and Solaris
To access the CLI from the Linux/FreeBSD/Mac/Solaris prompt,

display a window and type CLI in the directory. When the system
displays the CLI> prompt, which indicates that you can start to
use CLI commands.
For the commands to work in any directory, the path in the start-
up, please see your Linux/FreeBSD/Mac/Solaris documentation for
information on setting up directory paths.
12
CLI CONFIGURATION
3. CLI Command Line Configuration
3.1 Configuring Raid Sets and Volume Sets

You can configure RAID sets and volume sets with CLI function us-
ing Raid Set/Volume Set Function manually configuration method.
The configuration method requires a different level of user input.
The general flow of operations for RAID set and volume set con-
figuration is:
Step Action
1 Designate hot spares/pass-through (optional).
2 Create RAID sets using the available physical drives.
3 Define volume sets using the space in the RAID set.
4 Initialize the volume sets (logical drives) and use volume sets in the
host OS.
3.2 Conventions
You can enter only valid CLI commands at the command line
prompt.
All commands use the following syntax:
<CMD> [sub-command] [parameters]
The CLI syntax uses the following conventions for parameter:
<text> indicates items that you must specify.

[text] The text item within brackets is optional.
< ¦ > indicates an ‘or’ situation where the user has a choice be-
tween more than one option, but only one can be specified.
< ~ > indicates a range values where the user has a choice be-
tween these two values, but only one can be specified.
< , > Comma, indicates a separation between integer value.
13
CLI CONFIGURATION
3.3 Working Mode
You can also use the CLI commands in both interactive and non-
interactive (script) mode.
• Interactive Mode: Entering CLI commands at the main prompt

• Non-interactive Mode: As a series of single commands or creating
a script file (a multiple commands input)
3.3.1 Interactive Mode
You can run CLI in interactive mode, entering commands at the

main prompt and observing the results on the screen. The exam-
ples shown in this CLI manual reflect this interactive mode.
To run the CLI in the interactive mode

1. To enter interactive mode, type "CLI" and press "Enter".
The main prompt (CLI>) is displayed. This indicates that the
CLI program is waiting for a command input.
2. At the CLI prompt, you can input the commands.
Syntax
set <curctrl=xx ¦ password=xxxx>
Parameters
curctrl=xx
Example: CLI >set curctrl=1 password=0000 [Enter]

Set the selected controller 1 password as 0000.
Use this command to select the controller 1 on which to perform

an action. All actions or commands will be performed only on the
currently selected controller.
14
CLI CONFIGURATION
3.3.2 Non-interactive Mode
To run the CLI in a single command
You can use CLI with syntax and parameters, processing a single
command at a time. To process it, simply enter the command
with syntax and parameters.
Single commands can be useful when you want to perform a task

such as redirecting the console output of the command to a file.
Syntax
CLI ctrl=xx <command line with syntax and parameters>

The command line will be performed on the currently selected
controller ctrl=xx.
Example: cli ctrl=1 disk info drv=1

Get disk=1 drive information on the selected controller 1.
To run the CLI using automated script
This part describes how to write batch files and CLI command
scripts to perform the controller details task. You can run CLI
scripts by executing a batch file. The batch file is a text file con-
taining a valid list of CLI commands which you have included in
the file. A carriage return linefeed follows each command.
You can use the CLI commands alone in CLI command scripts or
in DOS batch files. You should already understand how to write
DOS batch files and be familiar with Windows-related backup
commands.
To execute a CLI command script, type the file name that con-
tains the CLI commands,
Syntax
<filename>
Where <filename> is the name of the text file you want to ex-
ecute.
15
CLI CONFIGURATION
Creating an Automated Script example
In its simplest example form, a text file contains two valid CLI
commands. A carriage return linefeed follows each command. The
diskinfo is the file included the following two commands:
cli ctrl=1 disk info drv=1 >> diskinfo.txt ===>save the ctrl=1,
disk=1 disk information into diskinfo.txt file.
cli ctrl=2 disk info drv=2 >> diskinfo.txt ===>save the ctrl=2,
disk=2 disk information into diskinfo.txt file.
To run the automated script, enter: diskinfo

The CLI command script stores both controller 1/disk=1 and con-
troller 2/disk=2 drive information into diskinfo.txt file.
3.4 Command Categories

This chapter provides detailed information about the SATA or SAS
RAID controller CLI commands. From a functional point of view,
command can be grouped into the following functional categories.
This list may vary depending upon the SATA or SAS RAID controller
model and the installed features.
The following table is the CLI command summary:
CMD Description
main Show command categories
set Open the controller to accept the CLI. It includes the controller as-
signment and password check
rsf RAID set functions, create, modify or delete a customized RAID set
vsf Volume set functions, create modify or delete a customized volume
set. It also includes the create and delete the Hot-Spare function
disk Physical drive functions, view individual disk information
sys RAID system function, setting the RAID system configurations
adsys Advanced system function, setting the advanced features to fit dif-
ferent video application.
hddpwr HDD power management function, it is designed to reduce power
consumption and heat generation on idle drives.
net Ethernet function, setting Ethernet configurations
16
CLI CONFIGURATION
event System events records or clears all system events in the buffer
hw Hardware monitor information shows all system environment status
mail To configure mail notification
snmp SNMP information
ntp NTP function synchronizes the time of a RAID controller to another
server or reference time source.
exit Exit CLI
Main Command
Main command in this category allows you to display main com-

mand in the SATA or SAS RAID controller. For details, see “Main
Command” on section 3.4.1.
Set Commands
To prepare a SATA or SAS RAID controller to receive a CLI com-

mand, you first need to select the controller. The set commands
select controller and prepare it to receive more CLI commands.
Typical operations include: select the controller, and key in the
password from the SATA or SAS RAID controllers. For details, see
“Set Commands” on section 3.4.2.
Rsf Commands
The rsf commands perform all RAID set operations on the drives
and RAID sets connect to the SATA or SAS RAID controller. Typical
operations include: create RAID set, delete RAID set, create hot
spare, and delete hot spare from the SATA or SAS RAID controller.
For details, see “Raid Set Function” on section 3.4.3.
Vsf Commands
The vsf commands perform all volume set operations on the
RAID sets connect to the SATA or SAS RAID controller. Typical
operations include: create volume set, delete volume set, modify
volume set, and migrate volume set from the SATA or SAS RAID
controller. For details, see “Volume Set Function” on section 3.4.4.
17
CLI CONFIGURATION
Disk Commands
The disk commands perform all pass-through operations on the

drives connect to the SATA or SAS RAID controller. Typical opera-
tions include: create pass-through, delete pass-through, modify
pass-through, and view disk information from the SATA or SAS
RAID controller. For details, see “Disk Function” on section 3.4.5.
Sys Commands
The sys commands perform the tuning of the SATA or SAS RAID
controller setting. Typical operations include: mute the controller,
JBOD/RAID, modify password, rebuild priority and view controller
information from the SATA or SAS RAID controller. For details, see
“Raid System Function” on section 3.4.6.
Adsys Commands
The advanced features on the Areca RAID controller are for power
user to tune the firmware behavior to fit different video applica-
tion. For details, see “Advanced System ” on section 3.4.7.
Hddpower Commands
The “HDD Power Management” is designed to reduce power

consumption and heat generation on idle drives. For details, see
“HDD Power Management” on section 3.4.8.
Net Commands
The net commands allows you to display Ethernet setting. For

details, see “Ethernet configuration” on section 3.4.9.
Event Commands
The event command allows you to display system event notifica-

tion that have been generated events by the SATA or SAS RAID
controller. Typical operations include: create pass-through, delete
pass-through, modify pass-through, and view disk information
from the SATA or SAS RAID controller. For details, see “Event
18
CLI CONFIGURATION
Function” on section 3.4.10.
Hw Commands
The hw command allows you to display hardware information that

have been collected by controllers. The “Hardware Monitor Infor-
mation” provides the temperature and fan speed (chassis fan) of
the SATA or SAS RAID controller. For details, see “Hardware Moni-
tor Function” on section 3.4.11.
Mail Commands
The mail command allows you to display e-mail information.

The firmware contains a SMTP manager monitoring all system
events. Single or multiple user notifications can be sent via “Plain
English” e-mails with no software required.
SNMP Commands
The SNMP command allows you to display SNMP information.

The firmware SNMP agent manager monitors all system events
and the SNMP function becomes functional with no agent software
required.
Exit Command
To close the currently selected controller and exit the CLI, use the
exit command.
Syntax:
CLI> exit
Help Command
This command provides an on-line table of contents, providing

brief descriptions of the help sub-commands. You can use the
<CMD> -h or –help to get detailed information about the sub-
command.
19
CLI CONFIGURATION
Syntax:
<CMD> -h or help
CMD: set, rsf, vsf, disk, sys, net, event or hw.
3.4.1 Main Commands
The main command shows the currently selected controller and

all controllers installed in the system.
This command provides a table of contents, providing brief de-

scriptions of the commands and controller installed in the system.
Typical output looks like:
3.4.2 Set Commands
If there is more than one RAID controller in the system (up to

four are supported), use this command to select the appropriate
controller on which to perform an action. All actions or commands
will be performed only on the currently selected controller.
20
CLI CONFIGURATION
To prepare a controller to receive a CLI command, first you need

to select the controller. To select the controller and prepare it to
receive CLI commands:
3.4.2.1 None
To define the selected controller, follow the procedure below:
Syntax:
set none
Parameter:
<curctrl=xx>
Description:
To prepare a RAID controller to receive a CLI command, first you
need to select the controller. You can select one RAID controller
at any time. To select controller and prepare it to receive more
CLI commands.
Example:
CLI > set curctrl=1 [Enter]
Select the controller 1 to receive the CLI command.
To set the selected controller password, follow the procedure

below:
21
CLI CONFIGURATION
Parameter:
<password=xxxx>
Description:
The password option allows user to set or clear the RAID con-
troller’s password protection feature. Once the password has
been set, the user can only monitor and configure the RAID
controller by providing the correct password. The password is
used to protect the RAID controller from unauthorized entry. The
controller will check the password only when entering the rsf,
vsf and disk function from the initial screen. The RAID controller
will automatically go back to the initial screen when it does not
receive any command in twenty seconds. The RAID controller
password is default setting at 0000 by the manufacture.
If the password of the RAID controller is already disabled you do
not need to specify it again when selecting the RAID controller.
Example
CLI > set password=0000 [Enter]
Enter the controller 1 password as 0000.
3.4.2.2 Save All Controller Information
To save the selected controller all information, follow the proce-

dure below:
Syntax:
set savecfg
Parameter:
<path=<xxx>>
Description:
To save all controller information into disk. If you would like to
record these settings, such as RAID set/volume set configura-
tions, system configuration event log, system information and
drive information, you can use the this command to record them
to a text file
Example:
CLI > set savecfg path=/cfg [Enter]
22
CLI CONFIGURATION
Save all information into folder "/cfg". If you just specify a path
without file name, CLI will automatically specify file name as
"controller<xx>': <xx> is the controller#.
3.4.3 Rsf Commands
User manual configuration can complete control of the RAID set

setting. Select the RAID set function to manually configure the
RAID set for the first time or deletes existing RAID set and recon-
figures the RAID set.
The help command rsf –h provides a table of contents, providing

brief descriptions of the sub-commands. Typical output looks like:
23
CLI CONFIGURATION
3.4.3.1 Create Raid Set
To define RAID set, follow the procedure below:
Syntax:
rsf create
Parameter:
<drive=xxx>
Description:
The drv=xxx selects the specified the SAS/SATA drive connected
to the current controller that user wants to add in a single RAID
set.
Parameter:
[name =xxx]
Description:
Enter 1 to 15 alphanumeric characters to define a unique identi-
fier for a RAID set. The default RAID set name will always assign
as Raidset # if the command doesn’t specify the name param-
eter.
Parameter:
[mode=<1>]
Description:
The mode=1 selects “Max 16 volumes” for the currently selected
RAID set. This is used to for SAS RAID adapter HDDs roaming
to previous SATA RAID adapter. For SAS RAID adapter, “Max 128
volumes” is the default number.
Example:
CLI > rsf create drv=1~3,5,7 name=raidset1 mode=1[Enter]
To create a RAID set, use the create RAID set command.
RAID set is created from disk 1, 2, 3, 5 and 7. The RAID set’s
name is raidset1 and Max 16 volumes.
3.4.3.2 Delete Raid Set

To delete RAID set, follow the procedure below:
24
CLI CONFIGURATION
Syntax:
rsf delete
Parameter:
<raid=xx>
Description:
To change a RAID set, first you should delete it and recreate the
RAID set. To delete a RAID set, specify the RAID set number
that user want to delete. it will free the associated disk occupied
by the RAID set.
Example:
CLI > rsf delete raid=1 [Enter]
The raidset1 will delete and the associated disk no. 1, 2, 3, 5,
and 7 will free.
3.4.3.3 Expand Raid Set
To expand RAID set, follow the procedure below:
Syntax:
rsf expand
Parameter:
<raid=xxx>
This parameter specifies the target RAID set number that user
wants to expand.
Parameter:
[drive=xxxx]
This parameter specifies the available disk drives that user
wants to expand the RAID set.
Description:
Instead of deleting a RAID set and recreating it with additional
disk drives, the expand RAID set function allows the users to
add disk drive to the RAID set that was created.
The new add capacity will be define one or more volume sets.
25
CLI CONFIGURATION
Follow the instruction presented in the volume set Function to
create the volume sets.
Example:
CLI > rsf expand raid=1 drv=3[Enter]
raid set#1 is expand by adding the disk drive 3.
NOTE:
1. Once the Expand RAID set process has started, user

cannot stop it. The process must be completed.
2. If a disk drive fails during RAID set expansion and a hot

spare is available, an auto rebuild operation will occur
after the RAID set expansion completes.
3. Migrating occurs when a disk is added to a RAID Set.

Migration status is displayed in the RAID status area of
the RAID set information when a disk is added to a RAID
set. Migrating status is also displayed in the associated
volume status area of the volume set information when
a disk is added to a RAID set.
3.4.3.4 Activate Incomplete Raid Set
The following screen is the RAID set information after one of its
disk drive has removed in the power off state.
When one of the disk drive is removed in power off state, the
RAID set state will change to “Incomplete” state. After the RAID
controller is power on in “Incomplete” state, user still wants to
continue to work. User can use the “Activate Incomplete Raid
Set” command to active the RAID set. After user complete the
function, the RAID set state will change to “Degraded” mode.
To activate incomplete RAID set, follow the procedure below:
Syntax:
rsf activate
Parameter:
<raid=xxx>
26
CLI CONFIGURATION
Description:
This parameter specifies the incomplete RAID set number that
user wants to activate it.
Example:
In the following example, raid set#1 is in the incomplete state.
CLI > rsf expand raid=1 [Enter]
After user complete the command, the RAID state will change to
“Degraded” mode.
3.4.3.5 Create Hot Spare
To assign one or more spare disks for all RAID sets, use this
command. This command enables you to configure the drive as
a global hot spare prior to a drive failure so that the RAID sets
contains the resources it needs to survive a failure.
“Create Hot Spare” option gives you the ability to define a global
hot spare. When creating a hot spare, be sure to select a drive
with an equal or larger size than the smallest drive in your RAID
set. Otherwise it can’t be used in a rebuild.
The controller automatically assigns the new disk as the Hot-

spare without your having to first assign it using this command.
To create hot spare, follow the procedure below:
Syntax:
rsf createhs
Parameter:
<drv=xx>
Description:
This parameter specifies the disk drive that user wants to create
as Hot-Spare.
Example:
CLI > rsf createhs drv=3 [Enter]
Assign the drive no. 3 as the global Hot-Spare disk.
27
CLI CONFIGURATION
3.4.3.6 Delete Hot Spare
This command deletes the create hot spare command defined

hot spare disk. To delete hot spare, follow the procedure below:
Syntax:
rsf deletehs
Parameter:
<drv=xx>
Description:
This parameter specifies the hot spare disk drive that user wants
to delete.
Example:
CLI > rsf deletehs drv=1 [Enter]
Free the Hot-Spare drive 1.
3.4.3.7 Offline Raid Set

This command is for customer being able to unmount and
remount a multi-disk volume. To unmount and remount a multi-
disk volume, follow the procedure below:
Syntax:
rsf offline
Parameter:
<raid=xx>
Description:
This parameter specifies the RAID set number that user wants
to offline it.
Example:
CLI > rsf offline raid=1 [Enter]
After user complete the command, the RAID state will change to
offline mode.
28
CLI CONFIGURATION
3.4.3.8 Raid Set Information
After creating a RAID set, use this command to display informa-

tion about the RAID sets. To display all RAID sets information,
follow the procedure below:
Syntax:
rsf info
Description:
Use this command to display all RAID sets information. The
RAID set information will show as following. You can only view
the information of all RAID sets.
Example:
CLI > rsf info [Enter]
Display all RAID sets information, which belongs to the currently
selected RAID controller.
3.4.4 Vsf Commands
A volume set is seen by the host system as a single logical de-

vice. It is organized in a RAID level with one or more physical
disks. RAID level refers to the level of data performance and
protection of a Volume Set. A volume set capacity can consume
all or a portion of the disk capacity available in a RAID set. Mul-
tiple volume sets can exist on a group of disks in a RAID set.
Additional volume sets created in a specified RAID set will reside
on all the physical disks in the RAID set. Thus each volume set on
the RAID set will have its data spread evenly across all the disks
in the RAID set.
29
CLI CONFIGURATION
The RAID controller has the following restrictions with regard to
CLI terminology and nomenclature:
1. SCSI Channel—SCSI Channel always equals 0.

2. SCSI LUN /SCSI ID—“SCSI LUN /SCSI ID” always means “Vol-
ume Set”.
30
CLI CONFIGURATION
3.4.4.1 Create Volume Set
The following is the volume set features for the RAID controller.
1. Volume sets of different RAID levels may coexist on the same

RAID set.
2. Up to 16 volume sets can be created in a RAID set for RAID

controller and 128 volume sets for SAS RAID controller.
The “Create Volume Set” attribute allows user to select the

Raid Set Number, Volume Name, Capacity, RAID Level, Greater
Two TB Volume Support, Initialization Mode, Stripe Size, Cache
Mode, Tagged Command Queuing, SCSI Channel/SCSI ID/SCSI
Lun, and Full Volume Encryption.
To create volume set, follow the procedure below:
Syntax:
vsf create
Parameter :
• Raid Set Number

<raid=xx>
Description:
Select the RAID set number for creating the volume set.
• Volume Name
<name=xxx>
Description:
The default volume name will always appear as Volume Set#.
You can rename the volume set name providing it does not ex-
ceed the 15 characters limit.
31
CLI CONFIGURATION
• Capacity
<capacity=xxx>
Description:
The maximum volume size is default in the first setting. Each
volume set has a selected capacity which is less than or equal to
the total capacity of the RAID set on which it resides.
• Raid Level
[level=<0:1:3:5:6>]
Description:
Set the RAID level for the volume set.
• Greater Two TB Volume Support

[gt2tb=<64BIT:WIN>]
Description:
Controller uses the “Greater Two TB Volume Support” submenu
to set the volume capacity and sector size. Greater Two
TB Volume Support option: “No”, “64bit LBA” and “Use 4K
Block”.
• Stripe Size
[stripe=<4:8:16:32:64:128:256:512:1024>]
Description:
This parameter sets the size of the segment written to each
disk in a RAID 0, 1, 1E, 5 or 6 logical drive. You can set the
stripe size to 4 KB, 8 KB, 16 KB, 32 KB, 64 KB, 128 KB, 256KB,
512KB, or 1024KB.
• SCSI Channel
[ch=<0>]
Description:
ch represents channel, which is always zero on the RAID con-
troller.
• SCSI ID
[id=<0~15>]
32
CLI CONFIGURATION
• SCSI LUN
[lun=<0~7>]
Description:
SCSI LUN/SCSI ID - “SCSI LUN/SCSI ID” always means “Volume
Set”
• Cache Mode
[cache=<Y:N>]
Description:
This command allows you to turn on or off the write-back cache
on a specified unit. User can set the cache mode to: Write-
Through Cache (N) or Write-Back Cache (Y).
• Tag Queuing
[tag=<Y:N>]
Description:
The “Enabled” option is useful for enhancing overall system
performance under multi-tasking operating systems. The Com-
mand Tag (Drive Channel) function controls the SAS command
tag queuing support for each drive channel. This function should
normally remain enabled. Disable this function only when using
older SAS drives that do not support command tag queuing.
• Initialization
[fginit=<Y:N>]
Description:
In the Background Initialization (N), the initialization proceeds
as a background task, the volume set is fully accessible for sys-
tem reads and writes. The operating system can instantly access
to the newly created arrays without requiring a reboot and wait-
ing the initialization complete. In Foreground Initialization (Y),
the initialization proceeds must be completed before the volume
set ready for system accesses.
Example:
To create a volume set, use the create volume set command.
In the following example, Volume 0 is created from RAID set
1on device ch:0 id:01 lun:0 from 1.5GB of available space. The
33
CLI CONFIGURATION
volume set’s cache and tag are enabled, and the name is areca.
The volume set sets in RAID level 5 and “Foreground Initializa-
tion” mode.
CLI>vsf create raid=1 capacity=1.5 level= 5 ch=0 id=1 lun=0

name=areca tag=Y cache=Y stripe=16 fginit=Y
• Full Volume Encryption

[entype=<0<No Encryption>:1<256bit password>:2<256bit
AES>:3<128bit password>:4<128bit AES>>]
Description:
Controller based hardware encryption describes the encryp-
tion of data occurring at the disk array controller before being
sent to the disk drives. Since RAID controller is a natural central
point of all data therefore encryption at this level is inherent and
also reduces deployment complexity.
Encrypting your volume can give your data an extra layer of

protection beyond setting up a controller password. Encryption
will conceal your volume’s data and make accessing the files
almost impossible for anyone who does not know your encryp-
tion key. Data saved in the volume will be hidden by Algorithm
developed by Areca Technology. With this scramble process, no
one can see and access into the hidden volume data without ac-
cess key.
Controllers support 128- and 256-bit encryption keys using AES

(a key size of 128, or 256 bits), or password (a variable key
size). Each encryption key size causes the algorithm to behave
slightly differently, so the increasing key sizes not only offer a
larger number of bits with which you can scramble the data, but
also increase the complexity of the cipher algorithm. We provide
five new key options in the Full Volume Encryption: “No Encryp-
tion”, “256Bit key, Password”, “256Bit key, AES”, “128Bit key,
Password”, “128Bit key, AES”.
34
CLI CONFIGURATION
3.4.4.2 Create Raid50/60 (SAS Only)
The new create volume set attribute allows user to select the
volume name, RAID level, capacity, greater two TB volume sup-
port, initialization mode, stripe size, cache mode, tagged com-
mand queuing, SCSI channel/SCSI ID/SCSI Lun. Please refer to
above section for details description of each item.
Syntax:
vsf create5060
Parameter:
• Raid Set Number

<raid=xx>
Description:
Select the RAID set number for creating the volume set.
• Volume Name
<name=xxx>
Description:
The default volume name will always appear as Volume Set#.
You can rename the volume set name providing it does not ex-
ceed the 15 characters limit.
• Capacity
<capacity=xxx>
Description:
The maximum volume size is default in the first setting. Each
volume set has a selected capacity which is less than or equal to
the total capacity of the RAID set on which it resides.
• Raid Level
[level=<30:50:60>]
Description:
Set the RAID level for the volume set.
35
CLI CONFIGURATION
Note:
RAID level 50 and 60 can support up to eight sub-volumes
(RAID set).
• SCSI Channel
[ch=<0>]
Description:
ch represents channel, which is always zero on the SATA/SAS
RAID controller.
• SCSI ID
[id=<0~15>]
• SCSI LUN
[lun=<0~7>]
Description:
SCSI LUN/SCSI ID - “SCSI LUN/SCSI ID” always means “Volume
Set”
• Tag Queuing
[tag=<Y:N>]
Description:
The enabled option is useful for enhancing overall system per-
formance under multi-tasking operating systems. The command
tag (Drive Channel) function controls the SAS command tag
queuing support for each drive channel. This function should
• Cache Mode
[cache=<Y:N>]
Description:
on a specified unit.
User can set the cache mode to: “Write-Through Cache” (N) or
“Write-Back Cache” (Y).
36
CLI CONFIGURATION
• Strip Size
[stripe=<4:8:16:32:64:128:256:512:1024>]
Description:
This parameter sets the size of the segment written to each
disk in a RAID 0, 1, 1E, 5 or 6 logical drive. You can set the
stripe size to 4 KB, 8 KB, 16 KB, 32 KB, 64 KB, 128 KB, 256KB,
512KB, or 1024KB.
• Initialization
[fginit=<Y:N>]
Description:
In the “Background Initialization (N)”, the initialization proceeds
as a background task, the volume set is fully accessible for sys-
tem reads and writes. The operating system can instantly access
to the newly created arrays without requiring a reboot and wait-
ing the initialization complete. In “Foreground Initialization (Y)”,
the initialization proceeds must be completed before the volume
set ready for system accesses.
Example:
To create a volume set, use the create volume set command.
In the following example, Volume 0 is created from RAID set
1on device ch:0 id:01 lun:0 from 1.5GB of available space. The
volume set’s cache and tag are enabled, and the name is areca.
The volume set sets in RAID level 5 and Foreground Initialization
mode.
CLI>vsf create5060 capacity=10G level= 50 ch=0 id=1 lun=0
name=areca tag=Y cache=Y stripe=16 fginit=Y
3.4.4.3 Delete Volume Set
To delete volume set, follow the procedure below:
Syntax:
vsf delete
Parameter:
<vol=xx>
37
CLI CONFIGURATION
Description:
Use this command to delete volume set from RAID set system
function.
Example:
CLI > vsf delete vol=1 [Enter]
Delete the VolumeSet#1.
3.4.4.4 Modify Volume Set
To modify volume set, follow the procedure below:
Syntax:
vsf create
Parameters:
<vol=xx> [level=<0:1:3:5:6>] [ch=<0>] [id=<0~15>]
[lun=<0~7>] [name=xxx] [tag=<Y:N>] [cache=<Y:N>]
[stripe=<4:8:16:32:64:128:256:512:1024>]
Description:
The user can use the modify volume set command to change the
current selected volume set attributes are defined by the volume
set create command. The attribute column headings are:
• The Raid Level,

• The Stripe Size,
• The SCSI ID/SCSI LUN/,
• The Cache Mode,
• The Tagged Queuing, and
• The Volume Name (number).
Note:
Migrating occurs when a volume set is migrating from one
RAID level to another, a volume set stripe size changes,
or when a disk is added to a RAID set. Migration status
is displayed in the volume status area of the volume set
information when one RAID level to another, a volume set
strip size changes or when a disk is added to a RAID set.
38
CLI CONFIGURATION
3.4.4.5 Check Volume Set
To check volume set status, follow the procedure below:
Syntax:
vsf check
Parameters:
<vol=xx>
Description:
Use this option to verify the correctness of the redundant data
in a volume set. For example, in a system with dedicated parity,
volume set check means computing the parity of the data disk
drives and comparing the results to the contents of the dedi-
cated parity disk drive.
3.4.4.6 Stop Volume Set Check
To stop volume set check, follow the procedure below:
Syntax:
vsf stopcheck
Description:
Use this option to stop all the “Check Volume Set” function.
3.4.4.7 Generate New Encrypted - Volume Key

File (ARC-1883 Series, ARC-1882 Series and ARC-
8050/8050T2)
To generate new encrypted - volume key file, follow the proce-

dure below:
Syntax:
vsf genkey
Parameter:
<path=xxx>
39
CLI CONFIGURATION
Description:
The New Encrypted - Volume Key value is generated in this
command by a random number process. The key file includes
all keys that assign to every volume on the RAID controller. The
RAID controller does not retain the key on the itself. If the New
Encrypted - Volume Key is not available, then the data is not
recoverable from that volume. However, good security practice
encourages New Encrypted - Volume Key to be backed up.
Example:
CLI > vsf genkey path=c:\key
Generate a key file into c:\key.
Syntax:
vsf genkey2
Parameter:
<path=xxx>
Description:
The New Encrypted - Volume Key value is generated in this com-
mand by a random number process. It will generate key file(s)
by volumeset and the file name is the same as the volumeset
name. The RAID controller does not retain the key on the itself.
If the New Encrypted - Volume Key is not available, then the
data is not recoverable from that volume. However, good se-
curity practice encourages New Encrypted - Volume Key to be
backed up.
Example:
CLI > vsf genkey2 path=c:\key
Generate a key file into c:\key.
40
CLI CONFIGURATION
3.4.4.8 Lock Volume (ARC-1883 Series, ARC-1882
Series and ARC-8050/8050T2)
To make an encrypted - volume key invalidated, follow the pro-

cedure below:
Syntax:
vsf lock
Parameter:
<vol=xx>
Description:
Lock Volume function secures a volume’s data from unauthor-
ized access or modification in the event of drive theft, as well as
more routine activities such as the return of defective drives for
servicing or the decommission or repurposing of drives. When
the Lock Volume is configured by the user (or I.T.), the encrypt-
ed - Volume Key is used to encrypt the data inside the volume.
Example:
CLI > vsf lock vol=1 [Enter]
Make VolumeSet#1 key invalidation.
3.4.4.9 Download an Encrypted - Volume Key File

(ARC-1883 Series, ARC-1882 Series and ARC-
8050/8050T2)
To download an encrypted - volume key file, follow the proce-

dure below:
Syntax:
vsf dlkey
Parameter:
<path=xxx>
Description:
However, once the encrypted volume is powered on, the volume
will ask for the Encrypted - Volume key to unlock it. If the cor-
rect Encrypted - Volume key is not given, the volume cannot be
41
CLI CONFIGURATION
decrypted. Use this command to unlock the volume.
Example:
CLI > vsf dlkey path=c:\key
Download a key file to make encrypted - volume validated.
3.4.4.10 Display Volume Set Info.
After creating all volume sets, use the command to display in-
formation about the selected RAID controller.
To display volume set information, follow the procedure below:
Syntax:
vsf info
Parameter:
<vol=xx>
Description:
Use this command to display all "Volume Sets Information". The
"Volume Set Information" will show as following. You can only
view the information of all volume sets.
Example:
CLI > vsf info [Enter]
Display all volume sets information, which belong to the
currently selected RAID controller.
42
CLI CONFIGURATION
3.4.5 Disk Commands
Use the disk commands to manage disks connected to the RAID

controller. The CLI enables you to create, delete and modify the
pass through disk characteristics.
43
CLI CONFIGURATION
3.4.5.1 Create Pass-Through Disk
To create pass-through disk, follow the procedure below:
Syntax:
disk create
Parameter:
• Drive Number
<drive=xx>
Description:
Select the disk number for creating the pass-through disk.
• SCSI Channel
[ch=<0>]
Description:
ch represents channel, which is always zero on the RAID con-
troller.
• SCSI ID
[id=<0~15>]
• SCSI LUN
[lun=<0~7>]
Description:
SCSI LUN /SCSI ID—“SCSI LUN /SCSI ID” always means “Pass-
Through disk”
• Tag Queuing
[tag=<Y:N>]
Description:
The Enabled option is useful for enhancing overall system per-
formance under multi-tasking operating systems. The Command
Tag (Drive Channel) function controls the SAS command tag
queuing support for each drive channel. This function should
44
CLI CONFIGURATION
• Cache Mode
[cache=<Y:N>]
Description:
on a specified unit.
User can set the cache mode to: Write-Through Cache (N) or
Write-Back Cache (Y).
• Speed
[speed=<150:300>]
Description:
The RAID controller supports ATA150, ATA133, ATA100, ATA66,
and ATA33 Mode.
3.4.5.2 Delete Pass-Through Disk
To delete pass-through disk, follow the procedure below:
Syntax:
disk delete
Parameter:
<drive=xx> - pass-through disk drive for which to delete.
Description:
Use this command to delete Pass-through drive from the Pass-
through drive pool.
3.4.5.3 Modify Pass-Through Disk
To modify pass-through disk, follow the procedure below:
Syntax:
disk modify
Parameter:
<drive=xx> [ch=<0>] [id=<0~15>] [lun=<0~7>] [tag=<Y:
N>] [cache=<Y:N>]
45
CLI CONFIGURATION
Description:
Use this option to modify the “Pass-Through Disk Attribute”. The
“Disk Attributes” are defined by the “Create Pass-Through Disk”
command.
3.4.5.4 Fail A Disk
To set a healthy HDD as a failed, follow the procedure below:
Syntax:
disk fail
Parameter :
<drive=xx>
Description:
It sets a normal working disk as “failed” so that users can test
some of the features and functions.
Example:
CLI > disk fail drv=1 [Enter]
Set the drive#1 as “failed”.
3.4.5.5 Activate A Fail Disk
To activate a failed HDD to be back online, follow the procedure

below:
Syntax:
disk activate
Parameter :
<drive=xx>
Description:
It forces the current “failed” disk in the system to be back on-
line. “Activate A Failed Disk” function has no effect on the re-
moved disks, because a “removed” disk does not give the con-
troller a chance to mark it as “failure”.
Example:
CLI > disk activate drv=1 [Enter]
46
CLI CONFIGURATION
Activate the failed drive on drive#1 to be back online.
3.4.5.6 Identify Selected Drive
You can used the "Identify Selected Drive" feature to prevent

removing the wrong drive, the selected drive fault LED will blink.
Syntax:
disk identify
Parameter:
<drive=xx>
Description:
Use this option to prevent removing the wrong drive.
3.4.5.7 Display Disk SMART Data
Use this command to show disk HDD SMART information.
Syntax:
disk smart
Parameter:
<drive=xx>
Description:
When you choose this option, the specify physical disks
connected to the RAID controller SMART informations are listed.
CLI > disk SMART drv=1 [Enter]

Display drive number=1 disks SMART information, which belong
to the currently selected RAID controller.
3.4.5.8 Self Test
To perform a S.M.A.R.T off-line short or extended self-test, fol-

low the procedure below:
Syntax:
disk sttest
47
CLI CONFIGURATION
Parameter:
<drive=xx> [mode=<short:extended>]
Description:
Current S.M.A.R.T selective self-tests provides for a
short self-test and an extended self-test option. The short selft-
est does read scan of a small area of the media in a short time.
The area of the media scanned is vendor specific. The extended
self-test does read scan of the entire media. As the capacity of
disk drives increases, the time to complete the extended selftest
becomes exceedingly long.
Example:
CLI > disk sttest drv=1~4 mode=short [Enter]
Perform a self test on drive number=1 to 4 disks and
mode=short, which belong to the currently selected RAID con-
troller.
3.4.5.9 View Drive Information
After connecting all disks, use this command to display drive

information about the selected RAID controller.
To view all disks information, please follow the procedure below:
Syntax:
disk info
Description:
When you choose this option, the physical disks connected to
the RAID controllers are listed.
Syntax:
disk info <drv=xx>
The selected disk Information will show as following.
Example:
CLI> disk info drv=1
Display the disk number=1 detail information.
48
CLI CONFIGURATION
3.4.5.10 SMART Off-line Data Collection (SATA Con-

troller Only)
To perform a S.M.A.R.T off-line data collection, follow the proce-

dure below:
Syntax:
disk dctest
Parameter:
<drive=xx> drive number
Description:
Current S.M.A.R.T selective self-tests provides for a short self-
test and an extended self-test option. The short self-test does
read scan of a small area of the media in a short time. The area
of the media scanned is vendor specific. The extended self-
test does read scan of the entire media. As the capacity of disk
drives increases, the time to complete the extended self-test
becomes exceedingly long.
49
CLI CONFIGURATION
3.4.5.11 Specific Read/Write Test (SATA Controller
Only)
To perform a vender specific read/write test, follow the proce-

dure below:
Syntax:
disk rwtest
Parameter:
<drive=xx> : driver number
[p=<1~100>] : percentage
Description:
Select Percentage to Test - Allow you to change the percentage
of the disk drive for utility to test. Enter the zero in this option
means without needing read/write test the target.
Example:
CLI > disk rwtest drv=1~4 p=20[Enter]
Perform a read/write test on the drive number 1~4.
3.4.5.12 Abort Read/Write Test (SATA Only)
To abort read/write test, follow the procedure below:
Syntax:
disk abortrwtest
Parameter:
<drive=xx>
Description:
Abort the abort read/write test process on previous command.
3.4.5.13 Check Read/Write Test (SATA Controller

Only)
To check the result of read/write test, follow the procedure be-

low:
50
CLI CONFIGURATION
Syntax:
disk checkrwtest
Parameter:
<drive=xx>
Description:
Get the read/write test result.
3.4.6 Raid System Function
To facilitate tuning of the RAID controller for its operation, a num-

ber of controller settings can be changed.
The sys -h command can view the sub-command and parameters
of the [ sys ] function.
51
CLI CONFIGURATION
3.4.6.1 Mute The Alert Beeper
To mute the alert beeper, follow the procedure below:
Syntax:
sys beeper
Parameter:
<p=<0<mute>:1<disable>:2<enable>>>
52
CLI CONFIGURATION
Description:
The “Mute The Alert Beeper” command is used to control the
RAID controller beeper function. This command turns the beeper
off temporarily. The beeper will still activate on the next event.
Example:
CLI > sys beeper p=0 [Enter]
This command turns the selected RAID controller beeper off
temporarily. The beeper will still activate on the next event.
3.4.6.2 Change Password
To change the password, follow the procedure below:
Syntax:
sys changepwd
Parameter:
<P=xxx>
Description:
The password option allows user to set or clear the RAID con-
troller password protection feature. Once the password has been
set, the user can only monitor and configure the RAID controller
by providing the correct password. The password is used to pro-
tect the internal RAID controller from unauthorized entry. The
controller will check the password only when entering the Main
menu from the initial screen. The RAID controller will automati-
cally go back to the initial screen when it does not receive any
command in twenty seconds.
To disable the password, leave the parameter column blank. The
existing password will be cleared. No password checking will oc-
cur when entering the main menu from the starting screen.
Example:
CLI > sys changepwd p=11111 [Enter]
The selected RAID controller password will change to new pass-
word:11111.
53
CLI CONFIGURATION
3.4.6.3 RAID/JBOD Function
To change the host mode, follow the procedure below:
Syntax:
sys mode
Parameter:
<p=<0<RAID>:1<JBOD>>>
Example:
CLI > sys mode p=1 [Enter]
The host mode will change to JBOD.
3.4.6.4 Raid Rebuild Priority
To change the background task priority, follow the procedure

below:
Syntax:
sys rebuildpt
Parameter:
<p=<0<ulow>:1<low>:2<medium>:3<high>>>
Description:
The “Raid Rebuild Priority’ is a relative indication of how much
time the controller devotes to a rebuild operation. The RAID
controller allows user to define the rebuild priority (ulow, low,
normal, high) to balance volume set access and rebuild tasks
appropriately.
Example:
CLI > sys rebuildpt p=0 [Enter]
Set the controller works at ultra low rebuild rate. It will provide
more computing resources for the system activity.
54
CLI CONFIGURATION
3.4.6.5 Maximum SATA Mode (SATA Controller Only)
To change the max speed, follow the procedure below:
Syntax:
sys maxspeed
Parameter:
<p=<0<SATA150>:1<SATA150+NCQ>:2<SATA300>:3<SATA3
00+NCQ>>>
Description:
The RAID controller can support up to SATA ll, which runs up to
300MB/s, twice as fast as SATA150. NCQ is a command proto-
col in Serial ATA that can only be implemented on native Serial
ATA hard drives. It allows multiple commands to be outstand-
ing within a drive at the same time. Drives that support NCQ
have an internal queue where outstanding commands can be
dynamically rescheduled or re-ordered, along with the necessary
tracking mechanisms for outstanding and completed portions of
the workload. The RAID controller allows the user to choose the
SATA Mode: SATA150, SATA150+NCQ, SATA300, SATA300+NCQ.
Example:
CLI > sys maxspeed=p=3 [Enter]
The selected RAID controller maxspeed will change to
SATA300+NCQ.
3.4.6.6 HDD SMART Status Polling (SATA Controller

Only)
Use this command to change HDD SMART status polling, follow

the procedure below:
Syntax:
sys smartpoll
Parameter:
<p=<0<disabled>:1<enabled>>>
55
CLI CONFIGURATION
Description:
An external RAID enclosure has the hardware monitor in the
dedicated backplane that can report HDD temperature status
to the controller. However, PCI cards do not use backplanes if
the drives are internal to the main server chassis. The type of
enclosure cannot report the HDD temperature to the controller.
For this reason, “HDD SMART Status Polling” was added to en-
able scanning of the HDD temperature function. It is necessary
to enable “HDD SMART Status Polling” function before SMART
information is accessible. This function is disabled by default.
Example:
CLI > sys smartpoll p=0 [Enter]
Set the controller works at disabled mode.
3.4.6.7 NCQ Support
Use this command to change ncq mode, follow the procedure

below:
Syntax:
sys ncq
Parameter:
<p=<0<enabled>:1<disabled>>>
Description:
The controller supports both SAS/SATA disk drives. The SATA
NCQ allows multiple commands to be outstanding within a
drive at the same time. Drives that support NCQ have an inter-
nal queue where outstanding commands can be dynami-cally
rescheduled or re-ordered, along with the necessary tracking
mechanisms for outstanding and completed portions of the
workload. The RAID controller allows the user to select the SATA
NCQ support: “Enabled” or “Disabled”.
Example:
CLI > sys ncq p=0 [Enter]
Set the controller works at enabled mode.
56
CLI CONFIGURATION
3.4.6.8 HDD Queue Depth
Use this command to change hdd queue depth, follow the proce-
dure below:
Syntax:
sys hddqdepth
Parameter:
<p=<0<1>:1<2>:2<4>:3<8>:4<16>:5<32>>>
Description:
This parameter is adjusted the queue depth capacity of NCQ
(SATA HDD) or Tagged Command Queuing (SAS) which trans-
mits multiple commands to a single target without waiting for
the initial command to complete.
Example:
CLI > sys hddqdepth p=0 [Enter]
Set the controller queue depth to 0.
3.4.6.9 Set The SAS Mux (ARC-1680 Only)
Use this command to set the SAS port wire the signal to exter-
nal or internal connector, follow the procedure below:
Syntax:
sys sasmux
Parameter:
<p=<0<auto>:1<internal>:2<external>>>
Description:
The function is only for ARC-1680 Intel SAS controller limitation
of auto configuration of CH5-8 for internal or external. If there
is no linkage at the beginning power on stage, some SAS HDDs
PHY will automatically enter the sleep mode. In this condition,
our firmware will set no linkage on those channels. Since some
HDDs have this behavior, our controller firmware will configure
the active channel CH5-8 on the external port. We added this
function for customer to set, if the controller automatically con-
57
CLI CONFIGURATION
figuration detect the wrong direction of CH5-8 internal channels.
Example:
CLI > sys sasmux p=0 [Enter]
Set the controller at auto mode.
3.4.6.10 Set The SES2 Support (SAS Controller Only)
Use this command to set the SES2 function on the controller,

Syntax:
sys ses2support
Parameter:
Description:
If your SAS backplane does not implement the correct SES2
function, you can disable the SES2 support on controller. Con-
troller will use SMP (only monitor PHY not environment) to com-
municate with SAS backplane, but you will be not able to moni-
tor the backplane information.
Example:
CLI > sys ses2support p=0 [Enter]
Enable the SES2 function on the controller firmware.
3.4.6.11 Set The Max Command Length
Use this command to set the max command length per transfer,
Syntax:
sys maxcmdlen
Parameter:
<p=<p=<0<148K>:1<256K>:2<512K>:3<1M>:1<2M>:2<
4M>>>
58
CLI CONFIGURATION
Description:
Max Command Length is used to set a “best” IO size for the
RAID controller.
Example:
CLI > sys maxcmdlen p=5 [Enter]
Set the controller max command length to 4MB per transfer.
3.4.6.12 Disk Cache
Use this command to show disk write cache mode, follow the
procedure below:
Syntax:
sys diskcache
Parameter:
<p=<p=<0<auto>:1<enable>:2<disabled>>>
Description:
User can set the “Disk Write Cache Mode” to “Auto”, “Enabled”,
or “Disabled”. “Enabled” increases speed, “Disabled” increases
reliability.
Example:
CLI > sys diskcache p=0 [Enter]
Set the controller works at auto mode.
3.4.6.13 HDD Read Ahead
Use this command to change hdd read ahead mode, follow the
procedure below:
Syntax:
sys hddreadahead
Parameter:
<p=<0<enabled>:1<disabled-MAXTOR>:2<disabled>>>
Description:
Allow Read Ahead (Default: Enabled)—When Enabled, the drive’s
59
CLI CONFIGURATION
read ahead cache algorithm is used, providing maximum perfor-
mance under most circumstances.
Example:
CLI > sys hddreadahead p=0 [Enter]
Set the controller works at enabled mode.
3.4.6.14 Capacity Truncation
Use this command to change disk capacity truncation mode, fol-

low the procedure below:
Syntax:
sys truncation
Parameter:
<p=<0<10G>:1<1G>:2<disabled>>>
Description:
Areca RAID controllers use drive truncation so that drives from
different vendors are more likely to be usable as spares for one
another. Drive truncation slightly decreases the usable capac-
ity of a drive that is used in redundant units. The controller
provides three truncation modes in the system configuration:
Multiples Of 10G, Multiples Of 1G and Disabled.
Example:
CLI > sys truncation p=0 [Enter]
Set the controller works at 10G.
3.4.6.15 Auto Activate Raid Set
Use this command to change auto activate incomplete RAID set,

Syntax:
sys autoact
Parameter:
60
CLI CONFIGURATION
Description:
When some of the disk drives are removed in power off state
or boot up stage, the RAID set state will change to “Incomplete
State”. But if a user wants to automatically continue to work
while the RAID controller is powered on, then user can set the
“Auto Activate Raid Set” option to “Enabled”. The RAID state will
change to “Degraded Mode” while it powers on.
Example:
CLI > sys autoact p=0 [Enter]
3.4.6.16 Controller Fan Detection
Use this command to set the detection function for fan on the
ROC, follow the procedure below:
Syntax:
sys cpufan
Parameter:
Description:
The “CPU Fan Detection” function is available in the firmware for
detecting the cooling fan function on the ROC if you want to use
the active cooling fan on the controller board.
Example:
CLI > sys cpufan p=0 [Enter]
Enable the ROC fan checking function.
3.4.6.17 Empty HDD slot HDD
Use this command to change empty hdd slot led, follow the pro-
cedure below:
Syntax:
sys hddled
61
CLI CONFIGURATION
Parameter:
<p=<0<on>:1<off>>>
Description:
The firmware has added the “Empty HDD Slot LED” option to
setup the fault LED light “ON “or “OFF” when there is no HDD
installedon this slot. When each slot has a power LED for the
HDD installed identify, user can set this option to “OFF". Choose
option "ON", the RAID controller will light the fault LED; if no
HDD installed.
Example:
CLI > sys hddled p=0 [Enter]
Set the controller hdd led to on mode.
3.4.6.18 Volume Data Read Ahead
Use this command to change volume data read ahead, follow

Syntax:
sys vloreadahead
Parameter:
<p=<0<normal>:1<aggressive>:2<conservative:3<disabl
ed>>>
Description:
The volume read data ahead parameter specifies the controller
firmware algorithms which process the Read Ahead data blocks
from the disk. The Read Ahead parameter is normal by default.
To modify the value, you must set it from the command line us-
ing the Read Ahead option. The default normal option satisfies
the performance requirements for a typical volume. The disabled
value implies no read ahead. The most efficient value for the
controllers depends on your application. Aggressive read ahead
is optimal for sequential access but it degrades random access.
Example:
CLI > sys hddreadahead p=0 [Enter]
Set the controller works at normal mode.
62
CLI CONFIGURATION
3.4.6.19 Write Same Configuration
Use this command to program the write same for initialization,

Syntax:
sys writesame
Parameter:
<p=<0<SAS And SATA>:1<SAS Only>:2<SATA
Only>:3<Disabled>>>
Description:
Drives that support the Write Same feature (SCT) can write to
multiple drive sectors at once, improving initialization time. To
take advantage of this feature, all the drives in the unit must
support Write Same. User can set the “SAS And SATA”, “SAS
Only”, “SATA Only or “Disabled” for the controller initialization.
Example:
CLI > sys writesame p=0 [Enter]
Set the controller works write same initialization mode for SAS
and SATA HDD.
3.4.6.20 Hot Plug Disk
Use this command to define the hot plugged disk for rebuilding”,
Syntax:
sys hpdforrebuilding
Parameter:
<p=<0<Blank Disk Only>:1<Always>:2<Disabled>>>
Description:
It defines if the RAID array volume should start rebuilding or not
when detects a disk is inserted/re-inserted during online.
The options are: “Blank Disk Only”, “Always”, and “Disable”. The
default is “Blank Disk Only”.
63
CLI CONFIGURATION
“Blank Disk Only”-it will trigger the rebuilding if and only if the
inserted disk has not been in the RAID array before, which has
no RAID signature on it. So when a previously removed disk is
self re-inserted, it won’t trigger the degraded RAID array to re-
build, and so that the administrator has a chance to identify this
misbehaving disk and replaces it.
“Always” – it is what it was before. Whenever a disk is inserted/

re-inserted whether new or previously existed, it always trigger
a rebuilding for the Degraded RAID set/Volume.
“Disable” – it will not trigger rebuilding regardless what sort of

disk plugging in. When “Disable” and/or “Blank Disk Only” is se-
lected, the re-inserted/previously removed disk will be identified
as a disk in a separate RAID set with duplicated RAIDset# and
with all the rest of RAID members missing.
Example:
CLI > sys hpdforrebuilding p=0 [Enter]
Set the controller “Hot Plugged Disk For Rebuilding” as “Blank
Disk Only”.
3.4.6.21 Smart Option
Use this command to define the SMART option, follow the proce-
dure below:
Syntax:
sys smartop
Parameter:
<p=<0<Failed The Disk>:1<Failed The Drive If Hot Spare
Exist>:2<Alert>>>
Description:
This option is used to increases the reliability of SSDs/HDDs by
automatically copying data from a drive with potential to fail to
a designated hot spare or newly inserted drive. The options are:
“Failed The Drive”, “Failed The Drive If Hot Spare Exist”, and
“Alert Only”. The default is “Alert Only”
64
CLI CONFIGURATION
“Failed The Drive”- controllers kill off the SMART fail drive imme-
diately.
“Failed The Drive If Hot Spare Exist” – controllers kill off the
SMART fail disk if hot spare dive is existed.
“Alert” – it will trigger alert when there happens a SMART fail
drive.
Example:
CLI > sys smartop p=1 [Enter]
Configure the SMART option for the HDD as “Failed The Drive If
Hot Spare Exist”.
3.4.6.22 Smart HDD Interval
Use this command to define the smart HDD interval, follow the
procedure below:
Syntax:
sys smartpi
Parameter:
<p=<0<on demand>:1<30 seconds>:2<1 min>:3<5
mins>:4<10 mins>:5<20 mins>:6<30 mins>:7<1 hour>:8<2
hours>:9<3 hourss>:10<6 hours>11<12 hours>>>
Description:
Besides the scheduled volume check, user can define the “Smart
Pulling Interval” to pull the SMART status of each disk. The de-
fault is “on demand”.
User can schedule every certain period of time interval to pull
the SMART status of each disk. When SMART pulling is executed,
disk activity will be temporally halted until the SMART parameter
reading is finished. That is why you don’t want to set the Inter-
val too frequent. What to use is up to the users to decide based
on their applications and experiment results
Example:
CLI > sys smartpi p=4 [Enter]
Configure the SMART Polling Interval option for the HDD as “10
minutes”.
65
CLI CONFIGURATION
3.4.6.23 Update Firmware
To update controller firmware, follow the procedure below:
Syntax:
sys updatefw
Parameter:
<path=<PATH_OF_FIRMWARE_FILE>>
Description:
Since the RAID controller features flash firmware, it is not nec-
essary to change the hardware flash chip in order to upgrade
the RAID controller firmware. The user can simply re-program
the old firmware through this command. New releases of the
firmware are available in the form of a DOS file at shipping CD,
website or FTP.
Example:
CLI > sys updatefw path=c:\fw\ARC1110firm [Enter]
Update firmware and file path is [C:\FW\ARC1110FORM.BIN] to
the currently selected RAID controller.
3.4.6.24 Show System Configuration
Use this command to display system configuration, follow the

procedure below:
Example:
CLI > sys showcfg p=0 [Enter]
3.4.6.25 Save Bin
Use this command to save RAID controller system configuration

into a binary file, follow the procedure below:
Syntax:
sys savebin
Parameter:
<path=<PATH_OF_FILE>>
66
CLI CONFIGURATION
Description:
Save RAID controller system function configurations into a bi-
nary file.
Example:
CLI > sys savebin path=c:\ctrlrl.bin [Enter]
The currently selected RAID controller RAID system function
configurations save to a file path on the [C:\ctlr1.bin].
3.4.6.26 Restore Bin
Use this command to restore RAID system function configura-

tions file into the selected RAID controller, follow the procedure
below:
Syntax:
sys restorebin
Parameter:
<path=<PATH_OF_FILE>>
Description:
Restore the RAID controller system function configurations file
on the <path=<PATH_OF_FILE>> into the selected RAID con-
troller.
Example:
CLI > sys savebin path=c:\ctrlrl.bin [Enter]
Restore RAID controller system function configurations file on
the path [C:\ctlr1.bin] into the selected RAID controller.
3.4.6.27 System Information
Choose this option to display main processor, CPU instruction

cache and data cache size, firmware version, serial number, con-
troller model name, and the cache memory size.
To view the system information, follow the procedure below:
Syntax:
sys info
67
CLI CONFIGURATION
Description:
This command provides currently selected RAID controller sys-
tem information.
Example:
CLI > sys info [Enter]
All the major controller system information will be displayed.
3.4.7 Advanced System
The advanced features on the Areca RAID controller are for power
user to tune the firmware behavior to fit different video applica-
tion.
68
CLI CONFIGURATION
3.4.7.1 HDD SMART Status Polling (SATA only)
Use this command to change HDD smart status polling, follow

Syntax:
sys smartpoll
Parameter:
Description:
An external RAID enclosure has the hardware monitor in the
dedicated backplane that can report HDD temperature status
to the controller. However, PCI cards do not use backplanes if
the drives are internal to the main server chassis. The type of
enclosure cannot report the HDD temperature to the controller.
For this reason, “HDD SMART Status Polling” was added to en-
able scanning of the HDD temperature function. It is necessary
to enable “HDD SMART Status Polling” function before SMART
information is accessible. This function is disabled by default.
Example:
CLI > sys smartpoll p=0 [Enter]
69
CLI CONFIGURATION
3.4.7.2 Time-Limited Error Recovery
Use this command to change HDD time-limited error recovery

value, follow the procedure below:
Syntax:
adsys tler
Parameter:
<p=<0<Default>:1<Disable>:2<5 Seconds>:3<6
Seconds>:4<Seconds>>>
Description:
TLER (time-limited error recovery) functions provide support for
WD Caviar RE (RAID) series disks. This is a new option from
WD to support RAID features that were traditionally missing
from standard desktop drives. TLER is a method of signaling the
system RAID controller in the event that an error recovery pro-
cess is taking longer than time-out specifications allow. This pre-
vents the RAID controller from dropping the drive from the array
during this period. Default value is manufacture setting. You can
select between 5, 6 and 7 second. This feature is to setup the
HDD internal timeout value.
Example:
CLI > adsys tler p=0 [Enter]
Use the manufacture default setting value.
3.4.7.3 Time Out
Use this command to program time out value, follow the proce-
dure below:
Syntax:
adsys timeout
Parameter:
<p=<0<8 Seconds>:1<7 Seconds>:2<6 Seconds>:3<5 Sec-
onds>:4<4 Seconds>:5<3 Seconds>:6<12 Seconds>:7<17
Seconds>:8<22 Seconds>:9<27 Seconds>:10<32 Sec-
onds>>>
70
CLI CONFIGURATION
Description:
Disk time-out is a registry setting that defines the time that
RAID controller will wait for a hard disk to respond to a com-
mand. You can modify the retry value by entering a new value
in the edit box beside this button and then selecting the but-
ton. Normally you should not need to modify this value. Default
value is 8 seconds: You can select between 3~8 second.
Example:
CLI > adsys timeout p=0 [Enter]
Set the controller time out value = 8 seconds.
3.4.7.4 Retry Count
Use this command to set the controller number of retries, follow

Syntax:
adsys retrycnt
Parameter:
<p=<0<2 Times>:1<3 Times>>>
Description:
This setting determines the number of access that will be at-
tempted before the current command from the RAID controller
to the disk drive is aborted. You can modify the retry value by
entering a new value in the edit box beside this button and then
selecting the button. Normally you should not need to modify
this value. There are two selections, either 2 retry or 3 retry.
Example:
CLI > adsys retrycnt p=0 [Enter]
Set the controller number of retries value = 2 times.
3.4.7.5 Buffer Threshold
Use this command to set the Buffer Threshold, follow the proce-
dure below:
71
CLI CONFIGURATION
Syntax:
sys bufthre
Parameter:
<p=<0<75%>:1<50%>:2<25%>:3<5%>>>
Description:
This new feature there are 3 options; 25%, 50% and 75%. The
percentage represents how much data should be kept in resi-
dent cache memory (how full cache should get) before controller
starts to flush data onto the hard drives. If the buffer is set for
25%, then all 25% will be cached and is used for writing data.
The remaining cache memory will be used for reading and other
system overhead. Write buffer threshold for 5% is added for
video recording. This option will push data to disk early.
This feature gives controller extra buffer time in case of slow re-
sponse from the hard drives within a given time. Consequently,
this can prevent a pause in data flow and there will be continues
data access and stream. This feature is very useful for the video
streaming applications where there is high demand for constant
non-stop data flow with no interruption due to lower perfor-
mance of specific hardware.
Example:
CLI > adsys bufthre p=0 [Enter]
Set the controller buffer threshold value = 75%.
3.4.7.6 Read Ahead Cache
Use this command to set the amount of read ahead, follow the
procedure below:
Syntax:
adsys readahead
Parameter:
<p=<0<Auto>:1<512K>:2<1MB>:3<2 MB>:4<4MB>:5<6MB
>:6<8MB>:7<10MB>:8<12MB>:9<14MB>:10<16MB>>>
72
CLI CONFIGURATION
Description:
Read-Ahead data is buffered in the RAID controller cache,
however, thereby cutting down on the amount of I/O traffic to
the disk. The Amount of Read Ahead defines how many data of
reading at a time, making more efficient use of the RAID sub-
system. This makes it possible to locate and re-issue the data
without repetitive hard parsing activities.
The amount of read ahead parameter is used to allocate an

amount of memory in the cache memory the frequently ex-
ecuted queries and return the result set back to the host with-
out real disk read execution. Default value is “Auto”. Controller
will base on the HDD number to set the amount of read ahead
value. You can select between 512KB ~ 16MB.
Example:
CLI > adsys readahead p=0 [Enter]
Set the amount of read ahead value on auto mode.
3.4.7.7 Audio/Video Stream Configuration
Use this command to set the Number of AV stream, follow the

procedure below:
Syntax:
adsys avstreams
Parameter:
<p=<0<6>:1<11>:2<16>:3<21>:4<26>:5<31>:6<36>:7<5
6>:8<76>:9<96>:10<116>:11<136>:12<156>:13<176>:14
<196>:15<216>:16<236>:17<256>>>
Description:
RAID controllers are required to have not only the function of
processing ordinary data but also the function of dealing with AV
(audio/video) stream data needing real-time processing. Since
the bus cycle used in RAID controller was designed to transfer
the computer data exactly, it was unsuitable for the transfer
of AV stream needing great band widths. They are required to
do some setting for the handshaking during the processing of
stream data. This setting is an object of transferring stream data
73
CLI CONFIGURATION
efficiently on an existing RAID controller. Normally you should
not need to modify this value. Default value is 6. You can select
between 6~256.
To decide how to set AV stream playout parameter, you need to

check the Number of stream, amount of read ahead, and total
cache memory during runtime. You can try to adjust the three
numbers to get the best performance as your requirement.
Number of stream shows the number of stream added to the
system, amount of read ahead shows the amount of read ahead
data taken from the cache without real disk execution, and total
cache memory shows the total available memory being installed
in the RAID controller.
Example:
CLI > adsys avstreams p=0 [Enter]
Set the Number of AV Stream value = 6.
3.4.7.8 Optimize Audio/Video Recording
Use this command to set the optimize AV recording, follow the

procedure below:
Syntax:
adsys optavrec
Parameter:
<p=<0<Disabled>:1<Mode1>:2<Mode2>:3<Mode3>>>
Description:
AV recording option is for video recording (no time limit), but if
used in normal operation, performance may be degraded. This
new feature there are 4 options; “Disabled”, “Mode1”, “Mode2”
and “Mode 3”. Default value is “Disabled”. Our controller cache
uses LRU method, there have no special memory capacity
reserved for read or write. The mode 1, 2 and 3 are used for
define the command sorting method. The default sorting method
is helpful for normal applications, but not useful for AV applica-
tions, so we have defined three different sorting methods for
these special applications. To decide how to optimize AV stream
recording parameter, you need to adjust the optimize AV record-
74
CLI CONFIGURATION
ing, and write buffer threshold during runtime.
Example:
CLI > adsys optavrec p=0 [Enter]
Set the Optimize AV Recording value as “disabled”.
3.4.7.9 Optimize HD Edition Configuration
Use this command to set the optimize HD edition, follow the

procedure below:
Syntax:
adsys opthdedit
Parameter:
<p=<0<Disabled>:1<MAC Mode1>:2<MAC Mode2>:3<MAC
Mode3>:4<Windows>>>
Description:
HD edit option is not for long time continuous AV recording (may
lose data if power loss). It is recommended for hours of opera-
tion and has some interval idling for house keeping action. This
new feature there are 4 options; “Disabled”, “MAC Mode1”, “MAC
Mode2”, “Mac Mode” 3 and “Windows”. Default value is “Dis-
abled”. To decide how to optimize HD stream editor parameter,
you need to adjust the optimize AV Recording, optimize HD edi-
tion, and write buffer threshold during runtime.
Example:
CLI > adsys opthdedit p=0 [Enter]
Set the Optimize HD Edition value as “disabled”.
3.4.7.10 Read Performance Margin
Use this command to set the read performance margin, follow

Syntax:
adsys readmargin
75
CLI CONFIGURATION
Parameter:
<p=<0~30>>
Description:
The “Read Performance Margin” is for controller to reserve
n% read margin during AV stream recording. It is designed to
eliminate the frame drop and ensure to provide the smooth and
stable performance on the application.
Example:
CLI > adsys readmargin p=10 [Enter]
Set the controller to keep the Read Performance Margin = 10%.
3.4.7.11 Write Performance Margin
Use this command to set the write performance margin, follow

Syntax:
adsys writemargin
Parameter:
<p=<0~30>>
Description:
The “Write Performance Margin” is for controller to reserve
n% read margin during AV stream recording. It is designed to
eliminate the frame drop and ensure to provide the smooth and
stable performance on the application.
Example:
CLI > adsys writemargin p=10 [Enter]
Set the controller to keep the Write Performance Margin = 10%.
3.4.7.12 Read And Discard Parity Data
Use this command to decide the read and discard parity data,
Syntax:
adsys readdiscard
76
CLI CONFIGURATION
Parameter:
Parameter<p=<0<enabled>:1<disabled>>>
Description:
This function is used to determine if parity data is to be read
and discarded.
Example:
CLI > adsys readdiscard p=0 [Enter]
Set the controller to enable the read and discard parity data.
3.4.7.13 Fail Disk For Any Timeout
Use this command to fail disk for any timeout, follow the proce-
dure below:
Syntax:
adsys faildiskiftimeout
Parameter:
Parameter<p=<0<enabled>:1<disabled>>>
Description:
Imaging system products expect to have constant speed for
writing raw data to the storage by constant speed without any
data loss whenever a drive becomes failure in RAID system. This
function is the option that RAID controller will kill off the HDD
for any time out. It can reduce the write cache size to buffer the
raw data.
Example:
CLI > adsys faildiskiftimeout p=0 [Enter]
Set the failed disk for any timeout.
3.4.7.14 SATA Speed
Use this command to change the SATA HDD speed, follow the
procedure below:
Syntax:
adsys specifichddspeed
77
CLI CONFIGURATION
Parameter:
<vendor=0<WDC>:1<Hitachi>:2<Seagate>>
<speed=0<Default>:1<1.5G>:2<3.0G>:3<6.0G>>>
Description:
This command provides currently selected RAID controller to
program the SATA speed for better compatibly with ROC or SAS
expander.
Example:
CLI > adsys specifichddspeed vendor=0 speed=3 [Enter]
Set the attached WDC SATA to work at the 6Gb/s speed.
3.4.7.15 System Information
Choose this option to display main processor, CPU instruction

cache and data cache size, firmware version, serial number, con-
troller model name, and the cache memory size.
To view the system information, follow the procedure below:
Syntax:
adsys info
Description:
This command provides currently selected RAID controller sys-
tem information.
Example:
CLI > adsys info [Enter]
All the major controller system information will be displayed.
78
CLI CONFIGURATION
3.4.8 HDD Power Management
Areca has automated the ability to manage HDD power based

on usage patterns. The “HDD Power Management” allows you to
choose a “Stagger Power On Control”, “Low Power Idle”, “Low
RPM” and completely “Spins Down Idle HDD”. It is designed to
reduce power consumption and heat generation on idle drives.
3.4.8.1 Stagger Power On Control
Use this command to change stagger power on control, follow

Syntax:
hddpwr spoweron
Parameter:
<p=<0<0.4>:1<0.7>:2<1.0>:3<1.5>:4<2.0>:5<2.5>:6<3.0
>:7<3.5>:8<4.0>:9<4.5>:10<5.0>:11<5.5>:12<6.0>>>
Description:
Areca RAID controller has included the option for customer to
select the disk drives sequentially stagger power up value. The
values can be selected from 0.4s to 6s per step which powers up
one drive.
Example:
CLI > hddpwr spoweron p=1 [Enter]
Set the controller works at 0.7 mode.
79
CLI CONFIGURATION
3.4.8.2 Time To Hdd Low Power Idle
Use this command to set time to hdd low power idle, follow
Syntax:
hddpwr tlowpwridle
Parameter:
<p=<0<Disabled>:1<2>:2<3>:3<4>:4<5>:5<6>:6<7>>>
Description:
This option delivers lower power consumption by automatically
unloading recording heads during the setting idle time. The val-
ues can be selected “Disabled” or within the range 2 to 7 min-
utes.
Example:
CLI > hddpwr tlowpwridle p=0 [Enter]
Set the Time to Hdd Low Power Idle value = 2 minutes.
3.4.8.3 Time To Hdd Low RPM Mode
Use this command to change time to hdd low RPM mode, follow
Syntax:
hddpwr tlowpmmode
Parameter:
<p=<0<Disabl
ed>:1<10>:2<20>:3<30>:4<40>:5<50>:6<60>>>
Description:
This function can automatically spin disks at lower RPM if there
have not been used during the setting idle time. The values can
be selected “Disabled” or within the range 10 to 60 minutes.
Example:
CLI > hddpwr tlowpmmode p=0 [Enter]
Disable the controller time to hdd low RPM mode.
80
CLI CONFIGURATION
3.4.8.4 Spin Down Idle HDD
Use this command to change spin down idle hdd, follow the pro-
cedure below:
Syntax:
hddpwr spindown
Parameter:
<p=<0<disabled>:1<min>:2<3min>:3<5min>:4<10min>:5<
15min>:6<20min>:7<30min>:8<40min>:9<60min>>>
Description:
This function can automatically spin down the drive if it hasn’t
been accessed for a certain amount of time. This value is used
by the drive to determine how long to wait (with no disk activ-
ity, before turning off the spindle motor to save power.)
Example:
CLI > hddpwr spindown p=3 [Enter]
Set the controller works at 3 mins.
3.4.8.5 View HDD Power Management
Use this command to view HDD power management informa-

tion, follow the procedure below:
Syntax:
hddpwr info
Description:
This command provides currently selected RAID controller HDD
Power Management information.
Example:
CLI > hddpwr info [Enter]
The selected controller HDD power management will be dis-
played.
81
CLI CONFIGURATION
3.4.9 Ethernet Configuration
Use this feature to set the controller Ethernet port configuration.

A customer doesn’t need to create a reserved space on the arrays
before the Ethernet port and HTTP service are working. The firm-
ware-embedded web browser-based RAID manager can access it
from any standard internet browser or from any host computer
either directly connected or via a LAN or WAN with no software or
patches required.
3.4.9.1 DHCP Function
Use this command to set the DHCP function, follow the proce-
dure below:
Syntax:
net dhcp
Parameter:
82
CLI CONFIGURATION
Description:
DHCP (Dynamic Host Configuration Protocol) allows network ad-
ministrators centrally manage and automate the assignment of
IP (Internet Protocol) addresses on a computer network. When
using the TCP/IP protocol (Internet protocol), it is necessary for
a computer to have a unique IP address in order to communi-
cate to other computer systems. Without DHCP, the IP address
must be entered manually at each computer system. DHCP lets
a network administrator supervise and distribute IP addresses
from a central point. The purpose of DHCP is to provide the
automatic (dynamic) allocation of IP client configurations for a
specific time period (called a lease period) and to minimize the
work necessary to administer a large IP network. Select the
“Disabled” or “Enabled” option to enable or disable the DHCP
function. If DHCP is disabled, it will be necessary to manually
enter a static IP address that does not conflict with other de-
vices on the network.
Example:
CLI > net dhcp p=1 [Enter]
Set the controller DHCP function as disabled.
3.4.9.2 Local IP address
Use this command to set the local IP address, follow the proce-
dure below:
Syntax:
net ipaddr
Parameter:
<p=xxx>
Description:
If you intend to set up your client computers manually (no
DHCP), make sure that the assigned IP address is in the same
range as the default router address and that it is unique to your
private network. However, it is highly recommend to use DHCP
if that option is available on your network. An IP address alloca-
tion scheme will reduce the time it takes to set-up client com-
puters and eliminate the possibilities of administrative errors
and duplicate addresses.
83
CLI CONFIGURATION
Example:
CLI > net ipaddr p=192.168.0.100 [Enter]
Set the controller ethernet local IP address =192.168.0.100.
3.4.9.3 HTTP Port Number
Use this command to set the HTTP port number, follow the pro-
cedure below:
Syntax:
net httpport
Parameter:
<p=xxx>
Description:
You can reassign the default “HTTP Port Number” of the control-
ler.
Example:
CLI > net httpport p=2000 [Enter]
Set the controller ethernet HTTP port number =2000.
3.4.9.4 Telnet Port Number
Use this command to set the Telnet port number, follow the pro-
cedure below:
Syntax:
net telnetport
Parameter:
<p=xxx>
Description:
You can then reassign the default “Telent Port Number” of the
controller.
Example:
CLI > net telnetport p=3000 [Enter]
Set the controller ethernet Telnet port number =3000.
84
CLI CONFIGURATION
3.4.9.5 SMTP Port Number
Use this command to set the SMTP port number, follow the pro-
cedure below:
Syntax:
net smtpport
Parameter:
<p=xxx>
Description:
You can then reassign the default “SMTP Port Number” of the
controller.
Example:
CLI > net smtpport p=3000 [Enter]
Set the controller SMTP port number =3000.
3.4.9.6 Gateway IP Setting
Use this command to set the gateway IP setting, follow the pro-
cedure below:
Syntax:
net gateway
Parameter:
<p=xxx>
Description:
You can then reassign the default “Gateway IP setting” of the
controller.
Example:
CLI > net gateway p=1912.168.0.1 [Enter]
Set the controller gateway IP address =1912.168.0.1.
3.4.9.7 Netmask Setting
Use this command to set the Netmask setting, follow the proce-
85
CLI CONFIGURATION
dure below:
Syntax:
net netmask
Parameter:
<p=xxx>
Description:
You can then set the default “Netmask” address of the controller.
Example:
CLI > net netmask p=255.255.255.0 [Enter]
Set the controller Netmask address =255.255.255.0.
3.4.9.8 View Network information
Use this command to view configuration, follow the procedure

below:
Syntax:
net info
Description:
This command provides currently selected RAID controller ether-
net configuration.
Example:
CLI > net info [Enter]
The selected controller Ethernet configuration will be displayed.
86
CLI CONFIGURATION
3.4.10 View System Events
A management program is almost useless without reporting or

notification function ability. For this reason, the GUI RAID Man-
ager enables you to configure notifications to occur in response to
various disk array events. For example, if you configure an e-mail
notification, the GUI RAID Manager will send an e-mail to selected
computers on the network if the event (that just occurred) falls
within the selected notification level. If the notification is detailed
enough, the recipient can respond accordingly.
The event command provides a log of events that have occurred

on the RAID controller. An event occurs when the RAID controller
requires attention, such as when a RAID set becomes degraded
and is no longer fault tolerant.
The event -h command can view the sub-command and param-

eters of the event function.
Syntax:
event info
Description:
Choose this option to view the system events information.
Example:
CLI > event info [Enter]
All the event of the currently selected controller information will
be displayed.
87
CLI CONFIGURATION
Syntax:
event clear
Description:
This command clears the entire events buffer information.
Example:
CLI > event clear [Enter]
All the event of the currently selected controller information will
be cleared.
3.4.11 Hardware Monitor
To display the cooler fan, and the associated disk temperature

status, use the hardware monitor command.
The hw -h command can view the sub-command and parameters

of the [ hw ] function.
To view the hardware monitor information, follow the procedure

below:
Syntax:
hw info
Description:
Choose this option to view the hardware monitor information.
Example:
CLI > hw info [Enter]
All the hardware monitor of the currently selected controller infor-
mation will be displayed.
88
CLI CONFIGURATION
3.4.12 Mail (Alert by Mail) Configuration

The mail -h command can view the sub-command and parameters
of the [ mail ] function.
89
CLI CONFIGURATION
To view the mail information, follow the procedure below:
Parameter:<p=xxx>>
Description:
To enable the controller to send the email function, you need to
configure the SMTP function on the ArcHttp software. To enable
the RAID controller email sending function, click on the “Mail Con-
figuration” link. The "SMTP Server Configurations" menu will show
as following: When you open the mail configuration page, you will
see following settings:
• SMTP Server Configuration:

SMTP Server IP Address: Enter the SMTP server IP address which
is not MCRAID manager IP.Ex: 192.168.0.2
• Mail Address Configurations:

Sender Name: Enter the sender name that will be shown in the
outgoing mail.Ex: RaidController_1Mail address: Enter the sender
email that will be shown in the outgoing mail, but don’t type IP to
replace domain name. Ex: [email protected]
Account: Enter the valid account if your SMTP mail server need
authentication.
Password: Enter the valid password if your SMTP mail server need
authentication.
MailTo Name: Enter the alert receiver name that will be shown in
the outgoing mail.
Mail Address: Enter the alert receiver mail address
Ex: [email protected]
• Event Notification Configurations:

According to your requirement, set the corresponding event level
:
Disable Event Notification: No event notification will be sent.
Urgent Error Notification: Send only urgent event
Serious Error Notification: Send urgent and serious event
Warning Error Notification: Send urgent, serious and warning
Event
Information Notification: Send all event
Notification For No Event: Notify user if no event occurs within 24
hours.
90
CLI CONFIGURATION
The "Mail (Alert by Mail) Configuration" sub-commands are used
to fill the item similar as the "Web Browser Configuration" window
below:
3.4.13 SNMP Configuration

The snmp -h command can view the sub-command and parameters
of the [snmp] function.
• SNMP Trap Configurations

Enter the SNMP trap IP address.
Syntax:
snmp ipaddr1
Parameter:
<p=xxx>
Description:
Enter the SNMP trap IP address.
Example:
CLI > snmp ipaddr1 p=192.168.0.1 [Enter]
Set the SNMP trap ip#1 address to 198.168.0.1.
91
CLI CONFIGURATION
• SNMP System Configurations

The system Contact, Name and Location that will be shown in
the outgoing SNMP trap. Community name acts as a password to
screen accesses to the SNMP agent of a particular network de-
vice. Type in the community names of the SNMP agent. Before ac-
cess is granted to a request station, this station must incorporate
a valid community name into its request; otherwise, the SNMP
agent will deny access to the system. Most network devices use
“public” as default of their community names. This value is case-
sensitive.
92
CLI CONFIGURATION
• SNMP Trap Notification Configurations
Event Notification Configurations. The controller classifies disk
array events into four levels depending on their severity. These
include level 1: Urgent, level 2: Serious, level 3: Warning and
level 4: Information. The level 4 covers notification events such
as initialization of the controller and initiation of the rebuilding
process; Level 2 covers notification events which once have hap-
pen; Level 3 includes events which require the issuance of warn-
ing messages; Level 1 is the highest level, and covers events the
need immediate attention (and action) from the administrator.
The “SNMP Configuration” sub-commands are used to fill the item
similar as the “Web Browser Configuration” window below:
3.4.14 NTP Configuration
The Network Time Protocol (NTP) is used to synchronize the

time of a computer client or server to another server or refer-
ence time source, such as a radio or satellite receiver or mo-
dem. It provides accuracies typically within a millisecond on
LANs and up to a few tens of milliseconds on WANs relative to
Coordinated Universal Time (UTC) via a Global Positioning Ser-
vice (GPS) receiver.
93
CLI CONFIGURATION
94
CLI CONFIGURATION
3.4.14.1 NTP server IP#1
Use this command to set NTP server IP#1, follow the procedure
below:
Syntax:
ntp ipaddr#1
Parameter:
<p=xxx>
Description:
The most important factor in providing accurate, reliable time is
the selection of NTP servers to be used in the configuration file.
Typical NTP configurations utilize multiple redundant servers and
diverse network paths in order to achieve high accuracy and re-
liability. Our NTP configuration supports two existing public NTP
synchronization subnets.
Example:
CLI > ntp ipaddr#1 p=140.112.4.189 [Enter]
Set the reference source server#1 IP address=140.112.4.189.
3.4.14.2 NTP server IP#2
Use this command to set NTP server IP#2, follow the procedure
below:
Syntax:
ntp ipaddr#2
Parameter:
<p=xxx>
Description:
The most important factor in providing accurate, reliable time is
the selection of NTP servers to be used in the configuration file.
Typical NTP configurations utilize multiple redundant servers and
diverse network paths in order to achieve high accuracy and re-
liability. Our NTP configuration supports two existing public NTP
synchronization subnets.
95
CLI CONFIGURATION
Example:
CLI > ntp ipaddr#2 p=140.112.2.189 [Enter]
Set the reference source server#1 IP address=140.112.2.189.
3.4.14.3 Time Zone
Use this command to change the timezone of the RAID control-

ler, follow the procedure below:
Syntax:
ntp timezone
Parameter:
<p=xxx>
Description:
Time zone conveniently runs in the system tray and allows you
to easily view the date and time in various locations around the
world. You can also quickly and easily add your own personal
locations to customize time zone the way you want.
Example:
CLI > ntp timezone p=60 [Enter]
Set the controller time zone at [<GMT+08:00>Taipei].
3.4.14.4 Automatic Daylight Saving
Use this command to change automatic daylight saving function,

Syntax:
ntp daylightsaving
Parameter:
Description:
Automatic daylight saving will normally attempt to automati-
cally adjust the system clock for daylight saving changes based
on the computer time zone. This tweak allows you to disable the
automatic adjustment.
96
CLI CONFIGURATION
Example:
CLI > ntp daylightsaving p=0 [Enter]
Set the controller works at automatic daylight saving mode.
3.4.14.5 View NTP Information
Syntax:
ntp info
Description:
This command display the currently selected RAID controller ntp
setting information.
Example:
CLI > ntp info [Enter]
The selected controller ntp information will be displayed.
97

Cli Manual

Uploaded by

Copyright:

Available Formats

Cli Manual

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Cli Manual

Uploaded by

Copyright:

Available Formats

SATA & SAS RAID Controller

Command Line Interface

Copyright and Trademarks

The information of the products in this manual is subject to change

There are often multiple ways to accomplish the same storage

• McBIOS RAID manager

The CLI contains the same functionality offered by Areca McRAID

• Create RAID set

1.2 Supported Operating Systems

2.1 CLI Installation

2.1.1 For Windows

Below screen in this section are taken from a Windows/XP instal-

1. Insert the RAID controller CD in the CD-ROM drive. You aslo

3. Click on the “Setup” file then the Welcome screen appears.

Click the “Finish” button to complete the installation.

2.1.2 For Linux, FreeBSD, Mac and Solaris

The following is the CLI installation procedure in the Linux, Free-

1. Insert the SATA or SAS RAID controller CD in the CD-ROM

2.2.1 For Windows

To access the CLI:

The CLI prompt is displayed in a DOS console window.

2.2.2 For Linux, FreeBSD, Mac and Solaris

To access the CLI from the Linux/FreeBSD/Mac/Solaris prompt,

3.1 Configuring Raid Sets and Volume Sets

All commands use the following syntax:

<CMD> [sub-command] [parameters]

The CLI syntax uses the following conventions for parameter:

<text> indicates items that you must specify.

• Interactive Mode: Entering CLI commands at the main prompt

3.3.1 Interactive Mode

You can run CLI in interactive mode, entering commands at the

To run the CLI in the interactive mode

Example: CLI >set curctrl=1 password=0000 [Enter]

Use this command to select the controller 1 on which to perform

To run the CLI in a single command

Single commands can be useful when you want to perform a task

CLI ctrl=xx <command line with syntax and parameters>

Example: cli ctrl=1 disk info drv=1

To run the CLI using automated script

To run the automated script, enter: diskinfo

3.4 Command Categories

The following table is the CLI command summary:

Main command in this category allows you to display main com-

To prepare a SATA or SAS RAID controller to receive a CLI com-

The disk commands perform all pass-through operations on the

The “HDD Power Management” is designed to reduce power

The net commands allows you to display Ethernet setting. For

The event command allows you to display system event notifica-

The hw command allows you to display hardware information that

The mail command allows you to display e-mail information.

The SNMP command allows you to display SNMP information.

This command provides an on-line table of contents, providing

3.4.1 Main Commands

The main command shows the currently selected controller and

This command provides a table of contents, providing brief de-

Typical output looks like:

3.4.2 Set Commands

If there is more than one RAID controller in the system (up to

To prepare a controller to receive a CLI command, first you need

To define the selected controller, follow the procedure below: