Package: cloud.debian.org
Followup-For: Bug #1130560
X-Debbugs-Cc: [email protected]
Dear Maintainer,
* What led up to the situation?
I confirm that raspi4 does not boot with the daily image (copied by dd after
tar)
I have also installed the image on a raspi3 added somme software it has been
impossible to clone the enhanced image -> **kernel panic**
* What exactly did you do (or not do) that was effective (or
ineffective)?
For the Pi4 the boot fails as explained by the previous message.
For the Pi3 install is OK Boot (multiple times) is OK But dd copy of the image
yields an unbootable image. All attempts with `gdisk` or `fdisk` failed to
recover a bootable image (garbage on partition table, inode errors ...)
* What was the outcome of this action?
The error message with `gdisk` is :
```shell
Caution: invalid backup GPT header, but valid main header; regenerating
backup header from main header.
Warning! Main and backup partition tables differ! Use the 'c' and 'e' options
on the recovery & transformation menu to examine the two tables.
Warning! One or more CRCs don't match. You should repair the disk!
Main header: OK
Backup header: ERROR
Main partition table: OK
Backup partition table: ERROR
Partition table scan:
MBR: hybrid
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
```
* What outcome did you expect instead?
I expected a bootable image
* Remars
I notice that the first partition is numbered 15 and the main partition is
numbered 2, which seems coherent with hints proposed in the previous message.
