Praxinator

Thanks for the tips, come to think of it I've had this thing for the better part of a year now running almost 24/7 and did have what seemed like a crash before, everything was still powered but could only access iDRAC and not OS until I cold rebooted. I guess I'll try a memtest then. It's in an older 12th gen Dell Poweredge with redundant PSUs, so I could easily swap main and spare to test if memtest doesn't find anything.

No, the implication here being I'm trying to avoid memtest unless no one can say what this "skip count bs" returning unexpected values actually means

================================================================== 1.22 = unRAID server Pre-Clear disk /dev/sde = cycle 1 of 1, partition start on sector 64 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 32C, Elapsed Time: 124:18:30 ========================================================================1.22 == WDCWD180EDGZ-11B2DA0 3LG8BP8U == Disk /dev/sde has NOT been precleared successfully == skip=6615600 count=200 bs=1000448 returned 26041 instead of 00000 skip=11330200 count=200 bs=1000 448 returned 43463 instead of 00000 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sde /tmp/smart_finish_sde ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 51 54 0 ok 32 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. Is my drive screwed? Everything seems to work except post-read, and SMART reads fine. Everything ran fine up until post-read verification, which failed twice with the plugin. So to troubleshoot I ran post-read verification with the docker and then a full pre-read, clear, post-read cycle; both times getting the message above. I have read that sometimes post-read failures can be caused by bad memory but I'm hoping someone can explain what this "skip count bs" returning unexpected values might be and if that's indicative of a bad drive, because I really want to avoid memtest on 96GB if possible...