SYNOPSIS

nvme [<global-options>] wdc vs-fw-activate-history <device>

DESCRIPTION

For the NVMe device given, read a Vendor Unique WDC log page that returns the firmware activation history.

The <device> parameter is mandatory and must be the NVMe character device (ex: /dev/nvme0).

This will only work on WDC devices supporting this feature. Results for any other device are undefined.

On success it returns 0, error code otherwise.

Firmware Activate History Log Page Data Output Explanation

Field Description

Entry Number

The number of fw activate entry. The most recent 20 entries will be displayed.

Power on Hour

The time since the power on in hours:minutes:seconds.

Power Cycle Count

The power cycle count that the firmware activation occurred.

Current Firmware

The firmware level currently running on the SSD before the activation took place.

New Firmware

The new firmware level running on the SSD after the activation took place.

Slot Number

The slot that the firmware is being activated from.

Commit Action Type

The commit action type associated with the firmware activation event

Result

The result of the firmware activation event. The output shall be in the format: Pass or Failed + error code

GLOBAL OPTIONS

The following options are defined at the top-level nvme command and are available to this subcommand:

--dry-run

Print the command that would be executed, but do not actually execute it.

--no-ioctl-probing

Disable probing for 64-bit IOCTL support.

--no-retries

Disable retry logic on transient errors.

-o <fmt>
--output-format=<fmt>

Set the reporting format to normal, tabular, 'json, or binary. Only one output format may be used at a time.

--output-format-version=<version>

Select the output format version. Version 1 uses the original field naming, while version 2 (default) provides more consistent and script-friendly field names.

--timeout=<ms>

Set the timeout for the command in milliseconds.

-v
--verbose

Increase the level of detail in the output. May be specified multiple times to further increase verbosity.

EXAMPLES

  • Has the program issue WDC vs-fw-activate-history Vendor Unique Command :

    # nvme wdc vs-fw-activate-history /dev/nvme0

NVME

Part of the nvme-user suite.