Mr. Anderson

Figured it out. My Global Share Settings wasn't including all drives, and by adding the new drive to the array it was being omitted. I adjusted it to allow All by default and the data on the new drive showed up in the share.

This is not my first time to use this tool, but months ago I had a failing drive and I moved all my data off the drive which was mainly Plex data - movies, music, TV shows, etc. Getting the drive I wanted was a fiasco, but I just got a replacement which was larger than my parity, so the new drive became my parity and the old parity became my new Plex drive. I used unbalanced a few days ago to move all the Plex data from the other drives onto my old parity drive using Gather. The move is completed and all my movies, music and TV shows are on this drive. But now I cannot see any of the files or folders in the share, and neither can Plex. I can look at the drive and see all the files. Has anyone seen this before? What did I do wrong this time? unbalanced didn't give me any errors. All drives are xfs. I have run Docker Safe New Perms and rebooted after. Still not seeing these folders show up in the share in unRAID UI.

That's my thought too. Seeing the shipping box damage and the hard drive box just bouncing around, I had my concerns if it was DOA.

I've been running my server for about 10 years and have upgraded drives without a problem. I bought a new WD Gold drive and when UPS delivered it the box was crushed and ripped. I loaded it into the server, made sure all the connections were tight. I hear a clicking since installing this drive on booting the machine. It shows in the BIOS and also in Tools>System Devices, but it doesn't have the drive size. It won't show up to assign or in Unassigned Devices. This drive is not shucked so the pin taping shouldn't be required, right? I haven't had a chance to test it in another machine yet - I spent my lunch troubleshooting this. Other than trying another machine, is there anything else I can try?

Interestingly enough, when I did the dry run first, then did the move this error did not occur. I also selected every folder inside the Applications instead of the Applications folder itself. But it occurred twice when I selected the Applications folder itself and just did the move without a dry run.

I am also having this issue when I try to move 1 certain folder called Applications. This is where most of my Docker container settings are. I have stopped my Docker containers, and the Docker vDisk is stored on my cache drive, not one of my array drives. This is the last folder of my reiserfs drive I started with back in 2015. Everything else is moved. The drive only shows 37.2GB used, and any of my other array drives have more than plenty of space for this. It will get through the planning, then when I move to the Transfer tab, it spins for a while. Only if I refresh the page do I see this error. I left it for 8 hours at one point and saw no updates. I'm on 2024.12.23a and Unraid 6.12.13

Thank you! I started MongoDB expecting authentication originally. I was able to get my db users added and it's all working now.

I'm having a hard time getting mine up and going. When I run the command to create the second user, I get a message saying "uncaught exception: Error: couldn't add user: command createUser requires authentication. I've shut down the MongoDB Docker and brought it back up, rebuilt it following the instructions about 3 times, but I always come to this same error.