High Grade Dedicated Servers - Upgrading your SSD SAS Western Digital SS530 firmware (EN)
Objective
Routine firmware updates play a pivotal role in upholding your drives 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 BPGNB969). We strongly recommend that you update your firmware to avoid premature end-of-life.
Firmware Release Notes: https://last-public-ovh-baremetal.snap.mirrors.ovh.net/hardware/SS530/PCN-005196-A01.pdf
The purpose of this guide is to help you upgrade your SSD SAS Western Digital SS530 firmware.
Disk Part Number:
- WUSTR6440ASS201 (400GB capacity)
- WUSTR6416ASS201 (1.6TB capacity)
- WUSTR1538ASS201 (3.84TB capacity)
- WUSTR1515ASS201 (15.36TB capacity)
Requirements
- A bare metal server with SSD SAS Western Digital SS530, from the following:
- High Grade HCI
- mHG/HG/BHG 2019
Instructions
- Before attempting any firmware update, a backup of the data on the drive must be made. Use our guide on Backup Storage to learn how to back up your data.
- 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.
All commands must be run as root for Linux and VMWare and with an administrator account for Windows.
Linux
Hardware/software configuration tested on the OVHcloud side
| Platform | Flash tool | Firmware | Result |
|---|---|---|---|
| Debian 11/12 OS | StorCLI 007.2705.0000.0000 | BPGNB969 | OK |
| Ubuntu 22.04 OS | StorCLI 007.2705.0000.0000 | BPGNB969 | OK |
| Rocky 7/8 OS | StorCLI 007.2705.0000.0000 | BPGNB969 | OK |
| Debian 11/12 OS + HARD RAID | StorCLI 007.2705.0000.0000 | BPGNB969 | OK |
| Ubuntu 22.04 OS + HARD RAID | StorCLI 007.2705.0000.0000 | BPGNB969 | OK |
| Rocky 7/8 OS + HARD RAID | StorCLI 007.2705.0000.0000 | BPGNB969 | OK |
Step 1 - Download StorCLI
Download the StorCLI package on your server:
Unpack the global archive:
Then unpack the archive containing the binaries for the various OS:
Step 2 - Install StorCLI
- For Debian, Ubuntu, Mint, Proxmox and similar:
- For RHEL, CentOS, RockyLinux, AlmaLinux, Fedora and similar:
Step 3 - Check if a firmware update is needed
Run the following command to retrieve your controller ID in the Ctl field:
Example:
Then retrieve enclosure and disk slot numbers by running the command:
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 SS530 because the firmware update only concerns these disk reference and your server may have other disks connected to it.
In our example, 2 disks need to be updated (:0 and :1). 0/1 is the disk slot number:
Step 4 - Firmware update
Download the firmware binary on your server:
Execute the following command for each identified disk displayed in step 3:
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 BPGNB969. Here's how we update the 2 disks and the command line returns:
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:
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:
The firmware version displayed for each disk must be B969, corresponding to the firmware we have just flashed.
ESXi 7.x
Hardware/software configuration tested on OVHcloud side
| Platform | Flash tool | Firmware | Result |
|---|---|---|---|
| ESXi 7.0 U3o OS + data in clear from disk | StorCLI 007.2705.0000.0000 | BPGNB969 | OK |
| ESXi 7.0 U3o OS + HARD RAID | StorCLI 007.2705.0000.0000 | BPGNB969 | OK |
Step 1 - Download StorCLI
Download the StorCLI package on your server:
Unpack the global archive:
Then unpack the archive containing the binaries for the various OS:
Step 2 - Install StorCLI
Unpack the ESXi 7.x archive:
Then install StorCLI:
<absolute path> must be replaced with the .vib package absolute path from the root directory (/).
Step 3 - Check if a firmware update is needed
Run the following command to retrieve your controller ID in the Ctl field:
Example:
Then retrieve enclosure and disk slot numbers by running the command:
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 SS530 because the firmware update only concerns this disk reference and your server may have other disks connected to it.
In our example, 2 disks need to be updated (:0 and :1). 0/1 is the disk slot number:
Step 4 - Firmware update
Download the firmware binary on your server:
Execute the following command for each identified disk displayed in step 3:
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 BPGNB969. Here's how we update the 2 disks and the command line returns:
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:
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:
The firmware version displayed for each disk must be B969, corresponding to the firmware we have just flashed.
ESXi 8.x
Hardware/software configuration tested on OVHcloud side
| Platform | Flash tool | Firmware | Result |
|---|---|---|---|
| ESXi 8.0b OS | StorCLI 007.2705.0000.0000 | BPGNB969 | OK |
| ESXi 8.0b OS + HARD RAID | StorCLI 007.2705.0000.0000 | BPGNB969 | OK |
Step 1 - Download StorCLI
Download the StorCLI package on your server:
Unpack the global archive:
Then unpack the archive containing the binaries for the various OS:
Step 2 - Install StorCLI
Unpack the ESXi 8.x archive:
Then install StorCLI:
<absolute path> must be replaced with the .vib package absolute path from the root directory (/).
Run a server reboot, which is necessary in order to update the binary.
Step 3 - Check if a firmware update is needed
Run the following command to retrieve your controller ID in the Ctl field:
Then retrieve enclosure and disks slots numbers by running the command:
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 SS530 because the firmware update only concerns these disk reference and your server may have other disks connected to it.
In our example, 2 disks need to be updated (:0 and :1). 0/1 is the disk slot number:
Execute the following command for each identified disk displayed in step 3:
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 BPGNB969. Here's how we update the 2 disks and the command line returns:
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:
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:
The firmware version displayed for each disk must be B969, corresponding to the firmware we have just flashed.
Windows
Hardware/software configuration tested on OVHcloud side
| Platform | Flash tool | Firmware | Result |
|---|---|---|---|
| Windows 2016 | StorCLI 007.2705.0000.0000 | BPGNB969 | OK |
| Windows 2019 | StorCLI 007.2705.0000.0000 | BPGNB969 | OK |
| Windows 2022 | StorCLI 007.2705.0000.0000 | BPGNB969 | OK |
| Windows 2016 + HARD RAID | StorCLI 007.2705.0000.0000 | BPGNB969 | OK |
| Windows 2019 + HARD RAID | StorCLI 007.2705.0000.0000 | BPGNB969 | OK |
| Windows 2022 + HARD RAID | StorCLI 007.2705.0000.0000 | BPGNB969 | OK |
Step 1 - Download StorCLI
Download the StorCLI via this link: https://docs.broadcom.com/docs-and-downloads/007.2705.0000.0000_storcli_rel.zip
Tool version: StorCLI 007.2705.0000.0000
Unzip the archive. The tool storcli.exe to use is located in the folder: storcli_rel\Unified_storcli_all_os.zip\Unified_storcli_all_os\Windows
Step 2 - Check if a firmware update is needed
Open Windows PowerShell as Administrator, then run the following command in the directory where storcli.exe was unzipped to retrieve your controller ID in the Ctl field:
Then retrieve enclosure and disk slot numbers by running the command:
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 SS530 because the firmware update only concerns these disk reference and your server may have other disks connected to it.
In our example, 2 disks need to be updated (:0 and :1). 0/1 is the disk slot number:
Step 3 - Firmware update
Download the firmware binary on your server:
Execute the following command for each identified disk displayed in step 2:
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 BPGNB969. Here's how we update the 2 disks and the command line returns:
At this point the firmware update is complete, please reboot your server.
Step 4 - Check the firmware version after the server reboot
Execute the following command for each identified disk displayed in step 2:
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:
The firmware version displayed for each disk must be B969, corresponding to the firmware we have just flashed.
Go further
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.
Join our community of users.