SOLVED Error when creating Ubuntu VM

stephenreda

Dabbler
Joined
Oct 28, 2012
Messages
29
I an running:
Version:
FreeNAS-11.3-U3.1
Physical Memory:
16213 MiB
Model:
Intel(R) Core(TM) i5-4670 CPU @ 3.40GHz

I followed this procedure:
  1. Downloaded latest Ubuntu Server (also tried Desktop) ISO on the local filesystem
  2. Used default settings to add a Linux VM
Screen Shot 2020-06-04 at 12.26.32.png
Screen Shot 2020-06-04 at 12.26.43.png
Screen Shot 2020-06-04 at 12.27.00.png
Screen Shot 2020-06-04 at 12.27.25.png
Screen Shot 2020-06-04 at 12.27.43.png


Summary:
VM Summary
  • Guest Operating System : Linux
  • Number of CPUs : 1
  • Memory : 512 MiB
  • Disk Size : 100 GiB
  • Installation Media : /mnt/Main/Open/ubuntu-20.04-live-server-amd64.iso
Confirm these settings.

I always get the following failure when starting the VM and opening VNC:

Screen Shot 2020-06-04 at 12.31.09.png


I saw a similiar report on reddit from not so long ago:
https://www.reddit.com/r/freenas/comments/gljoes/initramfs_unpacking_failed_write_error/
In the threat they suggested that 512 Mib is not enough so I changed it to 1024M.
I now see the first install window from Ubuntu
Screen Shot 2020-06-04 at 12.41.22.png

but when selecting the default, I get to see the same error message.
 
Last edited:

Samuel Tai

Never underestimate your own stupidity
Moderator
Joined
Apr 24, 2020
Messages
5,398
Change your disk type to VirtIO. Also, you don't have enough RAM allocated to hold the initramfs. You need at least 2048 MiB.
 

stephenreda

Dabbler
Joined
Oct 28, 2012
Messages
29
Thanks Samuel. For others searching on this: updating the Memory size via edit on an existing VM didn't change it. I had to recreate the VM with enough Memory.
 

Attachments

  • Screen Shot 2020-06-04 at 13.17.28.png
    Screen Shot 2020-06-04 at 13.17.28.png
    40.3 KB · Views: 261

Samuel Tai

Never underestimate your own stupidity
Moderator
Joined
Apr 24, 2020
Messages
5,398
Thanks Samuel. For others searching on this: updating the Memory size via edit on an existing VM didn't change it. I had to recreate the VM with enough Memory.

You can't edit the memory on a running VM. You can if the VM is not running.
 
Top