`<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Dec 9, 2014 at 9:51 AM, Dominik Hassler <span dir="ltr"><<a href="mailto:hasslerd@gmx.li" target="_blank">hasslerd@gmx.li</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Chip,<br>
<br>
when I had to reflash an onboard LSI2308 I used the UEFI shell. No<br>
fiddling around with boot disks etc.<br>
<br>
Not sure, if it is applicable to your problem.<br></blockquote><div><br></div><div>That was the trick. Under DOS I kept getting "ERROR: Failed to initialize PAL." Turns out this is a problem on X9 and newer Supermicro boards.<br><br></div><div>With the efi sas2flash version on a USB stick it was quite easy. The system BIOS has a boot override to drop into the UEFI shell from there I could see the USB stick and run the erase and flash.<br><br>Thanks for everyone's input on this. Hopefully I will only be upgrading in the future and can stick to the Solaris version of sas2flash.<br><br></div><div>-Chip<br><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<span class=""><br>
On 12/09/2014 03:49 PM, Schweiss, Chip wrote:<br>
> I'm still fighting this.<br>
><br>
> Under OmniOS the erase function is disabled in sas2flash for solaris.<br>
><br>
> I couldn't seem to find an iso bootable DOS that I could stage files<br>
> in. FreeDOS1.0 won't mount the CD, 1.1 got rid of the live mode.<br>
> Tried a Linux rescue CD and I get " ERROR: Erase Flash Operation<br>
> Failed!" Tried both P18 sas2flash and P20 sas2flash.<br>
><br>
> What OS environment are you running this in?<br>
><br>
><br>
><br>
> On Tue, Dec 9, 2014 at 3:06 AM, Filip Marvan <<a href="mailto:filip.marvan@aira.cz">filip.marvan@aira.cz</a><br>
</span>> <mailto:<a href="mailto:filip.marvan@aira.cz">filip.marvan@aira.cz</a>>> wrote:<br>
><br>
> Hi,____<br>
><br>
> __ __<br>
><br>
> first you have to erase P20 firmware with:____<br>
><br>
> __ __<br>
><br>
> sas2flsh -o -e 6____<br>
><br>
> __ __<br>
><br>
> now do not reboot(!) and flash P18 with____<br>
><br>
> __ __<br>
><br>
> sas2flsh -f XXXXXX.bin -b mptsas2.rom____<br>
><br>
> __ __<br>
><br>
> Filip____<br>
><br>
> __ __<br>
><br>
> __ __<br>
><br>
> *From:*OmniOS-discuss<br>
> [mailto:<a href="mailto:omnios-discuss-bounces@lists.omniti.com">omnios-discuss-bounces@lists.omniti.com</a><br>
> <mailto:<a href="mailto:omnios-discuss-bounces@lists.omniti.com">omnios-discuss-bounces@lists.omniti.com</a>>] *On Behalf Of<br>
> *Schweiss, Chip<br>
> *Sent:* Monday, December 08, 2014 08:09 AM<br>
> *To:* Filip Marvan<br>
> *Cc:* <a href="mailto:omnios-discuss@lists.omniti.com">omnios-discuss@lists.omniti.com</a><br>
> <mailto:<a href="mailto:omnios-discuss@lists.omniti.com">omnios-discuss@lists.omniti.com</a>><br>
> *Subject:* Re: [OmniOS-discuss] Parity error on path mpt_sas2____<br>
><br>
> __ __<br>
<span class="">><br>
> I've got some new LSI HBAs I'm trying to downgrade from firmware<br>
</span>> version 20 to 18.____<br>
<span class="">><br>
> I'm getting errors when trying to downgrade:<br>
><br>
> Attempting to flash firmware to LSI SAS SAS2308_2(D1) :<br>
><br>
> Executing Operation: Flash Firmware Image<br>
><br>
> Firmware Image has a Valid Checksum.<br>
> Firmware Version 18.00.00.00<br>
> Firmware Image compatible with Controller.<br>
><br>
> Valid NVDATA Image found.<br>
> NVDATA Version 11.00.00.00<br>
> Checking for a compatible NVData image...<br>
><br>
> NVDATA Device ID and Chip Revision match verified.<br>
> ERROR: Cannot downgrade NVDATA version 14.00.00.06<br>
> to 11.00.110000.00.<br>
><br>
> ERROR: Failed to get valid NVDATA image from File!<br>
><br>
</span>> Firmware Image Validation Failed!____<br>
<span class="">><br>
> Tried downgrading bios:<br>
><br>
> Attempting to flash Boot Service to LSI SAS SAS2308_2(D1) :<br>
><br>
> Validating BIOS Image...<br>
><br>
> BIOS Header Signature is Valid<br>
><br>
> BIOS Image has a Valid Checksum.<br>
><br>
> BIOS PCI Structure Signature Valid.<br>
><br>
> BIOS Image Compatible with the SAS Controller.<br>
><br>
> Attempting to Flash BIOS Image...<br>
><br>
> BIOS Version in flash : 07.39.00.00<br>
> BIOS Version from File : 07.35.00.00<br>
> Skipping flash since file version is not greater<br>
> than existing.<br>
><br>
</span>> Flash BIOS Image Failed!____<br>
<span class="">><br>
> I've tried sas2flash from P20 and P18.<br>
><br>
</span>> Can someone fill me in on the trick to downgrade? ____<br>
><br>
> -Chip____<br>
><br>
> __ __<br>
><br>
> __ __<br>
<span class="">><br>
> On Thu, Nov 27, 2014 at 9:03 AM, Filip Marvan <<a href="mailto:filip.marvan@aira.cz">filip.marvan@aira.cz</a><br>
</span>> <mailto:<a href="mailto:filip.marvan@aira.cz">filip.marvan@aira.cz</a>>> wrote:____<br>
<span class="">><br>
> Thank you for your help Aaron! I downgraded firmware to P18 and<br>
</span>> there are no more errors today.____<br>
><br>
> It seems, that there is something bad with P20 firmware!____<br>
><br>
> ____<br>
><br>
> You saved me a lot of time J____<br>
><br>
> ____<br>
><br>
> Filip____<br>
><br>
> ____<br>
><br>
> ____<br>
><br>
> *From:*Aaron Curry [mailto:<a href="mailto:asc1111@gmail.com">asc1111@gmail.com</a><br>
> <mailto:<a href="mailto:asc1111@gmail.com">asc1111@gmail.com</a>>]<br>
<span class="">> *Sent:* Tuesday, November 25, 2014 5:46 PM<br>
> *To:* Filip Marvan<br>
> *Cc:* Dan McDonald; <a href="mailto:omnios-discuss@lists.omniti.com">omnios-discuss@lists.omniti.com</a><br>
</span>> <mailto:<a href="mailto:omnios-discuss@lists.omniti.com">omnios-discuss@lists.omniti.com</a>><br>
> *Subject:* Re: [OmniOS-discuss] Parity error on path mpt_sas2____<br>
><br>
> ____<br>
<span class="">><br>
> I had this exact same problem recently when setting up a new home<br>
> server... same controller, same firmware (P20). The errors were on<br>
> all disks attached to the controller, but only on high read<br>
> activity. Writes did not generate the errors. I downgraded the<br>
> firmware to P18 (which is what we are using at work) and the errors<br>
> went away. Has anyone had success with this controller and the P20<br>
</span>> firmware?____<br>
><br>
> ____<br>
><br>
> Aaron____<br>
><br>
> ____<br>
<span class="">><br>
> On Tue, Nov 25, 2014 at 8:30 AM, Filip Marvan <<a href="mailto:filip.marvan@aira.cz">filip.marvan@aira.cz</a><br>
</span>> <mailto:<a href="mailto:filip.marvan@aira.cz">filip.marvan@aira.cz</a>>> wrote:____<br>
<span class="">><br>
> Hi Dan,<br>
><br>
> thanks for reply.<br>
> Yes, errors are on all 5 disks in the same RAIDZ pool. No<br>
> problem on other<br>
> disks in different pool but on the same SAS cable.<br>
> So maybe I only had bad luck with that disks.<br>
><br>
> Filip<br>
><br>
><br>
> _______________________________________________<br>
> OmniOS-discuss mailing list<br>
> <a href="mailto:OmniOS-discuss@lists.omniti.com">OmniOS-discuss@lists.omniti.com</a><br>
</span>> <mailto:<a href="mailto:OmniOS-discuss@lists.omniti.com">OmniOS-discuss@lists.omniti.com</a>><br>
> <a href="http://lists.omniti.com/mailman/listinfo/omnios-discuss____" target="_blank">http://lists.omniti.com/mailman/listinfo/omnios-discuss____</a><br>
><br>
> ____<br>
><br>
><br>
> _______________________________________________<br>
> OmniOS-discuss mailing list<br>
> <a href="mailto:OmniOS-discuss@lists.omniti.com">OmniOS-discuss@lists.omniti.com</a> <mailto:<a href="mailto:OmniOS-discuss@lists.omniti.com">OmniOS-discuss@lists.omniti.com</a>><br>
> <a href="http://lists.omniti.com/mailman/listinfo/omnios-discuss____" target="_blank">http://lists.omniti.com/mailman/listinfo/omnios-discuss____</a><br>
><br>
> __ __<br>
<div class=""><div class="h5">><br>
><br>
><br>
><br>
> _______________________________________________<br>
> OmniOS-discuss mailing list<br>
> <a href="mailto:OmniOS-discuss@lists.omniti.com">OmniOS-discuss@lists.omniti.com</a><br>
> <a href="http://lists.omniti.com/mailman/listinfo/omnios-discuss" target="_blank">http://lists.omniti.com/mailman/listinfo/omnios-discuss</a><br>
><br>
</div></div></blockquote></div><br></div></div>
`