However, if you're going to update the firmware of a production drive, make sure to read our tips on how to minimize the risk while using this powerful new functionality.
Warning Firmware updates are a potentially risky maintenance operation and you should only apply them after thorough testing of the new firmware image.
Per default, the Health Service will wait 7 days before updating the 2, …) updates with a 1 day delay.
Should an administrator find the firmware to be unstable or otherwise undesirable, she can stop further roll-out by the health service at any time.
If this occurs, here are a few good practices to follow before applying any drive firmware updates: Windows Server 2016 includes a Health Service for Storage Spaces Direct deployments (including Microsoft Azure Stack solutions).
The main purpose of the Health Service is to make monitoring and management of your hardware deployment easier.
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 expected and normal for Storage Spaces to transition to a "degraded" mode of operation while firmware is rolled out.To ensure a stable roll-out and sufficient validation time of a new firmware image, there exists a significant delay between the updates of several servers.As part of its management functions, it has the capability to roll-out drive firmware across an entire cluster without taking any workloads offline or incurring downtime.This capability is policy-driven, with the control in the admin's hands.These requirements outline which commands a SATA, SAS, or NVMe device must support to be firmware-updatable using these new, Windows-native Power Shell cmdlets.