Bmalone

Since there wasn't any data on the disks, I followed the procedure below to remove a disk and change the array to remove those disks. Everything was fine when I restarted the array for about 45 minutes and then I started getting all these errors that my unraidata share was still looking for the removed disks. I can't delete any shares, run diagnostics, format a disk, parity says it's running but there is no percentage progress showing, and it's basically keeled over and died. At least I have the backup server now so I can move everything off, wipe it, and start again from scratch. I don't know if the documentation needs to be updated or if there are fundamental issues with Unraid, but removing disks was a complete fail. Below is what I got in the 'fix common problems' plugin. I've tried to follow the guidance, but Unraid just hangs and doesn't do anything. Diagnostics has been running for 20 minutes now, but if it does complete, I'll post it here before I wipe the install and begin again. Removing data disk(s) -------------------------------------- Removing a disk from the array is possible, but normally requires you to once again sync your parity disk(s) after doing so. This means that until the parity sync completes, the array is vulnerable to data loss should any disk in the array fail. To remove a disk from your array, perform the following steps: Stop the array (optional) Make note if your disk assignments under the main tab (for both the array and cache; some find it helpful to take a screenshot) Perform the Reset the array configuration procedure. When doing this it is a good idea to use the option to preserve all current assignments to avoid you having to re-enter them (and possibly make a mistake doing so). Make sure all your previously assigned disks are there and set the drive you want removed to be Unassigned Start the array without checking the 'Parity is valid' box. A parity-sync will occur if at least one parity disk is assigned and until that operation completes, the array is vulnerable to data loss should a disk failure occur. ------------------------------------------------------ Reset the array configuration ------------------------------------------------------- you can reset your disk configuration from the new config page Reset the array configuration you can reset your disk configuration from the new config page If you wish to remove a disk from the array or you simply wish to start from scratch to build your array configuration, there is a tool in Unraid that will do this for you. To reset the array configuration, perform the following steps: Navigate to the Tools page and click New Config You can (optionally) elect to have the system preserve some of the current assignments while resetting the array. This can be very useful if you only intend to make a small change as it avoids you having to re-enter the details of the disks you want to leave unchanged. Click the checkbox confirming that you want to do this and then click apply to perform the operation Return to the Main tab and your configuration will have been reset Make any adjustments to the configuration that you want. Start the array to commit the configuration. You can start in Normal or Maintenance mode.

Ok, so using File Manager, selecting the folder Media (in my case) which has TV and Film subfolders, and moving it to another disk as per the images? Also, I just noticed that despite the disks saying there is 126GB of data used on the drives I want to use, the folders are empty. is this expected?

Just to be clear, you're suggesting to manually move any files on those disks to the appropriate shares and that will not have any unintended consequences?

I bought a backup server which I need to use some of the disks in my main server for. When I first set up Unraid I was using the high-water method before I realized the fill-up method works better for me. I have 143TB of usable space across a number of disks where most of the data is on 3 disks. I want to remove 5 disks (3 for data and 2 parity) for my backup server. What is the recommended way for moving this data to the other used disks in order to free up those disks for use in my backup server?

Today I tried to follow spaceinvaderone's instructions to route my traffic through my Deluge VPN. I followed his instructions, but it seems they are pretty far out of date. I saw Binhex had some information about forcing IP tables when using privoxy so I tried that as well. I tried using a custom network, a bridge network, adding a proxy in Sonarr, and every combination I could think of one step at a time, testing, and then making another change and testing, and so on. The traffic is getting routed through the VPN and the IP's are the same, but no UI when I use the host IP and the port I added to Deluge that Sonarr is using. So I've now brought the configs back to the one's recommended by spaceinvaderone, checked it is routing correctly, and since I'm out of ideas, I've come here. This doesn't seem like a very complex thing to do; is there no up to date guide as to how to configure this? DELUGE docker run -d --name='binhex-delugevpn' --net='bridge' --privileged=true -e TZ="America/Chicago" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Goathead" -e HOST_CONTAINERNAME="binhex-delugevpn" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='redacted' -e 'VPN_PASS'='redacted' -e 'VPN_PROV'='pia' -e 'VPN_CLIENT'='openvpn' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='yes' -e 'ENABLE_STARTUP_SCRIPTS'='no' -e 'LAN_NETWORK'='192.168.30.0/24' -e 'NAME_SERVERS'='84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1' -e 'DELUGE_DAEMON_LOG_LEVEL'='info' -e 'DELUGE_WEB_LOG_LEVEL'='info' -e 'DELUGE_ENABLE_WEBUI_PASSWORD'='no' -e 'DEBUG'='false' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8112]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/deluge-icon.png' -p '8112:8112/tcp' -p '58846:58846/tcp' -p '58946:58946/tcp' -p '58946:58946/udp' -p '8119:8118/tcp' -p '8989:8989/udp' -v '/mnt/user/downloads/incomplete/':'/data':'rw' -v '/mnt/user/appdata/binhex-delugevpn':'/config':'rw' --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-delugevpn' 89232f89a5bdbcc4c91637007b3c53a19cc922c99090cb41d0cac6b5d23a0c41 The command finished successfully! SONARR docker run -d --name='binhex-sonarr' -e TZ="America/Chicago" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Goathead" -e HOST_CONTAINERNAME="binhex-sonarr" -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8989]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/sonarr-icon.png' -v '/mnt/user/downloads/':'/data':'rw' -v '/mnt/user/unraiddata/tv/':'/media':'rw' -v '/mnt/user/appdata/binhex-sonarr':'/config':'rw' --net=container:binhex-delugevpn 'binhex/arch-sonarr' 269128ea2d045cb29a5ac558f4b3566c6366b4b8a491ec84795c4af972873348 The command finished successfully!

