[Dynamix - V6 Plugins]

For those who have installed an earlier version of the system buttons plugin, instead of upgrading do an uninstall and new install.

 

The upgrade process does not remove properly all old files (this happens because I moved directories).

 

I'm also having the problem but cannot uninstall because I don't have access to the installed plugins.  See screenshot.  Any thoughts?

 

Can you clear your browser cache (CTRL-F5) and reload the page ?

 

I cleared the browser cache (CTRL-F5) and no change.  I still have the "Please wait, retrieving plugin information ..." message.

[Dynamix - V6 Plugins]

For those who have installed an earlier version of the system buttons plugin, instead of upgrading do an uninstall and new install.

 

The upgrade process does not remove properly all old files (this happens because I moved directories).

 

I'm also having the problem but cannot uninstall because I don't have access to the installed plugins.  See screenshot.  Any thoughts?

[Upgrading unRaid-5 to unRaid-6]

Yes it's a BetaQuasi VMDK file, which was the reason the partition was ~ 100 MB and the reason that the upgrade script and v6 OS update don't work in this setup.  BetaQuasi's VMDKs split the base unRAID files and config files between a virtual hard drive and USB device.  I believe this was done for quicker booting.  BetaQuasi VMDKs have been reliable and served well but since this architecture doesn't work with unRAID v6, I'll switch to PLOP and follow your suggestions.

 

Thanks Ice_Black!

 

Update:  I kept the VMDK format given that a v6.01 VMDK was posted.  Plop seems to have a much slower boot and the "USB reset" quirk vs VMDK for ESXi configurations (like mine).  Limetech recommends bare metal only, so I may eventually migrate to bare metal, but I'll have to migrate/recreate all my ESXi VMs to KVM.  (on the list to research)

 

v6 is awesome!  Good job to Limetech and the community!  unRAID totally blows away the competition!! 

[Upgrading unRaid-5 to unRaid-6]

Thanks Squid!  I do run unRAID on a VMDK but have the key, config, etc on a USB flash drive that the VM uses.  I think you nailed it and only the USB flash was upgraded.  I'm checking now to see if this resolves it.

 

Edit:  This does appear what happened, the USB flash was upgraded but not the VMDK file.  But I'm having a space problem with the VMDK.  The VMDK is provisioned with 8GB space as think lazy zeroed, but only showing 93MB of disk space capacity.  Not enough space to copy over unRAID 6.01...but really wondering what happened to the VMDK to lose all the space.  Seeing if there is a way to reclaim the space or I might create a new VMDK file.

[Upgrading unRaid-5 to unRaid-6]

I'm using method #1 and it seems the upgrade download and install completed successfully but each time I reboot unRAID I still boot into v5.06.  (I rebooted multiple times.) The telnet output of the upgrade process is attached.  I'm running in a VM on ESXi but that doesn't matter, correct?

 

Edit:  also attached syslog.txt

upgrade_v5.06tov6.01_telnet_output.txt

syslog.txt

[M1015 / X9SCM-F USB Firmware Tools]

Thanks again BetaQuasi for the excellent guide! 

 

I thought I'd post what I did to upgrade my bios & firmware with a Linux installer, following your guide:

 

To upgrade M1015 card (already flashed/changed to a LSI9211-8i card) bios and firmware:

 

1.  Download "9211-8i_Package_P19_IR_IT_Firmware_BIOS_for_MSDOS_Windows" (in firmware section) at:  http://www.lsi.com/products/host-bus-adapters/pages/lsi-sas-9211-8i.aspx

2.  Download "Installer_P19_for_Linux" (in firmware section) at:  http://www.lsi.com/products/host-bus-adapters/pages/lsi-sas-9211-8i.aspx

3.  Unzip both files downloaded from the LSI website.  Copy "sas2flash", "2118it.bin" and "mptsas2.rom" from the 2 unzipped archives to a temporary folder on your unraid flash drive.  I created a temporary directory called "linux" at /boot/linux

4.  (Note:  To copy the 3 files to /boot/linux I used WinSCP to create a FTP session between my local PC and the unRAID server.)

5.  Use PuTTY to telnet to the unraid server.  Navigate to the /boot/linux folder.

6.  Execute this command to perform the firmware and bios upgrade:  "sas2flash -o -f 2118it.bin -b mptsas2.rom"

7.  (Note the Linux installer is called "sas2flash" instead of the UEFI installer "sas2flsh")

8.  See output of my upgrade process below.

 

