sturgismike

You can do this (its a bit slow on my system, be patient) docker container ls -sa --format 'table {{.Names}}\t{{.Size}}' If you want the full data you can drop the --format part. -s means size, -a means all (so that it will show both active and inactive containers)

You need to collect that stuff and shape it into a battleship. So that its.. naval lint.

If you have your router configured to give it a static IP, then you can leave dhcp on and it'll assign it for you. Also note, that on the screenshot you just posted, it says dns is static, but has no entries. As far as why it won't shut off VMs and docker when you apply... Not sure. I know that way back there were some weird issue in chrome with settings not sticking, but I doubt thats an issue any more. To get around this, you could go to the main tab and stop the array. Wait patiently for it to finish, then when you go to your network settings you should be able to make changes. Then go back and restart the array. Edit: I wonder if your drive issues might be causing issues with VM manager and docker not stopping when you apply.

I think you have dhcp off which would keep it from grabbing the dns settings too. Easy to check. Turn off docker and vms (in settings) then go to network settings and add your router and any other dns resolvers you normally use and see if it solves the install issue. From your log files: USE_DHCP="no" IPADDR="192.168.1.220" NETMASK="255.255.255.0" GATEWAY="192.168.1.1" BONDING="yes" BRIDGING="yes" DNS_SERVER1="..." <-- no dns Also, if you have bonding turned on (other than for fallback) your router would need to support whatever bonding mode you chose. For fallback it doesn't matter. (Think fallback is called "active-backup" in this case)

Looks like you have no dns server. And as pointed out by another, something is up with your drives.

You have to disable docker and vms before you can change your network settings. To do so, go to settings/ docker and turn docker off, then to settings/ vm manager and turn that off. Then you should be able to change your network settings.

I just went into exclusions and added the ip of my unraid server. Its sounding like that isn't it though if you completely disabled BD. For me, this also fixed the issue where cpu usage and "active" things on the dashboard page weren't updating correctly. I think there were recent messages about FF specifically causing problems. You might check a few messages up, also might make sure there isn't another update sitting there. Pretty sure squid did some type of FF specific fix recently.

You might try adding the ip of your unraid server to the exclusions in your antivirus software. My bitdefender causes issues with websockets and I think other AV do also. Despite adding the exclusion here, something in the last few updates (either ca, or unraid itself) have caused the number of screen updates on my system to drop off, but its still better than it was before the exclusion.

If I understand how things work, the available apps are packaged with settings specifically for unraid, and are maintained by unraid users. Nobody has done one for Paperless apparently. In settings, you can turn on "enable additional search results from dockerhub" at which point, you will be able to click the whale at the top of your search results to search dockerhub.

I just tried to hit the link directly and this is the response.. Error 503 Backend unavailable, connection timeout So it does look like its down at the moment.

Looks like my ups is on 0000:00:1d.1 , and I can unbind it, but as expected, unbinding it makes the ups stop showing up at all. Rebinding brings it back and it starts doing intermittent resets again. So, I'm stumped. As for re-directing the error messages, while they don't show up in the unraid interface any more, they still show up in syslog, so if errors every 30 seconds or so is a bad thing, I do need to find a solution. Worst case, I guess I can hook the ups to a different machine and use it to control shutdown. I did just try to do this using a raspberry pi, but ended up with the same resets going on. So now i'm wondering if I have a bad ups. (I've tried multiple cables, so am pretty sure its not a cabling issue) Guess i'll hook it up to my windows box and see what happens. Thanks for all the input. I do think I will start saving for a replacement server. I'd like better performance anyway, so throwing money at a system that may be going flaky is probably not the best idea. Edit: Managed to unbind using this command.. root@Tower:/sys/bus/pci/drivers/ehci-pci# echo -n "0000:00:1d.7" > unbind The usb still resets, but it has gone from 1 every 20 to 30 seconds to around a minute + between resets. Still no clue how to actually FIX the issue. Any suggestions welcome. 0000:00:1d.7 is the controller in question. The flash drive is on 0000:00:1a.7 so appears unaffected.

