Jump to content

rilles

Members
  • Content Count

    44
  • Joined

  • Last visited

Community Reputation

1 Neutral

About rilles

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. While it seemed the answer to everything... it doesn't appear to be stable. running it as a plain docker it just runs for a bit then exists for no apparent reason. Running as a unraid docker, it randomly shuts down also. Tried running emby, but it seems to have random shutdowns also under load and has too many quirks in the way it works I don't like. So now I'm running kodi 18.1 in a Virtualbox Ubuntu session.. that seems to work really well. So next step is to get a raspberri pi to run kodi and do the updates.
  2. I found a docker that seems to do what I want - a headless kodi docker that just does library updates and cleans. https://github.com/milaq/kodi-headless But I have to run this on my main pc until I can figure out how to get a "raw" docker on unraid.
  3. And the workaround for the non-exported symbols. https://www.phoronix.com/scan.php?page=news_item&px=ZFS-On-Linux-5.0-Workaround
  4. RobJ has an opinion. But ECC is not REQUIRED for ZFS or btrfs, probably strongly suggested for the more data paranoid who may lose sleep over a possible "scrub of death". But, RAID is not a backup - so I'm not going to be upset if bits flip in my movie stash and all my actual important stuff of course is backed up somewhere else.
  5. Yes, unless bits rotting away keep you up all night, but then you'd already have ECC RAM in your unraid box.
  6. after more reading.. found this related topic
  7. Or a load based parity check. As an example, I have a ZFS mirror - when it does a scrub it hammers the disk but when I use the file system, the scrub seems seem to have very little impact and the scrubbing picks up again after the transaction. unraid parity check seems to run at max priority, probably to minimum check time. As mentioned, with huge drives taking more than a day to check.. some kind of load based scheduling option would help parity checks from hogging IO at the expense of completion time.
  8. hmmm, I run a ZFS mirror cluster on Ubuntu 18.04. It really is an amazing file system for its features and ease of use. You don't require lots of RAM or ECC RAM, this is a myth. 1. plain ZFS can run on 1GB of RAM on any size array. If you have more RAM it will use more for a cache. Once you enable Dedupe and L2ARC you needs lots of RAM (rule of thumb is about 1GB of RAM per TB of storage) 2. If you use ZFS for business reasons, like any server you should use ECC RAM. For home use, storing movies... you don't need ECC RAM. btrfs doesn't require ECC. ZoL is ZFS on Linux, it functions in linux like a native file system. BSD has switched to this. https://zfsonlinux.org/
  9. newegg.ca has even a better deal at $589 each.
  10. I have a testing unraid system build from an old Acer H340 WHS. 2GB of RAM and a 1 core Atom CPU. runs the array fine and a few dockers.
  11. 5.5? thats still a baby. I have a fleet of 2TB drives I bought in 2009/2010 and I deliberately bought different makes. Only my WD EARS drives started to show end of life weirdness. But I have noticed in 6.4.1 (it may have been there before) there is now a spot for a drive manufacture date and a warranty end date. Not sure what unraid will do with that info but it does have information that could be harvested for a report from a plugin..
  12. yes. I moved to a new case - i didn't track what was plugged into what - when I started unraid from the new box it recognized all drives for that they should be.
  13. downside to these cheap SATA controllers seems to be lots of reports of reliability issues - from the card stop working to corrupted data. The issues I've seen was enough for me to go for a LSI controller, I got a used Dell PERC HBA that was already flashed into IT mode for a decent price from ebay.
  14. Marked this topic solved. The problem is not solved, by the why is.