NVME_MI_ADMIN_GET_LOG_DEVICE_SELF_TEST(2)

🌸 NAME 🌸

nvme_mi_admin_get_log_device_self_test — bestie, this one pulls up the device self test log for you 💖

It lives in the libnvme API manual, so you already know it's the good stuff.

---

✨ SYNOPSIS ✨

int nvme_mi_admin_get_log_device_self_test (nvme_mi_ctrl_t ctrl , struct
nvme_self_test_log *log );

---

🎀 ARGUMENTS 🎀

• ctrl — the controller you're interrogating, aka the thing you wanna know about 🔍
• log — the userspace address of the log payload. yeah, it's just a pointer to where the log is gonna land 💅

---

🦋 DESCRIPTION 🦋

okay so here's the tea, and it's genuinely good tea 🍵

This log page is giving you two whole things. First: the status of a self test that's currently in progress, plus the percent complete of that operation — so you always know exactly how far along it is, no guessing, no vibes-based estimation, fr fr.

Second: the results of the previous 20 self-test operations. twenty!! that's so much history, she's keeping receipts 💀✨

So basically one call and you've got the live status and the whole saga of everything that came before. iconic behavior honestly.

---

💜 RETURN 💜

She gives you back the nvme command status if a response was received — peep enum nvme_status_field for the deets on what those values mean 👑

Otherwise you get -1 with errno set. so like, check your errno bestie, it's trying to tell you something 😭

ngl if you're seeing -1, that's your sign to go read errno before you do literally anything else. she's not being mysterious for fun.

---

🌈 SEE ALSO 🌈

• enum nvme_status_field — go look at it, it's right there in the return value lore 🫶

---

and that's the whole page, no cap 🎀 shoutout to the libnvme API manual, July 2026 edition, for keeping us all fed and informed. slay, take care of your controllers, and may your self tests always report back to you promptly ✨👑💖