gundamguy

Duplicate files can still happen. /mnt/disk1/Video/BigBuckBunny.mkv /mnt/disk2/Video/BigBuckBunny.mkv Would only show up one time when looking at the user share IE. /mnt/user/Video/BigBuckBunny.mkv I think this still works.

No it totally would not. So yeah, I mostly brought it up because it leads me to believe that the CPU requirements to handle the in-home streaming part must not be too high. The server needs to have a pretty beefy CPU but the client seems like it would be ok having something that you could passively cool.

You know that is a good question. I've heard the capabilities of the client don't have to be that robust, but I'm not sure what the recommended specs are. I know steam also pushed out it's own Streaming Client Machine last fall called the SteamLink which is passively cooled and about the size of a 1 inch thick credit card... so I would imagine the requirements are pretty low. I'd see what you can find in the In-Home Streaming community on steam.

I see you found the answer, the answer to part A is well sort of... if you can add the launcher to steam it'll work with in home streaming. So maybe? Not sure if it will work with everything. Also you can totally stream from windows to Linux OS or windows to Mac, it is recommended that your using Windows as your server though because it has better support, and works better from what I've heard.

This isn't a horrible plan, but it wouldn't work for me. Any plan is going to have some element like this though. rsync can be made to do incremental backups by hard linking to files that were unchanged, can we use this somehow to create "snapshots" of sorts in some way? What I would really love is a redirected write in Samba, read from X directory, write to Y directory. If this sort of thing could be made to happen, and even writes to existing files resulted in a new version of that file at Y, then I think protecting the array from ransomware would be pretty easy.

Have you considered giving Steam In-Home Streaming a try? From my experience it works pretty well, they are still working some kinks out... and by that I mean it works really well, but they are working on perfecting it.

Jumperalex and Helmonder, that was actually very similar to the idea I had in mind. Like Helmonder said it would be easy to include the ignore-existing flag in mover, then have a second move step that moved the remaining files to a "Jail" of sorts awaiting positive confirmation (or some variation with incremental backups or something, lot's of options here.) The problem as far as I can tell is actually getting a share to be Read & Write but forcing ALL writes to the cache. I'm not sure if that's something that can be done, and even if it could, I'm not sure that solves the problem of how ransomware actually works.

First you should never have your OotB unRAID server on a DMZ, or fully open to the internet. Yes hackers and sniffers would tonally be interested in your server. People have posted logs with attempts to log into via SSH every couple of seconds when they had that open to the internet. I believe you are asking "If I install something like Plex and forward ports for Plex to have intrenet access is that a risk?" The answer is yes, but it's a standard risk that everyone that uses Plex takes. Someone might find security issues with Plex that allows exploitation, so you are really relying on the security of that app.

I think the major hurdle here is, that "Read & Append" or "Read and New Writes Only" isn't a permission set that exists in Linux currently... so it would take significant efforts to make that happen. Also BubbaQ I'm doing the same thing as you, expect in a few shares like iTunes which other computers need to log into... Question about Securing the Root though, by default unRAID ships with root having no password, if you add a password does it prompt you every time you bring up the webgui (it would be sweet if there was a way to avoid that but still secure root), in addition how did you set up your non-root maintainer?

Not from the GUI. Another post I have made about it here. In general support https://lime-technology.com/forum/index.php?topic=48643.0 I was a little confused by what you wanted with this originally as well, but now that I have a better understanding it makes a lot more sense to me. I think this would be a nice but not-critical feature to have.

I'm pretty sure Plex does the same thing.

IMO it's a design failure to have your first and second copy co-located in the same machine. Ideally they won't even be at the same physical address to reduce the risk of fire / water / other natural or unnatural disasters. It's hard to achieve this ideal I realize so I'm not suggesting you don't make a back up. In this case you can use plugins to mount disks outside of the array (not parity protected), back up to a another computer at the same physical address (could be parity protected depending on that computer). You can write a script to do the backups automatically and if your really clever you can even do incremental backups that work like Timemachine. One of the best and worst things about having a Linux machine is the sky is basically the limit, the only question is if you will know how to accomplish what you set out to do.

I think it's important to clear up that writes are redirected to the cache, data that is on the array and being read is read from the array, data that is on the cache waiting to be moved to the array will be read from the cache, but the data from the array isn't redirected though the cache for a read operation. Also the most common reason for using a cache at this point is to have a disk outside of your array for the purpose application storage and operations. This keeps your array disks from spinning up all the time, it can also greatly improve performance of some apps.

I think most modern CyberPower UPS's also works with APCUPSD... oddly like Squid said APCUPSD doesn't have a great list of supported UPSs.

I have been using Emby for over a year now and I have not had 1 hiccup. Very active development, great community, very frequent releases, feature rich, GREAT KODI plugin (which does centralised database management across multiple KODI / Openelec devices without having to mess around with an instance of MySQL). If a users main aim is centralised database management, then I don't think there is a better solution than Emby. > Install Kodi or Openelec on client device > Install Emby Docker > Add Folder to Emby > Install Emby Plugin => Emby Plugin searches Network, finds instance of Emby and auto configures and sync's media library into Kodi. > Done. No messing with database versions as KODI gets upgraded. FAST incremental Sync. FAST re-scan. No metadata issues. Supports streaming and direct play (e.g. via SMB). Can't fault it. Just m2c. Glad to hear Emby is coming up in the world. There were still some kinks to work out when I last looked into Emby and they were missing a key feature (ipad support was bad.) It showed a lot of promise so I am glad that they came though on a lot of it. I might have to go back and reevaluate my ecosystem again this summer and see if I want to make a switch.

Emby is an opensource Plex basically. They both use ffmpeg to transcode (with the Plex version being a slightly modified version of ffmpeg basically). The man difference is the ecosystem, Plex has a solid ecosystem which pretty much is consistent across platforms. This is actually a pretty recent change as some platforms were really far behind until earlier this year. Emby not so much. At least when I last looked into Emby about a year ago.

What exactly is a parent / child share, and what is your goal in creating one? (I ask because there might be another approach that does work)

Are there any hard limits on the banner size, I've seen mostly the same width, but I've seen a few different heights.

Just want to mention that an array of SSDs is not recommended or supported. Trim operations have a tendency to invalidate parity (or so I've heard)

Maybe? It depends on what your split level and allocation methods are set to be.

This seems like it would be a pretty hard problem, so I'd be interested to know if any NAS solutions allow this currently?

There is a way to disable to generation of .DS_Store and ._* files on remote shares.... that seems helpful for the people who don't like seeing these entirely harmless files.

Yeah i figured it wasn't an issue. It's more of an annoyance really. my /tmp folder is root with 777 permissions. Now I do have plex running as a custom user unraid-plex instead of root. Is that what's doing it?

When I ssh'd into my unRAID server I found a copy of sign_in again on the root directory again. I think it got created when I updated Plex. My configuration files should be going to a place on /mnt/cache/ I'll if I can provide more info when I'm home this evening. I don't know that this is a problem, it's just odd to see Plex breaking out of the configuration location I set an creating files in root.

Agreed. Just don't want people to think that if they didn't do a full backup or any backup of the flash drive that they would lose all there data.