Stable Releases
Bug reports for stable releases.
2506 reports in this category
-
Previous use unRAID 6.9.2, everything works normally, try to upgrade to 7.0 Stable, the Broadcom HBA 9500-16i which uses the mpt3sas driver was failed to initialize, and the error message is as follows: [ 18.699192] mpt3sas version 43.100.00.00 loaded [ 18.708419] mpt3sas_cm0: 63 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (131798868 kB) [ 41.546420] mpt3sas_cm0: _base_spin_on_doorbell_int: failed due to timeout count(10000), int_status(c0000000)! [ 41.546482] mpt3sas_cm0: doorbel
- Annoyance
- 1365 views
-
Noticed I hadn't updated for a while, seen 7.1.4 was available followed the on-screen prompts. When the WEBUI was available noticed all drives in array had the above error. I would really appreciate help getting this back up and running ASAP I don't want to try and tinker and make it worse! unraid-7.1.4.txt domain.cfg nvme.cfg downvme.cfg docker.cfg i915.conf editor.cfg super.dat ident.cfg network.cfg go.txt disk.cfg listen.txt ST18000NM001J-2TV113_ZR59A5XV-2025-02-25 disk1 (sdb).
- Solved
- Urgent
- 233 views
-
Attempted upgrades from 6.12.14 to 7.0.1 and 7.1.3. Both resulted in my array not recognizing the HDDs connected through a HBA LSI 9201-16i in IT Mode. Downgrade OS works for now as a solution, but I am worried the gap will become too great between versions that I will not be able to revert to save my data. superdrive-diagnostics-20250615_2335.zip
- Annoyance
- 241 views
-
The Update OS link in Tools is broken when using Brave Browser (see attached images). Updating is possible through the Downgrade OS link though. This has been reproduced with multiple NAS'. It works fine for through Firefox on the same machine.
- Annoyance
- 164 views
-
There might be more but this is certainly a case that stands out where the text input has the same colour as the background and makes searching a pita
- Solved
- Annoyance
- 440 views
-
hello, since the update my docker container dont start anymore. i can see those errors in the log May 6 01:01:53 Unraid-Server rc.docker: mariadb: Error response from daemon: network br0 not found May 6 01:01:53 Unraid-Server rc.docker: Error: failed to start containers: mariadb May 6 01:01:53 Unraid-Server rc.docker: nextcloud: Error response from daemon: network br0 not found May 6 01:01:53 Unraid-Server rc.docker: Error: failed to start containers: nextcloud i had t
- Minor
- 11995 views
-
Description: On my Unraid server (version 6.12.4), the Web UI incorrectly DISPLAYS the eth0 interface as using the iwlwifi driver, even though the CORRECT DRIVER IS IN USE ( ixgbe). Here’s the breakdown of the actual interface-driver mappings confirmed via ethtool -i: ``` eth0 — ixgbe — PCI 0000:09:00.0 eth1 — ixgbe — PCI 0000:09:00.1 eth2 — igc — PCI 0000:07:00.0 ``` However, the Network Settings page shows: ``` Interface eth0: PCI device 0x8086:0x2725 (iwlwifi) ← Incorrect ``` The I
- Retest
- Annoyance
- 286 views
-
I thought I was able to fix the issue but just moving everything from that disk, then reformatting it. It worked then when i brought the array offline it was saying the disk was too small again. It is absolutely the same. I even reformatted it to a different file system to see if that mattered. I thought everything was fine. This all happened after the recent upgrades. I have been a Plus member for years and never had this issue. fischershomelab-diagnostics-20250612-0608.zip
- Solved
- Annoyance
- 363 views
-
I am using an old HP Blade Server to host one of my UnRaid servers, however there are two drives in a pool which are enterprise SSD's that do not support TRIM. (Mostly due to the HBA in IT Mode not supporting Trim). I have Trim disabled on the pool "Autotrim off" and disabled in the scheduler. When running grep on the btrfs pool, I can confirm "discard=async" is provided in the mount point. root@DreamRuby:~# mount | grep btrfs /dev/sdb1 on /mnt/data type btrfs (rw,noatime,ssd,discard=async,
- Solved
- Minor
- 2261 views
-
every day my serv crash in 7.1.4, i have try to find the problem but i didn't find anything when i downgrade the system seem stable until i boot vm like windows or linux except for homeassistant have a nice day 🖤💜 raillineserv-diagnostics-20250703_2256.zip
- Solved
- Minor
- 522 views
-
I am facing the following issue. After refreshing my Unraid USB drive to version 7.1.4, I configured a VLAN in network settings. While the VLAN subnet appears in Docker settings, the custom network is unavailable for selection when creating Docker containers.
- Solved
- 421 views
-
Since two days most of my containers stopped working. They show a "Waiting for stream" message - forever. I wrote this in a thread of one of my containers without a response. But now, with nearly all containers failing, I think this might be a generic problem. Currently I dropped my docker containers and I installed the corresponding apps on my Windows laptop. But this can't be the solution. What's happening here? tower-diagnostics-20250729-0755.zip
- Closed
- 567 views
-
It's kind of impossible for me to attach a syslog here because I already downgraded to 7.1.3 and that resolved my issue so far. I noticed all of the sudden I was getting really really abysmal SMB speeds. I could not figure it out for the life of me. I finally downgraded to 7.1.3 and all of a sudden it is so much better. Please let me know if there's any information that I can provide, although I'm not sure a syslog would help because I'm not willing to upgrade again and break my SMB performance
- Minor
- 283 views
-
After upgrading from 7.0.1, I'm no longer seeing my Intel Arc gpu in the plugin or in my docker containers. It looks like it is showing in system devices so maybe this is an issue with the plugin? tower-diagnostics-20250725_0918.zip
- Closed
- 739 views
-
After installing the latest CA update the screen hangs for a few seconds and this window pops up. Tried 2 different servers and it happens on both. It eventually goes away after a few seconds.
- Closed
- 147 views
-
I have been using && docker network connect proxynet traefik in the docker "Post Arguments" field to connect my traefik container to an additional docker network after it is booted. It has been working great since forever. Since enabling tailscale on the container, I notice the docker run command sets this as an environment variable for the container With tailscale disabled this is the output from the update container screen: docker run -d --name='traefik' --net='br0.11' --ip='
- Solved
- Minor
- 1487 views
-
Installed 7.1.4 a couple weeks back. Server's been acting up a little, so I gave it a shut down and reboot. Now, even after multiple reboots, it comes back up with ZERO drives in the main pool area! Those drives are showing up in sys-devices tho... I have 2 PCiE SAS (external drives) cards and onboard SAS on this setup, and none of them are showing their drives on reboot. The only drives that are showing are the SSD's on a PCiE and onboard SATA port. Once i remove a video card things work aga
- Urgent
- 190 views
-
Share "backup". 1TB cache drive + 10TB HDD. Set min free to 500 GB > Size set is 285.5 GB. I can go a little above this, but around 380 GB or so, it'll revert to 285.5 GB. Nothing super in the logs, just: Jul 22 21:41:59 backup emhttpd: Starting services... Jul 22 21:41:59 backup emhttpd: shcmd (534): /etc/rc.d/rc.samba reload Jul 22 21:41:59 backup emhttpd: shcmd (537): exportfs -ra Jul 22 21:41:59 backup emhttpd: shcmd (539): /etc/rc.d/rc.avahidaemon reload It's quite irritating because It
- Solved
- Minor
- 374 views
-
Hello forgive my English, it only works with a translator. I have been struggling with the same problem for some time. I use Unraid 7.0.1 and everything works. I use a VM with Homeassistant. System is originally haos_ova-10.5.qcow2. After an update of Unraid the GUI page VM was not accessible and the VM does not start. Today I have reinstalled the VM from HA with the version haos_ova-16.0.qcow2. Unfortunately, the behavior of UnRaid is the same: First the GUI is accessible. all dockers are runni
- Minor
- 256 views
-
/var/log on my server filled up and was full for quite a while and I didn't know the only way I found out was some obscure errors from cron.daily trying to rotate logs and erroring because it was full can we have unraid monitor and warn about all mounted partitions the same as it does for arrays/mounts/shares ? I'm using 6.12.15 so maybe this has been solved in 7.x but I don't recall reading anything about that in the release notes
- Minor
- 112 views
-
From what I can see potentially only one of these are container templates with the rest appearing to be plugins. Since these plugin templates were merged into the repo they now appear in the Select a Template drop down under Docker.
- Annoyance
- 296 views
-
I am using UNRAID since two days and this is really an awesome product - I'm still in my trial period but on the verge of buying the license. Good job. If I'm very new to unraid, I a long time unix/linux user so I think this following is really an issue. I use F6-424MAX Terramaster with a dual disk docking station (most likely this is not dependent on the device, but report have to be as precise as possible, don't they ?) https://www.amazon.fr/dp/B0C2GKJ6ZJ?ref=fed_asin_title&th=1 I use tw
- Closed
- Minor
- 174 views
-
I'm running the WebUI on port 8080, but I believe this happens on any port including the default port 80. This is a fresh install. When accessing the WebUI using the hostname, the connection is redirected automatically to the configured startup page. However, when accessing using the IP address the redirect fails and results in a 404: http://NAS:8080 -> works fine, redirects to http://NAS:8080/Dashboard http://192.168.1.66:8080 -> redirect results in a 404 on http://192.168.1.66:8080/redi
- Closed
- 284 views
-
I recently upgraded to unRAID 7.0.1 and I had a bug where drives and GPU Ids keeps changing please see to this titan-diagnostics-20250720_0241.zip
- Urgent
- 251 views
-
I'm on 7.1.4 but I don't think this issue is new to this version, hoopster noticed it a little over a year ago. I have a general support thread about this but wasn't sure how much the dev's looked at those vs the bug reports here. Myself and others have been manually editing our /config/syslog.cfg & syslog.conf files to log to an unassigned device/pool/whatever instead of the default share only behavior in the webui. This was acknowledged as possible in a couple threads (here for example) b
- Annoyance
- 298 views
