Using the Linux fuel gauge command
Learn how to use the Linux operating system fuel gauge command to find the amount of remaining life in a mainstream solid-state drive (SSD).
To use the fuel gauge tool for the Linux operating system, complete the following steps:
- If the system has logical partitions, complete this procedure from the logical partition that reported the problem.
- Choose from the following options:
- In the command line, enter the following
command:
$ iprconfig
- In the main menu, select the Devices Statistics option.
- In the Device selection screen, select Read Intensive SSD (Mainstream SSD) by moving the cursor to the correct line and pressing 1.
- Press Enter to confirm. The statistics for the selected device is shown.
- Review the information in the first block of information.
- Continue with step 10.
- To use the ssd-report command
in the iprutils command-line interface, complete
the following steps:
- Type $ iprconfig -c ssd-report <dev>
Where <dev> is the device you want to use.
- Review the information that is shown.
- Continue with step 10.
- Type $ iprconfig -c ssd-report <dev>
- Interpret the statistics:
- Total Bytes Written: Number of GB already written to the device
- Number of Bytes reported by Warranty: Number of GBs that can be written according to the specification
- Life Remaining Gauge: An estimate of how much of the device's life has been consumed
- PFA Trip: The device has detected an issue that could lead to a failure
- Power-on Days: Number of days since the last power-on
- Is the value in the Life Remaining Gauge field less than or equal to 2
percent?
- Yes: Continue with the next step.
- No: The mainstream SSD is not reporting a change in status for the number of write operations available.
- Is the value in the Life Remaining Gauge field 0 percent?
- The mainstream SSD reached the limit for the number of write operations that are supported.
Write operations to the SSD become slower over time, and at some point the SSD becomes a read-only
drive. When the operating system writes to the read-only drive, the write operations are rejected,
and the operating system considers the drive as if a failure occurred. For example, if the operating
system writes to a drive that is in a RAID array and if the write operations are rejected, the array
becomes exposed. To support normal write operations, the drive must be replaced.
Replacement of the mainstream SSD might not be covered by the system's level of service entitlement, depending on the terms and conditions of the system. For more information about mainstream SSDs, see Mainstream solid-state drives. This ends the procedure.
- The mainstream SSD is nearing the limit for the number of write operations that are supported.
No service action is required at this time. Note: After the mainstream SSD reaches the limit for the number of write operations that are supported, write operations to the SSD become slower over time, and at some point the SSD becomes a read-only drive. To support normal write operations, the drive must be replaced. Replacement of the mainstream SSD might not be covered by the system's level of service entitlement, depending on the terms and conditions of the system. For more information about mainstream SSDs, see Mainstream solid-state drives. This ends the procedure.
Parent topic: Mainstream solid-state drives
Last updated: Fri, July 26, 2019