Stable Releases

Hello,   After i update from unraid 6.9.someting to 6.10.3 i have already two times a message that he tell me that the drive is verry hot about 84 c . Before i no problem with that. I have also check inmy server rack and feel the temp from the harddisck but is not so warm like 84 c. Around the 35 a 40 c.   If you need some extra information i here it.   greetings Fireozzei

Hey all, Just upgraded from 6.9.2 to 6.10.0 and my VMs VNC no longer connects. As far as I know, I'm using default settings, but both of my VMs VNC worked pre-update, and they both don't work post update. The VMs themselves are working, as I can ssh into them, but the VNC itself just loads a failed to connect (Screenshot & diagnostics attached).   Looks like there might be some related logs in the syslog - which if I'm correlating to the system/urls.txt file correctly, I imagi

Hi all,   i just tried to setup a new ubuntu vm and used the integrated vnc feature as gpu. once setup i started the vm and tried to connect via the But it fails with "Failed to connect to server", it is not working event after a minute, is it possible that this functionality has broken with 6.10.0? the vm logs did not report an error, and I remember this to work greatly with 6.9.2? i have tested the vnc connect with an existing vm of mine, which does not connect anymore with

I've been seeing near constant disk activity since last night. I opened the logs and noticed the following line over and over again: unRAID flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update I disabled flash backups and things seem to have gone back to normal. unraid-diagnostics-20220812-0902.zip

I have an unraid install that I set up with 6.9.x and when I did I set up a VM and the vnc worked as it should. I don't access the VNC Much of at all but when trying to recently (after upgrading to 6.10.2 then 6.10.3) VNC fails to connect.   In the VM the VNC is set to "vnc:auto" and when started displays "vnc:5900" but when I try to access the vnc viewer the weblink says "10.10.1.250/plugins/dynamix.vm.manager/vnc.html?v=1640104829&autoconnect=true&host=10.10.1.250&port=&a

Hi  After an upgrade my windows 10 VM is acting very strangley. It does start but it starts in low res mode and I get no sound and cannot change the resolution (its greyed out entirely).   Attached are the diagnostics for my machine after I reverted back to 6.9.2. I can attempty the upgrade again and run the diagnostics on the 6.10.2 version is you prefer? ironside-diagnostics-20220601-1746.zip

Same problem on 6.10.3 pallas-diagnostics-20220805-2255.zip

In 6.10.1+ the dockerman icon caching mechanism does not work correctly for icons specified by the net.unraid.docker.icon container label on containers without a dockerman template.    For containers created with this label outside of dockerman the caching mechanism initially downloads and displays the correct icon. If the icon url is changed however the new icon is never downloaded because the old icon remains cached and there is no mechanism in place for invalidating the icon in the

After installing Intel GPU drive, win 11 failed to start.   I also try unraid 6.11.0-rc2 but still got the same errors.   tower-diagnostics-20220805-1054.zip

I had a Win10 VM working with a disk capacity set to 80G. I tried increasing it to 180G through the webGUI (by clicking the VM name and modifying the Capacity value) but accidentally typed 1800G (an extra 0) and hit enter. It refreshed the page and showed 2T and I cannot change it anymore. No matter what I type there, whenever I press enter it changes back to 2T. Tried rebooting but no dice. My VM will run, and Windows simply sees the extra 1.7T unallocated space in Disk Manager, but I still nee

Hello !  Sorry to busy with that but with the laster version of UnraidOS i have seen that in my docker, pterodactyl-panel the ram / cpu where not updatin, after some search I found the issue of this and it's the docker version used in UnraidOS. DockerVersion of unraid 6.9.2 DockerVersion of unraid 6.10.2  the issue is that *from what i have understand*  is not really good with that version, from what i have seen an update of the version of docker to 20.10.16-3 fix it.

If an error is made in the Extra Parameters setting when configuring a Docker container, the container is not added to the list of containers. If an error is made when editing this setting for an existing container, the container is removed from the list of installed containers and the user configuration is lost. There is no warning or confirmation before this happens.   To reproduce:   Install the GitLab CE container and start it. Edit the container settings.

Hi, i want tell you a bug in VMs.   On my old machine 6.9.2 it works with this config: Windows10, i440fx.5.1, SeaBios, HyperV ON, USB3 QEMU XHCI, Dedicated GTX770 with modified rom. Works very well.   On 6.10.3 i cant create a NEW machine with exact this settings! The dedicated GPU gives no output. But it works with VNC Remote.   So there seems to be a fundamental problem with SeaBios and dedicated graphics cards now. If I use OVMF, the other settings don't mat

