skel2raw

So far I have not been able to resolve this issue. I have even made a factory reset and installed everything form scratch. Same result... I'll try again to remove all plugins and install them one after the other with a couple of hours running between installing each of them. But my hunch is that it might have to do something with the ZFS pool. I did not have this issue before I converted my pool to ZFS.

Thank you!

It keeps getting stranger... I have again deleted all dockers including the docker folder on the cache drive. When I try to shut down the server gets stuck again with the same message, that the "chace" drive is busy even though dockers are not running. What else can there be other than dockers that keep the chace drive busy? Might it be a zfs issue?

So... unfortunately I was not able to find out what the actual issue is. It seems that all my binhex dockers, cloudfaredtunnel, flaresolver cause this symptom. I have even completely removed two dockers and configured them from scratch but still no success. Any other ideas? I am even considering moving to a new Unraid Beta in the hope that something might be fixed that will prevent this issue from happening.

After I did what you suggested I was able to narrow the issue down to the docker service. It seems that at least one of the dockers running is causing the issue. However I have not yet figured out which one(s). However, if I manually stop all dockers the server shuts down without issues. Wondering why Unraid is not able to stop all dockers properly by itself.

Unfortunately not, even though I can stop all dockers if I try to stop the Array I get the same messages.

So I changed a couple of settings like making the appdata an exclusive share, deleting my docker folder and reinstalling all dockers and the call trace message disappeared. The only issue that is left is that unraid is not able to properly shut down and always does a parity check because of the forced shut down after the timer runs out. The repeating message is: Mar 30 23:49:42 Tower emhttpd: Unmounting disks... Mar 30 23:49:42 Tower emhttpd: shcmd (147333): /usr/sbin/zpool export -f cache Mar 30 23:49:42 Tower root: cannot export 'cache': pool is busy Mar 30 23:49:42 Tower emhttpd: shcmd (147333): exit status: 1 Mar 30 23:49:42 Tower emhttpd: Retry unmounting disk share(s)... Mar 30 23:49:47 Tower emhttpd: Unmounting disks... Mar 30 23:49:47 Tower emhttpd: shcmd (147334): /usr/sbin/zpool export -f cache Mar 30 23:49:47 Tower root: cannot export 'cache': pool is busy Mar 30 23:49:47 Tower emhttpd: shcmd (147334): exit status: 1 Mar 30 23:49:47 Tower emhttpd: Retry unmounting disk share(s)... syslog tower-diagnostics-20250330-2348.zip

Okay I seem to have found the issue for the permanently restarting docker messages. It was the immich docker which I created per docker compose. The other error messages still keep appearing. Any ideas about the other messages? Mar 29 19:35:50 Tower kernel: Freezing user space processes Mar 29 19:35:50 Tower kernel: Freezing user space processes failed after 20.004 seconds (3 tasks refusing to freeze, wq_busy=0): Mar 29 19:35:50 Tower kernel: task:dockerd state:D stack:0 pid:22831 ppid:1 flags:0x00000006 Mar 29 19:35:50 Tower kernel: Call Trace: Mar 29 19:35:50 Tower kernel: <TASK> Mar 29 19:35:50 Tower kernel: __schedule+0x667/0x6bb Mar 29 19:35:50 Tower kernel: ? super_lock+0x36/0xf0 Mar 29 19:35:50 Tower kernel: ? __pfx_zpl_test_super+0x10/0x10 [zfs] Mar 29 19:35:50 Tower kernel: ? __pfx_set_anon_super+0x10/0x10 Mar 29 19:35:50 Tower kernel: schedule+0x8e/0xc3 Mar 29 19:35:50 Tower kernel: grab_super_dead+0x88/0xc1 Mar 29 19:35:50 Tower kernel: ? __pfx_var_wake_function+0x10/0x10 Mar 29 19:35:50 Tower kernel: sget+0xcd/0x1d0 Mar 29 19:35:50 Tower kernel: zpl_mount+0xa3/0x22a [zfs] Mar 29 19:35:50 Tower kernel: legacy_get_tree+0x24/0x44 Mar 29 19:35:50 Tower kernel: vfs_get_tree+0x1e/0xa5 Mar 29 19:35:50 Tower kernel: path_mount+0x64c/0x72c Mar 29 19:35:50 Tower kernel: do_mount+0x5c/0x8f Mar 29 19:35:50 Tower kernel: __do_sys_mount+0x100/0x12e Mar 29 19:35:50 Tower kernel: do_syscall_64+0x57/0x7b Mar 29 19:35:50 Tower kernel: entry_SYSCALL_64_after_hwframe+0x78/0xe2 Mar 29 19:35:50 Tower kernel: RIP: 0033:0x2039e8e Mar 29 19:35:50 Tower kernel: RSP: 002b:000000c0039ce5b0 EFLAGS: 00000216 ORIG_RAX: 00000000000000a5 Mar 29 19:35:50 Tower kernel: RAX: ffffffffffffffda RBX: 000000c00b570e40 RCX: 0000000002039e8e Mar 29 19:35:50 Tower kernel: RDX: 000000c007b1f470 RSI: 000000c00b570ea0 RDI: 000000c00b570e40 Mar 29 19:35:50 Tower kernel: RBP: 000000c0039ce5f0 R08: 0000000000000000 R09: 0000000000000000 Mar 29 19:35:50 Tower kernel: R10: 0000000000000000 R11: 0000000000000216 R12: 0000000000000147 Mar 29 19:35:50 Tower kernel: R13: 000000c00104e000 R14: 000000c000c66340 R15: 0000000000000027 Mar 29 19:35:50 Tower kernel: </TASK> Mar 29 19:35:50 Tower kernel: task:dockerd state:D stack:0 pid:37768 ppid:1 flags:0x00000006

