I was able to install Unbuntu Core in Hyper-V, see https://askubuntu.com/questions/1209234/ubuntu-core-as-hyper-v-virtual-machine-image/1210966?noredirect=1#comment2132773_1210966
Currently, I have to work with VMWare, so I thought lets do the same thing again or just convert the disk to vmdk.
It looks like that it is not that easy at it may sounds.
I’m on VMWare Palyer 15.5.6 and Ubuntu 20 as live image.
I worked with
Converting didn’t work it always failed with
findfs: unable to resolve ‘LABEL=writable’, so I decided to do a reinstall, using standard settings. It failed again as, throwing the same error.
Occasionally, the boot dropped to a (initramfs) prompts/busybox
So, I started to some research.
- About findfs: unable to resolve 'LABEL=writable'
- Ubuntu Core cannot find 'writable' partition
- Why snap_core and snap_kernel in boot cmdline
- "unable to resolve 'LABEL=writable'"
- Installing Ubuntu Core on devices with internal drives
Eventually, it just clicked and I started searching for the drive. As only a few commands are available I used
cat /proc/scsi/scsi and
cat /proc/partitions (as all other commands in linux - How do I find out what hard disks are in the system? - Unix & Linux Stack Exchange won’t work) what told me there is nothing besides the CDROM but I wondered how it could even boot then???
I started experimenting adding a SATA and NVMe drive what was found by the system
I gave up with the standard SCSI drive, as there was only https://kb.vmware.com/s/article/1006621 leftover but all was set correctly.
I tried to install Ubuntu Core on NVMe as I expected a better performance compared to SATA,
I cannot remember if I got that after the very first flash and install attempt
but once again I felt somehow destroyed. So again I asked Google for help and found [Ubuntu 18.04] snapd.service fails on boot based “fully seeded” screenshot below.
Once again it just clicked. The comment it might be related to missing disk space made me think that it could be related to the dynamic disk space allocation of VMWare as the disk space is not pre-allocated.
So I resized the
writablepartition ni the drive manager of Ubuntu live to around 3.5 GB what resolved the problem
Installing on a NVMe resulted in the follwoing first
Ubuntu Core started to Bootstrap but got stuck in Stopped/Started Getty
somehow like in Ubuntu Core 18 on Raspberry Pi 3 doesn't bootstrap and https://superuser.com/questions/1553890/initializing-serial-getty-in-ubuntu-core-18
After the forced restart I saw
and was asked to configure but with an error echoed before
The configuration failed after entering my
It could be that due to a redownload of the install images that the setup worked once. Honestly, I cannot remember, what made it work.
After hours and hours, I was able to boot into Ubuntu Core. I got the impression that some errors were echoed during start-up and due to resize trick, I did not trust the install.
I tried to refresh the snap packages but it always failed with
In the end, I repeated the install using a SATA drive what gives me the impression that there is not any error echoed during start-up, although
snap refresh fails with
EOF but that could be due to my very slow internet connection currently.
I was only able to refresh
When I restarted after the flash I got always something like
DOES ANYONE HAS EXPERIENCE WITH THIS OR SUCH BEHAVIOUR?