Teeman

I don't want to change immediately, just add a new key. So that's why I want to do it manually.

Sorry to bump this ancient thread, but are these instructions still current? Also, do I need to change the key on the parity drive or does it not matter? Edit: I see above that I do not. Thanks

This might have to do with the way samba is configured on the client end to anyone who finds this in a search... Still trying to figure out what I need to do to fix it though. However, something changed with one of the newer versions of Unraid because I was able to find reports of this only happening after upgrading Unraid. So, I'm not entire sure what is going on. It's very annoying.

Remove any ports configured and use this in the extra parameters: -p 127.0.0.1:1234:1234

I have tried doing something like this: iptables -A INPUT -p tcp -s localhost --dport 1234 -j ACCEPT iptables -A INPUT -p tcp --dport 1234 -j DROP However, I can still access it via the LAN... I don't want it accessible from anywhere except localhost.

I don't want the port fully exposed on my LAN, it just seems like terrible security if anyone else is using the LAN. I am actually a bit surprised there isn't better security for this. I would like to just make an SSH tunnel so I can access it via localhost. Then I could do like # ssh -L 1234:127.0.0.1:1234 [email protected] Then connect with a web browser to 127.0.0.1:1234 from my workstation. There doesn't appear to be a way to do this unless I can do it with a specific network type. I saw guides for SSH tunneling to Unraid but they still assume the docker port will be fully exposed to the LAN.

I don't think you understood my first question. I mean a secure delete of individual files... aka "wipe". Not an entire secure erase of the entire cache drive. I just want it to do a "secure move", instead of a normal mv/rm. I want it to use something like wipe or shred.

1) I would like for the cache drives to automatically do a secure delete while moving to the main array, is there a way to do this? 2) Is there a way to make a second pool that will not be used for cache, that I can use only for docker containers? Thanks

After reading, I am a bit disappointed that I can't have two separate arrays/pools with their own parity drives. I have four brand new 18 TB clean drives and four old drives with data on them. Two of them being 14 TB and two of them being 10 TB My original plan was to use the four new drives with one parity, in one array. Then I would copy the data from the older NTFS drives onto that new array. Then I would add a second array with one of the 14TBs as parity. Since I won't be able to do this, how much of an issue will it be to add the old drives to the array later? Will the parity work more or less the same if I have one 18 TB and one 14 TB as parity. Will it still have the same amount of parity as it would if there would two separate arrays? It would be nice if this could allow for two drives to die and still have no data loss. And now after typing this, I think I would prefer having the parity protect all drives anyway. Thanks. Edit: One extra question I have is... Can I leave the NTFS formatted drives in the computer when installing UNRAID and will it clearly allow to me to select only the new drives to add to the array initially? I don't want to accidentally overwrite the old NTFS drives before copying the data off of them. I have backups, but I like having at least 2 copies of every file.

Or will I have to use the PBA or something.

So it is more of a bad hardware thing... OK. Good to know. I don't plan on using it for gaming or anything, just as a NAS and nothing more. I have tested RAM with memtest for days and will test again before installing Unraid. I learned my lesson about data integrity and overclocked RAM a couple of years go. I don't see how you wouldn't always get corruption in cases like that anyway. Thanks!

I thought btrfs was more or less immune to that unless it's data that literally was written less than 30 seconds before the power off or crash. Is there something different specifically about Unraid that makes corruption with btrfs more likey?

I am planning on setting up Unraid sometime relatively soon, and I would like to use Btrfs for at least the data drives (probably not cache drives though). The thing is I keep reading about people having issues with Btrfs on Unraid. Issues that I never see anyone have on any other setup. So what is the deal? Should I steer clear of Btrfs on Unraid? Is it not safe?

I am planning on setting up Unraid sometime relatively soon, and I would like to use Btrfs for at least the data drives (probably not cache drives though). The thing is I keep reading about people having issues with Btrfs on Unraid. Issues that I never see anyone have on any other setup. So what is the deal? Should I steer clear of Btrfs on Unraid? Is it not safe?