Update the correct board name and NVDATA product ID?

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.

MuscleLazy

Member
Apr 30, 2022
43
2
8
I recently flashed a Dell PERC H810 full card to IT mode using @fohdeesha's instructions:
Code:
# sas2flash -c 1 -list
LSI Corporation SAS2 Flash Utility
Version 20.00.00.00 (2014.09.18)
Copyright (c) 2008-2014 LSI Corporation. All rights reserved

    Adapter Selected is a LSI SAS: SAS2308_2(D1)

    Controller Number              : 1
    Controller                     : SAS2308_2(D1)
    PCI Address                    : 00:44:00:00
    SAS Address                    : [removed]
    NVDATA Version (Default)       : 14.01.00.06
    NVDATA Version (Persistent)    : 14.01.00.06
    Firmware Product ID            : 0x2214 (IT)
    Firmware Version               : 20.00.07.00
    NVDATA Vendor                  : LSI
    NVDATA Product ID              : SAS9207-8i
    BIOS Version                   : 07.39.02.00
    UEFI BSD Version               : 07.27.01.01
    FCODE Version                  : N/A
    Board Name                     : SAS9207-8i
    Board Assembly                 : N/A
    Board Tracer Number            : N/A

    Finished Processing Commands Successfully.
    Exiting SAS2Flash.
Is it possible to update the correct board name and NVDATA product ID assigned to card, with a command? Should be SAS9207-8e, since is an external card.
 

fohdeesha

Kaini Industries
Nov 20, 2016
2,740
3,108
113
33
fohdeesha.com
I recently flashed a Dell PERC H810 full card to IT mode using @fohdeesha's instructions:
Code:
# sas2flash -c 1 -list
LSI Corporation SAS2 Flash Utility
Version 20.00.00.00 (2014.09.18)
Copyright (c) 2008-2014 LSI Corporation. All rights reserved

    Adapter Selected is a LSI SAS: SAS2308_2(D1)

    Controller Number              : 1
    Controller                     : SAS2308_2(D1)
    PCI Address                    : 00:44:00:00
    SAS Address                    : [removed]
    NVDATA Version (Default)       : 14.01.00.06
    NVDATA Version (Persistent)    : 14.01.00.06
    Firmware Product ID            : 0x2214 (IT)
    Firmware Version               : 20.00.07.00
    NVDATA Vendor                  : LSI
    NVDATA Product ID              : SAS9207-8i
    BIOS Version                   : 07.39.02.00
    UEFI BSD Version               : 07.27.01.01
    FCODE Version                  : N/A
    Board Name                     : SAS9207-8i
    Board Assembly                 : N/A
    Board Tracer Number            : N/A

    Finished Processing Commands Successfully.
    Exiting SAS2Flash.
Is it possible to update the correct board name and NVDATA product ID assigned to card, with a command? Should be SAS9207-8e, since is an external card.
these metadata fields are pulled from the firmware image, so you'd have to flash the 9207-8e firmware image (Broadcom Inc. | Connecting Everything). You may have to create, compile then flash a new SBR with the appropriate PCI ID values for that to take. the 8e and 8i firmware are identical minus these metadata fields so I wouldn't worry about it
 

itronin

Well-Known Member
Nov 24, 2018
1,242
803
113
Denver, Colorado
I could have sworn there was a version of s2f that had an option to monkey with the board name. I did this once upon a time after flashing a bunch of H310's to IT. I wanted to differentiate the boards in vmware for pass-through. so long ago and I have semi permanent brain fog now.
 

MuscleLazy

Member
Apr 30, 2022
43
2
8
@fohdeesha I'm sure others mentioned but I want to thank you for the useful documents you offer to people.

I have 2 cards successfully flashed with your procedure on my R720xd, one internal Dell H710 mini and one external PCIe Dell H810. In my case, it will be useful to differentiate the 2 cards like @itronin needed too. This is what I see now, first card is the internal H710, second is the external H810:

1660419641621.png

Please let me know if the procedure listed below is correct.

Download the 9207-8e_Package_P20_IT_Firmware_BIOS_for_MSDOS_Windows, unzip it and use the following files:
  • /Firmware/HBA_9207_8e_IT/9207-8e.bin
  • /sas2flash_dos_rel/sas2flsh.exe
  • /sasbios_rel/mptsas2.rom
Create a bootable FreeDOS USB flash drive and copy the above files into it.

Boot in BIOS mode to USB drive with only H810 connected and run the following commands:
Code:
> sas2flsh -listall
> sas2flsh -o -e 6
> sas2flsh -o -f 9207-8e.bin -b mptsas2.rom
NVDATA Product ID and Vendor ID do not match. Would you like to flash anyway [y/n]? y
> sas2flsh -o -sasadd XXXXXXXXXXXXXXXX
I think the correct erasing parameter is 6?

