jbat66

I too have started to use "docker pull repository_name" for Immich and frigate (Thanks tacojutsu). Looking at the forums and reddit, this seems this has been an ongoing problem in verson 6 and 7, that has never been truly solved. People try changing DNS, change the docker timeout, move the docker image from cache to array, or array to cache, and then it works sometimes, I don't think any of those solutions, are solutions, and they just appear to work, randomly, but not repeatable because of the several times the user re-runs update. I too think it has something to do with dockers that have large files that have to be downloaded. Looking at all the different threads, there is no true fix... Please fix..

Thank you, I had not thought of that. I do that all the time with my UNRAID running on an Intel NUC in my RV. I didn't think about doing that with my Tower.

I ened up waiting over night, and while the Gui was still messed up, I was able to see my VM's and Dockers, and more importantly, I was able to login to the console, and do a safe reboot command, everything came back up, and no parity check was needed.

Howdy all, I was in viewing the GUI. I was not doing anything other than looking at the status, then it just timed out, I then could no longer change pages, connect to any dockers, or VM's. I can no longer login at console. I put in Username, but the password prompt does not display. ver 6.12.13 I can not SSH The web gui does not display. but I can ping the server. I put in the username of root, and then there is no prompt for password, and then after some time I get an error message. "Login: timed out after 60 seconds" What are my options? I really don't want to yank the power.

This question doesn't fit this thread. I would suggest you start a new thread, so the right people may see it.

This is minor, but I have many scripts that do copying and the such and I used figlet to make the output and status large on the screen. Would it be possible to add figlet back in? It is not a utility per se' but is useful in scripts for larger output, and was in the old nerd plug in.

Others have chimed in with the correct answer, in that the docker image file has to go somewhere, and the VM data also has to go somewhere if you enable it. I would recommend not doing VM's in UNRAID while under proxmox, you caaaaan, but why? Secondly I recommend just having one large disk, since you don't want to use Unraid's Raiding while virtulized, it does take a large performance hit. Your server that you are running proxmox on should have a raid of some sort, if not you can do it in unraid, but I wouldn't. If you don't have raid on your underlying server, then you could pass the drives through, but that is not how I'm using it. I just want the one click docker management that unraid gives me, and in some cases the file sharing.

OK, so changing to Intel NIC, did not work. I upgraded to 6.12 RC6 - thinking the updated Kernel would help - that did not work. I'm really out of ideas. I couldn't download a diag this time, because with 6.12 RC6, I couldn't get the console screen to come up. Heck even a command to restart networking form command line would be helpful, as I could setup a cron job to restart it when it can not longer ping the gateway. I have one that will reboot the server when it can't ping the gateway but that is hard on the system, because half the time I have to rebuild a drive.

As a matter of fact, I just installed in Intel NIC 2 min ago, and I'm waiting for reboot. We will see how long it stays up. Thanks for the info.

No, I didn't. After reading it, I was able to get it installed. First one I ever had to pre-install. lol

This has been driving me crazy. I purchased two different TP-Link NIC's and still have the problem. I thought maybe it was the internal NIC. Looks like it is just a problem in the Unraid code. Maybe it is the fact the on board NIC and the two I purchased are running RealTech chipsets. The funny thing is that Unraid worked great for years on this server with the internal NIC. I was away for a few months, and when I got back to the server it started having the problem. So it wasn't because of an update, unless it was a plugin update that caused it. Frustrating. Every time I pull diag, I get the same lines in syslog.

Just a note, I tried to install SwingMusic and got the following error: docker: Error response from daemon: pull access denied for swingmusic, repository does not exist or may require 'docker login': denied: requested access to the resource is denied. Looking in the Unraid app code, I see: https://registry.hub.docker.com/_/swingmusic , and when I go to it, I get a 404 error.

This is a wierd one. I was away from the server for several weeks and when I came back the server was running, but no gui, or any network access. I rebooted from console, and all was good for about a day and then no network. the server was fine, just no network. I was running 6.x something and figured I would upgrade to latest version so upgraded to 6.11.5. Same thing, the server would run fine for a day or so and then no network. I then figured I would replace my NIC, but no more slots, so I plugged in a USB3 Ethernet dongle, and moved ETH0 over to the dongle. Everything stayed running for over a week. I then thought I would try the internal NIC again and set it up as ETH0, but left the USB3 dongle plugged in, and added another IP so I can get to the GUI if the NIC/networking quit. Yep that night, networking quit, for both. I had to again reboot from console. While I can continue to run on the USB dongle, I would rather figure out if there is a setting or something to fix the network from quitting when using the internal NIC. Thoughts on what could be the cause? In each case I start seeing these lines in the syslog, when the Network quits: ### [PREVIOUS LINE REPEATED 2 TIMES] ### May 17 02:08:31 Thor kernel: net_ratelimit: 9 callbacks suppressed May 17 02:08:31 Thor kernel: r8169 0000:08:00.0 eth0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 17 02:08:31 Thor kernel: r8169 0000:08:00.0 eth0: rtl_ephyar_cond == 1 (loop: 100, delay: 10). ### [PREVIOUS LINE REPEATED 5 TIMES] ### May 17 02:08:31 Thor kernel: r8169 0000:08:00.0 eth0: rtl_eriar_cond == 1 (loop: 100, delay: 100). ### [PREVIOUS LINE REPEATED 2 TIMES] ### May 17 02:10:10 Thor kernel: net_ratelimit: 9 callbacks suppressed May 17 02:10:10 Thor kernel: r8169 0000:08:00.0 eth0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 17 02:10:10 Thor kernel: r8169 0000:08:00.0 eth0: rtl_ephyar_cond == 1 (loop: 100, delay: 10). thor-diagnostics-20230517-0652.zip

Thank you, I will give that a try.

Been a reliable system up until a few days ago. Then started getting XFS metadata I/O errors and on other occasions md disk read errors per the console. I do a reboot, Get a warning message that several disks had read errors, but all are OK now, and parity check started. After 16 hours of check, it comes back good. and then stays running for a few days, until the next time. Generaly when this happens, no one is useing the shares, nor the dockers (of course they are still running in the background). While I have VM's they are not running. Upgraded to 6.9.2 a month or two ago, never had a problem on the previous version of unraid. 6.8.x I have purchased a replacement drive, thinking it was disk2, but every time it 'seems' to be several disks with read errors. Unraid version: 6.9.2 ASUSTeK COMPUTER INC. PRIME B450M-A, Version Rev X.0x American Megatrends Inc., Version 1201 BIOS dated: Thu 25 Apr 2019 12:00:00 AM MDT Mem: 16 Gig DDR4 CPU: AMD Ryzen 3 2200G with Radeon Vega Graphics @ 3850 MHz thor-diagnostics-20220201-1851.zip