Hitting a wall when trying to boot from a partition with GPT
scanning bus for devices...
Device 0: (0:0) Vendor: ATA Prod.: Samsung SSD 860 Rev: RVT4
Type: Hard Disk
Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512)
Found 1 device(s).
btrfs probe failed
** Unrecognized filesystem type **
btrfs probe failed
** Unrecognized filesystem type **
It would appear that source development has incorporated GPT support since around 2012 but I cannot figure out whether uboot in downstream has GPT support and if not that being the reason the boot fails?
nvm, just saw that it is filesystem in question (or whatever related to ssd), why hiding output, if i didn't click accidentaly on first line i'd never thought there was some info posted..
From that build conf it is not cleat to me whether GPT support is explicitly excluded (=N) somewhere or just not enabled and the default build conf does not include it.
But sadly it would appear that GPT support is lacking.
Would appreciate if a developer could be obliged to enable/implement u-boot support for GPT in Master & 19.07, with MBR being sort of legacy and its issues/limitations.
If it is a space concern at least for the targets that can cope with it, e.g. mvebu & x86.
Can you use the build system and a little bit git?
I´ll prepare a patch and you build with the build system and test if its sufficient for your use case...
If you approve that this config symbols are sufficient, i will create a PR.
The symbol CONFIG_PARTITION_UUIDS is inferred from CONFIG_CMD_GPT.
This are the simple steps:
make package/uboot-mvebu/{clean,prepare} V=s QUILT=1
cd build_dir/target-arm_cortex-a9+vfpv3_musl_eabi/u-boot-clearfog/u-boot-2019.04/
quilt push -a
quilt new 220-mvebu_clearfog-add-gpt-support.patch
make clearfog_defconfig
make menuconfig
Select CONFIG_CMD_GPT and save
make savedefconfig
mv defconfig configs/clearfog_defconfig
quilt refresh
cd -
make package/uboot-mvebu/update V=s
git commit -asm "uboot-mvebu: add GPT support for clearfog"
There's an email address, so I'm lost why you refused to email the developer directly - as opposed to making posts here. Nonetheless, I'm glad @juppin was able to assist quickly. (I haven't got thru account setup yet...)