Updating cd drive firmware
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.
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.
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.
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.
To ensure common device behavior, we began by defining new and - for Windows 10 and Windows Server 2016 - optional Hardware Lab Kit (HLK) requirements for SAS, SATA, and NVMe devices.
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.
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.
Search for updating cd drive firmware:
Contact your solution vendor for info about whether your hardware supports Windows updating the drive firmware.