A RAID controller is a card or chip located between the operating system and a storage drive (usually a hard drive). This is an alert about the Adaptec raid controller. The Netdata Agent checks the logical device statuses which are managed by your raid controller.
This alert is triggered in critical state when a logical device state value is in degraded or failed state. This can indicate that one or more disks in your RAID configuration failed. Below you can find how tolerant is each raid configuration in cases of disk failures.
Fault tolerance for the most popular raid configurations
RAID 0 provides no fault tolerance. Any drive failures will cause data loss, so do not use this
on a mission critical server.
RAID 1 configuration is best used for situations where capacity isn’t a requirement but data
protection is. This set up mirrors two disks so you can have 1 drive fail and still be able to
recover your data.
RAID 5 can withstand a single drive failure with a tradeoff in performance.
RAID 6 can withstand two disk failures at one time.
RAID 10 can survive a single drive failure per array.
Your system manages your Adaptec raid controller via the ARCCONF command line tool. You can find more information about this utility from the user’s guide for the ARCCONF.
Data is priceless. Before you perform any action, make sure that you have taken any necessary backup steps. Netdata is not liable for any loss or corruption of any data, database, or software.
Your Adaptec RAID card will automatically start to rebuild a faulty hard drive when you replace it with a healthy one. Sometimes this operation may take some time or may not start automatically.
Manually change the status of your ldThis action will trigger a rebuild on your RAID.
Verify that a rebuild is not in process.
root@netdata # arcconf GETSTATUS <Controller_num>
Check for idle/missing segments of logical devices.
Manually change your ld status
root@netdata # arcconf SETSTATE <Controller_num> LOGICALDRIVE <LD_num> OPTIMAL ADVANCED nocheck noprompt