On Fri, Aug 14, 2020 at 10:31:36AM +0200, Thomas Lange wrote:
> > On Fri, 14 Aug 2020 09:45:43 +0200, Bastian Blank
> > said:
>
> > Yes. GPT got a copy of it's header at the beginning and the end. You
> > can expand the whole thing and the tools will relocate the header on the
I've just rebooted an AWS instance running buster and it
has failed to restart, with the message "symbol 'grub_calloc'
not found" shown on the console screenshot.
Just to wrap this up:
Thanks to Noah for your advice.
I have written up what I had to do to repair this at
> On Fri, 14 Aug 2020 09:45:43 +0200, Bastian Blank said:
> Yes. GPT got a copy of it's header at the beginning and the end. You
> can expand the whole thing and the tools will relocate the header on the
> end correctly, but you can't shorten it.
After shorten the image or
On 8/14/20 8:02 AM, Ross Vandegrift wrote:
> Could it be the GPT partition table at the end of the disk?
Right, that's probably the issue. I wonder, what is the way around this.
Thomas
Hi Ross
On Thu, Aug 13, 2020 at 11:02:55PM -0700, Ross Vandegrift wrote:
> Could it be the GPT partition table at the end of the disk? Even truncating
> off 1M breaks it. Nothing will use the copy at the start of the disk, I
> wonder
> what the point of it is.
Yes. GPT got a copy of it's
On Thu, Aug 13, 2020 at 12:37:12AM +0200, Thomas Goirand wrote:
> # Finally, truncate the final disk
> truncate -s ${FINAL_IMAGE_SIZE}M disk.raw
>
> After the parted + truncate, the partition 1 is broken, I don't
> understand why, but that's probably due to this weird layout.
I don't think it's
