thomas

Members
  • Posts

    76
  • Joined

  • Last visited

Everything posted by thomas

  1. How is your network wired? Are you using a switch in-between LAN port and unraid?
  2. I'm using 2GB, but my VM is just for testing. Are you using bridge for the LAN segment? I have seen sometimes using bridge it's causing issues and the whole network goes down. Try using 2 hardware ports, one for LAN and one for WAN...
  3. You ran out of space. If you press ALT+F4, you'll see the log. I tried with 10GB and it's too small. Increasing the disk space to 20GB fixed it. I used UTM 9.6 with 64bit and Enterprise.
  4. You can try and and check for any clue why it doesn't work.
  5. I replied on the other topic. See the link https://forums.unraid.net/topic/75275-solved-wanted-to-install-sophos-home-firewall-in-unraid/?do=findComment&comment=726911
  6. Find below an xml file. There is nothing fancy about it; choose Linux as VM, Machine Q35, BIOS SeaBIOS, OS Install CDROM set to SATA, Primary Disk set to SATA 10GB, VNC and 2 virtual NICs changed from virtio to e1000-82545em. You must remove the virtual NICs and use the pass-through ones if that's the case.
  7. After waking the system from sleep the spin up drive indicator is not refreshed. It stays grey (spin down) when is should be green (spin up). If I press the arrow to spin it up the colour changes. See below a part of the log file. Feb 27 20:08:19 unRAID s3_sleep: Disk activity on going: sdc Feb 27 20:08:19 unRAID s3_sleep: Disk activity detected. Reset timers. Feb 27 20:08:46 unRAID kernel: mdcmd (40): spinup 1 # I pressed the spin up button for sdc to see if it gets refreshed, and it did Feb 27 20:09:19 unRAID s3_sleep: Disk activity on going: sdc Feb 27 20:09:19 unRAID s3_sleep: Disk activity detected. Reset timers. Feb 27 20:10:19 unRAID s3_sleep: Disk activity on going: sdc Feb 27 20:10:19 unRAID s3_sleep: Disk activity detected. Reset timers.
  8. Try to change the machine type to Q35 and try again. For my AMD that was the only way to fix it.
  9. Make the selection like in the picture and change the IP address to match yours and it should work.
  10. It's working for me. Just use \\192.168.1.2\media or equivalent for your machine and add user/password, if required ... Also smb:\\192.168.1.2\media it's working. I guess you have SMB activated...
  11. I left them default, the only change I made is the type to "e1000-82545em" and everything works properly. Add Solved to the topic name, if there are no more issues...
  12. The drive needs to be SATA to work. And the same for the iso image.
  13. It seems that there are no more issues after switching to USB 2.0... I'll mark it solved for now.
  14. There are some changes that can be done using virt-manager, some are on the fly and some are saved and applied at next reboot. See docker support
  15. I don't recall if I had to switch the disks from Virtio to SATA, but you can try it. I can check later today to see...
  16. I made a test install for Sophos XG Firewall, but for me it only booted with Seabios, not OVMF. After install, I changed my computer's IP to 172.16.16.5 255.255.255.0 and I could access the https://172.16.16.16:4444 and do all the configuration...
  17. I had it on USB 3 for the last 2 years and it was working fine. Now I plugged it into USB2.0. I'll check to see if it's still happening. I upgraded to 6.6.5 a couple of days before and it seems that was the trigger point, or maybe it was just a coincidence...
  18. For the last few days I'm getting "System notifications are disabled. Click here to change notification settings." message. It seems that the USB get's disconnected and I have to reboot the whole machine to recover. I changed the usb port, I formated the drive, but the error keeps reappearing at random times. Thanks. Attached is my diagnostics. unraid-diagnostics-20181113-1815.zip
  19. They are both on LAN, but the WAN side will get an IP from the DHCP server that you have, while the other one will be 172.16.16.16. So you have to change your IP to be in the same subnet to be able to connect. Also you can connect with VNC and change the LAN side IP from the VM terminal. Default password is admin...
  20. Try also deleting the browser cache or using an incognito tab... Check also you're using the Lan side, because the Wan side doesn't allow access to :4444 port...
  21. Maybe a silly question, but you have changed your IP to be able to access the 172.16.16.16? You can try ping it first, to know that is accessible...
  22. Are you using https://IP.add.re.ss:4444 to connect and do the initial configuration? The page at https://IP.add.re.ss is just for user login and it will fail initially, because there are no users defined. Default is https://172.16.16.16:4444/
  23. When will be the new RC ready to test it? Also I have seen that even if I can ping 8.8.8.8, there is no "next" release available... Thanks