Stable Releases
Bug reports for stable releases.
2506 reports in this category
-
Steps to recreate Basic view only Enter VM edit on a VM with VNC already selected as the graphics option Enter password Click update button Enter VM edit Expected result: VNC password field has value and VNC connection requires password Actual result: VNC password field is empty and VNC connection does not require password Advanced view Enter VM edit on a VM with VNC already selected as the graphics option Swi
- Minor
- 2492 views
-
After upgrading to 6.12, Starting a VM with my AMD rx550 generates multiple kernel errors and a complete system freeze when the VM is shutdowned. The diagnostic logs have been pulled out after rolling back to 6.11.5 un 16 09:26:19 Dori kernel: amdgpu 0000:03:00.0: amdgpu: amdgpu: finishing device. Jun 16 09:26:19 Dori kernel: ------------[ cut here ]------------ Jun 16 09:26:19 Dori kernel: WARNING: CPU: 1 PID: 6612 at drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c:656 amdgpu_irq
- Urgent
- 1444 views
-
[BACKGROUND:] I would call this an edge-case, and just annoyance level of a bug - however I found this to be very annoying when caught in it. The Unraid webui, TOWER/Docker/, can be thrown into a refresh-loop - causing a number of page functions to stop working, or greyed-out, while the UI waits for the loop/task to stop. This was found trying to setup a VPN-client container and pointing a Torrent client container to the VPN container. [ISSUE:] When a Docker container fai
- Annoyance
- 1835 views
-
Hi there. I had to reboot my server recently, and I received a `Possible Hack Attempt` notification from a plugin called `Fix Common Problems'. Looking into this, I think I've found a bug/security issue. The server's SSH port should be configured to port `1122`. However while the system is booting up, SSH is started before the set configuration is read, leading to port 22 being exposed. Now, I have port 22 forwarded to the server for a service running `Forgejo`, a code repo
- Urgent
- 2093 views
-
Good day everybody. I have a strange problem with Unraid. I can't restart the system. My system can only boot cold. When you restart, a black screen appears immediately after the Bios (ASUS) logo and nothing else happens. The system can then be restarted via reset and the same thing happens. A "cold start" via the power button also produces the same result. Only when I turn off the system, unplug and plug it back in everything works normall
- Closed
- 1259 views
-
This is a fairly simple issue. Mover will not move a file between the cache and array or vice versa if the file or directory ends with a space character. Replication is simple, create a file that ends with a space, adjust the share so it will want to move the file between the array and cache and then run mover. The file will be left behind while everything else will move.
- Minor
- 642 views
-
despite putting --no-healthchecks being added to the containers advanced settings I am still having to restart Plex so many times a day to get it working for 5 or 10 min the cache pool is on ZFS and these issues have started since converting to ZFS on 6.12.2 and persist in 6.12.3 whats going on please help. this is driving me crazy as I am out and about and have to remote in to restart it when family and friends tell me it is not working again docker logs for plex are useless a
- Minor
- 3368 views
-
Hi there, it seems like there might be a bug with the wireguard integration in unraid. I read below that the routes for br0 access will automatically be created. Thus I should be able to connect from wireguard to unraid br0 docker container. And I am able to do that. Until I restart my machine. After restarting my machine all docker containers including my nginx proxy manager are booting up again. But after the npm docker container started, it has the
- Minor
- 1382 views
-
had to kill nginx and start it again endurance-diagnostics-20230719-2046.zip
- Minor
- 353 views
-
I've upgraded Unraid OS from 6.12.0 to 6.12.1 and after upgrade I couldn't start the array because of the unregistered USB GUID, even though it matched the registered GUID exactly. Downgrading back to 6.12.0 worked and my array started normally. tower-diagnostics-20230621-1019.zip
- Closed
- 1495 views
-
Hello, I'm trying to create a new shared folder and it's impossible. I return to the shared folder creation page (which is empty of any information) and the folder is not created. Anyone have this bug in version 6.12.2 ? Tanks for helping
- Solved
- Urgent
- 1642 views
-
From my understanding, a dataset should be automatically created if a share is set to cache only, and the cache is zfs. I have created (manually) datasets for each of my appdata, isos, system, and domains shares. I used rsync to move the data from the folders into the datasets. I create a new share called Test and set it to cache only. A new dataset appears called "Test". However, if an existing share is set to cache only and the data is moved to the cache, a dataset is n
- Annoyance
- 1861 views
-
I am currently trying to change my cache pool to zfs encrypted. I have moved all of my files off of the original btrfs file type to my array and confirmed that nothing is on the drives. I have successfully formatted the disks and they currently do not have any partition on them. When starting the array to format them, I'm met with a wrong encryption key for some of my array, which jumps to a different drive when stopping and starting the array back up. All I want to do is convert my
- Closed
- 1032 views
-
When starting the array after a restart, once you click start it will load it's configuration. Then a dialog box will appear and ask if you want to resend data. If you select okay, the array will not start. if you click cancel it will.
- Closed
- Annoyance
- 1396 views
-
After updating from 6.12.2 to 6.12.3, the server encounters frequent disconnections from the network. Using deco router to monitor when device disconnects. Received disconnects notification around 18 times within an hour. I have to downgrade the server to 6.12.2. It just fixes the problem. This version of unraid is causing this problem. I have exactly no idea what is happening. Added a diagnostics for better understanding. andromeda-diagnostics-20230717-2342.zip
- Annoyance
- 572 views
-
So I appear to be having a problem with dockers, Specifically Linuxserver ones, but they said to me it is an unRAID issue and it is "not just us." I chatted with someone from Linuxserver in private and they said it is an issue with "Update all containers." The dockers will say there is an update ready, but when updated, it does not do anything. Tried manually updating a docker, same result. gibson-diagnostics-20190829-1841.zip
- Closed
- Minor
- 24291 views
-
When assigning a different disk to the same pool without re-setting the pool, Unraid will automatically wipe the assigned disk without warning and confirmation. This leads to an unintentional wiped partition, data loss, and advanced partition recovery if lucky. This problem is too easy to do, and too disastrous. It either shouldn't be this easy to do, or ideally impossible without explicit user consent to destroy data. Context: Lost drive after creating pool (v6.12
- Minor
- 545 views
-
I have a share "SysLog", shared via samba and used for Syslog-Server. I accidentialy created a Folder "Syslog/backups" (with "l" and not "L" !) calling "mkdir -p /mnt/user/Syslog/backups" now the were two folders: "/mnt/user/SysLog" and "/mnt/user/Syslog" on disk and showen in shares-tab. Samba Server now used the new (wrong) folder "Syslog" instead of "SysLog". This seems to be a bug and should be prevented in some way. My solution was stopping all Services (Docker, VM), the I
- Closed
- 2292 views
-
Hi. I edited my conteiner variables and when i start it again i receive that error message: docker: Error response from daemon: endpoint with name DOCKER_NAME already exists in network NETWORK_NAME It not start, because they see that are other conteiner using the same name on my docker network. It only happens from >6.12, in older version that's not happens. i need manually remove my docker_name from my from Docker_network for start docker, at same docker_network. Or chan
- Minor
- 5093 views
-
Hey, my Unraid server has hung after 1 day under version 6.12.2. IPVlan was set as docker network. After a hard reboot I switched to MACVlan. Here I get a kernel error. Furthermore, the dashboard still shows me the ZFS storage at 100%. Have two pools each 2x 1 TB with (mirror). ZFS memory is allocated 8 GB. Hope you can do something with it. I go back to 6.12. There the server ran without problems! homeserver-diagnostics-20230701-1309.zip
- Minor
- 3018 views
-
I've formatted two drives of my array with ZFS by now. The web-ui is correctly showing the total size of the array. When mounting the share via SMB on Windows it doesn't include the zfs drives in the size. The 2TB of a btrfs formatted cache is added correctly to the size of the share. It's not a major issue but it could cause Windows to not accept a transfer due to insufficient space.
- Solved
- Minor
- 1286 views
-
Hi, I have built an new UNRAID ITX-System and want to use the onboard Realtek RTl8125BG network adapter because of the support of 2,5GBit/s network speed. The network adapter is recognised correctly and is using the kernel integrated r8169 driver. I have expirienced the already known problem like in the thread below: With iperf3 I am also reaching nearly the whole performance of the max. 2,5GBit/s in both directions. But If I use an SMB share and try to load an big file
- Minor
- 8102 views
-
(Just filing for info as I have downgraded to 6.11.5 and am happy) Since upgrading from 6.11.5 >> 6.12.2, the system arbitrarily locks up at least twice a day. Diagnostics and screenshot from the last lockup attached. Fix Common Problems highlighted macvlan traces, so I have followed the advice to migrate Docker from macvlan to ipvlan, this is functional but didn't stop the crashes. As this is a Ryzen system, I have double-checked all suggestions re: memor
- Urgent
- 996 views
-
Adding a second parity drive to my server and I noticed that the array is claiming it has one failed drive. This is a false notification as I'm doing a rebuild action and do not have any failed drives in the array. It would be nice if the server told me that it was rebuilding %X% drive(s) when the rebuild action is initiated. It could say one failed and one in rebuild, in the case where I replaced one but another was in the process of being rebuilt.
- Minor
- 458 views
-
Spaceinvader's custom VM icons reset with any server power cycle... The docker is a run once to download the additional icons and then never run again app. But currently overpower cycle causes the VM's icons to reset to default stock ones. https://github.com/SpaceinvaderOne/unraid_vm_icons
- Annoyance
- 470 views
