• Posts

  • Joined

  • Last visited

Recent Profile Visitors

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

harrisonmeister's Achievements


Newbie (1/14)



  1. Hey, I've been using unraid on a tower PC/Server successfully that functions as perfectly well as a Hypervisor and a NAS for work purposes. I have a parity drive on it, a data drive and an SSD cache pool that host my VMs. My employer recently paid for an ASRock Intel DeskMini to act as a Hypervisor. Since it's a small form factor PC which only has 2 drives (1 X 2TB SSD and 1 X 2 TB normal HDD) my question is really is unraid suitable for this PC setup? I'd like to use it for more VMs for work, and I love the unraid experience, just not sure how I would set the drives up. I assume the non-SSD drive could act as parity? And the SSD as the only drive in the array? To be clear I understand having only 2 drives leaves me with hardware failure risks. I'm fine with that and can backup the VM disks etc to either my other unraid server or another NAS I have. I have seen Proxmox too but was interested if anyone has suggestions on using unraid with only 2 drives and any tips?
  2. I got an error when running 3 scripts over the course of an hour: 2020-10-26 09:00 Simultaneous execution is disabled, and a script is already running. Exiting. Each of the configs have simultaneous execution enabled (set to Yes) Is there something obvious I'm missing?
  3. Can anyone help with this? This is really frustrating to have a VM just stopped responding. I can't see anything obvious in the logs and am a bit stumped.
  4. Hi, I'm running UNRAID 6.8.3, and have a handful (less than 10) Virtual machines. Yesterday I upgraded to 6.9 (beta 22) and started noticing issues with a single Windows 2019 VM - it would not start, instead replaced with a blue screen of death stating: KMODE exception not handled I restored from a backup of 6.8.3, and was able to rebuild the VM in question. Since then, I have tried to create a new Windows Server 2019 VM, and it will start, and then freeze. This is similar to what happened yesterday. In the logs, I can see this: 2020-06-23 12:44:49.256+0000: Domain id=30 is tainted: high-privileges 2020-06-23 12:44:49.256+0000: Domain id=30 is tainted: host-cpu char device redirected to /dev/pts/5 (label charserial0) 2020-06-23T12:47:45.311413Z qemu-system-x86_64: warning: guest updated active QH I looked for the error in the last line, and have since run a full parity check (as part of the restore process to 6.8.3), and in addition run both a btrfs balance and btrfs scrub. I've attached anonymized diagnostics. I'm a first-time UNRAID user, and although using Linux for work, it's not my speciality, so I'm at a bit of a loss where to go from here. Thanks zoidberg-diagnostics-20200623-1455.zip