Derek_

Hiya, I'm using Docker folder instead of docker.img. I've recently realised that this directory has about 64gb of stuff in it after a directory wipe and docker re-install. I've read through this post: It has some good information in there, however the 'fix' doesn't seem to work for me. I wiped the docker folder using the webui, and re-created it. One by one i installed my dockers and each time, the space used by the directory went up significantly. For example, rough figures of space used: Duplicacy - 200mb Firefox - 9gb sftpgo - 3gb UptimeKuma - 4gb Remmina - 15gb etc. So immediately upon re-installing the dockers there is the space used. I don't *think* there's anything wrong with my Docker mappings, either in the configs or in the tool/s themselves. Everything seems to work ok. nas-diagnostics-20240715-1220.zip

OK. Well i figured it out. The TLDR is: Delete the pool, create a new one, only add ONE DISK, set btrfs encrypted, THEN add the second disk to the pool. Here's the full procedure i used. Maybe it can be done slightly differently, but it worked for me. 1. With an empty cache pool (no disks assigned) - delete the pool. 2. Clear any partitions from the unassigned devices that will be used in the cache pool. 3. Create a new pool. 4. Set the pool slots to ONE disk. 5. Assign the first disk only to the pool. 6. Click on the word `cache` - choose the filesystem type - btrfs Encrypted. (password is taken from the array password automatically), click DONE. 7. There will be an open orange coloured padlock next to the word cache. 8. Change the pool slots number to 'TWO' disks. 9. Add the second disk. It will automatically acquire the values set in the first disk. 10. START the array. 11. The open orange padlock remains, and the disks are identified as "Unmountable: unsupported or no file system" 12. Scroll down - below the STOP array button there is a greyed out FORMAT button. 13. Check the disks on the left include ONLY the disks you want to include in the pool. 14. Click "Format will create a file system in all Unmountable disks" - YES I WANT TO DO THIS 15. Click OK to the warning. 16. Click Format. It will take a moment to format the disks. If everything worked ok, the open orange padlock will change to a green open padlock. It *should* now be good to go. Could the official instructions maybe have rather more information about how to do this procedure? Or perhaps there are official instructions, somewhere else?

Hiya, i've installed two nvme's to act as my cache. They replace two smaller SSDs, which were encrypted. I cannot figure out how to encrypt the new drives. These instructions tell me: 1. Is that when the disks are already in the pool? Or when they're in 'unassigned devices'? 2. How does one "select the drive"? 3. In what i assume is the "select"ed drive (i clicked "cache"), my "file system type" is greyed out. It says "btrfs" but gives me no ability to change anything about it.

That is indeed the answer that i've seen mentioned. I came here to see if anyone had something ready-made I didn't find it, so here's what i did: Settings > User Scripts > New Script. I called it "startup-sequence.sh" to hark back to my Amiga days ♥️ #!/bin/bash # create alias each boot: echo "alias ll='ls -l'" >> /root/.bash_profile I set it to run on first array start. It simply appends that line to `.bash_profile` when the array is first started. Don't know if that's appropriate/proper. But it works I don't know anything about the `go` file and i wanted something quickly as i've been doing a lot of organising today. btw, in doing that i noticed that `v` is already aliased for `ls -lA`. But i still kept `ll` because it's pretty ubiquitous.

haha, yeah. I've done it three time i think and every time i have to search for the answer My first thought is that a) it probably doesn't need to be locked; or b) the padlock should be at the bottom with the other action buttons. But i guess the padlock applies to other tabs as well (Dashboard, VMs and i think more to come as versions progress) - so it does make sense that it's where it is.

Is anyone able to describe the contents of the docker directory after the switch to folder mode? drwx--x--- 1 root root 20 Jul 6 10:02 btrfs/ drwx--x--x 1 root root 132 Jul 6 10:01 buildkit/ drwx--x--x 1 root root 12 Jul 6 10:01 containerd/ drwx--x--- 1 root root 384 Jul 6 10:19 containers/ drwx------ 1 root root 10 Jul 6 10:01 image/ drwxr-x--- 1 root root 10 Jul 6 10:01 network/ drwx------ 1 root root 20 Jul 6 10:01 plugins/ drwx------ 1 root root 0 Jul 6 10:17 runtimes/ drwx------ 1 root root 0 Jul 6 10:01 swarm/ drwx------ 1 root root 0 Jul 6 10:19 tmp/ drwx------ 1 root root 0 Jul 6 10:01 trust/ drwxr-xr-x 1 root root 12 Jul 6 10:11 unraid/ -rw-r--r-- 1 root root 13 Jul 6 10:19 unraid-autostart -rw-r--r-- 1 root root 767 Jul 6 10:19 unraid-update-status.json drwx-----x 1 root root 184 Jul 6 10:19 volumes/ cheers. Also curious to know why the 40gb docker.img file becomes a 70gb folder

