65 days ago · 10 min read1976 words · Tech · hide · Fediverse post

I saw this today in my logs on r730-01. It looks similar to a previous DEGRADED even back on July 2. In this case, the device is S7KGNU0Y915666E, not S7KGNU0Y912955D as it was back then. Sep 12 03:46:54 r730-01 kernel: nvme1: Resetting controller due to a timeout. Sep 12 03:46:54 r730-01 kernel: nvme1: event="start" Sep 12 03:46:54 r730-01 kernel: nvme1: Waiting for reset to complete Sep 12 03:47:14 r730-01 syslogd: last message repeated 197 times Sep 12 03:47:14 r730-01 ZFS[96518]: vdev I/O failure, zpool=data04 path=/dev/gpt/S7KGNU0Y915666E offset=270336 size=8192 error=6 Sep 12 03:47:14 r730-01 kernel: nvme1: Waiting for reset to complete Sep 12 03:47:14 r730-01 kernel: nvme1: controller ready did not become 0 within 20500 ms Sep 12 03:47:14 r730-01 kernel: nvme1: event="timed_out" Sep 12 03:47:14 r730-01 kernel: nvme1: failing outstanding i/o Sep 12 03:47:14 r730-01 kernel: nvme1: FLUSH (00) sqid:1 cid:112 nsid:1 Sep 12 03:47:14 r730-01 kernel: nvme1: ABORTED_BY_REQUEST (00/07)…

Commenting on Bubbles has been removed. Why? If you want to talk about this post, write to the author, use the comments on their blog if it has them, or reply with a "RE:" post on your own blog. Suggestions? feedback@bubbles.town