Jump to content

perhansen

Members
  • Content Count

    141
  • Joined

  • Last visited

Community Reputation

11 Good

About perhansen

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • Location
    Denmark

Recent Profile Visitors

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

  1. Thanks man, will have to try this out in both my Windows vm. Sent from my iPhone using Tapatalk
  2. +1 for this as well. It's not a dealbreaker for me, because i have been using midnight commander for years now, not just on unraid, but on all my linux distros for the last 25ish years.
  3. I think its more complicated then just the CPU, because i now for sure it will run on Ryzen 2200G and without ECC memory, so thats not the problem.
  4. So the problem was the CPU. Great you got it working.
  5. Does the log show anything?
  6. My xml is from long time back before 6.8.3, but i just tried a new fresh install, with your xml. Everything booted fine, i came all the way to the GUI installer. Maybe the different is the CPU. Try with Q35-4.2 or better, make a new vm with different name and just copy my xml, but leave out the part with my disk setup. You also might need to change some part with the USB, depending of your system, unraid will notify you about that before booting the vm.
  7. What version of unraid are you using? Consider filling out your signature and it will be easier to help. My xml: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>FreeNAS</name> <uuid>9b5aebda-154f-4bc7-5230-6c6e31d8ded8</uuid> <description>NAS</description> <metadata> <vmtemplate xmlns="unraid" name="FreeBSD" icon="/mnt/cache/VM/icons/freenas.png" os="freebsd"/> </metadata> <memory unit='KiB'>6291456</memory> <currentMemory unit='KiB'>6291456</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='3'/> <vcpupin vcpu='1' cpuset='13'/> <vcpupin vcpu='2' cpuset='4'/> <vcpupin vcpu='3' cpuset='14'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-3.1'>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='raw' cache='writeback'/> <source file='/mnt/user/VM/FreeNAS/vdisk1.img'/> <target dev='hdc' bus='sata'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/VM/FreeNAS/vdisk2.img'/> <target dev='hdd' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='3'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/VM/FreeNAS/vdisk3.img'/> <target dev='hde' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='4'/> </disk> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x10'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:5f:6b:d3'/> <source bridge='br0'/> <model type='e1000-82545em'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='da'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </memballoon> </devices> </domain>
  8. I also have it running. Post your xml file. Sent from my iPhone using Tapatalk
  9. I don't know if it's the same problem as yours, but i had complete freeze of unraid, with my GTX1660. I manage to get it working, by NOT passing through the USB controller on the GFX. It has been working like this since 6.7.
  10. Thanks man. I was hoping you would respond on this. I will try different methods with your command. Disable while copying data or accessing it at the same time. Unclean shutdown while copying data etc.
  11. Hi there Is there a good way to generate read fault, filesystem fault etc. on unraid. You may be wondering why I want to do it and why I bother to spend time on it. I have been running unraid for the last 6 years now, and never had any major break down, emulated disk, or failing disk. Yes i have swapped disks and changed disks around, but never because of a failure. I have multiply disks laying around going from 100GB to 2TB, that i am not using. Some of them are going in my test-server now. I wont to test some unraid failure handling, just for my own sake, i know there is some great wiki pages about all of this, but that just isn't the same as you have done the procedures by hand. Its better to test now in a controlled environment, before my critical system breaks down, and you are stressing because of possible data loss. Also, all my main disks are encrypted, so i wont to mount one of those with unassigned disk or maybe my main linux rig, just to see the behavior of those procedures. So is there a way to generate fault that will put unraid in emulated state or filesystem error or whatever faults that can be generated. I dont mind pulling sata cables while there is power on, but that cant be all.
  12. Hi there. My Shinobi log keeps filling up with this error {"f":"trigger","id":"wUEfhAPUd6","ke":"wjDSbcgmOV","name":"ABqYf","details":{"plug":"built-in","name":"ABqYf","reason":"motion","confidence":14},"plates":[],"imgHeight":"480","imgWidth":"640","doObjectDetection":false}{"f":"trigger","id":"wUEfhAPUd6","ke":"wjDSbcgmOV","name":"ABqYf","details":{"plug":"built-in","name":"ABqYf","reason":"motion","confidence":7},"plates":[],"imgHeight":"480","imgWidth":"640","doObjectDetection":false} SyntaxError: Unexpected token { in JSON at position 218 at JSON.parse (<anonymous>) at Socket.<anonymous> (/opt/shinobi/libs/monitor.js:1085:39) at emitOne (events.js:116:13) at Socket.emit (events.js:211:7) at addChunk (_stream_readable.js:263:12) at readableAddChunk (_stream_readable.js:250:11) at Socket.Readable.push (_stream_readable.js:208:10) at Pipe.onread (net.js:601:20) There was an error parsing a detection event It's the motion detection event that is triggering this. I have tried to delete the motion detection region and made a new one, but with same effect. This only occurs on this one camera. I have another camera, same model, where there is no error from. I have also tried to copy settings within Shinobi, with no effect. What could cause this error? When i leave my Shinobi open, my camera monitors suddenly turns black after 7 minutes, is this normal? ---edite--- I am not even sure that my motion detection is working. I get motion records from both cameras outside the red motion detection region.
  13. I also live in Denmark and would never run a 24/7 server without a ups. The biggest advantage for me is that the ups will do a normal shutdown of the server, when power runs out. Sent from my iPhone using Tapatalk
  14. Check the memory. I used to get those sort of behaviour with the GUI, when i was running low on memory. Sent from my iPhone using Tapatalk
  15. Upgraded from 6.8.1-rc1. Everything working fine. Thanks limetech and team. Sent from my iPhone using Tapatalk