Many server vendors ship their servers with branded MegaRAID RAID controllers. The relationship I have with the many flavours they come in is sometimes a bit poluted I dare to saay.
An excellent quick guide to the more modern StorCLI utility available to Linux, Windows, FreeBSD and others is Thomas Krenn's Wiki page on StorCLI. More often than not I have to look up in the CLI reference made available by (today) Broadcom.
Now I've come across a slightly stubborn controller that reported a Virtual Drive not being consistent.
I've come across a system with an IBM-branded MegaRAID controller where one of the virtual disks (a RAID5) show an optimal state but not consistent.
# /opt/MegaRAID/storcli/storcli64 /c0 show
Generating detailed summary of the adapter, it may take a while to complete.
CLI Version = 007.0409.0000.0000 Nov 06, 2017
Operating system = Linux3.2.0-5-amd64
[...]
Product Name = ServeRAID M5110
[...]
FW Package Build = 23.34.0-0018
BIOS Version = 5.50.03.0_4.17.08.00_0x06110200
FW Version = 3.460.105-6456
[...]
VD LIST :
=======
---------------------------------------------------------------
DG/VD TYPE State Access Consist Cache Cac sCC Size Name
---------------------------------------------------------------
0/0 RAID1 Optl RW Yes RWBD - ON 278.464 GB
1/1 RAID5 Optl RW No RWBD - ON 3.635 TB
---------------------------------------------------------------
I've attempted to start a consistency check on that VD but the controller always reported it couldn't:
root@ieu04-sr21:~# /opt/MegaRAID/storcli/storcli64 /c0 /v1 start cc
[...]
------------------------------------------------
VD Operation Status ErrCd ErrMsg
------------------------------------------------
1 CC Failed 255 Start CC not possible
------------------------------------------------
At first I suspected a running patrol read would block it. (storcli64 /c0 show pr) but the consistency check wouldn't start afterwards either. In the end after trying to resume it it was finally OK:
# /opt/MegaRAID/storcli/storcli64 /c0 /v1 show cc
[...]
--------------------------------------------------
VD Operation Progress% Status Estimated Time Left
--------------------------------------------------
1 CC - Paused -
# /opt/MegaRAID/storcli/storcli64 /c0 /v1 resume cc
CLI Version = 007.0409.0000.0000 Nov 06, 2017
Operating system = Linux3.2.0-5-amd64
Controller = 0
Status = Success
Description = Resume CC Operation Success
Afterwards the consistency check quickly ended as done and the alert issued by the monitoring system got cleared. Nonetheless I manually started a consistency check in order to see if any issues would be found. I guess the consistency check was paused at some point in time due to a preceeding firmware updated but wasn't restarted automatically afterwards.
If this is caused after a migration, it might be a running background initialization process:
# storcli /c0/v0 start cc
CLI Version = 007.1017.0000.0000 May 10, 2019
Operating system = Linux 5.4.106-1-pve
Controller = 0
Status = Failure
Description = None
Detailed Status :
===============
————————————————
VD Operation Status ErrCd ErrMsg
————————————————
0 CC Failed 255 Start CC not possible
————————————————
Starting CC not possible.
# storcli /c0/v0 show bgi
CLI Version = 007.1017.0000.0000 May 10, 2019
Operating system = Linux 5.4.106-1-pve
Controller = 0
Status = Success
Description = None
VD Operation Status :
===================
————————————————————–
VD Operation Progress% Status Estimated Time Left
————————————————————–
0 BGI 47 In progress 1 Days 23 Hours 11 Minutes
————————————————————–