Stable Releases
Bug reports for stable releases.
2506 reports in this category
-
Errors in syslog: May 5 21:06:13 Home kernel: iwlwifi 0000:03:00.0: Start IWL Error Log Dump: May 5 21:06:13 Home kernel: iwlwifi 0000:03:00.0: Start IWL Error Log Dump: May 5 21:06:13 Home kernel: iwlwifi 0000:03:00.0: 0x03100000 | IML/ROM error/state May 5 21:06:13 Home kernel: iwlwifi 0000:03:00.0: Start IWL Error Log Dump: May 5 21:06:13 Home kernel: iwlwifi 0000:03:00.0: Start IWL Error Log Dump: May 5 21:06:13 Home kernel: iwlwifi 0000:03:00.0: 0x03100000 | IML/ROM error/st
- Minor
- 500 views
-
Server not responsive after upgrade to 7.1. Any help will be appreciated wopr-diagnostics-20250505_1314.zip
- Annoyance
- 225 views
-
After upgrading to 7.0.1 my NIC was not recognised, after some troubleshooting and running in safe mode I get the following 'Unknown header type 7f': root@Lime:~# lspci -nn | grep -i aquantia 2e:00.0 Ethernet controller [0200]: Aquantia Corp. AQtion AQC107S NBase-T/IEEE 802.3an Ethernet Controller [Atlantic 10G] [1d6a:87b1] (rev 02) root@Lime:~# lspci -vnn -s 2e:00.0 2e:00.0 Ethernet controller [0200]: Aquantia Corp. AQtion AQC107S NBase-T/IEEE 802.3an Ethernet Controller [Atlantic 10
- Urgent
- 624 views
-
Ever since upgrading to 7.0.1 the search function in the community applications does nothing. You can type in the search box but nothing happens when you commit the search. wadzserver-diagnostics-20250424_0604.zip
- Closed
- 234 views
-
In Unraid 7.0.1, the Add VM template for Debian defaults to 1G of RAM for the "minimum" value. When I tried to install, I left the minimum unchanged, and set the maximum to 24G. With Debian 12.10 (the current version) the installer will fail non-gracefully (no errors regarding memory issues displayed or in logs). See thread. To prevent others from wasting their time trying to figure it out, I'd recommend modifying the template to start with a minimum of 8GB. (A smaller amount may
- Minor
- 15911 views
-
I have 7 drives (all btrfs) in my array they all are readable and work fine in 6.12.14. After the upgrade one drive shows as unmountable. BTRFS command line utilities are unable to detect any filesystem. The array itself seems fine and healthy. Downgrading back to the older OS makes everything work again. The only error I see in the logs is: BTRFS error: device /dev/sdj1 already registered with a higher generation, found 113104 expect 125395 Note: I do not have a /dev/s
- Solved
- Minor
- 292 views
-
I have a A4 processor with 2 cores and 2 threads but dasboard only see 1 core and 2 threads. See image
- Urgent
- 234 views
-
The Dynamix File manager does not have an pre-selected target for 'remotes' for a copy from a User Share. It does present 'remotes' as a target for Disk Shares. From a remote device, It also has the option to copy to other remotes, Disks Shares and User Shares. It should be a simple matter to add this to the File Manager. EDIT: I am running version 7.0.1. No Diagnostics file attached since this problem is evident on an otherwise perfectly funct
- Retest
- Minor
- 338 views
-
I am running 7.0.1 and for the most part everything is working however over time--several days--two of my 8 CPU cores get pinged at 100% for no reason that I can think of. It's usually the same cores and the only way I can clear it, is to reboot the server. It's happened on both of my servers and it's not right away, it takes a few days. Here's my diagnostics and image. unraid2-diagnostics-20250425-0754.zip
- Minor
- 198 views
-
One 4TB disk died so I've performed the following steps to replace it: - Turned off unraid - Removed defective drive - Added new 8TB drive - Started unraid - Replaced the drive in unraid webui - Data rebuild started Now at this point it said that the filesystem needs to be formatted for the disk to be used. So I clicked, checked the box and formatted the drive. The rebuild is still ongoing however no files are visible from the "emulate
- Closed
- Urgent
- 509 views
-
I am having this issue both on MAC OS and all my kubernetes nodes are failing to list shares. Downgrading helps. unraid-diagnostics-20250407-1033.zip
- Urgent
- 262 views
-
When configuring the port options for a docker container there is field for the container-side port, only host port. This looks like a visual issue, however, it also doesn't seem to actually change the port mapping if I modify the "host" port option (container port is still passed without modification). I have attached a screenshot of the config dialog (for a pi-hole container) that used to (prior to 7.0.0 update) display fields for host and container ports. I first noticed this issue in 7.0.0 a
- Closed
- 2706 views
-
Summary: Starting a parity check on Unraid OS 7.0.1 causes an immediate kernel panic due to a crash in the raid6_avx21_gen_syndrome function (AVX2-optimized RAID6 parity code). The parity check thread exits, but the UI misleadingly shows a successful check using old cached data. Confirmed on a Ryzen Threadripper 2920X system with 2 disks (1 parity, 1 data). System Info: Unraid OS: 7.0.1 (kernel 6.6.78-Unraid) CPU: AMD Ryzen Threadripper 2920X (AVX2 supported) Mobo: G
- Minor
- 426 views
-
Can't update containers, server is sluggish. nacho-diagnostics-20250406_0434.zip
- Closed
- 528 views
-
Hi. I previously had 4x20TB HDDs in the array. Two of them were for parity. Now, according to the documentation, I've added two more 20TB HDDs to the array. Everything went smoothly and without any problems. When the two new HDDs were added, the old four HDDs were sleeping according to the display in the GUI and the power consumption also confirmed this. First, UNRAID cleared the two new HDDs (about 24 hours), and then I formatted the new ones, which took anot
- Minor
- 224 views
-
Today I needed to replace a disk in a zfs pool. I could not have the new and old disks in the system at the same time and this server does not properly hot swap disks so I: Stopped the array Unassigned the old disk Shut down the server Physically swapped disks Restarted the server Assigned the new disk to the pool Started the array The zpool did not automatically begin resilvering; I manually ran a `zpool replace` command.
- Minor
- 2198 views
-
In my setup I have two virtual NICs (one is just bound to a VLAN br0.2, the other is the main br0) and then all of my VirtioFS shares. I've found that when I set up my Windows VM and use it for a while and then need to maybe pass an additional VirtioFS share through to the VM, the main br0 NIC totally breaks and gets a 169.254 IP address. The only way I can fix it is by deleting the entire template and re-creating from scratch. It's been happening for quite a while. My full XML of the fresh VM i
- Minor
- 600 views
-
NFS3 clients go through portmapper to access nfsd. Up to unraid 6.12.10 nfsd and lockd were registered with portmapper, so nfs3 clients worked. Starting with 6.12.11 nfsd and lockmanager are not registered with portmapper, so nfs3 clients fail to mount shares from unraid nfsd. NFS4 clients to not go through portmapper to access nfsd, this is why nfs4 clients still work with 6.12.11. To be correct: after rebooting unraid 6.12.11 all necessary rpc daemons are registered with po
- 6.12.15
- Solved
- Minor
- 2878 views
-
Hey there, I use the DelugeVPN-Container in my br0 network with an own ip address (192.168.2.161) whre my unraid-host runs on 192.168.2.150. I use ipvlan in the docker settings. From time to time the Deluge-Container couldn't be reached on the port 8112 to see the GUI of Deluge. So Sonaar and Co. couldn't reaach Deluge either in that case. My solution til the next time the error occurs is: Solution: Stop all containers and vms Disable Docker and VMs f
- Minor
- 1145 views
-
- 159 views
-
All was fine, did upgrade to 7.0.1 and suddenly lots of Bluetooth errors in log: kernel: Bluetooth: hci0: Hardware error 0x0a. This flooded the log. I looked to disable Bluetooth in BIOS but no such option exists. Since I had no HW changes, I tried downgrading and all is fine again on 7.0.0. I downloaded diagnostics before doing the downgrade in case it helps. Edit: forgot to add, the scary part was unraid wanted to do a parity check for some reason after the update (despite clea
- Closed
- Urgent
- 797 views
-
Every time I reboot my unRAID 7.0.1 server, the Docker service refuses to start (see screenshot capture.png). If I go to settings, Docker, the service is set to enabled, but it isn't running (see screenshot capture2.png). I can get it to run by disabling the service and then re-enabling the service.This has been going on for awhile now but is really only a nuisance. I was hoping a future upgrade would fix it, but so far that has not happened. I have also attached a recent diagnostics dump.
- Minor
- 2119 views
-
Hi, My Unraid 7.0.1 server has been crashing every 2-3 days for the last 14 days or so after upgrading to 7.0.0 and 7.0.1. I found an old forum post about macvlan and ipvlan so I switched to ipvlan but that's not helping either. When the problem occurs, I've tried logging in through SSH and at the physical server itself. I'm able to input login name at the server, but the password prompt never shows up and the login times out. I've attached syslog and diagnostics (after f
- Solved
- 3906 views
-
Unsure if this is a Bug or if I'm the "problem" I had till date a "Big" System which was only started "on demand" wiich holds the storage (#1), and another system (Tiny - #2) for 24/7 Services like Immich, Vaultwarden etc. But somehow i thought this 2 systems (which are also a littled aged) shouldn't be necessary, so i bought a new Ugreen NAS DXP2800 which should become my 24/7 all purpose Server. Everything works on this Ugreen, though i can't fully transfer my Dockers as some of
- Solved
- Minor
- 250 views
-
This is how it looks right now on Main... And this is Dashboard at the same time: ...and to top it off, BOTH are wrong as I did a transfer from cache to disk 10 just a couple of minutes ago (and drive sleep time is set to 15 mins IIRC) and nobody touched disk 11 (which has a very specific content and I know it wasn't touched). I am on 7.01 with all latest updates.
- Minor
- 154 views
