NVME-MICRON-SMART-LOG(1)

πŸ“¦ version 3.2, in arch rolling

πŸŽ€ nvme-micron-smart-log β€” the nvme-micron-smart-log(1) glow-up πŸŽ€

okay so bestie. you found the nvme-micron-smart-log page, and honestly? it's lowkey iconic. it's section 1 of the manual (that's the "just run the command, babe" section), and it's all about pulling the SMART/Health log off your NVMe drive but with Micron's extra ✨special✨ vendor fields decoded for you. no cap.


✨ NAME ✨

nvme-micron-smart-log β€” retrieve the SMART/Health log with Micron vendor-specific fields. that's the whole vibe. 🫢


🌸 SYNOPSIS 🌸

nvme [<global-options>] micron smart-log <device>

like, that's it. that's the whole invocation. so clean. πŸ’…


πŸ¦‹ DESCRIPTION πŸ¦‹

so for the NVMe device you hand it, this bad boy retrieves the SMART/Health Information log page and shows it to you with the Micron vendor-specific fields decoded. the standard stuff plus the exclusive Micron tea β˜•

the <device> parameter is mandatory β€” not optional, not vibes-based, mandatory β€” and it can be either:

  • the NVMe character device (ex: /dev/nvme0), or
  • a namespace block device (ex: /dev/nvme0n1)

either one works, pick your fighter. 😌

this command extends the standard SMART log with Micron-specific fields, which are:

  • OLEC (Operational Lifetime Energy Consumed) β€” living at bytes 232-239 in the SMART log reserved area. it reports the cumulative energy consumed by the device. so it's giving "how much juice has this thing slurped in total" πŸ”‹
  • IPM (Interval Power Measurement) β€” living at bytes 240-243 in the SMART log reserved area. it reports the power measurement over the sampling interval. iykyk ⚑

πŸ’– OPTIONS πŸ’–

🌈 GLOBAL OPTIONS 🌈

these are defined at the top-level nvme command and are available to this subcommand. so they're not this command's options, they're the whole family's options, and they still very much apply here. family privilege fr fr.

  • --dry-run β€” prints the command that would be executed, but does not actually execute it. it's giving window shopping. you see it, you don't buy it. πŸ‘€
  • --no-ioctl-probing β€” disables probing for 64-bit IOCTL support. bye bye probing πŸ‘‹
  • --no-retries β€” disables retry logic on transient errors. one shot, no second chances, main character energy only πŸ’€
  • -o <fmt>, --output-format=<fmt> β€” sets the reporting format to normal, tabular, 'json, or binary. only one output format may be used at a time, so don't get greedy bestie πŸ’…
  • --output-format-version=<version> β€” selects the output format version. version 1 uses the original field naming, while version 2 (the default) provides more consistent and script-friendly field names. any other version is rejected β€” nope, not allowed, denied πŸ™ˆ
  • --quiet β€” suppresses informational messages. errors are still reported, and --quiet cancels any --verbose for the library log level. so they can't both win, it's a whole veto situation 😭
  • --set-options=<key=value>[,<key=value>...] β€” sets libnvme library options for this invocation. the supported keys are force-4k, mi-probe-enabled, test-base-dir and test-sysfs-dir. exact keys, bestie, don't freestyle them πŸŽ€
  • --timeout=<ms> β€” sets the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). so if you truly have nowhere to be, that's your setting ⏳
  • -v, --verbose β€” increases the level of detail in the output. may be specified multiple times to further increase verbosity. stack it, bestie, stack it πŸ“š
also!! these options can be set as machine-wide defaults in nvme-cli.conf(5). a command-line flag always overrides the file. so the file is the default and the flag is the "actually, no" πŸ’…

⭐ EXAMPLES ⭐

  • display the SMART log in human-readable format:
# nvme micron smart-log /dev/nvme0
  • display the SMART log in JSON format:
# nvme micron smart-log /dev/nvme0 -o json

literally just vibes and a device path. you got this 🫢


πŸ‘‘ NVME πŸ‘‘

part of the nvme-user suite. that's the origin story 🧚


and that's the page, bestie πŸ’œ this whole thing lives in the nvme-user suite β€” and the footer at the bottom is just the page name echoed back at you like a little mirror, no extra date stamping going on. so go forth, decode those Micron fields, and slay πŸŽ€βœ¨πŸŒΈπŸ¦‹πŸ’…

πŸ“¦ where this page comes from