NVME-WDC-GET-CRAS(1)

📦
version 3.2 · 14 versions
, in arch rolling

💾 nvme-wdc-get-crash-dump — the NVMe WDC crash dump girly's moment 💅

okay so. bestie. you know how your WDC drive sometimes has a whole little crash dump just sitting there waiting to be rescued? yeah. this is the manual page for the tool that goes and gets it. we're in the NVMe manual, this is the nvme-wdc-get-cras page (that's the short name, the real name below is the long one, iykyk 🎀), and honestly? this one is kinda iconic.

✨ NAME ✨

nvme-wdc-get-crash-dump — Retrieve WDC device's crash dump. literally just. go get the dump. that's the whole vibe 🫶

✨ SYNOPSIS ✨

nvme [<global-options>] wdc get-crash-dump <device>
                        [--output-file=<FILE>, -O <FILE>]

✨ DESCRIPTION ✨

so for the NVMe device you give it, this bad boy sends the WDC vendor unique crash dump request and saves the result to a file. no cap, that's it. in the current implementation, the crash dump is captured if it is present. on success it will save the dump in a file with the appropriate suffix. and like... heads up bestie 🫣 — this command will clear the available dump from the device on success. so it's giving "one-time grab", not "peek at it and put it back". the dump is yours once it's saved, but it's gone from the drive, periodt.

the <device> parameter is mandatory and it's an NVMe character device (ex: /dev/nvme0). you cannot skip it. do not try to skip it. 💀

🌸 real talk: this will only work on WDC devices supporting this feature. Results for any other device are undefined. so don't be brave with your non-WDC drive, okay? that's not main character energy, that's just chaos.

✨ OPTIONS ✨

  • -O <FILE>, --output-file=<FILE> — the output file. defaults to the device serial number followed by a "crash_dump" suffix. so if you don't pick a name, it picks one for you, cute of it honestly 💖

🌈 GLOBAL OPTIONS 🌈

okay so the following options are defined at the top-level nvme command and are available to this subcommand too. like they're handed down. nepotism but make it CLI ✨

  • --dry-run — Print the command that would be executed, but do not actually execute it. all the anticipation, zero commitment, honestly relatable 🫠
  • --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. pick one. one. singular. 💅
  • --output-format-version=<version> — Select the output format version. Version 1 uses the original field naming, while version 2 (the default, bestie) provides more consistent and script-friendly field names. Other versions are rejected. so like... 1, 2, or get out 🚪
  • --quiet — Suppress informational messages. Errors are still reported, and --quiet cancels any --verbose for the library log level. it's the "shhh, i'm focusing" flag 🤫
  • --set-options=<key=value>[,<key=value>...] — Set libnvme library options for this invocation. Supported keys are force-4k, mi-probe-enabled, test-base-dir and test-sysfs-dir.
  • --timeout=<ms> — Set the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). no clock-watching, we stay patient ⏳
  • -v, --verbose — Increase the level of detail in the output. May be specified multiple times to further increase verbosity. stack 'em like bracelets, the more the louder 📣

these options can also be set as machine-wide defaults in nvme-cli.conf(5). A command-line flag always overrides the file. flag > file, always, no debate 🏆

🦋 EXAMPLES 🦋

  • Gets the crash dump from the device and saves to the default file in the current directory (e.g. STM00019F3F9crash_dump.bin):
# nvme wdc get-crash-dump /dev/nvme0
  • Gets the crash dump from the device and saves to a defined file in the current directory (e.g. testSTM00019F3F9crash_dump.bin):
# nvme wdc get-crash-dump /dev/nvme0 -O test
  • Gets the crash dump from the device and saves to a defined file with a pathname (e.g. /tmp/testSTM00019F3F9crash_dump.bin):
# nvme wdc get-crash-dump /dev/nvme0 -O /tmp/test

look at those suffixes doing their thing 😌 note how -O test and -O /tmp/test still get the serial number + crash_dump treatment. it's giving consistent. it's giving reliable. it's giving slay 🍓

👑 NVME 👑

Part of the nvme-user suite. you're in good company, bestie 💜

🧚 and that's the page!! this one's from the NVMe manual, dated 10/30/2026, living in source/version NVME-WDC-GET-CRAS(1) territory — so go forth, grab that crash dump, and remember: the dump is cleared on success, so treat it like your last slice of cake. no take-backsies. bye bestie, love u, stay iconique 💅✨🎀
📦 where this page comes from