October 23, 2025Oct 23 It is Disk 4 (screenshot) and is a 4TB, nvme drive that I only used for VMs.If look in /mnt/disk4, everything is there (screenshot)In the lsblk outputs (screenshot), I believe the correct drive is the one labled md4p1Logs show errors for my GPU but nothing for the disks. I did see some general disk stuff (screenshots). These lines seem to be the only indication anything didn't happen:Oct 21 08:26:55 Monarch kernel: mdcmd (5): import 4Oct 21 08:26:55 Monarch kernel: md: import_slot: 4 emptyIm at a bit of a loss on how to troubleshoot this, please let me know if I can provide more info. Any help is very much appreciated:) monarch-diagnostics-20251023-0943.zip Edited October 23, 2025Oct 23 by bukweet + diagnostics
October 23, 2025Oct 23 8 hours ago, bukweet said:If look in /mnt/disk4, everything is there (screenshot)This is expected as when a drive is disabled then Unraid starts emulating it using the combination of the other drives plus parity. As was mentioned we need diagnostics to give any sort of informed feedback.
October 23, 2025Oct 23 Looking at the diagnostics it seems that the drive that should be disk4 (a 4TB drive) is no longer being seen at the hardware level so it may have really failed. Have you checked if it is visible at the BIOS level? Have you done a server power cycle in case that is needed?
October 23, 2025Oct 23 Oct 12 19:58:30 Monarch kernel: nvme nvme0: I/O 9 QID 0 timeout, reset controllerOct 12 19:59:52 Monarch kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1Oct 12 19:59:52 Monarch kernel: nvme nvme0: Abort status: 0x371### [PREVIOUS LINE REPEATED 7 TIMES] ###Oct 12 20:00:12 Monarch kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1Oct 12 20:00:12 Monarch kernel: nvme nvme0: Disabling device after reset failure: -19NVMe device assigned as disk4 dropped offline; a power cycle (not just a reboot) may bring it back online.
October 23, 2025Oct 23 Author 8 hours ago, itimpi said:Have you checked if it is visible at the BIOS level?Edit: Well, I thought it was dead. Rebooted and jumped back into the server and the drive is sitting in Unassigned Devices. I was able to mount and ls the files. I've attached fresh diagnosticsEdit 2: Attached a SMART report. I think it dead lolThats a damn shame. I dont think I even got a year out of it:(>>> Yeah, I went and looked at when I bought it and its been a year to the month 🤣Maybe I'll get an m.2 -> usb dock and look into it more. Many thanks for taking the time! monarch-diagnostics-20251023-1827.zip Samsung_SSD_990_PRO_4TB_S7KGNU0X530779F-20251023-1640.txt Edited October 23, 2025Oct 23 by bukweet
October 24, 2025Oct 24 Solution The emulated disk is mounting. Assuming the content looks correct, you can rebuild, or if nothing was written to the emulated disk, and to avoid a full device write cycle, do a new config and check parity is already valid, then run a correcting parity check.P.S. It is not recommended to use SSDs in the array, since they cannot be trimmed.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.