mattekure

After turning off the dockers and VM, then rebooting, the shares came back. running a parity check now.

A few minutes ago, my unraid system hard lockedup. I could not access the GUI, webpage or ssh into it. I did a powerdown and restarted. When it came up, all of my shares are missing and I am getting parity errors when the parity check runs. What are my next steps? tower-diagnostics-20191112-2112.zip

Would it be possible to add a Pending Tasks count to the dashboard? So i can see how many are left in the queue?

I wanted to update this. I am still getting the messages but finally found something that may(?) explain it. this article on the archlinux wiki mentions: https://wiki.archlinux.org/index.php/APC_UPS I'm not sure if that makes sense to anyone or not.

I'm having some difficulty getting this working. I have installed a P2000 card, and installed the plugin, downloaded and installed the Nvidia Unraid Build. When I do a fresh reboot, I can go to the settings->Unraid Nvidia page and I see the GPU listed there. But after a few minutes, if I go back there, its gone and all the GPU entries are blank. I am not passing the P2000 to any VM. I have added it to only my plex docker. diag attached if it helps. Edit * Nevermind, I am an idiot. stupid mistake. all seems to be working now. and Thanks for the awesome work.

Yes, I know it comes from the UPS. The messages stop if I turn off the UPS Daemon. I posted it here as these messages did not appear prior to 6.7.0. They do not seem to cause any issue that I can see, and I dont see the logs filling up too quickly or causing problems.

Just adding that after upgrading to 6.7.2, this is still occuring. about 21 lines created each second in the log.

Thanks. I somehow overlooked that setting in the DHCP section of my router. I have added it there.

Quick question, I have the Pi-hole docker set up and working correctly (I think). the Dashboard shows queries being blocked and the blacklists in effect. I currently have it set up so that my Router points to pi-hole for DNS queries. On the pi-hole network overview, it show all the queries as originating from the router. I believe this is the expected behavior as the clients are passing the request to the router which then passes it to pi-hole. I just wanted to be sure that is what I should be seeing.

Thats essentially what I have done. My router uses pihole as the primary DNS, and secondary I have pointing to another one (quad9). that way even if pihole is down, it should allow DNS to continue working. Unraid of course is set to a static DNS, not getting it from the router so it works whether or not pihole is running.

Recently I noticed that my log has a huge number of these messages. I only noticed it since the last update to 6.7.0. Diagnostics attached. May 20 18:20:17 Tower kernel: hid-generic 0003:0764:0501.0001: control queue full May 20 18:20:17 Tower kernel: hid-generic 0003:0764:0501.0001: control queue full May 20 18:20:17 Tower kernel: hid-generic 0003:0764:0501.0001: control queue full May 20 18:20:17 Tower kernel: hid-generic 0003:0764:0501.0001: control queue full May 20 18:20:17 Tower kernel: hid-generic 0003:0764:0501.0001: control queue full May 20 18:21:17 Tower kernel: hid-generic 0003:0764:0501.0001: control queue full May 20 18:21:17 Tower kernel: hid-generic 0003:0764:0501.0001: control queue full May 20 18:21:17 Tower kernel: hid-generic 0003:0764:0501.0001: control queue full May 20 18:21:17 Tower kernel: hid-generic 0003:0764:0501.0001: control queue full May 20 18:21:17 Tower kernel: hid-generic 0003:0764:0501.0001: control queue full May 20 18:21:17 Tower kernel: hid-generic 0003:0764:0501.0001: control queue full May 20 18:21:17 Tower kernel: hid-generic 0003:0764:0501.0001: control queue full tower-diagnostics-20190520-2223.zip

Ok, sorry for the false alarm. It was my fault. one of my browser extensions (chromeiPass to auto fill in passwords) was injecting input fields into the page which were triggering the code that looks for blank fields. once I disabled that extension, it worked just fine.

Oh, I found the run command. docker run -d --name='codiad' --net='bridge' -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'PUID'='99' -e 'PGID'='100' -p '8088:80/tcp' -v '/mnt/cache/appdata/codiad':'/config':'rw' 'linuxserver/codiad'

Hmm, on https://hub.docker.com/r/linuxserver/codiad/ it shows that there is a docker parameter for TZ. should I add that parameter? it didnt exist when I installed it. Edit: that didnt appear to do anything. I set it exactly as it appears on the webpage, but it still asks for all fields to be filled out.

I'm not sure how to see the docker run command. The images are everything in the log and all the settings from the docker.

I get to that page, and when I click install I get the message saying all fields must be filled out. when I click OK there, I get the second message saying do you really want to create project..... clicking ok on that dismisses the message, but nothing happens. it never goes into the actual codiad gui.

Perhaps I should clarify. the container installs into Unraid just fine. its when you first run it, you go to the WebUI and it asks you do do an initial setup like setting up a username/password and initial project. thats the stage I cant pass.

The only thing in show more settings is the appdata config path which is filled out. advanced view also just shows blank spaces for extra parameters and post arguments. but there is no indication of what would need to be put in there.

I tried to install this, but could not get past the initial configuration. After filling all the fields and selecting Install, it keeps insisting that all fields must be filled out. I have checked every field on the page, and every one is filled, but it will not pass past that point.

Thank you, upgraded without issue.

The largest drive I have used with it is a 4TB, so I dont know beyond that.

I'm not sure what you mean, but its a SATA III card, so it should support any drive that uses SATA III.

I cant speak for others experiences, but this is the SATA card I use and I have had no issues with it. https://amazon.com/gp/product/B00AZ9T41M/

Overnight I began receiving this error about communicating with github and being unable to download the list of blacklisted plugins. I am using the google DNS and I am able to browse github without issue from my browser. I also tested pinging github and got a response fine, so I'm not sure whats going on. I've attached diagnostics if its helpful. tower-diagnostics-20181130-0721.zip