I had a squiz at this plugin, and decided to remove it. When i did so, it advised: Do i just delete the disklocation directory manually to fully remove it?

Yeah, they were still working. I already did the delete trick. Everything has been dandy since. One thing i remember is that my .img was less than 50% full. So that wasn't an issue.

My Dockers weren't updating, the last thing on my list was deleting the .img and starting fresh. As i was going to do that anyway, i thought i might do the folder thing. A friend of mine said he'd had much better reliability with the folder than the file when he switched.

I'm thinking of doing this. Why does the system suggest path: `/mnt/user/system/docker/docker/` ? When the first `docker` is empty (except for the to-be defunct .img file). Why not just go with `/mnt/user/system/docker/` ?

I would like to make Jellyfin available to be used over the internet, not just my local LAN. I will want to open up other things too when i feel more confident, photos and music. I also want to host an SSH backup server. I haven't decided on apps for these yet. Security is important. I only want authorised users to be able to access these services, or if possible to even be able to know they're there. I have no idea where to start with this, i've never 'exposed' anything before. Can someone recommend a good guide? The best guide? Thanks for any help you can offer.

I'm not sure when this issue popped up for me. It's been quite a while. At least 6 months, i'm confident somewhat longer. I was running Arch, and the install was 5 years old - and it was my first long-term Linux distro. I put it down to "i've been mucking around for so long, that maybe i need a clean install". I decided to give Nobara a go, and i changed from AutoFS to systemd for my mounting. At first it seemed ok, but then it started to happen again. It seems to happen when i make numerous changes rapidly, or i copy large files (the file still copied, but i can't navigate to it). Anyway, i've been looking around and it seems this issue happens on lots of different Linux system. But i've never seen a Windows client have this problem - has anyone else? I also had unRAID for a few years before i encountered this. I wonder what's done it. @NiLon As i'm hoping you'll appreciate, i avoid running commands (or changing settings) i don't understand without a little looking around. I can't find much on this `noserverino` option. It looks like you've been using it for about 2 years (3-ish now), so i'll give it a go and will report back. I'm writing here so i don't forget Thank you VERY much for your original post, and your follow-up some 2 years later. Truly appreciated. Wish me luck @ghostserverd I gave up on autofs. I had it set up on Arch and i found it very complicated compared to systemd, and even before i had these issues, i found it a little flaky. Here's some good reading that convinced me to try systemd: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/managing_file_systems/index#proc_using-systemd-automount-to-mount-a-file-system-on-demand-with-etc-fstab_mounting-file-systems-on-demand https://blog.tomecek.net/post/automount-with-systemd/ https://www.techtarget.com/searchdatacenter/tip/Mount-file-system-Linux-systemds-way The TL;DR is to add `x-systemd.automount` to your fstab entry!

Oh man. I was fixated on the 'warnings' re /mnt/disks - Your solution simply didn't occur to me. Sorry about that 🙃 I've just bought you a coffee

I have an issue with the backup of Duplicacy. I think it's because i use an Unassigned Device, that is only connected when i want to run the backup to it. I've shared the debug log with you (nice feature btw): 47d57179-09a3-460f-a435-2146ad89d7ba Thank you for this tool, it's much better than the previous one (except for this little issue )

Hiya. I procrastinate bad. So i haven't tried. A friend of mine suggested installing the new one and copying the database across. I don't know how to do that in a Docker and he didn't know if it'd work, so i had a quick look and i found this - but as i say, i haven't tried anything yet. https://jellyfin.org/docs/general/administration/migrate/

You're right, i noticed later that it only applies to the Ultra socket: https://www.asrock.com/mb/Intel/Z690 Pro RS/index.asp#Specification Though I don't know the difference between SATA and non-SATA device. How to tell? As an aside, i HATE the way these names keep coming about. Like USB's "full speed" and "high speed". That is literally impossible to know which is faster without reference. Likewise "hyper" and "ultra" for nvme. It's so stupid! I had to go hunting. To my surprise "hyper" appears capable of faster speeds than "ultra" :eyeroll:

