ADvorsky

Yes, it vanishes on my system as well after each reboot, but the nics are present as configured in the file. Without the file present during boot the 10gb nic is not available. That's why i have a copy of that file to recreating it after each reboot on array start

55 views, nobody answered This does not spin my hope up that this is gonna work...

run a memtest on that machine.... just to be sure

Try my network-rules.cfg with your mac addresses... If they dont come up, its something different... Worth a try though.

I had a similar issue including the vanishing network-rules.cfg after each restart... (btw, for this everybody replying to a previous thread of mine insists i have something installed that removes it, which is actually not the case. i still think that its unraid itself removing the file due to reasons during startup after reading it.) The machine has 2 NICs, the onboard (which whyever cannot be disabled in the bios) and the 10GBit Nic Here is my network-rules.cfg: SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="e4:1d:9c:92:ce:44", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="22:48:5c:05:16:45", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1" It is merely to make sure the 10GBit is eth0 because Unraid has some special handling for eth0 as we all know... As well, I made sure its there before restarting the server (user script just writes it to /boot/config each hour ) hope this helps you as well

I tried a lot of combinations of adding [global] vfs objects = dirsort to the samba extra config, but nothing I tried worked so far. Anybody had more luck with this?

just for your info.... tailscales magic dns might break your docker containers. /etc/resolv.conf gets copied to all freshly started contaieners from the host, which points to a dns not existing inside the container... disabling magic dns resolved this issue.

Same for me

After uninstalling and re installing a lot of plugin and nothing changed.... I just cleared all browser data, cookies, etc... And voila... it worked again 🤦‍♂️ So for everyone having issues this kind, dont be as stupid as i was... Just do the same and clear your browser data...

Same issue here since last night on 2 unraid instances. Maybe due to an auto upgrade? Unraid WebUI stopped being responsive and no information on the array or CPU stats are given. UD Plugin won't show anything and blocks the whole WebUI from working correctly. i am trying to uninstall ud now from one instance...

Actually i installed a few plugins, to try them out. i will check if this is caused by one of them... thanks for pointing this out.

Hi there... I am currently testing 6.10RC1 as a new user and i must say, i am impressed and really like what i see there. However, i do encounter an issue with the crontab for the mover. The log itself states the following line: Aug 30 10:55:01 Horus crond[1786]: failed parsing crontab for user root: /usr/local/sbin/mover.old start 2>/dev/null when i check the crontab the entry looks cropped from all cron information except from the cmdline: # Generated system monitoring schedule: */1 * * * * /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null # Generated mover schedule: 0 */1 * * * /usr/local/sbin/mover |& logger # Generated schedule for forced move /usr/local/sbin/mover.old start 2>/dev/null # CRON for CA background scanning of applications 18 * * * * php /usr/local/emhttp/plugins/community.applications/scripts/notices.php > /dev/null 2 >&1 # Generated ssd trim schedule: 0 */1 * * * /sbin/fstrim -a -v | logger &> /dev/null # Generated system data collection schedule: */1 * * * * /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Any ideas what i could have done wrong, or is this maybe a bug in the rc1? PS: The mover itself however does start, but of course not the .old one.... cheers, Alex