13313 2019-04-30 10:33:38 +0000 wic write --expand auto changes swap UUID 2020-05-13 17:38:28 +0000 1 1 7 Build System, Metadata & Runtime OE-Core Scripts and Tools 3.0 x86 Multiple RESOLVED FIXED Medium+ normal 3.2 M1 1 ross.burton chee.yang.lee chee.yang.lee randy.macleod ross.burton --- --- No (bug/feature does not impact docs) oldest_to_newest 83671 0 ross.burton 2019-04-30 10:33:38 +0000 The generated mount point for the swap in a wic image's fstab uses the swap UUID, whereas the partition regeneration code when the new expanded partition is created uses the partition UUID. If an image is written without using --expand the image boots. If --expand is used the UUID of the swap isn't preserved and the image won't boot. 83672 1 ross.burton 2019-04-30 10:42:18 +0000 Loopback mount the original wic: the fstab contains this: UUID=9951-E297 /boot vfat defaults 0 0 UUID=53fbb599-1298-4ffb-b5fa-c697f6d7d993 swap swap defaults 0 0 lsblk says: NAME FSTYPE LABEL UUID MOUNTPOINT loop1 ├─loop1p1 vfat efi 9951-E297 ├─loop1p2 ext4 platform 0c057449-028a-4227-8549-6c6fca952f26 /mnt └─loop1p3 swap swap1 53fbb599-1298-4ffb-b5fa-c697f6d7d993 Those are filesystem UUIDs not partition UUIDs: $ blkid /dev/loop1p3 /dev/loop1p3: LABEL="swap1" UUID="53fbb599-1298-4ffb-b5fa-c697f6d7d993" TYPE="swap" PARTLABEL="swap1" PARTUUID="ff602e88-56f8-4091-afdb-35af24f8644f" But when wic write builds the new partition table it is using the UUIDs from sfdisk, which are the partition UUIDs. $ wic write -e auto DEBUG: _exec_cmd: /data/poky-tmp/master/work/corei7-64-poky-linux/wic-tools/1.0-r0/recipe-sysroot-native/sbin/mkswap -L swap1 -U FF602E88-56F8-4091-AFDB-35AF24F8644F /tmp/wic-part3-626vx29l 87184 2 chee.yang.lee 2020-05-13 17:38:28 +0000 https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/scripts/lib/wic?id=df77ee47237244f400da4de62f201a55ec1a8f8d