NVME-SEAGATE-GET-(1)

πŸ’… nvme-seagate-get-ctrl-tele β€” the NVMe Manual, bestie edition πŸŽ€

okay so literally the whole point of this page (nvme-seagate-get-(1) from the NVMe Manual, iykyk) is one little command that pulls the Seagate Controller-Initiated Telemetry for you. you get it as a hex dump by default, or as raw binary if you're feeling fancy. let's get into it πŸ¦‹


✨ NAME ✨

nvme-seagate-get-ctrl-tele β€” grab the Seagate Controller-Initiated Telemetry, either as a hex dump (that's the default, no cap) or in binary format πŸ’–


✨ SYNOPSIS ✨

nvme [<global-options>] seagate get-ctrl-tele <device> [OPTIONS]

like, that's the whole shape of it. so clean ✨


✨ DESCRIPTION ✨

okay real talk first: this command only works on Seagate devices that support this feature. periodt. and heads up bestie β€” not all commands work across all product families, so don't come for me if your drive isn't the vibe πŸ’€

The <device> parameter is mandatory (literally cannot skip it, she is required) and it can be either:

  • an NVMe character device, ex: /dev/nvme0
  • or an nvme block device, ex: /dev/nvme0n1

either one is valid, you pick your fighter 🫢


✨ OPTIONS ✨

  • -n <NUM>, --namespace-id=<NUM> β€” the desired namespace. and the broadcast value 0xffffffff can also be given as all or -1. so you've got options, literally 🌸
  • -b, --raw-binary β€” output in raw format. this is the binary one, not the hexdump one. choose wisely πŸ’…

✨ GLOBAL OPTIONS ✨

these ones are defined up at the top-level nvme command and they're all available to this subcommand too, so you're never left hanging πŸ‘‘

  • --dry-run β€” print the command that would be executed, but don't actually execute it. it's giving window shopping πŸ›οΈ
  • --no-ioctl-probing β€” disable probing for 64-bit IOCTL support. yep, that's the whole thing ✨
  • --no-retries β€” disable retry logic on transient errors. no second chances, she's one and done πŸ’€
  • -o <fmt>, --output-format=<fmt> β€” set the reporting format to normal, tabular, json, or binary. only one output format at a time bestie, don't be greedy πŸŽ€
  • --output-format-version=<version> β€” select the output format version. version 1 uses the original field naming, while version 2 (the default) provides more consistent and script-friendly field names. other versions are rejected β€” so don't try it πŸ™ˆ
  • --quiet β€” suppress informational messages. errors are still reported though (she's not that quiet), and --quiet cancels any --verbose for the library log level. they literally cancel each other out, iconic 🌈
  • --set-options=<key=value>[,<key=value>...] β€” set libnvme library options for this invocation. the supported keys are force-4k, mi-probe-enabled, test-base-dir and test-sysfs-dir. mix and match, go off ⭐
  • --timeout=<ms> β€” set the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). no rush, take your time 🧚
  • -v, --verbose β€” increase the level of detail in the output. may be specified multiple times to further increase verbosity. stack it, queen πŸ‘‘
also these options can be set as machine-wide defaults in nvme-cli.conf(5). and a command-line flag always overrides the file β€” CLI stays main character energy, no cap πŸ’œ

✨ EXAMPLES ✨

get the controller initiated telemetry log in hexdump or binary format for the specified device, like so:

# nvme seagate get-ctrl-tele /dev/nvme0

that's it, that's the whole ritual πŸ”₯


✨ NVME ✨

part of the nvme-user suite πŸ¦‹


okay that's the whole page bestie, you're officially educated πŸ’– 🩷

sign-off corner: this little gem comes from the NVMe manual set, dated 10/30/2026 β€” go forth and telemetry responsibly, muah πŸ’‹πŸŽ€

πŸ“¦ where this page comes from