I just installed MicroOS on my Raspberry Pi 4, and first off: awesome work with getting this working! I was amazed to see GRUB, some kind of EFI loader, and more all working on the Pi 4 -- it's amazing to see the Pi evolve into an actual full-fledged computer. However, I discovered a workflow that seems to be poorly supported as of now. My goal is to get MicroOS booting from a USB SSD (for better performance over the MicroSD card), and I ran into all sorts of troubles along the way. The major issues were: 1. Somehow it seems the dracut-pre-mount hook is deleting the 2nd partition during Ignition firstboot; if I dd the base image onto my SSD and use an ignition file, I can see /dev/sda2 is a proper btrfs filesystem; however, after letting MicroOS start to boot, inspecting the disk after shows the filesystem has been wiped from /dev/sda2 2. I'm not sure if this is just how baremetal images are supposed to work, but I can't seem to disable Ignition/Combustion after the first boot. I tried deleting the ignition cmdline argument from /etc/default/grub and running `transactional-update grub.cfg`, but then it complains about generators/dependencies failing for MicroOS... and then it boots successfully anyways 3. Once I got what I thought was a "proper" install on a MicroSD card, I tried partcloning the MicroOS btrfs partition to my SSD and booting that. Sure enough it worked, but it kept throwing errors about `mmc1: Timeout waiting for hardware cmd interrupt`. It would seem that somewhere something is hardcoded to expect a MicroSD card, and it is VERY mad that I'm trying to only use my SSD :( I got some "screenshots" of the tty with these issues, and I also have the rdsosreport.txt from trying to install directly on the SSD, but I can certainly try the process again and help get any more info to help debug and improve this experience! Screenshots: https://imgur.com/a/IpMF0lw rdsosreport: https://gist.github.com/steelcowboy/5148d854b3d83d84c734e5a0830e927d Please let me know if I can do anything to help resolve some of these issues and make the Raspberry Pi experience better! Thanks! Jim --------------------------------------------------- James Heald Production Engineer Facebook james.r.heald@gmail.com -- To unsubscribe, e-mail: opensuse-kubic+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kubic+owner@opensuse.org