Firmware updating

A Storage Spaces Direct cluster achieves resiliency by spreading data across multiple server nodes; it is possible for the health service to isolate an entire node worth of drives for updates.

firmware updating-54

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.

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.

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.

Most routers have a built-in update checker, which may or may not perform the entire process automatically.

If you're using an Apple Air Port router, you can use the Air Port Utility program to check for updates.

It is possible that new firmware on unsupported hardware could negatively affect reliability and stability, or even cause data loss.

Administrators should read the release notes a given update comes with to determine its impact and applicability.

Updating the firmware for drives has historically been a cumbersome task with a potential for downtime, which is why we're making improvements to Storage Spaces, Windows Server, and Windows 10, version 1703 and newer.

Tags: , ,