dimes007 Posted September 13, 2019 Share Posted September 13, 2019 I've got an Adata XPG SX8200 Pro pci x4 NVME drive XFS formatted and mounted with unassigned device. It goes offline and "missing" in unassigned deviced on occasion. Last time I had 22 days of uptime. This time 9 days. Relevant System Log pasted below. This has been happening on and off for months. It was my cache but I moved that to an old SATA ssd so at least when the Adata goes offline my machine can stay up. PCIe ACS Override setting is enabled. I'm unsure of what to do to fix it and am also unsure if I should try a different PCI x4 SSD or I should just get a SATA SSD. Any help or suggestions appreciated. Thanks, --dimes Sep 13 10:31:52 pi kernel: nvme nvme0: I/O 336 QID 3 timeout, aborting Sep 13 10:31:52 pi kernel: nvme nvme0: I/O 378 QID 3 timeout, aborting Sep 13 10:31:52 pi kernel: nvme nvme0: I/O 427 QID 3 timeout, aborting Sep 13 10:31:52 pi kernel: nvme nvme0: I/O 428 QID 3 timeout, aborting Sep 13 10:31:52 pi kernel: nvme nvme0: I/O 430 QID 3 timeout, aborting Sep 13 10:32:22 pi kernel: nvme nvme0: I/O 336 QID 3 timeout, reset controller Sep 13 10:32:52 pi kernel: nvme nvme0: I/O 22 QID 0 timeout, reset controller Sep 13 10:34:23 pi kernel: nvme nvme0: Device not ready; aborting reset Sep 13 10:34:23 pi kernel: nvme nvme0: Abort status: 0x7 Sep 13 10:34:23 pi kernel: nvme nvme0: Abort status: 0x7 Sep 13 10:34:23 pi kernel: nvme nvme0: Abort status: 0x7 Sep 13 10:34:23 pi kernel: nvme nvme0: Abort status: 0x7 Sep 13 10:34:23 pi kernel: nvme nvme0: Abort status: 0x7 Sep 13 10:35:23 pi kernel: nvme nvme0: Device not ready; aborting reset Sep 13 10:35:23 pi kernel: nvme nvme0: Removing after probe failure status: -19 Sep 13 10:36:24 pi kernel: nvme nvme0: Device not ready; aborting reset Sep 13 10:36:24 pi kernel: XFS (nvme0n1p1): metadata I/O error in "xlog_iodone" at daddr 0x1dd59842 len 64 error 5 Sep 13 10:36:24 pi kernel: print_req_error: I/O error, dev nvme0n1, sector 612895568 Sep 13 10:36:24 pi kernel: XFS (nvme0n1p1): writeback error on sector 170104 Sep 13 10:36:24 pi kernel: print_req_error: I/O error, dev nvme0n1, sector 612895056 Sep 13 10:36:24 pi kernel: print_req_error: I/O error, dev nvme0n1, sector 612894544 Sep 13 10:36:24 pi kernel: print_req_error: I/O error, dev nvme0n1, sector 612893520 Sep 13 10:36:24 pi kernel: print_req_error: I/O error, dev nvme0n1, sector 612893008 Sep 13 10:36:24 pi kernel: print_req_error: I/O error, dev nvme0n1, sector 612892496 Sep 13 10:36:24 pi kernel: print_req_error: I/O error, dev nvme0n1, sector 612891984 Sep 13 10:36:24 pi kernel: print_req_error: I/O error, dev nvme0n1, sector 612891472 Sep 13 10:36:24 pi kernel: print_req_error: I/O error, dev nvme0n1, sector 612889424 Sep 13 10:36:24 pi kernel: print_req_error: I/O error, dev nvme0n1, sector 612888912 Sep 13 10:36:24 pi kernel: XFS (nvme0n1p1): writeback error on sector 399096 Sep 13 10:36:24 pi kernel: XFS (nvme0n1p1): writeback error on sector 557851984 Sep 13 10:36:24 pi kernel: XFS (nvme0n1p1): writeback error on sector 543126416 Sep 13 10:36:24 pi kernel: XFS (nvme0n1p1): writeback error on sector 400728 Sep 13 10:36:24 pi kernel: XFS (nvme0n1p1): writeback error on sector 596713920 Sep 13 10:36:24 pi kernel: XFS (nvme0n1p1): writeback error on sector 596713912 Sep 13 10:36:24 pi kernel: XFS (nvme0n1p1): writeback error on sector 401544 Sep 13 10:36:24 pi kernel: XFS (nvme0n1p1): writeback error on sector 596713864 Sep 13 10:36:24 pi kernel: XFS (nvme0n1p1): writeback error on sector 695560 Sep 13 10:36:24 pi kernel: XFS (nvme0n1p1): metadata I/O error in "xfs_buf_iodone_callback_error" at daddr 0x2483d170 len 8 error 5 Sep 13 10:36:24 pi kernel: XFS (nvme0n1p1): xfs_do_force_shutdown(0x2) called from line 1271 of file fs/xfs/xfs_log.c. Return address = 000000004d7dcc22 Sep 13 10:36:24 pi kernel: XFS (nvme0n1p1): Log I/O Error Detected. Shutting down filesystem Sep 13 10:36:24 pi kernel: XFS (nvme0n1p1): Failing async write on buffer block 0x1e50b5f0. Retrying async write. Sep 13 10:36:24 pi kernel: XFS (nvme0n1p1): Please umount the filesystem and rectify the problem(s) Sep 13 10:36:24 pi kernel: XFS (nvme0n1p1): metadata I/O error in "xlog_iodone" at daddr 0x1dd597ba len 64 error 5 Sep 13 10:36:24 pi kernel: XFS (nvme0n1p1): Failing async write on buffer block 0x1df9e870. Retrying async write. Sep 13 10:36:24 pi kernel: XFS (nvme0n1p1): xfs_do_force_shutdown(0x2) called from line 1271 of file fs/xfs/xfs_log.c. Return address = 000000004d7dcc22 Sep 13 10:36:24 pi kernel: XFS (nvme0n1p1): Failing async write on buffer block 0x1df9e878. Retrying async write. Sep 13 10:36:24 pi kernel: XFS (nvme0n1p1): Failing async write on buffer block 0x21101ba0. Retrying async write. Sep 13 10:36:24 pi kernel: XFS (nvme0n1p1): Failing async write on buffer block 0x1ee265d8. Retrying async write. Sep 13 10:36:24 pi kernel: XFS (nvme0n1p1): Failing async write on buffer block 0x1de0afb8. Retrying async write. Sep 13 10:36:24 pi kernel: XFS (nvme0n1p1): metadata I/O error in "xlog_iodone" at daddr 0x1dd597fa len 64 error 5 Sep 13 10:36:24 pi kernel: XFS (nvme0n1p1): Failing async write on buffer block 0x1de0b338. Retrying async write. Sep 13 10:36:24 pi kernel: XFS (nvme0n1p1): Failing async write on buffer block 0x20a47e88. Retrying async write. Sep 13 10:36:24 pi kernel: XFS (nvme0n1p1): Failing async write on buffer block 0x1df157f0. Retrying async write. Sep 13 10:36:24 pi kernel: XFS (nvme0n1p1): Failing async write on buffer block 0x1df14530. Retrying async write. Sep 13 10:36:24 pi kernel: XFS (nvme0n1p1): xfs_do_force_shutdown(0x2) called from line 1271 of file fs/xfs/xfs_log.c. Return address = 000000004d7dcc22 Sep 13 10:36:24 pi kernel: XFS (nvme0n1p1): metadata I/O error in "xlog_iodone" at daddr 0x1dd5983a len 64 error 5 Sep 13 10:36:24 pi kernel: XFS (nvme0n1p1): xfs_do_force_shutdown(0x2) called from line 1271 of file fs/xfs/xfs_log.c. Return address = 000000004d7dcc22 Sep 13 10:36:24 pi kernel: XFS (nvme0n1p1): metadata I/O error in "xlog_iodone" at daddr 0x1dd59840 len 64 error 5 Sep 13 10:36:24 pi kernel: XFS (nvme0n1p1): xfs_do_force_shutdown(0x2) called from line 1271 of file fs/xfs/xfs_log.c. Return address = 000000004d7dcc22 Sep 13 10:36:24 pi kernel: nvme nvme0: failed to set APST feature (-19) Sep 13 10:37:28 pi kernel: qemu-system-x86[32027]: segfault at 4 ip 00005635a59e04d7 sp 0000150abbafee98 error 6 in qemu-system-x86_64[5635a57b1000+4cc000] Sep 13 10:37:28 pi kernel: Code: 48 89 c3 e8 3b f3 ff ff 48 83 c4 08 48 89 d8 5b 5d c3 90 c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 8b 87 98 09 00 00 <01> 70 04 c3 0f 1f 44 00 00 c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f Sep 13 10:37:28 pi kernel: br0: port 4(vnet4) entered disabled state Sep 13 10:37:28 pi kernel: device vnet4 left promiscuous mode Sep 13 10:37:28 pi kernel: br0: port 4(vnet4) entered disabled state Quote Link to comment
JorgeB Posted September 13, 2019 Share Posted September 13, 2019 It's a hardware problem, either board (assuming it's not on a PCIe adapter) or the NVMe device. Quote Link to comment
dimes007 Posted September 13, 2019 Author Share Posted September 13, 2019 17 minutes ago, johnnie.black said: It's a hardware problem, either board (assuming it's not on a PCIe adapter) or the NVMe device. Thanks. Board is a Gigabyte Z370xp SLI. It's been a fine board. Ok. I ordered a 970 EVO. It's on the way. Fingers crossed. Thanks, --dimes Quote Link to comment
JorgeB Posted September 13, 2019 Share Posted September 13, 2019 20 minutes ago, dimes007 said: I ordered a 970 EVO. That's a good option, they are known to work great with Unraid. Quote Link to comment
dimes007 Posted November 17, 2019 Author Share Posted November 17, 2019 So with the 970 EVO I'm having the same issues I think. First stopped after 22 days. Rebooted. Now again after ~36 days. This time rebooted and it didn't even come back online. Maybe I didn't cut power long enough for everything to reset. Anybody else having issues in general with NVME in unRaid or is just me? 8700k, Gigabyte Z370xp SLI. Quote Link to comment
JorgeB Posted November 18, 2019 Share Posted November 18, 2019 14 hours ago, dimes007 said: Anybody else having issues in general with NVME in unRaid or is just me? Many users have been using NVMe devices for years without issues, including me, if it happens with different devices it's likely a board issue. Quote Link to comment
Recommended Posts
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.