Your card looks very much like mine in the sense of having the LSI 3008 chip on it, yet my card is an LSI 9300... the card model doesn't matter as much as the chip:However, I do not believe this applies to me, because it is a 3008 card, not a 9300.
Avago Technologies SAS3 Flash Utility Version 16.00.00.00 (2017.05.02) Copyright 2008-2017 Avago Technologies. All rights reserved. Adapter Selected is a Avago SAS: SAS3008(C0) Controller Number : 0 Controller : SAS3008(C0) PCI Address : 00:04:00:00 SAS Address : 500062b-2-02a3-2ac0 NVDATA Version (Default) : 0e.01.00.03 NVDATA Version (Persistent) : 0e.01.00.03 Firmware Product ID : 0x2221 (IT) Firmware Version : 16.00.12.00 NVDATA Vendor : LSI NVDATA Product ID : SAS9300-16i BIOS Version : 08.11.00.00 UEFI BSD Version : 06.00.00.00 FCODE Version : N/A Board Name : SAS9300-16i Board Assembly : 03-25600-01B Board Tracer Number : SP64601874 Finished Processing Commands Successfully.
If your vendor doesn't offer the latest firmware you can take a look at this thread dealing with cross-flashing over at ServeTheHome.Are 2 of My Drives Failed? (See Edit: Moving Data Onto To New Vdev, To Remove Old)
You have wrong firmware version. See the following resource. https://www.truenas.com/community/resources/lsi-9300-xx-firmware-update.145/ I got them directly from Supermicro's site under Firmware Also that states it's for a LSI 9300-xx, not my 3008..? I have been running this on the HBA since...www.truenas.com
A user in this thread mentioned that I am using the incorrect firmware for my HBA, and directed me here.
However, I do not believe this applies to me, because it is a 3008 card, not a 9300. I was just looking for confirmation though.
My HBA is a Supermicro AOC-S3008L-L8E Rev2 (IT MODE) and I got the IT Mode firmware directly from Supermicro's firmware page
View attachment 68966
I don't think this has anything to do with my issues in that thread either.
You state that this only affects SATA drives, all my drives in my pool are HDD and I have not noticed any issues and have been running this card for over a year with this firmware. My boot drive is a SATA SSD however, and I assume I would have noticed major issues, which I have never.
"3008" is the LSI reference of the controller chip. Controllers of the 3000 family of SAS3 controllers are found in cards of the LSI 9300 series.However, I do not believe this applies to me, because it is a 3008 card, not a 9300. I was just looking for confirmation though.
Well from what everyone is saying, it looks like this 9300-xx firmware update does actually apply to me so I should be good to just update it with this firmware.If your vendor doesn't offer the latest firmware you can take a look at this thread dealing with cross-flashing over at ServeTheHome.
Your card looks very much like mine in the sense of having the LSI 3008 chip on it, yet my card is an LSI 9300... the card model doesn't matter as much as the chip:
The firmware would certainly apply.
Looking at your current version, it's not only going to be the difference between the .11 and .12 fixes that you would benefit from, so my recommendation is to perform the update.
"3008" is the LSI reference of the controller chip. Controllers of the 3000 family of SAS3 controllers are found in cards of the LSI 9300 series.
So your LSI 3008 controller does belong to a LSI 9300 card (or OEM equivalent): Two different ways to designate the same thing.
And SAS2 controllers of the 2000 family are found in the 9200 series of cards.
.bin
file?sas3flash -o -f SAS9300_xx_IT.bin
AOC-S3008L-L8E Rev2
.SAS9300_8e_IT.bin
, out of all the options in there (9300-4i, 9300-4i4e, 9300-8e, 9300-8i, etc.)?SAS9300_8e_IT_acm
?You can run it in TrueNAS, but take your pool offline first. Otherwise, you'll get the equivalent of a hard power cut to the disks... maybe OK, but I wouldn't chance it (having said that, I'm speaking from experience, which I got away with sans damage, so there's that).If I am running this, can I do it directly from TrueNAS shell? Should I be bringing my Pool offline to be safe, or will nothing apply until I reboot the machine?
Is it of concern that my boot pool is a SATA SSD connected to my HBA?You can run it in TrueNAS, but take your pool offline first. Otherwise, you'll get the equivalent of a hard power cut to the disks... maybe OK, but I wouldn't chance it (having said that, I'm speaking from experience, which I got away with sans damage, so there's that).
The thread I linked to has a lot posts from people going through the same or similar upgrades, I found it valuable to read through.Well from what everyone is saying, it looks like this 9300-xx firmware update does actually apply to me so I should be good to just update it with this firmware.
Okay, will go ahead and do it.
Curiously, I remember when updating this I did it from EFI shell I believe.
But from @JoshDW19 instructions, it seems you can do it right from TrueNAS shell?
Looks like I'd just fetch the folder onto TrueNAS, extract it, navigate to the folder and flash the.bin
file?
sas3flash -o -f SAS9300_xx_IT.bin
As far as which one, how do I determine which to flash?
Again my device is aAOC-S3008L-L8E Rev2
.
Should I assume I am flashingSAS9300_8e_IT.bin
, out of all the options in there (9300-4i, 9300-4i4e, 9300-8e, 9300-8i, etc.)?
What is theSAS9300_8e_IT_acm
?
Also again my BOOT drive is SATA, and my entire Pool is SAS.
If I am running this, can I do it directly from TrueNAS shell? Should I be bringing my Pool offline to be safe, or will nothing apply until I reboot the machine?
I would say it's generally a good idea to do that anyway, but particularly for this case.Is it of concern that my boot pool is a SATA SSD connected to my HBA?
Or should I move it directly onto the motherboard so it doesn't get affected by this.
100% this.I would avoid any question by updating from the UEFI shell.
I am attempting this right now, and having trouble.I would avoid any question by updating from the UEFI shell.
FS0:
, FS1:
, etc.Ok.. that is what I was curious about. That's probably why.It sounds like you're missing the actual flashing executable, sas3flash. Just get it directly from Broadcom's latest release if you don't already have it on hand.
An appropriate invocation of sas3flash should list the SAS address. Though you probably don't even need it, since it's just a firmware page flash.I assume I'm going to need to get the last 9 digits of the SAS address which is on the label of the HBA. My machine is rackmounted and the rails are a bit shotty haha. Is there an easier way of getting the SAS address that doesn't involve me taking my entire machine off the rack?
Wdym by booting from the card? You mean if my boot drive is connected to the backplane (which is connected to the HBA)?Plus the UEFI extension ROM if you're planning on booting from the card.
An appropriate invocation of sas3flash should list the SAS address. Though you probably don't even need it, since it's just a firmware page flash.
Yes, exactly.Wdym by booting from the card? You mean if my boot drive is connected to the backplane (which is connected to the HBA)?
Matter of taste, really. I don't like booting from SAS controllers, some systems don't like to boot from SAS controllers - but sometimes I have to. It shouldn't be harmful, but the edge cases often get complicated - multiple HBAs with different firmware versions and different extension ROMs, that sort of thing.It is not currently, but it's probably best to install it anyways, no? In case that changes in the future I won't have to reflash it
mpt3x64.rom is the UEFI extension ROM, mptsas3.rom is the legacy BIOS option ROM.Which rom file do I need from here?