AdoMe

The above issue was caused by a failing SATA port. No outward errors, but popping it to another SATA port took care of the issue.

wipefs -a /dev/sdc #No error here parted /dev/sdc mklabel gpt #No error here parted -a optimal /dev/sdX mkpart primary btrfs 0% 100% # Errors with Error: /dev/sdc: unrecognised disk label So the "mklabel" command never actually created the label.

I have a few 1 TB SSDs lying around and I'm trying to get the first one into unRAID for a cache drive after a 256 GB drive failed on me. My issue is that no matter what I do, I can't get them formatted or mounted. Any attempts to format through the GUI give me "Unmountable: wrong or no file system". Digging deep, I can't even format the drives at the command line. If I wipe the drive, it seems to wipe them OK, but no tools are able to partition or format them. Nothing errors out, but nothing works, either. If I use parted to "mklabel gpt", I get nothing. It's like the system ignores it. If I use something like gdisk to create a partition, it doesn't error out, but it doesn't write the partition, either. Diagnostics file attached. Any help would be amazingly appreciated. henry-diagnostics-20251130-1819.zip

Holy crap. I have no idea how I didn't see that in the past...

That's the problem. I can't remove the old one. I have no option to do so. I can't remove a drive from the existing cache pool, either. Or more specifically, if I CAN do it, I don't know how.

JorgeB, I apologize. Can you explain what you mean when you say "create on the pool device"?

Yes, I have everything migrated off, so the cache drive is now sitting idle. I just have no idea how to terminate the cache pool so I can recreate it.

I've now changed all Shares that were set to Cache to now be Cache -> Array. I've started the mover, but it's ridonculously slow. About 100 MB/minute. But it's moving. The only one I'm not sure of is my docker.img file which is at /mnt/cache/docker.img. Since it's not a share, I figure I'll have to stop docker, move the image, update the location, then start docker again.

I'm on unRAID 7.2.x. I had 2x cache drives. 2 SSDs of size 256 GB (sdb) and 250 GB (sdc) respectively. 256 GB (/dev/sdb) is failing from a hardware standpoint. I have a spare 1 TB SSD (sdd). I throw it in and added it to the cache pool. It's now part of the BTRFS pool. I have the data from /dev/sdb1 copied and backed up. I need to drop /dev/sdb entirely, but I cannot since BTRFS complains about "Too many wrong or missing drives". One solution said I can convert the BTRFS pool from Single to RAID1, but I can't find where to do this. Most of the documentation appears to be for unRAID 6.x. I'm not sure what information I need to provide to you all in order to help me out.

MowMdown, yeah that jibes with what I was seeing. I appreciate that. They should add the text from the mover script and make it part of the documentation. VERY clear cut.

OK, that makes sense. Looks like the files that do not move are all files that already exist. If it exists in the Array and the cache, the mover will just ignore it entirely, it seems. Good to know. I assume it will handle it properly when being written to /mnt/user and not /mnt/cache. I think I need to stop trying to be "smart" and just use the system as it's intended. Leave /mnt/cache alone and write it directly to /mnt/user.

For sure! I'll get back to you on that.

Except about 50% of them weren't moved. They were copied with the cache copies left on the cache drive. Hence my confusion. syslog was showing that the move was finished. I'm reading through your posted link above right now. It's already cleared up some confusion, let's see what else it has in store for me.

I'm trying to set up cache properly, but I'm having issues understanding it fully. The documentation I find are all for 6.x.x and apparently those settings have changed for 7.x.x. I have a share, "media", that I want cached. The data is currently stored on a Synology NAS that's a workhorse, but expensive to expand. It's also fast since it's RAID. I have dozens of terabytes of data that I'll be copying, so I figured cache would work best. for the initial transfers. Plus, it's a good time to learn about unRAID's cache. So old shares used to say "use cache" with a boolean toggle. That setting no longer exists in the Share Settings. The only thing I see now are "Primary" and "Secondary" storage. So I set it to Cache as primary storage, Array as secondary. But when I did, I noticed it did not create the share directory in /mnt/cache and I had to do so manually. No biggie, create it myself and fix perms/ownership. If I copy data directly to /mnt/cache/media/filename.mp4, then it gets copied over to /mnt/user/media when I trigger the Mover. But it's about a 50% chance that it will delete it from the cache pool after. I'm expecting the cache to be a temporary storage for however long it takes the mover to get the data over to the array. So what am I missing? Do I have a misunderstanding on how unRAID's cache works or is there a setting elsewhere that I don't know about that would enable functionality as I imagine it?

Apologies for not replying sooner. I went back to get proper diagnostic logs and after YET ANOTHER reboot, it started working. While nobody here provided a solution, I *DO* 100% appreciate the response.

THANK YOU! I didn't know about that. It's attached here. henry-diagnostics-20250220-0740.zip

