Stable Releases
Bug reports for stable releases.
2506 reports in this category
-
Description: Starting Unraid 7.1.3 for the first time works, but starting a second time after first shutdown fails. The system will not boot and my motherboard displays the error code F6 (Reserved for future AMI progress codes). Attempting to start multiple times does not help. I have tried to make three unique flash disks and they all produce the same problem. I used Unraid USB Creator 1.0.1 to load Unraid 7.1.3. Booting to Windows works fine. Steps to Reproduce: Use Unraid USB Creator 1.0.1 t
- Closed
- 827 views
-
CLOUD: Socket closed none of my dockers are working, i had ti downgrade. tulipterminal-diagnostics-20250612_1059.zip
- Urgent
- 166 views
-
submitting my diagnostics in case helpful but I'm aware the problem has been reported already yannobox-diagnostics-20250611_1819.zip
- Minor
- 262 views
-
After upgrading from 7.1.2 to 7.1.3, three of my docker containers - plex, overseerr, sbnzbd - won't start. Says "execution error 403". Tried restarting docker service and whole system, to no avail. New to Unraid, and linux in general. Any help would be appreciated. Unconfirmed 921117.crdownload
- Minor
- 1258 views
-
Hello, I've recently updated to UnRAID version 7.1.0. The Server keeps crashing after i start the Array, but it seems to happen only when i try to do anything to do with Docker, otherwise the server doesn't crash. If i disable Docker and start the Array, it appears to be running smothly. If i enable docker again it almost immediately crashes. Interestinglly enough the Server was somewhat fine until a few hours ago, it only crashed if i tryed to start an Minecraft Server with the C
- Solved
- Urgent
- 1043 views
-
Recently I was adding some new drives to my system and 1 was bad... never registered with unraid that it was there and because of this the system reported that I was missing another disk in the array... after I replaced the missing disk (disk 1 or 2) the missing disk was found... no rhyme or reason as to how this happened... but it did... I have a recent support thread for this... to include logs, thankfully... I would be happy to replicate this should need be... but I dont think its safe to c
- Minor
- 149 views
-
After updating to 7.1.2 i notice this "error" message after i start the array, or rebooting unraid server. May 12 21:05:31 Tower rc.docker: Starting Docker daemon... May 12 21:05:32 Tower rc.docker: Docker daemon... Started. May 12 21:05:32 Tower rc.docker: Starting network... May 12 21:05:33 Tower root: Error response from daemon: network with name br0 already exists 7.1.1 log: May 6 08:30:07 Tower rc.docker: Docker daemon... Started. May 6 08:30:07 Tower rc.docker: Starting network...
- Solved
- Annoyance
- 601 views
-
Upgrade to 7.1.3 Dashboard only populates % space for drives but no images or data anywhere else, looks like a blank form Main is totatally blank Shares populate and work fine so seems to be upgrade issue Tried to download diagnostics and it freezes system, Downgrade back to 7.1.2 fixes it
- Urgent
- 334 views
-
Hello, Just used the new (well to me) USB Creator v1.0.1 to write a new USB stick. Download wise, not an issue. BUT writing to the USB drive is painfully slow... about 1% a minute... Its is in a USB2 port and writing to a USB2 drive but it should not be this slow.... Anyone else had an issue with this? Now I am not saying it is not my windows machine and the drive causing the issue but I have no way of know what the write speed is as it is not displayed... For a new release would it be pos
- Minor
- 443 views
-
I also posted this in a comment here but I thought I would make a new post too since I'm using a different version. Basically as I said there: I sometimes loose my shares when I am doing things in VS Code via SSH. These things are typical things like editing docker compose files and doing docker compose up etc.. Every once in a while I'll start getting errors in the terminal and when I head over to the dashboard I see my shares are gone. A reboot fixes it. I have syslog server set up, but it f
- Urgent
- 806 views
-
After I updated to 7.1.3 It would no longer show me the versions of all my Docker Containers and if I would check for updates for Plugins it would time out for Connecting and looking for updates. alliance-diagnostics-20250610_0346.zip
- 153 views
-
Up until recently, i mounted my cifs/samba shares to the host via unassigned devices. I then noticed that the docker gui was not showing the smb volumes i was mounting in my compose file. It used to, but it no longer does. Has anyone else seen this? I tried doing a top level named volume and map the the volumes per container like this: volumes: seed-volume: driver_opts: type: cifs o: username=u,password=p,uid=uid,gid=guid,vers=3.0 device: //[host]/mediaand then:
- Minor
- 237 views
-
Slightly convoluted, but effectively I did a 71.2 - > 7.1.3 upgrade and had issues with connectivity (no web ui accessible from the local network), so rolled back to 7.1.2 (using USB creator tool) and whilst I had connectivity back to the web UI, had issues with dockers Logs showed the container couldn't find the network ID All br0.x VLANs where missing in the drop down list when editing a container and 'docker network list' showed they indeed did not exist. I removed and re-added all VLAN
- Minor
- 1249 views
-
I am running 7.12 and have an old user.script left over from when nchan would kill the UI regularly. It simply runs /etc/rc.d/rc.nginx restart I have found since the 7.12 update that the nginx inside my apprise container is being stopped at the same time the nginx restart script is run. I have looked at the rc.nginx script and its being caught as line 739 pkill -f $NGINX is not checking if it is an nginx from the host OS or a container. Only my apprise container runs a nginx by full path /usr/bi
- Minor
- 1414 views
-
I have a few dockers running on br0 with their own IPs. after a reboot I lose access to the Host from these dockers. If I open the console for the docker and curl to the host it fails. I then have to stop the docker service, disable the allow host access to custom networks hit apply, enable the allow host access to custom networks again, hit apply and finally start the docker service and hit apply. then everything works beautifully. If I run curl on the host now it instantly responds
- Minor
- 13437 views
-
Have been on 7.1.2 and all previous releases with no issues. After upgrade to 7.1.3, my host and containers lost access to each other. DNS requests from unraid began failing to my pihole container, and connections from my home-assistant container began failing to reach NUT hosted by the unraid plugin. I am running a macvlan network with Host access to custom networks enabled. My containers are setup 50/50 between bridge networks and bond0 networks with static ips assigned via my unifi network.
- Minor
- 3039 views
-
Hi guys, Unraid keeps randomly losing internet connection. A reboot fixes the issue but then shortly loses internet. I've done a hard reset of my router, no difference. Any help would be appreciated. tower-diagnostics-20250605_2356.zip
- Annoyance
- 825 views
-
I'm getting server errors when attempting to start dockers, was fully functional prior to updating. reverting to older version ibm3650-diagnostics-20250506_0804.zip
- Minor
- 1329 views
-
After Updating to 7.1.1 die Memory and network usage of the system won't show anything anymore: No memory usage, network activity, no disk-status in the array - just die CPU-widget seems to work. angrynerds-diagnostics-20250509-0845.zip
- Closed
- Minor
- 414 views
-
While copying files from my disk array to my cache pool using the Unraid file manager, I found that the same file seems to be copied multiple times redundantly. This doesn't seem to happen every time, but I've witnessed it several times now while moving files to and from my cache pool and storage array. I'm also thinking this feature request is actually unintentional behavior now. This is what I did one of the times I saw this occur. I selected a directory to copy from /mnt/disk3. The directory
- Minor
- 2316 views
-
Good morning to all Yesterday I have updated from unraid 6.12.14 to 6.12.15. Over the night, I have got those e-mails. Exactly at 04:40! Only three from my five unraid server send me this e-mail. The only different between this unraid server is the plugin Unassigned Devices and Unassigned Devices Plus. The unraid server with those installed plugins are sending me an e-mail. Subject: cron for user root /usr/bin/run-parts /etc/cron.daily 1> /dev/null
- Minor
- 6738 views
-
It seems that I am able to bypass the WebUI authentication with any kind of inputs. Video is attached. Screen Recording 2025-06-05 at 9.31.22 AM.mov
- Minor
- 199 views
-
Hi, I've had a very stable UNRAID server running on 6.*.* for a long time. I finally decided to upgrade to 7+ and after upgrading to 7.1.2 I have been experiencing a lot of instability. The server will run completely fine for 1-5days and then I will experience either an unresponsive WebGUI, or ill find that my docker service has randomly failed, or even my VM service. A server restart will resolve these issues but then after another 1-5days another issue will occur. The hardware has not chang
- Solved
- Urgent
- 403 views
-
I have a single SSD in a ZFS pool - (data is ZFS rpelicated to another server, don't worry ) When upgrading from 7.0.1 to 7.1.0 the drive reports "Unmountable: Unsupported or no file system" Data is in tact when I use CLI to look at zpool status etc. I can mount it and read/write, start dockers etc zpool scrub with no issue, zpool upgrade the pool to latest as well. No luck. Unraid still reports Unmountable no matter what combo of maintenance modes I tried etc Downgrading to
- Retest
- Urgent
- 1265 views
-
Upgraded from 7.0.1 to 7.1.2 and my zfs raidz2 pool of 4xNVME shows as unmountable. Rolling back to 7.0.1 and everything is back up and running fine. Will likely stay on 7.0.1 unless there's something I can do to fix it. zimacube-diagnostics-20250520_0234.zip
- Solved
- Minor
- 1373 views
-Copy.thumb.png.53f56a5f1d1fd1d39e96c464502424d6.png)
