October 14, 20187 yr Hello, Machine Info First: Ryzen 7 1700 SSD 500GB Cache 4 HDD 1 Parity Drive So everything has been working great the past couple weeks, and most recently I setup an OSX VM following SpaceInvader one tutorial. This was also working fine. I then just attempted to passthrough a USB (on a different card / bus then the boot file). I thought I had it figured out, but when I added the hostdev info into the XML on the VM, and tried to run it, the whole thing crashed. Now I cannot ssh into the tower (I get message "port 22 host is down"), I can't load the webGUI (I also tried booting in safe mode with no plugins but no luck). I can still see it when I connect tower to a monitor, and it does get right to the "typical" end (everything loaded and asking for tower user log in details). So I did save a diagnostics file as well for more info. Question is - can I either just undo this mistake somehow in the unraid command line directly on the tower, or is there a way for me to simply remove the VM to delete what I think caused this whole issue? I attached the diagnostics file if that helps. syslog.txt
October 14, 20187 yr You can remove the autostart of the VM and then reboot. Delete the symlink in /etc/libvirt/qemu/autostart and then powerdown -r Or alternative, you can disable the entire VM service by editing /config/domain.cfg on the flashdrive and rebooting. Then edit the VM accordingly As an aside, a syslog is not the full diagnostics Edited October 14, 20187 yr by Squid
October 14, 20187 yr Author I tried editing the VM service in the domain file - but changing it to "disable" on the service line and then save & boot did nothing - still can't load GUI or ssh in to server. Am I perhaps incorrect in thinking it is an issue with the VM and USB passthrough?
October 14, 20187 yr 24 minutes ago, dwilliams said: Am I perhaps incorrect in thinking it is an issue with the VM and USB passthrough? Can't be related to passthrough if the VM service is disabled, and a reboot happened. Post your diagnostics diagnostics
October 14, 20187 yr Pretty sure somethings wrong on the network. First thing I'd check is that the cable is plugged in, as your only port seems to think that it's not. Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Speed: 10Mb/s Duplex: Half Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000033 (51) drv probe ifdown ifup Link detected: no driver: r8169 version: 2.3LK-NAPI firmware-version: rtl8168h-2_0.0.2 02/26/15 expansion-rom-version: bus-info: 0000:1b:00.0 supports-statistics: yes supports-test: no supports-eeprom-access: no supports-register-dump: yes supports-priv-flags: no --------------------------------
October 14, 20187 yr Author Tried that squid - I checked the ethernet plug in, and its good. My Macbook can see the tower as a device on the network (listed at the address I try to ssh to), but I can't load the tower.local page to manage from dashboard. I did manage to get it to boot in GUI mode and access directly from the tower with monitor attached, but I didn't see any VMs or plugins when I booted in GUI mode.
October 14, 20187 yr Author Ok. Managed to use the web access - looks like all my info was reset. The name of the tower I used wasn't working anymore but the ipaddress did when I logged in. Tried to use the restore plug in but that didn't seem to work. Going to try in safe mode and see if I can restore and keep some settings.
Archived
This topic is now archived and is closed to further replies.