eribob

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.

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

OK, thank you. It seems like it would be easy to fix, related to how Unraid processes the system information?

Thank you. Yes I can assign more than 32 GB of RAM to my VMs.

Thank you. Yes I can assign more than 32 GB of RAM to my VMs.

Thank you. Yes I can assign more than 32 GB of RAM to my VMs.

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

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... =)

Ok, I will look into it, thank you!

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!

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.

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...

Now I think I messed up, just asking if there is a magic fix or if I need to reinstall my VM:s... When trying to move I got the following in the log: Dec 29 00:54:08 Monsterservern root: mover: started Dec 29 00:54:08 Monsterservern move: move: file /mnt/cache/domains/Ubuntu - jupyterhub/vdisk1.img Dec 29 00:54:08 Monsterservern move: move_object: /mnt/cache/domains/Ubuntu - jupyterhub/vdisk1.img File exists Dec 29 00:54:08 Monsterservern move: move: file /mnt/cache/domains/Windows 10/vdisk2.img Dec 29 00:54:08 Monsterservern move: move_object: /mnt/cache/domains/Windows 10/vdisk2.img File exists Dec 29 00:54:08 Monsterservern root: mover: finished It looked like there were two copies of the vdisk.img files, one in the array /mnt/user/domains/... and one on the cache drive. I removed the ones on the cache drive and now my VM:s will not start. I guess the .img files were partly in both places and now they are corrupted? Is it fixable?

Thank you for the advice. I changed the behavior now so that appdata is on the cache ("prefer"). I also noticed that the "system" share was set to "prefer" for the cache drive. Is this advisable as well? It contains the docker apps right?

Thanks for quick replies to a noobs questions! I wanted to move the appdata off the cache because it was getting big and consuming a lot of the cache drive space. Is it better to put it on an unassigned drive? Still, I wonder why there is no activity on the cache drive at all during the move, only on two of the drives in the array? Thanks for the heads up. The boot drive is put in a USB2 port.

Hi! My cache drive was getting full so I wanted to empty it today. I realised that I had set the appdata share to "prefer" cache so I changed its cache setting to "yes" and made sure all other shares have "yes" as well. In addition I stopped all docker containers and all VMs. Then I started the move. The problem is that it has been doing the move for a long time now (2 hours) and it is reading from one drive in the array that is almost empty and writing to another drive and to the parity disk. It is however not reading from the cache drive. Some data seems to have been moved of the cache, but very slowly. Is this how it is supposed to work? It does not seem logical to only move things around in the array when I actually want to move from cache to array? See attached screenshots. I also activated "turbo write mode" in an attempt to speed the process up.

Here is my log (is this the one you meant?) Dec 22 10:58:20 Monsterservern kernel: vfio-pci 0000:03:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Dec 22 10:58:24 Monsterservern kernel: vfio-pci 0000:03:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Dec 22 10:58:24 Monsterservern kernel: br0: port 3(vnet1) entered blocking state Dec 22 10:58:24 Monsterservern kernel: br0: port 3(vnet1) entered disabled state Dec 22 10:58:24 Monsterservern kernel: device vnet1 entered promiscuous mode Dec 22 10:58:24 Monsterservern kernel: br0: port 3(vnet1) entered blocking state Dec 22 10:58:24 Monsterservern kernel: br0: port 3(vnet1) entered forwarding state Dec 22 10:58:25 Monsterservern avahi-daemon[4195]: Joining mDNS multicast group on interface vnet1.IPv6 with address fe80::fc54:ff:fe9b:403b. Dec 22 10:58:25 Monsterservern avahi-daemon[4195]: New relevant interface vnet1.IPv6 for mDNS. Dec 22 10:58:25 Monsterservern avahi-daemon[4195]: Registering new address record for fe80::fc54:ff:fe9b:403b on vnet1.*. Dec 22 10:58:37 Monsterservern acpid: input device has been disconnected, fd 4 Dec 22 10:58:37 Monsterservern acpid: input device has been disconnected, fd 5 Dec 22 10:58:37 Monsterservern acpid: input device has been disconnected, fd 6 Dec 22 10:58:37 Monsterservern acpid: input device has been disconnected, fd 7 Dec 22 10:58:38 Monsterservern kernel: usb 2-1.6: reset full-speed USB device number 3 using ehci-pci Dec 22 10:58:38 Monsterservern kernel: usb 1-1.2: reset full-speed USB device number 4 using ehci-pci Dec 22 10:58:38 Monsterservern kernel: usb 1-1.2: reset full-speed USB device number 4 using ehci-pci Dec 22 10:58:39 Monsterservern kernel: usb 2-1.6: reset full-speed USB device number 3 using ehci-pci Dec 22 10:58:42 Monsterservern kernel: usb 1-1.2: reset full-speed USB device number 4 using ehci-pci Dec 22 10:58:43 Monsterservern kernel: usb 2-1.6: reset full-speed USB device number 3 using ehci-pci Dec 22 10:58:43 Monsterservern kernel: usb 2-1.6: reset full-speed USB device number 3 using ehci-pci Dec 22 10:58:43 Monsterservern kernel: usb 1-1.2: reset full-speed USB device number 4 using ehci-pci Dec 22 10:58:54 Monsterservern kernel: usb 1-1.2: reset full-speed USB device number 4 using ehci-pci Dec 22 10:58:54 Monsterservern kernel: usb 1-1.2: reset full-speed USB device number 4 using ehci-pci Dec 22 10:58:54 Monsterservern kernel: usb 2-1.6: reset full-speed USB device number 3 using ehci-pci Dec 22 10:58:54 Monsterservern kernel: usb 2-1.6: reset full-speed USB device number 3 using ehci-pci Dec 22 10:58:55 Monsterservern kernel: usb 1-1.2: reset full-speed USB device number 4 using ehci-pci Dec 22 10:58:56 Monsterservern kernel: usb 2-1.6: reset full-speed USB device number 3 using ehci-pci Dec 22 10:58:56 Monsterservern kernel: usb 1-1.2: reset full-speed USB device number 4 using ehci-pci Dec 22 10:58:56 Monsterservern kernel: usb 2-1.6: reset full-speed USB device number 3 using ehci-pci Dec 22 10:58:57 Monsterservern kernel: usb 1-1.2: reset full-speed USB device number 4 using ehci-pci Dec 22 10:58:57 Monsterservern kernel: usb 2-1.6: reset full-speed USB device number 3 using ehci-pci Dec 22 10:58:57 Monsterservern kernel: usb 1-1.2: reset full-speed USB device number 4 using ehci-pci Dec 22 10:58:57 Monsterservern kernel: usb 2-1.6: reset full-speed USB device number 3 using ehci-pci Dec 22 11:37:35 Monsterservern login[11652]: ROOT LOGIN on '/dev/pts/2' Dec 22 11:49:23 Monsterservern kernel: usb 2-1.6: reset full-speed USB device number 3 using ehci-pci Dec 22 11:49:24 Monsterservern kernel: usb 1-1.2: reset full-speed USB device number 4 using ehci-pci Dec 22 12:25:51 Monsterservern login[14402]: ROOT LOGIN on '/dev/pts/2'

