Bees?

Ahh ok, that makes sense. Thanks!

I recently moved to a new bigger case so I could fit more drives, and when I inspected the drive logs on the disks I attached, one of them has some logs I'm not familiar with and could not find any info on. Before I put the drives into my array, I want to make sure that everything is OK with the drive, if there was anything I could try to get the logs to not be generated anymore, or if I should just toss it and not risk it. A bit of history on the drive, I used to have 8 10tb drives in the array (1 as parity). I upgraded the parity and 3 more of the drives to 20tb, and this was one of the 10tb drives that was replaced. So, this drive was in the array previously and ran fine for over a year. Now that I have more space in my case, I was hoping to simply add all these 10tb drives that I replaced to the array. Logs in question: Dec 6 19:16:52 Server1 kernel: sd 7:0:2:0: [sdd] 19532873728 512-byte logical blocks: (10.0 TB/9.10 TiB) Dec 6 19:16:52 Server1 kernel: sd 7:0:2:0: [sdd] 4096-byte physical blocks Dec 6 19:16:52 Server1 kernel: sd 7:0:2:0: [sdd] Write Protect is off Dec 6 19:16:52 Server1 kernel: sd 7:0:2:0: [sdd] Mode Sense: 7f 00 10 08 Dec 6 19:16:52 Server1 kernel: sd 7:0:2:0: [sdd] Write cache: enabled, read cache: enabled, supports DPO and FUA Dec 6 19:16:52 Server1 kernel: sd 7:0:2:0: [sdd] Attached SCSI disk Dec 6 19:17:07 Server1 wsdd2[1387]: starting. Dec 6 19:17:33 Server1 emhttpd: WDC_WD101EFBX-68B0AN0_VCJW45BP (sdd) 512 19532873728 Dec 6 19:17:34 Server1 emhttpd: read SMART /dev/sdd Dec 6 19:17:35 Server1 wsdd2[1387]: 'Terminated' signal received. Dec 6 19:17:35 Server1 wsdd2[1387]: terminating. Dec 6 19:17:37 Server1 root: /usr/sbin/wsdd2 -d Dec 6 19:17:37 Server1 wsdd2[9169]: starting. Dec 6 19:24:00 Server1 wsdd2[9169]: 'Terminated' signal received. Dec 6 19:24:00 Server1 wsdd2[9169]: terminating. Dec 6 19:24:03 Server1 root: /usr/sbin/wsdd2 -d Dec 6 19:24:03 Server1 wsdd2[19703]: starting. I'm specifically concerned with the wsdd2 Terminated signal received type messages. I'm currently running a pre-clear on the drive, I guess for no other reason than to stress test it to see if whatever is generating these logs would make the pre-clear fail, but it's successfully done the pre-clear and is going through the post-read now. I also tried changing the power cable that went to the drive, as well as the sata cable, and it's still generating these logs. There are also 4 other of the exact same model drives that are attached now that do not show these logs, nor do any of the drives in the array. I don't see any SMART errors, but I'm also running an extended self-test now to double check everything (I attached the current SMART report and will attach an updated one once the extended self-test is finished). Long story short, does anyone know what these logs mean? Are they even a problem? If so, can I try something I haven't already to fix the issue? Or should I just take the loss and keep the drive out of the array? WDC_WD101EFBX-20231207-1257.txt

For what it's worth, I was having this issue as well and simply disabling host access to custom networks seems to have resolved it for me. No vlan changes or anything else. Couldn't keep it running running for longer than a day or two, and now it's been running for about a week and a half without an issue.