October 10, 20232 yr Hey all, Relatively new to unraid, previously was using truenas, and after some help diagnosing a few issues I've been experiencing. Have had ongoing issues with a disk that would error, be put into a failed state and prevent unraid from shutting down or spinning down the array. So first question is why would a failed disk in an array completely prevent shutdown or array spin down? I have just replaced that drive which fixed the above issue. But now I have a second disk that has started spitting out errors. At the moment they appear to be udma crc errors. I have previously checked all connections to the disks and have now just reseated all the hotswap bays and moved the erroring disk to another bay to rule out further any hardware issues with the bays themselves. I have taken my array offline for now and I'm running a long SMART test on the errored drive. Waiting to see what that brings back... I just want to get my head around what is actually happening with the disks and the array. It's weird, coming from truenas unraid seems more difficult and harder to understand what is actually going on. For me, truenas just worked and was bullet reliable; whereas unraid I seem to be nervous every time I check on the server in case something else is wrong... Appreciate any help. I will attach the diagnostic file in the first post. Apparently, I can only post 1 message per day??? So will attach the diagnostic file here... z240-diagnostics-20231010-1113.zip Edited October 10, 20232 yr by fames_jranko
October 10, 20232 yr Constant errors on disk3: Oct 9 15:16:55 z240 kernel: sd 1:0:9:0: [sdj] tag#3190 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s Oct 9 15:16:55 z240 kernel: sd 1:0:9:0: [sdj] tag#3190 CDB: opcode=0x88 88 00 00 00 00 00 00 00 10 00 00 00 00 08 00 00 Oct 9 15:16:55 z240 kernel: I/O error, dev sdj, sector 4096 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 Oct 9 15:16:56 z240 kernel: sd 1:0:9:0: Power-on or device reset occurred Oct 9 15:16:56 z240 kernel: mpt2sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000) Looks more like a power/connection issue, replace cables.
October 10, 20232 yr Author Hey thanks for checking that out for me. dev sdj matches the disk I just pulled out and replaced that was originally failing. For reference, current disks are labelled: boot drive - sda array - sdb, sdc, sdd, sde, sdf, sdg, sdh, sdi I might still replace cables just in case though.
October 11, 20232 yr Author The fact that it's sdj makes me think that it's a false positive... Edited October 11, 20232 yr by fames_jranko
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.