Bug 8183 - UUID does not work for directdisk-gpt wic generated image.
Summary: UUID does not work for directdisk-gpt wic generated image.
Status: VERIFIED INVALID
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: deployment (show other bugs)
Version: 1.9
Hardware: All x86_64
: Medium major
Target Milestone: 1.9 M3
Assignee: Ed Bartosh
QA Contact: Daniel Istrate
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2015-08-19 13:52 UTC by Daniel Istrate
Modified: 2015-09-08 09:17 UTC (History)
1 user (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments
UUID does not work for directdisk-gpt (1.76 MB, image/jpeg)
2015-08-19 13:52 UTC, Daniel Istrate
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Istrate 2015-08-19 13:52:37 UTC
Created attachment 2668 [details]
UUID does not work for directdisk-gpt

Hi,

The partition UUID mechanism fails to determine the root partition on a directdisk-gpt image.


To reproduce:
1. Build wic dependencies
MACHINE=nuc bitbake syslinux syslinux-native parted-native gptfdisk-native dosfstools-native mtools-native core-image-minimal

2. Build a directdisk-gpt image with wic:
MACHINE=nuc wic create directdisk-gpt -e core-image-minimal -o wic-images-bak/nuc/directdisk-gpt/core-image-minimal/

3. Write the image to a usb stick:
sudo dd if=wic-images-bak/nuc/directdisk-gpt/core-image-minimal/build/directdisk-gpt-201508191536-sdb.direct of=/dev/sdc

4.Insert the usb stick into a NUC and boot from it.
You should see that image fails to boot. Please check the attached picture for more details.

If it booted correctly try modify the 'directdisk-gpt.wks' (sda -> sdb) and redo step 3 & 4. The partition UUID mechanism should be able to detect the root partition, which it doesn't in this case.

Thanks,
--Daniel
Comment 1 Ed Bartosh 2015-08-25 08:23:25 UTC
Started to work on this.
Comment 2 Ed Bartosh 2015-08-26 16:41:38 UTC
Neither me or bug author can reproduce this issue on latest master. Closing.
Comment 3 Daniel Istrate 2015-09-08 09:17:00 UTC
Failed to reproduce on master c1df471feacaf2590216aa476ce242908dac38cf, my guess is that it's fixed by kernel update.