trott

as the mover tuning plugins has been removed, is there any way to disable mover scheduling, I don't want to run Mover only based on schedule

Hi, when the plugin will be updated to use the data from emhttp?

I'm mix sata ssd, hdd and sas hdd on the same lsi 3408 with an expander without any issue

Can we have different HDD groups to control the fan speed instead of only the max temp

are you sure BTRFS is good for VM disk?

currently I'm putting the docker and VM on an unassigned device, how can I change the unassigned device to one cache pool?

May I sugguest to use 5.6 kernel (even RC one) for 6.9 beta/RC; 5.6 really includes a lot of new features, (wireguard for example), it is better to test it eariler

ECC is NOT working on current kerenl Unraid used

as I remember, telegraf itself has apcupsd input, you don't need another docker for it

I'm in China and pulling from docker hub is very slow, is there way that I can add a China mirror for docker hub?

are you using the cmd: btrfs subvol delete /mnt/user/TimeMachine/xxx ?

I like how easy unraid is to setup a VM I would see multi-array support, better with actual raid 1/10 support

my log also full of similar logs, in kodi, when you click a movie trying to play it, sometimes it says the file is not there, but sometimes it will work for the same movie, on such issue on 6.72, it would be better to upgrade NFS to supoort V3 Dec 27 17:33:18 Tower rpcbind[10637]: connect from 192.168.2.21 to getport/addr(nfs) Dec 27 18:26:20 Tower rpcbind[3941]: connect from 192.168.2.21 to dump() Dec 27 18:26:20 Tower rpcbind[3942]: connect from 192.168.2.21 to getport/addr(mountd) Dec 27 18:26:27 Tower rpcbind[4226]: connect from 192.168.2.21 to dump() Dec 27 18:26:27 Tower rpcbind[4227]: connect from 192.168.2.21 to getport/addr(mountd) Dec 27 18:26:31 Tower rpcbind[4387]: connect from 192.168.2.21 to dump() Dec 27 18:26:31 Tower rpcbind[4388]: connect from 192.168.2.21 to getport/addr(mountd) Dec 27 18:26:36 Tower rpcbind[4549]: connect from 192.168.2.21 to dump() Dec 27 18:26:36 Tower rpcbind[4550]: connect from 192.168.2.21 to getport/addr(mountd) Dec 27 18:26:37 Tower rpcbind[4590]: connect from 192.168.2.21 to dump() Dec 27 18:26:37 Tower rpcbind[4591]: connect from 192.168.2.21 to getport/addr(mountd) Dec 27 18:26:38 Tower rpcbind[4592]: connect from 192.168.2.21 to getport/addr(mountd) Dec 27 18:26:38 Tower rpc.mountd[5447]: authenticated mount request from 192.168.2.21:668 for /mnt/user/media

actully I have the same issue, and it should be the same on as reported below

6.8 use 4.19 kernel, please wait 6.9 RC1 which will use 5.4 kernel

any news on 6.9 RC1?

+1, I also request to add NFS v4 support in unraid

I think I just wait for the 5.9-rc1, I'm on ryzen, I need 5.4 kernel to test ECC

RC8 ha revert kernel back to 4.19, so it might be the issue

to be honest, I don't think it is unraid issue, my best guess is it is the docker issue with how the docker manage the network, it is better to report to docker team

then I might have different problem, I will grab the log when I upgrade my unraid next time

I read in other post that 6.9 RC1 will use 5.4

I remember I have the same issue after I poweroff and restart the sever, first time boot, all IP address is not set, then I reboot the server, this time system will have a IP of 169.x.x.x, reboot again, now system will get the correct IP I thought I was the only one have this issue since I never see anyone report similar issue, would you please try to reboot to see if you can duplicate my issue

thanks, should the 5.4 kernel will be release in 2 days?

sorry, I have no GPU on the sever yet