ghstridr

Having an issue with starting a 3 container compose file of proxmox servers. The error is: Error response from daemon: error while creating mount source path '/sys/kernel/security': mkdir /sys/kernel/security: operation not permitted Unraid 7.2.4 with 128GB Ram. Compose file: services: pve-1: image: ghcr.io/longqt-sea/proxmox-ve container_name: pve-1 hostname: pve-1 privileged: true restart: unless-stopped cgroup: host ports: - "2222:22" - "3128:3128" - "8006:8006" # First node Web GUI is listening on 8006 networks: - dual_stack volumes: - /sys/fs/cgroup:/sys/fs/cgroup - /usr/lib/modules:/usr/lib/modules:ro - /sys/kernel/security:/sys/kernel/security - ./VM-Backup:/var/lib/vz/dump - ./ISOs:/var/lib/vz/template/iso # Replace ./ISOs with the path to your ISO folder pve-2: image: ghcr.io/longqt-sea/proxmox-ve container_name: pve-2 hostname: pve-2 privileged: true restart: unless-stopped cgroup: host ports: - "2223:22" - "3129:3128" - "8007:8006" # Second node Web GUI is listening on 8007 networks: - dual_stack volumes: - /sys/fs/cgroup:/sys/fs/cgroup - /usr/lib/modules:/usr/lib/modules:ro - /sys/kernel/security:/sys/kernel/security - ./VM-Backup:/var/lib/vz/dump - ./ISOs:/var/lib/vz/template/iso # Replace ./ISOs with the path to your ISO folder pve-3: image: ghcr.io/longqt-sea/proxmox-ve container_name: pve-3 hostname: pve-3 privileged: true restart: unless-stopped cgroup: host ports: - "2224:22" - "3130:3128" - "8008:8006" # Third node Web GUI is listening on 8008 networks: - dual_stack volumes: - /sys/fs/cgroup:/sys/fs/cgroup - /usr/lib/modules:/usr/lib/modules:ro - /sys/kernel/security:/sys/kernel/security - ./VM-Backup:/var/lib/vz/dump - ./ISOs:/var/lib/vz/template/iso # Replace ./ISOs with the path to your ISO folder networks: dual_stack: enable_ipv6: true driver: bridge ipam: config: - subnet: fd00::/48

I am trying to figure out how to add multiple network interfaces to a vm. Not pass through or physical interfaces. Just virtual ones. I didn't see a way to do it in the web page while creating or afterward. I've searched various ways and can't seem to find an answer for this.

I'm not sure what is going on. I'm on 7.1.3 and have been since about a week after release. Today I discovered that it can't reach mothership.unraid.net with a 'Socket closed' error. If I turn off the Docker service, everything is fine. Plugins can be update, app store is accessible, etc. I've checked all my network settings and they are valid and unchanged since I first installed Unraid on this box several years ago with the 6.x release. I saw someone reference having the vpn manager in 'active' mode and turning it off. I checked that, but it was already in inactive mode. Before I closed the page it wanted me to generate keys, so I did, but left the tunnel manager in inactive mode. The problem went away for a few minutes after applying the config with generated keys, but eventually came back (Docker service still running during this). The VM service doesn't affect this situation at all. Only having the Docker service running with our without any containers active causes this issue. I'm going to look at the network configs for the containers and switch to them all to bridge to see if that makes a difference. I have a few on a custom network behind nginx proxy manager, but that hasn't been a problem before. My docker service is configured for 'ipvlan' at the moment, no changes to that since wayback when 'macvlan' was causing problems. Should i switch back to 'macvlan' now? I'm hesitating to update to 7.1.4 until I can solve this unless the new update fixes things like this. pinkfloyd.local-diagnostics-20250627-1303.zip

@SimonF There isn't a audio port. This is a headless gpu meant for things like processing for LLMs. That is how I am using it right now. No display output needed.. The issue turned out to be a stuck state for the board where it wasn't responding. So a cold start from power on fixed things for now. I'll update if it occurs again.

