tjb_altf4

I've been on this for a week or 2, mostly because patch notes said it was supposed to help some L3 switch issues I was seeing (which did improve). Have had no issues so far

You can set this at the disk or pool level also.

Yeah all Nvidia and commands I can see in nvidia-smi... as far as I could find there are 3 areas to update: apps array in gpustatus.page nvidia class in Nvidia.php app icons in images folder Should I make a pull request instead and just add what I need?

I get this on occasion still, and for some reason if I open the web cli and run top, it will finish stopping immediately.

Any chance we can see the config for supported apps moved from being hardcoded to a config file ? I have some containers I've put together that use GPU which are unlikely to be used/useful for most others, and would be ideal if I could add without those without needing to modify/fork the plugin. Thanks!

I didn't know that, thanks! I feel a discrete option would be more user friendly and ultimately more informative, but removing the mac address will do the job for me

Make sure you only have one network cable going to your unraid server, and you might need to power cycle the connected switch also to clear the arp cache. After that, it should connect even if Unraid still has those interfaces bonded. As you've enabled dhcp, then the webui might be coming up under a different IP address. I often just blow away the network.cfg file when having problems, which reverts to safe default network settings using dhcp (after reboot of course).

95% of the time I want the array to auto start, but it is a little painful constantly changing the autostart option for one off events like maintenance tasks or upgrades. On the occasions I don't want auto array start after a reboot (say I've just installed new hardware), the idea of this feature would be to allow me to choose array autostart to be disabled at boot menu time, e.g. a syslinux config option. Bonus points if this is implemented in a way that allows the dev team to set "next boot mode" to cater for events like after an Unraid OS upgrade (one of the main times disabling auto-start is important IMHO), or a dirty shutdown. This is how the config might look in Syslinux config screen (which would reflect boot options)

Can we get a dashboard graph for memory (RAM) usage on the Memory panel ? Thanks!

I have multiple network interfaces, and it would be great on the new dashboard for it to allow multiple instances, so that we can have multiple Network traffic graph views

Looking at reports of similar issues, another thing to check is time in BIOS is set to UTC

Just to cover bases, make sure browser/adblocker has greenlit the server for popups and blocklists. Time issues might be a red herring for browser extension / security quirks.

Try these instead 0.pool.ntp.org 1.pool.ntp.org 2.pool.ntp.org 3.pool.ntp.org

You can do this by creating the new share (empty) and have a symbolic link to the movies folder you want within the new share. The caveat is that permissions will be whatever this new share is set to, so set as read-only there.

Greetings from Australia and thank you for finally fixing the screen orientation bug.

He said he'd post on here, but Its showing the same on my stock 6.10.3 install also. In comparison, this is my other system on 6.11.5

Has 6.10.x support been dropped? The existing plugin can no longer find drivers (on this Unraid version etc). I noticed this while helping someone over on discord with the same problem. My existing driver install is fine for now, but I'm guessing next reboot it will fall over.

I use the go file located on the boot disk /boot/config/go add this entry below the existing commands: /usr/bin/qemu-ga -l /var/log/qemu-ga.log -d & As a test you can run this in the command line to get the agent running for the current session, it should show up in proxmox straight away. The go file will run this command on subsequent reboots.

Only if you are using the mac addresses assigned to those containers for some purpose, so for nginx and other things in layer 3 it won't/shouldn't have an impact. The one thing I miss from using macvlan is seeing each container appear in my router software (unifi), whereas ipvlan all share the host/interface mac.

@Waddoo further to the above reply, you need to stop the Docker service, not just running docker containers. To do this: go to SETTINGS > DOCKER with advanced view toggled (top right) set Enable Docker: No, then set Docker custom network type: ipvlan Once complete: set Enable Docker: Yes to restart docker service. Report back with fresh diagnostics if kernel panics continue.

TRIM is not supported in the Unraid array, but has always been supported in pools e.g. Cache pool. ZFS when used in the traditional sense (pools), supports TRIM already. ZFS can be used in the Unraid array as single disks filesystems, which loses most features people want from ZFS so isn't common, and in this scenario TRIM is not currently supported. Until a later release where the concept of pools and array gets a shake up, the workaround is to create a token device in the array, such as a usb disk, and utilise a pool for zfs, just make sure you update your share preferences to Cache only so data stays there. My personal favourite version of the technique is to add a HDD to the array and use this as a backup target.

Manual setting doesn't seem to work for me, but fan offset can be set (e.g. +20% fan speed). I'm on idrac 2.83.83.83 I think snmp is the only way to get firmware level, this doc covers idrac 7+8 https://dl.dell.com/topicspdf/dell-opnmang-sw-v8.1_connectivity-guide_en-us.pdf

Hyperscalers are a completely different kettle of fish to a home nas user, besides they won't be using device managed SMR junk that we are sold, they'll be on HM-SMR.

Yep you are correct, but I wanted to make sure the R7 series (2U) was accounted for also. I did make sure to call out the models I was describing, I'm sure the server 1U and 4U variants differ also.

Pic is worth a thousand words Numbers for a R730 poweredge show here, same layout for R720. It would be optimal to control as one group, but optionally controlling them in 2 groups (123 and 456) would be useful for people only running one CPU