On 10/17/2016 08:53 PM, Andreas Färber wrote:
Am 17.10.2016 um 20:00 schrieb Andreas Färber:
Am 17.10.2016 um 19:32 schrieb Andreas Färber:
Am 13.10.2016 um 17:30 schrieb Guillaume Gardet:
Le 13/10/2016 à 17:00, Andreas Färber a écrit :
Am 13.10.2016 um 16:15 schrieb Guillaume Gardet: [RPi2:]
If I reboot [...], I get a GRUB error: "attempt to read or write outside partition". This looks suspicious:
[ 0.171496] Calling pre-init stage in system image [ 809.514233] systemd-udevd[1545]: starting version 228 [ 810.029519] device-mapper: uevent: version 1.0.3 [ 810.049938] device-mapper: ioctl: 4.34.0-ioctl (2015-10-28) initialised: dm-devel@redhat.com [ 23.774995] Creating dracut based initrd [ 1016.740272] device-mapper: core: cleaned up skiped writing MBR ID for armv7l GPT fdisk (gdisk) version 1.0.1
Caution! After loading partitions, the CRC doesn't check out! Partition table scan: MBR: MBR only BSD: not present APM: not present GPT: damaged
Found valid MBR and corrupt GPT. Which do you want to use? (Using the GPT MAY permit recovery of GPT data.) 1 - MBR 2 - GPT 3 - Create blank GPT
Your answer: Command (? for help): b back up GPT data to a file c change a partition's name d delete a partition i show detailed information on a partition l list known partition types n add a new partition o create a new empty GUID partition table (GPT) p print the partition table q quit without saving changes r recovery and transformation options (experts only) s sort partitions t change a partition's type code v verify disk w write table to disk and exit x extra functionality (experts only) ? print this menu
Command (? for help): b back up GPT data to a file c change a partition's name d delete a partition i show detailed information on a partition l list known partition types n add a new partition o create a new empty GUID partition table (GPT) p print the partition table q quit without saving changes r recovery and transformation options (experts only) s sort partitions t change a partition's type code v verify disk w write table to disk and exit x extra functionality (experts only) ? print this menu
Command (? for help): b back up GPT data to a file c change a partition's name d delete a partition i show detailed information on a partition l list known partition types n add a new partition o create a new empty GUID partition table (GPT) p print the partition table q quit without saving changes r recovery and transformation options (experts only) s sort partitions t change a partition's type code v verify disk w write table to disk and exit x extra functionality (experts only) ? print this menu
Command (? for help): b back up GPT data to a file c change a partition's name d delete a partition i show detailed information on a partition l list known partition types n add a new partition o create a new empty GUID partition table (GPT) p print the partition table q quit without saving changes r recovery and transformation options (experts only) s sort partitions t change a partition's type code v verify disk w write table to disk and exit x extra functionality (experts only) ? print this menu
Command (? for help): b back up GPT data to a file c change a partition's name d delete a partition i show detailed information on a partition l list known partition types n add a new partition o create a new empty GUID partition table (GPT) p print the partition table q quit without saving changes r recovery and transformation options (experts only) s sort partitions t change a partition's type code v verify disk w write table to disk and exit x extra functionality (experts only) ? print this menu
Command (? for help): Expert command (? for help): Recovery/transformation command (? for help): WARNING! Hybrid MBRs are flaky and dangerous! If you decide not to use one, just hit the Enter key at the below prompt and your MBR partition table will be untouched.
Type from one to three GPT partition numbers, separated by spaces, to be added to the hybrid MBR, in sequence: Place EFI GPT (0xEE) partition first in MBR (good for GRUB)? (Y/N): Creating entry for GPT partition #1 (MBR partition #1) Enter an MBR hex code (default EF): Set the bootable flag? (Y/N): Creating entry for GPT partition #2 (MBR partition #2) Enter an MBR hex code (default 83): Set the bootable flag? (Y/N): Creating entry for GPT partition #3 (MBR partition #3) Enter an MBR hex code (default 83): Set the bootable flag? (Y/N): Recovery/transformation command (? for help): Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING PARTITIONS!!
Do you want to proceed? (Y/N): OK; writing new GUID partition table (GPT) to /dev/mmcblk0. Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully.
So, apparently we fail to answer to the question, and as a result it doesn't use the new MBR but instead an old GPT it found on the disk? For comparison on blank SD card:
skiped writing MBR ID for armv7l GPT fdisk (gdisk) version 1.0.1
Partition table scan: MBR: MBR only BSD: not present APM: not present GPT: not present
*************************************************************** Found invalid GPT and valid MBR; converting MBR to GPT format in memory. THIS OPERATION IS POTENTIALLY DESTRUCTIVE! Exit by typing 'q' if you don't want to convert your MBR partitions to GPT format! ***************************************************************
Command (? for help): Expert command (? for help): Partition number (1-3): Known attributes are: 0: system partition 1: hide from EFI 2: legacy BIOS bootable 60: read-only 62: hidden 63: do not automount
Attribute value is 0000000000000000. Set fields are: No fields set
Toggle which attribute field (0-63, 64 or <Enter> to exit): Have enabled the 'legacy BIOS bootable' attribute. Attribute value is 0000000000000004. Set fields are: 2 (legacy BIOS bootable)
Toggle which attribute field (0-63, 64 or <Enter> to exit): Expert command (? for help): Command (? for help): Expert command (? for help): Recovery/transformation command (? for help): WARNING! Hybrid MBRs are flaky and dangerous! If you decide not to use one, just hit the Enter key at the below prompt and your MBR partition table will be untouched.
Type from one to three GPT partition numbers, separated by spaces, to be added to the hybrid MBR, in sequence: Place EFI GPT (0xEE) partition first in MBR (good for GRUB)? (Y/N): Creating entry for GPT partition #1 (MBR partition #1) Enter an MBR hex code (default 07): Set the bootable flag? (Y/N): Creating entry for GPT partition #2 (MBR partition #2) Enter an MBR hex code (default 83): Set the bootable flag? (Y/N): Creating entry for GPT partition #3 (MBR partition #3) Enter an MBR hex code (default 82): Set the bootable flag? (Y/N): Recovery/transformation command (? for help): Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING PARTITIONS!!
Do you want to proceed? (Y/N): OK; writing new GUID partition table (GPT) to /dev/mmcblk0. Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully.
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. Thanks, Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org