JonathanM

@SpaceInvaderOne, this thread really needs to be policed better. If we don't watch it, it's going to start showing up in web searches for the magic phrase, and that would be a bad thing to bring attention. I'm sure @trurl is getting rather tired of dealing with mod editing posts on a daily basis.

There's your answer. Without a valid port forward through the VPN tunnel, nobody can initiate a connection to you.

LOL. Like many things in life, security is a continuum with many degrees. For some, the only reason to use encryption is to be able to safely EOL old drives or RMA bad drives without worrying about where those drives end up. At the other end of the spectrum, you have people that shut down and lock their system every time they finish using it, only entering a long passphrase from memory at the immediate point of use and only unlocking it to do the immediate operation at hand. You can't please both sets of people at the same time. Where you want to set the default mode is up to you. Full paranoia mode is no fun, but neither is getting your system hacked.

Unraid will only disable as many drives as you have parity drives, so after you correct the hardware issue and unraid can see all the drives again, it will allow you to rebuild the first failed drives. There may be some corruption, but likely not much, as the dropped drives can't have been written to. You can't start the array with too many failed drives, and I think the array goes offline if it exceeds fault tolerance. You are in an ideal place to test that scenario, by setting up a test array with only 1 parity and 3 data. Fail 2 data drives and see what happens. If you reattach the failed drives and any slots show unmountable, try running the file system checks in maintenance mode.

No, that's not it at all. When a drive can no longer be accessed by unraid for whatever reason, all activity to that drive slot is emulated. Since there are writes to the file system metadata when the drive slot is unmounted, parity is guaranteed to be out of sync with the actual physical drive. So, to answer the title to the thread, there is no way to add a drive back that has been disabled without rebuilding it, unless you don't care about any writes that happened after the disabling event. You will still need to correct parity for all changed bits, which may be anywhere on the drive, so a full correcting check is needed. That will take roughly the same time as a rebuild anyway. Parity is calculated across the entire capacity of the drive from start to finish, without regard to content. If there have been NO data writes, then the only changes will be to areas close to the beginning of the drive. If something happened to be written to the portion of the drive after you cancelled the parity correction, then that area of parity would be invalid and would cause corruption if a different drive failed out before you got parity back in sync. Normally when the array is operating you would not know for a few minutes that the drive has been dropped, and even after it's dropped the array will allow reads and writes to the slot without error, so you would pretty much be guaranteed to lose something if you readded the drive without rebuilding. Unraid doesn't drop a drive unless a write fails, so you are going to lose that specific write, and any subsequent ones as well.

Download a live iso of gparted. Set that iso as boot for the VM. Run gparted, move and expand partitions around as needed, reboot, done.

So do you have backups of all high value data stored elsewhere? Fault tolerance provided by a NAS is not a backup, plenty of ways to lose or corrupt data without a drive going bad.

I realize these aren't consumer grade drives, but I think you are about $10 too high, considering brand new warranteed 500GB drives aren't much more than $50 each.

What model was it?

That seems like an incredibly risky procedure. What sort of backups do you have in place should you lose data trying to do this? Perhaps it would be wiser to purchase a few new much larger drives and start the unraid array with new disks, 10TB seems to be the new sweet spot for pricing this season.

Yes, in the xml view. I don't know if the boot order functionality has been fixed in form view or not, but changing the xml works fine. @bonienl?

Perhaps the user has other folders in Films that he doesn't want to expose to Plex.

Sure. It will probably be a fair bit slower though.

Manual. Fastest would probably be command line, using MC or rsync. Source would be /mnt/disk3, destination /mnt/disk(X) where X is the disk number with enough space.

Yes, @binhex has a full lineup of VPN enabled containers.

tldr; L does not mean lower overall consumption, possibly more power over time because the CPU stays at full (limited) throttle for longer to accomplish the same task. The only reason to favor the L version of the SAME PROCESSOR NUMBER is if you don't have the heatsink and fan capacity to dump the peak load.

Look through some of the videos here. https://www.youtube.com/channel/UCZDfnUn74N0WeAPvMqTOrtA

Or, set a new config and build parity with all the disks. You will be unprotected from drive failure until it completes, so not the safest option, but much faster. Copying then adding keeps parity valid and allows you to compare the files to be sure the copy was successful. Slow, but safe.

This. When a write fails, unraid disables the drive and all further writes to that slot are done to the emulated drive calculated from all the other drives. What was on the disabled drive is no longer used at all, and to put the drive back in the array requires rebuilding the entire drive. If you want any kind of informed advice on how to proceed, you need to attach the diagnostics zip file to your next post to this thread.

It doesn't, it only covers 2 drives, but any 2. All the rest of the drives are used as well. If you have more than 2 failures, 1 for each parity, then you will lose the data on all the failed disks. Parity doesn't hold any data, only the answers to the equation formed by all the other drives. All remaining drives are used to emulate the missing one, or two if you have dual parity.

That's an unofficial build, and while they try to make it as close as possible while adding nvidia support, it's not completely the same code as the limetech build. You need to duplicate the issue and post diagnostics with the official rc3.

This. recipe for disaster. marvell cards are bad enough, add a port expander to the mix...

Somewhat. What condition would reset the total?

I can confirm. RC1 works fine, RC3 does not. Different android smb file manager, ASUS File Manager on Galaxy S7