Leaderboard

Popular Content

Showing content with the highest reputation on 04/10/19 in all areas

  1. Hi. I'm new to this forum and new to unRaid. In my late 50`s, not tech skilled. Been in the computer business since mid 80`s, actually launched Amiga 500 for Commodore back in ´87 I think it was. I am planning setting up UnRaid on a Supermicro Workstation (pressed purchase button today). Plex (4K transcoding) on Unbuntu with GPU passthru, a Mac vm, a Win vm, Roon Server, backup for friends and family, etc. So I will most likely ask for help from time to time. Looking forward to talk to you. Cheers, Frode
    2 points
  2. Yes After the initial loading of 2 files from the flash drive, every thing runs directly from RAM. Speed of the flash etc doesn't amount to more than around 1-2 seconds.
    1 point
  3. Not at this time. With unRaid and its extremely minimal writes to the flash drive, it will probably last longer than any hard drive you ever install. My first unRaid flash is now 6 years old and still running, whereas none of the hard drives I've had installed in that server still are.
    1 point
  4. Also an attribute to look for on WD drives, but just 1 should be fine, since the errors are old would keep it for now and just keep an eye on it.
    1 point
  5. Depends. I definitely wouldn't rely on it to keep data safe, but as a scratch drive, or backup of a backup, something like that, would be ok. It has NO place in the array, as you found out.
    1 point
  6. That’s been harder to assess lately for those of us who keep the OS updated with the latest stable or rc releases. Prior to UnRAID 6, my sever would run for months before it was rebooted because updates were far less frequent. I started with UnRAID 5 beta 14. I think my longest uptime was around 9 months. I am sure it was longer for others. With UnRAID 6, it’s usually a matter of weeks (the server was probably up for 3-4 months on 6.3.5) before I am rebooting for an update. Sent from my iPhone using Tapatalk
    1 point
  7. Back when I was running 4.7, I had more than 2 years uptime on one of my main servers. Nowadays I struggle to get more than 3 months before some security upgrade makes it a necessity, or at least highly advisable.
    1 point
  8. Grabbed a polo shirt and a sheet of stickers today (10 APR 19). I may go back for a coffee mug; forgot about them.
    1 point
  9. It should be sent immediately, check your spam folder.
    1 point
  10. Broadcasting and "downloading" are 2 different things. Playing a video from a network share is not a broadcast. A broadcast is a constant stream send out over whatever media (cable, wifi whatever). In this case you have only 1 file access, thats how cable tv, radio and i guess also most systems in airplanes work. The resolution basically doesn't matter if no encoding is involved. If the server has to reencode the video first before sending out, your CPU/GPU becomes the next important factor. Can it handle 40 parallel encoding sessions? For higher resolutions you need higher bitrates to have the same video quality. If you don't increase the bitrate and only the resolution the quality will getting worse and worse and the file size will kinda stay the same. The bitrate is an indicator how many informations can be stored for a specified time interval. 6000 bits per second.
    1 point
  11. See if stopping cache dirs makes a difference.
    1 point
  12. The equipment section can host pdf files. If you want a recipe to cross reference with the stock that you entered, you will need to enter and link those stock items manually. I suppose you could just copy and paste the recipe if you don't care about items being checked and pulled out inventory.
    1 point
  13. So basically you did everything but read the official documentation? See here for the most accurate info: https://hub.docker.com/r/linuxserver/openvpn-as Or here: https://github.com/linuxserver/docker-openvpn-as You may have missed the cap add statement. If it still doesn't work after that, check the logs (both the docker log and the log folder under config folder)
    1 point
  14. This is going to be an issue, as NordVPN doesn't support port forwarding. You will get very poor performance, and will not be able to seed completed torrents. PIA is the easiest to support for torrents.
    1 point
  15. A full desktop stack is not a small undertaking and would have a significant ongoing maintenance burden, for what may well be a very small percentage of the user base. I'm perfectly happy running headless with VMs for the times I need a desktop other than my laptop and wouldn't want to see Unraid migrate to essentially a desktop OS. One of the reasons the current desktop implementation is so limited is to keep the potential attack vectors down, hence the recommendation that the Firefox browser included isn't used for routine internet browsing. Like everything in tech/life, it's about using the right tool for the right job and it's my belief that a server OS isn't the right place for a full unrestricted access to a desktop environment machine on the same bare metal. Whilst I can see where the OP is coming from, and as a desktop Linux user myself, we also have to realise that a huge majority of the Unraid user base do not actually use/or wish to use a desktop Linux as their primary desktop computing OS, preferring to stick with Windows or MacOS. For the reasons above I can't see that this makes a lot of sense either on a practical or commercial basis for LT to dedicate resources to, however, I don't work for LT and this is purely my own point of view. It's possible (although I suspect highly unlikely) that @limetech pick this idea up and run with it. But I wouldn't hold my breath.
    1 point
  16. Holy moly, php7-pecl-imagick has a ton of dependencies and the size of all apps installed jump from 156MB to 233MB. So I'm not going to add it, but, you can create a file on your host called 90-config, with the following contents: #!/usr/bin/with-contenv bash apk add --no-cache php7-pecl-imagick and then map that file on the host to location in container: /etc/cont-init.d/90-config (add new path in container settings) That will install it during container start and will survive container recreation as long as the file on the host is still there
    1 point
  17. In general no, there's no problem mixing SAS and SATA drives in the same controller and/or expander.
    1 point
  18. Edit the container, then edit the path that has the host mounting with the UD mounted path, then change the mode to be either RW,slave or RO,slave depending upon your circumstances
    1 point