Marv

Members
  • Content count

    180
  • Joined

  • Last visited

Community Reputation

2 Neutral

About Marv

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • Location
    Germany

Recent Profile Visitors

296 profile views
  1. TVheadend plugin for unRaid 6

    I'm using the plugin because you can't wake your server with the container. With this plugin my server wakes up for each recording when shutdown.
  2. Read errors on Parity 2

    So I ran an extended SMART test but it got aborted because errors occured. Should I replace the disk? unraid-smart-20180216-2228.zip
  3. [Plugin] ControlR

    Can confirm that all is working again. Thanks a lot
  4. VM's Hosted on SSD - TRIM?

    Hi, I recently set up my first Win10 vm and came across this thread. Are you still sure that a SSD is detected by Windows as and HDD when run in a vm? Because when I wanted to turn off the optimization schedule in disk defragment settings the media type of my vdisk was automatically shown as SSD. Anyone else recognized this?
  5. Read errors on Parity 2

    will do, thanks a lot!
  6. Hi everyone, just got home and my server reported 168 read errors on my second parity drive. As I have no idea where to look at at the smart report maybe someone can help me out here. Something to worry about? unraid-diagnostics-20180215-1748.zip unraid-smart-20180215-1746.zip
  7. [Plugin] ControlR

    there you go $ ls -al /usr/local/emhttp/plugins/ipmi /bin/ls: cannot access '/usr/local/emhttp/plugins/ipmi': No such file or directory $ ls -al /dev/ipmi0 /bin/ls: cannot access '/dev/ipmi0': No such file or directory $ ls -al /dev/ipmi/0 /bin/ls: cannot access '/dev/ipmi/0': No such file or directory $ ls -al /dev/ipmidev/0 /bin/ls: cannot access '/dev/ipmidev/0': No such file or directory $ ls -al /boot/config/plugins/ipmi/ipmi.cfg /bin/ls: cannot access '/boot/config/plugins/ipmi/ipmi.cfg': No such file or directory $ ls -al /usr/sbin/ipmisensors /bin/ls: cannot access '/usr/sbin/ipmisensors': No such file or directory $ ls -al /usr/local/emhttp/plugins/dynamix.system.temp total 16 drwxr-xr-x 5 root root 160 Aug 26 2016 ./ drwxr-xr-x 28 root root 560 Nov 18 13:54 ../ -rw-r--r-- 1 root root 287 Aug 26 2016 README.md -rw-r--r-- 1 root root 900 Aug 26 2016 TempButton.page -rw-r--r-- 1 root root 8184 Aug 26 2016 TempSettings.page drwxr-xr-x 2 root root 140 Aug 26 2016 icons/ drwxr-xr-x 2 root root 60 Aug 26 2016 images/ drwxr-xr-x 2 root root 60 Aug 26 2016 include/ $ ls -al /usr/bin/sensors -rwxr-xr-x 1 root root 22032 Nov 23 2015 /usr/bin/sensors*
  8. [Plugin] ControlR

    I never installed the ipmi plugin I also didn't change anything in my configuration after upgrading to v6.4.0/1 Your plugin worked before without any issue detecting the sensors used by the dynamix system temp plugin. Really strange
  9. [Plugin] ControlR

    here it is: system temp plugin running fine and ups status is also working with your app I: 2018/02/09 11:56:20 app.go:57: controlr v2.8.0-355-acff82c-v2018.02.02 starting ... I: 2018/02/09 11:56:20 app.go:65: No config file specified. Using app defaults ... I: 2018/02/09 11:56:20 core.go:73: starting service Core ... W: 2018/02/09 11:56:20 core.go:251: Error identifying sensor: open /boot/config/plugins/ipmi/ipmi.cfg: no such file or directory I: 2018/02/09 11:56:20 core.go:263: No sensor detected ... I: 2018/02/09 11:56:20 core.go:276: Created apc ups ... I: 2018/02/09 11:56:20 server.go:70: Starting service Server ... I: 2018/02/09 11:56:20 server.go:89: Serving files from /usr/local/emhttp/plugins/controlr I: 2018/02/09 11:56:20 server.go:139: Server started listening https on :2378 I: 2018/02/09 11:56:20 api.go:46: Starting service Api ... I: 2018/02/09 11:56:20 api.go:90: Api started listening https on :2382 I: 2018/02/09 11:56:20 app.go:85: Press Ctrl+C to stop ... I: 2018/02/09 14:05:59 app.go:89: Received signal: (terminated) ... shutting down the app now ... I: 2018/02/09 14:05:59 api.go:105: stopped service Api ... I: 2018/02/09 14:05:59 server.go:156: stopped service Server ... I: 2018/02/09 14:05:59 core.go:141: stopped service Core ... I: 2018/02/09 14:56:20 app.go:57: controlr v2.8.0-355-acff82c-v2018.02.02 starting ... I: 2018/02/09 14:56:20 app.go:65: No config file specified. Using app defaults ... I: 2018/02/09 14:56:20 core.go:73: starting service Core ... W: 2018/02/09 14:56:20 core.go:251: Error identifying sensor: open /boot/config/plugins/ipmi/ipmi.cfg: no such file or directory I: 2018/02/09 14:56:20 core.go:263: No sensor detected ... I: 2018/02/09 14:56:20 core.go:276: Created apc ups ... I: 2018/02/09 14:56:20 server.go:70: Starting service Server ... I: 2018/02/09 14:56:20 server.go:89: Serving files from /usr/local/emhttp/plugins/controlr I: 2018/02/09 14:56:20 server.go:139: Server started listening https on :2378 I: 2018/02/09 14:56:20 api.go:46: Starting service Api ... I: 2018/02/09 14:56:20 api.go:90: Api started listening https on :2382 I: 2018/02/09 14:56:20 app.go:85: Press Ctrl+C to stop ... I: 2018/02/09 17:24:56 api.go:134: received /info I: 2018/02/09 17:24:56 api.go:142: info({Version:2 Wake:{Mac:78:24:af:3b:1f:a9 Broadcast:255.255.255.255} Prefs:{Number:., Unit:C} Samples:[{Key:UPS STATUS Value:Online Unit: Condition:green} {Key:UPS LOAD Value:26.0 Unit:% Condition:green} {Key:UPS CHARGE Value:100.0 Unit:% Condition:green} {Key:UPS LEFT Value:17.0 Unit:m Condition:green} {Key:UPS POWER Value:140.4 Unit:w Condition:green}] Features:map[sleep:true]}) I: 2018/02/09 17:24:57 api.go:110: log (system) requested
  10. Thanks for clarifying
  11. [Plugin] ControlR

    Many thanks for your work. Everything working again for me except I don't get my fan speeds and temperatures shown anymore in the app. This worked before unraid 6.4.0. Not sure if I need to change something now in my system temp plugin or where is the data for your plugin comming from?
  12. Can someone clear me up here please?
  13. Hi, I just removed my self-signed cert <server-name>_unraid_bundle.pem after upgrading as described in the first post. Unfortunately, my server doesn't create a new one after reboot. I still have the other file in my certs folder so which one does my server actually use and how do I get back the other file? A bit confused here.
  14. thanks for your advice. But unfortunatley I can't get it to work. Just tried everything from SeaBIOS with i440fx and Q35 aswell as OVMF with i440fx and Q35. Still no success. It all worked before without any issue. I can install SteamOS without any problem via VNC and when I assign my GPU afterwards it boots, updates steam and restarts itself again. From there on it doesn't reach the desktop anymore. Anyone got an idea please?
  15. Hi, just recognized that my SteamOS vm isn't booting anymore since using unraid 6.4.0. I'm 100% sure I didn't change its configuration. I already tried reinstalling and when I do this I get into desktop mode. But after another reboot it isn't booting again. Someone got an idea and can help please? this is what the vm log shows: 2018-02-03 10:24:53.733+0000: starting up libvirt version: 3.8.0, qemu version: 2.10.2, hostname: SteamOS LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name guest=SteamOS,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-30-SteamOS/master-key.aes -machine pc-q35-2.10,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host -drive file=/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/etc/libvirt/qemu/nvram/f6d09174-f5c4-eabc-4861-d4bb0e8da709_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 2048 -realtime mlock=off -smp 2,sockets=1,cores=2,threads=1 -uuid f6d09174-f5c4-eabc-4861-d4bb0e8da709 -display none -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-30-SteamOS/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -boot strict=on -device pcie-root-port,port=0x8,chassis=1,id=pci.1,bus=pcie.0,multifuncti2018-02-03 10:24:53.734+0000: Domain id=30 is tainted: high-privileges 2018-02-03 10:24:53.734+0000: Domain id=30 is tainted: host-cpu 2018-02-03T10:24:53.795214Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0) here is my xml file: <domain type='kvm'> <name>SteamOS</name> <uuid>f6d09174-f5c4-eabc-4861-d4bb0e8da709</uuid> <description>SteamOS</description> <metadata> <vmtemplate xmlns="unraid" name="SteamOS" icon="steamos.png" os="steamos"/> </metadata> <memory unit='KiB'>2097152</memory> <currentMemory unit='KiB'>2097152</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='3'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-2.10'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/f6d09174-f5c4-eabc-4861-d4bb0e8da709_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='2' threads='1'/> </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/domains/SteamOS/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/ISOs/SteamOSDVD-2.148.iso'/> <target dev='hda' bus='sata'/> <readonly/> <boot order='2'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <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> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <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='0x8'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x9'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0xa'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0xb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0xc'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0xd'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/> </controller> <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0xe'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x6'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:f9:3c:9d'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </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='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x00' slot='0x1b' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x045e'/> <product id='0x0719'/> </source> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc52b'/> <address bus='3' device='3'/> </source> <address type='usb' bus='0' port='2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc52b'/> <address bus='3' device='5'/> </source> <address type='usb' bus='0' port='3'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </memballoon> </devices> </domain>

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