Solved: Cold restart fixed things. I'll leave this post up in case someone happens to come across a similar issue.

Unraid version 7.0.1 CPU: i9-9900K RAM: 96GB MB: Gigabyte Z390 DESIGNARE-CF This was working just find in Unraid 6.xx. VM Config: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Ollama2</name> <uuid>14860697-0187-87b2-54ba-225059a6a357</uuid> <metadata> <vmtemplate xmlns="unraid" name="Ubuntu" icon="ubuntu.png" os="ubuntu" webui=""/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='8'/> <vcpupin vcpu='2' cpuset='1'/> <vcpupin vcpu='3' cpuset='9'/> <vcpupin vcpu='4' cpuset='2'/> <vcpupin vcpu='5' cpuset='10'/> <vcpupin vcpu='6' cpuset='3'/> <vcpupin vcpu='7' cpuset='11'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-9.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/14860697-0187-87b2-54ba-225059a6a357_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' clusters='1' cores='4' threads='2'/> <cache mode='passthrough'/> </cpu> <clock offset='utc'> <timer name='hpet' present='no'/> <timer name='hypervclock' present='no'/> <timer name='pit' tickpolicy='delay'/> <timer name='rtc' tickpolicy='catchup'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback' discard='ignore'/> <source file='/mnt/user/domains/Ollama2/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <serial>vdisk1</serial> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x8'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x9'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0xa'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0xb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0xc'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:1e:fe:2f'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us' sharePolicy='ignore'> <listen type='address' address='0.0.0.0'/> </graphics> <audio id='1' type='none'/> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </video> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/isos/vbios/NVIDIA.TeslaP4.8192.171211.rom'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev> <watchdog model='itco' action='reset'/> <memballoon model='none'/> </devices> </domain> Relevant Logs (can't find link to generate support zip now): Apr 21 13:20:58 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:20:58 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:20:59 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:20:59 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:22:41 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:22:41 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:22:41 pinkfloyd usb_manager: Info: rc.usb_manager vm_action Ollama2 prepare begin - Apr 21 13:22:41 pinkfloyd usb_manager: Info: rc.usb_manager vm_action Ollama2 stopped end - Apr 21 13:22:51 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:22:51 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:22:56 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:22:56 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:23:30 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:23:30 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:23:30 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:23:30 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:23:30 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:23:30 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:23:36 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:23:36 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:24:26 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:24:26 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:24:27 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:24:27 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:24:27 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:24:27 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:24:27 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:24:27 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:24:32 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:24:32 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:24:32 pinkfloyd usb_manager: Info: rc.usb_manager vm_action Ollama2 prepare begin - Apr 21 13:24:33 pinkfloyd usb_manager: Info: rc.usb_manager vm_action Ollama2 stopped end - Apr 21 13:24:45 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:24:45 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:33:28 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:33:28 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:35:26 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:35:26 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:35:26 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:35:26 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:35:27 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:35:27 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:35:27 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:35:27 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:35:32 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:35:32 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:35:32 pinkfloyd usb_manager: Info: rc.usb_manager vm_action Ollama2 prepare begin - Apr 21 13:35:32 pinkfloyd usb_manager: Info: rc.usb_manager vm_action Ollama2 stopped end - Apr 21 13:35:46 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:35:46 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:39:02 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 21 13:39:02 pinkfloyd kernel: vfio-pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Been doing the usual searching here for 'Tesla P4' and nothing relevant to my issues. My Google-fu seems to have failed me also. I will do a complete cold restart on the whole server because of the power state messages. I had discovered one core on the cpu stuck at 100%. That and the powerstate messages make me believe that the Tesla P4 might be in a stuck state and need a power cycle. I'll report back in a bit if that fixes it or not. TIA.

Trying to add the nvidia support and the container fails to start with a complaint from docker: docker run -d --name='CoolerControl' --net='bridge' --pids-limit 2048 --privileged=true -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e HOST_HOSTNAME="pinkfloyd.local" -e HOST_CONTAINERNAME="CoolerControl" -e 'CA_TS_FALLBACK_DIR'='/etc/coolercontrol' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:11987]/' -l net.unraid.docker.icon='https://gitlab.com/coolercontrol/coolercontrol/-/raw/main/coolercontrol/icons/icon.png' -p '11987:11987/tcp' -v '/mnt/user/appdata/coolercontrol':'/etc/coolercontrol':'rw' -v '/sys/class/hwmon':'/sys/class/hwmon':'ro' '--runtime=nvidia --gpus=all' 'ghcr.io/guniv/coolercontrol-docker' docker: Error response from daemon: unknown or invalid runtime name: nvidia --gpus=all. See 'docker run --help'. This is from following the instructions on how to activate the functionality. Without it the app starts. I tried the nvidia support again, this time with double-quots around all the flags (ie. "--runtime=nvidia --gpus=all") and got a similar message, but I noticed that the container image name is appearing after the additional args. docker run -d --name='CoolerControl' --net='bridge' --pids-limit 2048 --privileged=true -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e HOST_HOSTNAME="pinkfloyd.local" -e HOST_CONTAINERNAME="CoolerControl" -e 'CA_TS_FALLBACK_DIR'='/etc/coolercontrol' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:11987]/' -l net.unraid.docker.icon='https://gitlab.com/coolercontrol/coolercontrol/-/raw/main/coolercontrol/icons/icon.png' -p '11987:11987/tcp' -v '/mnt/user/appdata/coolercontrol':'/etc/coolercontrol':'rw' -v '/sys/class/hwmon':'/sys/class/hwmon':'ro' "--runtime=nvidia --gpus=all" 'ghcr.io/guniv/coolercontrol-docker' docker: Error response from daemon: unknown or invalid runtime name: nvidia --gpus=all. See 'docker run --help'. So I'm thinking that 'Extra Values' is inserting in the wrong order. Should be on the end of the command. BTW, when the container fails to start, the container disappears from the webgui and from 'docker container ls --all'. Even if you successfully started it previously without the nvidia args, as soon as you apply them...the container disappears! Neat trick, huh?

No, scripts. I don't see a way to specifically mark the USB drive as pass-through. In the pcie devices list , they are all grouped together.

I think I have a bug. I'm not quite sure what is causing it, but basically, I plugin a 32GB USB and it seems to be grabbed by UD. I can manually assign it to a VM, like my mac vm, but it will shortly be yanked away and show up in UD. The logs seem to support that. This was working, attaching it to the MacOS VM, but I formatted the USB drive. Right after that it started disappearing out of the MacOS VM within seconds of being attached to it no matter how many times I kept reattaching it to the VM. Every time it disappears, it is mounted by UD on the host file system. I made sure that automount USB is turned off, but that didn't affect anything. In the log you can see when I have unplugged and plugged in the device, numerous times. You can also see when I have attached to a VM and then it is remounted by UD. I don't know what to do. Unraid: 6.12.14 UD: 2024.12.27 Dec 29 18:19:52 pinkfloyd kernel: sd 5:0:0:0: Attached scsi generic sg7 type 0 Dec 29 18:19:52 pinkfloyd kernel: sd 5:0:0:0: [sdk] 60604416 512-byte logical blocks: (31.0 GB/28.9 GiB) Dec 29 18:19:52 pinkfloyd kernel: sd 5:0:0:0: [sdk] Write Protect is off Dec 29 18:19:52 pinkfloyd kernel: sd 5:0:0:0: [sdk] Mode Sense: 45 00 00 00 Dec 29 18:19:52 pinkfloyd kernel: sd 5:0:0:0: [sdk] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA Dec 29 18:19:52 pinkfloyd kernel: sdk: sdk1 sdk2 Dec 29 18:19:52 pinkfloyd kernel: sd 5:0:0:0: [sdk] Attached SCSI removable disk Dec 29 18:19:53 pinkfloyd unassigned.devices: Mounting partition 'sdk2' at mountpoint '/mnt/disks/MACOPENCOREBOOT'... Dec 29 18:19:53 pinkfloyd unassigned.devices: Mounting partition 'sdk1' at mountpoint '/mnt/disks/EFI'... Dec 29 18:19:53 pinkfloyd unassigned.devices: Partition 'sdk2' is already mounted. Dec 29 18:19:53 pinkfloyd unassigned.devices: Partition 'sdk1' is already mounted. Dec 29 18:20:14 pinkfloyd usb_manager: Info: virsh called Ventura-Test 002 026 Device attached successfully Dec 29 18:20:22 pinkfloyd kernel: usb 2-6: USB disconnect, device number 26 Dec 29 18:20:22 pinkfloyd usb_manager: Info: rc.usb_manager usb_remove _USB_DISK_3.0_0701232839E69D60 /dev/bus/usb/002/026 002 026 Dec 29 18:20:22 pinkfloyd usb_manager: Info: rc.usb_manager Device Match 002/026 vm: Ventura-Test 002 026 Dec 29 18:20:22 pinkfloyd usb_manager: Info: virsh called Ventura-Test 002 026 Device detached successfully Dec 29 18:20:22 pinkfloyd usb_manager: Info: rc.usb_manager Disconnect 002/026 vm: Ventura-Test running 002 026 Dec 29 18:20:22 pinkfloyd usb_manager: Info: rc.usb_manager Removed 002/026 vm: Ventura-Test running 002 026 Dec 29 18:20:22 pinkfloyd kernel: usb 2-6: new SuperSpeed USB device number 27 using xhci_hcd Dec 29 18:20:22 pinkfloyd kernel: usb-storage 2-6:1.0: USB Mass Storage device detected Dec 29 18:20:22 pinkfloyd kernel: scsi host5: usb-storage 2-6:1.0 Dec 29 18:20:22 pinkfloyd usb_manager: Info: rc.usb_manager usb_add _USB_DISK_3.0_0701232839E69D60 /dev/bus/usb/002/027 002 027 Dec 29 18:20:23 pinkfloyd usb_manager: Info: rc.usb_manager Autoconnect Parent usb2 Dec 29 18:20:23 pinkfloyd usb_manager: Info: rc.usb_manager Autoconnect No Mapping found _USB_DISK_3.0_0701232839E69D60 /dev/bus/usb/002/027 002 027 port 2-6 Dec 29 18:20:23 pinkfloyd kernel: scsi 5:0:0:0: Direct-Access USB DISK 3.0 PMAP PQ: 0 ANSI: 6 Dec 29 18:20:23 pinkfloyd kernel: sd 5:0:0:0: Attached scsi generic sg7 type 0 Dec 29 18:20:24 pinkfloyd kernel: sd 5:0:0:0: [sdk] 60604416 512-byte logical blocks: (31.0 GB/28.9 GiB) Dec 29 18:20:24 pinkfloyd kernel: sd 5:0:0:0: [sdk] Write Protect is off Dec 29 18:20:24 pinkfloyd kernel: sd 5:0:0:0: [sdk] Mode Sense: 45 00 00 00 Dec 29 18:20:24 pinkfloyd kernel: sd 5:0:0:0: [sdk] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA Dec 29 18:20:24 pinkfloyd kernel: sdk: sdk1 sdk2 Dec 29 18:20:24 pinkfloyd kernel: sd 5:0:0:0: [sdk] Attached SCSI removable disk Dec 29 18:20:25 pinkfloyd unassigned.devices: Mounting partition 'sdk2' at mountpoint '/mnt/disks/MACOPENCOREBOOT'... Dec 29 18:20:25 pinkfloyd unassigned.devices: Mounting partition 'sdk1' at mountpoint '/mnt/disks/EFI'... Dec 29 18:20:25 pinkfloyd unassigned.devices: Partition 'sdk1' is already mounted. Dec 29 18:20:25 pinkfloyd unassigned.devices: Partition 'sdk2' is already mounted. Dec 29 18:21:57 pinkfloyd emhttpd: _USB_DISK_3.0_0701232839E69D60-0:0 (sdk) 512 60604416 Dec 29 18:21:57 pinkfloyd emhttpd: read SMART /dev/sdk Dec 29 18:23:43 pinkfloyd ool www[22963]: /usr/local/emhttp/plugins/unassigned.devices/scripts/rc.settings 'save' Dec 29 18:24:00 pinkfloyd kernel: usb 2-6: USB disconnect, device number 27 Dec 29 18:24:02 pinkfloyd usb_manager: Info: rc.usb_manager usb_remove _USB_DISK_3.0_0701232839E69D60 /dev/bus/usb/002/027 002 027 Dec 29 18:24:02 pinkfloyd usb_manager: Info: rc.usb_manager Device Match 002/027 vm: 002 027 Dec 29 18:24:02 pinkfloyd usb_manager: Info: rc.usb_manager Removed 002/027 vm: nostate 002 027 Dec 29 18:24:09 pinkfloyd kernel: usb 2-6: new SuperSpeed USB device number 28 using xhci_hcd Dec 29 18:24:09 pinkfloyd kernel: usb-storage 2-6:1.0: USB Mass Storage device detected Dec 29 18:24:09 pinkfloyd kernel: scsi host5: usb-storage 2-6:1.0 Dec 29 18:24:09 pinkfloyd usb_manager: Info: rc.usb_manager usb_add _USB_DISK_3.0_0701232839E69D60 /dev/bus/usb/002/028 002 028 Dec 29 18:24:09 pinkfloyd usb_manager: Info: rc.usb_manager Autoconnect Parent usb2 Dec 29 18:24:09 pinkfloyd usb_manager: Info: rc.usb_manager Autoconnect No Mapping found _USB_DISK_3.0_0701232839E69D60 /dev/bus/usb/002/028 002 028 port 2-6 Dec 29 18:24:10 pinkfloyd kernel: scsi 5:0:0:0: Direct-Access USB DISK 3.0 PMAP PQ: 0 ANSI: 6 Dec 29 18:24:10 pinkfloyd kernel: sd 5:0:0:0: Attached scsi generic sg7 type 0 Dec 29 18:24:10 pinkfloyd kernel: sd 5:0:0:0: [sdk] 60604416 512-byte logical blocks: (31.0 GB/28.9 GiB) Dec 29 18:24:10 pinkfloyd kernel: sd 5:0:0:0: [sdk] Write Protect is off Dec 29 18:24:10 pinkfloyd kernel: sd 5:0:0:0: [sdk] Mode Sense: 45 00 00 00 Dec 29 18:24:10 pinkfloyd kernel: sd 5:0:0:0: [sdk] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA Dec 29 18:24:10 pinkfloyd kernel: sdk: sdk1 sdk2 Dec 29 18:24:10 pinkfloyd kernel: sd 5:0:0:0: [sdk] Attached SCSI removable disk Dec 29 18:24:11 pinkfloyd unassigned.devices: Disk with ID '_USB_DISK_3.0_0701232839E69D60-0:0 (dev7)' is not set to auto mount. Dec 29 18:24:11 pinkfloyd unassigned.devices: Disk with ID '_USB_DISK_3.0_0701232839E69D60-0:0 (dev7)' is not set to auto mount. Dec 29 18:24:59 pinkfloyd ool www[29731]: /usr/local/emhttp/plugins/unassigned.devices/scripts/rc.settings 'save' Dec 29 18:27:08 pinkfloyd usb_manager: Info: virsh called Ventura-Test 002 028 Device attached successfully Dec 29 18:27:16 pinkfloyd kernel: usb 2-6: USB disconnect, device number 28 Dec 29 18:27:16 pinkfloyd usb_manager: Info: rc.usb_manager usb_remove _USB_DISK_3.0_0701232839E69D60 /dev/bus/usb/002/028 002 028 Dec 29 18:27:16 pinkfloyd usb_manager: Info: rc.usb_manager Device Match 002/028 vm: Ventura-Test 002 028 Dec 29 18:27:16 pinkfloyd usb_manager: Info: virsh called Ventura-Test 002 028 Device detached successfully Dec 29 18:27:16 pinkfloyd usb_manager: Info: rc.usb_manager Disconnect 002/028 vm: Ventura-Test running 002 028 Dec 29 18:27:16 pinkfloyd usb_manager: Info: rc.usb_manager Removed 002/028 vm: Ventura-Test running 002 028 Dec 29 18:27:17 pinkfloyd kernel: usb 2-6: new SuperSpeed USB device number 29 using xhci_hcd Dec 29 18:27:17 pinkfloyd kernel: usb-storage 2-6:1.0: USB Mass Storage device detected Dec 29 18:27:17 pinkfloyd kernel: scsi host5: usb-storage 2-6:1.0 Dec 29 18:27:17 pinkfloyd usb_manager: Info: rc.usb_manager usb_add _USB_DISK_3.0_0701232839E69D60 /dev/bus/usb/002/029 002 029 Dec 29 18:27:17 pinkfloyd usb_manager: Info: rc.usb_manager Autoconnect Parent usb2 Dec 29 18:27:17 pinkfloyd usb_manager: Info: rc.usb_manager Autoconnect No Mapping found _USB_DISK_3.0_0701232839E69D60 /dev/bus/usb/002/029 002 029 port 2-6 Dec 29 18:27:18 pinkfloyd kernel: scsi 5:0:0:0: Direct-Access USB DISK 3.0 PMAP PQ: 0 ANSI: 6 Dec 29 18:27:18 pinkfloyd kernel: sd 5:0:0:0: Attached scsi generic sg7 type 0 Dec 29 18:27:18 pinkfloyd kernel: sd 5:0:0:0: [sdk] 60604416 512-byte logical blocks: (31.0 GB/28.9 GiB) Dec 29 18:27:18 pinkfloyd kernel: sd 5:0:0:0: [sdk] Write Protect is off Dec 29 18:27:18 pinkfloyd kernel: sd 5:0:0:0: [sdk] Mode Sense: 45 00 00 00 Dec 29 18:27:18 pinkfloyd kernel: sd 5:0:0:0: [sdk] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA Dec 29 18:27:18 pinkfloyd kernel: sdk: sdk1 sdk2 Dec 29 18:27:18 pinkfloyd kernel: sd 5:0:0:0: [sdk] Attached SCSI removable disk Dec 29 18:27:19 pinkfloyd unassigned.devices: Disk with ID '_USB_DISK_3.0_0701232839E69D60-0:0 (dev7)' is not set to auto mount. Dec 29 18:27:19 pinkfloyd unassigned.devices: Disk with ID '_USB_DISK_3.0_0701232839E69D60-0:0 (dev7)' is not set to auto mount. ud_diagnostics-20241229-184748.zip

