tdallen

Members
  • Content count

    1094
  • Joined

  • Last visited

Community Reputation

1 Neutral

About tdallen

  • Rank
    Advanced Member
  • Birthday

Converted

  • Gender
    Undisclosed
  1. The 500gb drives are undoubtedly quite old and slow, and the 1gb ones may not be much better. Is investing in some more SSDs for cache/VMs plus a larger hard drive or two an option?
  2. I happen to agree that the unRAID Admin UI should support HTTPS, but comments from posters like @johner make it sound like all we need it HTTPS on the UI and suddenly unRAID is secure. That's not true, and I suspect VPN will continue to be the recommended remote management solution even after Limetech implements HTTPS at some point (just my POV).
  3. Yes, VPN is the recommended approach. Even if unRAID supported HTTPS I suspect it would still be the recommended approach (see the " unRAID is by no means a secure operating system " comments above).
  4. Well the main consideration is how much data you want to store. Assuming that you can store everything you need in 8TB of effective storage space I'd go with 1 parity drive and 2 data drives. After that 1 parity/1 data is a special case, but once you add the second data drive you're into normal unRAID operations. Assuming you go with one parity drive and 2 data drives the remaining drive will be available as a spare when (not if) you loose one of the other drives (I like the idea of a spare). You could also use it to play with dual parity in the meantime as a learning experience. FWIW, I also maintain the 8TB drives offline/offsite approach for critical data.
  5. I agree with trurl, unRAID is a "purpose built" rather than "general purpose" distribution of Linux. You can certainly use it without parity but redundancy is part of the core value proposition of unRAID. You'd want to take advantage of one or two of the unique features of unRAID or it would be more cost effective to try one of the free distro's.
  6. Yeah, that sounds painful. I think there was a latent problem that the S3 sleep exercise just exposed, though.
  7. Here's my workflow for the occaisonal event/sports photography that I do, just as a simple example. Copy RAWs from SD card to local drive on PC Start Import with Lightroom, first pass keep/delete and obvious cropping Select final files for import Run Import FROM c:\pictures\import TO \\tower\Photos\ShootCategory\ShootName Do further developing on collection Export jpgs for client gallery So, where tower is your unRAID Server and Photos is a user share that will span across disks and allow you to use the entire server as essentially one big hard drive, my workflow just incorporates the movement from initial temporary working storage to long term storage on the unRAID server. You'd still incorporate Amazon cloud drive, backups of developed images (if desired), and backup of your Lightroom catalog into the overall workflow, but it really is easy to add unRAID into the "picture" ;). FYI, you can also simply open a Windows Explorer window to \\tower\Photos and copy back and forth, just like an external hard drive. Hope that helps give you some ideas.
  8. Might be worth trying, then. Since you don't have parity (and I'm assuming you have modern hard drives in the new server) the gating factor is the network connection at 112MB/s. If you can leverage both network connections and have the old servers targeting writes to different drives in the new server then you might be able to double up. Disclaimer - I don't have hands on experience using unRAID with dual NICs.
  9. Two questions, do you have parity set on the new server and does it have a standard 1Gb ethernet port? Oh, and if you have parity, are you using Turbo Write?
  10. Hi, welcome and a few comments: - A 450w power supply would be fine for unRAID and several disks, but might be underpowered depending on how much power the GPU needs. - An 8TB parity drive is expensive unless you plan to add 8TB data drives in the future. And if you plan to - then why not start now? - I'm not sure what role the external HDD will play... - You're putting a mini-ITX motherboard in a case that can support a micro-ATX board, and it only has 6 SATA ports, and you plan to put in a GPU for gaming which will occupy the only PCIex slot. The Node 804 can support 8+ disks, so the motherboard choice is going to limit you. Why not move up to a board with more SATA ports or more PCIex slots? Make sure it supports VT-d. - I don't think the Core i5 7500 is a great choice for a build with VMs. It's 4 cores, non-hyperthreaded. People have generally found that pinning cores to the VM works best under unRAID/KVM. 2 cores for unRAID, 2 for a VM, and you're done. Moving up to a Core i7 gives you 4 cores, hyperthreaded or 8 VCPUs. That's a lot more flexible. - You mention Kodi so I'm guessing you don't have Plex transcoding requirements but if you do, that should factor into the CPU choice. - It's always worth thinking about ECC RAM and a Xeon, but it does cost a little more.
  11. I've never heard of anyone regretting a more powerful processor ( ) but a Core i5 should be fine. Stepping up to an i7 would give you future headroom if you want. I mentioned the PSU because I didn't seen one in the original parts list. I'd start with a 250GB SSD - that should be plenty for several Dockers and their data. I think 128GB could be small, I've got 90GB of various stuff on my cache drive right now. 500GB might work out better if you also plan to use it in the traditional way, caching writes to the array. I just use my cache drive for Dockers. The case you've selected would allow you to add a number of additional drives. If you plan to do that, you'll need more SATA ports than any consumer level board will provide (though there are some server boards that can provide up to 14). If you plan to have 8-11 3.5" drives and a couple of SSDs then go for the SATA controller now (IBM M1015 or Dell H310 via eBay are the most commonly used). SyncBackFree works great with \\tower as a destination, but I don't have any experience backing up to Amazon.
  12. Overall your system looks good. The CPU is fine for unRAID and a few Dockers, including Plex with one or two streams. You'll need a quality power supply from someone like Seasonic or Corsair. You'll want an SSD to function as a cache drive and home for those Dockers. That means you'll either need a SATA Controller or motherboard with more SATA ports, though. Personally, I prefer to manage a small number of larger hard drives so I'd get 6TB or larger drives (that means you wouldn't need a SATA controller, either). That's a little more expensive initially so you'd have to assess budget impact. There are lots of PC Backup solutions, and they all work a little differently. I'm trying SyncBackFree right now and like it. I'll probably upgrade to the paid SyncBackSE if I keep using it. I've been though several solutions and like SyncBack best for my needs so far.
  13. UnRAID supports three different types of add-ins - Plugins, Dockers, and VMs. Start by getting the Community Applications plugin. It will give you access to all the other plugins (mostly OS extension type stuff) and Dockers. Most media server functions are Dockers these days. Spooling up a VM is only recommended if you can't find a Docker that does what you need.
Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.