Thanks, Unfortunately the support from huananzhi is not super... I have been googling a lot but I cant find a bios for the board. Is it possible to verify if the DMI table is indeed broken?

Hi! Here is the output. Only half of the RAM sticks seem to be there. Also the last line that says that the "DMI table is broken" is interesting. Is that a BIOS issue? Getting SMBIOS data from sysfs. SMBIOS 2.8 present. Handle 0x002E, DMI type 17, 40 bytes Memory Device Array Handle: 0x002C Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: No Module Installed Form Factor: DIMM Set: None Locator: Node0_Dimm0 Bank Locator: Node0_Bank0 Type: Unknown Type Detail: Synchronous Speed: Unknown Manufacturer: Dimm0_Manufacturer Serial Number: Dimm0_SerNum Asset Tag: Dimm0_AssetTag Part Number: Dimm0_PartNum Rank: Unknown Configured Memory Speed: Unknown Minimum Voltage: Unknown Maximum Voltage: Unknown Configured Voltage: Unknown Handle 0x0030, DMI type 17, 40 bytes Memory Device Array Handle: 0x002C Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: No Module Installed Form Factor: DIMM Set: None Locator: Node0_Dimm1 Bank Locator: Node0_Bank0 Type: Unknown Type Detail: Synchronous Speed: Unknown Manufacturer: Dimm1_Manufacturer Serial Number: Dimm1_SerNum Asset Tag: Dimm1_AssetTag Part Number: Dimm1_PartNum Rank: Unknown Configured Memory Speed: Unknown Minimum Voltage: Unknown Maximum Voltage: Unknown Configured Voltage: Unknown Handle 0x0032, DMI type 17, 40 bytes Memory Device Array Handle: 0x002C Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: No Module Installed Form Factor: DIMM Set: None Locator: Node0_Dimm2 Bank Locator: Node0_Bank0 Type: Unknown Type Detail: Synchronous Speed: Unknown Manufacturer: Dimm2_Manufacturer Serial Number: Dimm2_SerNum Asset Tag: Dimm2_AssetTag Part Number: Dimm2_PartNum Rank: Unknown Configured Memory Speed: Unknown Minimum Voltage: Unknown Maximum Voltage: Unknown Configured Voltage: Unknown Handle 0x0034, DMI type 17, 40 bytes Memory Device Array Handle: 0x002C Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: No Module Installed Form Factor: DIMM Set: None Locator: Node0_Dimm3 Bank Locator: Node0_Bank0 Type: Unknown Type Detail: Synchronous Speed: Unknown Manufacturer: Dimm3_Manufacturer Serial Number: Dimm3_SerNum Asset Tag: Dimm3_AssetTag Part Number: Dimm3_PartNum Rank: Unknown Configured Memory Speed: Unknown Minimum Voltage: Unknown Maximum Voltage: Unknown Configured Voltage: Unknown Handle 0x0036, DMI type 17, 40 bytes Memory Device Array Handle: 0x002C Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: 8192 MB Form Factor: DIMM Set: None Locator: Node0_Dimm4 Bank Locator: Node0_Bank0 Type: DDR3 Type Detail: Registered (Buffered) Speed: 1333 MT/s Manufacturer: SK Hynix Serial Number: 40354E13 Asset Tag: Dimm4_AssetTag Part Number: HMT31GR7EFR4A Rank: 2 Configured Memory Speed: 1333 MT/s Minimum Voltage: Unknown Maximum Voltage: Unknown Configured Voltage: Unknown Handle 0x0038, DMI type 17, 40 bytes Memory Device Array Handle: 0x002C Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: 8192 MB Form Factor: DIMM Set: None Locator: Node0_Dimm5 Bank Locator: Node0_Bank0 Type: DDR3 Type Detail: Registered (Buffered) Speed: 1333 MT/s Manufacturer: SK Hynix Serial Number: 40C54E0E Asset Tag: Dimm5_AssetTag Part Number: HMT31GR7EFR4A Rank: 2 Configured Memory Speed: 1333 MT/s Minimum Voltage: Unknown Maximum Voltage: Unknown Configured Voltage: Unknown Handle 0x003A, DMI type 17, 40 bytes Memory Device Array Handle: 0x002C Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: 8192 MB Form Factor: DIMM Set: None Locator: Node0_Dimm6 Bank Locator: Node0_Bank0 Type: DDR3 Type Detail: Registered (Buffered) Speed: 1333 MT/s Manufacturer: SK Hynix Serial Number: 40254E10 Asset Tag: Dimm6_AssetTag Part Number: HMT31GR7EFR4A Rank: 2 Configured Memory Speed: 1333 MT/s Minimum Voltage: Unknown Maximum Voltage: Unknown Configured Voltage: Unknown Handle 0x003C, DMI type 17, 40 bytes Memory Device Array Handle: 0x002C Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: 8192 MB Form Factor: DIMM Set: None Locator: Node0_Dimm7 Bank Locator: Node0_Bank0 Type: DDR3 Type Detail: Registered (Buffered) Speed: 1333 MT/s Manufacturer: SK Hynix Serial Number: 40254E09 Asset Tag: Dimm7_AssetTag Part Number: HMT31GR7EFR4A Rank: 2 Configured Memory Speed: 1333 MT/s Minimum Voltage: Unknown Maximum Voltage: Unknown Configured Voltage: Unknown Invalid entry length (0). DMI table is broken! Stop.

