August 11, 2025Aug 11 So recently I had some issues with a data drive that I had some questions about here...But I recently saw there were read errors on one of my parity drive, I have 2 parity drives, about 2300 errors. Since I didn't have time to address it over the weekend, outside of a extended SMART test, attached in this post, I'm here now to try and fix things. All the sources I've read say to simply replace the parity drive. As if there are any errors on the drive, it's in decline and isn't worth keeping. This parity drive is also one of my newest ones and it also passed the extended SMART test. Everything also stopped a read-check at 2.7%, it's now paused. I'm not sure what the best course of action is, other than replacing drives. warlock-diagnostics-20250811-1711.zip parity disk warlock-smart-20250811-1709.zip data drive warlock-smart-20250811-1742.zip
August 12, 2025Aug 12 Community Expert It's not logged as a disk problem, and SMART looks OK, replace cables and try again.
August 20, 2025Aug 20 Author It's been a while. I finally got a new cable in. I've replace the cable for the parity drive because it started with the parity drive and then there were errors on my new 12TB data drive, so I'm hoping the parity drive errors had had the errors which then caused errors in my data drive. But anyway, I've replace the cables for my parity drive, now what? I errors are still there when I started the array, how can I clear them and "restart" so to speak.
August 21, 2025Aug 21 Author warlock-diagnostics-20250821-0102.zip warlock-diagnostics-20250821-0102.zip Edited August 21, 2025Aug 21 by Herdie27
August 21, 2025Aug 21 Community Expert Still looks like a power/connection issue, any power splitters in use?
August 22, 2025Aug 22 Author No power splitters. I have two power supplies each with what I would say are pretty old power cables hooked up to a UPS. Do you think the power cables themselves could be the problem?The errors aren't listened anymore and the drives are still disabled Edited August 23, 2025Aug 23 by Herdie27
August 23, 2025Aug 23 Community Expert 11 hours ago, Herdie27 said:Do you think the power cables themselves could be the problem?Could be, it's likely bad power or bad SATA cables.
August 25, 2025Aug 25 Author So how can I get my Parity disk and Data Disk back up? Everything I've read says the data disk needs to rebuild on itself and I can't find anything on getting my parity disk re-enabled.Additionally, I decided to do another SMART test on each disk and it's been a day and a half and they're still not done testing. They both say 20% complete. I also attached the current diagnostics. warlock-diagnostics-20250823-1555.zip Edited August 25, 2025Aug 25 by Herdie27
August 25, 2025Aug 25 Community Expert The procedure to re-enable parity is the same as for a data drive:https://docs.unraid.net/unraid-os/manual/storage-management#rebuilding-a-drive-onto-itself
August 25, 2025Aug 25 Author Since I have 2 parity drives my data should be just fine and re-enabling both drives at the same time should be okay? Or should I do one at the time?
February 20Feb 20 On 8/21/2025 at 10:01 AM, JorgeB said:Still looks like a power/connection issue, any power splitters in use?In order to learn, what makes you say that?Which log / error message please?
February 20Feb 20 Community Expert 1 hour ago, AlanC said:Which log / error message please?The errors in the syslog are not logged as a disk problem:Aug 4 05:53:59 Warlock kernel: mpt3sas_cm0: log_info(0x31110d01): originator(PL), code(0x11), sub_code(0x0d01)Aug 4 05:54:00 Warlock kernel: sd 3:0:2:0: [sdd] tag#9917 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=4sAug 4 05:54:00 Warlock kernel: sd 3:0:2:0: [sdd] tag#9567 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0sAug 4 05:54:00 Warlock kernel: sd 3:0:2:0: [sdd] tag#9917 Sense Key : 0x2 [current] Aug 4 05:54:00 Warlock kernel: sd 3:0:2:0: [sdd] tag#9917 ASC=0x4 ASCQ=0x0 Aug 4 05:54:00 Warlock kernel: sd 3:0:2:0: [sdd] tag#9917 CDB: opcode=0x88 88 00 00 00 00 01 78 59 76 58 00 00 04 00 00 00Aug 4 05:54:00 Warlock kernel: sd 3:0:2:0: [sdd] tag#9567 Sense Key : 0x2 [current] Aug 4 05:54:00 Warlock kernel: I/O error, dev sdd, sector 6314096216 op 0x0:(READ) flags 0x0 phys_seg 128 prio class 0Aug 4 05:54:00 Warlock kernel: md: disk29 read error, sector=6314096152
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.