1660424514430.png

Thank you for your help.
 
Last edited:

fohdeesha

Kaini Industries
Nov 20, 2016
2,740
3,108
113
33
fohdeesha.com
@fohdeesha I'm sure others mentioned but I want to thank you for the useful documents you offer to people.

I have 2 cards successfully flashed with your procedure on my R720xd, one internal Dell H710 mini and one external PCIe Dell H810. In my case, it will be useful to differentiate the 2 cards like @itronin needed too. This is what I see now, first card is the internal H710, second is the external H810:

View attachment 23990

Please let me know if the procedure listed below is correct.

Download the 9207-8e_Package_P20_IT_Firmware_BIOS_for_MSDOS_Windows, unzip it and use the following files:
  • /Firmware/HBA_9207_8e_IT/9207-8e.bin
  • /sas2flash_dos_rel/sas2flsh.exe
  • /sasbios_rel/mptsas2.rom
Create a bootable FreeDOS USB flash drive and copy the above files into it.

Boot in BIOS mode to USB drive with only H810 connected and run the following commands:
Code:
> sas2flsh -listall
> sas2flsh -o -e 6
> sas2flsh -o -f 9207-8e.bin -b mptsas2.rom
NVDATA Product ID and Vendor ID do not match. Would you like to flash anyway [y/n]? y
> sas2flsh -o -sasadd XXXXXXXXXXXXXXXX
I think the correct erasing parameter is 6?

View attachment 23992

Thank you for your help.
I believe you'd need erase 7, 6 leaves manuf data which is what we're trying to change. All the flash scripts in my guide do a complete flash erase, the equivalent of -e 7
 

MuscleLazy

Member
Apr 30, 2022
43
2
8
I believe you'd need erase 7
I tried value 7 but I get stuck with 2 errors. On latest sas2flsh v20, I get a failed to upload image and on older v7 I get failed to validate MfgPage2.

I was wondering if I can modify your D1-H710 script and create a new D1-H710E with the 9207-8e firmware? Will this allow me to install correctly 9207-8e?

BTW, there is some information not accurate in your documentation. The boot images should always be installed (e.g. mptsas2.rom). If you want to save time at boot, you need to change the boot support in Avago configuration (CTRL + C) from Enabled BIOS & OS:

Screen Shot 2022-08-16 at 2.10.21 AM.png

To Enabled OS only:

Screen Shot 2022-08-16 at 2.10.39 AM.png

The card will be disabled into BIOS but fully functional into OS, which emulates your ROMless behaviour. However, if you need to troubleshoot something, all you have to do is enable back the Enabled BIOS & OS option. Feel free to use the screenshots for your docs.

1660630461493.png

1660631048125.png
 
Last edited:

fohdeesha

Kaini Industries
Nov 20, 2016
2,740
3,108
113
33
fohdeesha.com
I tried value 7 but I get stuck with 2 errors. On latest sas2flsh v20, I get a failed to upload image and on older v7 I get failed to validate MfgPage2.

I was wondering if I can modify your D1-H710 script and create a new D1-H710E with the 9207-8e firmware? Will this allow me to install correctly 9207-8e?

BTW, there is some information not accurate in your documentation. The boot images should always be installed (e.g. mptsas2.rom). If you want to save time at boot, you need to change the boot support in Avago configuration (CTRL + C) from Enabled BIOS & OS:

View attachment 24006

To Enabled OS only:

View attachment 24007

The card will be disabled into BIOS but fully functional into OS, which emulates your ROMless behaviour. However, if you need to troubleshoot something, all you have to do is enable back the Enabled BIOS & OS option. Feel free to use the screenshots for your docs.

View attachment 24008

View attachment 24010
yeah you can just edit the bash script in linux to point to the E firmware bin, just make sure to edit both instances (I believe the bin is referenced twice in the script). Regarding " there is some information not accurate in your documentation. The boot images should always be installed " - heelll no. Probably half the email I get is people having issues with the bootrom on boot, not being able to figure out the key combo over idrac to get into it to turn off OS support, etc. having 100% of users install it would be a nightmare. no reason to have it if you're not booting off it, everything it exposes is also visible with lsi utils from inside an OS. If a subset of people want to use it to debug without an OS, they can install the bootrom but no way I'm having it flashed by default
 

mobilenvidia

Moderator
Sep 25, 2011
1,956
212
63
New Zealand
Could have sworn I mentioned not needing BIOS in another thread numerous times
To me, you seem to spend far too much time in the BIOS, there is nothing to see or do in there when in IT mode
Remove everything from card (ie FW), then only flash the IT FW, nothing else
At boot you won't see a thing, in the OS you'll have glorious individual drives on both controllers
But do try flashing the 8e FW to the H810 so it may appear as a external controller to the OS to help you here
 
  • Like
Reactions: itronin