Jump to content

harshl

Members
  • Content Count

    71
  • Joined

  • Last visited

Community Reputation

3 Neutral

About harshl

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. ASRock Z390 Taichi Bios - Version P4.00. Dated: 03/13/2019 Intel® Core™ i9-9900K Been super solid for me so far. Hope your able to figure something out.
  2. For what it's worth, I have the following card working well, moved from a Vega 56 due to the reset bug making my life more difficult than it needed to be. MSI Gaming GeForce RTX 2060 Super 8GB GDRR6 256-bit HDMI/DP G-SYNC Turing Architecture Overclocked Graphics Card (RTX 2060 Super Armor OC).
  3. Well, I'm updating this post from Linux Mint with the video card passed through and everything working as it should in my Windows VM, which will no longer boot. I don't even know what to look at. Crazy that it will work fine in one VM and not in another. If anyone has any wise ideas, let me know. Thanks!
  4. Thanks! I only have it check once a week so it wasn't showing an update yet. I should have tried a forced update. Working fine now. Thanks again!
  5. Noticed my ownCloud container was down after a reboot today. Started it manually and it shut back down on its own. Seeing the following in the logs. Should I just blow the container away and recreate it or is there something I can do to fix this? Not sure what caused it. Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... The following packages will be upgraded: exim4 exim4-base exim4-config exim4-daemon-light libblkid1 libfdisk1 libmount1 libsmartcols1 libuuid1 mount psmisc 11 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 2,246 kB of archives. After this operation, 3,072 B of additional disk space will be used. Get:1 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 mount amd64 2.27.1-6ubuntu3.8 [121 kB] Get:2 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 libuuid1 amd64 2.27.1-6ubuntu3.8 [14.4 kB] Get:3 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 libblkid1 amd64 2.27.1-6ubuntu3.8 [107 kB] Get:4 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 libfdisk1 amd64 2.27.1-6ubuntu3.8 [139 kB] Get:5 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 libmount1 amd64 2.27.1-6ubuntu3.8 [114 kB] Get:6 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 libsmartcols1 amd64 2.27.1-6ubuntu3.8 [62.0 kB] Get:4 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 libfdisk1 amd64 2.27.1-6ubuntu3.8 [139 kB] Get:5 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 libmount1 amd64 2.27.1-6ubuntu3.8 [114 kB] Get:6 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 libsmartcols1 amd64 2.27.1-6ubuntu3.8 [62.0 kB] Get:7 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 psmisc amd64 22.21-2.1ubuntu0.1 [48.1 kB] Get:8 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 exim4-config all 4.86.2-2ubuntu2.5 [298 kB] Get:9 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 exim4 all 4.86.2-2ubuntu2.5 [7,926 B] Get:10 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 exim4-base amd64 4.86.2-2ubuntu2.5 [870 kB] Get:11 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 exim4-daemon-light amd64 4.86.2-2ubuntu2.5 [466 kB] Preconfiguring packages ... Fetched 2,246 kB in 1s (2,090 kB/s) Setting up util-linux (2.27.1-6ubuntu3.8) ... Configuration file '/etc/cron.weekly/fstrim' ==> Deleted (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** fstrim (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package util-linux (--configure): end of file on stdin at conffile prompt Errors were encountered while processing: util-linux E: Sub-process /usr/bin/dpkg returned an error code (1) Reading package lists... Building dependency tree... Reading state information... 0 upgraded, 0 newly installed, 0 to remove and 11 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up util-linux (2.27.1-6ubuntu3.8) ... Configuration file '/etc/cron.weekly/fstrim' ==> Deleted (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** fstrim (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package util-linux (--configure): end of file on stdin at conffile prompt Errors were encountered while processing: util-linux E: Sub-process /usr/bin/dpkg returned an error code (1) *** /etc/my_init.d/20_apt_update.sh failed with status 100 *** Killing all processes... Sep 7 20:41:53 537e263b9b6f syslog-ng[17]: syslog-ng shutting down; version='3.5.6' Thanks!
  6. Well, this was unexpected, but the Linux VM booted right up and produced video. It produced a bunch of garbage on the screen and hung during the boot, but I suspect that is a different issue entirely. So... what persists even through a VM deletion and recreation besides the disk that might be hanging this up? I'm stumped! -Landon
  7. I recently implemented a VM backup script from JTok referenced here: Three VMs were targeted for backup. Two with VNC graphics and one with a Vega 56 card being passed through. This VM with the Vega 56 has been running great for me since November of 2018. Once this script ran, it did not succeed on the gaming VM with the Vega card passed through. The logs/notifications seem to indicate it didn't shutdown in time, but I'm not 100% sure. Upon going to the server to check on it, the video card was at maximum fan speed and the gaming VM was down. I powered the server down to reset the Video and USB cards that are passed through and let it boot back up. The VM attempts to start and does not produce any errors when manually started, but it never produces any video and does not actually boot either. I removed the video card and put a VNC adapter in the config and it boots right up with the USB card still passed through. So the video card is producing some kind of issue, but I don't know what. I don't see any obvious errors anywhere. The VM never does actually start with the video card passed through now, the 4 vCPUs that are assigned are all flatlined at 0 with the exception of the first core, which has an occasional 1% and I never see it appear on the network. I have tried destroying the VM and recreating it and I get the exact same behavior. Anonymized diagnostics are attached. Here are the VM logs for the system with the issue: -device pcie-root-port,port=0x12,chassis=3,id=pci.3,bus=pcie.0,addr=0x2.0x2 \ -device pcie-root-port,port=0x13,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x3 \ -device pcie-root-port,port=0x14,chassis=5,id=pci.5,bus=pcie.0,addr=0x2.0x4 \ -device pcie-root-port,port=0x15,chassis=6,id=pci.6,bus=pcie.0,addr=0x2.0x5 \ -device pcie-root-port,port=0xa,chassis=7,id=pci.7,bus=pcie.0,addr=0x1.0x2 \ -device pcie-root-port,port=0xb,chassis=8,id=pci.8,bus=pcie.0,addr=0x1.0x3 \ -device pcie-pci-bridge,id=pci.9,bus=pci.1,addr=0x0 \ -device ich9-usb-ehci1,id=usb,bus=pcie.0,addr=0x7.0x7 \ -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pcie.0,multifunction=on,addr=0x7 \ -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pcie.0,addr=0x7.0x1 \ -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pcie.0,addr=0x7.0x2 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.2,addr=0x0 \ -drive file=/mnt/user/domains/cubegaming/vdisk1.img,format=raw,if=none,id=drive-virtio-disk2,cache=none \ -device virtio-blk-pci,scsi=off,bus=pci.4,addr=0x0,drive=drive-virtio-disk2,id=virtio-disk2,bootindex=1,write-cache=on \ -drive file=/mnt/user/domains/cubegaming/vdisk2.img,format=raw,if=none,id=drive-virtio-disk3,cache=none \ -device virtio-blk-pci,scsi=off,bus=pci.5,addr=0x0,drive=drive-virtio-disk3,id=virtio-disk3,write-cache=on \ -drive file=/mnt/user/isos/en_windows_10_business_editions_version_1903_updated_july_2019_x64_dvd_97049592.iso,format=raw,if=none,id=drive-sata0-0-0,readonly=on \ -device ide-cd,bus=ide.0,drive=drive-sata0-0-0,id=sata0-0-0,bootindex=2 \ -drive file=/mnt/user/isos/virtio-win-0.1.160-1.iso,format=raw,if=none,id=drive-sata0-0-1,readonly=on \ -device ide-cd,bus=ide.1,drive=drive-sata0-0-1,id=sata0-0-1 \ -netdev tap,fd=32,id=hostnet0,vhost=on,vhostfd=33 \ -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:b2:9f:1a,bus=pci.3,addr=0x0 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0 \ -chardev socket,id=charchannel0,fd=35,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 \ -vnc 0.0.0.0:3,websocket=5703 \ -k en-us \ -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.9,addr=0x1 \ -device vfio-pci,host=03:00.0,id=hostdev0,bus=pci.6,addr=0x0 \ -device vfio-pci,host=03:00.1,id=hostdev1,bus=pci.7,addr=0x0 \ -device vfio-pci,host=0b:00.0,id=hostdev2,bus=pci.8,addr=0x0 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2019-09-07 18:22:37.573+0000: Domain id=6 is tainted: high-privileges 2019-09-07 18:22:37.573+0000: Domain id=6 is tainted: host-cpu char device redirected to /dev/pts/3 (label charserial0) 2019-09-07T18:34:36.168070Z qemu-system-x86_64: terminating on signal 15 from pid 7305 (/usr/sbin/libvirtd) 2019-09-07 18:34:37.368+0000: shutting down, reason=destroyed Any thoughts on what might be going on here? The video card is fine. I pulled it from my server and dropped it into another system and it worked fine. I am creating a Linux VM and will try passing this through shortly as well and will report back what behavior I see with that when I am done testing. Any guidance is appreciated! -Landon diagnostics-20190907-1840.zip
  8. I proceeded with this update as described and can confirm I had no issues at all. Thanks for the great container!!
  9. Dropped a couple of these (CT500MX500SSD1) into a buddies server for a cache tier and started seeing these messages within 24 hours. Seem to be getting them sporadically now, several times a day. Appreciate everyones feedback, nice to know it is not a failing drive on this particular model. I will open up a ticket with them as well just to make a little more noise. Thanks!
  10. UNRAID 6.6.6 When creating a new VM and adding multiple NICs to the VM, you have to add one, generate the MAC, update the VM, edit the VM again, add the NIC, generate the MAC, update the VM, lather, rinse, repeat, until you have all of your desired NICs. Is it possible to make it so we can add many NICs in one motion (one update to the VM)? I honestly don't recall if this was possible in prior releases. thecube-diagnostics-20190205-1053.zip
  11. I know this thread is a bit old, but I had a similar issue and what I ended up doing was setting the BIOS settings such that it would always power on after a power failure (or power loss). I disconnected the front panel power and reset switches. When I need to shutdown and power back on the system, I simply flip the power supply switch to the off position (or remove the cord if your supply doesn't have a switch), then reapply power and the system powers back on. Fairly simple solution that may meet the OP's needs, though I am sure you worked something out by now.
  12. Minor unconfirmed update on this. I have abandoned one particular M.2 slot and I'm running both drives in the lower M.2 slots that are side by side. So far this issue has not repeated, but since I don't know what triggers it, it could be a false sense of security at this point. I will let it run for another week or two and see where I end up and report back. Hopefully I can run for that period of time without needing to reboot the host for any other reasons.
  13. I followed SpaceInvaderOne's video for optimizing the VM. It is for sure set to Performance. I will check to see if any other Sleep settings are enabled that I can find. I can have the VM sit idle for days and this won't occur, but the second someone prints, it happens. The USB for the UPS is not passed through to the guest, it is only seen by the host and is recognized and queried properly by UNRAID. Shouldn't be any way for the VM to communicate with it. I'm not, per my previous posts clarifying this, the printer is not plugged into the UPS, it is simply on the same electrical circuit (breaker) and causes enough sag on the circuit for the UPS to flip to battery for two seconds, then back to utility. It isn't even enough sag to shut anything down. XBOX, TV and other computers in the room all keep functioning just fine, but the UPS is sensitive enough that it kicks over briefly. Appreciate the pointers @bastl, hopefully I will find something. In the meantime, I have ordered an extension cable so I can run the printer power to a nearby dedicated circuit so it won't affect this machine anymore, but I sure would like to understand why this happens in the first place, because it shouldn't. Thanks again!
  14. Well, I was finally able to test again a bit yesterday. Running or not running the UPS daemon does not make a difference. Here are the logs for the VM after it happened and I force stopped it last time. The USB devices stay up, but it looks like it loses the video card for whatever reason. Dec 25 19:36:48 TheCube kernel: br0: port 2(vnet0) entered disabled state Dec 25 19:36:48 TheCube avahi-daemon[6418]: Interface vnet0.IPv6 no longer relevant for mDNS. Dec 25 19:36:48 TheCube avahi-daemon[6418]: Leaving mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:fe65:b60d. Dec 25 19:36:48 TheCube kernel: device vnet0 left promiscuous mode Dec 25 19:36:48 TheCube kernel: br0: port 2(vnet0) entered disabled state Dec 25 19:36:48 TheCube avahi-daemon[6418]: Withdrawing address record for fe80::fc54:ff:fe65:b60d on vnet0. Dec 25 19:36:49 TheCube kernel: AMD-Vi: Completion-Wait loop timed out Dec 25 19:36:49 TheCube kernel: AMD-Vi: Completion-Wait loop timed out Dec 25 19:36:49 TheCube kernel: AMD-Vi: Completion-Wait loop timed out Dec 25 19:36:50 TheCube kernel: iommu ivhd0: AMD-Vi: Event logged [ Dec 25 19:36:50 TheCube kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=0b:00.0 address=0x000000107ec5c7a0] Dec 25 19:36:50 TheCube kernel: iommu ivhd0: AMD-Vi: Event logged [ Dec 25 19:36:50 TheCube kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=0b:00.0 address=0x000000107ec5c7c0] Dec 25 19:36:50 TheCube kernel: iommu ivhd0: AMD-Vi: Event logged [ Dec 25 19:36:50 TheCube kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=0b:00.0 address=0x000000107ec5c7e0] Dec 25 19:36:50 TheCube kernel: vfio-pci 0000:0b:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none Dec 25 19:36:51 TheCube kernel: vfio-pci 0000:0b:00.0: Refused to change power state, currently in D3 Kind of looks to me like it has something to do with power management, but I really don't know. Simple for me to reproduce if anyone wants to see anything else at the time this occurs. It happens 100% of the time. Thanks for any ideas!
  15. To be clear, the Brother printer is not plugged into the UPS, just into the same breaker/circuit in the house. Tomorrow, I will test pulling the power on the unit and also letting the Brother printer cause the sag and see if there is any difference with and without the UPS daemon running. Thanks!