Jump to content

PilotReelMedia

Members
  • Content Count

    12
  • Joined

  • Last visited

Community Reputation

0 Neutral

About PilotReelMedia

  • Rank
    Member

Recent Profile Visitors

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

  1. Also useful information. Thank you for showing me how to isolate it in the kernel. Had it selected and thought that was all that need be done.
  2. Are you referring the assignment at the bottom of the VM edit page. If so I have the logitech device checked. "It stems from interaction between qemu/kvm, both of which we keep up with latest releases, both of which we have no control over. " <- Usefull information. Thanks
  3. Great. I will need to see what got mangled with my particular update. I appreciate the info.
  4. Wired keyboard works and I've ordered the wired version of the Logitech keyboard to replace. Would be more interested to find out if the new configuration can be modified to fix the problem. If that's of no interest to you guys then you've lost a little stock in my humble opinion. I love the community here and the shear utility of your product, but can't help feeling a bit let down by that comment coming from a Limetech rep..
  5. Please don't be confused. It appears that something in the update has boxed support for wireless logitech keyboards. Specifically the K800 and MK540 models. I use the K800 on all my machines and the only model I have been able to get passing through to the VM's is an old Asus wireless keyboard for a Eee pc. It has never been a problem before the update and since I have verified that the Logitech keyboards are working I don't think it's stretch that something in the update has caused a conflict with this hardware. I can interact with the machine but not through to VM's.
  6. Originally posted and was told to remove because my problem was probably not a bug. I have tested two Logitech wireless keyboards and Keyboard and mouse combos and only my older Asus wireless keyboard seems to work now. It's a bug! My Logitech keyboard worked fine tel 6.8.1 Can this be fixed?
  7. After last update my logitech keyboard no longer passes through to my VM's System Log File: Jan 14 04:46:43 TOWER kernel: vfio-pci 0000:06:00.0: No more image in the PCI ROM Jan 14 04:46:43 TOWER kernel: vfio-pci 0000:06:00.0: No more image in the PCI ROM Jan 14 04:46:44 TOWER kernel: vfio-pci 0000:06:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Jan 14 04:46:53 TOWER kernel: usb 2-1.5: reset high-speed USB device number 3 using ehci-pci Jan 14 04:49:02 TOWER kernel: usb 1-1.5: reset full-speed USB device number 4 using ehci-pci Jan 14 04:49:02 TOWER kernel: usb 3-3.4: reset full-speed USB device number 4 using xhci_hcd Jan 14 04:49:03 TOWER kernel: br0: port 3(vnet0) entered disabled state Jan 14 04:49:03 TOWER avahi-daemon[11004]: Interface vnet0.IPv6 no longer relevant for mDNS. Jan 14 04:49:03 TOWER avahi-daemon[11004]: Leaving mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:fe76:aba. Jan 14 04:49:03 TOWER kernel: device vnet0 left promiscuous mode Jan 14 04:49:03 TOWER kernel: br0: port 3(vnet0) entered disabled state Jan 14 04:49:03 TOWER avahi-daemon[11004]: Withdrawing address record for fe80::fc54:ff:fe76:aba on vnet0. Jan 14 04:49:03 TOWER kernel: usb 2-1.5: reset high-speed USB device number 3 using ehci-pci Jan 14 04:49:03 TOWER kernel: usb-storage 2-1.5:1.0: USB Mass Storage device detected Jan 14 04:49:03 TOWER kernel: scsi host0: usb-storage 2-1.5:1.0 Jan 14 04:49:03 TOWER kernel: usb 3-3.4: reset full-speed USB device number 4 using xhci_hcd Jan 14 04:49:03 TOWER kernel: input: Mad Catz Mad Catz R.A.T. Pro S as /devices/pci0000:00/0000:00:02.0/0000:03:00.0/usb3/3-3/3-3.4/3-3.4:1.0/0003:0738:1722.000D/input/input16 Jan 14 04:49:03 TOWER kernel: hid-generic 0003:0738:1722.000D: input,hidraw4: USB HID v1.11 Mouse [Mad Catz Mad Catz R.A.T. Pro S] on usb-0000:03:00.0-3.4/input0 Jan 14 04:49:03 TOWER kernel: hid-generic 0003:0738:1722.000E: hiddev97,hidraw5: USB HID v1.11 Device [Mad Catz Mad Catz R.A.T. Pro S] on usb-0000:03:00.0-3.4/input1 Jan 14 04:49:03 TOWER kernel: input: Mad Catz Mad Catz R.A.T. Pro S as /devices/pci0000:00/0000:00:02.0/0000:03:00.0/usb3/3-3/3-3.4/3-3.4:1.2/0003:0738:1722.000F/input/input17 Jan 14 04:49:03 TOWER kernel: hid-generic 0003:0738:1722.000F: input,hidraw6: USB HID v1.11 Keyboard [Mad Catz Mad Catz R.A.T. Pro S] on usb-0000:03:00.0-3.4/input2 Jan 14 04:49:03 TOWER kernel: input: Mad Catz Mad Catz R.A.T. Pro S as /devices/pci0000:00/0000:00:02.0/0000:03:00.0/usb3/3-3/3-3.4/3-3.4:1.3/0003:0738:1722.0010/input/input18 Jan 14 04:49:03 TOWER kernel: hid-generic 0003:0738:1722.0010: input,hidraw7: USB HID v1.11 Device [Mad Catz Mad Catz R.A.T. Pro S] on usb-0000:03:00.0-3.4/input3 Jan 14 04:49:03 TOWER kernel: usb 1-1.5: reset full-speed USB device number 4 using ehci-pci Jan 14 04:49:03 TOWER kernel: logitech-djreceiver 0003:046D:C52B.0013: hiddev98,hidraw8: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:1a.0-1.5/input2 Jan 14 04:49:03 TOWER kernel: input: Logitech K800 as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.2/0003:046D:C52B.0013/0003:046D:406E.0014/input/input19 Jan 14 04:49:03 TOWER kernel: logitech-hidpp-device 0003:046D:406E.0014: input,hidraw9: USB HID v1.11 Keyboard [Logitech K800] on usb-0000:00:1a.0-1.5:2 Jan 14 04:49:03 TOWER kernel: logitech-hidpp-device 0003:046D:406E.0014: unable to retrieve the name of the device Jan 14 04:49:04 TOWER kernel: vfio-pci 0000:06:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Jan 14 04:49:04 TOWER kernel: scsi 0:0:0:0: CD-ROM ASUS BW-12D1S-U E102 PQ: 0 ANSI: 0 Jan 14 04:49:04 TOWER kernel: sr 0:0:0:0: [sr0] scsi3-mmc drive: 125x/125x writer dvd-ram cd/rw xa/form2 cdda tray Jan 14 04:49:04 TOWER kernel: sr 0:0:0:0: Attached scsi CD-ROM sr0 Jan 14 04:49:04 TOWER kernel: sr 0:0:0:0: Attached scsi generic sg0 type 5 Jan 14 04:52:41 TOWER ntpd[2641]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Jan 14 04:53:00 TOWER root: Fix Common Problems Version 2019.12.29 Jan 14 04:53:00 TOWER root: Fix Common Problems: Warning: disk9 (SPCC_Solid_State_Disk_B7E0078C115300189267) is an SSD. ** Ignored Jan 14 04:53:00 TOWER root: Fix Common Problems: Warning: disk10 (SPCC_Solid_State_Disk_6D13078C120800038249) is an SSD. ** Ignored Jan 14 04:53:00 TOWER root: Fix Common Problems: Warning: disk11 (C300-CTFDDAC256MAG_0000000010160000D119) is an SSD. ** Ignored VM log file: -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=32,server,nowait \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=localtime \ -no-hpet \ -no-shutdown \ -boot strict=on \ -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 \ -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x7 \ -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x7.0x1 \ -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x7.0x2 \ -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x3 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 \ -blockdev '{"driver":"file","filename":"/mnt/user/domains/LapDragonVM/LapDragon.img","node-name":"libvirt-2-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-2-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-2-storage"}' \ -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=libvirt-2-format,id=virtio-disk2,bootindex=1,write-cache=on \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/virtio-win-0.1.160-1.iso","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-1-format","read-only":true,"driver":"raw","file":"libvirt-1-storage"}' \ -device scsi-cd,bus=scsi0.0,channel=0,scsi-id=0,lun=1,device_id=drive-scsi0-0-0-1,drive=libvirt-1-format,id=scsi0-0-0-1 \ -netdev tap,fd=35,id=hostnet0,vhost=on,vhostfd=36 \ -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:76:0a:ba,bus=pci.0,addr=0x2 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0 \ -chardev socket,id=charchannel0,fd=38,server,nowait \ -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ -device usb-tablet,id=input0,bus=usb.0,port=1 \ -device vfio-pci,host=0000:06:00.0,id=hostdev0,x-vga=on,bus=pci.0,addr=0x6 \ -device vfio-pci,host=0000:06:00.1,id=hostdev1,bus=pci.0,addr=0x8 \ -device usb-host,hostbus=1,hostaddr=4,id=hostdev2,bus=usb.0,port=2 \ -device usb-host,hostbus=3,hostaddr=4,id=hostdev3,bus=usb.0,port=3 \ -device usb-host,hostbus=2,hostaddr=3,id=hostdev4,bus=usb.0,port=4 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2020-01-14 11:51:38.019+0000: Domain id=1 is tainted: high-privileges 2020-01-14 11:51:38.019+0000: Domain id=1 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2020-01-14T11:51:45.759577Z qemu-system-x86_64: vfio: Cannot reset device 0000:06:00.1, depends on group 24 which is not owned. 2020-01-14T11:52:49.915193Z qemu-system-x86_64: terminating on signal 15 from pid 14629 (/usr/sbin/libvirtd) I highlighted the relevant area of the system log but have no idea how to resolve.. Can anyone help me fix this?
  8. I got a notification on the web GUI yesterday that the flash drive had failed and was no longer read and write enabled. I immediately backed up the flash before attempting to reboot the system to see if the thumb drive in-fact had failed which and it had, and the system failed to boot on restart. Thinking I had my bases covered I pulled the OS thumb drive to verify it's state. I could view the the files but cannot write to the original thumb drive, nor can I run check disk to see if windows can repair the files. I then attempted to restore the back up to a new thumb drive but I can't get past the limetech boot screen without it restarting the system. I have attempted to launch unraid in all possible options to know avail, it just keeps restarting. MEMTEST86 did function and the system passed. I'm at a loss. Did the corruption of the flash create errors on the back I'm attempting to restore? If so can I restore the system some other way!?! I have attached both system log file to be reviewed by those who are far more experienced to look at if anyone can help. Just noticed that the (bzroot file is empty on back-up) This seems to be the issue with the original flash drive. There appears to be data in the original file but I can't access or repair the file. Any suggestions? OK Jon @ UNRaid very quickly responded to request for assistance with this issue. the solution that got me up and running again was as follows: Problem (As drive failed base files in the root folder became corrupt) Solution (Replace all files in the root directory using the manual OS download files while leaving original configuration and all folders from the back up.) I'm back up.. Thank's Jon syslog.txt syslog1.txt
  9. I was hoping that some of the reviews about short term flash drive failures were just a few people using dated hardware. My new UNRaid server with just over 60 days of operating time gave a notification the the USB drive was no longer read/write capable and had failed. (A brand new thumb drive!) This now has me very concerned because the hook is one replacement per year. I hope my next lasts the remaining 10 months. I hope you wizards of code at unraid are flexible if someone has a bad run of luck with drives. If anyone else has experienced short life issue with their USB OS, I would be very interested to hear your story and or how UNRaid dealt with you if you needed and 3rd replacement. Update: I got a notification on the web GUI yesterday that the flash drive had failed and was no longer read and write enabled. I immediately backed up the flash before attempting to reboot the system to see if the thumb drive in-fact had failed which and it had, and the system failed to boot on restart. Thinking I had my bases covered I pulled the OS thumb drive to verify it's state. I could view the the files but cannot write to the original thumb drive, nor can I run check disk to see if windows can repair the files. I then attempted to restore the back up to a new thumb drive but I can't get past the limetech boot screen without it restarting the system. I have attempted to launch unraid in all possible options to know avail, it just keeps restarting. MEMTEST86 did function and the system passed. I'm at a loss. Did the corruption of the flash create errors on the back I'm attempting to restore? If so can I restore the system some other way!?! I have attached both system log file to be reviewed by those who are far more experienced to look at if anyone can help. Just noticed that the (bzroot file is empty on back-up) This seems to be the issue with the original flash drive. There appears to be data in the original file but I can't access or repair the file. Any suggestions? OK Jon @ UNRaid very quickly responded to request for assistance with this issue. the solution that got me up and running again was as follows: Problem (As drive failed base files in the root folder became corrupt) Solution (Replace all files in the root directory using the manual OS download files while leaving original configuration and all folders from the back up.) I'm back up.. Thank's Jon