Syslog disk errors during preclear

     Originally, three used Seagate Exos x14 14tb HDDs were purchased for my first server build. All three were precleared successfully. Two were added to the array and one became parity. Extended smart tests were run for all three and given a healthy status. Data began being added to cache drives, before being scheduled to move to the array. As soon as data started being written to the actual array, the parity disk would enter a disabled state after receiving read/write notification errors. I stopped the array, removed the disk, started the array, stopped, and readded the drive. It rebuilt parity and failed again after being written to. After reading into the possible causes of this, I switched the parity to another cable, it began rebuilding parity, but again as soon as data started being written to it, it disabled. 

     Recently I bought two of the same drives. One would be replacing my disabled parity and the other would be added to the array. They both precleared successfully. But this time I noticed multiple instances of this error in the syslog. 

Quote

Jul 18 15:12:20 AethelNas kernel: I/O error, dev sdf, sector 106400768 op 0x0:(READ) flags 0x80700 phys_seg 63 prio class 3

 I also ran extended SMART tests on both drives. The first time, the drive that gave errors in the syslog seemed to abort the test early. It said, "aborted by user command," but it certainly wasn't done intentionally. I read that this could happen if the delayed spin down setting was causing it to stop, but I have this setting disabled and neither disk has been added to the array yet to be affected by that setting. I restarted the extended test for the drive that aborted. By the end both were given healthy statuses, but someone can probably interpret this information better than I can. All of the cables are just a few months old and should not be causing issues, but I plan to get backups if I need to rerun anything. Although, I'm not sure I can even replicate the errors as they didn't show in anything aside from the syslog during the preclear. 

     Unfortunately, I do not believe I have a complete .zip that goes back as far as the original three drives. It was all brand new to me and I didn't realize syslog restarted when powering down. I do have the diagnostics for the events I described with the two new disks. I do not understand why a disk would give errors in the syslog that you specifically have to look for, but not show anything of the sort in the preclear logs or SMART info. I downloaded the preclear logs and put them into the diagnostics folder as I don't think they are typically included but I could be wrong. They are in the folder labeled preclears. I need help figuring out if this is a faulty drive that needs to be sent back for a new one, within a fairly short warranty period of 30 days. 

Thanks for the time and help.

aethelnas-diagnostics-20230723-1106.zip

Edited July 23, 20232 yr by aethelnas