tjb_altf4

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.

Instead of garbage collection happening on a schedule, e.g. once a day, it happens as soon as possible.

Seen the same with the UI, I'm fairly certain the cause is 3rd party plugins that need to be updated, in this case the plex streams plugin.

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

its says your plots directory is empty also, I'd double check your paths are still correct, and maybe check permissions also. I'm still on 1.6.2 so I've not personally tested the new build yet.

For reference, I went through this and did delete the system share, this is how I organised it.

You'll need to remove the share of the same name first, but yes works fine.

For what its worth, I've provisioned another 2 Unraid licences on Sandisk Ultra Flair (USB3.0) with zero problems for last couple of weeks.

A few I know of, the flag for third-party cooling response is an important one on the Dells, as this flag is only set through ipmitool and cannot be set in the ipmi ui (iDRAC) or bios. Disabling this flag stops the system raising minimum fan speed by +60% when you add third party cards like non-server GPUs. To set value to Low FAN speed offset run command: ipmitool -I lanplus -H <IPADDRESS> -U <USERNAME> -P <PASSWORD> raw 0x30 0xCE 0x00 0x09 0x07 0x00 0x00 0x00 0x07 0x00 0x02 0x02 0x02 0x00 0x00 To set value to high FAN speed offset run command: ipmitool -I lanplus -H <IPADDRESS> -U <USERNAME> -P <PASSWORD> raw 0x30 0xCE 0x00 0x09 0x07 0x00 0x00 0x00 0x07 0x00 0x02 0x02 0x02 0x01 0x00 Set Third-Party PCIe Card Default Cooling Response Logic To Disabled ipmitool -I lanplus -H <IPADDRESS> -U <USERNAME> -P <PASSWORD> raw 0x30 0xce 0x00 0x16 0x05 0x00 0x00 0x00 0x05 0x00 0x01 0x00 0x00 Set Third-Party PCIe Card Default Cooling Response Logic To Enabled ipmitool -I lanplus -H <IPADDRESS> -U <USERNAME> -P <PASSWORD> raw 0x30 0xce 0x00 0x16 0x05 0x00 0x00 0x00 0x05 0x00 0x00 0x00 0x00 Get Third-Party PCIe Card Default Cooling Response Logic Status ipmitool -I lanplus -H <IPADDRESS> -U <USERNAME> -P <PASSWORD> raw 0x30 0xce 0x01 0x16 0x05 0x00 0x00 0x00 The response data is: 16 05 00 00 00 05 00 01 00 00 (Disabled) 16 05 00 00 00 05 00 00 00 00 (Enabled) Referenced for 13th gen Dell servers, but I believe it is applicable to other models. https://www.dell.com/support/kbdoc/en-au/000135682/how-to-disable-the-third-party-pcie-card-default-cooling-response-on-poweredge-13g-servers Also note IPMI is disabled by default, and you have to got into iDRAC settings to enable it.