Jump to content

eribob

Members
  • Content Count

    27
  • Joined

  • Last visited

Community Reputation

0 Neutral

About eribob

  • Rank
    Member
  1. Hi, yes i can. I can not restart the vm through windows start menu from inside the VM, but I can restart it with the unraid interface. Quite often I have to ”force stop” it and start again though. restarting the server is not necessary though.
  2. Hi, yes, I had no problems passing through my radeon rx 580 to both a windows and a mac os VM. best if luck!
  3. Hi! i have not resolved the issue unfortunately. Any suggestions would be much appreciated. I am thinking of switching to a supermicro motherboard instead but it is a lot of work and some money as well so I am hesitant.
  4. Hi! I have done some more digging. The problem seems to be with dmidecode, the command that the unraid GUI uses to fetch system information. When I run dmidecode manually I get some output and in the end the following error: Invalid entry length (0). DMI table is broken! Stop Is there a way to fix the DMI table? Only through BIOS update? Thank you! /Erik
  5. OK, thank you. It seems like it would be easy to fix, related to how Unraid processes the system information?
  6. Thank you. Yes I can assign more than 32 GB of RAM to my VMs.
  7. Thank you. Yes I can assign more than 32 GB of RAM to my VMs.
  8. Hi! I have posted about this before, but I did not get an answer and I have found some more information. I have a Huananzhi x79 8D motherboard with 8x8GB of DDR3 ECC memory and 2 x Xeon E5 2670 CPU:s. The unraid dashboard lists my RAM to be 32GB (instead of 64GB). The system information as well: Model: Custom M/B: HUANANZHI X79-8D Version VAA31 - s/n: MB-201903272019 BIOS: American Megatrends Inc. Version 4.6.5. Dated: 03/28/2019 CPU: Intel® Xeon® CPU E5-2670 0 @ 2.60GHz HVM: Enabled IOMMU: Enabled Cache: 512 KiB, 2048 KiB, 20480 KiB, 512 KiB, 2048 KiB, 20480 KiB Memory: 32 GiB DDR3 Multi-bit ECC (max. installable capacity 192 GiB) Network: bond0: fault-tolerance (active-backup), mtu 1500 eth0: 1000 Mbps, full duplex, mtu 1500 eth1: interface down Kernel: Linux 4.19.88-Unraid x86_64 OpenSSL: 1.1.1d Uptime: The "free" command gives me 64GB of RAM: total used free shared buff/cache available Mem: 65966588 19896080 4611780 696308 41458728 44772192 Swap: 0 0 0 lshw -short Also shows 8 sticks of 8GB RAM: /W path Device Class Description ===================================================== system To be filled by O.E.M. (To be filled by O.E.M.) /0 bus X79-8D /0/0 memory 64KiB BIOS /0/1 processor Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz /0/1/5 memory 512KiB L1 cache /0/1/6 memory 2MiB L2 cache /0/1/7 memory 20MiB L3 cache /0/2 processor Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz /0/2/9 memory 512KiB L1 cache /0/2/a memory 2MiB L2 cache /0/2/b memory 20MiB L3 cache /0/2c memory System Memory /0/2c/0 memory DIMM Synchronous [empty] /0/2c/1 memory DIMM Synchronous [empty] /0/2c/2 memory DIMM Synchronous [empty] /0/2c/3 memory DIMM Synchronous [empty] /0/2c/4 memory 8GiB DIMM DDR3 1600 MHz (0.6 ns) /0/2c/5 memory 8GiB DIMM DDR3 1600 MHz (0.6 ns) /0/2c/6 memory 8GiB DIMM DDR3 1600 MHz (0.6 ns) /0/2c/7 memory 8GiB DIMM DDR3 1600 MHz (0.6 ns) /0/3e memory System Memory /0/3e/0 memory 8GiB DIMM DDR3 1600 MHz (0.6 ns) /0/3e/1 memory 8GiB DIMM DDR3 1600 MHz (0.6 ns) /0/3e/2 memory 8GiB DIMM DDR3 1600 MHz (0.6 ns) /0/3e/3 memory 8GiB DIMM DDR3 1600 MHz (0.6 ns) /0/3e/4 memory DIMM Synchronous [empty] /0/3e/5 memory DIMM Synchronous [empty] /0/3e/6 memory DIMM Synchronous [empty] /0/3e/7 memory DIMM Synchronous [empty] /0/4 memory 1023KiB BIOS /0/6 memory 1023KiB BIOS /0/7 memory 1023KiB BIOS /0/9 memory 1023KiB BIOS /0/a memory 1023KiB BIOS /0/b memory 1023KiB BIOS /0/c memory 1023KiB BIOS /0/d memory 1023KiB BIOS /0/237e memory 1MiB BIOS /0/e memory /0/f memory Attaching diagnostics and complete lshw output as a text file. Thank you for any assistance! monsterservern-diagnostics-20200114-2239.zip lshw-output.txt
  9. Thank you. Yes I can assign more than 32 GB of RAM to my VMs.
  10. Hi! I have posted about this before, but I did not get an answer and I have found some more information. I have a Huananzhi x79 8D motherboard with 8x8GB of DDR3 ECC memory and 2 x Xeon E5 2670 CPU:s. The unraid dashboard lists my RAM to be 32GB (instead of 64GB). The system information as well: Model: Custom M/B: HUANANZHI X79-8D Version VAA31 - s/n: MB-201903272019 BIOS: American Megatrends Inc. Version 4.6.5. Dated: 03/28/2019 CPU: Intel® Xeon® CPU E5-2670 0 @ 2.60GHz HVM: Enabled IOMMU: Enabled Cache: 512 KiB, 2048 KiB, 20480 KiB, 512 KiB, 2048 KiB, 20480 KiB Memory: 32 GiB DDR3 Multi-bit ECC (max. installable capacity 192 GiB) Network: bond0: fault-tolerance (active-backup), mtu 1500 eth0: 1000 Mbps, full duplex, mtu 1500 eth1: interface down Kernel: Linux 4.19.88-Unraid x86_64 OpenSSL: 1.1.1d Uptime: The "free" command gives me 64GB of RAM: total used free shared buff/cache available Mem: 65966588 19896080 4611780 696308 41458728 44772192 Swap: 0 0 0 lshw -short Also shows 8 sticks of 8GB RAM: /W path Device Class Description ===================================================== system To be filled by O.E.M. (To be filled by O.E.M.) /0 bus X79-8D /0/0 memory 64KiB BIOS /0/1 processor Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz /0/1/5 memory 512KiB L1 cache /0/1/6 memory 2MiB L2 cache /0/1/7 memory 20MiB L3 cache /0/2 processor Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz /0/2/9 memory 512KiB L1 cache /0/2/a memory 2MiB L2 cache /0/2/b memory 20MiB L3 cache /0/2c memory System Memory /0/2c/0 memory DIMM Synchronous [empty] /0/2c/1 memory DIMM Synchronous [empty] /0/2c/2 memory DIMM Synchronous [empty] /0/2c/3 memory DIMM Synchronous [empty] /0/2c/4 memory 8GiB DIMM DDR3 1600 MHz (0.6 ns) /0/2c/5 memory 8GiB DIMM DDR3 1600 MHz (0.6 ns) /0/2c/6 memory 8GiB DIMM DDR3 1600 MHz (0.6 ns) /0/2c/7 memory 8GiB DIMM DDR3 1600 MHz (0.6 ns) /0/3e memory System Memory /0/3e/0 memory 8GiB DIMM DDR3 1600 MHz (0.6 ns) /0/3e/1 memory 8GiB DIMM DDR3 1600 MHz (0.6 ns) /0/3e/2 memory 8GiB DIMM DDR3 1600 MHz (0.6 ns) /0/3e/3 memory 8GiB DIMM DDR3 1600 MHz (0.6 ns) /0/3e/4 memory DIMM Synchronous [empty] /0/3e/5 memory DIMM Synchronous [empty] /0/3e/6 memory DIMM Synchronous [empty] /0/3e/7 memory DIMM Synchronous [empty] /0/4 memory 1023KiB BIOS /0/6 memory 1023KiB BIOS /0/7 memory 1023KiB BIOS /0/9 memory 1023KiB BIOS /0/a memory 1023KiB BIOS /0/b memory 1023KiB BIOS /0/c memory 1023KiB BIOS /0/d memory 1023KiB BIOS /0/237e memory 1MiB BIOS /0/e memory /0/f memory Attaching diagnostics and complete lshw output as a text file. Thank you for any assistance! monsterservern-diagnostics-20200114-2239.zip lshw-output.txt
  11. Hi again! It actually works quite well with nomachine. A lot less latency than VNC at least. Thank you for that suggestion. Still not as good as parsec on my PC though... I will have to wait until they make a server for Mac OS as well I guess. To me, it seems like this is the future of computing, put your main computer resources in a closet and connect thin clients to it... =)
  12. Ok, I will look into it, thank you!
  13. Hi! I have installed a mac os vm on my unraid server (catalina) using spaceinvaders very nice plugin. I have passed my amd GPU through to it. I already have a windows vm that I connect to using parsec for a nice low latency remote desktop. I am now wondering if there is a similar solution for mac? I have tried to do it with steam remote and adding a non-game app like apple notes but I get a blank screen with a loading icon only when it connects. Is there another solution that can provide a low latency connection to my mac os vm? VNC and apples own screen sharing is not good enough I think Thank you in advance!
  14. The great overview of your server that the UI creates. A step by step guide that is launched in the UI the first time you log in. It can walk you through setting up the array and introduce the concepts such as parity cache etc.
  15. Thanks. It used to be prefer, but i wanted to change it to yes to move the vdisk img from cache to array. also, one of the vdisks was 500GB and my cache drive is only 256GB. Thats why I thought it was actually on the array, not the cache disk. when browsing cache drive files through the unraid web interface it looked like a 500GB vdisk was on the 256GB cache...