So check this out. Below you can see 2 views of the same share, one being viewed in Unraid GUi and the other in Explorer over SMB. The 'Downloads' folder is visible in SMB, but not in Unraid. How can this be explained? The share is public and all permissions are set to RW. There must be a bug here.

The unraidata share disappeared again. I have 2 x 36 bay NAS' and this is really making me question whether Unraid is reliable enough to continue investing in.

So Plex keeps losing access to the TV share only. Every time I set one or all shares to have ‘Nobody’ as owner and to have RW access, plex works fine. 10-15 mins later I can see it scan and the number of TV shows starts reducing. I stop the container, reset the permissions, and plex scans back the TV shows, but then 10-15 mins later it all starts again. Jellyfin has no issue. Is there any reason you can think of that UNRAID won’t allow me or decide who owns share and folders and what the permissions are?

Since the official Plex image uses /data by default, instead of /media, I thought I better leave it as is and only mapped the subfolders for the non-TV and non-film libraries and it worked. So I'm sorted now. Thanks so much for your help. I spent all weekend trying to get this to work to no avail.

I will run it and report back. However, I have an update. Your comment about permissions got me thinking. The shares were owned by my user account. I switched the permissions to 'Nobody' and all of a sudden Plex lit up with scanning activity. I just added the mnt/user/unraiddata:/data as you suggested. Plex seems confused as to what belongs where as I have TV, films, sports (F1, MotoGP, etc), and miscellaneous (extras, how-to-videos, random stuff I want available with a player). Also, there are less films discovered than I have, but it's still scanning. I have well over 5,000 films and over 500 TV series', so I think it should at least sort out the films and TV after it's done scanning.

I'm not familiar with that tool. Didn't find anything obvious Googling it or searching CA. Can you clarify?

Unfortunately it's the same behavior. It adds it to the navigation, but it can't see anything and a scan completes immediately and doesn't find anything.

Plex does have a folder for Movies under my server, but it's empty and a scan completes almost immediately. Same behavior consistently.

I thought you meant when I was editing it. In Plex, when I navigate to the library, the media folder is right there. /media

/mnt/user/unraiddata Isn't that what you suggested?

That was my misunderstanding. By the way, originally I did have a map to /user/unraiddata but deleted it as I was trying to simplify. It still can't see any media. docker run -d --name='Plex-Media-Server' --net='br0' --ip='192.168.30.34' -e TZ="America/Chicago" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Goathead" -e HOST_CONTAINERNAME="Plex-Media-Server" -e 'PLEX_CLAIM'='claim-RXRxSmBgPmXozLRcJ6n2' -e 'PLEX_UID'='99' -e 'PLEX_GID'='100' -e 'VERSION'='latest' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:32400]/web' -l net.unraid.docker.icon='https://raw.githubusercontent.com/plexinc/pms-docker/master/img/plex-server.png' -v '/mnt/user/unraiddata/':'/media':'rw' -v '/mnt/user/appdata/Plex-Media-Server':'/config':'rw' 'plexinc/pms-docker' 7081ba005873e821e326b47849a6d3cbf97b067984060bc08d78d3550f5a7b13 The command finished successfully!

