Skip to content

Stop mounting partition 1 as /boot#120

Merged
crschardt merged 4 commits intoPhotonVision:mainfrom
crschardt:fix/stop-mounting-partition-1-as-boot
Jan 11, 2026
Merged

Stop mounting partition 1 as /boot#120
crschardt merged 4 commits intoPhotonVision:mainfrom
crschardt:fix/stop-mounting-partition-1-as-boot

Conversation

@crschardt
Copy link
Contributor

Raspberry Pi OS's prior to Bookworm would mount partition 1 as /boot. This is the default behavior for the arm-runner-action that we were using to create images and this behavior was copied in the photon-image-runner that we now use. However, mounting this partition as /boot shadows the real /boot and prevents modifying the contents of that directory. This turns up as a problem when we try to modify the dtoverlay.

On Raspberry Pi images from Bookworm, partition 1 is mounted as /boot/firmware. On the Orange Pi images we use, partition 1 is a data folder for cloud-init and should be mounted at /CIDATA.

This PR overrides the automatic mounting of partition 1 and instead leaves it to the appropriate install script to mount any partitions other than root as appropriate for that image.

@crschardt crschardt merged commit 7c622bb into PhotonVision:main Jan 11, 2026
17 checks passed
@crschardt crschardt deleted the fix/stop-mounting-partition-1-as-boot branch January 11, 2026 05:01
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

Successfully merging this pull request may close these issues.

2 participants