Current Grafana-Unraid-Stack is broken from docker log: [info] Initialisation started... [info] influxdb fixed. [info] loki fixed. [info] telegraf fixed. [info] promtail fixed. [info] grafana fixed. [info] Initialisation complete [info] Runing apps... [info] Run influxdb as service on port 8086 Executable /usr/bin/influxd does not exist! [info] Run loki as daemon on port 3100 [info] Run telegraf as service [info] Run promtail as daemon on port 9086 [info] Run grafana as service on port 3006 * Starting Grafana Server ...done. [info] All done [error] influxdb crashed! [error] loki crashed! [info] Skip hddtemp due to USE_HDDTEMP set to no [error] telegraf crashed! [info] promtail PID: 77 [error] grafana crashed! [error] influxdb crashed! [error] loki crashed! [info] Skip hddtemp due to USE_HDDTEMP set to no [error] telegraf crashed! [info] promtail PID: 77 [error] grafana crashed! Looking around in the shell, influxdb and telegraf binaries are definitely not installed. The gpg signatures are waaaaay out of day and the apt sources for influx are pointing at 'focal' and trying to install on jammy. Seriously lazy developer.

@dlandon Attached my ud_diagnostics per your request. I gathered it after updating to version 2024.05.07 of UD. Checked and the mount buttons are currently greyed out. ud_diagnostics-20240507-202813.zip