I had looked up possibilities on the ups fix, basically what I read said that you could blacklist the hid (ok, so I don't remember exactly which driver it was at the moment) forcing things to run at 1.1 and it would get things working. Unfortunately, the info I found referred to a module, and from what I understand, that module is now part of the kernel, so the instructions I found to blacklist/disable the module no longer apply. I do have some 1.1 ports, but it doesn't seem to matter if I plug into those, or a 2.0. Functionally, the ups mostly works fine (I've tested it several times to make sure) Setting to 30 seconds on UPS triggering a shutdown DOES create false triggers. Since the port reset never takes much more than 30 seconds, I have it set to 60 and have had no issues since. Other than the incredibly annoying message that I don't know how to get rid of. As for the flash, this is the first time I've had an issue with it. The system has pretty much been a rock since I got it going. The reason I wonder about the way I was re-directing to syslog is that it is a a new thing I've been doing, and the system had been up since the 6.6.6 upgrade. Possibly long enough to cause an issue? Honestly, I'd LOVE to figure out how to fix the ups issue, but I just haven't been able to find an answer that I can make work. I'll see if I can re-locate the answer I found, (that I can't make work) and post it here on the off chance someone has an idea.

No usb 3 ports on this system, its old. But that does tell me, if I buy an addon card I should go with usb2. I was also running a couple rPis using usb, as well as having a keyboard and mouse hooked up that never get used, so I have removed everything except the flash drive and the ups. Stupid question.. Since I was getting the usb resets for the UPS, I redirected the messages to syslog (changing the setting to /usr/bin/logger) Works good and keeps me from seeing the errors that I know are there. Is it possible things went haywire because of log overload? After things went wonky I tried a reboot (using unraid) and couldn't boot, but things worked again after a full shutdown and then reboot. I've temporarily redirected those messages to /dev/null instead, so log overload shouldn't be an issue. (I'm hoping I did it right. I set it to go to cat > /dev/null rather than /usr/bin/logger) As long as i'm here, is there a way to make the change stick between boots? I'm not sure how to edit files on the actual flash so that changes stay changed.

I just had a weird issue with my unraid. All screens went white (though they still worked) and on checking logs, there were a ton of "can't find directory" errors regarding sda1 (the flash drive boot partition) I attempted, and failed to restart. No monitor available at the moment, so I couldn't see the console. After shutting down and shifting the drive to a new usb port, everything seemes to be working great again. Boot up was fine, no errors, no problems that I can see at all. My suspicion of course, is that the specific usb port has decided to blow chunks and die. I fear that others may kick the bucket soon, so my question is.. Would it be reasonable to buy a usb card so that I stop using the onboard usb ports, on the assumption that it will solve the issue, or should I worry that a failed port might indicate a motherboard that is thinking about failing. The worry about choice 2 (the motherboard going bad) is not good. My finances are extremely tight, yet I want a decent amount of cores/ability to play with. (currently i'm on a HP z800 with dual 6core cpus, for a total of 24 threads. Not the fastest, but it has worked really well for me) Could anyone recommend an affordable motherboard/cpu combo that would be comparable or better? By affordable I mean 500 or less including memory. (unless I can transfer my z800 memory over) I will probably take a plunge and just get a pci (or pcie, not sure) usb card and cross my fingers, unless you all think its likely that a failure is imminent. I suspect that these messages are a bad sign.. Dec 27 16:07:30 Tower kernel: usb 7-2: reset low-speed USB device number 2 using uhci_hcd Dec 27 16:08:22 Tower kernel: usb 7-2: reset low-speed USB device number 2 using uhci_hcd Device 2 is where my ups is hooked up.

I finally managed to afford a UPS, and chose one from tripp lite. Unfortunately, my system keeps doing low speed usb resets, and I don't know how this will affect the functioning of the ups. I did some research, and learned that it used to be possible to use modprobe and basically force the usb ports to 1.1 bypassing the issue (at the cost of usb speed) but the ehci part of that fix is no longer a module, so its not an option. I don't think the reset is specific to the ups, and have noticed keyboard lights flashing and being reset too. (though not nearly as often I don't think) So first question, does anyone know what might be causing the resets, and how to fix the issue? (or is it not really an issue despite the large number of resets?) If not, I have an alternate idea. I have an orange pi pc not being used, I guess I could hook the ups to it, and have it act as intermediary so that the ups isn't directly cabled (usb) to my unraid box. Is there any issue with this method that i'm not seeing? The machine in question is an HP z800 with the 850 watt power supply. Currently 3.5" drives and an ssd cache drive. Thanks in advance for any help.