Zeron

Uploaded today. Hopefully Limetech will not change the Kernel version before the final release of V6

It shouldn't cause any problems, but I have released an updated version with this warning fixed.

Beta15 plugin is available now.

Updated to support Beta-14

http://unraid.zeron.ca/plugins/open-vm-tools/openVMTools.plg Finally work with unRAID 6. 6.0/6.1 Requires the Powerdown package. 6.2+ does not. 6.3.5 is the last version supported by this plugin. I no longer use unRAID under ESXi

I have been running P12 on my IBM M1015 for about a week now. No issues so far. I have a zip file with all the files to upgrade from DOS here: http://unraid.zeron.ca/other/upgrade-M1015-P12.zip

...a P11 Firmware&BIOS package is available from LSI since 8 weeks now, here: http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/SAS_SATA_6G_P11/9211_8i_Package_P11_IR_IT_Firmware_BIOS_for_MSDOS_Windows.zip Any experience or insights from the experts around? I updated my IBM M1015 to P11 and have been running a preclear on a WD20EARX under Beta-6a. On the previous firmware I would get the following errors: sd 0:0:8:0: attempting task abort! scmd(ffff8802ede2fc80) sd 0:0:8:0: [sdg] CDB: cdb[0]=0x2a: 2a 00 2c 05 cf 90 00 00 30 00 scsi target0:0:8: handle(0x000f), sas_address(0x4433221103000000), phy(3) scsi target0:0:8: enclosure_logical_id(0x500605b001d0ab00), slot(3) 12 hours in and have not seen one yet. Beta-12a segfaulted on boot with P11, but I never did try beta-12a with the previous firmware version. I put together this file for upgrading for a DOS boot: http://unraid.zeron.ca/other/upgrade-M1015-P11.zip

The motherboard I tried it on had Intel Q45 and G43 chipsets. The one it worked on was a HP AMD based system.

If you get 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.aspx I had the same problem on my Intel server board, but it worked fin on the third PC I tired it in.