Thank you for the quick reply! Which log entries exactly show that? When I go to the docker tab all dockers seem to be running for 15 minutes now after my last restart.

Hi guys, I am having troubles with my Unraid server and cannot figure out what is causing the issue. I do not have anything extraordinary installed or made any big system settings chagnes. Issues that I have: - Syslog shows some error messages I cannot figure out what they mean, e.g.: Freezing user space processes failed after 20.004 seconds (3 tasks refusing to freeze, wq_busy=0) Call Trace: <TASK> __schedule+0x667/0x6bb - When I want to enter the GUI I only get a white page after the server has been running for a day or so - Every time I power down my server and boot it up afterwards Unraid starts a parity check. I have already doubled the timer for shutdown but still the same issue. Any ideas how to tackle one issue after the other? Or might they even be all related to the same root cause? Thanks! syslog

Hi guys, somehow I have managed to mess with my entire docker configuration so that I have to setup everything from scratch again. Though most stuff is simple to recover I cannot manage to recover immich. I am running - immich from imagegenius's Repository - PostgreSQL_Immich from SpaceInvaderOne's Repository The database and pictures seem all to be in place. However, when I started Immich, I had to setup Immich from scratch again and I haven't managed to restore my database. I tried following the instructions on the immich homepage but wasn't successful. Any ideas how I can restore my old database to immich?

I have the same UPS and unfortunately the same error messages. However, when I let NUT run, after a while it causes my server to hang up. The error message repeats for about half an hour before it causes my server to hang up. I added pollonly: "enabled" to the ups.conf file. Let's see if it whil help... Jan 13 13:37:00 Tower usbhid-ups[207320]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver! Jan 13 13:37:00 Tower usbhid-ups[207320]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround Jan 13 13:37:00 Tower usbhid-ups[207320]: libusb1: Could not open any HID devices: insufficient permissions on everything Jan 13 13:37:02 Tower usbhid-ups[207320]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver! Jan 13 13:37:02 Tower usbhid-ups[207320]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround Jan 13 13:37:02 Tower usbhid-ups[207320]: libusb1: Could not open any HID devices: insufficient permissions on everything Jan 13 13:37:04 Tower upsmon[207380]: Poll UPS [[email protected]] failed - Data stale Jan 13 13:37:04 Tower usbhid-ups[207320]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver! Jan 13 13:37:04 Tower usbhid-ups[207320]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround Jan 13 13:37:04 Tower usbhid-ups[207320]: libusb1: Could not open any HID devices: insufficient permissions on everything Jan 13 13:37:06 Tower usbhid-ups[207320]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver! Jan 13 13:37:06 Tower usbhid-ups[207320]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround Jan 13 13:37:06 Tower usbhid-ups[207320]: libusb1: Could not open any HID devices: insufficient permissions on everything Jan 13 13:37:08 Tower usbhid-ups[207320]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver! Jan 13 13:37:08 Tower usbhid-ups[207320]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround Jan 13 13:37:08 Tower usbhid-ups[207320]: libusb1: Could not open any HID devices: insufficient permissions on everything Jan 13 13:37:09 Tower upsmon[207380]: Poll UPS [[email protected]] failed - Data stale Jan 13 13:37:10 Tower usbhid-ups[207320]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver! Jan 13 13:37:10 Tower usbhid-ups[207320]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround Jan 13 13:37:10 Tower usbhid-ups[207320]: libusb1: Could not open any HID devices: insufficient permissions on everything Jan 13 13:37:12 Tower usbhid-ups[207320]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver! Jan 13 13:37:12 Tower usbhid-ups[207320]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround Jan 13 13:37:12 Tower usbhid-ups[207320]: libusb1: Could not open any HID devices: insufficient permissions on everything

