lookiana.blogg.se

1. #UBUNTU VIRTUALMACHINE HOME SCREEN FLASHES INSTALL#
2. #UBUNTU VIRTUALMACHINE HOME SCREEN FLASHES UPDATE#
3. #UBUNTU VIRTUALMACHINE HOME SCREEN FLASHES FULL#
4. #UBUNTU VIRTUALMACHINE HOME SCREEN FLASHES WINDOWS 10#
5. #UBUNTU VIRTUALMACHINE HOME SCREEN FLASHES PRO#

They all work in recovery mode and I was even able to start networking from there and ssh some files out. This is from the desktop vm and none work correctly. On the second machine I had Grafana stuff that wasn't backed up and although it's nothing special i didn't want to lose everything if I could so i dug deeper and found out that booting an older version there were no issues. However i noticed the freshly installed VM was doing the same thing and I then tried to investigate what was the root cause. I had backups of what was running in that vm so it wasn't a big deal.

Initially i thought something was wrong with the zvol/VM config and I tried a reinstall. In my investigation of the issue i did try to change the drive type from AHCI to VirtIO for a desktop but i was just pushing buttons to see if i get any response from the vm and obviously that's not how it works. I installed those VMs a long time ago and I think I went with what was default in the drive selector so that's why it's AHCI. When I woke up, I went to check a few things and noticed everything was just. Everything seemed fine, on a quick glance at least. I updated the Ubuntu VMs last night (every Monday/Tuesday, depending on when I get to it) before bed. All Ubuntu versions and their derivatives don't.

#UBUNTU VIRTUALMACHINE HOME SCREEN FLASHES WINDOWS 10#

#UBUNTU VIRTUALMACHINE HOME SCREEN FLASHES INSTALL#

EDIT: Live-boots of Ubuntu install media (18.04, 19.10, 20.04-beta) all work fine.

#UBUNTU VIRTUALMACHINE HOME SCREEN FLASHES FULL#

Just did a full pool scrub (took most of the day!) over the weekend, no errors on any of the drives.

Just a stock install of 11.3-U1, with an encrypted pool set up, a few datasets made, a few SMB shares made, and the above VMs spun up. Only 7 VMs ever used, 5 of which are Ubuntu (MATE and server mostly), one Windows 10, and one CentOS.The machine is a bog-standard Z800 with 2x X5650 and 24GB ECC.

#UBUNTU VIRTUALMACHINE HOME SCREEN FLASHES PRO#

Only a month old, one zpool of 5 drives in a RAIDz2, and 6TB of 25TB used.īoot drive is a 970 Pro 256GB. This is a relatively clean installation of FreeNAS.Some extra things worth noting, in case it help with the troubleshooting of the errors that I and OP are seeing:

#UBUNTU VIRTUALMACHINE HOME SCREEN FLASHES UPDATE#

The FreeNAS box rebooted a couple times during the update (judging from the POST beeps) which I didn't expect, but 5 minutes later the update was done. Then, I also noticed that I had no way of interacting with the VMs at all, and if I let them sit for ~30 seconds, they would all crash-out and show the same errors as my/OP's screenshots.Īlso this week, went from 11.3-U1 to 11.3-U2. My first round of troubleshooting, I noticed I had no cursor control on every noVNC session I started (where "every" just meant all my Ubuntu-based VMs, a pure coincidence until I created some CentOS and Windows VMs to check) no matter which browser or system I used, and even across reboots. I am currently running a scrub as well.Ĭlick to expand.I updated the Ubuntu VMs last night (every Monday/Tuesday, depending on when I get to it) before bed. I have checked for errors under the status tab and it shows zero errors. The pool in question here is the 22 x 4TB drives in a RAID10 setup. It appears to me that there is some kind of incompatibility with newer versions of Ubuntu and running it in a Freenas VM? I also went ahead and updated Freenas from 11.2 U8 to 11.3 U2 and upgraded both of my pools. (I assume.) They aren't throwing any errors and are fully operational. However, I have other un-updated VMs running 18.04.3 LTS that are running just fine because I haven't updated them. At this time I am unable to login to even a completely fresh install. I have since tried installing Ubuntu Server 18.04 LTS, 18.04.4 LTS, and 19.10 and they are all throwing the same/similar error messages before I can even login. Plex no longer loads and I can't access the system. After the updates completed and the VM rebooted, I started having issues with logging in via the vnc connection as messages continue to pop up that interrupt the login process. I updated my Plex VM (sudo apt update/upgrade) that runs Ubuntu Server 18.04.3 LTS.