Didn't make any difference. docker run -d --name='Plex-Media-Server' --net='br0' --ip='192.168.30.34' -e TZ="America/Chicago" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Goathead" -e HOST_CONTAINERNAME="Plex-Media-Server" -e 'PLEX_CLAIM'='claim-RXRxSmBgPmXozLRcJ6n2' -e 'PLEX_UID'='99' -e 'PLEX_GID'='100' -e 'VERSION'='latest' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:32400]/web' -l net.unraid.docker.icon='https://raw.githubusercontent.com/plexinc/pms-docker/master/img/plex-server.png' -v '/mnt/user/unraiddata/Films/':'/media':'rw' -v '/mnt/user/appdata/Plex-Media-Server':'/config':'rw' 'plexinc/pms-docker' 50ff81c3fbf0636ef89edcbe1778f2c435ba2d26b834479f58ad395b33abad2c The command finished successfully!

You think? I can rename Films to films, but I'd be incredibly surprised if that's what's causing the issue. It's not seeing either. I also had other folders for other media and it didn't see those either. I can't get any of the other imagine versions to work either, only the official Plex image. That's the only one that will actually run.

Other than the shares randomly disappearing from time to time, yes, they are viewable over SMB. Unraid doesn't allow me to upload or download anything using Finder, and viewing the shares in Finder usually works but not always. Explorer over SMB is always fine. I also installed Jellyfin and it worked without any issues first try. Jellyfin sees everything.

JFYI - I since deleted the GPU config to try and simplify it. docker run -d --name='Plex-Media-Server' --net='br0' --ip='192.168.30.34' -e TZ="America/Chicago" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Goathead" -e HOST_CONTAINERNAME="Plex-Media-Server" -e 'PLEX_CLAIM'='claim-RXRxSmBgPmXozLRcJ6n2' -e 'PLEX_UID'='99' -e 'PLEX_GID'='100' -e 'VERSION'='latest' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:32400]/web' -l net.unraid.docker.icon='https://raw.githubusercontent.com/plexinc/pms-docker/master/img/plex-server.png' -v '/mnt/user/unraiddata/tv/':'/media/tv':'rw' -v '/mnt/user/unraiddata/Films/':'/media/films':'rw' -v '/mnt/user/appdata/Plex-Media-Server':'/config':'rw' 'plexinc/pms-docker' 00080f4b59ec95869c6bdbcab6c11156047372298f6bb290edc8ec29b85dd89e The command finished successfully!

My media share randomly disappeared again. Can't be seen from Finder or Explorer. Also, Finder usually has access to the share, but cannot upload files at all, even in safe mode. goathead-diagnostics-20240312-2022.zip

I migrated PMS from my Synology to a new Unraid server where I’m running PMS as a Docker container. The migration worked perfectly, except it won’t recognize any new media. When I try to scan, it just completes almost instantly and no new media is added. I’ve checked the container paths and host paths many many times and it all looks correct. The only option I have is to just delete the PMS and start afresh. Maybe I’m missing something simple. Anyone have any ideas what I could try? I can see all the content that I had on my Synology when I stopped it for the migration, but I've added a lot of new media and none of it is being picked up. I also noticed some of my media folders such as 'tv' and 'films' seem to randomly duplicated, albeit they're empty. I chucked it up to being an Unraid bug but maybe it's related. Despite the container being immutable, I thought that if my container paths were mapped to my host path where my tv and films are that it would be able to pick up new media. Did I assume too much? goathead-diagnostics-20240312-1801.zip

I'll give it another go. Thanks

a Samsung 990 NVMe drive.

I've been having all sorts of issues with the firs VM I created, so I followed the instructions to drain the cache to the array. It worked for one cache, but not the other where my Domains and AppData shares were living (yes Docker and VM services were stopped and no downloads or transfers were happening). My plan was to create a new VM, and then when it's working, I'd delete the old VM and image and format the cache drive. Strangely, as I was working on this I lost access to the server on my Mac and it would just hang. It also broke Finder where Finder wouldn't work at all, and even trying to save an email would crash Outlook as soon as you tried to save it to the file system using Finder. So when I create the new VM, it just hangs. Previously when I was creating my first VM it all happened pretty quickly, and there also also loads of timeout errors in the logs that make no sense to me. In the error logs the 192.168.30.254 IP is my Mac with no browsers logged into Unraid, Finder is not open, and it's booted in safe mode, so I have no idea why there are so many connection errors. As soon as I try and create the VM, the whole server hangs and I have tom reboot it. The only difference I can think of from the prtevious VM creation is I've selected the GPU for video and audio, I'm using Win11 instead of Win10, and I'm adding some Unraid shares to the VM. I'm considering moving all the data off again and wiping everything and starting from scratch again if I can't pinpoint these issues, so any other potential avenues of investigation would be appreciated. Creating a Win10 machine with no GPU works fine, except it freezes all the time. It seems adding the GPU is causing the VM service to crash. As soon as I add it to the config and apply it, the service hangs. I will try creating a Win11 VM without a GPU configured. goathead-diagnostics-20240309-1745.zip