Error Failed To Initialise Pal
Contents |
to perform a firmware update on an LSI HBAs (eg. LSI 9211/9200/9207) on X9/H8 motherboards. Contents 1 Firmware update via DOS failed to initialise d3d11 error code 0 / UEFI 1.1 Firmware Update on X9 motherboards under DOS 2 failed to initialise steam Firmware update on a motherboard without an onboard SAS Controller 3 Firmware update on a motherboard with failed to initialize pal onboard SAS controller Firmware update via DOS / UEFI A firmware update via DOS is only possible when using H8 motherboards. With X9 motheroards an error message occurs failed to initialize pal exiting program during the writing process, due to the limited "option ROM". The writing process is the same with UEFI as with DOS, only the name of the writing tool is different (UEFI: sas2flash.efi, DOS: sas2flsh.exe). If the HBA-firmware is not only updated, rather the IT-firmware is written over the IR-firmware (or vise versa) the existing firmware should be
Sas2flsh Failed To Initialize Pal
deleted before the update from the controller. For more information see: Flashing IT firmware over IR firmware (and vice versa) for SAS HBAs. The command to delete the existing firmware with UEFI is: sas2flash.efi-o-e 6 (-cpci "PCI address"). Firmware Update on X9 motherboards under DOS When attempting to update the firmware of HBAs under DOS, the writing does not start and the following error message is given: "ERROR: Failed to initialize PAL. Exiting program". All X9 boards have a limited "option ROM", in which case it is not possible to flash the LSI HBAs firmware from DOS. An alternative would be to run the firmware update from the UEFI BIOS. Firmware update on a motherboard without an onboard SAS Controller Motherboards need to be written on UEFI: X9SCM-F X9DRi-F Motherboards need to be written via DOS: H8SCM-F The following screenshots illustrate the steps for an HBA firmware update with the UEFI-Shell: 1. Select "UEFI: Build-in EFI Shell" of the "Save & Exit" menu item 2. Select the medium
Joined: Jan 1, 2012 Messages: 19 Thanks Received: 3 Trophy Points: 6 I've just upgrade to FreeNAS 9.3 and saw a warning
Failed To Initialize Pal M1015
error regarding firmware and driver version mismatch. I went through a lot of sas2flash failed to initialize pal internet forum trying to upgrade my my LSI 9211-8i to V16 IT, but had no luck. I currently do sas2flash.efi download not have a system with a BIOS that supports EFI Shell. I tried upgrade via different methods: - FreeNAS SAS2FLASH (can't convert IR to IT) - FreeDOS (Failed to initialize PAL. https://www.thomas-krenn.com/en/wiki/Firmware_Update_of_LSI_9xxx_HBAs_on_H8_/_X9-motherboards Exiting program) - Windows Boot Disk (Erase flash command not Supported on this platform.) I've read that is highly recommended to have the firmware version to match the driver version. So I was wondering if a better way for upgrade / re-flash can be provided? YTKColumba, May 10, 2015 #1 SweetAndLow Sweet'NASty Joined: Nov 6, 2013 Messages: 3,104 Thanks Received: 345 Trophy https://forums.freenas.org/index.php?threads/solved-sas2flash-easier-alternative.30789/ Points: 81 Occupation: Software Development Engineer you need to get the file that is called sas2flash.efi and place that along with the firmware file that ends in .bin onto the root of a flash drive then when in the bios the sas2flash.efi shell will appear as a boot option. Once you boot from this you can follow the directions to flash as normal. My motherboard didn't have a built in efi shell and i spent way to much time learning about everything before i found this solution. Show : First System Build FreeNAS-9.2.1.9-RELEASE-x64 || Platform Intel(R) Xeon(R) CPU E3-1230 V3 @ 3.3GHz Memory Crucial 1600Mhz 16301MB ECC CT2KIT102472BD160B || Chassis Fractal Design Node 304 Disk WD-Red - 6x3TB || Motherboard ASRock E3C226D2I || UPS CP1000CPFLCD Show : Current System Build FreeNAS 9.3.1 || CPU: Intel Xeon e5-1650 || 4x16GB Samsung DDR4-2133 M393A2G40DB0-CPB || Supermicro 846e16-r1200b || X10SRL Show : Recommended Reading cyberjock's: Hardware recommendations (read this first) dlavigne's: ZFS Primer cyberjock's: Slideshow explaining VDev, zpool, ZIL and L2ARC for noobs! jgreco's: Building, Burn-In, and Testing your FreeNAS system qwertymodo's: [How To] Hard Drive Burn-In Testing DrKK's: H
Technology - unRAID Server Community » Community » Storage Devices and Controllers » LSI Controller FW updates IR/IT modes « previous https://lime-technology.com/forum/index.php?topic=12767.120 next » Send this topic Print Pages: 1 ... 7 8 [9] 10 11 ... 74 Go Down Author Topic: LSI Controller FW updates IR/IT modes (Read 571223 times) jkm9000 Member Posts: 50 Re: LSI Controller FW updates IR/IT modes « Reply #120 on: August 30, 2011, 04:28:44 PM » Quote from: Zeron on August 30, 2011, 03:22:31 PMIf you get failed to the failed to initialize pal message, you will have to do the flash using a motherboard with a different chipset. I had the same problem. LSI documents the issue here: http://kb.lsi.com/KnowledgebaseArticle15807.aspx and here: http://kb.lsi.com/KnowledgebaseArticle16266.aspxI had the same problem on my Intel server board, but it worked fin on the third PC I tired it in.Thanks. Luckily I have a SuperMicro failed to initialize C2SEE and some spare parts so I can give that a try. Tried several versions of sas2flash for linux but none see that card although it shows up via lspci. So, I'm not giving up! Logged jkm9000 Member Posts: 50 Re: LSI Controller FW updates IR/IT modes « Reply #121 on: August 30, 2011, 06:48:50 PM » Same error with the C2SEE Is it possible there is something else going on here or the only two motherboards I have won't work with this? Card is about to go out the window. Logged Zeron Community Developer Full Member Posts: 161 Re: LSI Controller FW updates IR/IT modes « Reply #122 on: August 30, 2011, 07:19:22 PM » Quote from: jkm9000 on August 30, 2011, 06:48:50 PMSame error with the C2SEE Is it possible there is something else going on here or the only two motherboards I have won't work with this? Card is about to go out the window.The motherboard I tried it on had Intel Q45 and G43 chipsets. The one it worked on was a HP AMD based