Hi,
Ok, that basically means that kiwi doesn't fix up the GPT properly if it's installing onto a disk that already has a GPT.
Marcus, if I dd a "short" OEM image with GPT onto a disk that already has a GPT, we now have 3 GPT tables:
* beginning of the disk * middle of the disk (from the kiwi image) * end of the disk (from the old system)
In such a situation I wouldn't be surprised if gdisk behaves differently from the typical case where we just find lots of zeros at the end of the disk. The errors above are really just a side effect of that.
There is code in kiwi which should fix that. The method is called relocateGPTAtEndOfDisk and should cleanup the mismatch between new gpt at start and potentially old data at the end gdisk ist called with x e w y but only if gdisk ist part of the initrd. If not you should see a log message "Warning, gdisk tool not found" Could you check that ? Thanks Regards, Marcus -- Public Key available via: https://keybase.io keybase search marcus_schaefer ------------------------------------------------------- Marcus Schäfer (Res. & Dev.) SUSE Linux GmbH Tel: 0911-740 53 0 Maxfeldstrasse 5 FAX: 0911-740 53 479 D-90409 Nürnberg HRB: 21284 (AG Nürnberg) Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton http://www.suse.de ------------------------------------------------------- -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org