| How to Collect RAID Controller Logs via MegaCli Command |
Content | Objective - To collect RAID Controller logs from the running OS in the server
- To troubleshoot issues related to RAID Controller (Broadcom SAS3108, Broadcom SAS3516)
Environment - Broadcom SAS3108
- Broadcom SAS3516
- HCP G10
- HCP G11
Procedure - To generate the RAID controller log (ttylog) output:
- MegaCli.exe -FwTermLog -Dsply -aALL (for Windows)
- ./MegaCli64 -FwTermLog -Dsply -aALL (for Linux)
- To generate a list with information about the RAID controllers, virtual disks and hard disks installed:
- MegaCli.exe -PDList -aALL (for Windows)
- ./MegaCli64 -PDList -aALL (for Linux)
- To generate a list with information about existing RAID volumes and configurations:
- MegaCli.exe -LDInfo -LALL -aALL (for Windows)
- ./MegaCli64 -LDInfo -LALL -aALL (for Linux)
- To generate a list with information about RAID controller settings:
- MegaCli.exe -AdpAllInfo -aALL (for Windows)
- ./MegaCli64 -AdpAllInfo -aALL (for Linux)
- To generate a detailed list of the battery status of the RAID controller (state of charge, learning cycle, etc.):
- MegaCli.exe -AdpBbuCmd -aALL (for Windows)
- ./MegaCli64 -AdpBbuCmd -aALL (for Linux)
- To create the RAID controller log (ttylog) with all information since very first controller initialization:
- MegaCli.exe -AdpEventLog -IncludeDeleted -f filename.txt -aALL (for Windows)
- ./MegaCli64 -AdpEventLog -IncludeDeleted -f filename.txt -aALL (for Linux)
(Note: This filename.txt will always be saved in the MegaCLI root folder) Additional Notes The MegaCLI utility can be downloaded from Broadcom site: |
|