I've been running Unraid in the same configuration for over 2 years, it's been rock solid. Since I updated to 6.10.x I've experience 2 system crashes where I can't login, neither through web interface or ssh. Most systems are down, SMB, some dockers (pi-hole), while a few keep running, partly (plex).   The first crash happened during a monthly scheduled parity check, the second happened just last night. I've been force to hardware reset and ofcourse a new parity check will start.

A little background, when I was on 6.9.2 I had no problems, uptime was 90+days no issues, i decide to upgrade to 6.10.1 and the problems start, after this downgrade to 6.9.2 but sometime the server just was unreachable and only manual restart do the thing. Now with 6.10.3, after 6+ days he do the same thing with attached log: First im not sure what cause the problem, i see the erros in the log and asap click on diagnostic and system hang... But I copy actual syslog to the clipbord and will

Since upgrading from 6.9 to 6.10.3, I'm getting errors for a logrotation:   keyword 'size' not properly separated, found 0x3d   My configuration for my job is:   /var/log/foobar/debug.log { su root root size=1M rotate 5 notifempty missingok }   Looking into this, the problem is with logrotation 3.18.1 which is in Unraid 6.10.3: https://www.linuxquestions.org/questions/showthread.php?p=6253137    

6.10.3   while I am going to /Settings/SyslogSettings, the WebUI lost responsive and stuck, open the webUI in a new tab/browser also stuck   workaround:  start webUI in a private window homelab-diagnostics-20220717-1101.zipmaybe after couple minutes

I recently Shrank the amount of disk in my array but increased the capacity of the array (more TB with fewer disks).   During this transition, I used unBalance to move everything off the drives that I intended to remove from the array.  After moving all the files off the drives, I specifically included "disk 3" for every share.  After having the disks empty I Replaced one with a higher capacity, and in a separate process I removed one (then used the "New Config" tool).     Th

Hi,   I've been using unraid since the previous stable version (6.9) where that issue was already present, can't talk about before.   Regularly unraid will tell me there's an update available for some containers, but uppon clicking on `apply update` it won't actually pull anything and just re-creates the container. Usually it then goes to 'up to date' afterwards, until I click the check update button again. It doesn't do it on every container and not every time, it seems

I have an old game which contains a file ._Darkplaces.icns I cannot copy this file to my unraid share, because the file starts with   ._ I created a ._test.txt file, which is empty. Same problem. So I am pretty sure, the filename is the problem.   I am copying from Windows 10 64 bit (german) to the unraid share.   unraid-diagnostics-20220628-1315.zip

syslog is getting spammed with the following warning:   kernel: Spectre V2 : WARNING: Unprivileged eBPF is enabled with eIBRS on, data leaks possible via Spectre v2 BHB attacks!   This isn't limited to Unraid, it's a kernel issue which could potentially be mitigated in Unraid? https://www.reddit.com/r/openSUSE/comments/tnxbi9/warning_unprivileged_ebpf_is_enabled_with_eibrs/ https://www.phoronix.com/scan.php?page=news_item&px=Spectre-BHI-Linux-Mitigation https:/

I have found by navigating to "Users > root > SSH authorized keys" and entering an ed25519 key the UI will present a message saying "Syntax of the key is incorrect". I dug into the frontend and found the javascript function that is being used to check the validity of keys entered into this field and it looks like it only allows rsa and ecdsa keys. ed25519 is somewhat new, but is supported in the version of openssh (8.8) included in unRAID 6.10.3. SSH key pairs using security keys (ex: yubi

Update from 6.9.2 fails permanently.   - intel_iommu=on iommu=pt did not work for me, but changed the error massage from bzimage checksum error to bzroot checksum error - intel_iommu=off did not work, too    What we tried until now: - Updated all plugins, OS Update Check from Fix common problems was OK - Updated within GUI  - Restart: --> bzimages checksum error - copied bz* files inlcuding crc files from the 6.10.1 zip to the USB -> bzimages ch

Linux EVERSTORE 5.10.28-Unraid #1 SMP Wed Apr 7 08:23:18 PDT 2021 x86_64 Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz GenuineIntel GNU/Linux   Just upgraded to 6.9.2 from 6.8.3 and it seems that the new kernel has a different way of organizing the /proc/mdstat for disk information. I use node-exporter and prometheus+grafana for monitoring and the node-exporter is complaining that it can't parse the /proc/mdstat anymore, so I get no disk information in my prometheus.   Error from n

There's a difference between Autostart on Docker Container page and Autostart on VM page.   Consider a stopped array: Some Docker Containers are marked with Autostart and some VMs are marked with Autostart.   Now start the array: The Docker Containers marked with Autostart will start. The VMs marked with Autostart will NOT start.