CorneliousJD

Are you able to confirm that LSIO will push an update that fixes this security issue - or is it something we have to actually go in and edit the config files for? This post from Nextcloud shows 2 options, one with updating php packages and one with editing nginx config: https://nextcloud.com/blog/urgent-security-issue-in-nginx-php-fpm/

Cool, thanks Squid! I did already have auto-update plugin installed and up to date and I did still get the update notice last night of a ton of containers updating, even though one in particular (Deluge) i have set to be locked at a specific version. This isn't a big deal to me though, it's just a notice I can ignore daily since I assume this will be fixed in the next unraid release as well? Server: Docker Auto Update Community Applications Deluge Grocy Heimdall HomeAssistant Jackett LetsEncrypt Lidarr MariaDB Nextcloud Ombi PiHole Portainer Radarr Sonarr UniFi Automatically Updated normal

Got this over night last night on scheduled run of scanning for common problems (Fix Common Problems plugin) Event: Fix Common Problems - Server Subject: Warnings have been found with your server.(Server) Description: Investigate at Settings / User Utilities / Fix Common Problems Importance: warning **** Template URL for docker application Bitwarden is missing. **** **** Template URL for docker application FileBot is missing. **** **** Template URL for docker application Grocy is missing. **** **** Template URL for docker application HA-Dockermon is missing. **** **** Template URL for docker application HomeAssistant is missing. **** **** Template URL for docker application PiHole is missing. **** **** Template URL for docker application Portainer is not the as what the template author specified. **** **** Template URL for docker application Tautulli is not the as what the template author specified. **** **** Template URL for docker application UniFi is not the as what the template author specified. **** **** Template URL for docker application UniFiVideo is missing. **** I re-ran the scan and am still seeing this. Nothing had changed previously, server uptime is almost 18 days right now. PS I had been getting repeat notices of docker containers updating every night despite not having an update available, but I've gathered that's a known bug in this version of unraid, maybe these two are related. Wondering how I can fix this, or both? Not sure if it's safe to apply template URL from fix common problems or if I should be waiting this out. So here I am

Just dropping by to say this affected me when adding a new RAID1 member to cache, thankfully johnnie.black is on the forums directing users here, was able to make sure metadata is updated correctly to RAID1 now.

Woo, wonderful! Back to showing a 500GB drive now. I also made a full backup before I did this just incase, but I will plan to follow the link from your first post to add a new drive and have it be 2 slots This will RAID1 the 2 drives and I shouldn't loose any data from what I'm understanding?

Ok, I did the conversion and it resulted with Done, had to relocate 5 out of 176 chunks But when I do btrfs device delete missing it results with btrfs device delete: not enough arguments: 1 but at least 2 expected

+1 here as well, this also just happened to me, every time array starts it tries to re-balance.

I'll be replacing the missing one - so I had a RAID1 of 2x 500GB SSDs, and one went back to Samsung for RAM which is why it's missing now. They're sending me a new drive today that will replace the missing RAID1 member, I'm assuming it will be a whole new drive/new serial number.

Before I do this, I want to make sure I need to because that deleted device will be replaced with a new SSD later this evening (when it arrives from Samsung RMA dept). Do I need to still convert to single or can I simply replace the drive later today and then after run btrfs device delete missing? Thanks in advance. You always come to the rescue when I have issues haha. If you have a paypal/venmo I'd happily send you some coffee/pizza money sometime!

As requested, attached. server-diagnostics-20190828-1322.zip

perfect, I knew there had to be a way, very helpful, thanks Squid!

I somehow turned off the "notify me of replies" on this so I missed your (helpful) reply. I had a power failure today and the server shut down cleanly but upon booting back up the server noticed cache1 was gone and it ran a balance on the cache array. Now it thinks it's a 1TB cache for some reason (only ever had 2x 500GB drives in RAID1). My replacement drive should finally be here from Samsung tomorrow, but I'm worried now about simply stopping array and placing this into the cache pool, if it thinks it's 1TB?

I've been having a lot of issues with an SSD (i'm finally replacing it) but it's caused me to have to rebuild my docker.img a lot lately. I do keep seeing all my old docker containers and names and I would like to clean these up so that if it happens again a year or two down the road I won't be confusedo n which version is which that I should be picking, and only have the active/live ones that I want to reinstall there? Screenshot to show what I mean during the "Add container" portion of adding a docker container when rebuilding docker.img. Thanks in advance.

