Problems with ubuntu 20.04 VM after booting

[tibblist]

So I have managed to get my vm to boot properly instead of reinstalling each time except now after I login or before I login the disk seems to start to error out. Initially with this https://i.imgur.com/T4oBO5r.png then moving onto a ton of errors https://i.imgur.com/4xAfp4d.png. This basically makes the VM unusable, I have a 30 GB zvol for it inside of a crucial mx500 240gb disk, is it possible that its just a hardware issue? The disk is brand new.

Edit: After it finishes with a bunch of errors attempting to do anything that modifies the disk appears to fail https://i.imgur.com/e15qS75.png.

 

[tibblist]

I changed the disk i/o type to virtIO, this broke booting and now it wants to install again but I can just go to boot from file manually and get in. This appeared to let me do IO but actually turns out the nic broke now and it cannot access the internet to even run sudo apt-get update, and given about a minute goes back to the same revalidation failed (errno=-5) errors as before...

 

[sretalla]

Have you done something like this?

[HOWTO] How-to Boot Linux VMs using UEFI

There have been a number of threads were people have failed to boot a Linux VM after the installation phase using the webUI of FreeNAS 11 nightly, finding themselves stuck in the EFI shell and not knowing how to proceed nor how to avoid this happening each time their VM is started. It has been...

www.ixsystems.com

 

[bignellrp]

I changed the disk i/o type to virtIO, this broke booting and now it wants to install again but I can just go to boot from file manually and get in. This appeared to let me do IO but actually turns out the nic broke now and it cannot access the internet to even run sudo apt-get update, and given about a minute goes back to the same revalidation failed (errno=-5) errors as before...

hi, I’m also getting similar IO errors on my VMs since upgrading from Freenas U1 to U2.

I read through the post above but it doesn’t seem to be related as my grub is booting but hangs with errors similar to yours.

what version of Freenas are you running?

 

[tibblist]

Freenas 11.3-U2, let me know if you figure out a solution

 

[bignellrp]

I fixed my issue with Ubuntu 19.04 by switching the disk type to virtIO. Still can’t solve the Ubuntu 20.04 as that as an IRQ error but there is a suggested fix in another post

 

[KrisBee]

@bignellrp For Ubuntu 20.04 server try the legacy installer iso, ubuntu-20.04-legacy-server-amd64.iso

 

[ecarter]

> I’m also getting similar IO errors on my VMs since upgrading from Freenas U1 to U2

Same thing here. Really frustrating. One peculiar thing I notice is that I only get these errors when my VM has more than 2 virtual CPUs.

 

[liquidpower]

yes this more the 2 virtual cpu's. iv been messing around all day only way i could get my 20.04 install stable was to drop it down to 1 core. super funky

 

[Samuel Tai]

When you switch to VirtIO, remember to update your /etc/fstab to use /dev/vdxx from /dev/sdxx devices. Likewise, you may need to update your grub.cfg, if your boot string includes any references to /dev/sdxx.

 

[Samuel Tai]

Also, it may be worth hard-coding the sector size in the disk devices attached to the VM to 512.

 

[Patrick M. Hausen]

When you switch to VirtIO, remember to update your /etc/fstab to use /dev/vdxx from /dev/sdxx devices. Likewise, you may need to update your grub.cfg, if your boot string includes any references to /dev/sdxx.

Ubuntu by default uses UUIDs for /etc/fstab entries instead of device names. These should not change when the disk type does. At least since 16.04 which is the oldest I still run anywhere.

 

[ecarter]

It appears this issue should be fixed in the next update: https://jira.ixsystems.com/plugins/servlet/mobile#issue/NAS-105649