Convington

I got it working and found the files under the PC name in the filesystem.

I'm a bit stuck. I installed the docker, then installed the client, and began backing up my server. After a full day it wasn't completed and somehow took up about 3TB of space on my UNRAID server. So - I stopped the backup (or tried), but it would not stop. Then I paused it on the client hoping that would help. It did not. Eventually I removed the Docker (and windows client) and looked for the backup files to remove them. All I saw were some folders under /media/urbackup that I removed. My UNRAID server still shows I have almost no disk space - so the files are out there somewhere. I'm trying to get back to normal so that I can reclaim the diskspace and start new with urbackup - but can't seem to figure out where the backup files are stored. My initial backup problem, I believe, was a backup paths issue on the client where it showed the H:\ drive as a backup path even though images only showed volume C. The H:\ drive is where I have a whole bunch of old VMs and is a USB drive.

No advice?

I'm having a problem installing Telegraf. It pulls just fine, but when it goes to install it eventually gets to this:

I have the same problem as Lohita above. Updated the docker from 2.0.x (unsure which flavor it was in June) using 'influxdb:latest' during the upgrade process within unraid, then when I start the Docker image I get the Influx Onboarding process. More information: I can see my influx folders at: /appdata/influxdb/data, /appdata/influxdb/meta, /appdata/influxdb/wal. All my data lives in the /data folder and is visible to the share. On the flash drive, I see: /boot/config/plugins/dockerMan/templates-user/my-Influxdb.xml, which contains the following: <Data> <Volume> <HostDir>/mnt/user/appdata/influxdb</HostDir> <ContainerDir>/var/lib/influxdb</ContainerDir> <Mode>rw</Mode> </Volume> </Data> <Environment/> <Labels/> <Config Name="Host Port 1" Target="8083" Default="8083" Mode="tcp" Description="Container Port: 8083" Type="Port" Display="always" Required="true" Mask="false">8083</Config> <Config Name="Host Port 2" Target="8086" Default="8086" Mode="tcp" Description="Container Port: 8086" Type="Port" Display="always" Required="true" Mask="false">8086</Config> <Config Name="Host Path 1" Target="/var/lib/influxdb" Default="/mnt/user/appdata/influxdb" Mode="rw" Description="Container Path: /var/lib/influxdb" Type="Path" Display="always" Required="true" Mask="false">/mnt/user/appdata/influxdb</Config> My shares include one named appdata, set to Public, Prefer: Cache. This share seems to go to the /appdata folder. Inside of Krusader, it looks like: /media/appdata. I hope someone can help me here.

Maybe this will help someone help me?? I can see my influx folders at: /appdata/influxdb/data, /appdata/influxdb/meta, /appdata/influxdb/wal On the flash drive, I see: /boot/config/plugins/dockerMan/templates-user/my-Influxdb.xml, which contains the following: <Data> <Volume> <HostDir>/mnt/user/appdata/influxdb</HostDir> <ContainerDir>/var/lib/influxdb</ContainerDir> <Mode>rw</Mode> </Volume> </Data> <Environment/> <Labels/> <Config Name="Host Port 1" Target="8083" Default="8083" Mode="tcp" Description="Container Port: 8083" Type="Port" Display="always" Required="true" Mask="false">8083</Config> <Config Name="Host Port 2" Target="8086" Default="8086" Mode="tcp" Description="Container Port: 8086" Type="Port" Display="always" Required="true" Mask="false">8086</Config> <Config Name="Host Path 1" Target="/var/lib/influxdb" Default="/mnt/user/appdata/influxdb" Mode="rw" Description="Container Path: /var/lib/influxdb" Type="Path" Display="always" Required="true" Mask="false">/mnt/user/appdata/influxdb</Config> My shares include one named appdata, set to Public, Prefer: Cache. This share seems to go to the /appdata folder. Inside of Krusader, it looks like: /media/appdata. Man - I hope someone can help me here. Somewhat painful considering I use this system to track power usage for my business (which is part of my home). Right now I'm blind (even though my meter is still tracking - it isn't forwarding to Influxdb anymore since it is down).

