March 27, 20224 yr Back story - had some renovations done over a few days and server was offline for most of it. Once renovations were completed I took my server outside and blew it out to clean it and set it all back up. Been running for a day or two no issues. Woke up this morning with read errors on one disk and no another disk has gone offline. I am thinking cables but I need to check with you guys first before powering down and reseating cables. Edited March 28, 20224 yr by SavageAUS
March 27, 20224 yr Author Ran short tests on both drives, completed successfully before posting diags.
March 27, 20224 yr Community Expert Can't open your diagnostics, try again. Attach to your NEXT post in this thread
March 28, 20224 yr Author 10 hours ago, trurl said: Can't open your diagnostics, try again. Attach to your NEXT post in this thread How’s this one? Edited March 28, 20224 yr by SavageAUS
March 28, 20224 yr Community Expert No that one doesn't work either. How are you creating this? The diagnostics is downloaded as a single zip file with no need to change it in any way.
March 28, 20224 yr Author I’m using wireguard on my iPhone to download the zip. I am not modifying it in anyway. I’ll be home soonish and I’ll upload it again. Here’s a new one for now. Edited March 28, 20224 yr by SavageAUS
March 28, 20224 yr it's an html, and it's content is the unraid login page Last one is ok Edited March 28, 20224 yr by ghost82
March 28, 20224 yr sdh drive seems to have issues: Mar 28 06:52:02 BlackBox kernel: mpt2sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000) ### [PREVIOUS LINE REPEATED 10 TIMES] ### Mar 28 06:52:02 BlackBox kernel: sd 1:0:4:0: [sdh] tag#3285 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=7s Mar 28 06:52:02 BlackBox kernel: sd 1:0:4:0: [sdh] tag#3285 Sense Key : 0x5 [current] Mar 28 06:52:02 BlackBox kernel: sd 1:0:4:0: [sdh] tag#3285 ASC=0x21 ASCQ=0x0 Mar 28 06:52:02 BlackBox kernel: sd 1:0:4:0: [sdh] tag#3285 CDB: opcode=0x8a 8a 00 00 00 00 00 00 00 00 c0 00 00 00 40 00 00 Mar 28 06:52:02 BlackBox kernel: blk_update_request: critical target error, dev sdh, sector 192 op 0x1:(WRITE) flags 0x0 phys_seg 8 prio class 0 Mar 28 06:52:02 BlackBox kernel: md: disk3 write error, sector=128 Mar 28 06:52:02 BlackBox kernel: md: disk3 write error, sector=136 Mar 28 06:52:02 BlackBox kernel: md: disk3 write error, sector=144 Mar 28 06:52:02 BlackBox kernel: md: disk3 write error, sector=152 Mar 28 06:52:02 BlackBox kernel: md: disk3 write error, sector=160 Mar 28 06:52:02 BlackBox kernel: md: disk3 write error, sector=168 Mar 28 06:52:02 BlackBox kernel: md: disk3 write error, sector=176 Mar 28 06:52:02 BlackBox kernel: md: disk3 write error, sector=184 This can be cable, but also the disk itself, or the controller.. Reseating the cable is the first thing to do. Edited March 28, 20224 yr by ghost82
March 28, 20224 yr Author Reseated all cables, power sata and mini sas. Nothing appeared loose. Powered back up, stopped the array, removed the errored disk, started the array, stopped the array, added the errored disk back in and started the array. Now i am waiting for the parity sync / rebuild to complete so we will see what happens when / if it happens.
March 28, 20224 yr Community Expert If it fails again you should run an extended SMART test on that disk, since the errors are logged as a disk problem.
March 28, 20224 yr Author 2 hours to go and no more errors. Array is back online and healthy. Edited March 29, 20224 yr by SavageAUS
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.