digity

What about adding the former 10TB parity drive as a regular data drive in the array? Do I have to prep/erase/pre-clear it beforehand or just stop array, pop out a 6TB drive and pop in this 10TB drive and start array?

I bought 2x 24TB drives to replace the 2x 10 TB parity drives in my array. I don't have physical space in the server to pre-clear the incoming 24TB parity drives. How do I replace these 10TB parity drives with the 24TB drives, then use those 10TB drives to replace some 6TB drives in the array?

I needed to add a second IP address (192.168.199.10) to my NIC and did so via a script (via the User Scripts plug-in) that starts when the array starts. The only problem is I can not access the shares (CIFS and NFS) nor the Unraid web GUI via the secondary IP address. A little further digging and it appears I can go out from the Unraid server and access anything on the 192.168.199.0/24 subnet, but nothing on the 192.168.199.0/24 subnet can see/access 192.168.199.10. Any ideas on how to resolve this? P.S. - The command I use in the script is "ip addr add 192.16.99.10/24 dev br0"

Is there a way to pre-clear 8 drives simultaneously on another computer then physically add it to the Unraid server to replace the smaller drives one at a time? I'm just trying to cut down the total time replace 8 drives. I don't have space in the Unraid server for additional drives, but I have a spare 12 bay computer I perform batch hard drive stuff like secure wipes.

I have to replace 8 x 2TB drives with 8 x used 6TB drives. I understand pre-clearing the replacement drive is recommended. Pre-clearing is time consuming and so is the subsequent parity rebuilding to the replacement drive. To replace the 8 drives faster, can I secure wipe (i.e., via DBAN Boot and Nuke) and then put them in the Unraid box to replace the smaller drive and start the parity rebuild (skipping the pre-clear process)??

Is there a way to write history immediately instead of waiting until logout/exit?? I often have multiple SSH sessions open simultaneously and don't really exit/logout on each (remote client restarts or something), but want all their history.

I'm in the middle of upgrading my cache pool size and adding more drives to the main array. After Mover moved appdata and system to the storage array and the outgoing cache pool was removed I took the liberty of applying any available updates and upgrades to any community plug-ins and Unraid's Docker engine. Mover moved appdata and system to the new cache pool when it was created. The problem is it seems Unraid's Docker installation got screwy during the upgrades because now when trying to start the containers I get the errors below (all via docker-compose, I don't use Unraid's web based Docker manager - this all worked beautifully before). How do I perform a factory reset/fresh start of Unraid's Docker installation? If that's not the best way to resolve the issues, please advise how. Error response from daemon: OCI runtime create failed: container_linux.go:367: starting container process caused: exec: "/docker-entrypoint.sh": stat /docker-entrypoint.sh: no such file or directory: unknown => [internal] load build definition from Dockerfile => => transferring dockerfile: 32B => [internal] load .dockerignore => => transferring context: 2B => [internal] load metadata for docker.io/library/alpine:latest => CACHED [1/4] FROM docker.io/library/alpine:latest@sha256:65a2763f593ae85fab3b5406dc9e80f744ec5b449f269b699b5efd37a07ad32e => [internal] load build context => => transferring context: 134B => ERROR [2/4] RUN echo "http://dl-cdn.alpinelinux.org/alpine/edge/testing/" >> /etc/apk/repositories && echo "http://dl-cdn.alpinelinux.org/alpine/edge/community/" >> /etc/apk/repositories && echo "http://dl-cdn.alpinelinux.org ------ > [2/4] RUN echo "http://dl-cdn.alpinelinux.org/alpine/edge/testing/" >> /etc/apk/repositories && echo "http://dl-cdn.alpinelinux.org/alpine/edge/community/" >> /etc/apk/repositories && echo "http://dl-cdn.alpinelinux.org/alpine/" >> /etc/apk/repositories && apk add --no-cache bash transmission-cli inotify-tools: #0 0.545 container_linux.go:367: starting container process caused: exec: "/bin/sh": stat /bin/sh: no such file or directory ------ failed to solve: executor failed running [/bin/sh -c echo "http://dl-cdn.alpinelinux.org/alpine/edge/testing/" >> /etc/apk/repositories && echo "http://dl-cdn.alpinelinux.org/alpine/edge/community/" >> /etc/apk/repositories && ec/dl-cdn.alpinelinux.org/alpine/edge/main/" >> /etc/apk/repositories && apk add --no-cache bash transmission-cli inotify-tools]: exit code: 1

It's tidier for me to have my homelab modularized, keeping roles/functions separate. Taking down the whole network just to troubleshoot one issue got old very fast for me.

I'm running Unraid 6.9.2 bare metal and it only stores my Plex media files (shared via NFS). I have Plex, etc. running in Docker containers in a Ubuntu Server VM on my ESXi physical server. The Unraid NFS share is mounted in the Ubuntu VM (/etc/fstab syntax below) then passed to the Docker containers via the volume feature. I'm constantly getting "Stale file handle" errors within the containers and the apps can not access the media files and folders. Restarting the VM fixes the problem momentarily (restarting the container by itself does NOT), but the error occurs again soon after. Why is this error occurring and how do I resolve it? /etc/fstab file on Ubuntu Server VM (Docker host): 192.168.0.20:/mnt/user/medialibrary /mnt/medialibrary nfs auto,nofail,noatime,nolock,intr,tcp,actimeo=1800 0 0 P.S. - the NFS mount options in fstab were copied over from my old TrueNAS setup (the media files use to be on a TrueNAS server, Unraid replaced that server)