JonathanM

<shrug> This area is fine. No, this is not a feature. You can do it manually, with scripting to make it happen on schedule, but it will require that you educate yourself on how user shares function, and how not to mess things up copying to and from places on the array. Normally it's frowned upon to keep all your backups live on the same machine you are backing up, typically you would want them on drives in another physical location, separated as much as is practical. If you have that much free space on the array, maybe you should remove some drives and use them for a normal backup, as it would be much safer.

You need to fill in the Container Path with whatever you want to use as your access point inside the container, whether that is /media or /Media, or something. Whatever you put in that box is where you will navigate to inside of plex to pick up your content.

Start reading at Secure Access https://forums.unraid.net/topic/65494-unraid-os-version-640-stable-release-available/

Not quite. Have you used the SSL service in unraid yet? It provisions a hostname that decodes back into a local IP, which makes things complicated sometimes. If you don't have a static IP for Unraid in your LAN, then the hostname can point to the wrong IP when you reboot. I would advise setting a static DHCP reservation in your router for Unraid, that should keep things a little happier when you have to reboot.

I'm definitely not the authority on this, but I think if you delete and recreate the docker image file it resets the docker network. If you use the previous apps section of community applications, it's a 5 or 10 minute operation and all your apps are back the way they were.

Look up Spaceinvader One's youtube channel.

Since 6.8 includes Wireguard, I wouldn't expect a whole lot of attention being paid to these plugins in the future.

That works. Remember though, all attached storage devices minus the boot stick count towards your license. BTW, your signature appears to be badly out of date (at least I hope so). You can click on your name at the top of the forum and go to account settings to edit your signature and toggle whether or not you see signatures in the forum.

Just a WAG, but could you try renaming the server? I'm wondering if somehow windows is getting hung up on ftp being a reserved name of sorts.

Can you clarify what you mean by those two statements? We need to be sure what data is where before we give advice.

You may need to put it back the way it was before. Some USB - SATA interfaces alter how the drive is presented.

The GUI is going to be a little tricky. With the array STOPPED, change the visible slots for cache to 1. Then the option to format XFS will be available for the single drive you assign to it. Stop the array again, assign the other cache drive, format it, stop again, set slots to 2 or whatever, change to BTRFS and assign both drives. Or, do it the easy way and at the command line do a blkdiscard /dev/sd? twice, substituting the correct sd designation for the two drives as seen on the main array page. It was sdg and sdh in the info posted earlier, but drive letters can change, so verify immediately before doing the command. That will wipe them out and allow a fresh format.

If the board was shipped without a CPU or CPU socket cover, I would inspect the pins VERY carefully, ideally take a well lit macro photo from several low angles and make sure all the pins are even and clean. If you don't have a good digital camera with macro, a cellphone camera and an old fashioned glass magnifying glass work acceptably well. 1 bent pin can have weird symptoms. Things you would never dream could be related.

Not a clear answer, but a possible alternative. 1st, connect all three intact as they are now to the new system. Confirm the array functions as it did before. Shuck and install 1 drive, parity would probably be best for testing, and do a non-correcting parity check. If zero errors, you should be ok to shuck the other 2. If you get a bunch of errors, stop and build parity from scratch, then after you get a clean non correcting check you should be good to go to shuck 1 more, and rebuild it, do a non-correcting check, repeat for the last drive. Make no mistake, your data is at risk here, so if any of what I'm saying is unclear, ask questions. You really need to understand the why and the how of each step so you don't make an error that erases your data. Ideally, you should purchase 2 more drives, and use those in the array and leave your current data drives intact as backups. That way there is much less pressure and you have a good foundation of backups to build on.

NO!!!! If you format, all your data on any unmountable drive will be erased! If you format a drive, parity will be updated to reflect the format, and rebuilding will result in a freshly formatted drive with no files, just like you told it to do. https://wiki.unraid.net/index.php/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui So all your drives are being powered by just one string from the PSU? That may well be causing a voltage drop that would cause your symptoms. Ideally you would only use one connector from each cable so you have the most possible wires running from the PSU to the backplane.

Could we get arp-scan added? https://slackbuilds.org/repository/13.0/network/arp-scan/ It would be helpful as a troubleshooting step for situations like this. https://forums.unraid.net/topic/86246-unraid-680-unable-to-communicate-with-githubcom/?tab=comments#comment-799652

Mover only acts on cache to array disks (cache:yes) or array disks to cache (cache:prefer) shares. Mover never migrates from diskX to diskY. There are many ways to manually move items from disk to disk, the best method for you depends on your experience and comfort level with the system as a whole. Are you comfortable at a console command line?

PSU model? HBA? Hot swap bays? Heat control issues?

Nothing in the VM uses space in the docker image.

Edit the first post of the thread.

Since this report references rc5, I'd advise updating to 6.8.0 and see if the issue still exists. If it does, then a new report needs to be filed, with all the diagnostics and steps needed to recreate it so the devs can fix it.

Be careful with that way of thinking. Unraid uses all parity protected array drives to rebuild a failed drive, so the health of all array drives is critical. Don't include any questionable drives in the array. If a drive starts to show signs of failure, it needs to be replaced ASAP, in case one of your other drives decides to fail without warning.

Depends what level of license you purchased. How many drives do you have? pro.key is typical of the "unlimited", basic.key and plus.key for the other levels.

If you are using custom IP addresses then the answering port is controlled by the application. So, change the port in the program itself.

Maybe the package was used as a football during shipping.