Taking account of the various posts (including mine), this is what i did: Old Server Hardware: Run Parity check Turn off Array auto-start Stop the VMs and Dockers, and turn off auto-start. If any hardware pass-through on the VMs, change: a. Graphics to VNC b. untick any `USB Devices` and `Other PCIe Devices` c. Tools > System Devices > Untick any devices ticked for pass-through. (On new PC, reverse the disabling changes done in 2a,b,c.) Take screenshots/note of: Disk order (including cache disks) - note SATA ports with single parity drive doesn't matter, but the order shown in MAIN does matter (apparently the order of SATA ports used does matter if you have 2 or more parity drives - i don't have this). Network settings - also set static ip address if not already, and if multiple NICs note the correct one is selected on the new system. Backup Data and USB stick Shutdown Rename `-EFI` directory on USB stick to `EFI` on PC. New Server Hardware: Memtest (this can also be done with the unRAID usb stick, but i did it before i transferred the HDDs). Review BIOS/UEFI settings: a. Virtualisation is on, if there's IOMMU configurations, take note and adjust as appropriate (i don't have these in my new server). b. HDD set to AHCI (before installing HDDs) c. HDDs are detected (after installing HDDs), double-check AHCI setting. d. Boot from USB as first/only boot device. e. Check XHCI is enabled, per this post. f. Left TPM as enabled. g. Cleared SecureBoot keys, turned off SecureBoot. Boot unRAID. Check network settings (especially if connected to a monitor/keyboard) Check disks are all detected and in the correct order (including cache). Start array. Start Docker service - test each docker and turn on auto-start as desired. Start VM service. Check pass-through settings - test each VM and turn on auto-start as desired. Check access to shares/files via usual access means. Set array to auto-start if desired. Reboot to make sure everything comes back as expected. Parity check. Backup USB stick I think that's all i did. I did write notes, but as is often the case, they're a bit of a mess

Thank you for updating Borg to 1.2.4 Most appreciated

Worse than Micro-USB? 🤦‍♂️ 😄

Well i'm happy to report that the transition seems to have gone well. Touch wood. With all the research and notes, i was very careful and tested it on the workbench (in the garage, i don't like working on carpet). Moved it into the study and somehow during the process, one of the cache SSD SATA cables detached. Luckily i was double-checked 'Main' before starting her up, so noticed and fixed it. Put things back the way they were (Dockers, VMs - no passthrough) and it looks ok. Thanks to everyone who offered advice. I'll jot down my step-by-step in the next few days for reference.

Hmm.. when you changed to the official Docker, did you have to re-do all of your metadata stuff? I spent a while changing show ratings to suit my kids more appropriately.

Oh i spent quite a while searching for the meaning of XHCI hand-off. I found many explanations, many contradictory. What i THINK it means is that it probably doesn't matter much except for old OSes (pre-Win7 - i wouldn't know which Linux kernel) which do not have driver support for USB3. For such systems, it should be disabled so the ports will operate as USB2 ports. For current OSes, I *think* having it enabled (i.e. handing off to the OS once the driver loads) is probably preferable to using the BIOS controller driver, as the software drivers are constantly being updated whereas bios firmware rarely, for things like usb3 controller. Thanks for the post about XHCI for unRAID - it relates to booting the OS via USB3 port which i won't do anyway. I was curious as to whether the USB3 thing was still an issue, that post/thread is from 2018. I think i've done enough research. I'm doing backups, parity check and whatnot (per initial post) and hopefully tomorrow i'll do the transition. Thanks everyone (happy to hear any additional words of advice).

Yep, the old hardware still works. It's merely an upgrade I only have 3 drives in the array, all onboard SATA, plus 2 cache drives also on the motherboard's SATA. Plus one permanent Unassigned Device, also on the mobo SATA port. The new motherboard has 8 SATA ports (or 7 if i use all the m.2 sockets). Although it seems likely to be unnecessary, i'll put them in the same port number in the new build to further reduce the likelihood of issues. I hope someone knows answers to my no.2 and no.6 questions. I'd rather have the right BIOS/UEFI settings before i even first boot on the new hardware.

How does one do that? Was the messaging you showed during the boot? You had a monitor attached and watched it boot (or fail to)?

Interesting, i don't remember seeing it. I have an AMD Ryzen 2700X PC and a new (just about to build) Intel 12th gen for unRAID. Maybe this is new? Or maybe i've just not noticed it. Thanks for the info