I’ve extended the EFI Partition from 1 GB to 10 GB since the system was running with GRUB2 with BLS as the system always claimed that the EFI Partition is not big enough. As this growing using Gparted was not completely good, I’ve still got error messages, I deciced to reinstall that complete system without touching the partitions. Now the Yast bootloader configurator shows “System Boot” als bootloader, I don’t know what this bootloader is and what it means
Thank you. Is there a way to fix it or do I have to do a complete new installation with creating a new partition table? After expanding the partition I left the partition table as it was and formatted the EFI partion. I don’t think that the hint with backup, grub-install will work. Imperfect growing of ESP, does this mean that the partition alignment is wrong?
The FAT32 format includes a BootSector and a BackupBootSector that might be used to mount the partition and access data even in the event that the BootSector becomes unreadable for whatever reason.
On a well formatted partition those two are a copy of each other; in your case this is apparently not true, possibly because the software used to enlarge the partition changed its BootSector but failed to change the copy in the BackupBootSector.
As long as the BootSector is readable, you will not notice that. In case the BootSector becomes unreadable you will not be able to recover the data, since using the BackupBottSector will not reflect the current layout of the partition.
I’m no forensic expert, so I don’t know what tool you can use to restore the backup, other than by deleting the current partition and creating another fresh.
IMHO there is no reason to “destroy the partition” (whatever that may be. What is to be done is creating a new file system on the partition.
Alternative there might be tools to repair the the copy (or maybe put it in the correct place, I do not know where it should be). But that then is a Windows tool of which I do not know anything. Browsing Windows forums/docs might help here.
I never intentionally write anything to partition tables with Linux tools. Since before I made *SUSE my primary pIatform >2 decades ago (coming from OS/2, not Windows), I’ve exclusively used the cross-platform (DOS, OS/2, Windows, Linux, Mac) tool DFSee for virtually all intentional writes, including cloning and imaging, and its automatic logs for keeping up with what lives where on my 40+ multiboot systems. I don’t think I’ve ever seen anyone else mention it here.
DFSee has at least a couple of unfixed GPT bugs, but I use it anyway. It originally was shareware, but the author open-sourced it and then retired from maintaining it.
IME, when it deletes a partition, nothing on the filesystem is disturbed. Thus, that partition can be recreated in the same place and size, with proper tables, and won’t need reformatting or restoring of data.
I am not understanding most of what you say, not knowing many of the names you mention there. But for partitioning I use fdisk and for file system maintenance mkfs and friends.
And yes when you first delete in the partition table an entry for a partition and then restore that with the same boundaries and other data, the contents is not touched (why would one want such a thing?). But in GPT I assume that the Part-UUID will be created anew.
But I think we should not mumble about what we would do, but try to find out what the TO did.
From what to what? Was there unpartitioned space adjacent to the partition?
And yes, this of course alters the partition table.
Yes, why would you alter it? What is the idea behind this remark?
I had a similar issue after resizing my efi partition with gparted. I was able to fix it with
sudo fsck -r -t vfat /dev/nvme0n1p3
You get 3 options:
1) Copy original to backup
2) Copy backup to original
3) No action
I used option 1 and then you have to confirm the change. Obviously your dev is a different one, but you have already been asked about the disk layout. In my case the ssd was nvme0n1 and the efi partition is the 3rd partition on the disk, therefor nvme0n1p3.
I have completely installed my laptop from new, completely wiped my harddisk created a complete new partition table without success. The error message when I open gparted is still the same. I repeat, I used Yast to erase all partitions and created all from new afterwards.
As shown above fsck.vfat -r /dev/(your_disk_partition_here) is apparently able to fix that error, no need to know how and why that happened, even if a wild guess points to enlarging the partition with gparted.
