├── 2118ir.bin ├── 2118ir_p7.bin ├── 2118it.bin ├── 2118it_p7.bin ├── DELL_6GBPSAS.FW ├── DELL_mptsas2.rom ├── MEGACLI.TXT ├── MEGAOEM.EXE ├── MEGAOEM.TXT ├── MEGAREC.TXT ├── MEGASAS.LOG ├── MegaCli.exe ├── MegaFl.exe ├── MegaRec.exe ├── README.md ├── SBR-A11.bin ├── SBR-A21.bin ├── XGREP.COM ├── docs ├── README_9211_8i_Package_P20_IR_IT_FW_BIOS_for_MSDOS_Windows.txt ├── README_Installer_P20_UEFI.txt ├── SAS2BIOS_Phase20.0-7.39.02.00.pdf ├── SAS2FLASH_Phase20.0-20.00.00.00.pdf ├── SAS2FW_Phase20-20.00.07.00 Release Notes.pdf └── SAS2Flash_ReferenceGuide.pdf ├── efi └── boot │ ├── bootaa64.efi │ ├── bootarm.efi │ ├── bootia32.efi │ ├── bootia64.efi │ └── bootx64.efi ├── img ├── img1.jpg └── img2.jpg ├── mptbios.txt ├── mptsas2.rom ├── mptsas2_p7.rom ├── sas2flash.efi ├── sas2flsh.exe ├── sas2hax.efi ├── sas2haxp20.efi └── sbrempty.bin /2118ir.bin: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/lrq3000/lsi_sas_hba_crossflash_guide/e458a8e359a582e8a7d046be8ecbc8bf678d7b1b/2118ir.bin -------------------------------------------------------------------------------- /2118ir_p7.bin: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/lrq3000/lsi_sas_hba_crossflash_guide/e458a8e359a582e8a7d046be8ecbc8bf678d7b1b/2118ir_p7.bin -------------------------------------------------------------------------------- /2118it.bin: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/lrq3000/lsi_sas_hba_crossflash_guide/e458a8e359a582e8a7d046be8ecbc8bf678d7b1b/2118it.bin -------------------------------------------------------------------------------- /2118it_p7.bin: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/lrq3000/lsi_sas_hba_crossflash_guide/e458a8e359a582e8a7d046be8ecbc8bf678d7b1b/2118it_p7.bin -------------------------------------------------------------------------------- /DELL_6GBPSAS.FW: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/lrq3000/lsi_sas_hba_crossflash_guide/e458a8e359a582e8a7d046be8ecbc8bf678d7b1b/DELL_6GBPSAS.FW -------------------------------------------------------------------------------- /DELL_mptsas2.rom: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/lrq3000/lsi_sas_hba_crossflash_guide/e458a8e359a582e8a7d046be8ecbc8bf678d7b1b/DELL_mptsas2.rom -------------------------------------------------------------------------------- /MEGACLI.TXT: -------------------------------------------------------------------------------- 1 | DOS/32A warning (9004): mouse initialization failed 2 | 3 | 4 | 5 | MegaCLI SAS RAID Management Tool Ver 8.05.06 Aug 28, 2012 6 | 7 | (c)Copyright 2011, LSI Corporation, All Rights Reserved. 8 | 9 | 10 | 11 | NOTE: The following options may be given at the end of any command below: 12 | 13 | [-Silent] [-AppLogFile filename] [-NoLog] [-page [N]] 14 | [-] is optional. 15 | N - Number of lines per page. 16 | 17 | MegaCli -v 18 | MegaCli -help|-h|? 19 | MegaCli -adpCount 20 | MegaCli -AdpSetProp {CacheFlushInterval -val} | { RebuildRate -val} 21 | | {PatrolReadRate -val} | {BgiRate -val} | {CCRate -val} 22 | | {ReconRate -val} | {SpinupDriveCount -val} | {SpinupDelay -val} 23 | | {CoercionMode -val} | {ClusterEnable -val} | {PredFailPollInterval -val} 24 | | {BatWarnDsbl -val} | {EccBucketSize -val} | {EccBucketLeakRate -val} 25 | | {AbortCCOnError -val} | AlarmEnbl | AlarmDsbl | AlarmSilence 26 | | {SMARTCpyBkEnbl -val} | {SSDSMARTCpyBkEnbl -val} | NCQEnbl | NCQDsbl 27 | | {MaintainPdFailHistoryEnbl -val} | {RstrHotSpareOnInsert -val} 28 | | {DisableOCR -val} | {BootWithPinnedCache -val} | {enblPI -val} | {PreventPIImport -val} 29 | | {EnblSpinDownUnConfigDrvs -val} -aN|-a0,1,2|-aALL 30 | | AutoEnhancedImportEnbl | AutoEnhancedImportDsbl -aN|-a0,1,2|-aALL 31 | | {ExposeEnclDevicesEnbl -val}|{UseDiskActivityforLocate -val} -aN|-a0,1,2|-aALL 32 | | {DsblSpinDownHsp -val} -aN|-a0,1,2|-aALL 33 | | {SpinDownTime -val} -aN|-a0,1,2|-aALL 34 | | {SpinUpEncDrvCnt -val} -aN|-a0,1,2|-aALL 35 | | {SpinUpEncDelay -val} | { Perfmode -val} -aN|-a0,1,2|-aALL 36 | MegaCli -AdpSetProp -AutoDetectBackPlaneDsbl -val -aN|-a0,1,2|-aALL 37 | val - 0=Enable Auto Detect of SGPIO and i2c SEP. 38 | 1=Disable Auto Detect of SGPIO. 39 | 2=Disable Auto Detect of i2c SEP. 40 | 3=Disable Auto Detect of SGPIO and i2c SEP. 41 | MegaCli -AdpSetProp -CopyBackDsbl -val -aN|-a0,1,2|-aALL 42 | val - 0=Enable Copyback. 43 | 1=Disable Copyback. 44 | MegaCli -AdpSetProp -EnableJBOD -val -aN|-a0,1,2|-aALL 45 | val - 0=Disable JBOD mode. 46 | 1=Enable JBOD mode. 47 | MegaCli -AdpSetProp -DsblCacheBypass -val -aN|-a0,1,2|-aALL 48 | val - 0=Enable Cache Bypass. 49 | 1=Disable Cache Bypass. 50 | MegaCli -AdpSetProp -LoadBalanceMode -val -aN|-a0,1,2|-aALL 51 | val - 0=Auto Load balance mode. 52 | 1=Disable Load balance mode. 53 | MegaCli -AdpSetProp -UseFDEOnlyEncrypt -val -aN|-a0,1,2|-aALL 54 | val - 0=FDE and controller encryption (if HW supports) is allowed. 55 | 1=Only support FDE encryption, disallow controller encryption. 56 | MegaCli -AdpSetProp -PrCorrectUncfgdAreas -val -aN|-a0,1,2|-aALL 57 | val - 0= Correcting Media error during PR is disabled. 58 | 1=Correcting Media error during PR is allowed. 59 | MegaCli -AdpSetProp -DsblSpinDownHSP -val -aN|-a0,1,2|-aALL 60 | val - 0= Spinning down the Hot Spare is enabled. 61 | 1=Spinning down the Hot Spare is disabled. 62 | MegaCli -AdpSetProp -DefaultLdPSPolicy -Automatic| -None | -Maximum| -MaximumWithoutCaching -aN|-a0,1,2|-aALL 63 | MegaCli -AdpSetProp -DisableLdPS -interval n1 -time n2 -aN|-a0,1,2|-aALL 64 | where n1 is the number of hours beginning at time n2 65 | where n2 is the number of minutes from 12:00am 66 | MegaCli -AdpSetProp -ENABLEEGHSP -val -aN|-a0,1,2|-aALL 67 | val - 0= Disabled Emergency GHSP. 68 | 1= Enabled Emergency GHSP. 69 | MegaCli -AdpSetProp -ENABLEEUG -val -aN|-a0,1,2|-aALL 70 | val - 0= Disabled Emergency UG as Spare. 71 | 1= Enabled Emergency UG as Spare. 72 | MegaCli -AdpSetProp -ENABLEESMARTER -val -aN|-a0,1,2|-aALL 73 | val - 0= Disabled Emergency Spare as Smarter. 74 | 1= Enabled Emergency Spare as Smarter. 75 | MegaCli -AdpSetProp -DPMenable -val -aN|-a0,1,2|-aALL 76 | val - 0=Disable Drive Performance Monitoring . 77 | 1=Enable Drive Performance Monitoring. 78 | MegaCli -AdpSetProp -SupportSSDPatrolRead -val -aN|-a0,1,2|-aALL 79 | val - 0=Disable Patrol read for SSD drives . 80 | 1=Enable Patrol read for SSD drives. 81 | MegaCli -AdpGetProp CacheFlushInterval | RebuildRate | PatrolReadRate 82 | | BgiRate | CCRate | ReconRate | SpinupDriveCount | SpinupDelay 83 | | CoercionMode | ClusterEnable | PredFailPollInterval | BatWarnDsbl 84 | | EccBucketSize | EccBucketLeakRate | EccBucketCount | AbortCCOnError 85 | | AlarmDsply | SMARTCpyBkEnbl | SSDSMARTCpyBkEnbl | NCQDsply 86 | | MaintainPdFailHistoryEnbl | RstrHotSpareOnInsert 87 | | EnblSpinDownUnConfigDrvs | DisableOCR 88 | | BootWithPinnedCache | enblPI | PreventPIImport | AutoEnhancedImportDsply | AutoDetectBackPlaneDsbl 89 | | CopyBackDsbl | LoadBalanceMode | UseFDEOnlyEncrypt | WBSupport | EnableJBOD 90 | | DsblCacheBypass | ExposeEnclDevicesEnbl | DsblSpinDownHsp | SpinDownTime 91 | | PrCorrectUncfgdAreas | UseDiskActivityforLocate | ENABLEEGHSP | ENABLEEUG 92 | | ENABLEESMARTER | -DPMenable | Perfmode -aN|-a0,1,2|-aALL 93 | | DsblSpinDownHSP -aN|-a0,1,2|-aALL 94 | | DefaultLdPSPolicy | DisableLdPsInterval | DisableLdPsTime 95 | | SpinUpEncDrvCnt | SpinUpEncDelay -aN|-a0,1,2|-aALL 96 | MegaCli -AdpAllInfo -aN|-a0,1,2|-aALL 97 | MegaCli -AdpGetTime -aN|-a0,1,2|-aALL 98 | MegaCli -AdpSetTime yyyymmdd hh:mm:ss -aN 99 | MegaCli -AdpSetVerify -f fileName -aN|-a0,1,2|-aALL 100 | MegaCli -AdpBIOS -Enbl |-Dsbl | -SOE | -BE | -HCOE | -HSM | EnblAutoSelectBootLd | DsblAutoSelectBootLd | -Dsply -aN|-a0,1,2|-aALL 101 | MegaCli -AdpBootDrive {-Set {-Lx | -physdrv[E0:S0]}} | {-Unset {-Lx | -physdrv[E0:S0]}} |-Get -aN|-a0,1,2|-aALL 102 | MegaCli -AdpAutoRbld -Enbl|-Dsbl|-Dsply -aN|-a0,1,2|-aALL 103 | MegaCli -AdpCacheFlush -aN|-a0,1,2|-aALL 104 | MegaCli -AdpPR -Dsbl|EnblAuto|EnblMan|Start|Suspend|Resume|Stop|Info 105 | |{SetDelay Val}|{-SetStartTime yyyymmdd hh}|{maxConcurrentPD Val} -aN|-a0,1,2|-aALL 106 | MegaCli -AdpCcSched -Dsbl|-Info|{-ModeConc | -ModeSeq [-ExcludeLD -LN|-L0,1,2] 107 | [-SetStartTime yyyymmdd hh ] [-SetDelay val ] } -aN|-a0,1,2|-aALL 108 | MegaCli -AdpCcSched -SetStartTime yyyymmdd hh -aN|-a0,1,2|-aALL 109 | MegaCli -AdpCcSched -SetDelay val -aN|-a0,1,2|-aALL 110 | MegaCli -FwTermLog -BBUoff|BBUoffTemp|BBUon|Dsply|Clear -aN|-a0,1,2|-aALL 111 | MegaCli -AdpAlILog -aN|-a0,1,2|-aALL 112 | MegaCli -AdpDiag [val] -aN|-a0,1,2|-aALL 113 | val - Time in second. 114 | MegaCli -AdpBatTest -aN|-a0,1,2|-aALL 115 | MegaCli -AdpDowngrade -aN|-a0,1,2|-aALL 116 | MegaCli -PDList -aN|-a0,1,2|-aALL 117 | MegaCli -PDGetNum -aN|-a0,1,2|-aALL 118 | MegaCli -pdInfo -PhysDrv[E0:S0,E1:S1,...] -aN|-a0,1,2|-aALL 119 | MegaCli -PDOnline -PhysDrv[E0:S0,E1:S1,...] -aN|-a0,1,2|-aALL 120 | MegaCli -PDOffline -PhysDrv[E0:S0,E1:S1,...] -aN|-a0,1,2|-aALL 121 | MegaCli -PDMakeGood -PhysDrv[E0:S0,E1:S1,...] | [-Force] -aN|-a0,1,2|-aALL 122 | MegaCli -PDMakeJBOD -PhysDrv[E0:S0,E1:S1,...] -aN|-a0,1,2|-aALL 123 | MegaCli -PDHSP {-Set [-Dedicated [-ArrayN|-Array0,1,2...]] [-EnclAffinity] [-nonRevertible]} 124 | |-Rmv -PhysDrv[E0:S0,E1:S1,...] -aN|-a0,1,2|-aALL 125 | MegaCli -PDRbld -Start|-Stop|-Suspend|-Resume|-ShowProg |-ProgDsply 126 | -PhysDrv [E0:S0,E1:S1,...] -aN|-a0,1,2|-aALL 127 | MegaCli -PDClear -Start|-Stop|-ShowProg |-ProgDsply 128 | -PhysDrv [E0:S0,E1:S1,...] -aN|-a0,1,2|-aALL 129 | MegaCli -PdLocate {[-Start] | -stop } -physdrv[E0:S0,E1:S1,...] -aN|-a0,1,2|-aALL 130 | MegaCli -PdMarkMissing -physdrv[E0:S0,E1:S1,...] -aN|-a0,1,2|-aALL 131 | MegaCli -PdGetMissing -aN|-a0,1,2|-aALL 132 | MegaCli -PdReplaceMissing -physdrv[E0:S0] -arrayA, -rowB -aN 133 | MegaCli -PdPrpRmv [-UnDo] -physdrv[E0:S0] -aN|-a0,1,2|-aALL 134 | MegaCli -EncInfo -aN|-a0,1,2|-aALL 135 | MegaCli -EncStatus -aN|-a0,1,2|-aALL 136 | MegaCli -PhyInfo -phyM -aN|-a0,1,2|-aALL 137 | MegaCli -PhySetLinkSpeed -phyM -speed -aN|-a0,1,2|-aALL 138 | MegaCli -LDInfo -Lx|-L0,1,2|-Lall -aN|-a0,1,2|-aALL 139 | MegaCli -LDSetProp {-Name LdNamestring} | -RW|RO|Blocked|RemoveBlocked | WT|WB [-Immediate]|RA|NORA | DsblPI 140 | | Cached|Direct | -EnDskCache|DisDskCache | CachedBadBBU|NoCachedBadBBU 141 | -Lx|-L0,1,2|-Lall -aN|-a0,1,2|-aALL 142 | MegaCli -LDSetPowerPolicy -Default| -Automatic| -None| -Maximum| -MaximumWithoutCaching 143 | -Lx|-L0,1,2|-Lall -aN|-a0,1,2|-aALL 144 | MegaCli -LDGetProp -Cache | -Access | -Name | -DskCache | -PSPolicy | Consistency -Lx|-L0,1,2|-LALL 145 | -aN|-a0,1,2|-aALL 146 | MegaCli -getLdExpansionInfo -Lx|-L0,1,2|-Lall -aN|-a0,1,2|-aALL 147 | MegaCli -LdExpansion -pN -dontExpandArray -Lx|-L0,1,2|-Lall -aN|-a0,1,2|-aALL 148 | MegaCli -Cachecade -assign|-remove -Lx|-L0,1,2|-LALL -aN|-a0,1,2|-aALL 149 | MegaCli -LDInit {-Start [-full]}|-Abort|-ShowProg|-ProgDsply -Lx|-L0,1,2|-LALL -aN|-a0,1,2|-aALL 150 | MegaCli -LDCC {-Start [-force]}|-Abort|-Suspend|-Resume|-ShowProg|-ProgDsply -Lx|-L0,1,2|-LALL -aN|-a0,1,2|-aALL 151 | MegaCli -LDBI -Enbl|-Dsbl|-getSetting|-Abort|-Suspend|-Resume|-ShowProg|-ProgDsply -Lx|-L0,1,2|-LALL -aN|-a0,1,2|-aALL 152 | MegaCli -LDRecon {-Start -rX [{-Add | -Rmv} -Physdrv[E0:S0,...]]}|-ShowProg|-ProgDsply 153 | -Lx -aN 154 | MegaCli -LdPdInfo -aN|-a0,1,2|-aALL 155 | MegaCli -LDGetNum -aN|-a0,1,2|-aALL 156 | MegaCli -LDBBMClr -Lx|-L0,1,2,...|-Lall -aN|-a0,1,2|-aALL 157 | MegaCli -GetBbtEntries -Lx|-L0,1,2|-Lall -aN|-a0,1,2|-aALL 158 | MegaCli -CfgLdAdd -rX[E0:S0,E1:S1,...] [WT|WB] [NORA|RA] [Direct|Cached] 159 | [CachedBadBBU|NoCachedBadBBU] [-szXXX [-szYYY ...]] 160 | [-strpszM] [-Hsp[E0:S0,...]] [-AfterLdX] [-Force]|[Secure] 161 | [-Default| -Automatic| -None| -Maximum| -MaximumWithoutCaching] [-enblPI] -aN 162 | MegaCli -CfgCacheCadeAdd -Physdrv[E0:S0,...] {-Name LdNamestring} -aN|-a0,1,2|-aALL 163 | MegaCli -CfgEachDskRaid0 [WT|WB] [NORA|RA] [Direct|Cached] [-enblPI] 164 | [CachedBadBBU|NoCachedBadBBU] [-strpszM]|[Secure] [-Default| -Automatic| -None| -Maximum| -MaximumWithoutCaching] [-enblPI] -aN|-a0,1,2|-aALL 165 | MegaCli -CfgClr -aN|-a0,1,2|-aALL 166 | MegaCli -CfgDsply -aN|-a0,1,2|-aALL 167 | MegaCli -CfgLdDel -LX|-L0,2,5...|-LALL -aN|-a0,1,2|-aALL 168 | MegaCli -CfgCacheCadeDel -LX|-L0,2,5...|-LALL -aN|-a0,1,2|-aALL 169 | MegaCli -CfgFreeSpaceinfo -aN|-a0,1,2|-aALL 170 | MegaCli -CfgSpanAdd -r10 -Array0[E0:S0,E1:S1] -Array1[E0:S0,E1:S1] [-ArrayX[E0:S0,E1:S1] ...] [-enblPI] -aN 171 | MegaCli -CfgSpanAdd -r50 -Array0[E0:S0,E1:S1,E2:S2,...] -Array1[E0:S0,E1:S1,E2:S2,...] 172 | [-ArrayX[E0:S0,E1:S1,E2:S2,...] ...] [WT|WB] [NORA|RA] [Direct|Cached] 173 | [CachedBadBBU|NoCachedBadBBU][-strpszM][-szXXX[-szYYY ...]][-AfterLdX]| 174 | [Secure] 175 | [-Default| -Automatic| -None| -Maximum| -MaximumWithoutCaching] [-enblPI] -aN 176 | MegaCli -CfgSpanAdd -r60 -Array0[E0:S0,E1:S1,E2:S2,E3,S3...] -Array1[E0:S0,E1:S1,E2:S2,...] 177 | [-ArrayX[E0:S0,E1:S1,E2:S2,E3,S3...] ...] [WT|WB] [NORA|RA] [Direct|Cached] 178 | [CachedBadBBU|NoCachedBadBBU][-strpszM][-szXXX[-szYYY ...]][-AfterLdX]| 179 | [Secure] 180 | [-Default| -Automatic| -None| -Maximum| -MaximumWithoutCaching] [-enblPI] -aN 181 | MegaCli -CfgAllFreeDrv -rX [-SATAOnly] [-SpanCount XXX] [WT|WB] [NORA|RA] 182 | [Direct|Cached] [CachedBadBBU|NoCachedBadBBU] [-strpszM] 183 | [-HspCount XX [-HspType -Dedicated|-EnclAffinity|-nonRevertible]] | 184 | [Secure] 185 | [-Default| -Automatic| -None| -Maximum| -MaximumWithoutCaching] [-enblPI] -aN 186 | MegaCli -CfgSave -f filename -aN 187 | MegaCli -CfgRestore -f filename -aN 188 | MegaCli -CfgForeign -Scan | [-Passphrase sssssssssss] -aN|-a0,1,2|-aALL 189 | MegaCli -CfgForeign -Dsply [x] | [-Passphrase sssssssssss] -aN|-a0,1,2|-aALL 190 | MegaCli -CfgForeign -Preview [x] | [-Passphrase sssssssssss] -aN|-a0,1,2|-aALL 191 | MegaCli -CfgForeign -Import [x] | [-Passphrase sssssssssss] -aN|-a0,1,2|-aALL 192 | MegaCli -CfgForeign -Clear [x]|[-Passphrase sssssssssss] -aN|-a0,1,2|-aALL 193 | x - index of foreign configurations. Optional. All by default. 194 | MegaCli -AdpEventLog -GetEventLogInfo -aN|-a0,1,2|-aALL 195 | MegaCli -AdpEventLog -GetEvents {-info -warning -critical -fatal} {-f } -aN|-a0,1,2|-aALL 196 | MegaCli -AdpEventLog -GetSinceShutdown {-info -warning -critical -fatal} {-f } -aN|-a0,1,2|-aALL 197 | MegaCli -AdpEventLog -GetSinceReboot {-info -warning -critical -fatal} {-f } -aN|-a0,1,2|-aALL 198 | MegaCli -AdpEventLog -IncludeDeleted {-info -warning -critical -fatal} {-f } -aN|-a0,1,2|-aALL 199 | MegaCli -AdpEventLog -GetLatest n {-info -warning -critical -fatal} {-f } -aN|-a0,1,2|-aALL 200 | MegaCli -AdpEventLog -GetCCIncon -f -LX|-L0,2,5...|-LALL -aN|-a0,1,2|-aALL 201 | MegaCli -AdpEventLog -Clear -aN|-a0,1,2|-aALL 202 | MegaCli -AdpBbuCmd -aN|-a0,1,2|-aALL 203 | MegaCli -AdpBbuCmd -GetBbuStatus -aN|-a0,1,2|-aALL 204 | MegaCli -AdpBbuCmd -GetBbuCapacityInfo -aN|-a0,1,2|-aALL 205 | MegaCli -AdpBbuCmd -GetBbuDesignInfo -aN|-a0,1,2|-aALL 206 | MegaCli -AdpBbuCmd -GetBbuProperties -aN|-a0,1,2|-aALL 207 | MegaCli -AdpBbuCmd -BbuLearn -aN|-a0,1,2|-aALL 208 | MegaCli -AdpBbuCmd -BbuMfgSleep -aN|-a0,1,2|-aALL 209 | MegaCli -AdpBbuCmd -BbuMfgSeal -aN|-a0,1,2|-aALL 210 | MegaCli -AdpBbuCmd -getBbumodes -aN|-a0,1,2|-aALL 211 | MegaCli -AdpBbuCmd -SetBbuProperties -f -aN|-a0,1,2|-aALL 212 | MegaCli -AdpBbuCmd -ScheduleLearn -Dsbl|-Info|[-STARTTIME DDD hh] -aN|-a0,1,2|-aALL 213 | MegaCli -AdpFacDefSet -aN 214 | MegaCli -AdpFwFlash -f filename [-NoSigChk] [-NoVerChk] [-FWTYPE n] -aN|-a0,1,2|-aALL 215 | MegaCli -AdpM0Flash -f filename 216 | MegaCli -AdpGetConnectorMode -ConnectorN|-Connector0,1|-ConnectorAll -aN|-a0,1,2|-aALL 217 | MegaCli -AdpSetConnectorMode -Internal|-External|-Auto -ConnectorN|-Connector0,1|-ConnectorAll -aN|-a0,1,2|-aALL 218 | MegaCli -PhyErrorCounters -aN|-a0,1,2|-aALL 219 | MegaCli -DirectPdMapping -Enbl|-Dsbl|-Dsply -aN|-a0,1,2|-aALL 220 | MegaCli -ShowEnclList -aN|-a0,1,2|-aALL 221 | MegaCli -ShowVpd -Page N -Encl N -aN|-a0,1,2|-aALL 222 | MegaCli -EnclLocate -Start|-Stop -Encl N -aN|-a0,1,2|-aALL 223 | MegaCli -PdFwDownload [offline][ForceActivate] {[-SataBridge] -PhysDrv[0:1] }|{-EncdevId[devId1]} -f -aN|-a0,1,2|-aALL 224 | MegaCli -SetFacDefault -Encl N -Esm A|B -f -aN|-a0,1,2|-aALL 225 | MegaCli -PDCpyBk -Start -PhysDrv[E0:S0,E1:S1] -aN|-a0,1,2|-aALL 226 | MegaCli -PDCpyBk -Stop|-Suspend|-Resume|-ShowProg|-ProgDsply -PhysDrv[E0:S0] -aN|-a0,1,2|-aALL 227 | MegaCli -PDInstantSecureErase -PhysDrv[E0:S0,E1:S1,...] | [-Force] -aN|-a0,1,2|-aALL 228 | MegaCli -Version -Cli|-Ctrl|-Driver|-Pd -aN|-a0,1,2|-aALL 229 | MegaCli -CfgSpanAdd -rX -array0[E0:S1,E1:S1.....] array1[E0:S1,E1:S1.....] -szxxx -enblPI -aN|-a0,1,2|-aALL 230 | MegaCli -LDMakeSecure -Lx|-L0,1,2,...|-Lall -aN|-a0,1,2|-aALL 231 | MegaCli -DeleteSecurityKey | [-Force] -aN 232 | MegaCli -CreateSecurityKey -Passphrase sssssssssss [-KeyID kkkkkkkkkkk] -aN 233 | MegaCli -CreateSecurityKey useEKMS -aN 234 | MegaCli -ChangeSecurityKey -OldPassphrase sssssssssss | -Passphrase sssssssssss | 235 | [-KeyID kkkkkkkkkkk] -aN 236 | MegaCli -ChangeSecurityKey -Passphrase sssssssssss | 237 | [-KeyID kkkkkkkkkkk] -aN 238 | MegaCli -ChangeSecurityKey useEKMS -oldPassphrase sssssssssss -aN 239 | MegaCli -ChangeSecurityKey -useEKMS -aN 240 | MegaCli -GetKeyID [-PhysDrv[E0:S0]] -aN 241 | MegaCli -SetKeyID -KeyID kkkkkkkkkkk -aN 242 | MegaCli -VerifySecurityKey -Passphrase sssssssssss -aN 243 | 244 | sssssssssss - It must be between eight and thirty-two 245 | characters and contain at least one number, 246 | one lowercase letter, one uppercase 247 | letter and one non-alphanumeric character. 248 | kkkkkkkkkkk - Must be less than 256 characters. 249 | MegaCli -GetPreservedCacheList -aN|-a0,1,2|-aALL 250 | MegaCli -DiscardPreservedCache -Lx|-L0,1,2|-Lall -force -aN|-a0,1,2|-aALL 251 | MegaCli -AdpInfoCompare {-checkFw | -checkID -hex | -checkBatt -val | -checkDimm -val} -aN|-a0,1,2|-aALL 252 | MegaCli -adpFwDump 253 | MegaCli -AdpNameRtn -aN|-a0,1,2|-aALL 254 | 255 | sssssssssss - It must be between eight and thirty-two 256 | characters and contain at least one number, 257 | one lowercase letter, one uppercase 258 | letter and one non-alphanumeric character. 259 | kkkkkkkkkkk - Must be less than 256 characters. 260 | MegaCli -ShowSummary [-f filename] -aN 261 | MegaCli -ELF -GetSafeId -aN|-a0,1,2|-aALL 262 | MegaCli -ELF -ControllerFeatures -aN|-a0,1,2|-aALL 263 | MegaCli -ELF -Applykey key [Preview] -aN|-a0,1,2|-aALL 264 | MegaCli -ELF -TransferToVault -aN|-a0,1,2|-aALL 265 | MegaCli -ELF -DeactivateTrialKey -aN|-a0,1,2|-aALL 266 | MegaCli -ELF -ReHostInfo -aN|-a0,1,2|-aALL 267 | MegaCli -ELF -ReHostComplete -aN|-a0,1,2|-aALL 268 | MegaCli -LDBreakMirror -Lx|-L0,1,2,...|-Lall -aN|-a0,1,2|-aALL 269 | MegaCli -FullStrSeekTest -aN|-a0,1,2|-aALL 270 | MegaCli -LDViewMirror -Lx|-L0,1,2,...|-Lall -aN|-a0,1,2|-aALL 271 | MegaCli -LDJoinMirror -DataSrc [-force] -Lx|-L0,1,2,...|-Lall -aN|-a0,1,2|-aALL 272 | MegaCli -SecureErase 273 | Start[ 274 | Simple| 275 | [Normal [ |ErasePattern ErasePatternA|ErasePattern ErasePatternA ErasePattern ErasePatternB]]| 276 | [Thorough [ |ErasePattern ErasePatternA|ErasePattern ErasePatternA ErasePattern ErasePatternB]]] 277 | | Stop 278 | | ShowProg 279 | | ProgDsply 280 | [-PhysDrv [E0:S0,E1:S1,...] | -Lx|-L0,1,2|-LALL] -aN|-a0,1,2|-aALL 281 | MegaCli -Perfmon {-start -interval } | {stop} | {-getresults -f } -aN 282 | MegaCli -PciSetLinkSpeed Speed -aN|-a0,1,2|-aALL 283 | MegaCli -DpmStat -Dsply {lct | hist | ra | ext } [-physdrv[E0:S0]] -aN|-a0,1,2|-aALL 284 | MegaCli -DpmStat -Clear {lct | hist | ra | ext } -aN|-a0,1,2|-aALL 285 | 286 | Note: The directly connected drives can be specified as [:S] 287 | 288 | Wildcard '?' can be used to specify the enclosure ID for the drive in the 289 | only enclosure without direct connected device or the direct connected 290 | drives with no enclosure in the system. 291 | 292 | Note:[-aALL] option assumes that the parameters specified are valid 293 | for all the Adapters. 294 | 295 | The following options may be given at the end of any command above: 296 | 297 | [-Silent] [-AppLogFile filename] [-NoLog] [-page [N]] 298 | [-] is optional. 299 | N - Number of lines per page. 300 | 301 | Exit Code: 0x00 302 | -------------------------------------------------------------------------------- /MEGAOEM.EXE: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/lrq3000/lsi_sas_hba_crossflash_guide/e458a8e359a582e8a7d046be8ecbc8bf678d7b1b/MEGAOEM.EXE -------------------------------------------------------------------------------- /MEGAOEM.TXT: -------------------------------------------------------------------------------- 1 | DOS/32A warning (9004): mouse initialization failed 2 | 3 | 4 | 5 | MegaOEM Ver 8.00.11 December 21, 2009 6 | 7 | (c)Copyright 2009, LSI Corporation, All Rights Reserved. 8 | 9 | 10 | NOTE: The following options may be given at the end of any command below: 11 | 12 | [-Silent] [-AppLogFile filename] [-NoLog] [-page[N]] 13 | [-] is optional. 14 | N - Number of lines per page. 15 | 16 | MegaOEM -v 17 | MegaOEM -help|-h|? 18 | MegaOEM -adpCount 19 | MegaOEM -AdpAllInfo -aN|-a0,1,2|-aALL 20 | MegaOEM -AdpSetSASA xxxxxxxxxxxxxxxx -aN 21 | MegaOEM -AdpSettings Read | Write -f FileName -aN 22 | -Read - reads INI file, forms MFC_DEFAULT structure and sends it to the FW. 23 | -Write - reads MFC_DEFAULT structure and creates an INI file 24 | MegaOEM -AdpMfgSet -f fileName -aN 25 | MegaOEM -AdpSetVerify -f fileName -aN|-a0,1,2|-aALL 26 | MegaOEM -AdpSetVerifyRaw -f fileName -aN|-a0,1,2|-aALL 27 | MegaOEM -AdpSetSubOEMId XX -aN 28 | XX - sub-OEM ID in Hexadecimal. 29 | MegaOEM -AdpGetSubOEMId -aN 30 | MegaOEM -adpUpdatePersistentPage -f filename - aN 31 | MegaOEM -AdpNVRAM {-Read | -Write -f FileName}|-Clear 32 | [-StartOffset 0xXXXX ] [-EndOffset 0xXXXX] -aN 33 | 34 | Note:[-aALL] option assumes that the parameters specified are valid 35 | for all the Adapters. 36 | 37 | The following options may be given at the end of any command above: 38 | 39 | [-Silent] [-AppLogFile filename] [-NoLog] [-page[N]] 40 | [-] is optional. 41 | N - Number of lines per page. 42 | 43 | Exit Code: 0x00 44 | -------------------------------------------------------------------------------- /MEGAREC.TXT: -------------------------------------------------------------------------------- 1 | DOS/32A warning (9004): mouse initialization failed 2 | 3 | MegaRAID HWR Contoller Recovery tool. Version 01.01-004 February 05, 2010 4 | Copyright (c) 2006-2008 LSI Corp. 5 | Supports 1078 controller and its Successors. 6 | Usage: 7 | MegaRec -help : Display the list of options 8 | MegaRec -adpList : Display identified MR controller(s) 9 | MegaRec -corruptInfo : Display corruption information of controller 10 | MegaRec -m0flash : Flash controller 11 | : where is the controller index 12 | : and is the image file to flash 13 | MegaRec -cleanflash : Erase Flash. Programs if image is Provided. 14 | : where is the controller index 15 | : and is the image file to flash 16 | MegaRec -readspd : Read controller SPD to specified file 17 | : where is the controller index 18 | : and is the specified file name 19 | MegaRec -writespd : Write controller SPD from specified file 20 | : where is the controller index 21 | : and is the specified file name 22 | MegaRec -readsbr : Read controller SBR to specified file 23 | : where is the controller index 24 | : and is the specified file name 25 | MegaRec -writesbr : Write controller SBR from specified file 26 | : where is the controller index 27 | : and is the specified file name 28 | -------------------------------------------------------------------------------- /MEGASAS.LOG: -------------------------------------------------------------------------------- 1 | Fatal error - Command Tool invoked with wrong parameters 2 | Exit Code: 0x01 3 | -------------------------------------------------------------------------------- /MegaCli.exe: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/lrq3000/lsi_sas_hba_crossflash_guide/e458a8e359a582e8a7d046be8ecbc8bf678d7b1b/MegaCli.exe -------------------------------------------------------------------------------- /MegaFl.exe: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/lrq3000/lsi_sas_hba_crossflash_guide/e458a8e359a582e8a7d046be8ecbc8bf678d7b1b/MegaFl.exe -------------------------------------------------------------------------------- /MegaRec.exe: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/lrq3000/lsi_sas_hba_crossflash_guide/e458a8e359a582e8a7d046be8ecbc8bf678d7b1b/MegaRec.exe -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # LSI SAS HBA 6Gbps Crossflash tools and guide in 2023 for LSISAS2008 (Fujitsu D2607, Dell H310) 2 | 3 | This is a guide and toolset to crossflash LSI SAS2 (6Gbps) HBA controllers with newer IT or IR firmwares. Crossflashing is when we use a firmware made for another device from another brand. This is necessary because for a lot of hba controllers the manufacturer stopped firmwares updates (eg, fujitsu), so then it's necessary to use firmwares made for other hba controllers but using the same LSISASXXXX chipset. 4 | 5 | This guide is focused on the LSISAS2008 chipset, but it should be applicable to any LSISAS2 chipset as long as you get the adequate SBR (or make your own) and firmware. 6 | 7 | This repository contains all the files you need to put on a USB drive to crossflash any LSI SAS card (theoretically). 8 | 9 | Also, this repository includes a new file you will not find anywhere else: `sas2haxp20.efi`, which is the hack of Marcan to skip vendor verification (Mfg page 2 verification failure) but applied on sas2flash p20.00.00.00 (there is no sas2flash p20.00.07.00, only the firmware can have this version, not the flashing tool), whereas Marcan's original sas2hax was from sas2flash p19. In my own tests it did not change anything in the crossflashing process but maybe it can help in some cases. 10 | 11 | Note that crossflashing SAS1 (3Gbps) and SAS3 (12 Gbps) HBA cards is outside the scope of this guide, but you can find the official `sas3flash.efi` tool [here](https://www.broadcom.com/support/knowledgebase/1211161501344/flashing-firmware-and-bios-on-lsi-sas-hbas). Note that SAS3 12Gbps hard drives are compatible with SAS2 6Gbps HBA controllers, and inversely SAS2 drives work on SAS3 controllers. But IIRC SAS1 drives and controllers are incompatible with both SAS2 and SAS3. 12 | 13 | ## The step-by-step guide to crossflashing any LSI SAS HBA card 14 | 15 | ### Preparing the crossflashing tools 16 | 1. Before starting, you need to know: 17 | 1. your hba card id and brand (eg, Fujitsu D2607), this will define what SBR to use, 18 | 2. the LSISASXXXX chipset on your HBA card, this will define which firmware crossflash, eg, LSISAS2008. 19 | 3. the LSI HBA controller with the same chipset, eg, LSI 9211 has the LSISAS2008 chipset, 20 | 4. how many ports your HBA controller has: if 4 ports, you need a 4i firmware, otherwise if 8 ports (more common case), you need a 8i firmware. Only 8i firmwares are included in this repository, you need to download other firmwares from Broadcom (ex-LSI and ex-Avago Technologies), Dell, or Supermicro. 21 | 2. Use [Rufus](https://github.com/pbatard/rufus/releases) to format and make a usb flash drive bootable with **FreeDOS**. 22 | 3. Copy content of this repository to the root of your USB drive. For the curious minds, you can see the section "Files sourcing" to know the source of each file. 23 | 24 | At this point, the usb drive is bootable both into freedos and uefi shell v1! You can select from the BIOS boot menu (see the next sections). 25 | 26 | ### HBA controller reprogramming 27 | 28 | From this point on, you do not need to reformat the usb drive. If you lack some firmwares, you can always just copy them, and restart all the steps in this section, but you do not need to prepare the USB drive again (no reformatting!). 29 | 30 | Also, know that LSI HBA controllers, are VERY hard to brick, so feel free to experiment: as long as `megarec.exe` can see your controller, you are fine! 31 | 32 | #### SBR hacking 33 | 34 | 1. Reboot and from the very first screen right away start pressing F12 repetitively for a few minutes until a boot selector appears. If this does not work, reboot and enter BIOS, usually by pressing F2, then it can offer a boot selector on the last tab. 35 | 2. Boot into normal (non uefi) option first, freedos. Note: If you get an error "memory corrupted" with FreeDOS hanging, disconnect sas and sata drives that are bigger than 2TB (even if your current sas firmware supports drives bigger than 2TB! Freedos doesn't!). 36 | 3. `megarec.exe -readsbr 0 origsbr.bin` - note: do this only the first time, to save your original sbr (Serial Boot ROM) in case it's a rare card with special flags necessary to flash it and to detect hard drives slots (such as fujitsu). If you redo the whole flashing process later, skip this to avoid overwriting your original! 37 | * CRITICAL NOTE: make sure to make a backup ASAP outside of the USB drive, not because of the SAS address as can be read in some places (we do not care about it because a random address can be used instead, it’s like a MAC address, you just need it to be unique on your system to avoid conflicts), but to backup the whole SBR as it may contain special flags that are unique to your HBA controller, especially if it’s rarely used by other users online! 38 | 4. Optional but strongly recommended: `megarec.exe -readspd 0 origspd.bin` to save your controller’s original SPD (Serial Presence Detect). 39 | * Also try to backup this file outside of the USB drive ASAP! 40 | 5. Optionally, you can save your HBA controller’s SAS address with `megacli.exe -AdpAllInfo -aAll -ApplogFile AdaptersInfo1.txt` or `sas2flsh.exe -l Adapters.txt -listall`, but any random unique address will be as fine. 41 | 6. `megarec.exe -writesbr 0 sbr-a11.bin` or `sbr-a21.bin` for fujitsu, sbr-empty.bin for others. This sets a new sbr to allow updating to a newer firmware from another brand, we here use hacked sbr mixing data from other brands with a few flags specific to our own original brand (that's why the original sbr can be necessary, in case you need to make a custom sbr yourself as explained here, see below). Note: in FreeDOS, writing filenames and commands in uppercase or lowercase does not matter. 42 | 7. `megarec.exe -cleanflash 0` to clean the firmware (while keeping the sbr). Note: i think this is equivalent to doing `sas2flash.efi -o -e 7` in the uefi shell, but not 100% sure. 43 | 44 | #### Crossflashing the firmware of another hba controller 45 | 46 | 6. Restart machine, tap f12 or use bios to boot into UEFI usb drive option to get UEFI shell. 47 | 7. Type `map -b` to list drives, and identify the Removable Storage one for USB. Type `fsx:` where x is the number, usually `fs0:` to change the working directory to be on the USB drive. 48 | 8. Do NOT do any other command between the sas2flash/sas2hax ones that are advised here, eg, do NOT try to sas2flash -listall in the middle, it may make the rest failbfor some reason as reported by some, sas2flash seems to be finicky and require a precise sequence of actions to work for crossflashing (which is not its primary purpose)! 49 | 9. `sas2haxp20.efi -o -f 2118IT.BIN -b mptsas2.rom` for fujitsu, sas2flash.efi for others. No need for sas2flash -o -e 6 or 7 beforehand but you can try if you messed up before. Use 2118IT.BIN for IT mode, 2118IR.BIN for IR mode (hardware RAID). IT mode is better if you fant to make a software RAID, and in general it's better for files recovery if you ever get a disk corruption (which WILL happen eventually for any hard drive or storage medium). 50 | 10. With fujitsu cards, the whole process should almost complete fine (Firmware download successful, no Mfg page 2 verification failed), but will fail at resetting the adapter with Fault code: 704. This is normal, your card is almost done but not fully yet, you need to reboot and redo the same. It's really necessary to reboot, trying any command in the current shell without rebooting will make the flashing fail and you may have to restart all the steps above. 51 | 11. For fujitsu only: Reboot into UEFI shell again (even though you were in it already), and write the same command again: `sas2haxp20.efi -o -f 2118IT.BIN -b mptsas2.rom` - this time it should complete fully, including the adapter reset! ![img1.jpg](img/img1.jpg) 52 | 12. Optional, only necessary if you plan on having multiple SAS HBA card simultaneously on the same motherboard (think about the future) : `sas2haxp20 -o -sasadd 5000xxxxxxxxxxxx` where x are 12 hexadecimal characters, just to make the card unique. You can restore your old id or just make one up. Eg of a basic one you can make up: `5000123456789abc` 53 | 13. Do `sas2haxp20 -listall` to check, you should see your card is up! In case you already rebooted, you can always check later by rebooting into UEFI shell. 54 | 14. Optional, or necessary for fujitsu if you did not use the right sbr (eg, some drives are not detected): Reboot to freedos (no uefi), and do `megarec -writesbr sbr-a11.bin` or a21 for fujitsu, for others no need to, then reboot one last time. If you already used one of these two sbr at the start and you can see all your drives detected at boot POST, then you do not need to do this step. If you cannot see all the drives detected, then try another sbr, no need to reflash the firmware. You can try as many sbr as you want without habing to reflash your hba card with sas2hax, once the firmware is there, it will stay unless you do megarec -cleanflash! 55 | 15. If you forgot to include the rom, you won't be able to use sas drives as bootable devices (ie, cannot install an OS on them). But you can always flash the bootable rom later, by rebooting into the UEFI shell and type `sas2haxp20 -o -b MPTSAS2.ROM` (without the firmware 2118IT.BIN). 56 | 16. Reboot, and you should see a new POST setup screen for the hba controller and it should show it detects all drives now! ![img2.jpg](img/img2.jpg) 57 | 58 | ### A few helpful rules and tips 59 | 60 | 1. Rule: to execute EXE files such as megarec.exe, use non uefi freedos env. For efi files, boot into tianocore edk2 v1 uefi shell env. If you let the drive boot without pressing f12, it will boot into freedos by default. 61 | 2. Use TAB key to autocomplete commands and filenames, but not flags. Can tap TAB multiple times when the first offered option is not the one you are looking for. 62 | 3. After first flash with sas2hax, will get a Fault 704 error. Don't worry, reboot and retry, it should then work this time. 63 | 4. Sas2hax necessary for fujitsu cards. Can also be used for other cards to bypass mfg branding verification, but still the error may appear, and it is not necessary for dell. Also, sas2hax is based on sas2flash p19, not p20, so it's slightly outdated. Although sas2hax can and is used in the current tutorial to flash a p20.00.07.00 firmware. 64 | 5. In the tuto, dashes are missing, but otherwise it works! writesbr and sasadd https://forums.unraid.net/topic/12114-lsi-controller-fw-updates-irit-modes/page/47/ 65 | 6. If unsure if, a21 or a11, no worries, can change at the end and change sbr multiple times with megarec -writesbr, just do not cleanflash, or you will have to redo sas2hax. 66 | 7. In bios set sata in ide mode, not raid! Then should see AvagoTech POST setup at boot and listing of drives. If installed boot rom. 67 | 8. If you need files such as firmwares (eg supermicro) that are specific to your hba card, just copy them over, you do NOT need to reformat with rufus at any time. This will avoid the risk that you overwrite and lose your original SBR as happened to me! 68 | 9. ALWAYS BACKUP YOUR ORIGINAL SBR IN CASE YOU NEED TO MAKE A CUSTOM SBR! In case you have a common HBA card, it's not that, bad, because you can use the SBR given by others online, but if you have a very specific card with a custom SBR, using others sbr may make the card half functional, such as not showing all drives. In this case, you need to take a sbr from a brand that accepts a newer firmware such as dell, and hack is with HxD (a hexadecimal editor) to apply the special flags from your original sbr, effectively making a hybrid custom sbr, as shown in the tuto, and then flash it on your card using megarec before attempting sas2haxp20 again. https://marcan.st/2016/05/crossflashing-the-fujitsu-d2607/ 69 | 10. To crossflash, need to know chipset version, lsisasxxxx. Why crossflash? To be able to get a fismware of higher version to support drives bigger than 2tb. 70 | 11. Do not worry about mistakes, apart from making sure to keep your original sbr in case you have a very rare hba card that uses different flags, there should be no risk to brick your card, or at least nobody really could. As long as megarec can see and flash your card, you can reconfigure it. Just restart the steps above from the start. 71 | 12. Do NOT use firmware of phase 20 below revision 07, they were buggy as hell and could cost you hard drives data! So either install phase 19 or p20.00.07.00, but nothing between. https://gist.github.com/dreamcat4/f9e16100d68be759ebaa0c9403a55121 72 | 73 | ### Troubleshooting 74 | 75 | 1. If sas2flash.efi fails because "No LSI SAS adapter found" error in uefi shell, then need to remove the branding first! Using megarec.exe in FreeDOS with boot option 4. See tuto: https://www.truenas.com/community/threads/ibm-serveraid-m1015-and-no-lsi-sas-adapters-found.27445/ and https://gist.github.com/dreamcat4/f9e16100d68be759ebaa0c9403a55121 76 | 2. To boot into UEFI: first ensure SecureBoot is disabled and UEFI booting from usb is enabled in BIOS (press F2 at startup), then make a bootable usb uefi drive using rufus and https://github.com/pbatard/UEFI-Shell , then replace the uefi files with tianocore edk2 version 1 (instead of v2) from https://superuser.com/questions/1057446/how-do-i-boot-to-uefi-shell , then copy sas2flash.efi and the IT firmware and bootable rom for the HBA SAS controller card from https://www.truenas.com/community/threads/how-to-flash-lsi-9211-8i-using-efi-shell.50902/ and follow instructions in this last link, to boot into uefi shell from usb drive and then use sas2flash.efi to flath to it mode. 77 | 3. To boot into uefi shell, use tianocore EDK2 Version 1 (not version 2 because incompatible with sas2flash.efi, too old), and can create a Bootable usb drive and newer link to uefi shell tianocore https://superuser.com/questions/1057446/how-do-i-boot-to-uefi-shell 78 | 4. How to flash uefi lsi sas2008 cards using sas2flash.efi and how to boot into uefi shell v1 + select firmware for adequate number of portsk(8i = 8 ports, 4i = 4 ports) + bootrom is necessary if we want to boot from sas drives! https://www.truenas.com/community/threads/how-to-flash-lsi-9211-8i-using-efi-shell.50902/ 79 | 5. Network address as long as you don't have the same addresses connected to the same machine it wont be a problem. + nearly impossible to brick so don't fret https://forums.servethehome.com/index.php?threads/need-help-on-dell-h310.24708/ - eg 500123456789abcd 80 | * Alternative: can generate any set of 12 random hexadecimal characters as the address after 5000, eg, 5000d847203de496 . https://forums.unraid.net/topic/12114-lsi-controller-fw-updates-irit-modes/page/47/ 81 | 6. Need specific sbr-a11.bin or sbr-a21.bin for flashing to work, otherwise need to use Dell firmware and then p7 before p20: https://forums.unraid.net/topic/12114-lsi-controller-fw-updates-irit-modes/page/46/#comment-522038 and https://www.truenas.com/community/threads/fujitsu-9211-8i-d2607-lsisas2008-wont-flash-to-anything.48946/page-2 and https://forums.unraid.net/topic/12114-lsi-controller-fw-updates-irit-modes/?do=findComment&comment=528319 82 | 7. If you have a Supermicro card, use their firmwares, they are very specific 83 | 8. Use mpsutil to show current firmware version https://www.truenas.com/community/threads/lsi-sas2008-hba-aka-9211-8i-q-firmware-upgrade-to-stop-bios-detection-fix-hotswap-not-working.84689/ 84 | 9. If you are stuck at the stage of "no controller detected, need firmware" and you type in the firmware binary, it's not going to work. Even if with sas2flash -o -e 7 it appears to work at first, it will only use the firmware to know how to flash the hba, but then you need to download the firmware on it using sas2flash -o -f 2118IT.bin and then it will again complaint that no card is detected, and then if you again try to input the firmware 2118IT.BIN, it will start and then fail to download the firmware. Normally if you did things right for your hba, this should never happen, the commands should work right away without sas2flash complaining about no controller detected. If that'r the case, it means you need to upload another sbr for your hba using megarec. 85 | 10. If you do not have a UEFI shell or get a strange error with `sas2haxp20.efi`, then try to boot into FreeDOS and use `sas2flsh.exe` with the same arguments you would with `sas2flash.efi` or `sas2haxp20.efi`, it should work. If you get a "Not PAL" error, then you need for sure to boot into the UEFI shell. 86 | 11. For some cards, you may need the [SAS2 BSD HII Driver ROMs](https://docs.broadcom.com/docs-and-downloads/host-bus-adapters/host-bus-adapters-common-files/sas_sata_6g_p20/UEFI_BSD_P20.zip). 87 | 12. If the whole procedure did not work at all, you can try the old fashioned way before sas2hax, especially useful if you cannot use sas2hax (card is not UEFI so you need to use sas2flsh.exe which is NOT patched): 88 | 1. Re-do the SBR Hacking section above as before. 89 | 2. Crossflash using `sas2flash.efi -o -f DELL_6GBPSAS.FW -b DELL_MPTSAS2.ROM` (replace sas2flash.efi with sas2flsh.exe if you do not have a UEFI compatible HBA controller). This will force the controller to think it is from the DELL vendor. This works especially well for controllers that were already DELL or IBM. If this does not work, try the next step anyway. 90 | 3. Reboot! 91 | 4. Crossflash with an older firmware, usually the P7 is advised: `sas2flash.efi -o -f 2118IT_P7.bin -b MPTSAS2_P7.ROM` . Hopefully this step worked, you downgraded your HBA controller to an older firmware, which will allow to bypass the "Mfg page 2 verification" vendor lock. 92 | 5. Reboot. 93 | 6. Crossflash the P20 firmware as in the normal steps in the Crossflash section: `sas2haxp20.efi -o -f 2118IT.BIN -b mptsas2.rom` 94 | 7. If this works, then all good! You can do the rest of the commands in the Crossflash section, and your card is ready! 95 | 96 | ## References 97 | 98 | Here are several resources that I read and that helped me learn how to crossflash, you may be interestet in reading them for more information or background, although no other guide covers as many lsi cards as here. 99 | 100 | If a link is dead, try to use the Wayback Machine, I tried to backup all the relevant links there, including executables wherever possible. 101 | 102 | 1. https://gist.github.com/dreamcat4/f9e16100d68be759ebaa0c9403a55121 103 | 2. P20.00.07.00 latest firmware (also mention that phase = version) https://docs.broadcom.com/docs/12350530 104 | 3. https://www.broadcom.com/support/knowledgebase/1211161501344/flashing-firmware-and-bios-on-lsi-sas-hbas 105 | 4. https://marcan.st/2016/05/crossflashing-the-fujitsu-d2607/ 106 | 5. https://forums.unraid.net/topic/12114-lsi-controller-fw-updates-irit-modes/page/46/#comment-522038 107 | 6. The instructions for Fujitsu D2607 were heavily inspired by FingerlessGloves’ guide (and I tested myself several variants to check that yes indeed the steps i retained are necessary): https://forums.unraid.net/topic/12114-lsi-controller-fw-updates-irit-modes/?do=findComment&comment=528319 108 | 109 | ## Files sourcing 110 | 111 | The files in this repository were sourced from the following sources: 112 | 113 | 1. [D2607.zip](https://forums.unraid.net/topic/12114-lsi-controller-fw-updates-irit-modes/page/46/#comment-522038) ([direct download](https://mega.nz/#!T8cSRSwL!UUo72yqq-ov2ulKgaznP8vgVeE_zBMdpBQ7ZB2LvfO8)) by FingerlessGloves, which includes the latest [phase 20 v20.00.07.00 firmware for the LSI 9211-8i HBA controller](https://docs.broadcom.com/docs/12350530) as well as megarec.exe (which itself likely comes from the [m1015.zip file shared here](https://www.truenas.com/community/threads/where-is-the-megarec-utility-to-crossflash-m1015-to-it-mode.25130/)). 114 | 2. [Toolset_PercH310_H200_2_LSI9211_P20.00.07.00_efimod.zip](https://forums.unraid.net/topic/12114-lsi-controller-fw-updates-irit-modes/?do=findComment&comment=527688) ([direct download](https://www.mediafire.com/?9cbklh4i1002n23)) by Fireball3, with all the tools and firmwares necessary to crossflash Dell H310. 115 | 3. The UEFI shell files are from the [Tianocore EDK2](https://github.com/tianocore/edk2) project, which is an open-source implementation of an UEFI shell. I took the [EDK2 v1 binaries](https://github.com/tianocore/edk2/tree/UDK2018/EdkShellBinPkg/FullShell), as otherwise sas2flash fails in UEFI v2 shells. 116 | 4. The UEFI files were organized according to the [ISO](https://github.com/pbatard/UEFI-Shell) provided by pbatard, the same author as Rufus, but his ISO uses EDK2 v2, whereas we need v1. 117 | 4. The [lsirec](https://github.com/marcan/lsirec) tool, to be used under Linux, is from Marcan, the same author who made `sas2hax.efi`. 118 | 5. `sas2haxp20.efi` is my own implementation of [Marcan’s hack of sas2flash.efi into sas2hax.efi](https://marcan.st/2016/05/crossflashing-the-fujitsu-d2607/), but applied on sas2flash.efi p20 instead of p19 as done by Marcan. Hence, this file is an exclusivity of this repository. 119 | * `sas2hax.efi` is the [original hack by Marcan](https://marcan.st/2016/05/crossflashing-the-fujitsu-d2607/) to bypass the vendors verification (Mfg page 2 verification failure). 120 | 6. `sas2flash.efi` is the original p20 tool from [Broadcom/LSI](https://www.broadcom.com/support/knowledgebase/1211161501344/flashing-firmware-and-bios-on-lsi-sas-hbas). 121 | 122 | ## Alternative projects 123 | 124 | * [Flash-it](https://github.com/confusingboat/flash-it) is an automated script to flash DELL and IBM cards using lsirec instead of the hacked sas2flash. 125 | 126 | ## Credits and license 127 | 128 | This guide (README.md) is under Creative Commons CC-BY-SA 4.0, written by Stephen Karl Larroque in 2023. 129 | 130 | I claim no credit for all the other files, please see their respective licenses. I believe this package fits under Fair Use for preservation purposes as the vendors do not provide support for these controllers anymore. 131 | -------------------------------------------------------------------------------- /SBR-A11.bin: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/lrq3000/lsi_sas_hba_crossflash_guide/e458a8e359a582e8a7d046be8ecbc8bf678d7b1b/SBR-A11.bin -------------------------------------------------------------------------------- /SBR-A21.bin: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/lrq3000/lsi_sas_hba_crossflash_guide/e458a8e359a582e8a7d046be8ecbc8bf678d7b1b/SBR-A21.bin -------------------------------------------------------------------------------- /XGREP.COM: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/lrq3000/lsi_sas_hba_crossflash_guide/e458a8e359a582e8a7d046be8ecbc8bf678d7b1b/XGREP.COM -------------------------------------------------------------------------------- /docs/README_9211_8i_Package_P20_IR_IT_FW_BIOS_for_MSDOS_Windows.txt: -------------------------------------------------------------------------------- 1 | ************************************************************************************************************************ 2 | Package for P20 Firmware BIOS Upgrade on MSDOS & Windows 3 | ************************************************************************************************************************ 4 | LSI Host Bus Adapter(HBA) - LSI SAS 9211-8i 5 | 6 | Package Contents- 7 | 8 | Readme first note : README_9211_8i_Package_P20_IR_IT_Firmware_BIOS_for_MSDOS_Windows.txt 9 | 10 | Installer(SAS2FLSH) : \sas2flash_dos_rel\sas2flsh Version no: 20.00.00.00 Release date: 18-SEP-14 11 | Installer(SAS2FLASH) : \sas2flash_win_x86_rel\sas2flash Version no: 20.00.00.00 Release date: 18-SEP-14 12 | Installer(SAS2FLASH) : \sas2flash_win_x64_rel\sas2flash Version no: 20.00.00.00 Release date: 18-SEP-14 13 | Installer(SAS2FLASH) : \sas2flash_win_ia64_rel\sas2flash Version no: 20.00.00.00 Release date: 18-SEP-14 14 | 15 | Reference Guide : SAS2Flash_ReferenceGuide.pdf Version no: 2.1 Release date: JUNE-11 16 | 17 | Firmware : \firmware\HBA_9211_8i_IR\2118ir.bin Version no: 20.00.07.00 Release date: 11-FEB-16 18 | 19 | Firmware : \firmware\HBA_9211_8i_IT\2118it.bin Version no: 20.00.07.00 Release date: 11-FEB-16 20 | 21 | BIOS : \sasbios_rel\mptsas2.rom Version no: 7.39.02.00 Release date: 03-AUG-15 22 | Readme for BIOS : \sasbios_rel\mptbios.txt Version no: NA Release date: NA 23 | 24 | 25 | ---------------------------------------------------------------------------------------------------------------------------- 26 | 27 | -------------------------------------------------------------------------------- /docs/README_Installer_P20_UEFI.txt: -------------------------------------------------------------------------------- 1 | *************************************************************************************************************************** 2 | 3 | Installer for EFI 4 | 5 | LSI Corporation SAS2FLASH Release 6 | 7 | *************************************************************************************************************************** 8 | ============================= 9 | Contents- 10 | ============================= 11 | Installer fOr EFI (SAS2FLASH) : \sas2flash_efi_ebc_rel\sas2flash.efi Version:20.00.00.00 Release Date:18-SEP-14 12 | README_FOR_Installer_P20_UEFI.txt 13 | SAS2Flash_ReferenceGuide.pdf 14 | SAS2FLASH_Phase20.0-20.00.00.00.pdf 15 | 16 | 17 | Installation: 18 | ============= 19 | 20 | SAS2FLASH is stand-alone binary and can be executed from any location on a file system. For more details on installer please refer to the SAS2FLASH User manual included in this package. 21 | 22 | 23 | 24 | 25 | 26 | -------------------------------------------------------------------------------- /docs/SAS2BIOS_Phase20.0-7.39.02.00.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/lrq3000/lsi_sas_hba_crossflash_guide/e458a8e359a582e8a7d046be8ecbc8bf678d7b1b/docs/SAS2BIOS_Phase20.0-7.39.02.00.pdf -------------------------------------------------------------------------------- /docs/SAS2FLASH_Phase20.0-20.00.00.00.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/lrq3000/lsi_sas_hba_crossflash_guide/e458a8e359a582e8a7d046be8ecbc8bf678d7b1b/docs/SAS2FLASH_Phase20.0-20.00.00.00.pdf -------------------------------------------------------------------------------- /docs/SAS2FW_Phase20-20.00.07.00 Release Notes.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/lrq3000/lsi_sas_hba_crossflash_guide/e458a8e359a582e8a7d046be8ecbc8bf678d7b1b/docs/SAS2FW_Phase20-20.00.07.00 Release Notes.pdf -------------------------------------------------------------------------------- /docs/SAS2Flash_ReferenceGuide.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/lrq3000/lsi_sas_hba_crossflash_guide/e458a8e359a582e8a7d046be8ecbc8bf678d7b1b/docs/SAS2Flash_ReferenceGuide.pdf -------------------------------------------------------------------------------- /efi/boot/bootaa64.efi: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/lrq3000/lsi_sas_hba_crossflash_guide/e458a8e359a582e8a7d046be8ecbc8bf678d7b1b/efi/boot/bootaa64.efi -------------------------------------------------------------------------------- /efi/boot/bootarm.efi: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/lrq3000/lsi_sas_hba_crossflash_guide/e458a8e359a582e8a7d046be8ecbc8bf678d7b1b/efi/boot/bootarm.efi -------------------------------------------------------------------------------- /efi/boot/bootia32.efi: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/lrq3000/lsi_sas_hba_crossflash_guide/e458a8e359a582e8a7d046be8ecbc8bf678d7b1b/efi/boot/bootia32.efi -------------------------------------------------------------------------------- /efi/boot/bootia64.efi: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/lrq3000/lsi_sas_hba_crossflash_guide/e458a8e359a582e8a7d046be8ecbc8bf678d7b1b/efi/boot/bootia64.efi -------------------------------------------------------------------------------- /efi/boot/bootx64.efi: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/lrq3000/lsi_sas_hba_crossflash_guide/e458a8e359a582e8a7d046be8ecbc8bf678d7b1b/efi/boot/bootx64.efi -------------------------------------------------------------------------------- /img/img1.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/lrq3000/lsi_sas_hba_crossflash_guide/e458a8e359a582e8a7d046be8ecbc8bf678d7b1b/img/img1.jpg -------------------------------------------------------------------------------- /img/img2.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/lrq3000/lsi_sas_hba_crossflash_guide/e458a8e359a582e8a7d046be8ecbc8bf678d7b1b/img/img2.jpg -------------------------------------------------------------------------------- /mptbios.txt: -------------------------------------------------------------------------------- 1 | **************************************************************************** 2 | MPTBIOS.TXT 3 | ***************************************************************************** 4 | 5 | This file presents general information about the Avago Technologies SAS BIOS and 6 | Configuration Utility. 7 | 8 | Copyright 2000-2015 Avago Technologies. All rights reserved. 9 | 10 | This text file is divided into these sections: 11 | 12 | SAS BIOS 13 | Features 14 | Boot Initialization with SCSI BIOS Boot Specification 15 | CD-ROM Boot Initialization 16 | Starting the SAS BIOS Configuration Utility 17 | Using the Configuration Utility 18 | Adapter List 19 | Global Properties 20 | Adapter Properties 21 | SAS Topology 22 | Device Properties 23 | Format/Verify Screens 24 | SAS Topology - More Keys 25 | Advanced Adapter Properties 26 | Advanced Device Properties 27 | Adapter Timing Properties 28 | Integrated RAID Configuration and Management Screens 29 | Exiting the SAS Configuration Utility 30 | 31 | 32 | * * * * * * * * * * * * SAS BIOS * * * * * * * * * * * 33 | 34 | A SAS BIOS is the bootable ROM code that manages SAS hardware resources. It is 35 | specific to a family of Avago Technologies SAS controllers or processors. 36 | A SAS BIOS integrates with a standard system BIOS, extending the standard 37 | disk service routine provided through INT13h. 38 | 39 | During the boot time initialization, the SAS BIOS determines if there are other 40 | hard disks, such as an IDE drive, already installed by the system BIOS. If 41 | there are, the SAS BIOS maps any SAS or SATA drives it finds behind the drive(s) 42 | already installed. Otherwise, the SAS BIOS installs drives starting with the 43 | system boot drive. In this case, the system boots from a drive controlled by 44 | the SAS BIOS. The Avago Technologies SAS BIOS supports the 45 | BIOS Boot Specification (BBS). 46 | 47 | The next section, "Boot Initialization with BIOS Boot Specification (BBS)," 48 | discusses selecting boot and drive order. 49 | 50 | 51 | * * * * * * * * * * * Features * * * * * * * * * * * * 52 | 53 | The SAS BIOS features include: 54 | 55 | o Configuration for up to 16 adapters-any 4 can be chosen for 56 | INT13 (bottom) support 57 | 58 | o Support for Message Passing Technology 59 | 60 | o Support for the following family of second-generation SAS Controllers: 61 | o SAS2004 62 | o SAS2008 63 | o SAS2108 64 | o SAS2116 65 | o SAS2208 66 | o SAS2308 67 | 68 | o Support for SAS and SATA devices 69 | 70 | o Support for Integrated RAID initialization (with proper firmware) 71 | 72 | 73 | * * * * Boot Initialization with BIOS Boot Specification (BBS) * * * 74 | 75 | The SAS BIOS provides support for the BIOS Boot Specification (BBS) which 76 | allows you to choose which device to boot from by selecting the priority. 77 | 78 | To use this feature, the system BIOS must also be compatible with the BBS. If 79 | your system supports the BBS, then you will use the system BIOS setup menu to 80 | select the boot and drive order. In the system BIOS setup, the Boot Connection 81 | Devices menu appears with a list of available boot options. Use that menu to 82 | select the device and rearrange the order. Then exit to continue the boot 83 | process. 84 | 85 | 86 | * * * * * * * * * CD-ROM Boot Initialization * * * * * * * * * 87 | 88 | The SAS BIOS supports boot initialization from a CD-ROM drive. 89 | The five types of supported emulation are: 90 | 91 | o No emulation disk 92 | o Floppy 1.2 Mbyte emulation disk 93 | o Floppy 1.44 Mbyte emulation disk 94 | o Floppy 2.88 Mbyte emulation disk 95 | o Hard disk emulation 96 | 97 | The type of emulation assigns the drive letter for the CD-ROM. For example, 98 | if a 1.44 Mbyte floppy emulation CD was loaded, then the CD-ROM drive would 99 | become the designated A: drive, and the existing floppy would become drive B:. 100 | 101 | 102 | * * * * * * Starting the SAS BIOS Configuration Utility * * * * * * 103 | 104 | If you have SAS BIOS version 7.XX, and it includes the SAS BIOS Configuration 105 | Utility, you can change the default configuration of your SAS host adapters. 106 | You may decide to alter these default values if there is a conflict between 107 | device settings or if you need to optimize system performance. 108 | 109 | You can see the version number of the SAS BIOS in a banner displayed on your 110 | computer monitor during boot. If the utility is available, this message 111 | also appears on your monitor: 112 | 113 | Press Ctrl-C to start Avago Technologies Configuration Utility... 114 | 115 | This message remains on your screen for about five seconds, giving you time 116 | to start the utility. If you decide to press "Ctrl-C", the message changes 117 | to: 118 | 119 | Please wait, invoking SAS Configuration Utility... 120 | 121 | After a brief pause, your computer monitor displays the Main Menu of the 122 | SAS BIOS Configuration Utility. 123 | 124 | 125 | These messages may appear during the boot process: 126 | 127 | 1. "Adapter removed from boot order!" appears when an adapter is removed from 128 | the system or relocated behind a PCI bridge. 129 | 130 | 2. "Adapter configuration may have changed, reconfiguration is suggested!" 131 | appears if none of the information in the NVRAM is valid. 132 | 133 | 3. "Updating Adapter List!" appears when less than four adapters are in the 134 | boot order and more adapters exist than are shown. 135 | 136 | 4. "Preferred boot device is missing, reconfiguration is suggested!" appears 137 | if the user has selected a preferred or alternate boot device and is not 138 | detected during BIOS initialization. 139 | 140 | IMPORTANT: The SAS BIOS Configuration Utility is a powerful tool. If, while 141 | using it, you somehow disable all of your controllers, pressing 142 | Ctrl-A (or Ctrl-E on version 5.00 or later) after memory 143 | initialization during reboot allows you to re-enable and 144 | reconfigure. 145 | 146 | Note: Not all devices detected by the Configuration Utility can be 147 | controlled by the BIOS. Devices such as tape drives and scanners 148 | require that a device driver specific to that peripheral be 149 | loaded. The SAS BIOS Configuration Utility does allow parameters 150 | to be modified for these devices. 151 | 152 | 153 | 154 | ************************************************************************** 155 | * * * * * * * Using the Configuration Utility * * * * * * * * 156 | ************************************************************************** 157 | 158 | 159 | * * * Screen Format * * * 160 | 161 | All SAS BIOS Configuration Utility screens are partitioned into fixed areas. 162 | Here is an example: 163 | 164 | 165 | X 1 78 166 | Y ---------------------------------------- 167 | 1 | Header Area | 168 | ---------------------------------------- 169 | 1 | Menu Area | 170 | ---------------------------------------- 171 | 2 | | 172 | | | 173 | ... Main Area ... 174 | | | 175 | 21 | | 176 | ---------------------------------------- 177 | 22 | | 178 | | Footer Area | 179 | 23 | | 180 | ---------------------------------------- 181 | 182 | Header Area 183 | 184 | This area provides static information text, which is typically 185 | the product title and version. 186 | 187 | Menu Area 188 | 189 | This area provides the current Screen title and Controller 190 | information when on screens other than Adapter List. 191 | 192 | Main Area 193 | 194 | This is the main area for presenting data. This area has a cursor for 195 | item selection, horizontal scrolling, and vertical scrolling. The 196 | horizontal and vertical scroll bars appear here if needed. 197 | 198 | Footer Area 199 | 200 | This area provides general help information text. 201 | 202 | * * * User Input * * * 203 | 204 | Throughout the Configuration Utility there are general key inputs that apply 205 | on all screens: 206 | 207 | F1 = Help 208 | Context sensitive help for the cursor-resident field. 209 | 210 | Arrow Keys = Select Item 211 | Home/End = Select Item 212 | Up, down, left, right movement to position the cursor. 213 | 214 | +/- = Change Item 215 | Items with values in [] brackets are modifiable. 216 | Numeric keypad '+' and numeric keypad '-', update a modifiable field to 217 | its next relative value. 218 | 219 | Esc = Abort/Exit 220 | 221 | Escape aborts the current context operation and/or exits the current 222 | screen. User confirmation is solicited as required if changes have been 223 | made by user. 224 | 225 | Enter = Execute 226 | 227 | Executable items are indicated by highlighted text and a different 228 | background color. Press Enter to execute the field's associated function. 229 | 230 | **Throughout the GUI, selections that are not currently permissible are 231 | grayed out. 232 | 233 | Behavior of executable items will vary throughout the Configuration 234 | Utility. Screen details below include info on their executable items. 235 | 236 | 237 | * * * * * * * * * * * Adapter List * * * * * * * * * * * * 238 | 239 | When you invoke the SAS BIOS Configuration Utility, the Adapter List appears. 240 | This screen displays a scrolling list of up to 16 Avago Technologies SAS adapters 241 | in the system and information about each of them. 242 | 243 | Use the arrow keys to select an adapter, then press Enter to view and modify 244 | the selected adapter's properties (and to gain access to the further screens). 245 | After selecting an adapter and pressing Enter, the adapter's devices are 246 | scanned and the Adapter Properties screen appears. An example is shown below. 247 | 248 | The Adapter Boot Order is modifiable on this screen by using the -,+,Ins, and 249 | Del keys while on the Boot Order field. Use Ins/Del to add or remove an adapter 250 | from the Boot Order. Use the -/+ keys to modify an adapter's position in the 251 | boot order. When changes have been made to the boot order, the user will be 252 | prompted to save changes before exiting the screen. 253 | 254 | From the Adapter List, the user may also access the Global Properties screen by 255 | pressing Alt+N. 256 | 257 | Global Properties allows changes to global scope settings. Refer to the section 258 | on Global Properties below. 259 | 260 | |------------------------------------------------------------------------------| 261 | | Avago Technologies Config Utility v7.38.01.00 (2014.07.06) | 262 | | Adapter List Global Properties | 263 | | | 264 | | Adapter PCI PCI PCI PCI FW Revision Status Boot | 265 | | Bus Dev Fnc Slot Order | 266 | | SAS2008 01 00 00 04 2.00.50.00-IR Enabled 0 | 267 | | SAS2008 01 00 00 03 2.250.02.00-IR Enabled 1 | 268 | | SAS2116-1 02 00 00 02 1.250.51.00-IR Enabled | 269 | | SAS2116-1 02 00 00 02 1.250.50.00-IT Disabled | 270 | | | 271 | | | 272 | | | 273 | | | 274 | | | 275 | | | 276 | | Esc = Exit Menu F1/Shift+1 = Help | 277 | | Alt+N = Global Properties -/+ = Alter Boot Order Ins/Del = Alter Boot List | 278 | |------------------------------------------------------------------------------| 279 | 280 | 281 | * * * Field Descriptions * * * 282 | 283 | Adapter 284 | 285 | Indicates the specific Avago Technologies SAS controller type. 286 | 287 | PCI Bus 288 | 289 | Indicates the PCI Bus number (range 0x00 - 0xFF, 0 - 255 decimal) 290 | assigned by the system BIOS to an adapter. 291 | 292 | PCI Dev 293 | 294 | Indicates the PCI Device (range 0x00 - 0x1F, 0 - 31 decimal) assigned 295 | by the system BIOS to an adapter. 296 | 297 | PCI Fnc 298 | 299 | Indicates the PCI Function (range 0x00 - 0x7, 0 - 7 decimal) assigned 300 | by the system BIOS to an adapter. 301 | 302 | PCI Slot 303 | 304 | Indicates the PCI Slot the controller is located in. 305 | 306 | FW Revision 307 | 308 | Displays the MPT Firmware version and type (IR or IT) 309 | 310 | Status 311 | 312 | Indicates whether an adapter is eligible for Avago Technologies software control 313 | or is reserved for control by non-Avago software 314 | (Enabled, Disabled, Error). 315 | 316 | Enabled indicates the BIOS is either currently controlling the adapter 317 | or will attempt to control the adapter upon reload. 318 | 319 | Disabled indicates the BIOS is either not controlling the adapter or 320 | will discontinue control of the adapter upon reload. 321 | 322 | Whether Enabled or Disabled, the user will still be able to view and 323 | modify settings for the adapter. The Boot Support setting in the Adapter 324 | Properties menu can be used to change the status of this setting. The 325 | BIOS must be reloaded (e.g., system rebooted) in order for a new Boot 326 | Support setting to take effect. 327 | 328 | Error indicates that the BIOS encountered a problem with the adapter. 329 | Viewing and modifying settings for the adapter is allowed but the 330 | information and functionality available may be limited. 331 | 332 | Boot Order 333 | 334 | The Boot Order specifies the order in which adapters will boot when 335 | more than one adapter is in a system. Up to four adapters in a system 336 | may be selected as bootable. 337 | 338 | To add an adapter to the boot list, press Insert while on the Boot Order 339 | field of the adapter. To remove an adapter from the boot list, press Delete 340 | while on the desired adapter's Boot Order field. The -/+ keys can be used 341 | to change the adapter's position in the Boot Order. 342 | 343 | 344 | 345 | * * * * * * * * * * Global Properties * * * * * * * * * * 346 | 347 | The Global Properties screen is accessible by pressing Alt+N while on the 348 | Adapter List Screen. To return to Adapter List from Global Properties Alt+N can 349 | again be pressed. 350 | 351 | Here is an example of the Global Properties Menu: 352 | 353 | |------------------------------------------------------------------------------| 354 | | Avago Technologies Config Utility v7.38.01.00 (2014.07.06) | 355 | | Adapter List Global Properties | 356 | | | 357 | | | 358 | | | 359 | | Pause When Boot Alert Displayed [Yes] | 360 | | Boot Information Display Mode [Display adapters only] | 361 | | Support Interrupt [Hook interrupt, the Default] | 362 | | | 363 | | Restore Defaults | 364 | | | 365 | | | 366 | | | 367 | | | 368 | | | 369 | | Esc = Exit Menu F1/Shift+1 = Help | 370 | | Alt+N = Adapter List -/+ = Change Item | 371 | |------------------------------------------------------------------------------| 372 | 373 | 374 | * * * Field Descriptions * * * 375 | 376 | Pause When Boot Alert Displayed 377 | 378 | This option specifies whether to pause for user acknowledgement after 379 | displaying an alert message during boot. The Boot Alert setting can be 380 | either No or Yes. 381 | 382 | To continue after displaying a message, specify No. 383 | To wait for any key after displaying a message, specify Yes. 384 | 385 | Boot Information Display Mode 386 | 387 | This option specifies the information display mode of the BIOS during 388 | boot. It controls how much information about adapters and devices 389 | are displayed during boot. Possible values are: 390 | 391 | Display adapters only 392 | Display adapters and all devices 393 | Display minimal information 394 | Display adapters and installed devices 395 | 396 | Support Interrupt 397 | 398 | This option allows the ability to prevent a hook on INT40, if required. 399 | Possible values are: 400 | 401 | Hook interrupt, the Default. 402 | Bypass interrupt hook. 403 | 404 | 405 | 406 | Press Enter to obtain default settings. 407 | 408 | 409 | 410 | * * * * * * * * * Adapter Properties * * * * * * * * * * 411 | 412 | The Adapter Properties Screen allows you to view and modify adapter settings. 413 | It also provides access to all other screens. Here is an example of the 414 | Adapter Properties screen: 415 | 416 | |------------------------------------------------------------------------------| 417 | | Avago Technologies Config Utility v7.38.01.00 (2014.07.06) | 418 | | Adapter Properties -- SAS2008 | 419 | | | 420 | | Adapter SAS2008 | 421 | | PCI Slot 03 | 422 | | PCI Address(Bus/Dev) 03:00 | 423 | | MPT Firmware Revision 01.250.51.00-IR | 424 | | SAS Address 500605B0:0000C580 | 425 | | NVDATA Version 00.09 | 426 | | Status Enabled | 427 | | Boot Order 1 | 428 | | Boot Support [Enabled BIOS & OS] | 429 | | | 430 | | | 431 | | RAID Properties | 432 | | | 433 | | SAS Topology | 434 | | | 435 | | Advanced Adapter Properties | 436 | | | 437 | | | 438 | | | 439 | | | 440 | | Esc = Exit Menu F1/Shift+1 = Help | 441 | | Enter = Select Item -/+ = Change Item | 442 | |------------------------------------------------------------------------------| 443 | 444 | 445 | * * * Field Descriptions * * * 446 | 447 | Adapter 448 | 449 | Indicates the specific Avago Technologies SAS controller type. 450 | 451 | PCI Slot 452 | 453 | Indicates the PCI Slot the controller is located in. 454 | 455 | PCI Address 456 | 457 | Displays the PCI Address assigned by the system BIOS to the adapter. 458 | Bus value has range 0x00 - 0xFF, 0 - 255 decimal. 459 | Device value has range 0x00 - 0x1F, 0 - 31 decimal. 460 | 461 | FW Revision 462 | 463 | Displays the MPT Firmware version and type (IR or IT) 464 | 465 | SAS Address 466 | 467 | Displays the SAS Address assigned to this adapter. 468 | 469 | Status 470 | 471 | Indicates whether an adapter is eligible for Avago Technologies software control 472 | or is reserved for control by non-Avago software (Enabled, 473 | Disabled, Error). 474 | 475 | Enabled indicates the BIOS is either currently controlling the adapter 476 | or will attempt to control the adapter upon reload. 477 | 478 | Disabled indicates the BIOS is either not controlling the adapter or 479 | will discontinue control of the adapter upon reload. 480 | 481 | Whether Enabled or Disabled, the user will still be able to view and 482 | modify settings for the adapter. The Boot Support setting in the Adapter 483 | Properties menu can be used to change the status of this setting. The 484 | BIOS must be reloaded (e.g., system rebooted) in order for a new Boot 485 | Support setting to take effect. 486 | 487 | Error indicates that the BIOS encountered a problem with the adapter. 488 | Viewing and modifying settings for the adapter is allowed but the 489 | information and functionality available may be limited. The possible 490 | error conditions are: 491 | Device Initialization Failed: Device initialization has failed. May be due to invalid IO Port address. 492 | Issuing IOC Facts failed: This error may be due to FW fault state. 493 | Bus Master Error: This error may be due to bus mastering bit was not set 494 | PCI Chip Malfunctioning: If the adapter was not found or was not properly functioning. 495 | Discovery Error: The Phy discovery error displayed in D_ERR 0xXXXXXXXX on Phy X. 496 | 497 | Boot Order 498 | 499 | The Boot Order specifies the order in which adapters will boot when 500 | more than one adapter is in a system. Up to four of the total 501 | adapters in a system may be selected as bootable. 502 | 503 | Boot Support 504 | 505 | Specifies whether an adapter is eligible for Avago software control 506 | or is reserved for control by non-Avago software 507 | (Enabled BIOS & OS, Enabled BIOS Only, Enabled OS Only, Disabled, 508 | default: Enabled BIOS & OS). 509 | If Enabled BIOS & OS, then both the bios and OS driver will control the 510 | adapter. 511 | If Enabled BIOS Only, then the adapter will be controlled by the bios, 512 | but OS drivers will not control it. This setting may not be supported by 513 | all OS drivers, for example there is no means to disable an adapter in a 514 | Windows driver. 515 | If Enabled OS Only, then the bios will not control the adapter but the 516 | OS driver will control the adapter. 517 | If Disabled, then the bios will not control the adapter when loaded. 518 | However, the adapter will still be visible through the Configuration 519 | Protocol. 520 | Changes to this setting will be reflected in the Status field on the 521 | main Adapter List menu. The new setting will not take effect until the 522 | bios is reloaded (e.g., system rebooted). 523 | 524 | 525 | * * * * * * * * * * SAS Topology * * * * * * * * * * 526 | 527 | The SAS Topology screen presents a view of the adapter's SAS hierarchy. This 528 | screen also provides other user functionality as noted below. 529 | 530 | The following objects along with their significant properties are shown: 531 | Adapter 532 | PHYs 533 | Attached Devices 534 | Expanders/Enclosures. 535 | 536 | The SAS Topology is expanded for display as follows: 537 | Select an expander/enclosure and press Enter to expand the Expander or 538 | Enclosure and display all its Phys/Devices/Bays. 539 | 540 | Hit Enter again to collapse the expander/Enclosure. 541 | 542 | 543 | While cursor is on the Device Identifier: 544 | 545 | -Hit Alt+D access device-specific screen. 546 | -Hit Alt+M to display additional options. 547 | -Hit Enter while on expander/enclosure to expand/collapse the display 548 | -Hit Enter while on enclosure/expander device to activate locate LED. 549 | 550 | |------------------------------------------------------------------------------| 551 | | Avago Technologies Config Utility v7.38.01.00 (2014.07.06) | 552 | | SAS Topology -- SAS2008 | 553 | | Device Identifier Device | 554 | | SAS2008(03:03) Info | 555 | | |-Controller Direct Attach Devices Controller | 556 | | |-PHY 0 SEAGATE ST9146803SS B241 SAS | 557 | | |-PHY 3 ATA SAMSUNG MCBQE32G 5006 SATA-SSD | 558 | | |-Expander LSILOGICSASx12 A.0 Expander | 559 | | |-PHY 3 ATA Maxtor 6y080M0 1EW0 SATA | 560 | | |-PHY 4 SEAGATE ST9146803SS B241 SAS | 561 | | |-PHY 7 RAID Physical Disk SATA | 562 | | |-PHY 9 RAID Physical Disk SATA | 563 | | |-RAID0 VOL LSI Logical Volume 3000 | 564 | | |-PHY 9 ATA Maxtor 6y080M0 1EW0 RAID | 565 | | |-PHY 7 ATA Maxtor 6y080M0 1EW0 RAID | 566 | | | 567 | | | 568 | | | 569 | | | 570 | | Esc = Exit F1/Shift+1 = Help | 571 | | Alt+D = Device Properties Alt+M = More Keys | 572 | |------------------------------------------------------------------------------| 573 | 574 | Scrolling Cursor once to the right will display further information: 575 | 576 | |------------------------------------------------------------------------------| 577 | | Avago Technologies Config Utility v7.38.01.00 (2014.07.06) | 578 | | SAS Topology -- SAS2008 | 579 | | Device Identifier Negotiated Link | 580 | | SAS2008(03:03) Speed (Gbps) | 581 | | |-Controller Direct Attach Devices | 582 | | |-PHY 0 SEAGATE ST9146803SS B241 6.0 | 583 | | |-PHY 3 ATA SAMSUNG MCBQE32G 5006 3.0 | 584 | | |-Expander LSILOGICSASx12 A.0 | 585 | | |-PHY 3 ATA Maxtor 6y080M0 1EW0 1.5 | 586 | | |-PHY 4 SEAGATE ST9146803SS B241 3.0 | 587 | | |-PHY 5 ATA SAMSUNG MCBQE32G 5006 1.5 | 588 | | |-PHY 7 RAID Physical Disk 1.5 | 589 | | |-PHY 9 RAID Physical Disk 1.5 | 590 | | |-RAID0 VOL LSI Logical Volume 3000 | 591 | | |-PHY 9 ATA Maxtor 6y080M0 1EW0 | 592 | | |-PHY 7 ATA Maxtor 6y080M0 1EW0 | 593 | | | 594 | | | 595 | | | 596 | | Esc = Exit F1/Shift+1 = Help | 597 | | Alt+D = Device Properties Alt+M = More Keys | 598 | |------------------------------------------------------------------------------| 599 | 600 | Scrolling Cursor once more to the right will display further information: 601 | 602 | |------------------------------------------------------------------------------| 603 | | Avago Technologies Config Utility v7.38.01.00 (2014.07.06) | 604 | | SAS Topology -- SAS2008 | 605 | | Device Identifier Maximum Link | 606 | | SAS2008(03:03) Speed (Gbps) | 607 | | |-Controller Direct Attach Devices | 608 | | |-PHY 0 SEAGATE ST9146803SS B241 6.0 | 609 | | |-PHY 3 ATA SAMSUNG MCBQE32G 5006 6.0 | 610 | | |-Expander LSILOGICSASx12 A.0 | 611 | | |-PHY 3 ATA Maxtor 6y080M0 1EW0 3.0 | 612 | | |-PHY 4 SEAGATE ST9146803SS B241 3.0 | 613 | | |-PHY 5 ATA SAMSUNG MCBQE32G 5006 3.0 | 614 | | |-PHY 7 RAID Physical Disk 3.0 | 615 | | |-PHY 9 RAID Physical Disk 3.0 | 616 | | |-RAID0 VOL LSI Logical Volume 3000 | 617 | | |-PHY 9 ATA Maxtor 6y080M0 1EW0 | 618 | | |-PHY 7 ATA Maxtor 6y080M0 1EW0 | 619 | | | 620 | | | 621 | | | 622 | | Esc = Exit F1/Shift+1 = Help | 623 | | Alt+D = Device Properties Alt+M = More Keys | 624 | |------------------------------------------------------------------------------| 625 | 626 | 627 | * * * Field Descriptions * * * 628 | 629 | Device Identifier 630 | 631 | This field indicates the ASCII device identifier string extracted from 632 | the device's Inquiry Data. 633 | 634 | Device Info 635 | 636 | This field indicates if a device is SAS or SATA, and if the device has 637 | been selected as the Boot Device. 638 | 639 | Negotiated Link Speed 640 | 641 | This field indicates the negotiated link speed for this Phy or whether it 642 | has been disabled 643 | 644 | Maximum Link Speed 645 | 646 | This field indicates the maximum hardware link rate possible for this Phy. 647 | 648 | * * * * * * * * * * Device Properties * * * * * * * * * * 649 | 650 | 651 | The Device Properties screen displays information about a specific Device and 652 | is accessed by pressing Alt+D on the SAS Topology screen when the cursor is on 653 | the Device Identifier field of a Device. 654 | 655 | User can press Alt+N or Alt+P at any time while on this screen to cycle to the 656 | next/previous device. 657 | 658 | |------------------------------------------------------------------------------| 659 | | Avago Technologies Config Utility v7.38.01.00 (2014.07.06) | 660 | | Device Properties -- SAS2008 | 661 | | | 662 | | | 663 | | Device Identifier SEAGATE ST936701SS B828 | 664 | | Scan Order 3 | 665 | | Slot Number 1 | 666 | | RAID Member No | 667 | | Device Information SAS | 668 | | Disk Capacity (GiB) 36 | 669 | | SAS Address 5000C500:001009E1 | 670 | | Serial Number 3LC0093N0000H4442MHE | 671 | | | 672 | | | 673 | | Format | 674 | | | 675 | | Verify | 676 | | | 677 | | | 678 | | | 679 | | Esc=Exit F1/Shift+1=Help | 680 | | Alt+N = Next Device Alt+P = Previous Device Enter = Select Item | 681 | |------------------------------------------------------------------------------| 682 | 683 | 684 | * * * Field Descriptions * * * 685 | 686 | Device Identifier 687 | 688 | This field indicates the ASCII device identifier string extracted from 689 | the device's Inquiry Data. 690 | 691 | Scan Order 692 | 693 | Indicates the scan order for this device. This would be the equivalent of 694 | a SCSI ID in parallel SCSI. 695 | 696 | Slot Number 697 | 698 | Indicates the slot number for this device. This is used by enclosures to 699 | locate devices. 700 | 701 | RAID Member 702 | 703 | If this disk is included in an integrated RAID volume, then this value will 704 | be 'Yes'. The disk will be 'No' if it is not a member of an IR volume. 705 | 706 | Disk Capacity 707 | 708 | This is the size of the disk in Gigabytes. 709 | 710 | Device Information 711 | 712 | This field indicates if a device is SAS or SATA. 713 | 714 | SAS Address 715 | 716 | This field indicates the SAS Address of this device. 717 | 718 | Serial Number 719 | 720 | This field indicates the Serial Number of this device. 721 | 722 | Format 723 | 724 | Press Enter to enter the low-level format screen for the device. Once 725 | on the format screen (see below) you can start a low-level format. 726 | 727 | If enabled, this option allows low-level formatting on a disk drive. 728 | Low-level formatting will completely and irreversibly erase all data on the 729 | drive. 730 | 731 | Note: Formatting will default the drive to a 512-byte sector size even if 732 | the drive had previously been formatted to another sector size. 733 | 734 | Verify 735 | 736 | Press Enter to enter the verify all sectors screen. Once on the Verify 737 | screen (see below) you can start a verify of all sectors on the device 738 | and if needed reassign defective Logical Block Addresses (LBAs). 739 | 740 | 741 | * * * * * * * * * * Format/Verify Screens * * * * * * * * * * 742 | 743 | The Format and Verify screens have similar layout and are accessed by hitting 744 | Enter on the appropriate field on the Device Properties screen. 745 | These screens include an Elapsed Time and status bar that begin incrementing 746 | once the operation is started and enable user to determine current progress of 747 | the operation. 748 | 749 | Once on the Format screen, pressing the "F" key will begin the format. 750 | 751 | ***ONCE FORMAT HAS STARTED IT CANNOT BE STOPPED OR CANCELLED*** 752 | 753 | |------------------------------------------------------------------------------| 754 | | Avago Technologies Config Utility v7.38.01.00 (2014.07.06) | 755 | | Device Format -- SAS2008 | 756 | | | 757 | | Device Identifier SEAGATE ST936701SS B828 | 758 | | SAS Address 5000C500:001009E1 | 759 | | Serial Number 3LC0093N0000H4442MHE | 760 | | | 761 | | WARNING! Format will change the sector size to 512 bytes. | 762 | | Format will permanently erase all data on this device! | 763 | | Format may take hours to complete and cannot be stopped. | 764 | | Press the 'F' key to begin format or any other key to exit. | 765 | | | 766 | | | 767 | | | 768 | | Elapsed Time: 00:00:00 | 769 | | | 770 | | Percent | 771 | | Complete 0% 100% | 772 | | --------------------------------------------------- | 773 | | | | | 774 | | | | | 775 | | --------------------------------------------------- | 776 | | | 777 | | | 778 | | Esc = Exit Menu F1/Shift+1 = Help | 779 | | | 780 | |------------------------------------------------------------------------------| 781 | 782 | 783 | Once on the Verify screen pressing the Enter key will begin the verify. 784 | 785 | User may hit Esc at anytime to cancel the verify. 786 | 787 | |------------------------------------------------------------------------------| 788 | | Avago Technologies Config Utility v7.38.01.00 (2014.07.06) | 789 | | Device Verify -- SAS2008 | 790 | | | 791 | | Device Identifier SEAGATE ST936701SS B828 | 792 | | SAS Address 5000C500:001009E1 | 793 | | Serial Number 3LC0093N0000H4442MHE | 794 | | | 795 | | All sectors on the device will be verified | 796 | | Press Enter to continue or any other key to cancel | 797 | | | 798 | | | 799 | | | 800 | | | 801 | | | 802 | | Elapsed Time: 00:00:00 | 803 | | | 804 | | Percent | 805 | | Complete 0% 100% | 806 | | --------------------------------------------------- | 807 | | | | | 808 | | | | | 809 | | --------------------------------------------------- | 810 | | | 811 | | | 812 | | Esc = Exit Menu F1/Shift+1 = Help | 813 | | | 814 | |------------------------------------------------------------------------------| 815 | 816 | * * * Field Descriptions * * * 817 | 818 | Device Identifier 819 | 820 | This field indicates the ASCII device identifier string extracted from 821 | the device's Inquiry Data. 822 | 823 | SAS Address 824 | 825 | This field indicates the SAS Address of this device. 826 | 827 | Serial Number 828 | 829 | This field indicates the Serial Number of this device. 830 | 831 | Elapsed Time 832 | 833 | Displays the total time elapsed since Format or Verify Operation started. 834 | 835 | Percent Complete 836 | 837 | Graphical status bar display that indicates the current relative % complete 838 | of the operation. 839 | 840 | 841 | * * * * * * * * * SAS Topology - More Keys * * * * * * * * * 842 | 843 | There are additional functions that can be performed while on the SAS Topology 844 | screen. These are detailed on by selecting Alt+M from the main SAS Topology 845 | screen. 846 | 847 | |------------------------------------------------------------------------------| 848 | | Avago Technologies Config Utility v7.38.01.00 (2014.07.06) | 849 | | SAS Topology -- SAS2008 | 850 | | | 851 | | More keys for the SAS Topology display: | 852 | | | 853 | | Alt+B = Select or deselect a device as the preferred boot device | 854 | | Alt+A = Select or deselect a device as the alternate boot device | 855 | | | 856 | | Enter = On a SAS Enclosure or Expander - Expand or Collapse Item | 857 | | Enter = On a Disk Drive - Turn on the Locate LED (next key press turns off) | 858 | | | 859 | | | 860 | | | 861 | | | 862 | | | 863 | | | 864 | | Esc = Exit F1/Shift+1 = Help | 865 | | Alt+D = Device Properties Alt+M = More Keys | 866 | |------------------------------------------------------------------------------| 867 | 868 | * * * Field Descriptions * * * 869 | 870 | Set/Clear Preferred Boot Device ('Alt+B') 871 | 872 | Press this key to set the highest priority (preferred) boot device. This can 873 | be either an INT13 device, or an active RAID volume. This device will be the 874 | first device the core BIOS will look for when attempting to boot. Pressing 875 | Alt+B for a device that is already the preferred boot device will clear the 876 | device's boot status. 877 | 878 | Set/Clear Alternate Boot Device ('Alt+A') 879 | 880 | Press this key to set the second priority (alternate) boot device. This can 881 | be either an INT13 device, or an active RAID volume. This device will only 882 | be checked if the preferred boot device cannot be located by the core BIOS. 883 | Pressing Alt+A for a device that is already the alternate boot device will 884 | clear the device's boot status. 885 | 886 | 887 | * * * * * * * * * * Advanced Adapter Properties * * * * * * * 888 | 889 | The Advanced Adapter Properties screen supports viewing and modification of 890 | infrequently accessed adapter settings. It provides access to advanced 891 | Device Properties, Adapter Timing Properties, and PHY Properties. 892 | 893 | |------------------------------------------------------------------------------| 894 | | Avago Technologies Config Utility v7.38.01.00 (2014.07.06) | 895 | | Advanced Adapter Properties -- SAS2008 | 896 | | | 897 | | IRQ 0B | 898 | | NVM Yes | 899 | | IO Port Address 9000 | 900 | | Chip Revision ID 00 | 901 | | | 902 | | | 903 | | Advanced Device Properties | 904 | | Adapter Timing Properties | 905 | | | 906 | | | 907 | | | 908 | | | 909 | | | 910 | | | 911 | | Esc = Exit Menu F1/Shift+1 = Help | 912 | | Enter = Select Item -/+ = Change Item | 913 | |------------------------------------------------------------------------------| 914 | 915 | * * * Field Descriptions * * * 916 | 917 | IRQ 918 | 919 | Indicates the Interrupt Request Line used by an adapter. The system 920 | BIOS assigns this value. 921 | 922 | NVM 923 | Indicates whether an adapter has non-volatile memory (NVM) associated 924 | with it. An adapter's configuration is stored in its associated NVM. 925 | 926 | IO Port Address 927 | Indicates the I/O Port Address used to communicate with an adapter. The 928 | system BIOS assigns this number. 929 | 930 | Chip Revision ID 931 | 932 | Indicates the Revision ID of this adapter. 933 | 934 | Advanced Device Properties 935 | 936 | Press Enter to view and modify Advanced Device Properties. 937 | 938 | Adapter Timing Properties 939 | 940 | Press Enter to view and modify Adapter Timing Properties. 941 | 942 | 943 | 944 | * * * * * * * * * Advanced Device Properties * * * * * * * * * 945 | 946 | The Advanced Device Properties screen supports viewing and modification of 947 | infrequently accessed device settings. 948 | 949 | |------------------------------------------------------------------------------| 950 | | Avago Technologies Config Utility v7.38.01.00 (2014.07.06) | 951 | | Advanced Device Properties -- SAS2008 | 952 | | | 953 | | Maximum INT 13 devices for this adapter 24 | 954 | | | 955 | | IO Timeout for Block Devices 10 | 956 | | IO Timeout for Block Devices(Removable) 10 | 957 | | IO Timeout for Sequential Devices 10 | 958 | | IO Timeout for Other Devices 10 | 959 | | Start Stop Unit Timeout 30 | 960 | | | 961 | | LUNs to Scan for Block Devices All | 962 | | LUNs to Scan for Block Devices(Removable) All | 963 | | LUNs to Scan for Sequential Devices All | 964 | | LUNs to Scan for Other Devices All | 965 | | | 966 | | Removable Media Support [None] | 967 | | | 968 | | Restore Defaults | 969 | | | 970 | | | 971 | | Esc = Exit Menu F1/Shift+1 = Help | 972 | | Enter = Select Item -/+ = Change Item | 973 | |------------------------------------------------------------------------------| 974 | 975 | 976 | * * * Field Descriptions * * * 977 | 978 | Maximum INT 13h Devices for this adapter 979 | 980 | This field specifies the maximum number of devices attached to the 981 | adapter for which to install a pre-OS IO interface. The specified 982 | number of devices in the adapter's device scan order list will have 983 | an IO interface installed. An installed IO interface is defined as 984 | INT 13H. 985 | 986 | X86 platforms allow a maximum of 24 INT 13h devices per system. Therefore, 987 | fewer than the specified number of INT 13h devices may be installed. The 988 | defaults for X86 is 24 devices with a range of 0-24 allowed. 989 | 990 | IO Timeout for Block Devices 991 | 992 | This field specifies the time, in seconds, (0-999, 0 means no-timeout) which 993 | the host uses to timeout I/Os for the following devices with Non-Removable 994 | Media: 995 | 996 | SCSI Device Type 00h - Direct Access 997 | SCSI Device Type 04h - Write Once 998 | SCSI Device Type 07h - Optical 999 | SCSI Device Type 0Eh - Simplified Direct Access 1000 | 1001 | IO Timeout for Block Devices (Removable) 1002 | 1003 | This field specifies the time, in seconds, (0-999, 0 means no-timeout) which 1004 | the host uses to timeout I/Os for the following devices with Removable Media: 1005 | 1006 | SCSI Device Type 00h - Direct Access 1007 | SCSI Device Type 04h - Write Once 1008 | SCSI Device Type 05h - CD-ROM 1009 | SCSI Device Type 07h - Optical 1010 | SCSI Device Type 0Eh - Simplified Direct Access 1011 | 1012 | IO Timeout for Sequential Devices 1013 | 1014 | This field specifies the time, in seconds, (0-999, 0 means no-timeout) which 1015 | the host uses to timeout I/Os for the following devices: 1016 | 1017 | SCSI Device Type 01h - Sequential Access. 1018 | 1019 | IO Timeout for Other Devices 1020 | 1021 | This field specifies the time, in seconds, (0-999, 0 means no-timeout) which 1022 | the host uses to timeout I/Os for devices other than: 1023 | 1024 | SCSI Device Type 00h - Direct Access 1025 | SCSI Device Type 01h - Sequential Access 1026 | SCSI Device Type 04h - Write Once 1027 | SCSI Device Type 05h - CD-ROM 1028 | SCSI Device Type 07h - Optical 1029 | SCSI Device Type 0Eh - Simplified Direct Access 1030 | 1031 | LUNs to Scan for Block Devices 1032 | 1033 | Controls LUN scans for the following devices with Non-Removable Media: 1034 | 1035 | SCSI Device Type 00h - Direct Access 1036 | SCSI Device Type 04h - Write Once 1037 | SCSI Device Type 07h - Optical 1038 | SCSI Device Type 0Eh - Simplified Direct Access 1039 | 1040 | LUN 0 Only: Scan only LUN 0. 1041 | All: Scan all LUNs. 1042 | 1043 | LUNs to Scan for Block Devices(Removable) 1044 | 1045 | Controls LUN scans for the following devices with Removable Media: 1046 | 1047 | SCSI Device Type 00h - Direct Access 1048 | SCSI Device Type 04h - Write Once 1049 | SCSI Device Type 05h - CD-ROM 1050 | SCSI Device Type 07h - Optical 1051 | SCSI Device Type 0Eh - Simplified Direct Access. 1052 | 1053 | LUN 0 Only: Scan only LUN 0. 1054 | All: Scan all LUNs. 1055 | 1056 | LUNs to Scan for Sequential Devices 1057 | 1058 | Controls LUN scans for the following devices: 1059 | 1060 | SCSI Device Type 01h - Sequential Access. 1061 | 1062 | LUN 0 Only: Scan only LUN 0. 1063 | All: Scan all LUNs. 1064 | 1065 | LUNs to Scan for Other Devices 1066 | 1067 | Controls LUN scans for all devices other than the following: 1068 | 1069 | SCSI Device Type 00h - Direct Access 1070 | SCSI Device Type 01h - Sequential Access 1071 | SCSI Device Type 04h - Write Once 1072 | SCSI Device Type 05h - CD-ROM 1073 | SCSI Device Type 07h - Optical 1074 | SCSI Device Type 0Eh - Simplified Direct Access. 1075 | 1076 | LUN 0 Only: Scan only LUN 0. 1077 | All: Scan all LUNs. 1078 | 1079 | Removable Media Support 1080 | 1081 | This field specifies the removable media support option for an adapter. 1082 | 1083 | None: 1084 | Install no INT 13H interface for any Direct Access Removable Media 1085 | devices. 1086 | 1087 | Boot Device Only: 1088 | Install INT 13H interface for a Direct Access Removable Media device if 1089 | and only if media is present in the device at the time of BIOS 1090 | initialization and either: 1091 | 1092 | BBS System 1093 | The device is selected as the boot device. Refer to the BIOS Boot 1094 | Specification for a description of BBS. 1095 | 1096 | Non-BBS System 1097 | The device is setup as the boot device The adapter the device is 1098 | connected to is specified as the first adapter (i.e., 0) in the 1099 | Boot Adapter List. The device is specified as the first device 1100 | in the adapter's device scan order list. 1101 | 1102 | With Media Installed: 1103 | Install INT 13H interfaces for Direct Access Removable Media devices if 1104 | media is present in the device at the time of BIOS initialization. 1105 | 1106 | Restore Defaults 1107 | 1108 | Press the Enter key to set default values for all items on this screen. 1109 | 1110 | 1111 | 1112 | * * * * * * * * * Adapter Timing Properties * * * * * * * * * 1113 | 1114 | The Adapter Timing Properties screen supports viewing and modification of 1115 | timing-specific settings. 1116 | 1117 | Note that the Link Error Settings values on this screen display the current 1118 | values for this PHY only and are not modifiable. To modify the Threshold values 1119 | user should return to Advanced Adapter Properties screen. 1120 | 1121 | 1122 | |------------------------------------------------------------------------------| 1123 | | Avago Technologies Config Utility v7.38.01.00 (2014.07.06) | 1124 | | Adapter Timing Properties -- SAS2008 | 1125 | | | 1126 | | Direct Attached Spinup Delay (Secs) [ 2] | 1127 | | | 1128 | | Direct Attached Max Targets to Spinup [ 0] | 1129 | | | 1130 | | Report Device Missing Delay [ 0] | 1131 | | | 1132 | | IO Device Missing Delay [ 0] | 1133 | | | 1134 | | | 1135 | | | 1136 | | | 1137 | | | 1138 | | | 1139 | | Esc = Exit Menu F1/Shift+1 = Help | 1140 | | Enter = Select Item -/+ = Change Item | 1141 | |------------------------------------------------------------------------------| 1142 | 1143 | * * * Field Descriptions * * * 1144 | 1145 | Direct Attached Spinup Delay (Secs) 1146 | 1147 | This field specifies the number of seconds to wait between spinups of 1148 | devices. Valid only when the device is configured (jumpered) to require a 1149 | spin up. 1150 | Values range from 0 to 15. 1151 | 1152 | Direct Attached Max Targets to Spinup 1153 | 1154 | This field specifies the maximum number of targets that can be simultaneously 1155 | spinning up. The IOC must delay by the time indicated in spin-up delay field 1156 | before starting spin-up of the next set of targets. A value of zero in this 1157 | field is treated the same as a value of one. 1158 | Values range from 0 to 15. 1159 | 1160 | Report Device Missing Delay 1161 | 1162 | This field specifies the time (in seconds) the IOC will delay reporting a 1163 | target device missing after it becomes unavailable. If the device returns 1164 | before this timer expires, the device is not reported as missing. 1165 | Values range from 0 to 2032. 1166 | 1167 | IO Device Missing Delay 1168 | 1169 | This field specifies the time interval (in seconds) the IOC will delay 1170 | replying to SCSI Initiator request messages when the addressed device is 1171 | missing due to the inability to access the target device. 1172 | Values range from 0 to 255. 1173 | 1174 | 1175 | 1176 | * * * * Integrated RAID Configuration and Management Screens * * * * * 1177 | 1178 | Integrated RAID configuration and management involves many screens, all of which 1179 | are accessed by selecting RAID Properties on the Adapter Properties screen. 1180 | 1181 | If there are no RAID volumes currently configured: 1182 | The user is asked to create a RAID volume 1183 | 1184 | If there are two active RAID volume currently configured: 1185 | The user is shown the current volume(s) for management purposes. 1186 | 1187 | If there are RAID volumes currently configured, but fewer than two active: 1188 | The user is given the option to view the current volume(s), or create 1189 | RAID volumes. 1190 | 1191 | The screens contained in the RAID configuration and management area are: 1192 | Select RAID Volume Actions 1193 | Create New Volume 1194 | View Volume 1195 | Manage Volume 1196 | Manage Hot Spares 1197 | 1198 | 1199 | * Select RAID Volume Actions * 1200 | 1201 | Select the type of volume to create. 1202 | 1203 | |------------------------------------------------------------------------------| 1204 | | Avago Technologies Config Utility v7.38.01.00 (2014.07.06) | 1205 | | Select New Volume Type -- SAS2008 | 1206 | | | 1207 | | View Existing Volume View the existing configuration | 1208 | | | 1209 | | | 1210 | | Create RAID 1 Volume Create a RAID 1 volume | 1211 | | consisting of 2 disks plus up to 2 | 1212 | | optional hot spares. ALL DATA on | 1213 | | volume disks will be deleted! | 1214 | | | 1215 | | Create RAID 1E/10 Volume Create a RAID 1E or RAID 10 volume | 1216 | | consisting of 3 to 10 disks including up | 1217 | | to two optional hot spares. ALL DATA on | 1218 | | volume disks will be deleted! | 1219 | | | 1220 | | Create RAID 0 Volume Create a RAID 0 volume consisting of | 1221 | | 2 to 10 disks. ALL DATA on | 1222 | | volume disks will be deleted! | 1223 | | | 1224 | | | 1225 | | Esc = Exit Menu F1/Shift+1 = Help | 1226 | | Enter = Choose volume type to create | 1227 | |------------------------------------------------------------------------------| 1228 | 1229 | 1230 | * * * Field Descriptions * * * 1231 | 1232 | View Existing Volume 1233 | 1234 | If an existing volume is found, then this option will be displayed. 1235 | Press enter to view existing volumes on the controller. 1236 | 1237 | Create RAID 1 Volume 1238 | 1239 | Press Enter to create a RAID 1 volume. Existing 1240 | data on the selected disks will be deleted. 1241 | 1242 | Create RAID 10/1E Volume 1243 | 1244 | Press Enter to create a RAID 10 or RAID 1E volume. Existing 1245 | data on the selected disks will be deleted. 1246 | 1247 | Create RAID 0 Volume 1248 | 1249 | Press Enter to create a RAID 0 volume. Existing 1250 | data on the selected disks will be deleted. 1251 | 1252 | 1253 | 1254 | * Create New Volume * 1255 | 1256 | This screen allows the user to create a new volume by selecting disks for the 1257 | volume. After the volume is configured, the user would press 'C' to create the 1258 | volume. The user will be asked to save changes, which will create the volume. 1259 | During the creation process, the utility will pause. After which time, the 1260 | user will be taken back to Adapter Properties. 1261 | 1262 | - The Locate LED will turn ON for the enclosure drives that are selected to be 1263 | member of the new volume. 1264 | 1265 | |------------------------------------------------------------------------------| 1266 | | Avago Technologies Config Utility v7.38.01.00 (2014.07.06) | 1267 | | Create New Volume -- SAS2008 | 1268 | | | 1269 | | Volume Type: RAID 1 | 1270 | | Volume Size(GiB) 135 | 1271 | | | 1272 | | Slot Device Identifier RAID Hot Drive Pred Size | 1273 | | Num Disk Spr Status Fail (GiB) | 1274 | | 1 SEAGATE ST9146803SS B241 [Yes] No Primary --- 135 | 1275 | | 2 SEAGATE ST9146803SS B241 [Yes] No Secondary --- 135 | 1276 | | 8 ATA SAMSUNG MCBQE32G 5006 [No] No --------- --- 29 | 1277 | | 11 ATA SAMSUNG MCBQE32G 5006 [No] No --------- --- 29 | 1278 | | | 1279 | | | 1280 | | | 1281 | | | 1282 | | | 1283 | | | 1284 | | | 1285 | | | 1286 | | | 1287 | | | 1288 | | Esc = Exit Menu F1/Shift+1 = Help | 1289 | | Space/+/- = Select disk for volume or hot spare C = Create volume | 1290 | |------------------------------------------------------------------------------| 1291 | 1292 | 1293 | * * * Field Descriptions * * * 1294 | 1295 | Volume Type 1296 | 1297 | Indicates the type of volume being created. 1298 | 1299 | Volume Size 1300 | 1301 | Indicates the size of the volume in Megabytes. 1302 | 1303 | Device Identifier 1304 | 1305 | This field is the device identifier. 1306 | 1307 | RAID Disk 1308 | 1309 | This field specifies the devices (disks) that make up a RAID volume 1310 | (Yes, No, default: NO). 1311 | 1312 | If Yes, the device is part of a RAID volume. 1313 | If No, the device is not part of a RAID volume. 1314 | 1315 | During the creation of a volume, this field will be No for all 1316 | members of a pre-existing volume. 1317 | 1318 | This field is grayed out under the following conditions: 1319 | - the device does not meet the minimum requirements for use in a RAID volume 1320 | - the device is not large enough to mirror existing data on the primary drive 1321 | - the device is not interface compatible with another selected volume drive 1322 | - this disk is already a member of another RAID volume 1323 | 1324 | Hot Spr 1325 | 1326 | This field specifies whether a device is a Hot Spare for a RAID volume 1327 | (Yes, No, default: NO). 1328 | If Yes, the device will be used as a Hot Spare for the RAID volume. 1329 | If No, the device will not be used as a Hot Spare for the RAID volume. 1330 | Notes: 1331 | - Only two Hot Spares per controller are permitted. 1332 | - RAID volumes do not require any Hot Spares. 1333 | - Hot Spares can only be specified after a volume has been created. 1334 | 1335 | This field is grayed out on this screen 1336 | 1337 | Drive Status 1338 | 1339 | Ok Disk is online and fully functional 1340 | Missing Disk is not responding or is not present 1341 | Failed Disk is not accessible or has reported a failure 1342 | Initing Disk is initializing 1343 | UserFail Disk is marked failed at host's request 1344 | Offline Disk is offline for some other reason 1345 | Inactive Disk has been set inactive 1346 | RAID Disk is already a member of another RAID volume 1347 | Not Syncd Data on disk is not synchronized with the rest of the volume 1348 | Primary Disk is the primary disk in a RAID 1 volume and is OK 1349 | Secondary Disk is the secondary disk in a RAID 1 volume and is OK 1350 | Hot Spare Disk is a hot spare disk for a RAID 1 or RAID 1E volume 1351 | Wrg Type Device is not compatible for use as part of the RAID volume 1352 | Too Small Disk is too small to be a hot spare for this volume 1353 | Max Dsks Maximum # of disks allowed for this type of volume reached 1354 | Maximum # of total IR disks on a controller reached 1355 | Inc RAID Disk doesn't support SMART or SATA extended commands 1356 | Wrg Intfc Disk interface (SAS/SATA) differs from existing IR disks 1357 | Inc PI Disk doesnt support required Protection Information 1358 | 1359 | Pred Fail 1360 | 1361 | Indicates whether device SMART is predicting device failure (Yes, No). 1362 | 1363 | Size(GiB) 1364 | 1365 | Indicates the size of the device in gigabytes (where a gigabyte is 1366 | (1024 x 1024 x 1024) = 1,073,741,824 bytes). 1367 | 1368 | If the device is part of a two-disk volume, this field will reflect the size 1369 | of the volume - not the size of the individual disk. 1370 | 1371 | If the device is part of a three or more disk volume, this field is the size 1372 | that the disk makes up within the volume. 1373 | 1374 | NOTE: When creating a RAID 0 volume, the usable size of the volume is 1375 | determined by the Number of drives X Size of the smallest drive in the 1376 | volume. In volumes consisting of different sized drives, excess space on 1377 | larger drives will be unusable. 1378 | 1379 | 1380 | 1381 | * View Volume * 1382 | 1383 | This screen allows the user to view the current volume configuration. 1384 | 1385 | Press Enter to Manage the Volume when Manage Volume is highlighted. 1386 | 1387 | Press Alt+N to view the next volume. 1388 | 1389 | - The Locate LED will turn ON for all the enclosure drives that are part of the 1390 | RAID volume. 1391 | 1392 | |------------------------------------------------------------------------------| 1393 | | Avago Technologies Config Utility v7.38.01.00 (2014.07.06) | 1394 | | View Volume -- SAS2008 | 1395 | | | 1396 | | Volume 1 of 1 | 1397 | | Identifier LSILOGICLogical Volume 3000 | 1398 | | Type RAID 1 | 1399 | | Size(GiB) 135 | 1400 | | Status Optimal | 1401 | | | 1402 | | Manage Volume | 1403 | | | 1404 | | Slot Device Identifier RAID Hot Drive Pred Size | 1405 | | Num Disk Spr Status Fail (GiB) | 1406 | | 1 SEAGATE ST9146803SS B241 Yes No Primary --- 135 | 1407 | | 2 SEAGATE ST9146803SS B241 Yes No Secondary --- 135 | 1408 | | 8 ATA SAMSUNG MCBQE32G 5006 No No --------- --- 29 | 1409 | | 11 ATA SAMSUNG MCBQE32G 5006 No No --------- --- 29 | 1410 | | | 1411 | | | 1412 | | | 1413 | | | 1414 | | | 1415 | | Esc = Exit Menu F1/Shift+1 = Help | 1416 | | Enter=Select Item Alt+N=Next Volume | 1417 | |------------------------------------------------------------------------------| 1418 | 1419 | 1420 | * * * Field Descriptions * * * 1421 | 1422 | Volume 1423 | 1424 | The number of this volume. 1425 | 1426 | Identifier 1427 | 1428 | The identifier of this volume. 1429 | 1430 | Type 1431 | 1432 | The RAID type. 1433 | 1434 | Size(GiB) 1435 | 1436 | The size of the volume. 1437 | 1438 | Status 1439 | 1440 | The status of the volume. 1441 | 1442 | Device Identifier 1443 | 1444 | This field is the device identifier. 1445 | 1446 | RAID Disk 1447 | 1448 | This field specifies the devices (disks) that make up a RAID volume 1449 | (Yes, No, default: NO). 1450 | 1451 | If Yes, the device is part of a RAID volume. 1452 | If No, the device is not part of a RAID volume. 1453 | 1454 | This field is grayed out on this screen 1455 | 1456 | Hot Spr 1457 | 1458 | This field specifies whether a device is a Hot Spare for a RAID volume 1459 | (Yes, No, default: NO). 1460 | If Yes, the device will be used as a Hot Spare for the RAID volume. 1461 | If No, the device will not be used as a Hot Spare for the RAID volume. 1462 | 1463 | This field is grayed out on this screen 1464 | 1465 | Drive Status 1466 | 1467 | Ok Disk is online and fully functional 1468 | Missing Disk is not responding or is not present 1469 | Failed Disk is not accessible or has reported a failure 1470 | Initing Disk is initializing 1471 | UserFail Disk is marked failed at host's request 1472 | Offline Disk is offline for some other reason 1473 | Inactive Disk has been set inactive 1474 | RAID Disk is already a member of another RAID volume 1475 | Not Syncd Data on disk is not synchronized with the rest of the volume 1476 | Primary Disk is the primary disk in a RAID 1 volume and is OK 1477 | Secondary Disk is the secondary disk in a RAID 1 volume and is OK 1478 | Hot Spare Disk is a hot spare disk for a RAID 1 or RAID 1E volume 1479 | Wrg Type Device is not compatible for use as part of the RAID volume 1480 | Too Small Disk is too small to be a hot spare for this volume 1481 | Max Dsks Maximum # of disks allowed for this type of volume reached 1482 | Maximum # of total IR disks on a controller reached 1483 | Inc RAID Disk doesn't support SMART or SATA extended commands 1484 | Wrg Intfc Disk interface (SAS/SATA) differs from existing IR disks 1485 | Inc PI Disk doesnt support required Protection Information 1486 | 1487 | Pred Fail 1488 | 1489 | Indicates whether device SMART is predicting device failure (Yes, No). 1490 | 1491 | Size(GiB) 1492 | 1493 | Indicates the size of the device in gigabytes (where a gigabyte is 1494 | (1024 x 1024 x 1024) = 1,073,741,824 bytes). 1495 | 1496 | If the device is part of a two-disk volume, this field will reflect the size 1497 | of the volume - not the size of the individual disk. 1498 | 1499 | If the device is part of a three or more disk volume, this field is the size 1500 | that the disk makes up within the volume. 1501 | 1502 | NOTE: When creating a RAID 0 volume, the usable size of the volume is 1503 | determined by the Number of drives X Size of the smallest drive in the 1504 | volume. In volumes consisting of different sized drives, excess space on 1505 | larger drives will be unusable. 1506 | 1507 | 1508 | 1509 | * Manage Volume * 1510 | 1511 | Manage the current volume. 1512 | 1513 | If the user selects Manage Hot Spare, the utility will display a hot spare 1514 | management screen that has the same layout as the Create New Volume screen. 1515 | 1516 | The user will be asked to confirm selections of Synchronize Volume, Activate 1517 | Volume, and Delete Volume by pressing 'Y' for yes or 'N' for no. 1518 | 1519 | |------------------------------------------------------------------------------| 1520 | | Avago Technologies Config Utility v7.38.01.00 (2014.07.06) | 1521 | | Manage Volume -- SAS2008 | 1522 | | | 1523 | | | 1524 | | Identifier LSILOGICLogical Volume 3000 | 1525 | | Type RAID 1 | 1526 | | Size(GiB) 135 | 1527 | | Status Optimal | 1528 | | | 1529 | | Manage Hot Spares | 1530 | | | 1531 | | Consistency Check | 1532 | | | 1533 | | Activate Volume | 1534 | | | 1535 | | Delete Volume | 1536 | | | 1537 | | Online Capacity Expansion | 1538 | | | 1539 | | | 1540 | | | 1541 | | Esc = Exit Menu F1/Shift+1 = Help | 1542 | | Enter = Select Item | 1543 | |------------------------------------------------------------------------------| 1544 | 1545 | 1546 | * * * Field Descriptions * * * 1547 | 1548 | Identifier 1549 | 1550 | The identifier of this volume. 1551 | 1552 | Type 1553 | 1554 | The RAID type. 1555 | 1556 | Size(GiB) 1557 | 1558 | The size of the volume. 1559 | 1560 | Status 1561 | 1562 | The status of the volume. 1563 | 1564 | Manage Hot Spares 1565 | 1566 | Press enter to modify the volume's hot spare configuration. 1567 | 1568 | This field is grayed out under the following conditions: 1569 | - The volume is inactive. 1570 | - The volume is at its maximum number of devices. 1571 | - The volume type is RAID 0. RAID 0 volumes do not support 1572 | Hot Spares. No modifications can be made to a RAID 0 1573 | volume once it has been created. 1574 | 1575 | Consistency Check 1576 | 1577 | Press Enter to run a consistency check on the RAID volume. 1578 | 1579 | This field is grayed out under the following conditions: 1580 | - The adapter's MPT FW does not support the feature 1581 | - The volume is a RAID 0 1582 | - The volume is not optimal 1583 | - The volume is already running a consistency check 1584 | - The volume has a consistency check pending 1585 | 1586 | Activate Volume 1587 | 1588 | This field is used to activate a RAID volume. 1589 | 1590 | Delete Volume 1591 | 1592 | This field is used to delete the currently displayed RAID volume. 1593 | 1594 | Online Capacity Expansion 1595 | 1596 | Press enter to expand the volume's maximum size. This will allow the user 1597 | to create a RAID 1 volume and replace existing volume drive with larger 1598 | drives. Once each drive is replaced and synchronization for that drive is 1599 | complete, this option will be allowed (presuming a minimum of 50 GiB 1600 | difference between the old RAID 1 volume drives and the new ones). 1601 | 1602 | This field is disabled under the following conditions: 1603 | - The volume is not a RAID 1 volume 1604 | - Firmware is configured to disable this feature 1605 | 1606 | * Manage Hot Spares * 1607 | 1608 | This screen allows the user to create, delete, or modify hot spares on the 1609 | adapter. After the volume is created, the user can select this screen to 1610 | configure hot spare drives. 1611 | 1612 | - The Locate LED will turn ON for the enclosure drives that are selected to be 1613 | Hot Spare. 1614 | 1615 | |------------------------------------------------------------------------------| 1616 | | Avago Technologies Config Utility v7.38.01.00 (2014.07.06) | 1617 | | Manage Hot Spares -- SAS2008 | 1618 | | | 1619 | | Volume Type: RAID 1 | 1620 | | Volume Size(GiB) 135 | 1621 | | | 1622 | | Slot Device Identifier RAID Hot Drive Pred Size | 1623 | | Num Disk Spr Status Fail (GiB) | 1624 | | 1 SEAGATE ST9146803SS B241 Yes [No] Primary --- 135 | 1625 | | 2 SEAGATE ST9146803SS B241 Yes [No] Secondary --- 135 | 1626 | | 8 SEAGATE ST9146803SS B241 No [Yes] Hot Spare --- 135 | 1627 | | 11 ATA SAMSUNG MCBQE32G 5006 No [No] --------- --- 29 | 1628 | | | 1629 | | | 1630 | | | 1631 | | | 1632 | | | 1633 | | | 1634 | | | 1635 | | | 1636 | | | 1637 | | | 1638 | | Esc = Exit Menu F1/Shift+1 = Help | 1639 | | Space/+/- = Select disk for volume or hot spare C = Create volume | 1640 | |------------------------------------------------------------------------------| 1641 | 1642 | 1643 | * * * Field Descriptions * * * 1644 | 1645 | Volume Type 1646 | 1647 | Indicates the type of volume being created. 1648 | 1649 | Volume Size 1650 | 1651 | Indicates the size of the volume in Megabytes. 1652 | 1653 | Device Identifier 1654 | 1655 | This field is the device identifier. 1656 | 1657 | RAID Disk 1658 | 1659 | This field specifies the devices (disks) that make up a RAID volume 1660 | (Yes, No, default: NO). 1661 | 1662 | If Yes, the device is part of a RAID volume. 1663 | If No, the device is not part of a RAID volume. 1664 | 1665 | During the creation of a volume, this field will be No for all 1666 | members of a pre-existing volume. 1667 | 1668 | This field is grayed out for this screen 1669 | 1670 | Hot Spr 1671 | 1672 | This field specifies whether a device is a Hot Spare for a RAID volume 1673 | (Yes, No, default: NO). 1674 | If Yes, the device will be used as a Hot Spare for the RAID volume. 1675 | If No, the device will not be used as a Hot Spare for the RAID volume. 1676 | Notes: 1677 | - Only two Hot Spares per controller are permitted. 1678 | - RAID volumes do not require any Hot Spares. 1679 | - Hot Spares can only be specified after a volume has been created. 1680 | 1681 | This field is grayed out under the following conditions: 1682 | - The device does not meet the minimum requirements for use in a RAID volume 1683 | - There are already two Hot Spares on this controller. 1684 | - The maximum number of RAID physical disks have been configured (14). 1685 | - The device isn't large enough to replace a volume disk. 1686 | - A RAID 0 volume is being displayed. Hot Spares are not supported on 1687 | RAID 0 volumes. 1688 | - The device characteristics are not compatible with the volume 1689 | characteristics (SSD/non-SSD, SAS/SATA, etc.) 1690 | 1691 | Drive Status 1692 | 1693 | Ok Disk is online and fully functional 1694 | Missing Disk is not responding or is not present 1695 | Failed Disk is not accessible or has reported a failure 1696 | Initing Disk is initializing 1697 | UserFail Disk is marked failed at host's request 1698 | Offline Disk is offline for some other reason 1699 | Inactive Disk has been set inactive 1700 | RAID Disk is already a member of another RAID volume 1701 | Not Syncd Data on disk is not synchronized with the rest of the volume 1702 | Primary Disk is the primary disk in a RAID 1 volume and is OK 1703 | Secondary Disk is the secondary disk in a RAID 1 volume and is OK 1704 | Hot Spare Disk is a hot spare disk for a RAID 1 or RAID 1E volume 1705 | Wrg Type Device is not compatible for use as part of the RAID volume 1706 | Too Small Disk is too small to be a hot spare for this volume 1707 | Max Dsks Maximum # of disks allowed for this type of volume reached 1708 | Maximum # of total IR disks on a controller reached 1709 | Inc RAID Disk doesn't support SMART or SATA extended commands 1710 | Wrg Intfc Disk interface (SAS/SATA) differs from existing IR disks 1711 | Inc PI Disk doesnt support required Protection Information 1712 | 1713 | Pred Fail 1714 | 1715 | Indicates whether device SMART is predicting device failure (Yes, No). 1716 | 1717 | Size(GiB) 1718 | 1719 | Indicates the size of the device in gigabytes (where a gigabyte is 1720 | (1024 x 1024 x 1024) = 1,073,741,824 bytes). 1721 | 1722 | If the device is part of a two-disk volume, this field will reflect the size 1723 | of the volume - not the size of the individual disk. 1724 | 1725 | If the device is part of a three or more disk volume, this field is the size 1726 | that the disk makes up within the volume. 1727 | 1728 | NOTE: When creating a RAID 0 volume, the usable size of the volume is 1729 | determined by the Number of drives X Size of the smallest drive in the 1730 | volume. In volumes consisting of different sized drives, excess space on 1731 | larger drives will be unusable. 1732 | 1733 | 1734 | * * * * * * * Exiting the SAS Configuration Utility * * * * * * * * 1735 | 1736 | As some changes only take effect during the exit of the utility, it is important 1737 | to always exit the utility properly. From the Adapter List, press the Esc key 1738 | to exit the utility. In addition, the a similar exit screen is used when 1739 | exiting most other screens, and can be used to save settings. 1740 | 1741 | The exit screen will show some options that are grey, indicating that they are 1742 | not available at this time. Only available options will be selectable. 1743 | 1744 | 1745 | |------------------------------------------------------------------------------| 1746 | | Avago Technologies Config Utility v7.38.01.00 (2014.07.06) | 1747 | | | 1748 | | | 1749 | | | 1750 | | | 1751 | | | 1752 | | Are you sure you want to exit? | 1753 | | Cancel Exit | 1754 | | Save changes and reboot | 1755 | | Discard changes and reboot | 1756 | | Exit the Configuration Utility and Reboot | 1757 | | | 1758 | | | 1759 | | | 1760 | | | 1761 | | | 1762 | | | 1763 | | Esc=Exit Menu F1/Shift+1=Help | 1764 | | | 1765 | |------------------------------------------------------------------------------| 1766 | 1767 | 1768 | -------------------------------------------------------------------------------- /mptsas2.rom: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/lrq3000/lsi_sas_hba_crossflash_guide/e458a8e359a582e8a7d046be8ecbc8bf678d7b1b/mptsas2.rom -------------------------------------------------------------------------------- /mptsas2_p7.rom: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/lrq3000/lsi_sas_hba_crossflash_guide/e458a8e359a582e8a7d046be8ecbc8bf678d7b1b/mptsas2_p7.rom -------------------------------------------------------------------------------- /sas2flash.efi: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/lrq3000/lsi_sas_hba_crossflash_guide/e458a8e359a582e8a7d046be8ecbc8bf678d7b1b/sas2flash.efi -------------------------------------------------------------------------------- /sas2flsh.exe: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/lrq3000/lsi_sas_hba_crossflash_guide/e458a8e359a582e8a7d046be8ecbc8bf678d7b1b/sas2flsh.exe -------------------------------------------------------------------------------- /sas2hax.efi: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/lrq3000/lsi_sas_hba_crossflash_guide/e458a8e359a582e8a7d046be8ecbc8bf678d7b1b/sas2hax.efi -------------------------------------------------------------------------------- /sas2haxp20.efi: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/lrq3000/lsi_sas_hba_crossflash_guide/e458a8e359a582e8a7d046be8ecbc8bf678d7b1b/sas2haxp20.efi -------------------------------------------------------------------------------- /sbrempty.bin: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/lrq3000/lsi_sas_hba_crossflash_guide/e458a8e359a582e8a7d046be8ecbc8bf678d7b1b/sbrempty.bin --------------------------------------------------------------------------------