An update: I got it to work by moving my Unraid USB to a USB2 port as suggested elsewhere in the forum.

I tried that already (UEFI->legacy). No luck :(

I have built a server using the huananzhi x79 8d motherboard, dual intel xeon e5 2670 (v1), 64GB of ECC ddr3 RAM. The GPU is an old radeon HD 6870 and I have a monitor plugged in to it, since the motherboard does not have on board graphics. I would like to try to pass through a GPU to a windows 10 VM and turned on intel virtualization in the BIOS settings. However, when I do this, unRAID does not load normally. I have attached some screenshots. It seems to be unable to find some hardware. For example, I get one of those IP addresses beginning with 169.x.x.x that you get when there is no connection to a DHCP server. I also attach som pictures I took during the boot process of unRAID. If I turn of intel virtualization unRAID boots normally and functions fine, but I can only assign VNC graphics to the VM:s. Do you have any suggestions what could be the problem? Thank you! Erik

Ok, so why is not all RAM detected then? My BIOS reports 64GB.

Hi! I have installed unRAID on a server based on a chinese motherboard form huananzhi (x79 8d) with two xeon e5 2670 CPU:s and 64GB of ECC DDR3 memory. I really like the simplicity of unRAID so far and I am running several fun apps 😃 Now to my problem. The system information page and "dashboard" only shows 32GB of RAM, even though I see all 64GB in BIOS and when I execute "top" and "free" commands in the console. I can also allocate up to 64GB of RAM when creating a VM. root@Monsterservern:~# free total used free shared buff/cache available Mem: 65900588 3426488 58066292 615880 4407808 61168248 Swap: 0 0 0 See the attached images for dashboard and BIOS. I think that the BIOS in my huananzhi motherboard is a bit strange. It looks like it shows a lot more DIMM slots than are actually physically on the board (8 slots). See attached image. Perhaps this is the reason that unRAID does not include all RAM in the system information? This is not a huge issue, but a bit annoying to me as a perfectionist 😃 Also the system information only shows one CPU even though there are two of them, the dashboard shows all 16 threads / 32 cores accurately however. Is there a way to make unraid detect all my RAM in the system information? Thank you! /Erik