Using the Health Service to roll-out firmware across a cluster is very simple and involves the following steps: At this point, the Health Service will inspect and parse the xml and identify any drives that do not have the desired firmware version deployed.
It will then proceed to re-direct I/O away from the affected drives – going node-by-node – and updating the firmware on them.
The drive will first load the new firmware image to an internal staging area. This means that this drive serves no data during the activation.
An application accessing data on this drive would have to wait for a response until the firmware activation completes.
The second cmdlet, Update-Storage Firmware, enables administrators to update the drive firmware with an image file, if the drive supports the new firmware update mechanism.
You should obtain this image file from the OEM or drive vendor directly. During this time the drive will not be able to respond to I/O commands as an internal reset occurs.
It is possible that new firmware on unsupported hardware could negatively affect reliability and stability, or even cause data loss.
If left unchecked (with Software Update set to On), you will be notified when an update is available, but will have to manually complete the process.
Here's an example of the cmdlet in action: $pd | Update-Storage Firmware -Image Path C:\Firmware\[email protected] Number 0 $pd | Get-Storage Firmware Information Supports Update : True Number Of Slots : 1 Active Slot Number : 0 Slot Number : Is Slot Writable : Firmware Version In Slot : Drives typically do not complete I/O requests when they activate a new firmware image.
How long a drive takes to activate depends on its design and the type of firmware you update.
Once a server is in production, it's a good idea to make as few changes to the server as is practical.
However, there may be times when your solution vendor advises you that there is a critically important firmware update for your drives.