Leaderboard

Popular Content

Showing content with the highest reputation on 10/22/18 in all areas

  1. Well, you want one of us to go through all of the updates and pick out the ones that are important to you? Come on, give us a break. Everything in these updates is important to the various different users of Unraid for different reasons! Some are security updates. Some are updates to Samba, some address hardware issues, driver issues, incompatibilities, and some are new drivers for the latest hardware. It is easy enough to roll back if you find some issue or you can request assistance to solving the problem. But understand that waiting until some future version in the distance future may give you a lot of upgrade problems because of the small adjustments and tweaks that were detailed out as each update came out. You will have to make your own decision about about when to move up to a new version but I can assure you that keeping in the current major release version will give you the fewest problems over the long haul! (Plus, unlike other software, all updates are FREE!!!)
    3 points
  2. I've been using unraid for almost 10 years with only one small upgrade over 7 years ago. The server has been bullet proof and the MB/CPU have survived transplants 3 times as I grew. This summer I started ground-up rebuild to move from a 24 bay rack to a system that could reside in my office. This is a work in progress, I upgraded the Case/Drives/Fans over the summer and am now assembling the parts to replace the MB/CPU/RAM. I'm not going to make this a build-log, just going to edit it as I settle on parts and get things running. The basic idea came from snuffy1pro's "Shogun" build OS at time of building: 6.6.0 CPU: E-2176G Cooler: Noctua NH-DS15S Heatsink Covers: Noctua NA-HC3 chromax.Black.swap heatsink Covers Replacement Cooler Fans: Noctua NF-A15 HS-PWM chromax.Black.swap Premium-Grade Quiet 140mm Fan Motherboard: X11SCA-F-O Thermal: Graphite Pad RAM: 2xSupermicro 16GB 288-Pin DDR4 2666 (ECC) Case: LIAN LI PC-D600WB Drive Cage(s): 3xiStarUSA BPN-DE350SS-BLACK 3x5.25" to 5x3.5" SAS/SATA 6.0 Gb/s Trayless Hot-Swap Cage Note: I replaced the fans on the cages with Noctua NF-A8 PWM Premium 80mm and ran them to the motherboard along with the 3 Noctua fans on the back of the drive side of the case, all 6 fans are controlled by the auto-fan plugin and watching HD temps rather than system temps. Power Supply: Seasonic 650W 80 Plus Titanium ATX12V Power Supply with Active PFC F3 (SSR-650TD) SATA Expansion Card(s): LSI SAS 9207-8i Cables: Cable Matters Internal Mini SAS to SATA Cable (SFF-8087 to SATA Forward Breakout) (2x3.3' 2x1.6') Addon Network Card: ASUS XG-C100C 10G Network Adapter PCI-E x4 Card Fans: 2xCorsair ML140 Pro LED, Blue (1xML120); 3xNoctua NF-A14 PWM chromax.Black.swap Parity Drive: 12TB Seagate Ironwolf Data Drives: 5x10TB Seagate Ironwolf, 3x8TB Seagate Ironwolf Cache Drive: Samsung 860 EVO 2TB VM Drive: Samsung 970 EVO 250GB Total Drive Capacity: 74TB (67% used) Primary Use: Media storage and streaming (Kodi local, Plex remote) Likes: Love the look, very quiet even under load. Dislikes: Seagate drives in these trayless bays can "tick" a bit, sort of annoying in an otherwise silent system. Add Ons Used: Radarr, Sonarr, NZBGet, Organizr, DuckDNS and tons of plugins...I'm a nerd what I can I say. Future Plans: None at the moment Boot (peak): TBD Idle (avg): 70w Active (avg): ~90w Light use (avg): ~80w Disk Rebuild: 105w The highest usage I've seen was the 105w during data rebuild, even booting my windows and linux VMs doesn't push it about the mid 80s. More information to follow when I can order the CPU and swap the core of the system. Current view from the front (Will replace later with full pictures of finished project) System Side: System Side with Chromax fans and Heatsink covers: Drive side:
    1 point
  3. At this point in time, hardware transcoding with Plex in a Linux docker requires the use of an Intel CPU with an iGPU and Quick Sync Video support. If you want to transcode 4K/HEVC 10-bit (UHD)/H.265 you are going to to need at least a Kaby Lake generation CPU with iGPU (gen 7) or a Coffee Lake (gen. 8 ) CPU with iGPU. In the Xeon family that is an E3 12x5 V6 (Kaby Lake) or an E-21xxG (Coffee Lake) If your CPU can't do hardware transcoding of 4K video it can due brute strength transcoding in software, but, that is likely to heavliy tax the CPUs you mentioned. 4K transcoding requires a lot of CPU if not transcoding in hardware. For example to do 4K on my Xeon E3 1245 V5 (Skylake) CPU it utilizes all core/threads (4/8) at a continuous 85-95%. The dual E5 setup you mentioned may handle it better, but, it is limited to software transcoding and it will put a heavy load on your CPU(s). Hardware transcoding offloads much of the work to the iGPU so the CPU is only utilized at about 10-20%, sometimes, even less. Since you are limited with what you can do with Plex hardware transcoding under Linux/Docker, another option is to run Plex in a Windows VM under unRAID and pass through an NVIDIA or AMD GPU to do the transcoding. Assuming this is still accurate (and some say it is out of date), it's the Plex hardware transcoding guide.
    1 point
  4. Upgraded two servers with no issues. Drank a beer for each update. I need to have more Unraid server so I can drink more beer :)
    1 point
  5. I recommend to delete the files (make the folder empty) and then use the GUI to delete the folder. This will keep all configuration files in sync.
    1 point
  6. Try changing the access mode from RW to be RW:Slave or RW:Shared (Folder may also already have to exist - not sure)
    1 point
  7. Try it again. There was a blip in the feed for ~10 minutes.
    1 point
  8. In celebration of the Legalization of a certain recreational plant that came into effect earlier this week, I twisted one up and 6.6.3 installed very (very) smoothly.
    1 point
  9. Not to go overboard on exploring this situation, I'm working to gather all the same pieces in my current setup, with the exception of all the array drives, and just a few SSDs. Can't afford to screw up my main system. Furthermore, there seems to be several different things going on. One being, the migration of mpt2sas and mpt3sas. With those two converged, on the surface, nothing should have changed. One thing I came across was a linux tool called sg_unmap. It communicates vis SCSI rather ATA. I want to see if the issue is communication commands, but i'm unsure how to sideload packages on unraid. Lastly, the package in which the command/program fstrim resides, there is an update to that package 2.32 > 2.33 that mentions a few things about FITRIM ioctl failed. Does anyone know how to update this package (util-linux)? Package was released on the 19th of October (https://mirrors.edge.kernel.org/pub/linux/utils/util-linux/) The journey continues...
    1 point
  10. It's normal not to reduce available space, it's overwriting, it's like for example a windows bare metal install, it keeps doing small writes to disk but it's not always using more space. In my case my VMs and dockers write about 12 to 15GB/hour
    1 point
  11. 1 point
  12. The problem I wanted to solve was different to yours. I wanted to ditch unionfs from Nerd Pack as I have a strong suspicion it is causing problems on my server. To get rid of it I created a new rclone cache remote to handle uploading files to gdrive, whilst still presenting a 'union' for radarr and sonarr of what's on gdrive and what's still local. I still use a vfs mount for plex to play cloud files. I thought plex via the vfs mount wouldn't see new files uploaded via rclone cache or scan just the right directories, but this luckily proved to be wrong. The other problem I thought I'd have was how to get plex to see and play files that were local i.e how to expose just the local files from the rclone cache mount, as I wanted plex to play gdrive files via the vfs mount? I managed to fix this by decrypting and mounting the folder where the local files were encrypted and awaiting upload by rclone cache, and then adding this new mount of just local files to plex. Again, I lucked out as plex spotted any new local files almost instantly.
    1 point
  13. Also, let's clarify this if possible. The issue tagged in this bug report, assuming the title is correct, is not with *FTP*. It is with *SFTP*. Looking at the video from @nbenis106 above, it's clear that this is about SFTP (based on the credentials used in the video). Anyway, they're completely different protocols, although often with the same desired result. FTP always worked fine for me, including on 6.6.0 and 6.6.1. It is SFTP that doesn't work on 6.6.1 for me. The comment above "Unraid doesn't have a sFTP server built-in, what are software you using?" isn't correct unless there's a distinction being made between built-in vs not built-in that I'm missing. Poking around unRAID looks like the built-in FTP server runs on vsftpd (very common). I can't see how that's related to this issue, though. cc: @bonienl @truetype
    1 point
  14. I tried both methods (manually, and usb creator). Neither worked. I posted a bug report here:
    1 point
  15. Microserver gen7 is 64 bits, so you can upgrade to v6.
    1 point
  16. Newer versions of unraid are 64bit only. You should check to make sure your hardware supports that first. I am not certain at what version unraid switched away from 32bit, since it has been so long (multiple years now). The wiki link has this as the first steps, so be sure to follow that section closely.
    1 point
  17. See the wiki. https://wiki.unraid.net/index.php/Upgrading_to_UnRAID_v6
    1 point
  18. After executing the modprobe it87 force_id=0x8620 I go to System temp plugin, enter IT87 then press Load Drivers button and I have four options for processor temperature, the same for mainboard temp and only option for the array fan speed. So effectively I have something but I don't know what. Which temperature is processor temp, which is mainboard temp? What are others? As I have another issue (big one with my latin keyboard that I can't get working) I did not look further on this.
    1 point
  19. To enable hardware transcoding in Plex, do the following: This goes in the Extra Parameters in the Plex Docker config (you have to enable Advanced View on the docker edit page to see this). Note: this is for the linuxserver.io Plex docker (others Plex dockers may be different): Also, you need some entries in your go file like this (after entering these commands in the CLI): #Setup drivers for hardware transcoding in Plex modprobe i915 chmod -R 777 /dev/dri And in your Plex server Transcoder Settings page you need to enable hardware acceleration
    1 point
  20. CHBMB and others have a great setup, I use OPENVPN server on my pfsense box and it works great, I also use it as client to connect to Airvpn,org. However i also use the reverse proxy dockers, because i run nextcloud and it was much more simple to do this than configure pfsense (to me). Yes i had to expose some ports but pfsense has done such a good job at keeping bad things out that im happy.
    1 point
  21. Correct, I followed my dream back in August '15 and started a Business to Business I.T. consultation company. Preparing for growth in 2017.
    1 point
  22. Going to leave comments on the actual temps to others more knowledgeable. But, the problem with cooling in hotswap cases is that you need high static pressure fans (like the ones that came with the case). And high static pressure fans generally means loud (which the noctua's are not) And high CFM does not equal high static pressure (which is required to pull air through a very small crack)
    1 point
  23. Ok, instead of reducing the number of cache slots to 1, leave it assigned at 2. Then start the array and a rebalance should occur that converts the raid1 pool to a single. Good day Jonp! I'm in the same boat as MasterC. I've originally had one single cache drive (1TB WD Black) and I've recently purchased a 500GB SSD hoping to improve VMs/Dockers performance. I've mounted the SSD as a second cache drive and it seems to have created a raid pool of some sort. Now, I was hoping to remove my 1TB WD Black HDD and only use my 500GB SSD but when I try your suggested method by stopping the array, unassigning the Cache #1 (1TB WD Black), the cache won't mount anymore and it' shows "Unmountable" in my Cache section of Unraid. I was under the impression a rebalance would occur once removing the other but sadly, it doesn't. Is there a proper way to remove the 1TB WD Black HDD and only have the 500GB SSD without losing what's on the Cache drives? Thanks and have yourself a great day!
    1 point