Hi Ian,
On Sun, Feb 02, 2025 at 09:50:03AM +0000, Ian via BitFolk Users wrote:
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/xvda: 52428800 sectors, 25.0 GiB
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 1632EDC1-5D6E-4B1A-9DF5-D1C3D193B0F3
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 52428766
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)
Number Start (sector) End (sector) Size Code Name
1 227328 52428766 24.9 GiB 8300
14 2048 10239 4.0 MiB EF02
15 10240 227327 106.0 MiB EF00
Interesting. Was this a clean install of Ubuntu 24.04 or an upgrade
from 22.04?
You are not affected because you already have a bios_boot partition; it
is partition number 14 here, a 4MiB partition between sectors 2048 and
10239.
You also have what I assume is an EFI System Partition (type EF00) as
#15.
Both of these are what grub wants to see, so no problems.
All the affected users installed 24.04 directly and I can replicate
their problem as the cloud disk image that the installer uses does not
have a bios_boot nor an ESP. It is written directly to the VPS xvda disk
so whatever is in the cloud disk image is what ends up as the initial
state of the VPS, that cloud-init then customises.
So, now the only way I can understand what is going on is if:
a) The 22.04 disk image is different and you upgraded from that
or
b) the 24.04 disk image has changed at some point.
Either way, probably I should be adjusting the 24.04 disk image to be
like the 22.04 one. I already adjusted it to have a bios_boot but I may
as well add an ESP and renumber the partitions as well.
You are making me doubt my memory of what happened two
and a half weeks ago
- was there a complaint when it happened?? - but it's worked since and I
can update and reboot fine.
It seems very unlikely that you have been affected in any way as I'm
sure you would remember repartitioning your disk to include two new
partitions. 😀
Thanks,
Andy
PS The 22.04 cloud image was definitely different:
$ sudo gdisk -l ./jammy-server-cloudimg-amd64.disk
GPT fdisk (gdisk) version 1.0.3
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk ./jammy-server-cloudimg-amd64.disk: 4612096 sectors, 2.2 GiB
Sector size (logical): 512 bytes
Disk identifier (GUID): 1632EDC1-5D6E-4B1A-9DF5-D1C3D193B0F3
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 4612062
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)
Number Start (sector) End (sector) Size Code Name
1 227328 4612062 2.1 GiB 8300
14 2048 10239 4.0 MiB EF02
15 10240 227327 106.0 MiB EF00
--
https://bitfolk.com/ -- No-nonsense VPS hosting