• Content count

  • Joined

  • Last visited

  • Days Won


tdallen last won the day on September 20

tdallen had the most liked content!

Community Reputation

57 Good

About tdallen

  • Rank
    Advanced Member


  • Gender
  1. +1, that's what I do with my P5B. Something like this, though preferably local: Get an LSI based card, not Marvell.
  2. The higher end versions of the Roku 3 and 4, but I've never done anything more than 5.1 with them. I sometimes even strip out the DTS-HD MA or Dolby TrueHD tracks for movies where I don't care about high quality audio. I may regret that someday but reassembling my HT isn't a priority right now.
  3. Upgrade/Rebuild Path - Does It Make Sense?

    Hi - What CPU and how much RAM (sounds like 8GB) do you have now?
  4. Using Plex - front ends are Roku, xbox, smart TVs, iPads and iPhones. While I don't have any complaints about audio quality, I'm not running that into a 7.1 HT or anything that runs advanced Dolby formats, etc. Is there anything specific you are trying to support?
  5. Take a look at these:
  6. You need to boot unRAID 6.3 in legacy mode but the newest 6.4, currently in late beta testing supports UEFI boot.
  7. Not enough free space transferring data

    I'd do things one step at a time. First, stop mover. Then, for the shares where there's data on the cache drive that you want moved to the array set cache to "Yes". For everything else set it to No. Then run mover and make sure that your cache drive is cleaned off. Then set Movies, etc to "No" and set the shares that you want on the cache drive to "Prefer" and run mover again - it should move things off the array back to the cache drive for Docker, etc. Don't make any changes to share settings while Mover is running - let it run to completion.
  8. Not enough free space transferring data

    45 degrees is fine for an SSD, so is 52 - normal operating temperature range is typically up to 70 degrees. It would be best to reset the alert trigger. What files are you seeing on the cache drive that is filling it up?
  9. Yeah, from that post "2 copies of all the data on different devices" is the simple way to view it. But you might want to calculate it out, try this calculator . For instance, adding another 500GB SSD only gets you 250GB of usable space. Adding a 1TB SSD would double your usable space.
  10. Not enough free space transferring data

    Instead of setting cache to "only" set it to "prefer" and run mover. Mover will then move the files from the array back to the cache disk. Set System to prefer as well. You can then set cache to "only" if you want, but you don't need to. Setting your other shares to "No" is correct, but run mover first to clear off your cache drive.
  11. Not enough free space transferring data

    There's nothing that says you have to use a cache drive to cache writes to the array. I only use my cache drive for Dockers, Docker data, and the occasional VM test. I find that writes directly to the array are fast enough for me 90% of the time, and if that's not enough I turn on Turbo Write. Unless you copy large amounts of data to your server while sitting there watching and waiting, or have some other specific use case, you might want to try turning write-caching off and seeing if you can live without it. It's simpler and has the benefit that your data is immediately protected by parity. To determine the size of your cache drive you need to decide whether you want cache writes to the array or not. If you want to be able write-cache large amounts of data, use the 2TB spinner for your cache drive. If you only want to use the cache drive as the "application drive" for Dockers, then the 250GB SSD is perfect. For most folks a 250GB SSD would also support write-caching for a few dozen GB of data each day as well. I would not mix the 2TB HD and the 256GB SSD in the cache pool. The cache pool works best with like sized or carefully planned devices with similar performance, try this space calculator to see what I mean .
  12. New Server Setup: Can't view/access shares?

    Grasping at straws... Do you statically assign IPs to your servers, or use DHCP? Are you able to telnet into the servers by name, or do you need to use IPs?
  13. New to unRAID...a few questions...

    I lose power a fair amount, 4 times in the last 90 days according to my logs. Without a UPS data corruption would eventually burn me with that kind of track record.
  14. New to unRAID...a few questions...

    Your characterization of the E5640 sounds right - a little more powerful and less energy efficient. I don't understand the recommendation for a 5 amp fuse - I'd look at the factory specs and run whatever Dell recommends. A hardware RAID controller may or may not be useful. First, you generally don't use a hardware RAID controller with unRAID in RAID mode. Instead, it is useful if it can be flashed into IT or JBOD mode, passing individual disks through to unRAID. unRAID is a software RAID implementation that needs access to the individual disks. Some hardware RAID controllers can be used this way, some can't - depends on the model. There are rare cases where you'd actually use a hardware RAID controller in RAID mode, but I'd recommend saving that discussion for another day. By the way - you definitely should run unRAID on a UPS. You are correct that the parity drive needs to be as large as, or larger than, the biggest data disk. You're also correct that 2TB drives aren't a great buy right now... You can copy from one disk share to another disk share, though, if you want to do a two part migration. There are some rules about this - check back if you go that route. There's no reason to use a big flash drive, 4GB or 8GB is fine.
  15. The main reason to use BTRFS right now is its RAID capabilities which don't apply to a single unassigned device. UD supports a number of formats, I'd use XFS. I don't have any persistently mounted UDs right now so I can't offer advice on the best way to schedule trims and backups.
Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.