GeekVerve

I've read that moving a typical Unraid environment to a new system is fairly straightforward. Move the drives to the new system. Move the OS flash drive to the new system. Boot new system. If that's truly the case, I feel pretty good about the prospect. However, I'm going to be moving from an Intel platform to AMD. Does that introduce any additional factors for which I need to account? Current: Xeon E3-1265L V2 (4c/8t) on an Asus Z77 mATX motherboard, DDR3 RAM (non-ECC) New: AMD Ryzen 9 3900X (12c/24t) on an Asrock X570 ATX motherboard, DDR4 RAM (non-ECC) I'm running Unraid Pro v6.11.1 and just running NAS, VMs and a (relatively) meager Plex library with just a few convenience plugins.

I figured it out. I was trying to configure all four NICs at once, and it was only saving one. Turns out I had to configure them one at a time and hit the Apply button on each one. Thanks.

Can someone point me to any detailed documentation on the settings in network.cfg? I'm trying to enable a quad-port NIC and not having much luck through the GUI. My networking game is a little weak, and some of the variables in the config file aren't quite clear to me.

I've removed the 512GB and 2-128GB SSDs from the cache pool and formatted them as unassigned devices. I now have a couple VMs running quite happily on them. Thank you again for the advice.

Yikes, completely forgot about the parity writes. I also didn't know trim is not supported in an array. I hadn't considered using them as unassigned drives. That may be the way to go. Thanks!

My Unraid implementation is intended to provide storage for media, documents and various workstation backups as well as host a few VMs for home lab use. My storage needs aren't all that huge. The 3x 4TB HDDs I have set up (1-parity and 2-pool) should be more than enough for quite some time. Over the years I've also accumulated a bunch of SSDs: 1-500GB, 4-256GB, 2-128GB, all SATA3, and I'm debating on how to use them. My first thought was to dump them all into the cache pool and run all my VMs from there. I'm just not real keen on giving up half their capacity in doing so. Then the idea occurred to me of using just the 4x 256GB drives for the cache pool and add the rest to the storage array. That would provide some fault tolerance and if it's not housing my VMs, 512GB should be plenty of write cache. I'm guessing that I could then set my VMs up to run from the SSDs in the storage array and turn off caching for those drives. Is that correct? Are there reasons this may not be a good idea? What it boils down to is I'm trying to maximize the amount of fast SSD space available for VMs while still providing reasonable caching. Any suggestions or insights would be appreciated.

Here's some - spend less time on the internet and more time dealing with people face to face. You may be surprised to learn that the same manners are expected in both cases.

I've been seriously considering it as well. The only downside I can find is that you need to drill and tap some standoff holes yourself, if you are wanting to put an SSI-EEB or extended ATX motherboard in it (it does support XL-ATX). That's not a show-stopper, though.

Ahh, that makes sense. Just connect both to separate inputs on my monitor. Will the keyboard/mouse plugged into a passed through USB controller be accessible in the unRAID GUI at that point? EDIT: Wait, are you talking about accessing the unRAID GUI at boot time on the unRAID system? I wouldn't want to reboot unRAID (to get to the local unRAID GUI) every time I needed to start my Windows VM.

1. Can one GPU be assigned to multiple VM's as long as they are not used concurrently? 2. Can a motherboard's on-board GPU (e.g. that found on the SUPERMICRO MBD-X11SSH-LN4F-O) be passed through to a VM? Ok, I lied, I have one additional question regarding running my Windows 10 desktop in a VM. If the VM shuts down, is accessing unRAID from another device still the only way to boot it? I would typically leave my Windows VM running, but in the event that it does shut down...

Thermaltake Core W200 CaseLabs was super peeved about it.

Do you void the warranty on the drive, when you take it out of the MyBook?

Glad to see I'm not the only OCD-afflicted with a color-coded, formula-laden, conditionally-formatted HDD capacity spreadsheet.

In researching drives for my first unRAID build, my first thought was to buy three of the biggest drives I can afford - one parity and a couple for storage (plus a couple SSD's for cache, but that's not important for the purposes of this discussion). "Wow, the 8TB WD Reds look great, kind of pricey, though I may be able to swing it...OOH! 10TB IronWolf! (drool) Probably run kind of hot, and three would be $1500 - OUCH! It would be 18TB+ to start out, though..." ...and so on. Then I realized that bigger disks means *very* long times for preclear, rebuilds, etc. If one drive goes down, I'm looking at days just to preclear a replacement, and that's *after* I get it through warranty replacement, and *before* throwing it in to be rebuilt - all while the remaining disks remain unprotected. "No problem, I'll run dual parity, but that means I then have *two* drives not counted in my total available storage capacity. Ugh. Not great, but maybe worth it for peace of mind. I could just go with 4x6TB drives, I guess...less than 11TB of space. " I guess it's just a balance that everyone must strike according to their own preferences. Of course any important documents and photos will be backed up someplace online, but I don't particularly enjoy the thought of re-ripping large numbers of my Blu-ray movies. What are everyone else's thoughts? Is high capacity the top priority? Are you willing to use smaller drives, if it lets you go with dual parity? Do preclear/rebuild times with 8-10TB drives concern you at all? I suppose I could go with dual parity and keep a precleared cold spare on hand...if I went with 2 or 3TB drives.

Excellent! That did the trick. Plus, now I have a means of preclearing future drives from within the unRAID GUI. Thanks!