On Tue, Dec 9, 2014 at 9:51 AM, Dominik Hassler <[email protected]> wrote:
> Chip, > > when I had to reflash an onboard LSI2308 I used the UEFI shell. No > fiddling around with boot disks etc. > > Not sure, if it is applicable to your problem. > 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. 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. 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. -Chip > On 12/09/2014 03:49 PM, Schweiss, Chip wrote: > > I'm still fighting this. > > > > Under OmniOS the erase function is disabled in sas2flash for solaris. > > > > I couldn't seem to find an iso bootable DOS that I could stage files > > in. FreeDOS1.0 won't mount the CD, 1.1 got rid of the live mode. > > Tried a Linux rescue CD and I get " ERROR: Erase Flash Operation > > Failed!" Tried both P18 sas2flash and P20 sas2flash. > > > > What OS environment are you running this in? > > > > > > > > On Tue, Dec 9, 2014 at 3:06 AM, Filip Marvan <[email protected] > > <mailto:[email protected]>> wrote: > > > > Hi,____ > > > > __ __ > > > > first you have to erase P20 firmware with:____ > > > > __ __ > > > > sas2flsh -o -e 6____ > > > > __ __ > > > > now do not reboot(!) and flash P18 with____ > > > > __ __ > > > > sas2flsh -f XXXXXX.bin -b mptsas2.rom____ > > > > __ __ > > > > Filip____ > > > > __ __ > > > > __ __ > > > > *From:*OmniOS-discuss > > [mailto:[email protected] > > <mailto:[email protected]>] *On Behalf Of > > *Schweiss, Chip > > *Sent:* Monday, December 08, 2014 08:09 AM > > *To:* Filip Marvan > > *Cc:* [email protected] > > <mailto:[email protected]> > > *Subject:* Re: [OmniOS-discuss] Parity error on path mpt_sas2____ > > > > __ __ > > > > I've got some new LSI HBAs I'm trying to downgrade from firmware > > version 20 to 18.____ > > > > I'm getting errors when trying to downgrade: > > > > Attempting to flash firmware to LSI SAS SAS2308_2(D1) : > > > > Executing Operation: Flash Firmware Image > > > > Firmware Image has a Valid Checksum. > > Firmware Version 18.00.00.00 > > Firmware Image compatible with Controller. > > > > Valid NVDATA Image found. > > NVDATA Version 11.00.00.00 > > Checking for a compatible NVData image... > > > > NVDATA Device ID and Chip Revision match verified. > > ERROR: Cannot downgrade NVDATA version 14.00.00.06 > > to 11.00.110000.00. > > > > ERROR: Failed to get valid NVDATA image from File! > > > > Firmware Image Validation Failed!____ > > > > Tried downgrading bios: > > > > Attempting to flash Boot Service to LSI SAS SAS2308_2(D1) : > > > > Validating BIOS Image... > > > > BIOS Header Signature is Valid > > > > BIOS Image has a Valid Checksum. > > > > BIOS PCI Structure Signature Valid. > > > > BIOS Image Compatible with the SAS Controller. > > > > Attempting to Flash BIOS Image... > > > > BIOS Version in flash : 07.39.00.00 > > BIOS Version from File : 07.35.00.00 > > Skipping flash since file version is not greater > > than existing. > > > > Flash BIOS Image Failed!____ > > > > I've tried sas2flash from P20 and P18. > > > > Can someone fill me in on the trick to downgrade? ____ > > > > -Chip____ > > > > __ __ > > > > __ __ > > > > On Thu, Nov 27, 2014 at 9:03 AM, Filip Marvan <[email protected] > > <mailto:[email protected]>> wrote:____ > > > > Thank you for your help Aaron! I downgraded firmware to P18 and > > there are no more errors today.____ > > > > It seems, that there is something bad with P20 firmware!____ > > > > ____ > > > > You saved me a lot of time J____ > > > > ____ > > > > Filip____ > > > > ____ > > > > ____ > > > > *From:*Aaron Curry [mailto:[email protected] > > <mailto:[email protected]>] > > *Sent:* Tuesday, November 25, 2014 5:46 PM > > *To:* Filip Marvan > > *Cc:* Dan McDonald; [email protected] > > <mailto:[email protected]> > > *Subject:* Re: [OmniOS-discuss] Parity error on path mpt_sas2____ > > > > ____ > > > > I had this exact same problem recently when setting up a new home > > server... same controller, same firmware (P20). The errors were on > > all disks attached to the controller, but only on high read > > activity. Writes did not generate the errors. I downgraded the > > firmware to P18 (which is what we are using at work) and the errors > > went away. Has anyone had success with this controller and the P20 > > firmware?____ > > > > ____ > > > > Aaron____ > > > > ____ > > > > On Tue, Nov 25, 2014 at 8:30 AM, Filip Marvan <[email protected] > > <mailto:[email protected]>> wrote:____ > > > > Hi Dan, > > > > thanks for reply. > > Yes, errors are on all 5 disks in the same RAIDZ pool. No > > problem on other > > disks in different pool but on the same SAS cable. > > So maybe I only had bad luck with that disks. > > > > Filip > > > > > > _______________________________________________ > > OmniOS-discuss mailing list > > [email protected] > > <mailto:[email protected]> > > http://lists.omniti.com/mailman/listinfo/omnios-discuss____ > > > > ____ > > > > > > _______________________________________________ > > OmniOS-discuss mailing list > > [email protected] <mailto: > [email protected]> > > http://lists.omniti.com/mailman/listinfo/omnios-discuss____ > > > > __ __ > > > > > > > > > > _______________________________________________ > > OmniOS-discuss mailing list > > [email protected] > > http://lists.omniti.com/mailman/listinfo/omnios-discuss > > >
_______________________________________________ OmniOS-discuss mailing list [email protected] http://lists.omniti.com/mailman/listinfo/omnios-discuss
