Trying to see what version of my sas controlers are useing

ran both these cammands.
sas2Flash is giving me an error.
sas 9300 16i cards there are 2 of them

root@truenas:~# lspci|grep SAS
09:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS3008 PCI-Express Fusion-MPT SAS-3 (rev 02)
0b:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS3008 PCI-Express Fusion-MPT SAS-3 (rev 02)
0f:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS3008 PCI-Express Fusion-MPT SAS-3 (rev 02)
11:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS3008 PCI-Express Fusion-MPT SAS-3 (rev 02)
root@truenas:~# sas2flash -listall
LSI Corporation SAS2 Flash Utility
Version 20.00.00.00 (2014.09.18)
Copyright (c) 2008-2014 LSI Corporation. All rights reserved

    No LSI SAS adapters found! Limited Command Set Available!
    ERROR: Command Not allowed without an adapter!
    ERROR: Couldn't Create Command -listall
    Exiting Program.

root@truenas:~#

try sas3flash -listall

As you have a SAS3 controller.

2 Likes

sweet that worked.
Now how to flash newer firmware on them if needed.




root@truenas:~# sas3flash -listall
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)

Num   Ctlr            FW Ver        NVDATA        x86-BIOS         PCI Addr
----------------------------------------------------------------------------

0  SAS3008(C0)  07.00.01.00    07.01.00.03    08.15.00.00     00:09:00:00
1  SAS3008(C0)  07.00.01.00    07.01.00.03    08.15.00.00     00:0b:00:00
2  SAS3008(C0)  07.00.01.00    07.01.00.03    08.15.00.00     00:0f:00:00
3  SAS3008(C0)  07.00.01.00    07.01.00.03    08.15.00.00     00:11:00:00

        Finished Processing Commands Successfully.
        Exiting SAS3Flash.
1 Like

That’s very old.

1 Like

i had a feeling it was running an old firmwere. given that i cant connect more than 12 drives and my case supports 24. :disappointed:
yes i tried multiple backplanes and different cables.

I’d be surprised if flashing the FW changes this.

Put the firmware and sas3flash.efi on a FAT-formatted USB drive and boot to the UEFI shell.

1 Like

Its so close but so far… i seem to have flashed one of them but not the other 3…
how to fix?

        Adapter Selected is a Avago SAS: SAS3008(C0)

Num   Ctlr            FW Ver        NVDATA        x86-BIOS         PCI Addr
----------------------------------------------------------------------------

0  SAS3008(C0)  16.00.12.00    0e.01.00.03    08.15.00.00     00:09:00:00
1  SAS3008(C0)  07.00.01.00    07.01.00.03    08.15.00.00     00:0b:00:00
2  SAS3008(C0)  07.00.01.00    07.01.00.03    08.15.00.00     00:0f:00:00
3  SAS3008(C0)  07.00.01.00    07.01.00.03    08.15.00.00     00:11:00:00

        Finished Processing Commands Successfully.
        Exiting SAS3Flash.
root@truenas:              

And never mind i found the command that works for me. i have 2 SAS9300 16i.
Dont do this if you have mixed sas controllers

command ran

sas3flash -fwall SAS9300_xx_IT.bin

(replace SAS9300_xx_IT.bin with correct .bin file. For your sas controller/s)

2 Likes

With mixed controllers, you specify the number of the target controller : -c 1

1 Like

I wouldn’t. P7 is ancient and the SAS3 firmware saw a lot of improvements over a relatively short period until things stabilized at around P16, which got crystallized as the firmware release series by virtue of gen1 SAS3 controllers never getting P17 and newer.

2 Likes

I’ve seen sooooo many lost pools and other issues with LSI controllers in these forums, while using older firmware. It’s definitely a problem the OP needs to resolve.

both sas controllers are running version 16 now the problem has been resolved.

3 Likes