Today, my colleague told me that a Dell server did raid, using MEGACLI not to see the raid information, went up to see it did not return any raid information, but did raid on the machine.
This is strange, and then the MEGACLI upgrade to the latest version, or the same results
The company is basically a Dell-series server, the raid information of the previous machine was MEGACLI obtained, which is a bit strange. Because of the previous RAID card version caused by other issues, so this time also suspected is not the raid card version caused by the problem, so want to see the System RAID card version information
Did not find the raid information, but looked at the SCSI controller information, according to sas1068e on the internet to find out that sas1068e RAID card is SAS 6i/r.
Why SAS 6I/R RAID information is not available with the MegaCli64 command, SAS 6/ir only supports 2 hard drives for RAID0 or RAID1. Now go back to see the MegaCli64 tool, the MegaCli64 tool is very useful, many features, not only can view the RAID card information, but also can set the raid card, but it does not support the SAS 6/ir RAID card, Dell's many 1U models of the server default RAID controller are SAS 6I/R, and for this controller MegaCli64 is not available. So why does MegaCli64 not support SAS 6i/r, because MEGACLI is designed for the PERC controller (it uses a familiar megaraid driver), but the SAS 6I/R controller is for the mpt* type of driver, Therefore, the RAID information is not MegaCli64. However, if you want to manage SAS 6i/r in command line mode, you can use the Lsiutil tool.
Download Lsiutil Tools
Link:
Ftp://ftp.ntplx.net/pub/LSI/LSIUtil_1.62.zip
After the decompression to see the supported system is still pretty much AH
I am a Linux 64-bit system, in the Linux directory directly copied lsiutil.x86_64 to the target machine, modified to executable permissions. Let's see how lsiutil.x86_64 is used, lsiutil.x86_64 has two modes, one is interactive and the other is command line mode:
lsiutil.x86_64 Interactive
lsiutil.x86_64 Command-line
You can see that lsiutil.x86_64 is also able to view raid information. The help documentation is as follows:
Http://www.thomas-krenn.com/de/wikiDE/images/4/44/Lsi_userguide_2006_20130528.pdf
If you are a debian/ubuntu system, you can download the appropriate Deb package
' Http://hwraid.le-vert.net/debian/pool-wheezy/lsiutil_1.60-1_amd64.deb ' dpkg-i lsiutil_1. 60-1_amd64.deb
The official explanations on the sub-issue are as follows:
Http://lists.us.dell.com/pipermail/linux-poweredge/2009-March/038758.html
The following is an enclosed MegaCli64 return status code information
MEGACLI Error Messages0x00 Command completed successfully0x01 Invalid Command0x02 DCMD opcodeis invalid0x03 Input Parameters is invalid0x04 Invalid Sequence Number0x05 Abort isn' t possible for the requested COMMAND0X06 application ' host' Code not found0x07 application already in Use-try later0x08 application not initialized0x09 Given array index is inval id0x0a Unable to add missing drive to array, as row have no empty slots0x0b Some of the CFG resources conflict with each OT Her or the current config0x0c Invalid device id/select-timeout0x0d Drive are too small for requested operation0x0e Flash Memory allocation failed0x0f Flash download already in progress0x10 Flash operation failed0x11 Flash image is bad0x12 Dow nloaded Flash image is incomplete0x13 flash OPEN were not done0x14 flash sequence are not active0x15 Flush command failed0x1 6 Specified application doesn ' t have host-resident code0x17 LD operationNot POSSIBE-CCIsIn progress0x18 LD InitializationIn progress0x19 LBAis outof range0x1a Maximum LDs is already configured0x1b LDIsNot OPTIMAL0x1c LD RebuildIsIn progress0X1D LDis undergoing reconstruction0X1E LD RAID LevelIs wrongFor requested operation0x1f Too Many spares assigned0x20 Scratch MemoryNot Available-Try command again later0x21 Error writing MFC data to Seeprom0x22 Required HWis missing (i.e. Alarmor BBU)0x23 ItemNot found0x24 LD Drives isNot within an enclosure0x25 PD CLEAR operationIsIn progress0x26 Unable to use SATA (SAS) drive to replace SAS (SATA)0x27 Patrol Readis disabled0x28 Given Row Indexis invalid0x2d SCSI command done, but Non-good status is Received-see mf.hdr.extStatusFor Scsi_status0x2e IO RequestFor MFI_CMD_OP_PD_SCSI Failed-see ExtstatusFor DM Error0x2f Matches SCSI reservation_conflict0x30 Oneor moreOf the flush operations failed0x31 FW Real-time currentlyNot set0x32 Command IssuesWhile FWIn wrong state (i.e. GET RECONWhen opNot active)0x33 LDIsNot Offline-ioNot possible0X34 Peer Controller rejected request (possibly due to resource conflict)0X35 unable to inform peerof communication changes (retry might be appropriate)0x36 LD Reservation alreadyIn progress0X37 I²c errors were detected0x38 PCI errors occurred during XOR/DMA operation0X39 Diagnostics Failed-see Event LogFor details0X3A Unable to process command as boot messages is pending0x3b returnedInchCaseIf foreign configurations is imcomplete0x3d returnedInchCaseIf a commandis triedOn unsupported hardware0x3e CC Schedulingis disabled0x3f PD Copyback operationIsIn progress0x40 Selected more than one PD per array0x41 microcode Update operation failed0x42 Unable to process command as drive security featureIsNot enabled0x43 Controller already has a lock key0x44 Lock key cannot be backed-up0x45 Lock Key Backup cannot be verified0x46 Lock Key from backup failed verification0x47 Rekey operationNot Allowed,Unless controller already has a lock key0x48 Lock KeyIsNot valid, cannot authenticate0x49 Lock key from escrow cannot be used0X4A Lock Key Backup (pass-phrase)is required0x4b Secure LD exist0X4C LD Secure operationIsNot allowed0X4D reprovisioningIsNot allowed0x4e Drive Security Type (FDEor non-fde)IsNot appropriateFor requested operation0x4f LD Encryption TypeIsNot supported0X50 cannot mix FDEand Non-fde drivesIn same array0X51 cannot mix secureand unsecured LDIn same array0x52 Secret KeyNot allowed0X53 physical device errors were detected0x54 Controller has LD cache pinned0x55 requested operationis alreadyIn progress0x56 another power state set operationis in progress0x57 Power State Span class= "Hljs-keyword" >of device is not Correct0x58 No PD is available for Patrol Read0x59 Controller resert is required0x5a No EKM Boot agent Detected0x5b No space on the snapshot Repositiry vd< Span class= "Hljs-number" >0x5c for consistency SET pits, some PiT creations might fail and some Succeed0xff Invalid status-used for polling command completion< /span>
http://www.codeweblog.com/dell%E6%9C%8D%E5%8A%A1%E5%99%A8megacli%E5%91%BD%E4%BB%A4%E5%8F%AA%E8%BF%94%E5%9B% 9eexit-code-0x00%e9%97%ae%e9%a2%98%e5%88%86%e6%9e%90/
Dell Server MEGACLI command returns only exit code:0x00 problem analysis