walchst

@JorgeB you were bang on! Upon further inspection the power cable connecting both drives was touching the side of the case and had some white corrosion on it; as did the case where it was resting against. I replaced the cable and both drives have been solid since. Thanks for your help!

Hi Unraiders, Hoping you can assist in pinpointing the issue I've encountered in the last couple of days. During a scheduled parity check it failed and the parity disk was subsequently disabled. I noticed the following in the syslog: Oct 23 19:51:01 UNRAID root: Fix Common Problems: Error: parity (WDC_WD140EFFX-68VBXN0_9RJ9XS8C) is disabled Oct 23 19:51:20 UNRAID emhttpd: error: hotplug_devices, 1706: No such file or directory (2): tagged device WDC_WD140EFFX-68VBXN0_9RJ9XS8C was (sdc) is now (sde) Oct 23 19:51:20 UNRAID emhttpd: read SMART /dev/sde Oct 23 19:51:20 UNRAID kernel: emhttpd[5557]: segfault at 67c ip 0000557a41da175f sp 00007fff5d4a8c90 error 4 in emhttpd[557a41d8c000+24000] likely on CPU 0 (core 0, socket 0) I powered off and reseated both drives (only have the two WD Reds), ran a few short SMART tests and after nothing came back re-added the disk back into the mix and successfully rebuilt the parity over the following day. Upon completion of that process I decided to stop the array and do an extended check on both disks as I heard an odd sound from the box and in doing so the data disk went missing. I decided to run an extended test on the parity disk, so disabled spin down and started the process but after 10% that also dropped off. I grabbed the diagnostics before a reboot (attached). Post reboot both drives were once again listed but oddly the array utilisation was reporting 100% whereas it was only 71% prior. I attempted to run the extended SMART self-test on both drives but after doing so both went missing after 10% progress. As far as the source of the issue, I'm leaning more towards a cable/board issue as opposed to disk but I'm wondering if anyone can look into the logs to determine the issue. I'd be surprised if both disks failed simultaneously though that said they were purchased/installed at the same time. Thanks for your help! unraid-diagnostics-20231025-0808.zip

Any trick to get this working? I've passed it through to VMs but nothing registers when I use the usb slots.

Doesn't look like any of those 3.0 controllers are about anymore, it's superseded by this one. Any recommendations on what to use instead? This is the 2nd card I've tried and would really love to be third time lucky.

Tag me in on this one - I'm having the same problem.

Hi all, I'm an Unraid noob (6.8.1) but am loving the change and soaking up as much as I can so thank you for all the info! Anyhoo, I'm having this exact issue with my Unifi Controller docker; losing the defined IP address after server restart. Its the only one configured to use BR0, the rest being bridge/host. In my situation the setting is lost only upon server restart, however it resolves itself if I simply stop/start the docker. EDIT: Only after I hardcoated my IP on the Unraid server did this resolve; it was previously using a DHCP reservation.