PeteAsking

Cant you run htop when it happens and just look at what process is using 100%?

Also I think from memory you choose legacy boot mode from the setup.

<?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='40'> <name>Bard</name> <uuid>92346885-a31e-1c8d-3bc9-6a32b0f13e8a</uuid> <metadata> <vmtemplate xmlns="unraid" name="FreeBSD" icon="freebsd.png" os="freebsd"/> </metadata> <memory unit='KiB'>3145728</memory> <currentMemory unit='KiB'>3145728</currentMemory> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='4'/> <vcpupin vcpu='1' cpuset='10'/> <vcpupin vcpu='2' cpuset='5'/> <vcpupin vcpu='3' cpuset='11'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-4.2'>hvm</type> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='2' threads='2'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='writeback'/> <source file='/mnt/disk3/domains/Bard/bard1.img' index='1'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </disk> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='ide' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </controller> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:b2:1a:2b'/> <source bridge='br0'/> <target dev='vnet2'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <interface type='bridge'> <mac address='52:54:00:4a:88:62'/> <source bridge='br0'/> <target dev='vnet3'/> <model type='virtio'/> <alias name='net1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/2'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/2'> <source path='/dev/pts/2'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-40-Bard/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <graphics type='vnc' port='5902' autoport='yes' websocket='5702' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </memballoon> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain> Screenshot for OPNSense:

I use opnsense fine. I will send you a copy of my config when I am back at my pc.

I would like the ability for the usb flash to mirror its config on a daily basis as an automatic backup to one of the shares and then if you plug in a fresh unraid usb stick because it died to have the option if it detects disks with a config on it to restore that backup and reboot setting itself back up and restored semi automatically so that flash failures no longer are the big deal that I see on the forums from time to time.

Maybe the wiki is out of date because when I boot unraid fresh it uses 900 something mb of ram before I even do or turn anything else on. To actually do anything needs a bit of ram on top of that.

Does the ram fill up when you start copying to unraid (check by running htop via ssh on unraid) and slow down once the memory fills up a bit? If so it means the memory fills while the transfer is quick and it has to then slow down while data written to the disk is catching up and clearing whats in ram. Adding more ram would help if this is the case.

Did you set any cpu isolation by any chance?

Not really. I dont know what specifically ‘remote into the VM’ means as it could be interpreted many ways.

Your fighting the good fight for all of us!

I use nomachine mx with it and it seems fine. You can set 60fps in that software with using the h264 codec for fastest results. Its better than vnc for sure. (I also dont have a grphics card passed and just unticked the ‘use acceleration for display processing under server options).

I guess you could try limiting it to less like 2GB and seeing what happens. Someone has to do the experiment for everyone to find out if anyone is feeling like it lol

It may be that DPI uses the database quite a bit and the DB is configured to cache as much as it can in RAM, so wthout a limit, and DPI on, it just eats up whatever it can, however with a limit is forces it to cleanup the cache as it fills close to the limit, meaning the problem you guys see is a combination of things working in conjunction to create the scenario you see.

Wow thanks, you were correct. A different browser loaded it up fine. Apologies for wasting your time.

Yes that IP is the machine I am trying from, and it prompts for the login, once it logs in I get that error though.

Here you go It does look like there are a lot of errors at the end - hopefully nothing drastic. supervisord.log

I havent altered the default settings but if you tell me where to check I can tell you what they are set to.

I cant see anything connecting and it only on my LAN. I also have never used it before and am just trying form this 1 pc at the moment so havent got very far with it. I will wait and see if anyone else has any issues connecting because I am stuck

I dont understand what to do. I stopped the docker and restarted it. If I immediatly try connect with the console web the same issue happens. How can something already be connected if I just restarted it?

Hi, I added the docker lines and config for the terminal on port 8222. When I open my browser I am prompted to authenticate and I can login, but the page that loads simply says:

I really hope someone else will look at the logs because I cant see the issue and cant thibk what else to do at this point.

https://db-ip.com/99.1.1.90

99.1.1.90 is a public IP so thats weird it was offered that if it is plugged into your lan.

There is a serious lack of willing info from the OP in this thread. I feel I am more concerned for his data than he is. Im not even sure how replacing a drive on an unprotected unraid array with a missing disk would have even worked.

No problem did you check the drive you replaced still had all the data? Which drive did you replace?