Stable Releases
Bug reports for stable releases.
2506 reports in this category
-
Hello, Aug 3 18:18:18 Dunkin php-fpm[10040]: [WARNING] [pool www] child 4710 exited on signal 9 (SIGKILL) after 246.847517 seconds from start Aug 3 18:18:20 Dunkin php-fpm[10040]: [WARNING] [pool www] child 10288 exited on signal 9 (SIGKILL) after 209.727298 seconds from start Aug 3 18:19:31 Dunkin php-fpm[10040]: [WARNING] [pool www] child 7051 exited on signal 9 (SIGKILL) after 304.937449 seconds from start I have been having this problem since 6.12.3 (updated from 6.11).
- Annoyance
- 1754 views
-
Having two containers with network type set to "None" becase they route via another container. For both containers I have deleted all port mapprings and set network type to none. I have added --net=container:containername to extra config. When opening Docker tab and looking at my two specially routed countainers i expect the field for PORT MAPPINGS should be blank. They are not blank. Showing radom data that comes from my stopped mariadb-instance (for now
- Minor
- 661 views
-
The USB Flash Creator stops with an error if it is run under an account name that has some kind of special characters in it. In the example in the picture, it is the character "å" in the username Håkan that causes the error. Using an alternative account with the username Hakan instead, the USB Flash Creator works just fine. Discussed since 2018: https://forums.unraid.net/topic/76084-usb-flash-creator-on-windows-10-error
- Minor
- 588 views
-
Added 1TB drive June 24. Disk-clear in parity check log. All ok. Monthly parity check ran at midnight until early morning today. Everything ok but the notification in GUI and Join show the stats from the disk-clear. The check before this one. Wrong duration here too Shows up correct in log/history/gui I don't know if this has happened before because I haven't added any drive in years and all parity checks have
- Minor
- 808 views
-
I've been using a JMB585 SATA controller to connect my two hard drives to my Unraid system for a long time. After updating to 6.12.3, my system can't recognize these two drives anymore. I found that the native SATA ports on the motherboard can recognize the drives, so I suspect it's a driver issue.
- Minor
- 2341 views
-
Since updating to 6.12.3, docker containers are randomly shutting down. Reviewing the docker logs, I see SIGTERM received. This is happening on a few containers. I've switched from macvlan to ipvlan as recommended, but not sure why this is happening or how to resolve. Attached diagnostics as well. Appreciate any insight to figure out the cause and fix. RADARR was the last container this happened to and here is the excerpt from the log for reference: 2023-08-02 06:48:40
- Minor
- 1856 views
-
After 2 drives dropped offline, a segfault occured in emhttpd which resulted in inaccurate health and status displays on the dashboard, and aslo the nightly health report email to erroneously report that the array was healthy. No indication from the server that anything was wrong, save for the entries in the syslog which I happened to read by chance. When this happened back on 6.11.1 during a parity re-build, the correct FAIL email was sent so I'm not sure if this is specific to 6.12
- Urgent
- 357 views
-
Seems that nobody expected that somebody is not interested in Unraid Update notifications I'm on 6.11.5 and will stick with that for a while (MACVLAN/IPVLAN, German User, Fritzbox, ...). So if the logic for the notification does exist in 6.12.x as well, somebody should check that: I changed the settings to "Once a month" and kept the notifications as shown in the screenshot. I applied that on all my three Unraid servers. On all Unraid servers the update banner returns daily ...
- Minor
- 348 views
-
Hi Everybody, i posted here in the german forum. after update to 6.12.3 my mashine was fully loaded... need extreme long to login / do something. also after deactivating docker / vm modul. i switched back to 6.11.5 and now it worked again.. if you need some further information, PM me
- Urgent
- 476 views
-
We have recently upgraded our server hardware to a Ryzen 9 7900 and since then we are having almost daily lock ups with no known cause. We have disabled global c-state controls and changed the power supply idle controls to "Typical" as advised. The Web UI and all dockers and VM's crash and become unavailable, and while the console command line is available, no command actually works (at least in a reasonable time frame). See attached the log file. A diagnostic file could not be created before th
- Urgent
- 593 views
-
the blue bootloader screen in unraid it's just looping around oading /bzimage. . . failed: No such file or directory
- Closed
- 684 views
-
Hi all, I am running unraid on a Dell T40 for more that 2 years now. It was rock solid with no issues. Since some weeks, and I think after I have upgraded to OS version 6.12.3 the server crashes every day. I have no possibility to access the webinterface anymore. Also no other services, like docker containers are available anymore. What can I do to analyze the issue. Logs are cleaned after the reboot, so I cannot figure out what causes the crash As I can read in serveral
- Urgent
- 597 views
-
- 550 views
-
Hi there, I recently changed my cache drive from btrfs to zfs, and now when I try and stop the array, it gets stuck trying to unmount the disk shares. If I try and shutdown the array, it has to force a shutdown. I have this in the syslog: Jul 12 20:10:33 Percy emhttpd: Unmounting disks... Jul 12 20:10:33 Percy emhttpd: shcmd (267285): /usr/sbin/zpool export cache Jul 12 20:10:33 Percy root: cannot unmount '/mnt/cache/appdata': pool or dataset is busy Jul 12 20:10:33 Percy emhtt
- Solved
- Minor
- 4229 views
-
It seems that, compared to 6.11.5 Docker is using more RAM overall. Looking at last 7 days it hovers around 2GB, after installing 6.12.1 and rebooting it jumped to 6GB, after that I had to manually restart each container and now it hovers around 3GB. Taking a closer look at the last 12 hours We can clearly see a jump in RAM usage and a point where I restarted the containers. Overall usage is just higher compared to docker version in 6.11.5. fla
- Minor
- 4569 views
-
Hi! After updating to 6.12 my Unraid won't turn off my UPS anymore. It had been worked like a charm since 6.9 (and later) and stopped worked after update to 6.12. I'm using embed APCUPSD and Shut Down UPS option is on. My UPS is APC Smart-UPS SC1000, UNRAID can read everything properly, doing shutdown properly, but UPS stay ON.
- Minor
- 1199 views
-
Spotted this parsing error at the end of start up for some older drives in a (non-critical) pool, doesn't seem to have impacted server operation.
- Annoyance
- 638 views
-
Hi, been rock solid 6.11 and since 6.12 its stuck once a week, or since latest 6.12.1 stuck once a day... (i thought it would get better...) Jun 24 09:06:46 Unraid-Server kernel: ------------[ cut here ]------------ Jun 24 09:06:46 Unraid-Server kernel: WARNING: CPU: 6 PID: 0 at net/netfilter/nf_nat_core.c:594 nf_nat_setup_info+0x8c/0x7d1 [nf_nat] Jun 24 09:06:46 Unraid-Server kernel: Modules linked in: tcp_diag udp_diag inet_diag xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6tab
- Retest
- 5344 views
-
Increased max number of devices per pool from 30 to 60. In a future release we will eliminate the upper maximum entirely. i didn't see the increased or what step i need to do for the increase? thanks
- Closed
- 1851 views
-
Just upgraded from 6.11.1 to 6.11.2 this morning. After reboot decided to update all containers. Hmmm, looks like it just resolved itself. That was weird. There were several containers that updated up 4X and freaked me out. Everything appears stable for now. Will leave this post out here in case others run into the issue and maybe verify the odd behavior if it proves to be a bigger problem.
- Annoyance
- 2039 views
-
Server becomes unresponsive after upgrading to 6.12.3. Issue was also observed on 6.12.2 and 6.12.1 as well as 6.11 reverting to 6.10 does resolve the issue. Issue occurs with little to no server load after an 12 to 24 hours. Issue appears to be repeatable when running docker container transmission with wireguard network interface. Attached debug kernal log. 2023-07-21T23:25:52-04:00 Carbon14 kernel: mdcmd (31): set md_num_stripes 1280 2023-0
- Urgent
- 666 views
-
Hello everyone, I'm encountering a critical issue with my unRAID system, and I could really use some assistance in troubleshooting it. The problem has been causing my system to become inaccessible, and I'm getting the following error message in my logs: Jul 24 16:51:30 HOME-unRAID kernel: ------------[ cut here ]------------ Jul 24 16:51:30 HOME-unRAID kernel: WARNING: CPU: 4 PID: 12624 at net/netfilter/nf_conntrack_core.c:1210 __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Jul 24 16:5
- Minor
- 550 views
-
Under the Settings >>> Notification Settings, the 'Array Status Notification' does not have a setting for the time of day that the report will be generated. I have this report sent from both of my servers once a day. It seems like it is always sent at 00:20 each day. The problem is that I use the same E-mail server for both of my servers. If the two MB clocks are close enough in time, this apparently results the E-mail server rejecting the login request from one of
- Minor
- 709 views
-
I upgraded to 6.12.3, especially because of the in the wiki mentioned IPv6 issues and now I have another, more annoying one. If I try to start docker container with IPv6 addresses assigned to them, it will fail. I have my addresses to my IPv6 dockers assigned, Unraid showed them in the docker-settings page, and they are enabled, yet in the container Settings they are not showing up as they did with version. 6.12.2! Unraid Network Settings of the Interface Docker Se
- Minor
- 2607 views
-
Hello, I've noticed the following errors in dmesg: [Fri Jul 21 11:04:31 2023] ixgbe 0000:02:00.0: Warning firmware error detected FWSM: 0x80000000 [Fri Jul 21 11:04:33 2023] ixgbe 0000:02:00.0: Warning firmware error detected FWSM: 0x80000000 [Fri Jul 21 11:04:35 2023] ixgbe 0000:02:00.0: Warning firmware error detected FWSM: 0x80000000 [Fri Jul 21 11:04:37 2023] ixgbe 0000:02:00.0: Warning firmware error detected FWSM: 0x80000000 [Fri Jul 21 11:04:39 2023] ixgbe 0000:02:00.0: Warning fi
- Minor
- 648 views
