gundamguy

trurl gave a bit more clarity, but I believe that even if you don't have the super.dat file unRAID will see them as properly formatted and let you add them without formatting them. A backup of your USB isn't really required (other then the key) to restore your array from a clean start. At least that's the impression I've been given, if this is wrong I'd really like to know because it would mean I need to change a few things.

From a Linux terminal he did cat /proc/cpuinfo | grep MHz for the first section, and top for the second.

Be careful about holding on to a super.dat file for too long, if you've changed your array or parity since you backed up that super.dat restoring it could result in data loss. This has mostly happened to people who moved a parity disk to the array after upgrading the parity disk. In this case it works fine because you aren't planning to make changes to your array just clean out the junk on your boot USB. Also not sure anyone has said this year, back up your Key file. you are going to need it to register your copy again.

Yes, if you want to do that you need to make sure you set the share you download to be CACHE ONLY. If it's not cache only mover will move the files to the disk.

No ISO files for unRAID . I think he's talking about ISO's for VM's. Also sure you could do that, or you could put them on some other storage device and use Unassigned Devices to load them.

Yes I am aware of that however I wont be stoping the array unless I am leaving my place for an extended time period (vacation or something) Or is there somthing I am misunderstanding? It's totally up to you. It's kind of an all your eggs in one basket sort of issue, it's great when it's working, but if something goes wrong or you have to reboot unraid well now you've lost network access. If you are remote at the time, you won't be able to boot it back up until you are back physically in the same location.

Why can't you just download the file to your unraid machine? (There are plugins / Dockers for torrent services, and at a command line level wget should work.)

The only thing I could find is a comment from an Admin that says that hard links are not supported on user shares. (I think this is a limitation of hard links since they are required to be on the same volume, and not exactly unRAID specific)

If you want to change the existing data so that it matches these split levels then you are going to have to do some manual moving of files. I'm not sure if anyone has written a plugin to make this easier, but the unbalance plugin might do this?

Another thing that might be forcing it to that disk is the split level settings.

I assume you mean to use it as if it were a USB disk? If so, then no this is not supported. Not even with the unassigned devices plugin?

Nope. I don't need anything transcoded. I just need it remuxed into a different container. Handbrake won't do that. It can. Ok I'll be a little bit more helpful. Just set everything to pass though, and turn the logarithmic slider all the way down, and it's basically just a remux. Handbrake is basically just a GUI for FFMPEG anyway.

When you say you no longer have access do you mean to the webgui? It seems like you are having a DNS issue even though you can WOL the server... (can you though, are you sure it's booting?)

I think the answer to this question is... it depends on the nature of the failure.

Noticed something weird with Plex today. I had 4 strange files under my / directory today. sign_in sign_in.1 sign_in.2 sign_in.3 all contained the same information, and all seemed to be some sort of HTML file related to Plex (numerous Plex references) Did Plex make a recent change that has config files going to different places?

i would be extremely surprised if the recycle bin is not by-passed. Ransom ware rewrites files, it does not delete them. Yeah that is what I suspect as well. A couple of random thoughts. A lot of users have a set up where they have a cache drive and cache enabled shares. Which in effect results in reading from one directory say /mnt/user/movies and writing to another directory /mnt/cache/movies. I believe this is a product of our FUSE set up. My question is this, if one modifies a file in /mnt/user/movies does it modify in place to /mnt/user/movies, or is that modified file placed in /mnt/cache/movies. I suspect the former, but it would be great if it were the latter. If it works such that a file that is opened over SMB and modified is moved to /mnt/cache/movies then using rsync with the --ignore-existing option would allow all modified files to remain on the cache and not be updated over existing files. Then you could use a second rsync command to park those files in some sort of quarantine where they await user action (confirmation) before they are moved to the array. This of course only will work if there is a way to disable modify in place and force the creation of a working file in an alternative directory.

There are a lot of ways to do this. One way is to use a cron job and rsync. This thread does a pretty good job walking though how you would set this up.

Question: Does the samba recycle bin plugin give any protection against ransomware? Or would that be bypassed?

I can't help you with your other question, but to answer your first question. It depends on what your goals and concerns are. The major concern in this thread is that a Windows (or less likely a Mac) machine gets infected with ransomware that traverses the shares it has access to and encrypts the data on your Linux machine. If you don't allow that samba share to have write permission that ransomware running on the Windows machine can't modify the files on your Linux machine. This does not protect against your Linux machine getting infected with ransomeware. If this should be a concern or not is dependent on a lot of factors but for most users it's way less of a concern then an external machine with access causing problems.

Yes you can do that. The critical thing you need to keep in mind is the drive serial numbers. You want a list of the assignments and serial numbers (What is your Parity, what is assigned as Drive 1, ect.) so that you can properly reassign them.

Why is that? I've also found this to be confusing.

It's not going though SMB at all, so SAMBA's (SMB server) permission schemes aren't being applied. There is setting a file to be read only in Linux using chmod, and then there is setting SMB to deny write permission on a share... You are doing the latter when you change SMB settings. It's not actually changing the permissions on every file in that share. Also be very careful when mixing /mnt/user/xxxx with /mnt/diskx/xxxx if there is a collision (IE attempt to write to the same place) it'll cause data loss.

There are visual cues on main and dashboard. A spun down disk has a gray circle icon. You can check your settings on settings -> disk settings -> default spin down delay. Does this save life? Good question. It saves power...

Caveat: It's true that reading from an array drive doesn't involve the parity drive normally... if that disk is being emulated because of an error state then the parity drive will be involved.

FYI: The thing that actually finally fixed this for me, was using the guide on this Windows Support website to disable SMB 2 & 3 support, forcing it to SMB 1 for now... (until bugs are worked out between Samba and Windows. This might be fixed in the Beta that I'm NOT testing right now, since that is using a more recent version of Samba) How to enable or disable SMB protocols on the SMB client Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, and Windows Server 2012 Note When you enable or disable SMBv2 in Windows 8 or in Windows Server 2012, SMBv3 is also enabled or disabled. This behavior occurs because these protocols share the same stack. To disable SMBv2 and SMBv3 on the SMB client, run the following commands: sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi sc.exe config mrxsmb20 start= disabled Notes You must run these commands at an elevated command prompt. You must restart the computer after you make these changes.