Unraid 6.12.10 Diagnostics attached After a reboot, the mount buttons are always greyed out. If I start stepping through the wizard and select the windows icon and then the scan button, both mount buttons will become available after the scan is done. I have the smb version turned off and extended the timeout to 120 seconds (which I somehow think that the timeout isn't being used?) I also need to add that for some reason one of my ssds that are part of a zfs zraid6 pool is showing as unmountable even though zpool status shows it as working perfectly, no errors from a scrub either. Attached a screenshot pinkfloyd.local-diagnostics-20240502-1834.zip

You are very welcome. Glad to be of help.

I have some experience with building bespoke clusters using various technologies. Forgive me here, but proxmox does have this ability if you wanted to started experimenting using a gui or something. Again sorry for mentioning a competing product. Back to UnRaid. If you have 2 UnRaid servers and separate shared storage, you could move all your data/docker stuff there, but you have to have software to manage the system. One method is to provide a quorum or fencing. Basically this keeps the slave machine/s from accessing data that currently belongs to the master. It keeps the slave/s from locking/writing to files while they are held open by the master, thus avoiding corruption and data loss. The shared storage can be accomplished over network via iScsi, NFS or even SMB as well as a number of other more advance storage protocols. These are the ones commonly available in Open Source. You can also use older cabled scsi or sas methods as long as you have interfaces and controllers that support fencing to keep the hosts separated. Now the networking bit. You would need a way of introducing a VIP (virtual ip) to the networking stack so that accessing it would take you to the current 'master' in the cluster. The idea is that when one member of the cluster becomes unavailable, code on the other machine takes over the VIP and takes over all the services that were being manage by the now defunct old master. There are a couple of ways of accomplishing that. One such piece of software is Pacemaker. It can handle switching a VIP, stopping/starting services, mounting/connecting storage, etc. It determines which is the master (assuming only 2 members in the cluster) by using a heartbeat signal which is usually sent over a private ethernet link between them. I've just used a direct connection cable between them before and let the nic cards figure the auto-mdx for themselves. The heartbeat allows to keep track of the health of the other machine. It can include status info on several aspects of the opposite machine which can all go into making decisions for what actions to take. Say if you have multiple dockers on a bridge interface so they all have their own ip? Well you could have certain dockers 'moved' over to the other cluster member when, say, the overall cpu usage gets too high on the other machine. I would shut down the docker so that the config info and data shares are updated and flushed to the shared storage. Then you could import it or already have it imported and start it up on the other machine and that docker ip should be now available there. I'm probably missing/glossing over some of the finer details, but proper fail over clustering is a complicated subject. So it would be possible with UnRaid, but it would be A LOT of hacking. You really have to know and understand your networking and shared storage concepts. That said, I really love UnRaid for it's standalone abilities and I feel that it does a lot of things very well. Proxmox has the clustering thing designed in pretty well, so that would be the better tool for the job if clustering is your aim. Use the correct tool for the job instead making the one you have fit the odd shaped hole.

So, shouldn't the nerdpack plugin check that the required versions are up to date for the requirements in other plugins like vmbackup? ex. vmbackup requires x.x.x and it is installed, so it's marked up to date. If there is a conflict between other plugins, it notes that and doesn't recommend a upgrade in that situation as that would be up to the plugin authors to discern.