2019-09-26 Raspbian Image PTUUID

[RonR]

Prior to the latest Raspbian image (2019-09-26), an SD card or USB drive received a unique PTUUID/PARTUUID/UUID on startup. With the 2019-09-26 image, the PTUUID/PARTUUID/UUID is not changed on startup from that of image file (PTUUID=6C586E13). IOW, all devices created with the 2019-09-26 Raspbian image will have the same PTUUID/PARTUUID/UUID. This is not good.

[Milliways]

Prior to the latest Raspbian image (2019-09-26), an SD card or USB drive received a unique PTUUID/PARTUUID/UUID on startup.

No it didn't!

[RonR]

Prior to the latest Raspbian image (2019-09-26), an SD card or USB drive received a unique PTUUID/PARTUUID/UUID on startup.

No it didn't!

Yes it did. After the SD card was auto-expanded by /usr/lib/raspi-config/init_resize.sh, it had a new PTUUID. /boot/cmdline.txt and /etc/fstab had to be adjusted to account for it:

Code: Select all

get_variables () {
...
  OLD_DISKID=$(fdisk -l "$ROOT_DEV" | sed -n 's/Disk identifier: 0x\([^ ]*\)/\1/p')
...
}

fix_partuuid() {
  DISKID="$(fdisk -l "$ROOT_DEV" | sed -n 's/Disk identifier: 0x\([^ ]*\)/\1/p')"

  sed -i "s/${OLD_DISKID}/${DISKID}/g" /etc/fstab
  sed -i "s/${OLD_DISKID}/${DISKID}/" /boot/cmdline.txt
}

For some reason, this change isn't occurring in 2019-09-26 whereas it did in previous versions. I double checked this behavior before posting.

[ShiftPlusOne]

I haven't confirmed the issue yet, but I can believe it.

The UUID change was not intentional, but it probably should be. It will be fixed in the next image.