Solas

Members
  • Posts

    4
  • Joined

  • Last visited

Recent Profile Visitors

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

Solas's Achievements

Noob

Noob (1/14)

1

Reputation

  1. Hi Guys, My Windows 10 VM - originally set up as per Spaceinvaderone's instructions - started to shut down automatically after working without any issues for 7-8 months straight (VM's log and settings provided below). I've been using it as a gaming VM for Elder Scroll Online (ESO). I expanded the VM's disk space by 65Gb and added EVE Online 4-5 days ago. Both games worked fine in isolation from each other. Two days ago I decided to launch EVE Online while the ESO launcher was still running in a background downloading a substantial update (without running the actual ESO game). EVE Online did start but the VM itself stopped several minutes later. Since then any attempt to start the VM results in an automatic shutdown. The VM's share/image does use cache, but cache (1Gb SSD) was only 60% full at the time the issue occurred (now only 20% of the cache is used). I'd greatly appreciate if someone can shed any light on this mystery. Thank you for considering my post. -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=31,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-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 \ -blockdev '{"driver":"file","filename":"/mnt/user/domains/Narbondel/vdisk1.img","node-name":"libvirt-3-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-3-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-3-storage"}' \ -device virtio-blk-pci,bus=pci.0,addr=0x4,drive=libvirt-3-format,id=virtio-disk2,bootindex=1,write-cache=on \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/Windows64ISO.iso","node-name":"libvirt-2-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-2-format","read-only":true,"driver":"raw","file":"libvirt-2-storage"}' \ -device ide-cd,bus=ide.0,unit=0,drive=libvirt-2-format,id=ide0-0-0,bootindex=2 \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/virtio-win-0.1.190-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 ide-cd,bus=ide.0,unit=1,drive=libvirt-1-format,id=ide0-0-1 \ -netdev tap,fd=33,id=hostnet0 \ -device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:a4:29:42,bus=pci.0,addr=0x2 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0 \ -chardev socket,id=charchannel0,fd=34,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:0a:00.0,id=hostdev0,bus=pci.0,addr=0x5,romfile=/mnt/user/windowsdisk/-PNY_QuadroP2000_Latest.rom \ -device vfio-pci,host=0000:0a:00.1,id=hostdev1,bus=pci.0,addr=0x6 \ -device usb-host,hostbus=3,hostaddr=2,id=hostdev2,bus=usb.0,port=2 \ -device usb-host,hostbus=5,hostaddr=3,id=hostdev3,bus=usb.0,port=3 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2023-03-16 09:49:01.485+0000: Domain id=3 is tainted: high-privileges 2023-03-16 09:49:01.485+0000: Domain id=3 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2023-03-16T09:50:10.860635Z qemu-system-x86_64: terminating on signal 15 from pid 4596 (/usr/sbin/libvirtd) 2023-03-16 09:50:13.495+0000: shutting down, reason=shutdown
  2. Hi JorgeB Thank you for pointing out that the issue was indeed with the onboard SATA, not the JMB controller. I've reset the MOBO's BIOS to its default settings and the onboard SATA drives re-appeared. Then I assigned the data disks back to their places within the Unraid array and started the server. Once the data disks were mounted successfully, I put the parity disk back in and completed a parity check. The server is up and running again with no issues. I guess I had a case of a tunnel vision not being able to see what was right in front of me. Thank you once again, issue resolved.
  3. My apologies, the diagnostics file has been attached. I would greatly appreciate if someone can have a look and explain what went wrong with those two SATA drives. As far as this server build goes, to be honest, I should probably stop playing with things I don't understand. 🤦‍♂️🤕 menzoberranzan-diagnostics-20220605-0635.zip
  4. Hi Guys, I'm a noob when it comes to anything Unraid. I copied this server build a month ago. It utilises IOCrest M.2(PCie3.0) adapter. Everything was okay until I started playing with Windows 10 VM trying to pass through an iNvidia Quadro P2000 GPU. Nothing worked, after seeing some commentaries I tried to change from legacy to uefi boot. The server stopped seeing 2 SATA drives connected via this adapter. Below is the boot log. Any ideas how to bring these SATA drives back online? Jun 4 22:55:41 Menzoberranzan kernel: sdd: sdd1 Jun 4 22:55:41 Menzoberranzan kernel: ata5.00: Enabling discard_zeroes_data Jun 4 22:55:41 Menzoberranzan kernel: sd 5:0:0:0: [sdd] Attached SCSI disk Jun 4 22:55:41 Menzoberranzan kernel: ACPI: Invalid passive threshold Jun 4 22:55:41 Menzoberranzan kernel: thermal LNXTHERM:00: registered as thermal_zone0 Jun 4 22:55:41 Menzoberranzan kernel: ACPI: Thermal Zone [TZ10] (17 C) Jun 4 22:55:41 Menzoberranzan kernel: ACPI: Invalid passive threshold Jun 4 22:55:41 Menzoberranzan kernel: thermal LNXTHERM:01: registered as thermal_zone1 Jun 4 22:55:41 Menzoberranzan kernel: ACPI: Thermal Zone [PCT0] (17 C) Jun 4 22:55:41 Menzoberranzan kernel: ata7: softreset failed (1st FIS failed) Jun 4 22:55:41 Menzoberranzan kernel: ata8: softreset failed (1st FIS failed) Jun 4 22:55:41 Menzoberranzan kernel: ata7: softreset failed (1st FIS failed) Jun 4 22:55:41 Menzoberranzan kernel: ata8: softreset failed (1st FIS failed) Jun 4 22:55:41 Menzoberranzan kernel: ata7: softreset failed (1st FIS failed) Jun 4 22:55:41 Menzoberranzan kernel: ata7: limiting SATA link speed to 3.0 Gbps Jun 4 22:55:41 Menzoberranzan kernel: ata8: softreset failed (1st FIS failed) Jun 4 22:55:41 Menzoberranzan kernel: ata8: limiting SATA link speed to 3.0 Gbps Jun 4 22:55:41 Menzoberranzan kernel: ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Jun 4 22:55:41 Menzoberranzan kernel: ata8.00: link online but device misclassified Jun 4 22:55:41 Menzoberranzan kernel: ata8: link online but 1 devices misclassified, device detection might fail Jun 4 22:55:41 Menzoberranzan kernel: ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Jun 4 22:55:41 Menzoberranzan kernel: ata7.00: link online but device misclassified Jun 4 22:55:41 Menzoberranzan kernel: ata7: link online but 1 devices misclassified, device detection might fail