So - this happened previously as shown above... I upgraded everything after some tinkering around. It is a 2.0 Influx, but same thing happened. After upgrade it just looks like a new system again All the data seems to be there in the appdata structure, but the org stuff seems to be gone. Which means I have to reset the whole damn thing again after upgrading? Something has to be wrong either with the way I am upgrading (just hit the 'upgrade' link in Unraid) or the procedure.

I do see now that I posted in the wrong forum. However - I don't see a proper one that isn't German for the InfluxDB container and I think this is more of a generic container problem than it is a specific one.

I've updated InfluxDB several times without any issues using the UNRAID Docker interface and "Apply Update" link. This time, however, I can no longer login - I get the onboarding process when I go to port 8086 Any ideas on what I can do? I'm afraid my data is lost now and I have several Node-Reds running data into nothing now along with my home energy monitoring software.

I didn't do anything (not even restart) and it is back to being able to update. I'm confused.

Once again Docker is unable to show the version number of the apps This is the second time. Last time I put in a new cache drive because I was told the cache drive had some issues (it did). But now I have a brand new SSD in there as my cache drive and it is happening again. It took 3 months before it happened, but I'm pretty sure it was 3-4 months in the first time it happened. I really don't want to have to rebuild the cache each time this happens, doesn't make sense. I could move my Dockers to something more stable? Not sure what the solution is, but I can't have my dockers unable to update - that is a security problem waiting to happen.

Ah, crap Learning something every time. Thanks. I will keep an eye on the log and see how it performs over the coming days.

Here is the current diagnostics after reboot. You should be able to see the errors prior to reboot which don't seem good (and I couldn't start a couple of dockers at that time). tower-diagnostics-20200828-0915.zip

Doing this now. I should have remembered that. Had some errors this morning (prior to format), hopefully relates but doesn't appear that way. I will add diagnostics after the format if anything goes wrong. thanks again for the help.

Went out and grabbed a new SSD and installed. Still some errors in there - what should I look at next? Sorry just not good at UNRAID yet tower-diagnostics-20200827-1409.zip

ok. Thank you. Will find a replacement again. Appreciate the help!

But this is the second cache drive within a week - why would it be failing? That's what was said about my last cache drive hence the replacement Seems very odd to me that 2 SSD drives would fail so easily when I haven't had any fail previous to that since I've been using SSDs.

Feel free to read through my previous issue:

Previously I had a cache drive issue. I added a different SSD for Cache. The old drive used for cache is still there somewhere (didn't want to pull drives to find it, so left it in) but isn't used in the configuration anywhere. After replacement things were great for a bit. Lately my Dockers seem to crash, virtual ethernets seem to be the problem. And today when I went to plex and nothing showed (yet again) I look to the log and see a crapload of errors again Attached are the diagnostics. It's difficult to keep up with all the problems - I feel like I haven't had a stable system in a while now and it is frustrating since I keep backups on UNRAID along with running my new Plex server and Unifi Controller. You will see in the syslog that there are a ton of sdc1 BTRFS errors towards the end. Pretty sure it is my new Cache drive. Not sure why it is constantly corrupting this drive? maybe this makes sense to someone smarter than me tower-diagnostics-20200827-0940.zip

When I get on a computer that has not attempted to connect previously and use Window File Explorer - it does ask for credentials. I have tried with: \{username} to get to the default context (instead of it forcing in my domain name) and that will not work even with admin user for Unraid.

I don't think this is a Windows problem because my shares used to be visible. Sometime after a drive failure (cache drive) they are no longer visible. Not sure if there is a correlation, but now I cannot access any of the shares at all Trying to move some files around, but can't get to them. Attached diagnostics in case that helps. thx. tower-diagnostics-20200817-0709.zip

Thanks everyone for the help, I seem to be back up and running. I even have the appdata backup plugin loaded.

I will look that up as soon as I figure out how to get the appdata onto the new cache drive I'm new to Unraid, so didn't realize there was that plugin.

I do have a second drive, but not sure what I do first.. I would think I need the following things to happen: Copy that data somehow from the backup to the new cache drive start up the array after this is done Those are guesses, but I have no idea lol

Don't I have to do something with the cache drive? Like, format, replace, something? I'm not real sure where to do that since the cache drive is live.