caplam Posted September 5 Posted September 5 (edited) Last month my 9207-8e died. I received it's replacement : LSI 9400-8e It seems files available to update it have changed. updating firmware seems to be done with storcli utility. Can it be donne with unraid ? here are the rel notes for the packages i can download for latest version P24 *********************************************************************************************************************** Package for SAS3.5 Phase 24 Firmware BIOS UEFI ************************************************************************************************************************ LSI Host Bus Adapter(HBA) - LSI SAS9400_8e Package Contents- Readme first note : README_9400_8e_Pkg_P24_SAS_SATA_FW_BIOS_UEFI.txt Component : Path Version Release Date ============================================================================================================================================ Firmware : \Firmware\HBA_9400-8e_SAS_SATA_Profile.bin 24.00.00.00 25-JULY-22 BIOS : \SAS35BIOS_Rel\mpt35sas_legacy.rom 09.47.00.00 09-JULY-22 Readme for BIOS : \SAS35BIOS_Rel\ReadMe_MPT35SAS_BIOS.txt NA NA UEFI BSD Signed : \UEFI_BSD_HII_SAS3.5_IT\Signed\mpt35sas_x64.rom 24.00.00.00 08-JULY-22 UEFI BSD : \UEFI_BSD_HII_SAS3.5_IT\mpt35sas_x64.rom 24.00.00.00 08-JULY-22 Driver Sign Info for UEFI BSD : \UEFI_BSD_HII_SAS3.5_IT\DriverSignInfo.txt NA NA Readme for UEFI BSD : \UEFI_BSD_HII_SAS3.5_IT\readme_SAS3.5_UEFI_BSD_HII_X64.txt NA NA UEFI BSD Signed : \UEFI_BSD_HII_SAS3.5_IT\Signed\mpt35sas_ARM.rom 24.00.00.00 08-JULY-22 UEFI BSD : \UEFI_BSD_HII_SAS3.5_IT\mpt35sas_ARM.rom 24.00.00.00 08-JULY-22 Driver Sign Info for UEFI BSD : \UEFI_BSD_HII_SAS3.5_IT\DriverSignInfo.txt NA NA Readme for UEFI BSD : \UEFI_BSD_HII_SAS3.5_IT\readme_SAS3.5_UEFI_BSD_HII_ARM.txt NA NA -------------------------------------------------------------------------------------------------------------------------------------------- Note: Please use STORCLI utility for flashing the firmware which is posted under "Management Software and Tools" section. I suppose i only need the bin file for it mode. and for the storcli package: ********************************************************* Broadcom SAS3.5 StorCLI Utility ********************************************************* Supported Controllers: SAS3004 SAS3008 SAS3108_1 SAS3108_2 SAS3108_3 SAS3108_4 SAS3108_5 SAS3108_6 SAS3216 SAS3224 SAS3316_1 SAS3316_2 SAS3316_3 SAS3316_4 SAS3324_1 SAS3324_2 SAS3324_3 SAS3324_4 STORCLI utility for LSI SAS3.5 Controllers is designed to run from a host. Phase 24 GCA Release Version 007.2307.0000.0000 Release Date : 22-JULY-22 Package contains binaries for Windows x86/x64, Linux x86/x64/PPC64/ARM, EFI, FreeBSD x86/x64 Release Notes: MR_SAS_Unified_StorCLI-v007.2307.0000.0000 pdf binaries in the package are: Description: =========== This is a StorCLI readme file mentioning instructions to use: 1. StorCLI on all the supported operating systems. 2. StorCLI's JSON Schema files. 3. StorCLI's logging feature. Please read before you start using StorCLI executable. Privileges: ========= 1. StorCLI should be installed / executed with administrative / root / super user privileges. 2. Installed/Execution location should have Read/Write/Execute permissions. Windows: ======== Installation / Execution: 1. StorCLI is a executable. Copy-Paste the executable from where you want to execute. Sign verification: command : signtool.exe verify /v /pa <storcli executable name> Notes: 1. signtool.exe is required to validate the StorCLI's signature. Windows-ARM ============ Installation / Execution: 1. StorCLI is a executable. Copy-Paste the executable from where you want to execute. Linux: ====== Installation / Execution : 1. Unzip the StorCLI package. 2. To install the StorCLI RPM, run the rpm -ivh <StorCLI-x.xx-x.noarch.rpm> command. 3. To upgrade the StorCLI RPM, run the rpm -Uvh <StorCLI-x.xx-x.noarch.rpm> command. StorCLI RPM Verification: 1. Import the public key to RPM DB. Command : rpm --import <public-key.asc> 2. Verify the RPM signature. Command : rpm -Kv <storcli-rpm> 3. Install the StorCLI RPM. If imported public key is for the RPM being installed, No warnings should be shown during installation. 4. Please adhere to the steps in the above mentioned order only. Linux-ARM: ========== Installation / Execution : 1. Unzip the StorCLI package. 2. To install the StorCLI RPM, run the rpm -ivh <StorCLI-x.xx-x.aarch64.rpm> command. 3. To upgrade the StorCLI RPM, run the rpm -Uvh <StorCLI-x.xx-x.aarch64.rpm> command. VMware: ====== Installation: 1. The StorCLI VIB Package can be installed using the following syntax : esxcli software vib install -v=<Filepath of the StorCLI VIB> 2. The installed VIB Package can be removed using the following syntax : esxcli software vib remove -n=<VIB Name of StorCLI> 3. All the installed VIB Packages can be listed using following command: esxcli software vib list Notes : 1. VIB under directory "VMwareOP" : This binary is for versions from ESXi6.0 to ESXi6.7. 2. VIB under directory "VMwareOP64" : This binary is for versions from ESXi7.0 and later. FreeBSD: ======== Installation / Execution: 1. Extract the tar archive and execute the StorCLI. Usage policies / Privileges: 1. StorCli or StorCli64 application will not function if the user is trying to run it in CSH, the default shell in FreeBSD. 2. Please ensure that the user has entered the bash shell by executing the command "bash". EFI: ==== Installation / Execution: 1. From the boot menu, choose EFI Shell. 2. Goto the folder containing the StorCLI EFI binaries. 3. Execute StorCLI binaries. EFI-ARM: ======== Installation / Execution: 1. From the boot menu, choose EFI Shell. 2. Goto the folder containing the StorCLI EFI binaries. 3. Execute StorCLI binaries. Ubuntu: ======= Installation: 1. Debian package can be installed using following command syntax : sudo dpkg -i <.deb package> 2. Installed debian package can be verified using following command syntax : dpkg -l | grep -i storcli PowerPC: ======= Open Power Big Endian Distribution: ----------------------------------- Installation / Execution: 1. Unzip the StorCLI package and execute the storcli binary. Open Power Little Endian Distribution: ----------------------------------- Installation / Execution: 1. Unzip the StorCLI package and execute the storcli binary. 2. To install .deb package,Use "dpkg" command. JSON-Schema: ============= Installation: 1. Create a folder under /home/JSON-SCHEMA-FILES. 2. Unzip the JSON-SCHEMA-FILES.zip and copy all the schema files to /home/JSON-SCHEMA-FILES (In any of the operating systems). Command to Schema mapping: 1. Please refer to the Schema_mapping_list.xlsx for command to schema mapping. Logging: ======== 1. While executing StorCLI, Logging is enabled by default. 2. To Turn-off the logging, Place the storcliconf.ini in the current directory and change the DEBUGLEVEL to 0. 3. To change the log level, Place the storcliconf.ini in the current directory and change the DEBUGLEVEL to any desired log level. 4. In case of application crash, Place the storcliconf.ini in the current directory to capture logs. I booted with the hba. It's seen by unraid and so are the disks. But i'd like to verify firmware version and upgrade if needed. I would also like to remove mpt rom edit: i guess i have to go with efi. My server is a hp Z620. As far as i know it's booting in legacy mode for now. Can it boot unraid in efi ? I have no experience with efi. If i understand correctly, i have to : - make a bootable efi boot disk and place storcli.efi and bin file on the disk -disable legacy boot and change boot order to efi disk. Edited September 5 by caplam Quote
JorgeB Posted September 5 Posted September 5 41 minutes ago, caplam said: Can it boot unraid in efi ? Yes, check that and EFI folder exists on the flash drive, if it's EFI- rename it. Quote
caplam Posted September 5 Author Posted September 5 it exists and is named EFI. I'm quite confused about efi booting. I'm reading lots of things about it right now. If my motherboard supports uefi it should boot and offer an efi shell. So i think i have to unplug unraid boot disk and plug only an usb with storcli.efi and the bin file. access it with fs0: and laucnh storcli. If i have not access to shell i should make a boot disk with efi environment as per these instructions on broadcom site Quote
caplam Posted September 5 Author Posted September 5 (edited) i think i'm gonna spend a few hours to understand how to proceed. My server is a hp Z620. It doesn't have an efi shell. So i formatted an usb key (fat32 mbr) with broadcom "LSI Preboot EFI packages for flashing LSI products" I end up with a prompt in efi shell but "storcli show" doesn't detect any controller edit : i spend my afternoon trying with no luck. I had to reset cmos several times. I ended up with boot messages from the hba but when in efi shell storcli doesn't detect any controller. is there another way to proceed than efi shell? Edited September 5 by caplam Quote
caplam Posted September 6 Author Posted September 6 I could use some help I finally managed to use storcli. For that i fire up a kali live with persistent storage on my server. I pass on frustrating things for a newbie like dep package installed in opt and opt is not in PATH and executable is not storcli but storcli64 ....... I finally obtain these with storcli64 /c0 show all CLI Version = 007.2307.0000.0000 July 22, 2022 Operating system = Linux 6.6.9-amd64 Controller = 0 Status = Success Description = None Basics : ====== Controller = 0 Adapter Type = SAS3408(B0) Model = HBA 9400-8e Serial Number = SP72011816 Current System Date/time = 09/05/2024 17:41:50 Concurrent commands supported = 8192 SAS Address = 500062b202b814c0 PCI Address = 00:03:00:00 Version : ======= Firmware Package Build = 00.00.00.00 Firmware Version = 06.00.00.00 Bios Version = 09.03.00.00_02.00.00.00 NVDATA Version = 04.04.00.13 Driver Name = mpt3sas Driver Version = 43.100.00.00 PCI Version : =========== Vendor Id = 0x1000 Device Id = 0xAF SubVendor Id = 0x1000 SubDevice Id = 0x3010 Host Interface = PCIE Device Interface = SAS-12G Bus Number = 3 Device Number = 0 Function Number = 0 Domain ID = 0 Pending Images in Flash : ======================= Image name = No pending images Status : ====== Controller Status = OK Memory Correctable Errors = 0 Memory Uncorrectable Errors = 0 Bios was not detected during boot = No Controller has booted into safe mode = No Controller has booted into certificate provision mode = No Supported Adapter Operations : ============================ Alarm Control = No Cluster Support = No Self Diagnostic = No Deny SCSI Passthrough = No Deny SMP Passthrough = No Deny STP Passthrough = No Support more than 8 Phys = Yes FW and Event Time in GMT = No Support Enclosure Enumeration = Yes Support Allowed Operations = Yes Support Multipath = Yes Support Security = No Support Config Page Model = No Support the OCE without adding drives = No support EKM = No Snapshot Enabled = No Support PFK = No Support PI = No Support Shield State = No Support Set Link Speed = No Support JBOD = No Disable Online PFK Change = No Real Time Scheduler = No Support Reset Now = No Support Emulated Drives = No Support Secure Boot = No Support Platform Security = No Support Package Stamp Mismatch Reporting = No Support PSOC Update = No Support PSOC Part Information = No Support PSOC Version Information = No HwCfg : ===== ChipRevision = B0 BatteryFRU = N/A Front End Port Count = 1 Backend Port Count = 9 Serial Debugger = Absent NVRAM Size = 0KB Flash Size = 16MB On Board Memory Size = 0MB On Board Expander = Absent Temperature Sensor for ROC = Present Temperature Sensor for Controller = Absent Current Size of CacheCade (GB) = 0 Current Size of FW Cache (MB) = 0 ROC temperature(Degree Celsius) = 70 When i try to flash it with bin file from P24 package i've got an error "invalid file" Do i need to follow an upgrade path as it seems hba is using old bios? Quote
Wody Posted September 15 Posted September 15 On 9/6/2024 at 10:58 AM, caplam said: When i try to flash it with bin file from P24 package i've got an error "invalid file" Do i need to follow an upgrade path as it seems hba is using old bios? Make sure you have the package called 9400_8e_Pkg_P24. For Unraid, you only need the firmware, but if there is a BIOS on there or the UEFI-version of it, you need to flash those too. You can also use storcli on unraid, and if you have unpacked it already, you can just copy the storcli64 file over, no other files are needed. If you put it in for example /usr/bin you don't need to use the path, but if you put it in the current directory, you need to use ./storcli64 with the commands. If you want to back up everything from the card, just in case, use the following: storcli /c0 get bios file=backup_bios storcli /c0 get firmware file=backup_firmware storcli /c0 get mpb file=backup_mpb storcli /c0 get fwbackup file=backup_fwbackup storcli /c0 get nvdata file=backup_nvdata storcli /c0 get flash file=backup_flash Then to flash the firmware, assuming the firmware and bios files are in the current directory. For the firmware: storcli /c0 download file=HBA_9400-8e_SAS_SATA_Profile.bin For the BIOS: storcli /c0 download bios file=mpt35sas_legacy.rom For the UEFI interface: storcli /c0 download efibios file=mpt35sas_x64.rom After this, Broadcom says you'll want to power down the computer, remove power, wait half a minute or so, and apply power again. However, powering down, and waiting a bit and starting up again works too. Just restarting or resetting doesn't always work, because the card may stay powered on. Quote
caplam Posted September 15 Author Posted September 15 great post. what version of storcli do i have to use ? There is no bios version. There are version for freebsd, ubuntu and a linux rpm package. The other ones are for windows, arm, linux ppc, efi and vmware. I guess i could have to convert rpm to tgz. Quote
caplam Posted September 15 Author Posted September 15 (edited) I tried with the rpm file. I extracted it 7z. The executable is storcli64 ans is on my usb key. I ran all commands with ./storcli64 i can view the controller details with ./storcli64 /c0 show: CLI Version = 007.2307.0000.0000 July 22, 2022 Operating system = Linux 6.1.106-Unraid Controller = 0 Status = Success Description = None Product Name = HBA 9400-8e Serial Number = SP72011816 SAS Address = 500062b202b814c0 PCI Address = 00:03:00:00 System Time = 09/15/2024 15:46:35 FW Package Build = 00.00.00.00 FW Version = 06.00.00.00 BIOS Version = 09.03.00.00_02.00.00.00 NVDATA Version = 04.04.00.13 Driver Name = mpt3sas Driver Version = 43.100.00.00 Bus Number = 3 Device Number = 0 Function Number = 0 Domain ID = 0 Vendor Id = 0x1000 Device Id = 0xAF SubVendor Id = 0x1000 SubDevice Id = 0x3010 Board Name = HBA 9400-8e Board Assembly = 03-50013-17004 Board Tracer Number = SP72011816 Security Protocol = None Physical Drives = 4 PD LIST : ======= --------------------------------------------------------- EID:Slt DID State DG Size Intf Med SED PI SeSz Sp --------------------------------------------------------- 0:8 5 JBOD - 5.458 TB Unknown HDD - - 512B - 0:9 3 JBOD - 3.638 TB Unknown HDD - - 512B - 0:10 2 JBOD - 3.638 TB Unknown HDD - - 512B - 0:11 4 JBOD - 3.638 TB Unknown HDD - - 512B - --------------------------------------------------------- EID-Enclosure Device ID|Slt-Slot No|DID-Device ID|DG-DriveGroup UGood-Unconfigured Good|UBad-Unconfigured Bad|Intf-Interface Med-Media Type|SED-Self Encryptive Drive|PI-Protection Info SeSz-Sector Size|Sp-Spun|U-Up|D-Down|T-Transition Requested Boot Drive = Not Set but when i tried to flash the firmware i have: root@Z620:/mnt/disks/ESD-USB/lsi# ./storcli64 /c0 download file=HBA_9400-8e_SAS_SATA_Profile.bin Downloading image.Please wait... CLI Version = 007.2307.0000.0000 July 22, 2022 Operating system = Linux 6.1.106-Unraid Controller = 0 Status = Failure Description = The firmware flash image is invalid when i tried the bios: root@Z620:/mnt/disks/ESD-USB/lsi# ./storcli64 /c0 download bios file=mpt35sas_legacy.rom Downloading image.Please wait... CLI Version = 007.2307.0000.0000 July 22, 2022 Operating system = Linux 6.1.106-Unraid Controller = 0 Status = Failure Description = Flash failed. i redownloaded from broadcom site to be sure but with the same result. edit: i tried with P7 version (for both storcli and firmware). It runs for 30s and ends up with failure. when i try with P24 i have a failure immediately. Edited September 15 by caplam Quote
caplam Posted September 16 Author Posted September 16 here is the storcli log file. Nothing obvious except response code but i don't know what it means Sun Sep 15 17:57:31.383 2024 : CtMain::main processing for command=/ c 0 download file=../P24/HBA_9400-8e_SAS_SATA_Profile.bin Sun Sep 15 17:57:31.383 2024 : Entering LinuxControllerExplorer::explore Sun Sep 15 17:57:31.383 2024 : Entering LinuxControllerExplorer::getCtrlCount Sun Sep 15 17:57:31.383 2024 : LinuxControllerExplorer::getCtrlCount _hDvr=-1 _hDvrSwr =-1 Sun Sep 15 17:57:31.383 2024 : LinuxControllerExplorer::explore ctrlCount=1 Sun Sep 15 17:57:31.383 2024 : returning LinuxControllerExplorer::explore ctrlIdListPtr Sun Sep 15 17:57:31.383 2024 : SlItControllerExplorer::explore - Entering Sun Sep 15 17:57:31.383 2024 : StorelibItDp::processLibCommand SL request sent Sun Sep 15 17:57:31.385 2024 : StorelibItDp::processLibCommand SL responded with retcode=0 Sun Sep 15 17:57:31.385 2024 : StorelibItDp::processLibCommand SL request sent Sun Sep 15 17:57:31.385 2024 : StorelibItDp::processLibCommand SL responded with retcode=0 Sun Sep 15 17:57:31.385 2024 : SlItControllerExplorer::explore - Getting the StoreLIB instance for SAS3.5 IT controller Sun Sep 15 17:57:31.385 2024 : StorelibItDp::processLibCommand SL request sent Sun Sep 15 17:57:31.463 2024 : StorelibItDp::processLibCommand SL responded with retcode=0 Sun Sep 15 17:57:31.463 2024 : SlItControllerExplorer::explore - Issuing SL_GET_CTRL_LIST to SLIT Sun Sep 15 17:57:31.463 2024 : StorelibItDp::processLibCommand SL request sent Sun Sep 15 17:57:31.463 2024 : StorelibItDp::processLibCommand SL responded with retcode=0 Sun Sep 15 17:57:31.463 2024 : SlItControllerExplorer::explore - Issuing SL_GET_CTRL_LIST to SLIT - retCode:0x0 Sun Sep 15 17:57:31.463 2024 : SlItControllerExplorer::explore - Controller count:1 Sun Sep 15 17:57:31.463 2024 : SlItControllerExplorer::explore - Controller count index:0 Sun Sep 15 17:57:31.463 2024 : SlItControllerExplorer::explore - Issuing SL_GET_PCI_INFO to SLIT Sun Sep 15 17:57:31.463 2024 : StorelibItDp::processLibCommand SL request sent Sun Sep 15 17:57:31.464 2024 : StorelibItDp::processLibCommand SL responded with retcode=0 Sun Sep 15 17:57:31.464 2024 : SlItControllerExplorer::explore - Issuing SL_GET_PCI_INFO to SLIT - retCode:0x0 Sun Sep 15 17:57:31.464 2024 : SlItControllerExplorer::explore - Domain:0 Bus:3 device:0 Function:0 Sun Sep 15 17:57:31.464 2024 : SlItControllerExplorer::explore - Issuing SL_GET_CTRL_INFO to SLIT Sun Sep 15 17:57:31.464 2024 : StorelibItDp::processLibCommand SL request sent Sun Sep 15 17:57:31.465 2024 : StorelibItDp::processLibCommand SL responded with retcode=0 Sun Sep 15 17:57:31.465 2024 : SlItControllerExplorer::explore - Issuing SL_GET_CTRL_INFO to SLIT - retCode:0x0 Sun Sep 15 17:57:31.465 2024 : SlItControllerExplorer::explore - Adapter is good Sun Sep 15 17:57:31.465 2024 : LinuxMfiDataProvider::fireIoctl DCMD=1010000 mbox.w[0]=1 mbox.w[1]=0 mbox.w[2]=0 Sun Sep 15 17:57:31.465 2024 : LinuxMfiDataProvider::fireIoctl send_ioctl retcode=-1 cmdStatus=255 Sun Sep 15 17:57:31.465 2024 : LinuxMfiDataProvider::fireIoctl returning with =-1 errno=9 Sun Sep 15 17:57:31.465 2024 : StorelibItDp::processLibCommand SL request sent Sun Sep 15 17:57:31.466 2024 : StorelibItDp::processLibCommand SL responded with retcode=0 Sun Sep 15 17:57:31.466 2024 : StorelibItDp::processLibCommand SL request sent Sun Sep 15 17:57:31.467 2024 : StorelibItDp::processLibCommand SL responded with retcode=0 Sun Sep 15 17:57:31.469 2024 : Entering MWCliRootCp::process ver=007.2307.0000.0000 July 22, 2022 copyright=2022 Sun Sep 15 17:57:31.469 2024 : initializing the RaidManager Instance Sun Sep 15 17:57:31.469 2024 : Entering ITCtFlshCp::process Sun Sep 15 17:57:31.469 2024 : Entering ITCtFlshCp::getFileLength Sun Sep 15 17:57:31.469 2024 : Exiting ITCtFlshCp::getFileLength - File length:1854468 Sun Sep 15 17:57:31.472 2024 : Entering ITUtils::getSlCtrlInfo Sun Sep 15 17:57:31.472 2024 : StorelibItDp::processLibCommand SL request sent Sun Sep 15 17:57:31.473 2024 : StorelibItDp::processLibCommand SL responded with retcode=0 Sun Sep 15 17:57:31.473 2024 : Exiting ITUtils::getSlCtrlInfo Sun Sep 15 17:57:31.473 2024 : ITCtFlshCp::process - Get controller info retCode:0 Sun Sep 15 17:57:31.473 2024 : ITCtFlshCp::process - Is controller valid:0 Sun Sep 15 17:57:31.473 2024 : ITCtFlshCp::process - Firmware found:1 Sun Sep 15 17:57:31.473 2024 : ITCtFlshCp::process - It's a package file Sun Sep 15 17:57:31.473 2024 : ITCtFlshCp::process - Signature passed Sun Sep 15 17:57:31.473 2024 : ITCtFlshCp::process - Is Aero image:0 Sun Sep 15 17:57:31.475 2024 : StorelibItDp::processLibCommand SL request sent Sun Sep 15 17:57:31.475 2024 : StorelibItDp::processLibCommand SL responded with retcode=32783 Sun Sep 15 17:57:31.476 2024 : Entering MWCliRootCp::handleOuput retCode=32783, DriveFull=0 Sun Sep 15 17:57:31.476 2024 : MWCliRootCp::process processed for subtokenID=105 errorCode=32783 Sun Sep 15 17:57:31.476 2024 : Entering MWCliRootCp::handleOuput retCode=32783, DriveFull=0 Sun Sep 15 17:57:31.476 2024 : StorelibItDp::processLibCommand SL request sent Sun Sep 15 17:57:31.482 2024 : StorelibItDp::processLibCommand SL responded with retcode=0 Sun Sep 15 17:57:31.482 2024 : StorelibItDp::processLibCommand SL request sent Sun Sep 15 17:57:31.482 2024 : StorelibItDp::processLibCommand SL responded with retcode=0 Sun Sep 15 17:57:31.483 2024 : CtMain::main command completed with retcode=32783 Sun Sep 15 18:00:30.436 2024 : CtMain::main processing for command=/ c 0 download file=../P24/HBA_9400-8e_SAS_SATA_Profile.bin Sun Sep 15 18:00:30.436 2024 : Entering LinuxControllerExplorer::explore Sun Sep 15 18:00:30.437 2024 : Entering LinuxControllerExplorer::getCtrlCount Sun Sep 15 18:00:30.437 2024 : LinuxControllerExplorer::getCtrlCount _hDvr=-1 _hDvrSwr =-1 Sun Sep 15 18:00:30.437 2024 : LinuxControllerExplorer::explore ctrlCount=1 Sun Sep 15 18:00:30.437 2024 : returning LinuxControllerExplorer::explore ctrlIdListPtr Sun Sep 15 18:00:30.437 2024 : SlItControllerExplorer::explore - Entering Sun Sep 15 18:00:30.437 2024 : StorelibItDp::processLibCommand SL request sent Sun Sep 15 18:00:30.438 2024 : StorelibItDp::processLibCommand SL responded with retcode=0 Sun Sep 15 18:00:30.438 2024 : StorelibItDp::processLibCommand SL request sent Sun Sep 15 18:00:30.438 2024 : StorelibItDp::processLibCommand SL responded with retcode=0 Sun Sep 15 18:00:30.438 2024 : SlItControllerExplorer::explore - Getting the StoreLIB instance for SAS3.5 IT controller Sun Sep 15 18:00:30.439 2024 : StorelibItDp::processLibCommand SL request sent Sun Sep 15 18:00:30.516 2024 : StorelibItDp::processLibCommand SL responded with retcode=0 Sun Sep 15 18:00:30.517 2024 : SlItControllerExplorer::explore - Issuing SL_GET_CTRL_LIST to SLIT Sun Sep 15 18:00:30.517 2024 : StorelibItDp::processLibCommand SL request sent Sun Sep 15 18:00:30.517 2024 : StorelibItDp::processLibCommand SL responded with retcode=0 Sun Sep 15 18:00:30.517 2024 : SlItControllerExplorer::explore - Issuing SL_GET_CTRL_LIST to SLIT - retCode:0x0 Sun Sep 15 18:00:30.517 2024 : SlItControllerExplorer::explore - Controller count:1 Sun Sep 15 18:00:30.517 2024 : SlItControllerExplorer::explore - Controller count index:0 Sun Sep 15 18:00:30.517 2024 : SlItControllerExplorer::explore - Issuing SL_GET_PCI_INFO to SLIT Sun Sep 15 18:00:30.517 2024 : StorelibItDp::processLibCommand SL request sent Sun Sep 15 18:00:30.517 2024 : StorelibItDp::processLibCommand SL responded with retcode=0 Sun Sep 15 18:00:30.517 2024 : SlItControllerExplorer::explore - Issuing SL_GET_PCI_INFO to SLIT - retCode:0x0 Sun Sep 15 18:00:30.517 2024 : SlItControllerExplorer::explore - Domain:0 Bus:3 device:0 Function:0 Sun Sep 15 18:00:30.517 2024 : SlItControllerExplorer::explore - Issuing SL_GET_CTRL_INFO to SLIT Sun Sep 15 18:00:30.517 2024 : StorelibItDp::processLibCommand SL request sent Sun Sep 15 18:00:30.518 2024 : StorelibItDp::processLibCommand SL responded with retcode=0 Sun Sep 15 18:00:30.518 2024 : SlItControllerExplorer::explore - Issuing SL_GET_CTRL_INFO to SLIT - retCode:0x0 Sun Sep 15 18:00:30.519 2024 : SlItControllerExplorer::explore - Adapter is good Sun Sep 15 18:00:30.519 2024 : LinuxMfiDataProvider::fireIoctl DCMD=1010000 mbox.w[0]=1 mbox.w[1]=0 mbox.w[2]=0 Sun Sep 15 18:00:30.519 2024 : LinuxMfiDataProvider::fireIoctl send_ioctl retcode=-1 cmdStatus=255 Sun Sep 15 18:00:30.519 2024 : LinuxMfiDataProvider::fireIoctl returning with =-1 errno=9 Sun Sep 15 18:00:30.519 2024 : StorelibItDp::processLibCommand SL request sent Sun Sep 15 18:00:30.519 2024 : StorelibItDp::processLibCommand SL responded with retcode=0 Sun Sep 15 18:00:30.519 2024 : StorelibItDp::processLibCommand SL request sent Sun Sep 15 18:00:30.520 2024 : StorelibItDp::processLibCommand SL responded with retcode=0 Sun Sep 15 18:00:30.522 2024 : Entering MWCliRootCp::process ver=007.2307.0000.0000 July 22, 2022 copyright=2022 Sun Sep 15 18:00:30.522 2024 : initializing the RaidManager Instance Sun Sep 15 18:00:30.522 2024 : Entering ITCtFlshCp::process Sun Sep 15 18:00:30.522 2024 : Entering ITCtFlshCp::getFileLength Sun Sep 15 18:00:30.522 2024 : Exiting ITCtFlshCp::getFileLength - File length:1854468 Sun Sep 15 18:00:30.526 2024 : Entering ITUtils::getSlCtrlInfo Sun Sep 15 18:00:30.526 2024 : StorelibItDp::processLibCommand SL request sent Sun Sep 15 18:00:30.527 2024 : StorelibItDp::processLibCommand SL responded with retcode=0 Sun Sep 15 18:00:30.527 2024 : Exiting ITUtils::getSlCtrlInfo Sun Sep 15 18:00:30.527 2024 : ITCtFlshCp::process - Get controller info retCode:0 Sun Sep 15 18:00:30.527 2024 : ITCtFlshCp::process - Is controller valid:0 Sun Sep 15 18:00:30.527 2024 : ITCtFlshCp::process - Firmware found:1 Sun Sep 15 18:00:30.527 2024 : ITCtFlshCp::process - It's a package file Sun Sep 15 18:00:30.527 2024 : ITCtFlshCp::process - Signature passed Sun Sep 15 18:00:30.527 2024 : ITCtFlshCp::process - Is Aero image:0 Sun Sep 15 18:00:30.528 2024 : StorelibItDp::processLibCommand SL request sent Sun Sep 15 18:00:30.529 2024 : StorelibItDp::processLibCommand SL responded with retcode=32783 Sun Sep 15 18:00:30.529 2024 : Entering MWCliRootCp::handleOuput retCode=32783, DriveFull=0 Sun Sep 15 18:00:30.529 2024 : MWCliRootCp::process processed for subtokenID=105 errorCode=32783 Sun Sep 15 18:00:30.529 2024 : Entering MWCliRootCp::handleOuput retCode=32783, DriveFull=0 Sun Sep 15 18:00:30.529 2024 : StorelibItDp::processLibCommand SL request sent Sun Sep 15 18:00:30.536 2024 : StorelibItDp::processLibCommand SL responded with retcode=0 Sun Sep 15 18:00:30.536 2024 : StorelibItDp::processLibCommand SL request sent Sun Sep 15 18:00:30.536 2024 : StorelibItDp::processLibCommand SL responded with retcode=0 Sun Sep 15 18:00:30.536 2024 : CtMain::main command completed with retcode=32783 Quote
Wody Posted September 19 Posted September 19 On 9/15/2024 at 4:13 PM, caplam said: FW Package Build = 00.00.00.00 FW Version = 06.00.00.00 I'm not quoting correctly, but this is what I'm a bit concerned about. For P24 it says FW Package Build = 24.00.00.00 FW Version = 24.00.00.00 Note how yours says 0 and 6, while both say 24. It could be that it is something they added later, and that it is normal, so I tried flashing version P6 to see but it won't flash older firmware, so I can't verify if that is normal or not. Try flashing the P6 version first, and see if it will change the numbers, instead of P7. Quote
caplam Posted September 19 Author Posted September 19 (edited) Yes very strange and the bios version is odd too: FW Package Build = 00.00.00.00 FW Version = 06.00.00.00 BIOS Version = 09.03.00.00_02.00.00.00 Firwmare 6.00 is from P6 package Bios 09.03 seems to be from P2 package and driver version 43.100 is from unraid. Hba is working correctly so far but i'd like to make that clear. edit: maybe i should first update bios with version from P6 package and then proceed with P7 and P24. I will end up with all package version on my hdd Edited September 19 by caplam Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.