anony

Members
  • Posts

    17
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

anony's Achievements

Noob

Noob (1/14)

1

Reputation

  1. Whenever I try to run the biginit command it automatically enters [n] and cancels. root@Tower:/mnt/user/appdata/nextcloud/nextcloud# docker exec -u 33 Nextcloud ./occ db:convert-filecache-bigint Nextcloud is in maintenance mode - no apps have been loaded Following columns will be updated: * federated_reshares.share_id * files_trash.auto_id * share_external.id * share_external.parent This can take up to hours, depending on the number of files in your instance! Continue with the conversion (y/n)? [n]
  2. When I try to run occ in appdata/ to fix all of these isses: Your installation has no default phone region set. This is required to validate phone numbers in the profile settings without a country code. To allow numbers without a country code, please add "default_phone_region" with the respective ISO 3166-1 code ↗ of the region to your config file. The database is missing some indexes. Due to the fact that adding indexes on big tables could take some time they were not added automatically. By running "occ db:add-missing-indices" those missing indexes could be added manually while the instance keeps running. Once the indexes are added queries to those tables are usually much faster. Missing index "fs_size" in table "oc_filecache". Missing index "cards_abiduri" in table "oc_cards". Missing index "properties_path_index" in table "oc_properties". The database is missing some primary keys. Due to the fact that adding primary keys on big tables could take some time they were not added automatically. By running "occ db:add-missing-primary-keys" those missing primary keys could be added manually while the instance keeps running. Missing primary key on table "oc_federated_reshares". Missing primary key on table "oc_systemtag_object_mapping". Missing primary key on table "oc_comments_read_markers". Missing primary key on table "oc_collres_resources". Missing primary key on table "oc_collres_accesscache". Missing primary key on table "oc_filecache_extended". The database is missing some optional columns. Due to the fact that adding columns on big tables could take some time they were not added automatically when they can be optional. By running "occ db:add-missing-columns" those missing columns could be added manually while the instance keeps running. Once the columns are added some features might improve responsiveness or usability. Missing optional column "reference_id" in table "oc_comments". Module php-imagick in this instance has no SVG support. For better compatibility it is recommended to install it. Some columns in the database are missing a conversion to big int. Due to the fact that changing column types on big tables could take some time they were not changed automatically. By running 'occ db:convert-filecache-bigint' those pending changes could be applied manually. This operation needs to be made while the instance is offline. For further details read the documentation page about this. federated_reshares.share_id share_external.id share_external.parent Please double check the installation guides ↗, and check for any errors or warnings in the log. Check the security of your Nextcloud over our security scan ↗. I get this message: #2 {main}root@Tower:/mnt/user/appdata/nextcloud/nextcloud# ./occ db:add-missing-primary-keys The current PHP memory limit is below the recommended value of 512MB. Nextcloud is not installed - only a limited number of commands are available No database drivers (sqlite, mysql, or postgresql) installed. PHP module zip not installed. Please ask your server administrator to install the module. PHP module XMLWriter not installed. Please ask your server administrator to install the module. PHP module XMLReader not installed. Please ask your server administrator to install the module. PHP module libxml not installed. Please ask your server administrator to install the module. PHP module GD not installed. Please ask your server administrator to install the module. An unhandled exception has been thrown: Exception: Environment not properly prepared. in /mnt/user/appdata/nextcloud/nextcloud/lib/private/Console/Application.php:168 Stack trace: #0 /mnt/user/appdata/nextcloud/nextcloud/console.php(99): OC\Console\Application->loadCommands(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput)) #1 /mnt/user/appdata/nextcloud/nextcloud/occ(11): require_once('/mnt/user/appda...') What is going on here?
  3. I have discovered this error in the log now: 2020-12-13T01:19:05.191309Z qemu-system-x86_64: vfio: Cannot reset device 0000:0a:00.0, depends on group 32 which is not owned. 2020-12-13T01:19:05.191404Z qemu-system-x86_64: vfio: Cannot reset device 0000:0a:00.0, depends on group 32 which is not owned.
  4. I have downgraded the bios to 2702 with no luck. I have no idea why ubuntu works on both gpu's but windows 10 does not work at all yet windows 10 used to work. Im on my 6th hour trying to fix this - this is my 4th year running unraid and the one thing it had kept this entire time is how much of a pain in the ass it has been. 😀
  5. Yes if I create a new VM it doesn't work. Thanks I forgot about BIOS flash back I will try that tomorrow to revert back to 2702.
  6. Version: 6.9.0-beta35 Tried latest stable too. CPU: Ryzen 9 5900x Motherboard: ASUS X570 Hero Wifi BIOS version: 3003 (latest) https://rog.asus.com/motherboards/rog-crosshair/rog-crosshair-viii-hero-wi-fi-model/helpdesk_bios/ I run two VMs on my machine. A Windows 10 system and an ubuntu system. They both use the OVMF BIOS with Q35. Recently I decided to update my motherboard bios to from 2702 to 3003 as it was recently released. After updating, I cannot get my Windows 10 VM to display. After booting the screen goes blank with nothing after. I cannot find any errors in the logs either. My ubuntu VM works completely fine and boots no problem. I have tried the fx bios which also doesn't work. Only SeaBIOS works now - I dont like SeaBIOS; it requires me to reinstall windows since I cant seem to boot from my past OVMF version of Windows 10. I have tried disabling hyperv and messing with bios settings (default) but no luck! I cannot downgrade the motherboard BIOS either. I have also tried re-creating the VM numerous times. Including booting off UEFI version of unraid. What else should I provide? Logs of Windows 10 VM on OVMF -m 30208 \ -overcommit mem-lock=off \ -smp 12,sockets=1,dies=1,cores=6,threads=2 \ -uuid 269b9d68-44ba-e501-0878-d5d36b29911f \ -display none \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=32,server,nowait \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=localtime \ -no-hpet \ -no-shutdown \ -boot strict=on \ -device pcie-root-port,port=0x8,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x1 \ -device pcie-root-port,port=0x9,chassis=2,id=pci.2,bus=pcie.0,addr=0x1.0x1 \ -device pcie-root-port,port=0xa,chassis=3,id=pci.3,bus=pcie.0,addr=0x1.0x2 \ -device pcie-root-port,port=0xb,chassis=4,id=pci.4,bus=pcie.0,addr=0x1.0x3 \ -device pcie-root-port,port=0xc,chassis=5,id=pci.5,bus=pcie.0,addr=0x1.0x4 \ -device pcie-root-port,port=0xd,chassis=6,id=pci.6,bus=pcie.0,addr=0x1.0x5 \ -device qemu-xhci,p2=15,p3=15,id=usb,bus=pcie.0,addr=0x7 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.2,addr=0x0 \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/Win10_20H2_v2_English_x64.iso","node-name":"libvirt-2-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-2-format","read-only":true,"driver":"raw","file":"libvirt-2-storage"}' \ -device ide-cd,bus=ide.0,drive=libvirt-2-format,id=sata0-0-0,bootindex=2 \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/virtio-win-0.1.189-1.iso","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-1-format","read-only":true,"driver":"raw","file":"libvirt-1-storage"}' \ -device ide-cd,bus=ide.1,drive=libvirt-1-format,id=sata0-0-1 \ -netdev tap,fd=35,id=hostnet0 \ -device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:1a:65:88,bus=pci.1,addr=0x0 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0 \ -chardev socket,id=charchannel0,fd=37,server,nowait \ -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ -device vfio-pci,host=0000:09:00.0,id=hostdev0,bus=pci.3,addr=0x0,romfile=/mnt/user/isos/gpubios.rom \ -device vfio-pci,host=0000:09:00.1,id=hostdev1,bus=pci.4,addr=0x0 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2020-12-10 10:43:11.416+0000: Domain id=5 is tainted: high-privileges 2020-12-10 10:43:11.416+0000: Domain id=5 is tainted: host-cpu char device redirected to /dev/pts/1 (label charserial0) tower-diagnostics-20201210-0244.zip
  7. Receiving this in my system logs. Could this be related to the PCIe device not being plugged in correctly or all the way? Aug 11 10:30:45 Tower kernel: pcieport 0000:00:03.0: device [8086:2f08] error status/mask=00001000/00002000 Aug 11 10:30:45 Tower kernel: pcieport 0000:00:03.0: [12] Timeout Aug 11 10:30:50 Tower kernel: pcieport 0000:00:03.0: AER: Corrected error received: 0000:00:03.0 Aug 11 10:30:50 Tower kernel: pcieport 0000:00:03.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) Aug 11 10:30:50 Tower kernel: pcieport 0000:00:03.0: device [8086:2f08] error status/mask=00001000/00002000 Aug 11 10:30:50 Tower kernel: pcieport 0000:00:03.0: [12] Timeout Aug 11 10:30:54 Tower kernel: pcieport 0000:00:03.0: AER: Corrected error received: 0000:00:03.0 Aug 11 10:30:54 Tower kernel: pcieport 0000:00:03.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) Aug 11 10:30:54 Tower kernel: pcieport 0000:00:03.0: device [8086:2f08] error status/mask=00001000/00002000 Aug 11 10:30:54 Tower kernel: pcieport 0000:00:03.0: [12] Timeout Aug 11 10:30:56 Tower kernel: pcieport 0000:00:03.0: AER: Corrected error received: 0000:00:03.0 Aug 11 10:30:56 Tower kernel: pcieport 0000:00:03.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) Aug 11 10:30:56 Tower kernel: pcieport 0000:00:03.0: device [8086:2f08] error status/mask=00001000/00002000 Aug 11 10:30:56 Tower kernel: pcieport 0000:00:03.0: [12] Timeout Aug 11 10:31:05 Tower kernel: pcieport 0000:00:03.0: AER: Corrected error received: 0000:00:03.0 Aug 11 10:31:05 Tower kernel: pcieport 0000:00:03.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) Aug 11 10:31:05 Tower kernel: pcieport 0000:00:03.0: device [8086:2f08] error status/mask=00001000/00002000 Aug 11 10:31:05 Tower kernel: pcieport 0000:00:03.0: [12] Timeout Aug 11 10:31:53 Tower kernel: pcieport 0000:00:03.2: AER: Multiple Corrected error received: 0000:00:03.2 Aug 11 10:31:53 Tower kernel: pcieport 0000:00:03.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Aug 11 10:31:53 Tower kernel: pcieport 0000:00:03.2: device [8086:2f0a] error status/mask=00000040/00002000 Aug 11 10:31:53 Tower kernel: pcieport 0000:00:03.2: [ 6] BadTLP Aug 11 10:31:59 Tower kernel: pcieport 0000:00:03.2: AER: Multiple Corrected error received: 0000:00:03.2 Aug 11 10:31:59 Tower kernel: pcieport 0000:00:03.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Aug 11 10:31:59 Tower kernel: pcieport 0000:00:03.2: device [8086:2f0a] error status/mask=00000040/00002000 Aug 11 10:31:59 Tower kernel: pcieport 0000:00:03.2: [ 6] BadTLP Aug 11 10:32:23 Tower kernel: pcieport 0000:00:03.2: AER: Multiple Corrected error received: 0000:00:03.2 Aug 11 10:32:23 Tower kernel: pcieport 0000:00:03.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Aug 11 10:32:23 Tower kernel: pcieport 0000:00:03.2: device [8086:2f0a] error status/mask=00000040/00002000 Aug 11 10:32:23 Tower kernel: pcieport 0000:00:03.2: [ 6] BadTLP Aug 11 10:32:32 Tower kernel: pcieport 0000:00:03.2: AER: Multiple Corrected error received: 0000:00:03.2 Aug 11 10:32:32 Tower kernel: pcieport 0000:00:03.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Aug 11 10:32:32 Tower kernel: pcieport 0000:00:03.2: device [8086:2f0a] error status/mask=00000040/00002000 Aug 11 10:32:32 Tower kernel: pcieport 0000:00:03.2: [ 6] BadTLP Aug 11 10:32:52 Tower emhttpd: req (4): cmd=/plugins/dynamix.plugin.manager/scripts/plugin&arg1=checkos&csrf_token=**************** Aug 11 10:32:52 Tower emhttpd: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin checkos Aug 11 10:33:23 Tower kernel: pcieport 0000:00:03.0: AER: Corrected error received: 0000:00:03.0 Aug 11 10:33:23 Tower kernel: pcieport 0000:00:03.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) Aug 11 10:33:23 Tower kernel: pcieport 0000:00:03.0: device [8086:2f08] error status/mask=00001000/00002000 Aug 11 10:33:23 Tower kernel: pcieport 0000:00:03.0: [12] Timeout -+-[0000:ff]-+-0b.0 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 R3 QPI Link 0 & 1 Monitoring | +-0b.1 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 R3 QPI Link 0 & 1 Monitoring | +-0b.2 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 R3 QPI Link 0 & 1 Monitoring | +-0c.0 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers | +-0c.1 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers | +-0c.2 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers | +-0c.3 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers | +-0c.4 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers | +-0c.5 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers | +-0f.0 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Buffered Ring Agent | +-0f.1 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Buffered Ring Agent | +-0f.4 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 System Address Decoder & Broadcast Registers | +-0f.5 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 System Address Decoder & Broadcast Registers | +-0f.6 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 System Address Decoder & Broadcast Registers | +-10.0 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 PCIe Ring Interface | +-10.1 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 PCIe Ring Interface | +-10.5 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Scratchpad & Semaphore Registers | +-10.6 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Scratchpad & Semaphore Registers | +-10.7 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Scratchpad & Semaphore Registers | +-12.0 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Home Agent 0 | +-12.1 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Home Agent 0 | +-13.0 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Target Address, Thermal & RAS Registers | +-13.1 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Target Address, Thermal & RAS Registers | +-13.2 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder | +-13.3 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder | +-13.4 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder | +-13.5 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder | +-13.6 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO Channel 0/1 Broadcast | +-13.7 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO Global Broadcast | +-14.0 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel 0 Thermal Control | +-14.1 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel 1 Thermal Control | +-14.2 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel 0 ERROR Registers | +-14.3 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel 1 ERROR Registers | +-14.4 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO (VMSE) 0 & 1 | +-14.5 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO (VMSE) 0 & 1 | +-14.6 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO (VMSE) 0 & 1 | +-14.7 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO (VMSE) 0 & 1 | +-15.0 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel 2 Thermal Control | +-15.1 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel 3 Thermal Control | +-15.2 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel 2 ERROR Registers | +-15.3 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel 3 ERROR Registers | +-16.0 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 1 Target Address, Thermal & RAS Registers | +-16.6 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO Channel 2/3 Broadcast | +-16.7 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO Global Broadcast | +-17.0 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 1 Channel 0 Thermal Control | +-17.4 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO (VMSE) 2 & 3 | +-17.5 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO (VMSE) 2 & 3 | +-17.6 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO (VMSE) 2 & 3 | +-17.7 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO (VMSE) 2 & 3 | +-1e.0 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Power Control Unit | +-1e.1 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Power Control Unit | +-1e.2 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Power Control Unit | +-1e.3 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Power Control Unit | +-1e.4 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Power Control Unit | +-1f.0 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 VCU | \-1f.2 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 VCU \-[0000:00]-+-00.0 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DMI2 +-01.0-[03]-- +-01.1-[04]-- +-03.0-[02]--+-00.0 NVIDIA Corporation GP104 [GeForce GTX 1070] | \-00.1 NVIDIA Corporation GP104 High Definition Audio Controller +-03.2-[01]--+-00.0 NVIDIA Corporation GP104 [GeForce GTX 1070] | \-00.1 NVIDIA Corporation GP104 High Definition Audio Controller +-05.0 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Address Map, VTd_Misc, System Management +-05.1 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Hot Plug +-05.2 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 RAS, Control Status and Global Errors +-05.4 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 I/O APIC +-11.0 Intel Corporation C610/X99 series chipset SPSR +-11.4 Intel Corporation C610/X99 series chipset sSATA Controller [AHCI mode] +-14.0 Intel Corporation C610/X99 series chipset USB xHCI Host Controller +-16.0 Intel Corporation C610/X99 series chipset MEI Controller #1 +-19.0 Intel Corporation Ethernet Connection (2) I218-V +-1a.0 Intel Corporation C610/X99 series chipset USB Enhanced Host Controller #2 +-1b.0 Intel Corporation C610/X99 series chipset HD Audio Controller +-1c.0-[05]-- +-1c.3-[06-0b]----00.0-[07-0b]--+-01.0-[08]----00.0 Intel Corporation I211 Gigabit Network Connection | +-02.0-[09]----00.0 Broadcom Inc. and subsidiaries BCM4360 802.11ac Wireless Network Adapter | +-03.0-[0a]-- | \-04.0-[0b]-- +-1c.4-[0c]----00.0 Renesas Technology Corp. uPD720201 USB 3.0 Host Controller +-1c.6-[0d]----00.0 ASMedia Technology Inc. ASM1042A USB 3.0 Host Controller +-1d.0 Intel Corporation C610/X99 series chipset USB Enhanced Host Controller #1 +-1f.0 Intel Corporation C610/X99 series chipset LPC Controller +-1f.2 Intel Corporation C610/X99 series chipset 6-Port SATA Controller [AHCI mode] \-1f.3 Intel Corporation C610/X99 series chipset SMBus Controller lspci -vt output ^
  8. Wondering how I can view a share for games on each of my VMs. For example I'd like two VMs to be able to access a single .img/vdisk at the same time, and view the same files as if it was the same hard drive. Thanks
  9. Hi, New user here with no experience. I read through most of the basic documentation on how unRAID works. I have a few questions. How can I assign two separate disks to two VMs. Would this be done by selecting two disks with or without a parity drive then creating a share for each disk which each share can be assigned to a specific VM? Secondly, lets say I want two Windows VMs running off of 1 512GB SSD split so each VM has 240GB allocated alongside a third VM for backup with a single 1TB HDD & a parity drive. Would I assign a 1TB+ drive as parity1 then a 1TB HDD as disk1 with the 512GB SSD as disk2. Add a share for the 1TB HDD & 512GB SSD; split the 512GB SSD to 240GB per Windows VM. After create a share for the 1TB disk and assign that to the 3rd VM? Supposedly the parity drive will take care of both disks in-case 1 has a fault, or is it a lot more complicated than that? Thanks Please link any helpful guides as I am currently a blind man in this binary world.
  10. I see, OK. I'm planning on using the system for two VMs on 1 computers. Thanks for the help. I understand now.