April 23Apr 23 Unraid just took a disk offline due to 58 "Errors", but checking SMART all I see is Raw_Read_Error_Rate, but it hasn't even hit the threshold at its worst:ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-- 100 064 044 - 0/1183016I've attached my diagnostics, is there any indication of what's actually erroring, and if the disk is completely borked and needs replacing?Thanks,Josh unraid-diagnostics-20260424-0047.zip
April 24Apr 24 From your syslog, your disk 11 is having READ and WRITE errors. Maybe it's your MPT3 SAS controller or cables?Not sure what more to look at/for, been ages since I looked at this sort of stuff, so out of practice. Hoping someone else can pickup the ball and continue the task.The SMART report seems to be when you were in process of performing an Extended Offline SMART test?SMART Extended Self-test Log Version: 1 (1 sectors)Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error# 1 Extended offline Self-test routine in progress 90% 11299 -Drive Identification:Apr 17 12:10:25 Unraid emhttpd: online: ST16000NM000J-2TW103_ZR553342 (sdn) 512 31251759104Syslog error segment:Apr 24 00:24:14 Unraid kernel: mpt3sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00)Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1543 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0sApr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1543 Sense Key : 0x2 [current] Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1543 ASC=0x4 ASCQ=0x0 Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1543 CDB: opcode=0x88 88 00 00 00 00 07 0d 30 99 f0 00 00 00 20 00 00Apr 24 00:24:14 Unraid kernel: I/O error, dev sdn, sector 30286060016 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 0Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=30286059952Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=30286059960Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=30286059968Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=30286059976Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1544 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=4sApr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1544 Sense Key : 0x2 [current] Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1544 ASC=0x4 ASCQ=0x0 Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1544 CDB: opcode=0x88 88 00 00 00 00 01 07 65 79 68 00 00 00 80 00 00Apr 24 00:24:14 Unraid kernel: I/O error, dev sdn, sector 4419058024 op 0x0:(READ) flags 0x0 phys_seg 16 prio class 0Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419057960Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419057968Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419057976Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419057984Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419057992Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419058000Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419058008Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419058016Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419058024Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419058032Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419058040Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419058048Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419058056Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419058064Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419058072Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419058080Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1559 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0sApr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1559 Sense Key : 0x2 [current] Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1559 ASC=0x4 ASCQ=0x0 Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1559 CDB: opcode=0x8a 8a 00 00 00 00 01 07 65 79 68 00 00 00 28 00 00Apr 24 00:24:14 Unraid kernel: I/O error, dev sdn, sector 4419058024 op 0x1:(WRITE) flags 0x0 phys_seg 5 prio class 0Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419057960Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419057968Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419057976Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419057984Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419057992Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1560 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0sApr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1560 Sense Key : 0x2 [current] Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1560 ASC=0x4 ASCQ=0x0 Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1560 CDB: opcode=0x8a 8a 00 00 00 00 07 0d 30 99 f0 00 00 00 20 00 00Apr 24 00:24:14 Unraid kernel: I/O error, dev sdn, sector 30286060016 op 0x1:(WRITE) flags 0x0 phys_seg 4 prio class 0Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=30286059952Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=30286059960Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=30286059968Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=30286059976Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1562 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0sApr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1562 Sense Key : 0x2 [current] Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1562 ASC=0x4 ASCQ=0x0 Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1562 CDB: opcode=0x8a 8a 00 00 00 00 01 07 65 79 90 00 00 00 58 00 00Apr 24 00:24:14 Unraid kernel: I/O error, dev sdn, sector 4419058064 op 0x1:(WRITE) flags 0x0 phys_seg 11 prio class 0Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419058000Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419058008Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419058016Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419058024Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419058032Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419058040Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419058048Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419058056Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419058064Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419058072Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419058080Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1563 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0sApr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1563 Sense Key : 0x2 [current] Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1563 ASC=0x4 ASCQ=0x0 Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1563 CDB: opcode=0x88 88 00 00 00 00 01 07 6b 74 48 00 00 00 28 00 00Apr 24 00:24:14 Unraid kernel: I/O error, dev sdn, sector 4419449928 op 0x0:(READ) flags 0x0 phys_seg 5 prio class 0Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419449864Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419449872Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419449880Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419449888Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419449896Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1567 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0sApr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1567 Sense Key : 0x2 [current] Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1567 ASC=0x4 ASCQ=0x0 Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1567 CDB: opcode=0x88 88 00 00 00 00 01 92 80 99 c8 00 00 00 20 00 00Apr 24 00:24:14 Unraid kernel: I/O error, dev sdn, sector 6752868808 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 0Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=6752868744Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=6752868752Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=6752868760Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=6752868768Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1584 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0sApr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1584 Sense Key : 0x2 [current] Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1584 ASC=0x4 ASCQ=0x0 Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1584 CDB: opcode=0x8a 8a 00 00 00 00 01 07 6b 74 48 00 00 00 28 00 00Apr 24 00:24:14 Unraid kernel: I/O error, dev sdn, sector 4419449928 op 0x1:(WRITE) flags 0x0 phys_seg 5 prio class 0Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419449864Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419449872Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419449880Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419449888Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419449896Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1592 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0sApr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1592 Sense Key : 0x2 [current] Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1592 ASC=0x4 ASCQ=0x0 Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1592 CDB: opcode=0x8a 8a 00 00 00 00 01 92 80 99 c8 00 00 00 20 00 00Apr 24 00:24:14 Unraid kernel: I/O error, dev sdn, sector 6752868808 op 0x1:(WRITE) flags 0x0 phys_seg 4 prio class 0Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=6752868744Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=6752868752Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=6752868760Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=6752868768
April 24Apr 24 Author Hi Brit,Thanks for taking a look.The SMART report seems to be when you were in process of performing an Extended Offline SMART test?I started that after the drive disabled due to errors, and it's been stuck at 10% so I decided to post this instead of waiting potentially foreverI'm unsure how far back the diagnostic logs go - do they imply when the read/write errors started occurring?Thanks,Josh Edited April 24Apr 24 by Proddy Fix quote
April 24Apr 24 The current syslog started on April 17 12:09:05 and ends on April 24 00:48:15.The previous syslog started on April 10 04:40:59 and ends on April 16 08:28:01.The only "read error" or "write error" related to any drives started (and ended) at April 24 00:24:14.
April 24Apr 24 Author Thanks - the server was shutoff and moved about a week ago, so I was wondering if it had started then.What would you suggest as next steps? Power off, check/replug cables, and see if that improves anything?Thanks,Josh
April 24Apr 24 Community Expert 51 minutes ago, Proddy said:Power off, check/replug cables, and see if that improves anything?That would be a start. You will have to rebuild disk11 of course. Emulated disk11 is mounted so should be OK to rebuild on top.
April 24Apr 24 Author 32 minutes ago, trurl said:That would be a start. You will have to rebuild disk11 of course. Emulated disk11 is mounted so should be OK to rebuild on top.I shutdown, reseated everything, powered on, stopped the array, but the disk just says "disabled" - I may be blind but where do I re-enable the disk?Thanks,Josh
April 24Apr 24 Author I checked some other threads and saw I need to rebuild the drive onto itself, but all the links provided were dead links (https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself), and the equivalent link I found pointing to the new docs (https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/array/overview/#rebuilding-a-drive-onto-itself) doesn't seem to have that section either.Thanks,Josh
April 24Apr 24 Community Expert https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array/#re-enabling-a-disabled-disk-rebuilding-onto-itself
April 24Apr 24 Community Expert Probably simpler to search the docs themselves since any forum links may be outdated.
April 24Apr 24 Author 5 minutes ago, trurl said:https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array/#re-enabling-a-disabled-disk-rebuilding-onto-itselfAh thank you, I was looking in the wrong subsection - my mistake.That rebuild is going now. Hopefully all goes well.Thanks,Josh
April 24Apr 24 Community Expert Solution The errors are not logged as a disk problem, so most likely a power/connection issue, in case it happens again.
April 26Apr 26 Author So after reseating and rebuiling, it worked fine for a couple days until I got another error last night - this time from a different disk. I've attached the diagnostics just in case, but presumably this is a connection issue as mentioned.With that in mind, is there a way to test if it's data or power? I'm using a HBA with two Mini SAS -> 4xSATA, so that could explain the different disks erroring without the entire card being dead.Thanks,Josh unraid-diagnostics-20260426-1302.zip
April 26Apr 26 Community Expert How are the drives powered? Any splitters? Ideally no more than 4 drives per PSU cable.
April 26Apr 26 Author 1 minute ago, trurl said:How are the drives powered? Any splitters? Ideally no more than 4 drives per PSU cable.I think one of the cables has 5 drives on it - though it has been that way for over a yearThanksJosh
April 27Apr 27 Community Expert Try using different power cables, no splitters if possible, and if the issue persists, replace the miniSAS cable.
April 27Apr 27 Community Expert 4 hours ago, JorgeB said:Try using different power cablesBut if you have a modular PSU, you must use cables for that specific PSU. There is no standard pinout for modular PSU. Don't fry your drives by using a wrong cable.
April 30Apr 30 Author So I now have:- 3 x 4 HDDs on one cable- 1 x 3 HDDs + 1 SSD + 1 Fan Controller on one cable(17 SATA powered devices total, but I think the SSD and Fan Controller don't draw that much, so putting them on the one with 3 HDDs makes sense to me)I've also replaced the Mini SAS -> 4x SATA cables, because I didn't want to have to get physical access to the server again (it's in an awkward place)Hopefully that's all the issues resolve, thanks for the support everyone Edited April 30Apr 30 by Proddy Missed a word
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.