Grub/Bootmanager destroyed how to restore?

Started by mash, 2022/05/29, 19:41:19

Previous topic - Next topic

hendrikL

Like

# cryptsetup luksOpen /dev/foo foo

# mount /dev/mapper/foo /mnt


?

Only to understand what you are doing!

lanig

@hendrikL
Quote# cryptsetup luksOpen /dev/foo foo

# mount /dev/mapper/foo /mnt
Yes, this is what I have done, I don't have any problem with this part.

@ro_sid : yes, the "grub_efi_load_image" message is  after I have "fixed" grub.
There is one thing that I would like to know :
my efi partition has only one directory named "EFI" so when I mount my efi partition to inside /boot I have in fact a /boot/efi/EFI directory. Could it be a problem to install properly grub?
Grub correctly sees the hd0gpt2 (encrypted) partition where / resides.

ro_sid

Hello, I hope in "@ro_sid : yes, the "grub_efi_load_image" message is  after I have "fixed" grub." there is a 'gone' missing?!  :)
If not, it is still messy.

And yes, /boot/efi is exactly the correct mountpoint, so /boot/efi/EFI is as it should be.
Within EFI/, there should at least be a subdirectory "siduction" and, may be, "BOOT". Since you have not a (just) BOOT-directory already, it is a good idea to copy that BOOT-directory in EFI/ to the partition-root (i.e. /boot/efi), too, such that you have an /boot/efi/BOOT entry. This way, you can boot the disk without an EFI-entry in the EFI-variables list.

This will not help with the encrypted partition, though. What error (message) do you get now? Still "no such cryptodisk found"?

tommy2

Had a simular issue, ended up using super grub 2 to start my system. Once that was up I sudo grub-install /dev/sda(x) in my case 2 the second partition when that completed I ran sudo update-grub and all was back to normal. In my case I needed to identify which partition my efi was in (2) to make the grub installation in the correct location. Hope this helps..
Tommy2

lanig

Thanks for the answers. I have done what ro_sid suggested me but with no luck so I have given up, backed my files and clone the system with apt-clone and reinstalled siduction which btw allowed me to discover the new artwork.  ;)

lanig

In short :
- Installation of Siduction  with encrypted disk ok
- Boot on new system ok
- apt update ; apt upgrade and installation of new kernel ---> same failure as before. There is something wrong.

I am trying a net install of Debian 12 to compare but the installer is really unpractical for encrypted disks.

lanig

Questions :

- Is the efi partition formated at install time? in this partition, I have a siduction folder and a siduction_2012_3 folder. Could it be the origin of my problems?
- Why siduction can boot an encrypted root fs without a /boot partition and debian 12 can't?

edlin

Quote from: lanig on 2023/09/10, 08:49:38
In short :
- Installation of Siduction  with encrypted disk ok
- Boot on new system ok
- apt update ; apt upgrade and installation of new kernel ---> same failure as before. There is something wrong.
What i would do:
- Installation of Siduction  with encrypted disk
- Boot on new system
- apt update ; apt full-upgrade and installation of new kernel
- grub-install
- update-grub
- reboot

edlin
,,Ein kluger Mann macht nicht alle Fehler selber. Er lässt auch anderen eine Chance."

Winston Churchill

hendrikL

Why not use one of our fixed ISO's!

Maybe we have to announce it.

Or like edlin wrote and/or as written at the top of our warnings, https://forum.siduction.org/index.php?topic=9115.0

lanig

Thanks for the answers. I absolutely need my laptop tomorrow so I've installed Bookworm which works. The one year and a half spent with Siduction was very nice, with far less hassles (in fact until this one, only one) that I had imagined. Thanks to the developers and the forum members.

eriefisher

I am having similar issues. An update a few days ago rendered my laptop unbootable. Booted a current iso to run grub-install and update-grub but the system just freezes. Also tried to use the live system to boot the installed system but it wouldn't find it. I decided to reinstall. Installation runs fine until installing the boot loader and the system locks up. I use the live system to boot into the newly installed system and again run grub-install but the system freezes.
When there was a freeze up I let it go just to see if it would eventually complete but no go. I may try and older iso and hope for better results 
I AM CANADIAN!

hendrikL

#41
intel_iommu=igfx_off

Maybe you need to add this to the boot command line.

And if you install new, please before rebooting after apt full-upgrade do an apt grub-install and update-grub.

See https://forum.siduction.org/index.php?topic=9115.0

and here https://forum.siduction.org/index.php?topic=9118.0

ro_sid

Falls sich jemand das Experimentieren "nicht antun" will und auf unkomplizierte Wiederherstellung Wert legt, ferner ein boot-fähiges Medum (Stick, SSD, Platte etc.) zu opfern bereit ist, möchte ich ihn auf das Programm "Relax and Recover" (Debian-Paket "rear") hinweisen. Dessen Hauptaufgabe ist die Wiederherstellung der Bootfähigkeit anhand der letzten Sicherung.
Es kann auch komplette Sicherungen vornehmen, aber sein Hauptaugenmerk liegt auf der Boot-Wiederherstellung.