February 17, 20242 yr Background: I had two 6tb parity drives and one started to show an issue with a red thumbdown on Dashboard (no errors shown on Main screen). Decided it's a good reason to swap to 8tb parity, so swapped one parity disk at a time to 8tb, all went well, both parity are now 8tb. Leaving me with two 6tb drives on the bench. All drives involved are WD Reds. The thumbdown drive kept throwing smart errors, so that's going in the bin, however the other drive passed smart test, so went to replace one of my 3tb data drives (it also had a red thumbdown). It rebuilt for an hour (out of about 22hrs expected) and then got disabled. Trying to pull fresh smart report from unraid it says "exiting. To continue, add one or more '-T permissive' options." From the Disk Log Info it's got: Feb 14 22:05:00 NAS kernel: sd 9:0:6:0: [sds] tag#847 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=51s Feb 14 22:05:00 NAS kernel: sd 9:0:6:0: [sds] tag#847 CDB: opcode=0x8a 8a 00 00 00 00 00 03 55 2e 40 00 00 02 00 00 00 Feb 14 22:05:00 NAS kernel: I/O error, dev sds, sector 55914048 op 0x1:(WRITE) flags 0x0 phys_seg 64 prio class 0 Thanks in advance! old parity disk throwing errors.txt
February 17, 20242 yr Community Expert Solution Looks like the disk dropped offline, check/replace cables for that disk and post new diags after array start.
March 2, 20242 yr Author Apologies for the delay, took some time before there was an appropriate time to take the server down. The drive is in a caddy on a backplane, but I still took down the server, re-seated the drive in the caddy, re-seated the caddy in the case and kicked it all off again. It's rebuilding now. Will update how it goes.
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.