20 hours ago20 hr So I'm aware this is a underlying Linux/power issue (at least that's how I understand it) - I have been dealing with issues with my cache drive dropping for some time now. My original config (on different hardware even) was 2 nvme drives in bfrs as cache. Randomly 1 of the 2 would drop on sustained writes and the issue required a full shutdown to resolve (reboot dosn't bring back) This also was on OS 6 and I had configured the boot prams by hand. After managing to get to OS 7 I noted unraid devs cleverly added these into the boot prams as a toggle option to make this easy. Its toggled on and after many more drops I got a replacement NAS hardware in an attempt to see if that might help resolve as sometimes just a different chipset/drive etc is enough to better handle things. Now I have 3 nvme bays. I started with continuing to do a 2 drive cache but had the same issues. I had read one comment that someone had resolved this by switching to a single drive cache. As a test I have moved my dockers to a 2 drive and the main cache to a single drive. This has at least eliminated unclean shutdowns from when this issue would occur while moving. Again, when hitting sustained heavy writes this drive will ghost itself. I'm not 100% on this but I think it tends to happen most (or at least easy to repro) when I kick off downloads via binhex-sabnzbdvpn. It seems to saturate the controller. I just finished another test after adding the extra pram to the docker: --device-write-bps=/dev/nvme2n1:50mb and it failed again.Is there anything else that can be done for this issue where the controller bus drops the cache drive on high i/o and power draw?All the power options are already toggled on in Boot Paramsappend initrd=/bzroot usbcore.autosuspend=-1 nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off
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.