Stable Releases
Bug reports for stable releases.
2506 reports in this category
-
Please see post for more information. Sometimes the update dialog will be blank and not show the current progress (like Docker pulling the new image, etc.) In the console, the following error is logged: 11:00:27.506 Uncaught TypeError: progress_span[data[1]] is null progress_dots[data[1]]< https://dipper:1443/Docker:1494 setInterval handler* https://dipper:1443/Docker:1494 emit https://dipper:1443/webGui/javascript/dynamix.js?v=1700087630:15 onmessa
- Minor
- 360 views
-
Hello there, I would like to ask You for a help with my problem. Well since I do not move, or upgrade my files on array drives (downloading on a large cacheSSD) my parity disk is off practically all the time. BUT every night, exactly at midnight Parity drive powers on. There are no files written on it (according to) : so HOW can I manage to find the docker? plugin? source of this power on of this disk if its completely unneeded? Here is the log of parity drive;
- Closed
- 434 views
-
After update to 6.12.5 I got this message asking me to visit the Support Forum. I'm not really sure if only visiting the Forum will avoid plugin issues, but I'm willing to give it a go. What is the cure here? helmaxx-diagnostics-20231130-1811.zip
- Closed
- 437 views
-
So I had posted another thread about after a kernel panic, docker host access to custom networks doesn't work until docker is stopped/restarted on 6.9.0 After further investigation and setting up syslogging, it apperas that it may actually be that host access that's CAUSING the kernel panic? EDIT: 3/16 - I guess I needed to create a VLAN for my dockers with static IPs, so far that's working, so it's probably not HOST access causing the issue, but rather br0 static IPs b
- Urgent
- 44794 views
-
When updated to 6.12.5, my network interface bond to a RTL-8125 2.5G was down. I checked the cable, but is good. I restored to 6.12.4, and it worked again. Just report it here.
- Solved
- Minor
- 788 views
-
Hello all, Today, I finally updated from 6.9.2 to 6.11.5. After updating, redis failed to start. When I attempted to start it, I got this message in the logs. mkdir: cannot create directory '/bitnami/redis/data': Permission denied As a result, Authelia won't start and most of my services are unreachable. I can't find a concise way to fix this problem. Any advice? Thanks! mccoyserver-diagnostics-20221217-2157.zip
- Urgent
- 4156 views
-
It's been like this for half a year or more, I've tried switching avatars several times, doesn't seem to do anything. Always pointing at https://forums.unraid.net/uploads/monthly_2020_10/2062585464_hammyhavocavatar500px.png.f0e358b64eb3efa3f1bcd275ff8233dc.png
- Minor
- 436 views
-
when i thought it was a good idea to put my cache drives as mirrored in zfs i encounted an issue with vms and passthough and the libvirt.img keeps crashing and it looks like this and by swiching it back to the normal arry it works fine but slow Nov 27 00:41:35 Tower kernel: BTRFS info (device loop4): using free space tree Nov 27 00:41:35 Tower kernel: BTRFS info (device loop4): checking UUID tree Nov 27 00:41:35 Tower root: initializing /etc/libvirt Nov 27 00:4
- Closed
- 833 views
-
I've been running into a bug with updating dockers on 6.12.3 recently where I'll have a few containers that have updates and when I go to "Update all" and it launches the popup it will go through and update everything but then continue to loop through the containers over and over again attempting to update. So the first pass, things update, then the second pass it doesn't find any new updates to pull for the container: "Status: Image is up to date for {containerName} TOTAL DATA PULLED:
- Minor
- 3200 views
-
Hi, Upgraded from 6.12.3 and having issues with my dockers using custom ipv6 addresses. I'm getting this error: docker: Error response from daemon: user specified IP address is supported only when connecting to networks with user configured subnets. These are the settings which worked fine on 16.12.3: docker run -d --name='binhex-sabnzbd' --net='br0' --ip='192.168.93.193' --ip6='2a02:restofip' -e TZ="Europe/Londo
- Urgent
- 4936 views
-
I'm using a couple of Docker containers with docker-compose on my system. One of the stacks is for my web-services (nginx, nextcloud, wordpress) but the exact containers don't really matter. I use docker-compose though a docker-container (docker/compose:latest). The problem I have is, that the "Check for Updates" in the Unraid WebUI only works once for those containers. After creation it'll show "up-to-date" just fine, but after detecting an update once, it'll ne
- Annoyance
- 3724 views
-
I've noticed that during zfs replication from nvme drive plugged into the motherboard to sata hdd connected via LSI 2907 sas controller, the gui dashboard always show one cpu core loaded 100% during the entire replication. On the other hand, htop is showing minimal cpu load. Snapshot attached. hyperx-diagnostics-20231122-2110.zip
- Closed
- 579 views
-
Starting with 6.12.4 update_cron is no longer running during system start in a virtualized environment (Unraid VM). This worked until 6.11.5. Not running update_cron has impact on the User Scripts plugin that relies on that tool to add it's "Custom schedules" to "/etc/cron.d/root". So a scripts with "Custom schedules" attached, no longer runs from within the User Scripts plugin. One can work around this by calling update_cron manually after system start to add these missi
- Minor
- 3142 views
-
I have a ZFS cache pool with two mirrored SSDs. Initially, everything worked fine, but after a few hours, the second drive stopped showing any temperatures. Upon further investigation, I discovered that the SMART attributes failed to load, and the ZFS pool was in a "DEGRADED" state. While I am still investigating the issue with the drive itself (likely just a cable problem), my concern here is that the UI did not inform me about any issues with my cache pool. Besides not display
- Minor
- 656 views
-
Accidentally discovered Normally it is like PIC1 Then when hover the pointer above the Bars and swing it around... PIC2 it is - possibly the query rate of exact memory amount that lead to the problem - And I would really need a function of managing Memories of Unraid OS in the following 6.12 versions, thanks bro
- Annoyance
- 2465 views
-
Originally reported as 6.12.3, still occurs on 6.12.4. As the title indicates, mousing over the RAM percentages (such that is shows the absolute size) can spike your CPU quite high. On hover of the RAM percentage, it fires of a POST request to /webGui/include/DashboardApps.php Just doing this once probably won't be noticeable. However if you constantly mouse over these, it'll spike your CPU quite high, for me it almost pegs to 100%. Reproduction:
- Minor
- 918 views
-
Hello! I have a situation where I am using a trial key during my exchange with support to get my key replaced. You can see that it says "Trial Key Expires in 29 days 6 hours 25 Minutes". However, when support identified the correct Key install file and I installed it -- there was an issue that required more support. Normal behavior for bad keys is shown, all is well except Unraid still acknowledges that I have a trial key active, bu
- Minor
- 806 views
-
Booted up into GUI mode today to try and fix something. Noticed no option to shutdown the server or reboot. Only log out to a menu showing 'username'. I know you can trigger shutdown with a press of the power button but a noob might not know that. Please can we add a button to do this from the login menu. Thanks.
- Closed
- 2031 views
-
So this just happened. I stopped the array to make some new pools. Upon stop, i noticed my parity drive assignment had reverted back to the old 4TB parity disk that i had replaced, with a 6TB (SAS), a couple weeks back. I had just left the old 4TB in the drive bay, meaning to clear it later. When i tried to put the 6TB (current) drive back, it shows "All existing data ...will be overwritten" on the parity slot, but the 4TB (old) drive shows parity is ok (and i know it is not). As a
- Annoyance
- 410 views
-
Once every few months, my unraid server's settings and parameters are completely changed. The strange part is that they change to a configuration that I have had before. For example, time zone changes from my actual zone (Central European Time) to Pacific time. The landing page of my server changes from the dashboard to the disk array page. FTP settings suddenly turn of. Docker auto-start is turned of, etc. These changes don't occur gradual, they happen suddenly and all at once. This
- Minor
- 633 views
-
I discovered that docker start order is not maintained even though the GUI makes it seem like it is when you delete the docker folder/vDisk. Steps to recreate. Install several containers. See they are in alphabetical order by default. Change their order. Set startup timeout so you can confirm it's working correctly. Stop all containers and stop docker service. Delete docker vdisk/folder. Restart docker service Reinstall same containers See that
- Closed
- Minor
- 1079 views
-
Hi, I woke up in the morning and found that Unraid NAS cannot respond to any requests, including SSH, SMB, WEBUI. The following is the system log I rescued (the log is written to Flash). The NAS has a screen and keyboard plugged into it. At this time, the screen does not respond (no signal), the keyboard light is on, but typing CTRL+ALT+DELETE cannot complete the restart operation. Aug 3 01:57:28 OuO avahi-daemon[15911]: Withdrawing address record for 2409:8a20:5214:4c9
- Urgent
- 3901 views
-
Re-pro steps: 1. Create a cache pool, call it nvme-docker-vms 2. configure shares: appdata and system -> set "Primary storage (for new files and folders)": nvme-docker-vms 3. Docker Configuration: Settings -> Docker -> (Advanced View) Docker data-root: directory Docker directory: /mnt/user/system/docker 3. Create and start dockers (more than 1) 4. Stop dockers 5. Go to Tools -> New Permissions ->
- Closed
- 1941 views
-
The problem is fairly self-explanatory. VMs can ping other devices (including the server), the gateway, and the internet. Diagnostics attached. LMK if you need more info. storage-diagnostics-20231027-1254.zip
- Closed
- 2600 views
-
Logged in today as its been the first time ive been free of non-work nonsense. Shut down all my VM's, did the update from 6.12.3 to 6.12.4. Upon reboot I went to the VM tab to start my VM's back up and am greeted with: "Libvirt Service failed to start." In logs I see: Oct 8 17:11:24 X root: /usr/sbin/libvirtd: error: Unable to initialize network sockets. Check /var/log/messages or run without --daemon for more info. Also: 2023-10-08 22:11:24.912+0000: 13
- Minor
- 2222 views
(Small).thumb.png.b884b0484e848c502a315fc27b995f59.png)
