Grub/Bootmanager destroyed how to restore?

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

Previous topic - Next topic

towo

Your fstab is missing the entry for efi!
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

gorzka

or try supergrub2

https://www.supergrubdisk.org/super-grub2-disk/
Auf dem Baum da saß ein Specht
der Baum war hoch, dem Specht war schlecht

mash

Quoteor try supergrub2
Well at least with supergrub2 I am at the same situation as before. I can boot into my original siduction but it still is a workaround.
I will have a look at the options and possibilities of supergrub2, maybe I find a solution there.
when it was hard to write it should be hard to read

towo

step by step

1. boot your siduction#
2. fix your fstab
3. install grub
4. provide us the outpot of
efibootmgr -v
5. provide us the output of
lsblk -o NAME,MOUNTPOINT,PTUUID
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

mash

efibootmgr -v
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0006,0001,2001,2002,2003
Boot0000* USB HDD: Generic STORAGE DEVICE       PciRoot(0x0)/Pci(0x1a,0x0)/USB(0,0)/USB(0,0)/HD(2,GPT,663d6ede-3cef-4c0c-a007-ceba919e5cca,0x164,0x1680)RC
Boot0001* Windows Boot Manager  HD(2,GPT,8d6d84ca-13e3-4202-8aae-8933f957db75,0xfa000,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...8................
Boot0002* MATSHITABD-MLT UJ272Q                 BBS(CDROM,,0x500)................-...........A......#...............................,........A.........................
Boot0003* KINGSTON RBU-SNS8100S3256GD           BBS(HD,,0x500)................-...........A......B..............................v,........A.........................
Boot0004* ST2000LM003 HN-M201RAD                BBS(PCMCIA,,0x500)................-...........A......R..............................],........A.........................
Boot0005* TOSHIBA TransMemory           BBS(Network,,0x500)............................................................................A...........................
Boot0006* siduction     HD(2,GPT,8d6d84ca-13e3-4202-8aae-8933f957db75,0xfa000,0x32000)/File(\EFI\siduction\grubx64.efi)
Boot2001* EFI USB Device        RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network   RC

and
lsblk -o NAME,MOUNTPOINT,PTUUID
NAME   MOUNTPOINT     PTUUID
sda                   6dd228f8-babb-4316-a9d4-70ebf5bdf927
├─sda1                6dd228f8-babb-4316-a9d4-70ebf5bdf927
├─sda2 /boot/efi      6dd228f8-babb-4316-a9d4-70ebf5bdf927
├─sda3                6dd228f8-babb-4316-a9d4-70ebf5bdf927
├─sda4                6dd228f8-babb-4316-a9d4-70ebf5bdf927
└─sda5 /              6dd228f8-babb-4316-a9d4-70ebf5bdf927
sdb                   45768881-4c8d-436f-87f3-b469538e2b2a
├─sdb1 /media/work    45768881-4c8d-436f-87f3-b469538e2b2a
├─sdb2 /media/workwin 45768881-4c8d-436f-87f3-b469538e2b2a
├─sdb3                45768881-4c8d-436f-87f3-b469538e2b2a
└─sdb4 /home          45768881-4c8d-436f-87f3-b469538e2b2a
sdc                   663d6ede-3cef-4c0c-a005-ceba919e5cca
├─sdc1                663d6ede-3cef-4c0c-a005-ceba919e5cca
├─sdc2                663d6ede-3cef-4c0c-a005-ceba919e5cca
└─sdc3                663d6ede-3cef-4c0c-a005-ceba919e5cca
sr0                   

when it was hard to write it should be hard to read

towo

The best would be, you come to IRC, forum is too slow fur such problems.
I had make a mistake
lsblk -o NAME,MOUNTPOINT,PARTUUID
is the output, i want.
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

sotnik

Hello
I have a similar problem. The system was idle and something happen and lost internet. After reboot does not boot (goes to bios).
How I can  get root privileges in live CD to restore grub?

hendrikL

so, if you have a mow or giants iso than it is easy, boot it and click on the chroot-helper icon. When in chroot, than run grub-install and afterwards update-grub, That would be the first thing I would try, reboot and hope.
Or try to update your system again. in chroot. there is a fixed version of grub on the way.
For more information see the upgrade warnings!

You can change to root with sudo su -, if you need to.

sotnik

grub-install gives error: install device isn't specified

towo

Quote from: sotnik on 2023/09/06, 08:50:18
grub-install gives error: install device isn't specified

grub-install /dev/sdX

without a target it only works on EFI systems.
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

lanig

I have also a boot problem described here https://forum.siduction.org/index.php?topic=9110.new#new

I did follow all the steps described on the second post of this thread.

At the
install-grub /dev/nvmeXnY step I got a warning that EFI variables can't be set. Update-grub did not report any problem.

When I enter my password to decrypt the / disk, I got the following message :
[attachment id=0 msg=72194]

What should I do to get the / correctly mounted?

hendrikL

#26
@lanig

Here is the way you could try, but you have to decrypt your system, then mount it.

> https://forum.siduction.org/index.php?topic=8617.msg68872#msg68872

And what you need is a grub-install then an update-grub.

Important is that you also mount your efi partition too!

lanig

Thanks for your answer. This is what I have done but for a reason I don't understand either the encrypted disk is not found, or is found but not decrypted and mounted as /.

ro_sid

After your repair trials, did the "error: symbol `grub_efi_load_image' not found." line vanish? If not, you are still not using the 'fixed' grub. And without that, I doubt that the "cryptodisk" problem can be solved.

By the way, 'grub' is a really powerful tool (when it works  :) ). Even when the configuration does not work, you can get into the command mode (by typing a 'c') and have a look. You have to study the the manual a little bit, or at least use the built-in "h(elp)" command. An e.g. "ls" command should list all available disks and partitions, encrypted or not. [For the encrypted ones, not their contents, of course.] Is your encrypted disk listed there?

Good luck.

hendrikL

#29
with a live ISO you should be able to boot an existing system, did you try this? This is also a possibility.

How do you try to open the encrypted disk?
Which command you use?