October 14, 2025Oct 14 Community Expert Oct 14 10:09:22 JAYnJAS kernel: sd 3:0:0:0: [sdd] tag#15 Sense Key : 0x5 [current] Oct 14 10:09:22 JAYnJAS kernel: sd 3:0:0:0: [sdd] tag#15 ASC=0x21 ASCQ=0x4 Oct 14 10:09:22 JAYnJAS kernel: sd 3:0:0:0: [sdd] tag#15 CDB: opcode=0x88 88 00 00 00 00 01 80 16 70 d8 00 00 01 00 00 00 Oct 14 10:09:22 JAYnJAS kernel: I/O error, dev sdd, sector 6443921624 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0 Oct 14 10:09:22 JAYnJAS kernel: md: disk0 read error, sector=6443921560 Oct 14 10:09:22 JAYnJAS kernel: md: disk0 read error, sector=6443921568 Oct 14 10:09:22 JAYnJAS kernel: md: disk0 read error, sector=6443921576 Oct 14 10:09:22 JAYnJAS kernel: md: disk0 read error, sector=6443921584 Oct 14 10:09:22 JAYnJAS kernel: md: disk0 read error, sector=6443921592Errors followed the disk, which basically confirms it's failing. That means it cannot be used to rebuild disk2, SMART for disk2 also shows some issues, but could be OK for now, I would recommend doing a new config without parity and seeing if both disks 1 and 2 mount (note that if there was any data written to disk2 after it got disabled, that data will be lost, but not much you can do about it anyway).
October 14, 2025Oct 14 Author To do a new config without parity, will I just remove it in the webUI or would I have to remove the hdd from the server phsyically?
October 14, 2025Oct 14 Community Expert Do a new config (Tools - New Config - Keep all - Apply), then back on main unassign parity, disks 1 and 2 should remain assigned, and start the array.
October 14, 2025Oct 14 Author Without the parity this is the error I am getting on the array. I also included the new diags test. jaynjas-diagnostics-20251014-1154.zip
October 15, 2025Oct 15 Community Expert Check filesystem on disk1, disk2 also has issue similçar to parity:Oct 14 11:54:35 JAYnJAS kernel: sd 6:0:0:0: [sde] tag#17 CDB: opcode=0x8a 8a 00 00 00 00 01 80 0a 37 50 00 00 01 00 00 00Oct 14 11:54:35 JAYnJAS kernel: I/O error, dev sde, sector 6443120464 op 0x1:(WRITE) flags 0x800 phys_seg 32 prio class 0Oct 14 11:54:35 JAYnJAS kernel: md: disk2 write error, sector=6443120400Oct 14 11:54:35 JAYnJAS kernel: md: disk2 write error, sector=6443120408Oct 14 11:54:35 JAYnJAS kernel: md: disk2 write error, sector=6443120416Oct 14 11:54:35 JAYnJAS kernel: md: disk2 write error, sector=6443120424If these are the original cables, it's worth replacing them, but could be failing similarly to parity.
October 15, 2025Oct 15 Author They are new cables that were replaced. Is it still possible to recover the data from the failed disks?
October 15, 2025Oct 15 Community Expert Parity won't have any data, but you can try recovering disk2 with ddrescue:https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-525075
October 15, 2025Oct 15 Community Expert 16 hours ago, JorgeB said:Check filesystem on disk1, disk2Did you do this? What were the results?
October 17, 2025Oct 17 Author I was able to fix disk1 and mount it. However, disk2 is now showing that the disk is not encrypted and needs to be encrypted.
October 17, 2025Oct 17 Community Expert Disk2 appears to be in a really bad state, but may still be worth trying to clone it with ddrescue, then try to mount the clone
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.