Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FAT partition label: don't name it "boot" #669

Closed
macmpi opened this issue Feb 13, 2023 · 5 comments
Closed

FAT partition label: don't name it "boot" #669

macmpi opened this issue Feb 13, 2023 · 5 comments

Comments

@macmpi
Copy link

macmpi commented Feb 13, 2023

There is a quite maddening side effect of default boot partition label together with a longstanding firmware bug uncovered by @pelwell :
raspberrypi/firmware#1529 (comment)

That partition naming prevents use of boot directory name inside it, for anything essential to boot the system from FAT partition... Not a major problem for PiOS but has adverse consequence for other distribution that may be installed after.

Agreed, root of problem is in firmware side, but as this does not seem to get resolved, here is a typical consequential use-case if default Pi OS image use that boot label.

  • User makes an initial Pi OS image media (with rpi-imager or manually), and runs fine on his device: all good.
  • Then user may want to try another distribution for Pi device (Alpine to name one), which has a boot directory inside FAT partition.
  • User replaces FAT partition content with new distribution's files
  • Device won't boot.
  • Try default reformat, re-install...won't boot either

All this because first-off media generation had that colliding boot label... definitely not an obvious guess!

Would it be possible to consider another non-colliding label name for that default FAT partition (FATboot or something), until that firmware bug is eventually fixed?

@XECDesign
Copy link
Member

@pelwell, @timg236, is this a bootrom issue on older pis, or can it be fixed in bootcode.bin or start.elf files?

@pelwell
Copy link
Member

pelwell commented Feb 13, 2023

It's somewhere deep in the filesystem abstractions of start*.elf.

@macmpi
Copy link
Author

macmpi commented Feb 14, 2023

thanks 👍

@XECDesign
Copy link
Member

Thanks for reporting the issue

@macmpi
Copy link
Author

macmpi commented Feb 14, 2023

Hopefully firmware will get a permanent fix at some point, but at least one main source of catch-22 should be gone with next release. 😉

martignoni added a commit to moodlebox/pi-gen-moodlebox that referenced this issue Mar 31, 2023
* Fix apt gpg key install
* export-image: change boot partition lable to 'bootfs'

Fixes RPi-Distro#669

* Update release notes
* Check that docker is not set up in rootless mode (RPi-Distro#679)

Mounting binfmt_misc inside the container requires root rights. If
"docker info" indicates rootless mode then fall back to "sudo docker".

Allow the user to override the docker command with the DOCKER by setting
the environment variable.

* Ensure that deploy is always owned by user (RPi-Distro#680)

Switch "docker cp" to tar streaming mode. As the receiving "tar" command
is executed outside Docker the resulting directories & files are owned
by the calling user.

* DRY removal for docker run command line (RPi-Distro#686)

Factor out the differences into variables so that there is only one
implementation of the "docker run" command line to maintain.

* Use tmpfs for chroot /run and /tmp

---------

Co-authored-by: Serge Schneider <[email protected]>
Co-authored-by: Stefan Becker <[email protected]>
wandering-andy pushed a commit to wandering-andy/pi-gen that referenced this issue Oct 15, 2023
kayhannay pushed a commit to kayhannay/efalive_pi that referenced this issue Feb 12, 2024
UmeshMohan-Dozee pushed a commit to DozeeRnD/pi-gen that referenced this issue Sep 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants