Jump to content


  • Content count

  • Joined

  • Last visited


About dalekphalm

  • Title
    Ginger Beard
  • Birthday 1986-09-24

Profile Information

  • Gender
  • Location
    Ontario, Canada
  • Occupation
    IT Technician

Recent Profile Visitors

4,506 profile views
  1. Windows server in a VM?

    Yes, FreeNAS 11 can create and host VM's for any number of operating systems, including Windows 10/Server, etc. I personally use ESXi as my Hypervisor (VM host), and run FreeNAS and Windows both as VM's - I just find ESXi much more user friendly on the VM front. But FreeNAS will totally work if you want to try it out.
  2. Help moving FreeNas Drives to new Computer

    I can confirm that importing ZFS pools from a previous install works very well. If you have the drives plugged in while installing, the configuration wizard will walk you through the import.
  3. NCIX declares "Supreme Bankruptcy"

    Linus doesn't have $36m to cover the debt NCIX owes, let alone enough to buy the brand/assets, etc. It would be pointless for him to buy it, as it would not cleanly interface with LMG. He could buy it as an investment, but he would either need to quit day to day operations at LMG to manage the NCIX brand, or hire a ton of people to do it for him. Either way, huge investment of time and money that I don't think he has.
  4. Might be a dumb question, but were you signed into your FireFox Sync account before the wipe, and after the wipe did you sign back in? Some plugins may be incompatible with the new version. Bookmarks, etc, should come back immediately after the first sync.
  5. If you selected CUDA rendering, and your GPU usage was at 1%, clearly something isn't working correctly on your system. Also, how can you possibly rule out thermal throttling without knowing the temperatures? In the very screenshot you posted, your CPU is pegged at 3.15 GHz. The Turbo frequency of the Ryzen 7 1700 is 3.7 GHz (without OCing). Now, if you're not hitting 3.7 GHz, temperature is almost certainly the cause. What Heatsink/cooling are you using? I would recommend re-starting the render, and record temps for at least 30 minutes (I'd go an hour to be safe) and see how bad the temps get. No need to finish the render though - you just want to see how much it stresses the CPU.
  6. What were your CPU temps during the rendering? What was the average, and what was the highest spike? Could be thermally throttling. For example, your GPU is only running at around 3 GHz at the moment of that screenshot (I believe it should boost up to 4 GHz assuming no thermal problems).
  7. Help!! Building a VMware server

    Just an FYI but someone in the forum (Sorry, forgot your username) literally just tested out Ryzen w/ the newest version of ESXi (6.5U1 I believe), and it works perfectly fine (so far) with SMT fully enabled and everything. The Ryzen bugs therefore may be worked out by now, so I wouldn't immediately dismiss Ryzen as an option.
  8. NAS - ITX okay?

    There are many instances of people running FreeNAS 9.x as a VM. I myself ran it for a while, before trying FreeNAS 10 (hated it) - I ended up going back to FreeNAS 9.x (latest version) until FreeNAS 11 came out. Both 9.x and 11 worked flawlessly for me under a VM. Indeed, erring on the side of caution for the URE's is not a bad thing, so long as all the information is given and each person makes their own informed decision on risk level. I do have plans of eventually switching to RAIDZ2, but that won't be until I need to upgrade my drives to bigger ones.
  9. NAS - ITX okay?

    Correct. I have FreeNAS running inside a VM on ESXi. I have an LSI 9207-8e HBA (Host Bus Adapter), and it works perfectly with PCIe Passthrough. FreeNAS sees it exactly the same as if FreeNAS was the base OS. All HDD SMART Data is passed through correctly, and FreeNAS is properly able to scrub, detect failures, rebuild the array, etc. You're wrong about VM's. In the past (Version 8 and before) they recommended you not to run FreeNAS as a VM, simply because the devs didn't test that environment. Also, historically, support for PCIe Passthrough on hardware wasn't as wide spread, especially consumer hardware. Hardware RAID is a totally different problem, and exists whether FreeNAS is a VM or not. The issues of Hardware RAID that you talk about, however, are correct. As for RAID5 (RAIDZ1 in ZFS) vs RAID6 (RAIDZ2 in ZFS), it's possible to encounter an URE during a RAID5 rebuild, but it's by no means guaranteed. I had to do a full rebuild of my 6x 3TB RAIDZ1 array, and it went smoothly. That's why it's important to always backup any important data. RAID does not equal backup. RAID is to protect against downtime and as a convenience factor. Even a RAID6 array can fail. It is true however, that the risk grows as the drive size grows. I wouldn't out 6x 10TB HDD's in a RAID5 array, for example. @phongle123 Running FreeNAS as your OS is totally fine with the hardware you've chosen. As others have noted, you don't need to use a dedicated HDD for the OS if you don't want. Using a small USB Drive is sufficient. However, there's certainly no harm in using an SSD or small HDD. For your hardware choices, I'd recommend against using the built-in motherboard RAID. Instead, you should plug all the drives directly into the motherboard and then configure ZFS inside FreeNAS. It will provide better protection against something called Bit Rot. Bit Rot is a normal process that happens on mechanical HDD's. Basically Bit Rot is when a bit on a mechanical HDD randomly flips it's state (turns from a 0 to a 1, or vice versa. This is usually caused by cosmic background radiation, but can be caused by any sufficiently powerful magnetic or electric field. Bit flips are pretty rare, but if they happen, the data is corrupted. The problem with Bit Rot is that when a bit flips, motherboard RAID (and Hardware RAID that don't perform scrubs automatically), the OS can't tell which file is correct, the flipped bit, or the parity calculation. Bit Rot can also cause rebuild failures in the case of a flipped bit being read during a rebuild. Parity rebuild calculations rely on the rest of the data being good, because you're already down one HDD. ZFS automatically scrubs the array, looking for flipped bits. If it detects corrupted data, it'll rebuild the file from parity. Some hardware RAID cards do this as well, but ZFS typically is very good at it. Especially when used with ECC RAM (although not strictly necessary).
  10. Yes, unfortunately there are plenty of yahoos who think they're better. Touching a single button, without taking your eyes off the road, once or twice is fine. But if you're relying on stuff like TouchID, etc, then you're driving wrong. Hands Free technology has been around for literally over a decade, and it has gotten pretty damn good at the basics (Eg: Music and phone calls).
  11. Think about this statement. Just... give it a few minutes to sink in In case you didn't get it: 1. You shouldn't be using your phone while driving. Even using your thumb on the TouchID button could lead to distracted driving. 2. Use Hands Free voice controls, either via Siri, or via Bluetooth - I use them every day, they work well. 3. Use Hands Free Steering Wheel controls if your car has them (When plugged in via the MDI connector, my iPhone 6s can change songs, etc, using the steering wheel controls In many countries, including Canada, touching your phone at all while driving could land you with a ticket - or worse. EDIT: On topic There's no way Apple is making 4 variations on size, with 3 of them all being 0.1" different from the next model. Seriously, that's fucking stupid. Apple needs: 1. A small phone, iPhone SE sized or maybe a bit bigger 2. A "normal" phone - eg: iPhone 6/6s/7/8 sized 3. A "big" phone - Eg: 6 Plus/7 Plus, etc. And that's it. That's a complete Apple product stack. Adding anything beyond this is confusing and unnecessary. The iPhone X would get shuffled into the mix, but that was mostly a test bed for OLED/Face ID. Likely one of the future "Plus" models will simply take the place of the X model.
  12. Should I Buy This Graphics Card?

    Those GPU's are basically the same core, with 320 Shader Units and the same architecture. One is a FirePro workstation card, the other is the R7 gaming card. If you're gaming, obviously get the R7 240, as it's gonna perform exactly the same for less than half the price.
  13. Pfsense on Freenas

    Direct access is 100% possible when virtualizing FreeNAS. If you use PCIe Passthrough to "pass" a controller (typically a PCIe SAS HBA Controller Card, or a PCIe SAS RAID Card in IT mode) to the VM, the VM sees the controller as if it were a standard physical installation. Some Hypervisors/VM software doesn't support PCIe Passthrough though. And your CPU/MB has to be compatible as well. I've been using FreeNAS in an ESXi VM for 6+ months. It's 100% stable and works perfectly as intended. I even did a rebuild once when one of my HDD's died and was replaced.
  14. Newbie Plex Media Server

    1. A GPU is entirely unnecessary for Plex Server. It simply won't utilize any installed GPU's. All transcoding is done by the CPU. 2. Yep that's fine. Plex won't take up much space by itself, but Plex will use the C:\ drive by default as the cache (This is where it stores the files being transcoded when streaming a video). It will basically use as much as it needs, up to the remaining empty space on the drive (Typically, however much space is used, equals the size of the file being transcoded). It will periodically empty the cache, so unless you're very short on space, don't worry about it. A 120GB SSD for example, would be totally fine for OS + Plex + installed programs. 3. That's fine as well. RAM would be 4GB minimum. I'd recommend 8GB. 16GB is entirely unnecessary (though having more RAM may decrease buffering times - but the SSD will do a bigger job of that anyway, due to the cache). For HDD's, you can pretty much use anything at all. I'd suggest getting a pair of large capacity drives (Eg: 2x 6TB) in RAID1, but honestly even just a single large HDD is totally fine (just backup anything important).
  15. UNRAID VM to VM 10gigabit transfer

    Slightly off topic, but I wanted to know why you chose to use unRAID as your base hypervisor, and then you virtualized FreeNAS anyway. Why not simply use FreeNAS as the hypervisor and run the Windows 10 VM from there? Or are you utilizing other features of unRAID that you prefer over FreeNAS?