I this post, I explained an issue I was having with the arm-image-installer Aarch64 Fedora 30 on Raspberry Pi 3B+ dracut-initqueue timeout
The resulting SD card wouldn’t boot and now I know why. The arm-image-installer created a duplicate “fedora” volume group on my laptop (F30) NOT on the SD card. So when the card was attempted to be booted from in the rpi3b+ it couldn’t find the appropriate partitions and volume groups. Because they were on my laptop. Thankfully I did not reboot and I was able to trudge thru lv/vg commands to get rid of this duplicate VG using the “–select vg_uuid=” for most of them and using the uuid of the bogus vg.
This is the command used…
sudo arm-image-installer --image=Fedora-Server-30-1.2.aarch64.raw.xz --target=rpi3 --media=/dev/sde --resizefs
What concerns me is the harm using arm-image-installer could have caused me and my main system. For now I am going to stick with manually creating SD cards using the xzcat method and I would strongly suggest folks are kept away from using the arm-image-installer until we can replicate the issue and get a fix in place.