bigjme

Members
  • Content count

    336
  • Joined

  • Last visited

Community Reputation

1 Neutral

About bigjme

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. bigjme

    [support] Spants - Kerberos.io template

    What trouble is it having spants? Permissions or simply getting a mount point in the docker?
  2. bigjme

    [Resolved] Primary GPU passthrough

    Hmm, I'm not entirely sure then. I followed a fix someone else found so I don't really know how they found what to do Jamie
  3. bigjme

    [Resolved] Primary GPU passthrough

    It may be something unsupported on the Web terminal, try it from an actual ssh connection, echo should always be available For mine I ssh'd in as the root user (same details as the gui), you may find the Web terminal user may be different to root Regards, Jamie
  4. bigjme

    KVM Live Backup qcow2

    Hi All, So i know this has been mentioned a million times but i'm trying to back up my VM's live without any shut down or suspensions as part of my daily incremental rsync backup. The machines in question are for CCTV and VoIP systems so they need to remain online Right now i have this which does work, it creates a temporary overlay file allowing the base image to stay unchanged. You should then be able to clone the original file which in itself should work as an isolated backup and once done merge the overlay into the main file as snapshot point on the main system virsh snapshot-create-as --domain "Windows Server 2016" $(date '+%Y-%m-%d-%H-%M-%S') --diskspec dc,file="/mnt/user/ArrayVDisks/TempVms/overlays/Windows Server 2016.qcow2" --disk-only --atomic virsh blockcommit "Windows Server 2016" hdc --active --verbose --pivot rm "/mnt/user/ArrayVDisks/TempVms/overlays/Windows Server 2016.qcow2" If i then run this command afterwards i can see the snapshot is created and i can see the overlay file be created then merged as needed virsh snapshot-list "Windows Server 2016" So far, so good But then i try and run with my rsync command and it doesn't work properly, below is a fully working copy of the code sources=( "/mnt/cache/VMImages/Windows Server 2016/" ) targets=( "/mnt/disks/Disk_1/VMImages/Windows Server 2016" ) arraylength=${#sources[@]} virsh snapshot-create-as --domain "Windows Server 2016" $(date '+%Y-%m-%d-%H-%M-%S') --diskspec hdc,file="/mnt/user/ArrayVDisks/TempVms/overlays/Windows Server 2016.qcow2" --disk-only --atomic for (( ii=1; ii<${arraylength}+1; ii++ )); do echo "Starting backup of" "${sources[$ii-1]}" " to " "${targets[$ii-1]}" mkdir -p "${targets[$ii-1]}" 2>/dev/null BACKUPS=30 END=$((BACKUPS - 1)) mv "${targets[$ii-1]}"/backup."$BACKUPS" "${targets[$ii-1]}"/backup.tmp 2>/dev/null for ((i=END;i>=0;i--)); do mv "${targets[$ii-1]}"/backup."$i" "${targets[$ii-1]}"/backup.$(($i + 1)) 2>/dev/null done mv "${targets[$ii-1]}"/backup.tmp "${targets[$ii-1]}"/backup.0 2>/dev/null cp -al "${targets[$ii-1]}"/backup.1/. "${targets[$ii-1]}"/backup.0 rsync -ahv --delete --progress --exclude "docker.img" --exclude "Program Files" "${sources[$ii-1]}" "${targets[$ii-1]}"/backup.0/ done virsh blockcommit "Windows Server 2016" hdc --active --verbose --pivot rm "/mnt/user/ArrayVDisks/TempVms/overlays/Windows Server 2016.qcow2" Using the same internal backup loop on a normal set of folders gives me proper incremental backups and only copies over file differences. For the VM image it seems to just take a full copy of the base image every time, in this instance creating a 50GB image every day rather than copying over the maybe 2GB of file differences I've really new to rsync and i'm new to the kvm virsh command line so i'm hoping i am just miss-understanding something and there is an obvious issue. I keep seeing this mentioned in some online backups for virsh as i'm doing above but i'm unsure exactly what it does or if this would fix the issue "--no-metadata" Help would be hugely appreciated as i know a lot of people are looking for the same thing. My aim is to allow this to copy the differentials to an offsite ssh server for rsync but i need to get this working locally first as i can't afford to be copying 500GB of vm images a night and having them offline during the process As an additional, i'm using qcow2 as these are running on an NVMe drive so i need them to be sparse images and just use what they need Regards, Jamie
  5. Thanks johnnie.black, i will write something to use the UUID instead
  6. bigjme

    unRAID OS version 6.5.3 available

    I'd put this update off for a while but I've done it today and no issues so far I had one vm stutter a few times after fresh server reboots but a sits just the one vm I'm assuming it's a Windows problem as a reboot fixed it Other than that, all good so far
  7. Hi All, Really sorry if this has been covered but there is just so much about this plugin that i'm struggling to find what i need I'm testing something for backups so i have attached an old usb cradle to my machine. This cradle accepts 2 HDD's and shows them as a JBOD to the host. Unassigned devices detects them as in the attached screen shot. Problem is, if i try and change the mount point names (as right now it would try and mount them both in the same place), it changes the path of both devices. Checking the config is adds this: [ICY_BOX_IB-3620_PROLIFICMP000000B86] mountpoint.1 = "/mnt/disks/ICY_BOX_ICY_BOX_IB-362" So i can't actually give them separate names as its linking to the main device names. Does anyone know how to fix this issue or work around it? I'm trying to use rsync and want to keep the permissions hence using xfs Regards, Jamie
  8. This may help, I overcame this issue recently, I put the answer in the first question
  9. bigjme

    [Resolved] Primary GPU passthrough

    Ok so i tried the above on my main card, and my other card which i currently pass to a VM. they are both 750ti's, the same make and model. Both had been passed through to a vm in a secondary slow at the time. The exported roms both times were a tiny 62KB Safe to say, booting the vm i get no error saying the device is in use, but the vm has no video output at all Having read through the export i noticed my gpu was on an older bios then the one i fetched from techpower so i went and fetched n older version, edited it to remove the jump, and booted the vm I have video output and the windows startup recovery launched. So i restarted it to boot windows. Again like before, the windows loading screen comes up, and the seconds windows starts to initialise the nvidia drivers, i get the same error 2018-05-03T20:11:39.036200Z qemu-system-x86_64: vfio_region_write(0000:04:00.0:region3+0x1088, 0x7ffe11,8) failed: Device or resource busy KVM internal error. Suberror: 1 emulation failure RAX=ffffe3fca3011000 RBX=ffffe3fca3011000 RCX=ffffe3fca3011000 RDX=0000000000000000 RSI=ffff8f8b58f44830 RDI=ffff8f8b58fb1000 RBP=ffff8f8b58efc000 RSP=ffffa30c4d3868f8 R8 =0000000000001000 R9 =0101010101010101 R10=fffff80a6783c4ac R11=ffffa30c4d3866b0 R12=ffff8f8b56a72ab0 R13=ffff8f8b58f43010 R14=0000000000000000 R15=0000000000100000 RIP=fffff80a67abb038 RFL=00010216 [----AP-] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES =002b 0000000000000000 ffffffff 00c0f300 DPL=3 DS [-WA] CS =0010 0000000000000000 00000000 00209b00 DPL=0 CS64 [-RA] SS =0018 0000000000000000 00000000 00409300 DPL=0 DS [-WA] DS =002b 0000000000000000 ffffffff 00c0f300 DPL=3 DS [-WA] FS =0053 0000000000000000 00017c00 0040f300 DPL=3 DS [-WA] GS =002b ffffd401e8712000 ffffffff 00c0f300 DPL=3 DS [-WA] LDT=0000 0000000000000000 ffffffff 00c00000 TR =0040 ffffd401e8721000 00000067 00008b00 DPL=0 TSS64-busy GDT= ffffd401e8722fb0 00000057 IDT= ffffd401e8720000 00000fff CR0=80050033 CR2=ffffe40646de7000 CR3=000000026416e000 CR4=001506f8 DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 DR6=00000000ffff0ff0 DR7=0000000000000400 EFER=0000000000000d01 Code=66 66 66 66 0f 1f 84 00 00 00 00 00 66 48 0f 6e c2 0f 16 c0 <0f> 11 01 4c 03 c1 48 83 c1 10 48 83 e1 f0 4c 2b c1 4d 8b c8 49 c1 e9 07 74 2f 0f 29 01 0f 2018-05-03T20:11:57.679635Z qemu-system-x86_64: terminating on signal 15 from pid 12367 (/usr/sbin/libvirtd) 2018-05-03 20:11:58.880+0000: shutting down, reason=destroyed I've double checked the device is in its owm iommu group and it is I've also checked the gpu is not bound to the vfio-pci driver and its not My next thought is that its because i'm booting unraid into gui mode and thats using something perhaps? --Edit Ok so i just did a fresh reboot with unraid in console mode and still, the exact same behaviour -- Edit 2 Ok so i found this post elsewhere on the forum So it says to run these 3 lines echo 0 > /sys/class/vtconsole/vtcon0/bind echo 0 > /sys/class/vtconsole/vtcon1/bind echo efi-framebuffer.0 > /sys/bus/platform/drivers/efi-framebuffer/unbind I've ran them and the vm has started up and the rom errors have vanished I'm going to run some tests and have added it into my user scripts to run on array start up to see if that is fine on a fresh restart
  10. So, another topic on this but there are a few things I want to check with my systems as I think it may just be me So I've followed spaceinvader ones video on getting a vbios for tech power up, modifying it, and using that All went well, passed through the primary gpu from unraid to a vm, did a full windows 10 install and basic setup with the gpu passed through, perfect So I installed the new nvidia drivers for my 750ti, and carried on tinkering. I then decided to reboot the vm so the video drivers could finish installing and it will no longer boot I don't get error 43 like most others. Windows starts to load, showing the loading icon with the uefi splash screen and then the vm pauses This is the vm log from boot up to shutdown 2018-05-02T20:54:30.216302Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,id=hostdev0,bus=pci.4,addr=0x0,romfile=/mnt/cache/VMImages/GPURoms/msi-750ti.rom: Failed to mmap 0000:04:00.0 BAR 3. Performance may be slow 2018-05-02T20:57:26.776428Z qemu-system-x86_64: vfio_region_write(0000:04:00.0:region3+0x1088, 0x7ffe11,8) failed: Device or resource busy KVM internal error. Suberror: 1 emulation failure RAX=ffffab7e37c11000 RBX=ffffab7e37c11000 RCX=ffffab7e37c11000 RDX=0000000000000000 RSI=ffffac04d77445c0 RDI=ffffac04d6055000 RBP=ffffac04d7f12000 RSP=ffff80890cd8d8f8 R8 =0000000000001000 R9 =0101010101010101 R10=fffff80fc1dcc4ac R11=ffff80890cd8d6b0 R12=ffffac04d3a75910 R13=ffffac04d77441e0 R14=0000000000000000 R15=0000000000100000 RIP=fffff80fc204b038 RFL=00010216 [----AP-] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES =002b 0000000000000000 ffffffff 00c0f300 DPL=3 DS [-WA] CS =0010 0000000000000000 00000000 00209b00 DPL=0 CS64 [-RA] SS =0018 0000000000000000 00000000 00409300 DPL=0 DS [-WA] DS =002b 0000000000000000 ffffffff 00c0f300 DPL=3 DS [-WA] FS =0053 0000000000000000 0000fc00 0040f300 DPL=3 DS [-WA] GS =002b ffff9b8042cb9000 ffffffff 00c0f300 DPL=3 DS [-WA] LDT=0000 0000000000000000 ffffffff 00c00000 TR =0040 ffff9b8042cc8000 00000067 00008b00 DPL=0 TSS64-busy GDT= ffff9b8042cc9fb0 00000057 IDT= ffff9b8042cc7000 00000fff CR0=80050033 CR2=ffffd180f654a000 CR3=0000000268559000 CR4=001506f8 DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 DR6=00000000ffff0ff0 DR7=0000000000000400 EFER=0000000000000d01 Code=66 66 66 66 0f 1f 84 00 00 00 00 00 66 48 0f 6e c2 0f 16 c0 <0f> 11 01 4c 03 c1 48 83 c1 10 48 83 e1 f0 4c 2b c1 4d 8b c8 49 c1 e9 07 74 2f 0f 29 01 0f 2018-05-02T20:57:45.189655Z qemu-system-x86_64: terminating on signal 15 from pid 12367 (/usr/sbin/libvirtd) Now I did have unraid booted in gui mode but I'm assuming that as it passed through for setup, this isn't the problem. So I'm a little stuck on exactly what would be causing this error as the error says its in use, but this only occurs after installing the nvidia driver. After so many boots I am able to get into the windows recovery menus which all function fine so it seems to pause the second the drivers initialized I'm on unraid 6.5.1 with the vbios passed through the gui. The vm is ovmf with Hyper-V off on Q35-2.11. I can post the full xml if it would help Any ideas as I am a little stumped? Regards, Jamie ----------- ANSWER -------- For easy reading, this was the answer needed. In the event that you get mmap errors on passing through the rom, or you install the nvidia drivers and get errors like the above, try running the following in command line and try again echo 0 > /sys/class/vtconsole/vtcon0/bind echo 0 > /sys/class/vtconsole/vtcon1/bind echo efi-framebuffer.0 > /sys/bus/platform/drivers/efi-framebuffer/unbind I added these to a user script that triggers on first array boot up. I have now successfully remove a gpu i no longer need from my system and am able to reboot unraid and have the vm auto start on the primary gpu
  11. You may be able to using command line to edit the cfg file but I would need to dig through to find that I did try to get blueiris tools to install so we could override the Web portal for one... A little nicer but i wasn't able to It seems that it is unable to override the web files so I couldn't get that to work. It launches and runs fine though I think the main things the docker needs are: Potentially blueiris tools install fixing as a side thing as i would imagine a lot of people will use that A higher resolution for the novnc display as the current one is tiny Other than that it worked OK although it was a little resource heavy compared to my native install on server 2016. One thing I did notice was that unless you enabled the blueiris option to allow it to minimise to tray (even without a password), clicking minimise would crash blue iris and you would have to reboot the docker or open task manager to kill blue iris Setting it to create a tray option works without issues though so its just a few user tweaks more than anything Edit Ok digging is done, do the following to force disable the display options mentioned below Put the attached reg file into the /root/prefix32 folder Run this command: wine regedit /root/prefix32/wine_reg_overrides.reg You can run this on boot if needed. In short it imports registries into wine that overrides the values that set those 2 visual fields to true. If there is anything else you want to tweak, here is a link to useful registry entries https://wiki.winehq.org/Useful_Registry_Keys Ooo and some information for the regedit system https://wiki.winehq.org/Regedit Edit 2 Here you go, reg edit to set blueiris to automatically go to the system tray on minimize Just like the other one, copy it to the folder and run this wine regedit /root/prefix32/blueiris_reg_overrides.reg wine_reg_overrides.reg blueiris_reg_overrides.reg
  12. So the part that wasn't working was the addition of a camera The option to close, minimise, and go full screen were all missing. Removing those options added the options in so everything looked like normal. The main blue iris interface worked fine as the close options are rendered into the app
  13. Ok so fresh install onto the docker set, i'm mapping this to a specific ip on the network so i stripped out all the port forwarding, this is the command unraid is running docker run -d --name='blueiris' --net='br1.20' --ip='192.168.20.32' -e TZ="Europe/London" -e HOST_OS="unRAID" -v '/mnt/cache/blueiris':'/root/prefix32':'rw' 'jshridha/blueiris' Now that should match your identically besides the extra bits unraid adds Port 8080 loads as normal and vnc loads, but there is nothing on the display. I'm also seeing the blueiris installer downloading on repeat still as its not running For testing purposes, is there any way to get an output from the wine command to echo into the docker log? Or even remove the suppression on the wine installer so we can see in novnc what is happening? Regards, Jamie Edit Right ok so i got this working by ssh'ing into it manually So i ssh'd into the docker and fetched a copy of the bluriris installer using wget http://blueirissoftware.com/blueiris.exe into the /root/prefix32/drive_c folder All of a sudden the novnc showed the following 2 messages, i clicked install on 1 and 2, then was shown 3. Ok so thats fine So i manually just ran wine blueiris.exe Followed the installer and it launched without an issue. So next things next, i'm going to delete the docker, re-install it, connect to it via ssh and novnc, and repeating the same again will install it My thought is that the installer may be having trouble due to where its storing (in the docker file not in the user array) One thing i would like to note, the novnc resolution is tiny so setup and usage may be an issue as everything only just fits Edit 2 Ok, more bug checking So i found that after a fresh install onto a disk array, the /root/prefix32 folder is not owned by root, see image 4.png So, i ran chown root:root prefix32, instantly the novnc started to show the above warnings as posted in 1.png and 2.png So i restarted the docker, the installer started immediately however it does not self install. It stops on the screen 5.png Doing the install by hand finished fine (although you have to tell it not to launch blue iris 4 from the tick box else it will try to launch it again) I'm now trying the cameras for testing Edit 3 Ok so all installed, camera added, and all working I've had to make a few changes to use certain aspects of blue iris properly, run this from command line within the docker winecfg -> This should open the ui -> Graphics -> Disable everything -> Apply That's all fine and working. Its also recording perfectly fine with a single 3mp camera Its a little glitchy, and i would love if blueiris launches in minimised after the install but it does run...
  14. @Bungy Do you have a screen shot of your configuration to ensure I don't miss anything? I will give this a try when I get home, just want to make sure the paths for recording are passed through correctly --Edit Ok so i finally got round to testing this and its not working on my side i'm afraid. Attached is every config screen, the output of accessing the docker via port 8080, and by connecting using vnc. Ooo and this is the docker log if its useful /usr/lib/python2.7/dist-packages/supervisor/options.py:297: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security. 'Supervisord is running as root and it is searching ' 2018-04-03 21:00:55,006 CRIT Supervisor running as root (no user in config file) 2018-04-03 21:00:55,006 WARN Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing 2018-04-03 21:00:55,015 INFO RPC interface 'supervisor' initialized 2018-04-03 21:00:55,015 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2018-04-03 21:00:55,015 INFO supervisord started with pid 1 2018-04-03 21:00:56,017 INFO spawned: 'x11vnc' with pid 9 2018-04-03 21:00:56,018 INFO spawned: 'X11' with pid 10 2018-04-03 21:00:56,020 INFO spawned: 'progman' with pid 11 2018-04-03 21:00:56,021 INFO spawned: 'x11vnc-loc' with pid 12 2018-04-03 21:00:56,023 INFO spawned: 'novnc' with pid 13 2018-04-03 21:00:57,051 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-04-03 21:00:57,052 INFO success: X11 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-04-03 21:00:57,052 INFO success: progman entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-04-03 21:00:57,052 INFO success: x11vnc-loc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-04-03 21:00:57,052 INFO success: novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-04-03 21:02:43,909 INFO exited: x11vnc-loc (exit status 0; expected) 2018-04-03 21:02:44,910 INFO spawned: 'x11vnc-loc' with pid 59 2018-04-03 21:02:45,921 INFO success: x11vnc-loc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-04-03 21:02:54,432 INFO exited: x11vnc-loc (exit status 0; expected) 2018-04-03 21:02:55,434 INFO spawned: 'x11vnc-loc' with pid 61 2018-04-03 21:02:56,447 INFO success: x11vnc-loc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-04-03 21:08:50,611 INFO exited: x11vnc (exit status 0; expected) 2018-04-03 21:08:51,614 INFO spawned: 'x11vnc' with pid 62 2018-04-03 21:08:52,624 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) Accessing via port 81 does nothing other than connection refused Regards, Jamie -- Follow up number 2 So i found out my firewall was preventing the docker from downloading the blueiris exe file which would make sense why nothing worked. So i unblocked this and re-installed the docker from scratch while keeping an eye on network traffic Having started the docker i have seen the blueiris installer download around 25 times now all fully downloaded to completion but nothing happens in the vm still. I've stopped the docker for now as it seems to have some sort of a problem with the downloads ( i can't see where these are downloading to within the docker files ) ---- followup 3 OK so Ive had a quick look, now I don't know how to write a docker or anything else but as the blueiris file is downloading on repeat I think the issue is in the blueiris.sh file My though is, your using wget to download the file, is it worth putting in full file paths to the installer? Right now it looks like it finished downloading, fails to install and therefore to run the program and just repeats the loop over and over I do have the path passed through for persistence which makes me think this may be the issue It's currently going via my normal user share so I may move the docker to store on a specific drive instead in case that's causing a problem --- edit 4 So I set the docker to store on a specific disk in the array and had the same outcome, the installer downloads, and then a few seconds later another download launches
  15. Click advanced editor in the top right

Copyright © 2005-2018 Lime Technology, Inc.
unRAID® is a registered trademark of Lime Technology, Inc.