RAID member failed critical alerts

Products

• Content Analysis Software
• CAS-S200
• CAS-S400
• CAS-S500

Issue/Introduction

The following health monitoring alert is received:

RAID casma-raid Working Members CRITICAL - 1/2  members are working

 

CAS event logs show:

info check-raid-status[24535]: No of failed members: 1 for the RAID: casma_raid

 

Only one of two disks shows as present on the device.

Resolution

Generate the Content Analysis troubleshooting logs and check the file /var/log/dmesg for any errors present on the disk.

 

Example from a failing disk.

[   83.592327] sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=7s
[   83.592331] sd 0:0:0:0: [sda] tag#0 CDB: Synchronize Cache(10) 35 00 00 00 00 00 00 00 00 00
[   83.592338] blk_update_request: I/O error, dev sda, sector 974663688
[   83.592370] sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[   83.592373] sd 0:0:0:0: [sda] tag#0 CDB: Write(10) 2a 00 22 28 90 00 00 00 08 00
[   83.592375] blk_update_request: I/O error, dev sda, sector 573083648
[   83.592413] sd 0:0:0:0: [sda] Read Capacity(16) failed: Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[   83.592416] sd 0:0:0:0: [sda] Sense not available.
[   83.592448] sd 0:0:0:0: [sda] Read Capacity(10) failed: Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[   83.592451] sd 0:0:0:0: [sda] Sense not available.
[   83.592480] sda: detected capacity change from 500107862016 to 0
[   83.609863] md: super_written gets error=-5, uptodate=0
[   83.609867] md/raid1:md127: Disk failure on sda1, disabling device.

 

An RMA for the disk was issued to resolve the issue.