February 18, 20233 yr Hi All, Interesting issue has developed over the past few days. I have been unable to access my server due to an Error 500 code, inconvenient but not the end of the world so I just left it. Today it appeared that the docker containers failed (Plex stopped working). I decided to try the good old turn it off and on again, in hindsight this was not the best idea. Server booted up and went into Unraid as normal, drives automatically re-mounted themselves and I thought we were back up and running. Then I looked and noticed docker is no longer running and a grey dot has appeared next to the 'cache' label instead of the usual green and now the drive has a reported capacity of 0 B (It should be 2 TB) My first instinct tells me that the drive has failed, although it is a reasonably new drive (6 months old). I thought It was worth a post here to see if anyone has any ideas on how to proceed.
February 18, 20233 yr Community Expert Feb 17 21:07:09 PLEX kernel: nvme nvme1: I/O 896 QID 6 timeout, aborting Feb 17 21:07:39 PLEX kernel: nvme nvme1: I/O 896 QID 6 timeout, reset controller Feb 17 21:08:09 PLEX kernel: nvme nvme1: I/O 24 QID 0 timeout, reset controller Feb 17 21:09:12 PLEX kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Feb 17 21:09:12 PLEX kernel: nvme1n1: I/O Cmd(0x2) @ LBA 0, 32 blocks, I/O Error (sct 0x3 / sc 0x71) Feb 17 21:09:12 PLEX kernel: I/O error, dev nvme1n1, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0 Feb 17 21:09:12 PLEX kernel: nvme nvme1: Abort status: 0x371 Feb 17 21:09:43 PLEX kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Feb 17 21:09:43 PLEX kernel: nvme nvme1: Removing after probe failure status: -19 Feb 17 21:10:13 PLEX emhttpd: error: ckmbr, 2291: Input/output error (5): read: /dev/nvme1n1 Problem with the NVMe device, try power cycling the server, a reboot might not be enough, and post new diags after array start.
February 18, 20233 yr Author plex-diagnostics-20230218-1340.zip It appears that has mostly worked. The docker containers are back online but the docker tab in the UI is looking different.
February 19, 20233 yr Community Expert This time it worked during pool mount but if failed again shortly after: Feb 18 13:32:18 PLEX kernel: nvme nvme1: I/O 150 QID 2 timeout, aborting Feb 18 13:32:18 PLEX kernel: nvme nvme1: I/O 820 QID 4 timeout, aborting Feb 18 13:32:19 PLEX kernel: nvme nvme1: I/O 355 QID 8 timeout, aborting Feb 18 13:32:19 PLEX kernel: nvme nvme1: I/O 356 QID 8 timeout, aborting Feb 18 13:32:49 PLEX kernel: nvme nvme1: I/O 150 QID 2 timeout, reset controller Feb 18 13:33:19 PLEX kernel: nvme nvme1: I/O 4 QID 0 timeout, reset controller Feb 18 13:34:19 PLEX kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Feb 18 13:34:19 PLEX kernel: nvme nvme1: Abort status: 0x371 ### [PREVIOUS LINE REPEATED 3 TIMES] ### Feb 18 13:34:50 PLEX kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Feb 18 13:34:50 PLEX kernel: nvme nvme1: Removing after probe failure status: -19 Try re-seating the device, if it keeps failing you'll probably have to replace it.
February 23, 20233 yr Author Reseated the drive and it failed again, this time failing to find the device... I will attempt a few more times but realistically all the signs are pointing to a failed drive, bit of a bummer the drive is only 277 days old.
February 24, 20233 yr Author plex-diagnostics-20230224-1456.zip Development: Tried to reseat the drive for the 5th time and this time it appears everything has fired up correctly. Going to replace the drive anyway but it would be interesting to see what went wrong.
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.