i have an Intel Nuc-8i3beh running a Debian 10 Buster and Windows 10 in dual boot. The Windows system was installed first. The bootloader is grub in uefi mode.
sda -> main harddrive with windows and debian on
sdb -> second harddrive for data
sdc -> external harddrive for backup of second harddrive
I recently installed some new drivers for the intel systems in Windows 10. After that my bootloader is not showing up anymore. The system directly boots in Windows. I then tried to run a boot-repair image on an usb stick, but the default repair of the Boot-Repair utility wont work. Here is the hole summary of the boot-repair: http://paste.ubuntu.com/p/kgPymkWqGM/
I think the problem lies in the line 29:
wrong fs type, bad option, bad superblock on /dev/sda6, missing codepage or helper program, or other error
Somehow the tabel of the superblocks are not correct anymore:
Disk sda: 111.8 GiB, 120034123776 bytes, 234441648 sectors Disk identifier: EC763990-4AF7-4A4C-A3AA-355A8DC62FB8 Start End Sectors Size Type sda1 2048 1085439 1083392 529M Windows recovery environment sda2 1085440 1290239 204800 100M EFI System sda3 1290240 1323007 32768 16M Microsoft reserved sda4 1323008 117221375 115898368 55.3G Microsoft basic data sda5 117221376 125034495 7813120 3.7G Linux swap sda6 125034496 234437070 109402575 52.2G Linux filesystem
The end of sda6 is not correct anymore.
I tried the following after telcoM's answer. I booted with a live system of debian with an usb drive:
efibootmgr -c -b 0005 -d /dev/sda2 -l \\efi\\debian\\shimx64.efi -L "Debian-UEFI" Could not prepare Boot variable: Permission denied
The same i tried after that with sudo:
sudo efibootmgr -c -b 0005 -d /dev/sda2 -l \\efi\\debian\\shimx64.efi -L "Debian-UEFI" Could not prepare Boot variable: No space left on device
After reading the comment i tried to run the fsck command without success:
sudo e2fsck -C0 -p -f -v /dev/sda6 /dev/sda6: The filesystem size (according to the superblock) is 13675776 blocks The physical size of the device is 13675321 blocks Either the superblock or the partition table is likely to be corrupt! /dev/sda6: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options)
I don't know what options i have to set on fsck when running it manually.
Anyone got an idea of how to fix that? Very thanks