You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I added storcli to my phpSysInfo some time ago to display the raid status.
Today I noticed that storcli does not show the consistency check status. I assume that the rebuild status and other active operations would not be shown either, since the storcli64 /call show all command does not show any active operations.
You could expand the available data with the command storcli64 /call show all>raidstorcli.tmp; storcli64 /call /vall show all>>raidstorcli.tmp so that you can also evaluate the active operations.
This is what the output from this command looks like:
Thank you for the Christmas present.
What the status appears for under "Active Operations" remains to be seen in the future.
I found "Background Initialization" and "Consistency Check" listed under "Active Operations".
I like Storcli because it gives more information than megaclisas-status. (Hard Drive Model, Supported Raid Types, BBU Temperature)
The disadvantage is that with storcli you have to query everything individually. (/call show all; /call show patrolread; /call /vall show all; /call /eall /sall show all; /call /eall /sall show rebuild; ...) So everything has its pros and cons.
Good day,
I added storcli to my phpSysInfo some time ago to display the raid status.
Today I noticed that storcli does not show the consistency check status. I assume that the rebuild status and other active operations would not be shown either, since the
storcli64 /call show all
command does not show any active operations.You could expand the available data with the command
storcli64 /call show all>raidstorcli.tmp; storcli64 /call /vall show all>>raidstorcli.tmp
so that you can also evaluate the active operations.This is what the output from this command looks like:
raidstorcli.tmp.txt
Best regards and happy Christmas holidays
schabau
The text was updated successfully, but these errors were encountered: