I'll have a look a this issue - maybe it's the same case:
Why won't my raspberryPi boot if I use parted to adjust the partition?
https://raspberrypi.stackexchange.com/q ... -partition
I've been struggling to figure out a boot problem with the RaspberryPi 3 (I've not tested other models) using a modified Raspbian Jessie Lite image, and finally narrowed down to something to do with the MBR -- but now I'm baffled and curious as to what exactly the problem is.
In short: if I adjust partitions with parted, the Pi doesn't boot. If I do the exact same adjustment with fdisk, it works fine.
But:The bootstrap code in the parted-created image, however, is entirely different:
The suspect:According to NOOBs documentation (and elsewhere): "a Raspberry Pi doesn't use any of the bootstrap code stored in the MBR.". So why is the different bootstrap code causing a failure to boot?
To summarize the comment section: we don't know why parted changes the disk identity, but can only guess (or rather speculate). Anyway, this change made by parted has the undesired side effect that it renders Raspbian images after beginning of April 2017 unable to boot. The reason is that the partition UUID (PARTUUID) changes, and the kernel boot parameters as well as the /etc/fstab still reference the old PARTUUID. So either don't use parted, or update thr command line parameters and /etc/fstab with the new PARTUUIDs you can retrieve via blkid.
Statistics: Posted by mrpib3 — Sun Apr 14, 2024 9:14 am