tillkrueger

Bingo! Was in bed already, over here in Berlin, when you replied, but just did as you suggested, and it worked. I had to search for how that is done, and found this thread, explaining it. Go to Settings > Docker Turn On Advanced View (small slider in upper right) Set Enable Docker: to No (and Apply) Change Docker Size (and Apply Set Enable Docker: to Yes (and Apply) Thanks again and as always for being so helpful, Squid

Yes, I should have...sorry, here they are.

when trying to update my binhex-krusader Docker, I get this error: Error: failed to register layer: ApplyLayer exit status 1 stdout: stderr: write /usr/lib/tcl8.6/auto.tcl: no space left on device My Docker memory shows at 79%, so how can I free up enough space to update all of my Dockers without such errors?

Alright, then I won't worry for now... I'll return to this when things seem to turn south for real... Thanks!

Aaaactually, the reason why I even went into the SMART page for that drive was because of the "error" warning I saw in the Dashboard...looks like there are errors pertaining to the NAND block count (see attached)...is that something to worry about, and if so, what to do?

Well, that settles it, then...cheers, JorgeB !

Oh, now that you ask, I may have misinterpreted these numbers (see attached) as the number of errors found...but maybe those numbers refer to the Attribute number given to label a particular error in the log file, when it is found?

While my parity is rebuilding, I just noticed what looks like a concerning amount of errors on my cache NVM (see attached). Is this within the realm of the acceptable, or is my Crucial NVM near or at the end of its life (it's been in operation for a few years (maybe 3-5), but I don't really copy/move data around or onto the array but once of twice a year). Should I Scrub it with the "Repair corrupted blocks" option, or is it more complex than that?

Thanks for the quick response trurl ! I confirmed the error, as you suggested, and started the rebuild of the content to the new drive, without a Preclear...I remember how looong preclears take, and how rarely I did them in the past 15+ years of growing my unRAID. Here's to hoping that it will all return to normal (+2TB) soon. And thanks again for helping me along! Best from Berlin, Till

It's been a while (a year or more) that I've had to change anything on my unRAID server, but today, I wanted to upgrade the only remaining 6TB drive to an 8TB. I did a clean shutdown via terminal, directly on my unRAID, then took out the 6TB and replaced it with an 8TB WD80EDAZ shucked from a new WD My Drive enclosure. Now that I am back at home and have taken a look at what I am faced with, I am greeted by the following situation (see attached). So, the new drive shows a CRC error, and I don't want to do anything to jeopardize the health of my array. What is the safest way to proceed? If possible, could anyone give me very specific step-by-step directions to properly have this 8TB take the place of the removed 6TB drive? I faintly remember having to do a Preclear first, or is that not correct? Anyway, what to do, what to do?

I am also now getting the same error message as you, discojon, when starting the WebGUI of my Nextcloud Docker: This version of Nextcloud is not compatible with > PHP 7.3. You are currently running 7.4.14 would you be able to let me know how exactly can I get it to work again? Where exactly is this config folder where you edited versioncheck.php?

Ok, I guess I can’t have it all with this, but I am glad to have an easier method to administer and connect to my unRAID by means of your Docker. Thank you! Sent from my iPhone using Tapatalk

Ok, I am able to add my unRAID system to my Finder via "Connect to Server..." in the Go menu, but this wasn't necessary when I first had Zero Tier running correctly...it just appeared as part of my Network. Is this a configuration error in Tailscale, or do I need to run some other service for "Bonjour-like" Finder integration of my unRAID system (if that is possible)?

After figuring out that Tailscale has *two* icons in the mac Menu bar (one for the app itself, and another for the VPN status), I was able to Log in and add my MBP to my Tailscale Dashboard. I can now log into my unRAID webUI via the supplied IP number at the top (100.*.*.*), so the webUI access ability (without using the supplied company VPN access) is now working. Is there a way to see unRAID as another computer in my Mac's Network, to be able to access its resources (files) directly?

After ZeroTier stopped working for me for some reason, I was advised to try your Tailscale Docker. So I installed the Tailscale Docker, got the network ID via Ragemachinest instructions and registered it via the link in the console, and now see it in my Tailscale Dashboard. Then installed Tailscale on my MBP. Still no sight of my unRAID system in my Network, though. Maybe I will first need to register my MBP with my Tailscale account as well? I don't see it in my Dashboard. Maybe I don't correctly understand the purpose of Tailscale, but since it was recommended to me as an alternative to ZeroTier, which after first configured showed my unRAID system in my Finder Network, I thought that Tailscale will also server this purpose (amongst other much more lower-level functions, I am sure). Am I misunderstanding what this Docker allows me to do? If the main function I want is to implement unRAID in my local network via the Finder Network *and* get to the unRAID webUI, will this work when correctly configured?