For AI agents: the complete documentation index is available at https://docs.us.ovhcloud.com/en/llms.txt, the full documentation bundle is available at https://docs.us.ovhcloud.com/en/llms-full.txt, and this page is available as Markdown at https://docs.us.ovhcloud.com/en/bare-metal-cloud/dedicated-servers/high-grade-upgrading-ssd-sas-western-digital-ss300-firmware.md.
  • English

High Grade Dedicated Servers - Upgrading Your SSD SAS Western Digital SS300 Firmware

View as Markdown

Learn how to upgrade your SSD SAS Western Digital SS300 firmware.

Routine firmware updates play a pivotal role in upholding your drive's performance, stability, and security. Such updates often encompass critical bug fixes, enhanced compatibility, and advanced security features that are indispensable for preserving your data integrity and maintaining optimal operational efficiency.

An important patch has been introduced in this new firmware (version BCGNB17D). We strongly recommend updating your firmware to avoid any premature end-of-life.

Click here for the firmware release notes.

Disk part numbers:

  • HUSMR3280ASS201 (800GB capacity)
  • HUSMR3240ASS201 (400GB capacity)

 

Requirements

  • A bare metal server with SSD SAS Western Digital SS300, from the following:

    • mHG/HG/BHG 2017
    • mHG/HG/BHG 2018
    • mHG/HG/BHG 2019

 

Instructions

Danger

WARNING:

  • Before attempting any firmware update, a backup of the data on the drive must be made. Use our Getting Started - Backing Up a Bare Metal Server with Veeam Enterprise guide to see an option for how to do this.
  • The firmware update does not format the drive or delete data, but a firmware update failure may happen. Please do not power off the drive or the bare metal server during the firmware update process.
Info

All commands must be run as root for Linux and VMWare and with an administrator account for Windows.

Linux
Windows
ESXi 7.x
ESXi 8.x

Linux

Hardware/software configuration tested on the OVHcloud side

PlatformFlash toolFirmwareResult
Debian 11/12 OSStorCLI 007.2705.0000.0000BCGNB17DOK
Ubuntu 22.04 OSStorCLI 007.2705.0000.0000BCGNB17DOK
Rocky 7/8 OSStorCLI 007.2705.0000.0000BCGNB17DOK
Debian 11/12 OS + HARD RAIDStorCLI 007.2705.0000.0000BCGNB17DOK
Ubuntu 22.04 OS + HARD RAIDStorCLI 007.2705.0000.0000BCGNB17DOK
Rocky 7/8 OS + HARD RAIDStorCLI 007.2705.0000.0000BCGNB17DOK

 

Step 1 - Download StorCLI

Download the StorCLI package on your server:

wget https://docs.broadcom.com/docs-and-downloads/007.2705.0000.0000_storcli_rel.zip

Unpack the global archive:

unzip 007.2705.0000.0000_storcli_rel.zip

Then unpack the archive containing the binaries for the various OS:

unzip storcli_rel/Unified_storcli_all_os.zip

 

Step 2 - Install StorCLI

  • For Debian, Ubuntu, Mint, Proxmox and similar:
dpkg -i Unified_storcli_all_os/Ubuntu/storcli_007.2705.0000.0000_all.deb
  • For RHEL, CentOS, RockyLinux, AlmaLinux, Fedora, and similar:
rpm -ivh Unified_storcli_all_os/Linux/storcli-007.2705.0000.0000-1.noarch.rpm

 

Step 3 - Check if a firmware update is needed

Run the following command to retrieve your controller ID in the Ctl field:

/opt/MegaRAID/storcli/storcli64 show

Example:

root@labo:~# /opt/MegaRAID/storcli/storcli64 show
CLI Version = 007.2705.0000.0000 August 24, 2023
Operating system = Linux 6.1.51-mod-std
Status Code = 0
Status = Success
Description = None
Number of Controllers = 1
Host Name = test.ovh.us
Operating System = Linux 6.1.51-mod-std
StoreLib IT Version = 07.2703.0200.0000
StoreLib IR3 Version = 16.14-0
System Overview :
===============
------------------------------------------------------------------------------------
Ctl Model Ports PDs DGs DNOpt VDs VNOpt BBU sPR DS EHS ASOs Hlth
------------------------------------------------------------------------------------
 0 AVAGOMegaRAIDSAS9361-4i 4 4 0 0 0 0 Opt On 1&2 Y 3 Opt
