[U-Boot] Partition UUIDs in U-Boot and Linux (blkid vs 'part list')
Hi,
I find that blkid provides different output from 'part list' and I'm not sure why:
=> part list scsi 0
Partition Map for SCSI device 0 -- Partition Type: EFI
Part Start LBA End LBA Name Attributes Type GUID Partition GUID 1 0x00000800 0x001007ff "" attrs: 0x0000000000000000 type: c12a7328-f81f-11d2-ba4b-00a0c93ec93b guid: 9d02e8e4-4d59-408f-a9b0-fd497bc9291c 2 0x00100800 0x037d8fff "" attrs: 0x0000000000000000 type: 0fc63daf-8483-4772-8e79-3d69d8477de4 guid: 965c59ee-1822-4326-90d2-b02446050059 3 0x037d9000 0x03ba27ff "" attrs: 0x0000000000000000 type: 0657fd6d-a4ab-43c4-84e5-0933c84b4f4f guid: 2c4282bd-1e82-4bcf-a5ff-51dedbf39f17
$ sudo blkid /dev/sda1: UUID="819A-4923" TYPE="vfat" /dev/sda2: UUID="b2aaf743-0418-4d90-94cc-3e6108d7d968" TYPE="ext4" /dev/sda3: UUID="742df38d-6a50-4b47-a39a-c0076b0cc057" TYPE="swap"
Does anyone know? I'd like U-Boot to be able to show the same information as well as the TYPE.
Regards, Simon
On Sat, May 07, 2016 at 11:51:12AM -0600, Simon Glass wrote:
Hi,
I find that blkid provides different output from 'part list' and I'm not sure why:
=> part list scsi 0
Partition Map for SCSI device 0 -- Partition Type: EFI
Part Start LBA End LBA Name Attributes Type GUID Partition GUID 1 0x00000800 0x001007ff "" attrs: 0x0000000000000000 type: c12a7328-f81f-11d2-ba4b-00a0c93ec93b guid: 9d02e8e4-4d59-408f-a9b0-fd497bc9291c 2 0x00100800 0x037d8fff "" attrs: 0x0000000000000000 type: 0fc63daf-8483-4772-8e79-3d69d8477de4 guid: 965c59ee-1822-4326-90d2-b02446050059 3 0x037d9000 0x03ba27ff "" attrs: 0x0000000000000000 type: 0657fd6d-a4ab-43c4-84e5-0933c84b4f4f guid: 2c4282bd-1e82-4bcf-a5ff-51dedbf39f17
$ sudo blkid /dev/sda1: UUID="819A-4923" TYPE="vfat" /dev/sda2: UUID="b2aaf743-0418-4d90-94cc-3e6108d7d968" TYPE="ext4" /dev/sda3: UUID="742df38d-6a50-4b47-a39a-c0076b0cc057" TYPE="swap"
Does anyone know? I'd like U-Boot to be able to show the same information as well as the TYPE.
Hmm. A quick test here shows that it _is_ matching for MBR style partition tables (which is what is common for TI/armv7 and why ti_armv7_common.h grabs the likely rootfs PARTUUID and boots with root=PARTUUID= like I imagine you're trying).
On 05/07/2016 11:51 AM, Simon Glass wrote:
Hi,
I find that blkid provides different output from 'part list' and I'm not sure why:
"part list" prints partition UUIDs (from the partition table), whereas I /think/ blkid prints filesystem UUIDs (from the fs superblock).
The kernel will accept either on its cmdline root= parameter, but you have to tell it which you're using, e.g. root=PARTUUID=partition_uuid, or IIRC root=UUID=fs_uuid.
participants (3)
-
Simon Glass -
Stephen Warren -
Tom Rini