| RAID powered on |
For starting the controller (turning on the host or plugging in the Thunderbolt system) |
| HTTP Login |
Refers to the login time (including IP or localhost, if applicable) to the RAID controller's management interface via a web browser using an integrated web server (ArcHTTP). The user logs in via an HTTP-based GUI to configure the controller, monitor its status, and perform management tasks. |
| VT100 Log In |
Refers to logging into a system or device via a VT100-compatible terminal emulation. This means access via CLI or terminal with timestamp, as well as as a device: RS232 Terminal VT100 Log In |
| Test Event |
An intentionally generated test message to validate surveillance and monitoring |
| Create RaidSet |
A RAID set has been created. The WebGUI displays the corresponding name in the Device column, e.g., Raid Set # 000 |
| Delete RaidSet |
A RAID set has been deleted. The WebGUI displays the corresponding name in the Device column, e.g., Raid Set # 000 |
| Expand RaidSet |
The user has expanded a RAID set. The WebGUI displays the corresponding name in the Device column, e.g., Raid Set # 000 |
| Create Volume |
The user has created a volume. The WebGUI displays the corresponding name in the Device column, e.g., ARC-1886-VOL#000 |
| Delete Volume |
The user has deleted a volume. The WebGUI displays the corresponding name in the Device column, e.g., ARC-1886-VOL#000 |
| Modify Volume |
The user has changed/modified a volume. The WebGUI displays the corresponding name in the Device column, e.g., ARC-1886-VOL#000 |
| Created Passthrough |
A passthrough disk has been created. Its name is displayed in the Device column: PassthroughDisk#001 created |
| Deleted Passthrough |
A passthrough disk has been deleted. Its name is displayed in the Device column: PassthroughDisk#001 deleted |
| Start Initialization |
Signals the start of RAID volume initialization. This is an important process in which the controller prepares the newly created volume by writing the necessary metadata and parity information to the disks. This initialization is essential to ensure data integrity and stable operation of the RAID array. (The corresponding timestamp is always displayed.) |
| Abort Initialization |
The user has aborted the initialization. The elapsed time is displayed under Elapse Time |
| Completed Init |
Initialization has been completed. The elapsed time is shown under Elapse Time. |
| HotSpare created |
This entry means that a hard disk has been configured as a hot spare (hot standby drive) in the RAID array. In the event of a Device Failed failure, the hot spare HDD takes over, and the system initiates the rebuild. |
| HotSpare deleted |
A previously created hot spare disk has been deleted. The corresponding slot of this HDD is also displayed. |
| Start rebuilding |
The recovery has begun. To return to the "Normal" state, the rebuild must be completed. |
| Stop rebuilding |
The rebuild was manually stopped by user intervention. The failure of another disk may also have interrupted the rebuild. |
| Start checking |
The controller has begun a check of the RAID array. This is usually a so-called "consistency check" or "surface scan." The WebGUI displays the corresponding name in the Device column, e.g., ARC-8050-VOL#000 Start Checking |
| Abort checking |
An ongoing check process (e.g., a parity or consistency check of the RAID array) was aborted prematurely. This can be caused by a manual abort by the administrator or by an unexpected event such as an error, power outage, or a problem with a hard disk. If the Elapse Time occurs, the log displays the time elapsed during the volume check. |
| Check completed |
The current RAID array verification process has been successfully completed. This verification process, often referred to as a consistency check or surface scan, verifies the integrity of the data and parity information on the disks in the RAID array. The GUI also displays the time required and any errors found. |
| Device Inserted |
A hard disk (HDD or SSD) has been inserted into the RAID system or has been recognized by it. This system message documents the successful installation or recognition of a new drive. The system also displays the corresponding slot (e.g., E1 Slot#5). |
| Device Removed |
A hard drive (HDD or SSD) has been removed from the RAID system or is no longer recognized. This could be caused by the drive being physically removed from the enclosure or by a connection loss, a defect, or a drive error. The corresponding slot is displayed in the Device column, e.g., E1 Slot#5. |
| Failed |
It indicates that a device—a drive (HDD or SSD), fan, volume, or power supply—has been detected as having failed. The device name (this can refer to sensors, parts, or devices) is displayed, e.g.:
E#1 FAN#1 - Failed
ARC-1886-VOL#000 - Volume Failed
E1 Slot#5 - Device Failed
E#1 Power#1 - Failed |
| Device Failed (SMART) |
The controller has detected an error in the SMART (Self-Monitoring, Analysis, and Reporting Technology) status of a hard drive. SMART is an integrated disk monitoring system that provides early warning of potential hardware problems. These could include increasing read errors, bad sectors, or other critical conditions. The affected slot is displayed. |
| Added |
A device has been added. The corresponding type is mentioned: e.g., Battery Module added |
| Removed |
A device was removed e.g.: Battery Module removed |
| Volume degraded |
A RAID volume is in a degraded state. The RAID array is still functional, but redundancy is compromised, usually due to one or more failed or faulty drives. While the volume can still be used, the failed drive should be replaced with a new global hot spare as soon as possible. Only once the rebuild on the replaced drive is complete will the volume return to a "Normal" state. |
| Raid set degraded |
A RAID set (a group of disks that together form a RAID volume) is in a degraded state. This could be partial failure (at least one disk in the RAID set has failed or is unavailable, compromising the redundancy of the RAID array), reduced security (the RAID set continues to function, but there is an increased risk of data loss if additional drives fail), or urgent action (the failed drive should be replaced as soon as possible to restore the RAID set and ensure full redundancy). |
| Complete Rebuild |
The rebuild process of a RAID volume has been successfully completed. A rebuild is necessary when one or more drives in the RAID array have failed and been replaced with new ones. During the rebuild, the missing data or parity information is reconstructed on the new drives to restore the redundancy and data integrity of the RAID array. For Elapse Time, the GUI displays the time required for this. |
| Discovered |
A new device or component has been detected by the controller. |
| Recovered |
In practice, "Recovered" means that a problem has been resolved and the affected devices have been restored from an error state. This is a positive message indicating that the controller has restored data integrity and resumed normal operation. e.g., E#1 FAN#1 Recovered (If no replacement has been performed previously, a previous defect should be assumed and the corresponding part replaced). |
| Over Temp |
Areca RAID controllers and storage systems continuously monitor the temperature of components such as the controller chip, the hard drives, and the enclosure. If a temperature is measured by the sensors that exceeds the threshold / limit value of the respective “device sensor”, the controller notices this and issues a corresponding message. |
| Reading Error |
A "Reading Error" is a warning signal that the affected hard drive may be damaged or about to fail. If these errors occur frequently, they can jeopardize the stability and data integrity of the RAID array. In a RAID array with redundancy (e.g., RAID 5 or RAID 6), the controller can often compensate for such errors using parity information, but repeated read errors increase the risk of data loss. When "Reading Error" messages occur, it is recommended to check the affected hard drive, back up important data, and, if necessary, replace the drive to ensure the reliability of the RAID system. An example of this message would be: E1 Slot#5 Reading Error |
| Writing Error |
"Writing Error" indicates that the controller had trouble writing data correctly to a hard drive, indicating a possible hardware defect or incipient failure and requiring immediate action. For example, the message would be E1 Slot#2 Writing Error. |
| Under Voltage |
It means that the supply voltage of the controller or a connected device has fallen below the defined minimum value. This warning indicates that the power supply is unstable or insufficient, which may lead to malfunctions, instability, or even damage to the hardware. (It also indicates a hardware defect.) The hardware monitor, meanwhile, displays live values of the operating voltage. |
| Overvoltage |
Indicates that the voltage has exceeded the permissible range and that measures are necessary to ensure a stable and safe power supply to prevent damage to the RAID system. (Also indicates a hardware defect.) The hardware monitor displays the live voltage values. |
