April 28Apr 28 unraid-diagnostics-20260428-1924.zipHi, this morning my server crashed, and now my zfs pool says Unmountable: wrong or no file systemI have rebooted to see if the drive was working but its seems the problem is deeperzpool doens't see any poolI'll stop here before making damagesSend help ahah
April 28Apr 28 Apr 28 16:16:15 unRAID kernel: nvme nvme0: I/O tag 448 (81c0) opcode 0x2 (I/O Cmd) QID 5 timeout, aborting req_op:READ(0) size:28672Apr 28 16:16:15 unRAID kernel: nvme nvme0: I/O tag 320 (7140) opcode 0x2 (I/O Cmd) QID 7 timeout, aborting req_op:READ(0) size:131072Apr 28 16:16:15 unRAID kernel: nvme nvme0: I/O tag 448 (81c0) opcode 0x2 (I/O Cmd) QID 15 timeout, aborting req_op:READ(0) size:4096Apr 28 16:16:15 unRAID kernel: nvme nvme0: I/O tag 0 (5000) opcode 0x2 (I/O Cmd) QID 16 timeout, aborting req_op:READ(0) size:4096Apr 28 16:16:45 unRAID kernel: nvme nvme0: I/O tag 448 (81c0) opcode 0x2 (I/O Cmd) QID 5 timeout, reset controllerApr 28 16:19:57 unRAID kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1Apr 28 16:22:05 unRAID kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1Apr 28 16:22:07 unRAID kernel: nvme 0000:01:00.0: not ready 1023ms after FLR; waitingApr 28 16:22:08 unRAID kernel: nvme 0000:01:00.0: not ready 2047ms after FLR; waitingApr 28 16:22:10 unRAID kernel: nvme 0000:01:00.0: not ready 4095ms after FLR; waitingApr 28 16:22:14 unRAID kernel: nvme 0000:01:00.0: not ready 8191ms after FLR; waitingApr 28 16:22:23 unRAID kernel: nvme 0000:01:00.0: not ready 16383ms after FLR; waitingApr 28 16:22:40 unRAID kernel: nvme 0000:01:00.0: not ready 32767ms after FLR; waitingApr 28 16:23:13 unRAID kernel: nvme 0000:01:00.0: not ready 65535ms after FLR; giving upApr 28 16:23:13 unRAID kernel: nvme nvme0: Disabling device after reset failure: -25There's a problem with the NVMe device, make sure it's well seated, or try a different M.2 slot. If the same post is new, do diagnostics before the array starts, while it's hopefully still online.
April 28Apr 28 Author 52 minutes ago, JorgeB said:Apr 28 16:16:15 unRAID kernel: nvme nvme0: I/O tag 448 (81c0) opcode 0x2 (I/O Cmd) QID 5 timeout, aborting req_op:READ(0) size:28672Apr 28 16:16:15 unRAID kernel: nvme nvme0: I/O tag 320 (7140) opcode 0x2 (I/O Cmd) QID 7 timeout, aborting req_op:READ(0) size:131072Apr 28 16:16:15 unRAID kernel: nvme nvme0: I/O tag 448 (81c0) opcode 0x2 (I/O Cmd) QID 15 timeout, aborting req_op:READ(0) size:4096Apr 28 16:16:15 unRAID kernel: nvme nvme0: I/O tag 0 (5000) opcode 0x2 (I/O Cmd) QID 16 timeout, aborting req_op:READ(0) size:4096Apr 28 16:16:45 unRAID kernel: nvme nvme0: I/O tag 448 (81c0) opcode 0x2 (I/O Cmd) QID 5 timeout, reset controllerApr 28 16:19:57 unRAID kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1Apr 28 16:22:05 unRAID kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1Apr 28 16:22:07 unRAID kernel: nvme 0000:01:00.0: not ready 1023ms after FLR; waitingApr 28 16:22:08 unRAID kernel: nvme 0000:01:00.0: not ready 2047ms after FLR; waitingApr 28 16:22:10 unRAID kernel: nvme 0000:01:00.0: not ready 4095ms after FLR; waitingApr 28 16:22:14 unRAID kernel: nvme 0000:01:00.0: not ready 8191ms after FLR; waitingApr 28 16:22:23 unRAID kernel: nvme 0000:01:00.0: not ready 16383ms after FLR; waitingApr 28 16:22:40 unRAID kernel: nvme 0000:01:00.0: not ready 32767ms after FLR; waitingApr 28 16:23:13 unRAID kernel: nvme 0000:01:00.0: not ready 65535ms after FLR; giving upApr 28 16:23:13 unRAID kernel: nvme nvme0: Disabling device after reset failure: -25There's a problem with the NVMe device, make sure it's well seated, or try a different M.2 slot. If the same post is new, do diagnostics before the array starts, while it's hopefully still online.Reseated and rebooted, now it's online, array autostart disabled and stoppedunraid-diagnostics-20260428-2053.zip
April 28Apr 28 Author Tried to get the array online, no success, new diagnosticunraid-diagnostics-20260428-2118.zip
April 29Apr 29 The device dropped again as soon as Unraid tried to import the pool, it may be failing.
April 29Apr 29 Author 40 minutes ago, JorgeB said:The device dropped again as soon as Unraid tried to import the pool, it may be failing.Is there a way to get the file even in read only?
April 29Apr 29 Author 9 hours ago, JorgeB said:You can try, reboot and then try zpool import -o readonly=on storageIt worked, now I'm restoring files, thank you a lot
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.