procount

Could be. I recall there was special noobs detection code at some point. I used to remove/adapt the firstrun script to prevent the unnecessary root partition expansion, but leaving it...

Yes, that's certainly relevant, thanks. Does "re-running the partition_setup.sh script" from the fix up menu sort this out, without you having to mess with installed_os.json?

@Lurch - The firstboot script still checks for the presence of NOOBS, but doesn't take this into account before calling fix_partuuid. Looks like this has been an issue since 20220901...

We just need to stop Raspios (and others based on it) from modifying the diskid when in a multi-boot environment. I'm working on it.....

> Out of curiosity, if those changes were made, if a PINN user installed multiple copies of the same OS image on the same drive, would there be a PARTUUID...

@mkreisl - Which OS are you installing (exact name, version, release date would help)

I don't think switching to UUID will totally help. The problem was that everyone who downloads the standard image would have the same PARTUUIDs or UUIDs. So to make these...

Just to be clear: 1. There is no reason for the PARTUUIDs to change, and they shouldn't. 2. PINN is not changing the PARTUUIDs 3. Most likely, this is due...

I will try to follow your installation steps to see if I can replicate your issue. It may take a little while....

Re-reading your procedure, maybe it was the ubuntu update that killed it? Was it version 23.10?