Artoo-Detoo login: root
Password:
Linux 3.9.11p-unRAID.
root@Artoo-Detoo:~# cd /boot/linux
root@Artoo-Detoo:/boot/linux# ls
2118it.bin*  mptsas2.rom*  sas2flash*
root@Artoo-Detoo:/boot/linux# sas2flash -o -f 2118it.bin -b mptsas2.rom
LSI Corporation SAS2 Flash Utility
Version 19.00.00.00 (2014.03.17)
Copyright (c) 2008-2014 LSI Corporation. All rights reserved

        Advanced Mode Set

        Adapter Selected is a LSI SAS: SAS2008(B2)

        Executing Operation: Flash Firmware Image

                Firmware Image has a Valid Checksum.
                Firmware Version 19.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.
                NVDATA Versions Compatible.
                Valid Initialization Image verified.
                Valid BootLoader Image verified.

                Beginning Firmware Download...
                Firmware Download Successful.

                Verifying Download...

                Firmware Flash Successful.

                Resetting Adapter...
                Adapter Successfully Reset.

        Executing Operation: Flash BIOS Image

                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...

                Verifying Download...

                Flash BIOS Image Successful.

                Updated BIOS Version in BIOS Page 3.

        Finished Processing Commands Successfully.
        Exiting SAS2Flash.
root@Artoo-Detoo:/boot/linux#

[M1015 / X9SCM-F USB Firmware Tools]

Thank you Beta Quasi!    This resource/tools made it really easy to update!  FYI the X9SCM-F now has v2.38 IPMI firmware.

[LSI Controller FW updates IR/IT modes]

Thanks, cane you explain UEFI she'll ? How I can change to that ?

 

// Peter

 

When booting, enter The BIOS and select the UEFI shell as a boot device.  From there, you can flash the M1015. 

 

Ogi

 

See here for more detail on using UEFI shell to overcome the "ERROR: Failed to initialize PAL. Exiting program" message.

[[SOLVED] Flashing LSI 9220-8i Controller (IBM M1015) on a ASROCK 970 Extreme3]

I didn't get to try your hint BQ.  Didn't see your post.  I was playing around with it as I was having the dreaded "Failed to initialize PAL" error message.  I was about to try flashing on another MB, but decided to search around and found out it works on the UEFI console.

 

You'll need two items:

 

1. Download the full UFEI shell from here:  https://wiki.archlinux.org/index.php/Unified_Extensible_Firmware_Interface#UEFI_Shell  (used x86_64 1.0) and paste Shell_Full.efi on the root of the USB.  I unfortunately figured this out after going through the whole routine.  Makes things a bit easier.

 

2. http://www.lsi.com/channel/products/storagecomponents/Pages/LSISAS9211-8i.aspx

download firmware > Installer_P15_for_UEFI

Drop the resulting sas2flash.efi into the folder with the sas2flsh.exe.

 

 

Now to actually do the deed:

 

In my MB, if I bring up the boot menu by pressing F11, one of the options is "Built-in EFI Shell".  If you don't have this, I searched and saw there are bootable linux distros what come with EFI shells.  If it will work for flashing the card, I have no idea

 

Booting into this, you'll get a command promt.  Listed above the promt, will be all the devices attached.  In my case, there was fs0 and blk0.

 

Type

 

> fs0:

 

Type "ls" (list).  If "ls" doesn't work, keep pressing tab.  If you see the files in your usb appearing one after another, you're in business.  if not, try some of the other FS.  DON'T FORGET THE COLON :

 

Keep tabbing until you come to Shell_Full.efi and press enter.  Now you will see the same device info listed once more.  Now ls will work.  cd into the directory with your bat files (which is where you have your sas2flash.efi).

 

Now to run the commands for step 5 and 6.  Execute the following.

 

Step 5:

> sas2flash.efi -l Flashlog.txt -o -f 2118it.bin -b mptsas2.rom

 

Step 6:

> sas2flash.efi -o -sasadd 500605bxxxxxxxxx

 

Where 500605bxxxxxxxxx is replaced by SAS Address from Adapters.txt

 

 

THAT'S IT!  I've been struggling with this since saturday and after BobPhoenix's hint about using the right software, it's fixed in one.  I hope this helps someone stuck in this step.

 

Cheers

 

Excellent!  These notes allowed me to flash a M1015 with my X9SCM-F after getting the "Failed to initialize PAL" message.  Thanks to you and others in this forum! 

[Undelete help please!!]

I apologize if this has already been answered.  Two questions:

• 
   
   
  1.  Once I recover the files in "lost+found" how to I effectively decrypt the original file name?
  2.  For some reason the "disk share" is still visible even though I copied the "lost+found" contents to a local pc , deleted the "lost+found" folder from the disk and set "Disk shares (SMB)" to "Don't export" Any ideas?
   
  Running unRAID Server Pro v4.7
   
  Edit:  Further research indicates there is no easy, straight-forward method to decipher the original file name.  The date time stamp and file size seem to be the best clues.  Also, I found out that stopping and restarting the array eliminated the "disk share" that was still visable.  I answered my own questions.