> On my amd64 PC, I typically use ext4 for all partitions. > However, I'm not very knowledgeable about ARM architecture.
At least in this respect there's no difference: the same partitioning scheme (MBR / GPT) is used on both PCs and Pis, and the same file- systems (FAT, ext4, etc.) within them. > So I trust the partitioning scheme used by the Raspberry Pi Imager. > (I don't remember the specific version of Imager tool I used) It's not the rpi-imager that does the partitioning on the destination media, but the image it's flashing. The imager (more or less) blindly writes all the bytes of the source image to the target media; if there happen to be partitions it doesn't really notice (unless it's doing post-write customization of the boot partition, but that doesn't modify the partitions, just the content of some text files). In the case of the Ubuntu images, we've always defined two partitions on our images: * A small FAT32 partition which mounts at /boot/firmware and... * A large ext4 partition which mounts at / The fact you've got a FAT32 partition mounted at /boot suggests this may be one of the unofficial flavours. I think Ubuntu MATE used that layout? I may be wrong about that though. Do you happen to remember (roughly) which image you flashed to the card? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2085700 Title: linux-image-5.15.0-1064-raspi package post-installation returned error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2085700/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