I had 2x 500GB SSDs running cache, however one has been failing and blinking offline all the time no matter the backplane slot, so it's going back for RMA. Is there a clean way to remove that one SSD from my cache for now and use the live data left on the other drive w/out rebuilding everything? Then after the new drive arrives am I able to cleanly add it back in? Or would I need to destroy and rebuild the cache each time? Trying to find the best way of doing it. Right now the server knows the drive is missing so /var/log is 100% full and I don't know how long it will be before a replacement drive arrives.

Entering! Thanks guys. Almost 2 years user now. I love having all the docker containers in one place ran by an amazing community. Plus of course all that file storage!

Yep, I am, just thought it was odd that it was the only one showing that error - the rest of the scripts I have exit cleanly. I'll go ahead and schedule that for hourly runs. I created a scrub script and a script to reset error counts incase this happens again. the SSD is on a backplane so I can't really change any cables, and it hasn't happened for over a year until now. I'll be prepared this time though with the new scripts added incase it happens again. Thank you again for your time and info!

So I'm working on setting up the scripts for ease of use and the one that generates a warning seemed to work once, but now it's not, I had deleted the script to create them with better names/descriptions (and so the folders would get named correctly in /flash/config/plugins/user.scripts/scripts/) Now when I copy/paste your script in I get the following error, and it doesn't actually generate the warning. /tmp/user.scripts/tmpScripts/Cache - Error Check/script: line 4: syntax error: unexpected end of file The script is only 3 lines long, so there's nothing on line 4. Is there a way I should be closing out this script to run cleanly?

Awesome, good to know I can at least get back to normal work-mode today for now, I'll circle back on the scripts in a few hours. Was awesome waking up to the fix - thanks @johnnie.black -- you've helped me before in the past as well, much appreciated!

Scrubbing didn't take long, but now btrfs dev stats /mnt/cache shows corrupt errors now when it didn't before the scrub. Not sure what to make of this.

Thanks, the NOCOW was key, my /system/ and /vms/ shares are NOCOW (both were this way by default from what I recall). docker.img rebuilt and running btrfs scrub start -B /mnt/cache/ now -- so far no output, not sure how long to expect it to take, or if I can continue to rebuild docker containers while this goes. The odd thing is this same disk blinked offline before, but it was OVER a year ago (early April of 2018). Strange....

Got an alert that one of my cache drives was missing, but it showed as an unassigned device. I rebooted server and it's detected as part of cache again but docker service is now failing to start. What's the proper way to solve an issue like this? Is the rest of the data in cache pool likely to be corrupt?

Thanks, I put in linuxserver/deluge:5b398f77-ls22 I honestly picked 146 at first because I wasn't completely following which arch I should pick on the newer releases, didn't realize that 5b398f77-ls22 would have automatically picked the proper one for me. I see my mistake now. I was just looking to go back to the release numbers I had recognized the last time I had a small issue, (back then I went to 135) -- that's why I ended up trying to go back to 135 again this time, just familiarity. I'm on 5b398f77-ls22 now though, restored from backup from last night before the update happened, all back up and good to go! All torrents back and appear to be where they should be now! Appreciate the assist @CHBMB!

Thanks, I did this in the meantime, after I noticed none of my torrents were seeding, (client not on whitelist) and I tried pulling 146 but it failed to open the WebUI after that. I went back to 135 and now Deluge opens but none of my torrents are there - everything is cleared out. Do you know of a way to fix that? I had many on very different paths and labels, etc.

With this latest update (2.0.0 it seems) I can no longer connect with the daemon from Deluge installed on a Windows machine. Deluge 1.3.15 is all that seems to really be available on Windows still at this time. The connection manager now shows the server as down all the time. (This is from 1.3.15 on Windows) (This is from WebUI on Unraid) Any advice on how to get this back up and working would be appreciated. I actually use a lot of features in the full version on a Windows machine (such as renaming individual files before they download, etc) Thanks in advance!

Thanks, I think i had messed with that because of the www aesthetic I wanted but I can certainly live without that as long as it properly works. Just updated this and it seems to, although I think the 301 redirect on my PC was working for a while and I didn't notice it until I tried from another device. Will do more in-depth testing with things set back to default. Thanks!