------------------------------------------------------------------------------------
Ctl=Controller Index|DGs=Drive groups|VDs=Virtual drives|Fld=Failed
PDs=Physical drives|DNOpt=Array NotOptimal|VNOpt=VD NotOptimal|Opt=Optimal
Msng=Missing|Dgd=Degraded|NdAtn=Need Attention|Unkwn=Unknown
sPR=Scheduled Patrol Read|DS=DimmerSwitch|EHS=Emergency Spare Drive
Y=Yes|N=No|ASOs=Advanced Software Options|BBU=Battery backup unit/CV
Hlth=Health|Safe=Safe-mode boot|CertProv-Certificate Provision mode
Chrg=Charging | MsngCbl=Cable Failure

Then retrieve enclosure and disk slot numbers by running the command:

/opt/MegaRAID/storcli/storcli64 /cx /eall /sall show | grep -i 'HUSMR3240ASS201\|HUSMR3280ASS201'
Info

x is the ID of the controller managing the disks to be updated (see above).

We added a filter on this command to only display the SSD SAS Western Digital SS300 because the firmware update only concerns this particular disk and your server may have other disks connected to it.

In our example, 2 disks need to be updated (252:0 and 252:1). 252 is the disk enclosure ID and 0/1 the disk slot number:

root@labo:~# /opt/MegaRAID/storcli/storcli64 /c0 /eall /sall show | grep -i 'HUSMR3240ASS201\|HUSMR3280ASS201'
252:0 6 JBOD - 745.211 GB SAS SSD Y N 512B HUSMR3280ASS201 U -
252:1 4 JBOD - 745.211 GB SAS SSD Y N 512B HUSMR3280ASS201 U -

 

Step 4 - Firmware update

Download the firmware binary on your server:

wget https://last-public-ovh-baremetal.snap.mirrors.ovh.us/hardware/PM9A1/BCGNB17D_Noformat.binwget https://last-public-ovh-baremetal.snap.mirrors.ovh.us/hardware/SS300/BCGNB17D.bin

Execute the following command for each identified disk displayed in step 3:

/opt/MegaRAID/storcli/storcli64 /cx /ey /sz download src=BCGNB17D.bin
Info

x is the ID of the controller managing the disks to be updated; y is the disk enclosure ID; z is the disk slot number (see above).

In our previous example, 2 disks need a firmware update to the latest firmware version BCGNB17D. Here's how we update the 2 disks and the command line returns:

root@labo:~# /opt/MegaRAID/storcli/storcli64 /c0 /e252 /s0 download src=BCGNB17D.bin
Starting microcode update .....please wait...
Flashing PD image .....please wait...
CLI Version = 007.2705.0000.0000 August 24, 2023
Operating system = Linux 6.1.51-mod-std
Controller = 0
Status = Success
Description = Firmware Download Succeeded.
root@labo:~# /opt/MegaRAID/storcli/storcli64 /c0 /e252 /s1 download src=BCGNB17D.bin
Starting microcode update .....please wait...
Flashing PD image .....please wait...
CLI Version = 007.2705.0000.0000 August 24, 2023
Operating system = Linux 6.1.51-mod-std
Controller = 0
Status = Success
Description = Firmware Download Succeeded.

At this point the firmware update is complete, please reboot your server.

 

Step 5 - Check the firmware version after the server reboot

Execute the following command for each identified disk displayed in step 3:

/opt/MegaRAID/storcli/storcli64 /cx /ey /sz show all | grep -i 'Firmware Revision'
Info

x is the ID of the controller managing the disks to be updated; y is the disk enclosure ID; z is the disk slot number (see above).

Result for our example in this guide:

root@rescue:~# /opt/MegaRAID/storcli/storcli64 /c0 /e252 /s0 show all | grep -i 'Firmware Revision'
Firmware Revision = B17D
root@rescue:~# /opt/MegaRAID/storcli/storcli64 /c0 /e252 /s1 show all | grep -i 'Firmware Revision'
Firmware Revision = B17D
Info

The firmware version displayed for each disk must be B17D, corresponding to the firmware we have just flashed.

Your NVMe drive now should have the firmware version BCGNB17D.

 

Go further

Browse all the Dedicated Servers guides.

Browse the rest of the OVHcloud US documentation for guides on our other products and services.

Learn more about Dedicated Servers on the OVHcloud US website.

If you need training or technical assistance to implement our solutions, contact your sales representative or click on this link to get a quote and ask our Professional Services experts for a custom analysis of your project.