bjp999

Moderators
  • Content count

    6912
  • Joined

  • Last visited

  • Days Won

    7

bjp999 last won the day on July 19

bjp999 had the most liked content!

Community Reputation

130 Very Good

1 Follower

Converted

  • Gender
    Male
  • Location
    Virginia
  • Personal Text
    ASRock E3C224-4L/A+, SM C2SEE/B, Asus P5B VM DO/C
  1. I wouldn't bother unless it is gong to be parity.
  2. It is fine. UnRaid literally reinstalls Linux, and your plug-ins with every boot. In essence, to unRaid, every boot it's on a new motherboard. Your Dockers and VMs are independent of the motherboard, and we'll also work fine.
  3. If you want to backup to another stick, make sure only one of the sticks has the label "UNRAID".
  4. Threre is a USB backup plugin that @Squid put together that maintains a usb backup, but not to another usb device - but to a folder on the server. I don't use it, but you can check into it. The danger of a backup is one file called super.dat. It contains the current unRaid slot to drive mappings. If an old backup is used, and the settings had changed, starting the array could cause data loss. Think about upsizng parity and moving the old parity to be a data disk, and then rebooting to a time that the old parity was parity. This is dangerous. Squid renames the super.dat file to put an extra safeguard in the restore process, which I applaud. Note that a failured or broken USB is not the end of the world. It is pretty easy to rebuild one from scratch. But certainly having a backup, or even a screenshot of the drive mappings, helps.
  5. Technically WD owns HGST after purchase from Hitachi, but they operate autonomously, and I believe HGST has a superior product (which is substantiated by BackBlaze published statistics, which although not directly comparable to typical unRaid usage, is the best info I am aware of on long term drive failure rates.) Is this a good vendor in UK? https://www.scan.co.uk/products/4tb-hgst-0s03665-deskstar-nas-35-hdd-24x7-use-sata-iii-6gb-s-7200rpm-64mb-cache-8ms-ncq-retail-box Cheers!
  6. I'd give the Enermax a go. Says it supports 15 drives. You won't be going near that anytime soon, or beyond that maybe ever. GPU and CPU on separate rails so won't interfere. I honestly think it will be fine. Others you posted are single rail also seem fine. But I'd be looking at 500Watt or close to it. The reason people recommended single rail is that the GPU rail was useless to unRaid as a basic NAS. Now people are looking to run mostly VMs and pass through multiple GPUs, it is not such a clear argument. And you could always get a Molex splitter off the GPU plug to use that power for drives. Like I said, i'd stick with the Enermax. The CPU is 2600 passmark, 2 cores, 4 threads. Not bad actually. One transcode at a time with Plex. The 4G ram may hold you back from running dockers you want. If you could add 4G cheaply I'd do that. I'd seriously look at new drives. Aging 2T drives don't have a great track record here. I'd suggest 4T or larger. HGSTs are excellent. If you have an SSD, great. Otherwise suggest using one of the 2T drives as cache to leave more funds for the unRaid array disks - they should be the priority. The next priority (for me at least) would be an updated MB and CPU, and maybe new memory. If you looked at Haswell you could probably reuse the memory. Probably looking at socket 1151. You want an i7 or E3 Xeon that supports vt-d. Something close to 9000 passmark. Used you could probably do under $400 USD. Upgrade to 16G or 32G RAM and you'd be positioned for 4 transcodes, a Windows 10 VM with passthrough, and most anything else you might want to do. Cheers!
  7. "config" folder
  8. No user shares on the flash drive, but probably possible for a tinkerer. Poor performance I expect. Can't speak to longevity. Pessimistic it will meet your needs, but interesting experiment.
  9. Case is excellent. You need a bit swap drive cage (like CSE-M35T-1B) to install. The PSUs each have 3 12 rails. The Enemax says it supports 15 derives, so suggest that one. You really want single 12 volt rail PSU. MB, CPUx memory ... should be ok for a basic build. You won't be running VMs. But this is an ok pace to start. Hard disks ... maybe. We'll have to see the smart reports.
  10. I think either could work, but I was thinking symlinks. Create a folder on your cache with links to the files you want to seed. And configure, or figure out a way to fake out, the DLer so it seeds files from there.
  11. Soft links?
  12. @brando56894 You could link the file from the array into a seeding directory. One copy, two places at the same time.
  13. If moved, not copied, it'd be instant. You'd want it to DL to the right user share.
  14. If you get reallocated sectors, I'd preclear it again. Skip the preread if you want. My experience is that reallocated sectors that occur after burn in (~1000 power on hours) is usually a bad sign. Sometimes the young ones will stabilize. If it runs two cycles and the numbers don't get worse, I'd give it a try.
  15. Yep, that's it. There are some weirdities about having to power down to reset some of the hdparm settings.as I recall, but spindown time may not be a problem. Set then in your go file or via a script that runs once per bout.
Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.