unRAID 7.0.0, all packages updated. Every single container I try so far gives me output similar to the below. My docker.img is in `/mnt/cache`. I've also tried saving it to `/mnt/user/appdata`. I did this in an attempt to try different disks to make sure there weren't any disk issues getting in the middle of it. All drives have plenty of space. I'm unsure what to look for outside of this. docker run -d --name='binhex-plexpass' --net='host' --pids-limit 2048 -e TZ="America/Denver" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Henry" -e HOST_CONTAINERNAME="binhex-plexpass" -e 'TRANS_DIR'='/config/transcode' -e 'NVIDIA_DRIVER_CAPABILITIES'='all' -e 'NVIDIA_VISIBLE_DEVICES'='' -e 'PLEX_CLAIM'='' -e 'SHARED_NETWORK'='no' -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='000' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:32400]' -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/plex-icon.png' -v '/mnt/user/appdata/binhex-plexpass':'/config':'rw' -v '/mnt/user/media/':'/media':'rw' 'binhex/arch-plexpass' e49c4543033d91de3672d14504c13acb0f6e7e1ba5130789fc0d37c2b0ae5919 docker: error during connect: Post "http://%2Fvar%2Frun%2Fdocker.sock/v1.46/containers/e49c4543033d91de3672d14504c13acb0f6e7e1ba5130789fc0d37c2b0ae5919/start": EOF.

docker run -d --name='binhex-plexpass' --net='host' --pids-limit 2048 -e TZ="America/Denver" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Henry" -e HOST_CONTAINERNAME="binhex-plexpass" -e 'TRANS_DIR'='/config/transcode' -e 'NVIDIA_DRIVER_CAPABILITIES'='all' -e 'NVIDIA_VISIBLE_DEVICES'='' -e 'PLEX_CLAIM'='' -e 'SHARED_NETWORK'='no' -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='000' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:32400]' -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/plex-icon.png' -v '/mnt/user/appdata/binhex-plexpass':'/config':'rw' -v '/mnt/user/media/':'/media':'rw' 'binhex/arch-plexpass' 604959905b70df61750e28976d34a95296331af4939483f1bf6e77d9712aab42 docker: Error response from daemon: endpoint with name binhex-plexpass already exists in network host. The command failed. Not the same error, but this is what happens ever other time I've done this. If my main docker .img is fresh, I get the error on my first post. If I remove the Plex container and re-add it with the existing docker .img, then I get *THIS* error.

This installation is brand new, both for unRAID and plex. I'm unsure why it's failing. The log doesn't make sense to me. Full log is at the bottom, but the most relevant line is below. docker: error during connect: Post "http://%2Fvar%2Frun%2Fdocker.sock/v1.46/containers/ef381c9689c99f282de24bb3361e0e5d5ff11c5864b5e0b88f903d7aa60dd744/start": EOF. The command failed. Any help you folks can direct me towards, I'd be immensely appreciative. Pulling image: binhex/arch-plexpass:latest IMAGE ID [1298004660]: Pulling from binhex/arch-plexpass. IMAGE ID [7598295aa48a]: Pulling fs layer. Downloading 100% of 263 B. Verifying Checksum. Download complete. Extracting. Pull complete. IMAGE ID [719e8f2f6e10]: Pulling fs layer. Downloading 100% of 3 KB. Download complete. Extracting. Pull complete. IMAGE ID [562a2e7981e2]: Pulling fs layer. Downloading 100% of 1 MB. Download complete. Extracting. Pull complete. IMAGE ID [9211fb3bd118]: Pulling fs layer. Downloading 100% of 5 KB. Download complete. Extracting. Pull complete. IMAGE ID [2350cfe85633]: Pulling fs layer. Downloading 100% of 221 MB. Verifying Checksum. Download complete. Extracting. Pull complete. IMAGE ID [010377481244]: Pulling fs layer. Downloading 100% of 249 B. Download complete. Extracting. Pull complete. IMAGE ID [2315630d07a9]: Pulling fs layer. Downloading 100% of 2 KB. Download complete. Extracting. Pull complete. IMAGE ID [608edab9f75d]: Pulling fs layer. Downloading 100% of 2 KB. Verifying Checksum. Download complete. Extracting. Pull complete. IMAGE ID [9aac7d0aa6a3]: Pulling fs layer. Downloading 100% of 373 MB. Retrying in 5 seconds. Retrying in 4 seconds. Retrying in 3 seconds. Retrying in 2 seconds. Retrying in 1 second. Downloading 100% of 230 MB. Verifying Checksum. Download complete. Extracting. Pull complete. Status: Downloaded newer image for binhex/arch-plexpass:latest TOTAL DATA PULLED: 596 MB Command execution docker run -d --name='binhex-plexpass' --net='host' --pids-limit 2048 -e TZ="America/Denver" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Henry" -e HOST_CONTAINERNAME="binhex-plexpass" -e 'TRANS_DIR'='/config/transcode' -e 'NVIDIA_DRIVER_CAPABILITIES'='all' -e 'NVIDIA_VISIBLE_DEVICES'='' -e 'PLEX_CLAIM'='' -e 'SHARED_NETWORK'='no' -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='000' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:32400]' -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/plex-icon.png' -v '/mnt/user/appdata/binhex-plexpass':'/config':'rw' -v '/mnt/user/media/':'/media':'rw' 'binhex/arch-plexpass' ef381c9689c99f282de24bb3361e0e5d5ff11c5864b5e0b88f903d7aa60dd744 docker: error during connect: Post "http://%2Fvar%2Frun%2Fdocker.sock/v1.46/containers/ef381c9689c99f282de24bb3361e0e5d5ff11c5864b5e0b88f903d7aa60dd744/start": EOF. The command failed.