perhansen

Members
  • Posts

    143
  • Joined

  • Last visited

Posts posted by perhansen

  1. hi @BGameiro

     

    I get this in the log, after installing trilium.

    Error: EACCES: permission denied, mkdir '/home/node/trilium-data/log'

    I change the default install directory from appdata to config, so i tried to use the default one, but that did not help either. 

    The docker app wont start.

     

    ---edit---

    Looks like some write rights. I just made the folder myself, and then got this error.

    Error: EACCES: permission denied, open '/home/node/trilium-data/session_secret.txt'

     

    ---edit---

    Figured out that the trillium directory did not had the write flag. So i just changed that with chmod +w and everything seems to work now.

    • Like 1
  2. I mainly use mine for media streamning, from plex. But i also have various dockers like surveillance station, nextcloud, homeautomation, unifi controller etc.

    I also have a bunch of vms, i run from time to time. I like to try new Linux distros, and use unraid to test them in.

    Whenever i need inspiration, i look at screenshots from other unraid users, to see what docker and vms they have.

     

     

    Sent from my iPhone using Tapatalk

  3. 5 minutes ago, Hunter47 said:

    That was very interesting... I wonder if it is because of AMD rather than Intel or just because of the 2200G?...

    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. 3 minutes ago, Hunter47 said:

    Good news, the problem was the host-cpu passthrough... I created a new vm using emulated qemu64 and it went through.

    So the problem was the CPU.

    Great you got it working.

  5. 2 minutes ago, Hunter47 said:

    This is what I get with your xml :( unfortunately no luck... It seems the only difference is CPU.

    Before switching to unraid I used to have proxmox with the same hardware. I was successful with freenas as a VM inside Proxmox and worked without any issue. I wished that I had the same luck with Unraid

    Capture.PNG

    Does the log show anything?

  6. 13 minutes ago, Hunter47 said:

    I use the latest stable 6.8.3

    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. 5 minutes ago, Hunter47 said:

     

    here it is the xml.

    I also tried seabios which is also stuck at booting...

    I have tried pc-q35-2.6 as can be seen in the xml, nothing changed :(

    can you send me your xml? what is different?

    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. 16 hours ago, discojon said:

    Any updates on this?  I have the same board and experience the same issue.  Was it ever resolved?

     

    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.

  9. 38 minutes ago, johnnie.black said:

    To disable a disk you can use:

     

    
    echo 1 > /sys/block/sdX/device/delete

     

    It might not get disabled by Unraid until it tries to access it.

     

    Causing filesystem corruption it's not so easy, disk getting disabled can sometimes cause it, especially if there was still unflushed data, unclean shutdowns in general can also do it.

    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. 

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

     

     

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

  12. I was wondering if I should invest in an UPS. Since I live in Denmark, where the power is constant and last time we had a power outage was... Let me get back when I remember the year I do know it was before 2010.
    I do not need to level out the power, we have few power outages, so do I need an UPS?
     
    So How many of you use an UPS in private, and what is the reason(s) for having one?
     
    /Alphahelix
     
     


    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
  13. 26 minutes ago, johnnie.black said:

    CRC errors are a connection problem, most times the SATA cable, but it can also be the controller, backplane, etc, start by replacing the SATA cable, and note that the attribute doesn't reset, so as long as it doesn't keep increasing the problem is solved.

     

    Now that you are saying that, i recall to have heard that before :-)

    I could easily swap two sata cables between two drives, to see if the error moves with it.

    I need to order a new set of SFF-8087 LSI cables from ebay, if thats the problem.

  14. Hi guys

     

    First thing, i have been using WDreds for many years now, and have been quite happy with then.

    Some of my WDreds have been spinning for almost 5 years now, and one just started throwing CRC errors, going from 2 to 7 now on 17.

    So that definitely needs a replacement.

    The plan is to swap both my paritys for larger ones, and then swap the old paritys with the falling ones.

    The last harddrive I bought was the seagate ironwolf, but the specific drive was for important backup, so not data I use quite often.

    Will the little faster speed in the ironwolf give my any advantage, in let's say in playing multiple plex streams? I know i need to change all data drives to iron wolf, to benefit from the speed. All my drives are right now placed in 3x3in2 drive cages and is working from 30-40 degrees. The speed in ironwolf 5900-7200rpm vs. 5400rpm in WDred will of course automatically provide higher temperatures and they are using more power. The power supply i use is a corsair 450W.

    Will i be giving myself more problems by picking fast and more power hungry drives?

     

  15. 7 hours ago, cgi2099 said:

    I will try in a different slot, do you get a black screen still if you dump your own vbios and use it?

    I never did get my own vbios to work, because you need to manually remove the header from the file. Maybe you could try that. SpaceInvaderOne has some excellent guides on pass-through and editing vbios.

    I use SeaBios and Q35-4.0.1. I can see you using the newest q35-4.1, i don't know if that makes a different. I also had a lot of problems when i pass-through the USB-controller and Serial bus controller from the Vvidia GPU. Do you pass-through the Nvidia audio controller? If not, you should, that has also been giving people problems.

    • Thanks 1
  16. Thanks for the reply Perhansen. I changed the ACS override to "both" in the drop down menu but no change in the GUI settings for the VM, and the group appears the same to me in system devices except now it is in group 20:
     
    IOMMU group 20:
    [8086:244e] 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a6)
    [1102:0006] 0c:01.0 Multimedia audio controller: Creative Labs EMU10k1X [sB Live! Value/OEM Series]
    [1102:7004] 0c:01.1 Input device controller: Creative Labs [sB Live! Value] Input device controller
    [102b:0532] 0c:04.0 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G200eW WPCM450 (rev 0a)
     
    Is this what you were hoping for or should something have changed? That all said, I don't think this motherboard has onboard audio.



    No, this was certanly not was i was hoping for. I wanted each device to be in its own IOMMU group.

    Try another pci slot, as bastl mentioned.


    Sent from my iPhone using Tapatalk
  17. Hi all,
     
    I am a noob, so go easy on me. I've recently installed a Creative Labs PCI Audio card into my system and was hoping to pass through to a couple of VMs. It shows up in systems devices as this:
     
    IOMMU group 11:
    [8086:244e] 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a6)
    [1102:0006] 0c:01.0 Multimedia audio controller: Creative Labs EMU10k1X [sB Live! Value/OEM Series]
    [1102:7004] 0c:01.1 Input device controller: Creative Labs [sB Live! Value] Input device controller
    [102b:0532] 0c:04.0 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G200eW WPCM450 (rev 0a)
     
    I am not sure if this is separated correctly because the last line shows up as a graphics card option and not as a sound card option in the gui.
     
    Here are my computer specs if that helps:
     
    Model: Custom
    M/B: Supermicro X9SRH-7F/7TF Version 0123456789 - s/n: VM133S007866
    BIOS: American Megatrends Inc. Version 3.2. Dated: 02/12/2015
    CPU: Intel Xeon CPU E5-2650 0 @ 2.00GHz
    HVM: Enabled
    IOMMU: Enabled
    Cache: 512 KiB, 2048 KiB, 20480 KiB
    Memory: 32 GiB DDR3 Multi-bit ECC (max. installable capacity 512 GiB)
     
    Please let me know if there is any other information required to help me out. Thanks in advance.


    The gfx card is the onboard one, so you need to enable ACS override in the vm settings, to split the IOMMU group. Before you can passthrough the sound card.


    Sent from my iPhone using Tapatalk