So I removed the NUT package and also the UPS settings are disabled. My server is running without any issues again. So it seems there is some incompatiblity or wrong configuration. Any advice on how to proceed?

Froze again this morning. In the new syslo I see many errors regarding the UPS. Can the UPS be causing this issue? In fact the UPS has been the only addition to my setup in the last couple of weeks. syslog-previous_11.01.2025

Yes, it was after a crash. Both syslogs are after a crash.

Hi guys, I am having troubles with my server and hope you guys can help me figure out what the root cause: 1. Since couple of days my server hangs randomly without me doing anything. I didn't change any settings, just installed some dockers but removed them again. Sometimes my server runs for couple of hours sometimes for a day, but eventually freezes. 2. When I running unmanic with my RTX 3050 the docker runs and converts 264 files into 265 files. At the beginning unmanic ran for weeks without any issues. But now, after a couple of hours or a couple of days suddenly the RTX3050 begins spinning the fans at full speed and unraid is no longer able to find the GPU. I have removed unmanic, the drivers and reinstalled everything again. But after a couple of hours I get the same issue. Since then I am not running unmanic anymore. Do you guys have a clue what might couse this issue? Diagnostics and syslog are attached. Thank you guys!! syslog syslog-previous tower-diagnostics-20250110-2159.zip

Unfortnuately I did not figure out what exactly caused this issue. I eventually ended up creating new custom networks and avoiding br0. I also think it has to do with a recent Unraid update. Though this issue began with the binhex dockers, it was not limited to those. It also happend e.g. with the official Plex container.

Finally I moved to my new place and setup my network again. I did check the IP address issue and corrected it. The "192.168.1.0/24" IP was in the default field which I now changed accordingly to 192.168.178.0/24. Unfortunately this did not resolve the issue. In addition I now have the problem that almost all of by binhex containers (sonarr, radarr, readarr) are not bringing up the UI either. I did not change anything in the configuration, just usual automatic updates of the containers. Am I really the only one who is having this issue? Edit: After looking further and playing around with the settings I figured out, that the issue is somehow caused by the "Network Type" setting. With "Custom:Br0" the UI is not coming up, however when I change it to "Bridge" the webui is coming up again. Edit2: It seems that for some reason with br0 the portmappings are gone. When I create a new custom network the portmappings are back again and I cann access the UI. Do you know how I can geht the portmappings for the containers on the br0 network back?

Hi guys, I recently moved to Turkey and unfortunately the government is blocking all major VPN providers like NordVPN, Proton, PIA, etc. Do you guys know any workaround so that I can continue using VPN? Or any alternative solutions I could use with Unraid and containers like qbittorentvpn etc.? Thanks!

Oh wow I'll check that. But it's weird because I didn't change anything on the IP configuration of my network or the dockers and everything was working flawlessly for months. Might this have happened during an update?

192.168.178.103 But nothing changed on the network side. Strange thing is, that radarr, sonarr etc. are able to download via sabnzbd just as usual. The only thig not working is the web ui. When I click on "WebUi" nothing happens. I installed another container for qbittorrentvpn and there it works just as usual. I guess it will work with another sabnzbd container as well. But I'd like to avoid chaning a running system.

Here you go supervisord.log CommandExecution.txt

Hi guys, since a couple of days I have the issue, that the webui is not opening up anymore. First I had thiss iusse with binhey-qbittorrentvpn and now with the sabnzbdvpn package as well. Is this a known issue and is there an easy fix? Replacing vpn config files didn't help, fresh install didn't help either.