manilx

P.S. I disabled the warning, re-enabled it again and did another scan. This time all was OK. Go figure

I also updated the plugin this morning but a scan shows exactly the same issue with ugreenleds-driver, so no change here.

done.

I suddenly got this in fix common problems: The plugin ugreenleds-driver.plg is not known to Community Applications and is possibly incompatible with your server Was fine yesterday! Had it running on 7.3 also since I updated a couple of days ago. And the plugin is available in the app store

I suddenly got this in fix common problems: The plugin ugreenleds-driver.plg is not known to Community Applications and is possibly incompatible with your server Was fine yesterday! Had it running on 7.3 also since I updated a couple of days ago. And the plugin is available in the app store

Migrated 2 Ugreen NAS, DXP480T and DXP6800 Pro, to boot from internal (old UGOS) nvme and also move licenses to TPM (which I was happy to find out that this worked with Ugreen). All green.

True about the replacement if it fails, hassle at least. But i would only boot from it and not use for anything else. But yes, guess flash is a lot easier in the long term.

Was waiting for the boot from nvme support but after seeing the video I will not use it. Why: I have a Ugreen DXP480T and a DXP6800 Pro and they do not seem to have (or Bios support) TPM. I wanted to boot from the unused UGOS small nvme for this but having to keep the flash drive for the license is just stupid. So I will keep using it as boot.

Using Arcane for compose stacks now. Works fine. Unraid team really has to step up here...... The whole docker experience is outdated.

FOLKS, lost hours on this, until I realized that Firefox started to act up. Trying the same in Brave had no issue. In the end I just had to delete cookies and cache in Firefox!!!! So restored VM's from backup. At least I now know how to: restore flash from backup clean libvirt.img and start from scratch restore VM's from scratch Always see the positive side. BTW I'm on macos latest version

I deleted all vm's. In VM manager stopped it and deleted and then recreated the libvirt.img Imported a VM from backup XML/disk. Tried to start it and the same issue: VNC does not work!? Did yesterday.

I had a subdata-set in cache/domains with nothing in it, had the name of one of my vm's. I managed to delete it. All my VM's are running fine but none can open the VNC window. I only have access via ssh. I restarted Unraid, didn't help. I restored the pen drive from last nights flash backup, didn't help. I don't now what to do else to have VNC running on the VM's again. I did not alter any settings in them. HELP

First Unraid OS update after entering the Unraid world a couple of months ago with 7.1.4 on an UGREEN NASync DXP6800 Pro. No issues. P.S. Still needs a good internal backup solution to compete with my QNAP's.....

Hi. Just installed this and it created the VM fine. BUT there was an error in the log when it did. Running latest version of Unraid 7 Warning: exec(): Unable to fork [TIMESTAMP='1760812599' EVENT='HomeAssistantinabox' SUBJECT='Home Assistant' DESCRIPTION='VM setup successfully completed. The VM is now ready to be run.' IMPORTANCE='normal' CONTENT='' LINK='' bash /boot/config/plugins/dynamix/notifications/agents/Pushover.sh] in /usr/local/emhttp/webGui/scripts/notify on line 228 Here is the log: version check passed. Continuing... Host path for '/domains' is /mnt/user/domains Highest Q35 machine type available is pc-q35-9.2 The default VM network type is br0 Icon already there skipping..... mkdir: created directory '/domains/Home Assistant' I have created the Home Assistant directories. Found .qcow2.xz file: https://github.com/home-assistant/operating-system/releases/download/16.2/haos_ova-16.2.qcow2.xz downloading the Home Assistant vdisk from the official source extracting the vdisk to /config/vdisk1.qcow2.xz (removing the .xz)... /config/vdisk1.qcow2.xz: 324.6 MiB / 861.6 MiB = 0.377, 25 MiB/s, 0:34 Moving the extracted vdisk to /domains/Home Assistant/vdisk1.img... vdisk downloaded and moved to /domains/Home Assistant/vdisk1.img. As this is an OVMF VM, I need to create an NVRAM file. Creating now .... Formatting '/etc/libvirt/qemu/nvram/9f056e44-615b-43b3-bae4-966d37c83336_VARS-pure-efi.fd', fmt=raw size=65536 All required files are present. Attempting to define the VM... Domain Home Assistant defined from /config/tmp.xml Warning: exec(): Unable to fork [TIMESTAMP='1760812599' EVENT='HomeAssistantinabox' SUBJECT='Home Assistant' DESCRIPTION='VM setup successfully completed. The VM is now ready to be run.' IMPORTANCE='normal' CONTENT='' LINK='' bash /boot/config/plugins/dynamix/notifications/agents/Pushover.sh] in /usr/local/emhttp/webGui/scripts/notify on line 228 current status of VM 'Home Assistant': shut off VM 'Home Assistant' is not running. RESTART is set to 'Yes'. Attempting to start the VM... Attempting to start VM 'Home Assistant' (Attempt 1/5)... Domain Home Assistant started VM 'Home Assistant' started successfully. current status of VM 'Home Assistant': running VM 'Home Assistant' is running. Checking for the IP address of the running VM... Guest agent is not responding. Waiting for 5 seconds before retrying... (1/9) Guest agent is not responding. Waiting for 5 seconds before retrying... (2/9) Guest agent is not responding. Waiting for 5 seconds before retrying... (3/9) Guest agent is not responding. Waiting for 5 seconds before retrying... (4/9) Guest agent is connected. The IPv4 address of the VM 'Home Assistant' is: 192.168.2.120 Reloading Nginx with the new configuration... * Reloading nginx configuration nginx ...done. Waiting for 5 minutes before checking again to ensure VM is still running...

Rebooted and it fixed the issue. Thx for coming back on this

No. None shown. They were deleted and then the stack was deleted. There is no trace of them anywhere (normal places) and they show up as unknown in the plugin.

I had a stack in docker compose manager plugin but I deleted it a while ago. No when I select to not update all docker containers in the Auto Update Applications plugin the docker apps I had previsously installed are shown as unknown. How can I remove them? I already uninstalled and reinstalled the plugin.

I had a stack in docker compose manager plugin but I deleted it a while ago. No when I select to not update all docker containers in the Auto Update Applications plugin the docker apps I had previsously installed are shown as unknown. How can I remove them? I already uninstalled and reinstalled the plugin.

Looks like I got this fixed by applying these: https://forums.unraid.net/topic/185576-working-with-nfs-on-unraid-best-practices/ and not using the cache on the respective arrays. Since I have them only on the archive I've had no more issues. Seems like the cache->array shares are an issue with nfs/connections even before the mover sets in.

Coming from QNAP where I never had any issues with this I find that my debian VM's loose nfs shares after a while. I have to reboot the vm's to get the shares connecting again. I had the shares as public, then read the sticky post here and made them private with the indicated options. But this didn't help. Unraid definitely is not QuTS Hero but that is not the point. But if I don't get this working I revert to the QNAP and use Unraid only for backups.....