Siduction Forum
Siduction Forum => Installation - Support => Topic started by: mash on 2022/05/29, 19:41:19
-
Hi,
yesterday I used my laptop on battery and unfortunately the battery went dead before I could plug it in again.
This happened before without causing any damage. Nevertheless this time the bootmanager was affected and the bootmanager shows only the option of booting windows.
I have a small windows 10 system installed on the laptop in question that I need from time to time but not very often.
Situation:
/dev/sda is a 256 GB ssd
/dev/sda1 [acer recovery for windows] 500 MB
/dev/sda2 EFI 100MB Including a folder for winboot and siduction_2018.3.0
/dev/sda4 Windows system Partition 110 GB
/dev/sda5 Linux system partition 125 GB
/dev/sdb is the hdd containing the actual data
-------------------------------------
How can I repair the bootmanagaer, so that siduction is shown again in bootmanager?
------
When I insert a USB pendrive with siduction 2021.3 (wintersky) the USB drive is shown in the bootmanager together with windows.
Siduction from USB now offers "detect EFI Bootloaders"
After selecting "detect EFI Bootloaders" I can select
/efi/siduction_2018.3.0/grubx64.efi(see image)
----
So, in fact I can start my previous siduction installation without any problems but going over the USB is a possible solution but not an option in the long run.
So I started wintersky and went to the installer in the hope that there is an option to fix the boot-system, but I only could find a new install.
So, please any advice on how to fix this?
thanks and sorry for the long explanation(s)
-
Okay here is what you can do.
1. Boot into the siduction live iso.
2. Open the terminal and get root privileges
3. lsblk -o +LABEL and identify your root- and your EFI-Partition
4. mount /dev/<rootfs> /mnt
mount /dev/<efi-partition> /mnt/boot/efi
replace <rootfs> and <efi-partition> with the right devices
5.for dir in /dev /dev/pts /proc /sys /run ; do mount --bind $dir /mnt$dir ; done 6.chroot /mnt /bin/bashNow you should have successfully chrooted into your system.
You can try two different things now. The easy one is issuing a simple
update-grub but if you want to be sure that grub is reinstalled you first find out if linux device naming has changed in the meantime (using lsblk again) and after that you do
grub-install /dev/sdX # where X is the right device letter
# or for nvme drives
grub-install /dev/nvmeXnY # where X and Y are the right device numbers
Note: In both cases don't pass a partition to this command e.g. no /dev/sda1 you need to provide it with just the device.
After that you can exit the chroot using exit unmount the bind mounted directories using
for dir in /run /sys /proc /dev/pts /dev ; do umount /mnt$dir ; done unmount your partitions
umount /mnt/boot/efi
umount /mnt and reboot afterwards.
Note that if you want to be carefull you should do a backup of your system (if you don't already have one) before doing this.
-
Thanks for this invaluable hint.
I will try that tomorrow. (After a day of seven hours seminars I am just blank in my mind).
Question: do I really have to do that from the live ISO or is this even possible from the siduction already installed?
-
So, in fact I can start my previous siduction installation without any problems but going over the USB is a possible solution but not an option in the long run.
Ah I missed that bit.
Of course you can install it from the already installed system. In that case update-grub might be sufficient. If that fails find out the drive your bootloader resides on and do the
grub-install /dev/sdX if that also fails try what's described here https://forum.siduction.org/index.php?topic=8250.msg66572#msg66572
EDIT: Just for clarification you can skip the entire chroot part i.e. the part with mounting and chrooting and unmounting
EDIT2: Considering you lost power, your filesystem could be corrupted. It could therefore be wide to run fsck on your filesystems either by using the live system (find out the right disks first then run as root)
fsck /dev/<rootfs> /dev/<efi-partition>
or by appending fsck.mode=force to line starting with linux in grub. You can do this by pressing e in grub of your installed system.
If everything I told you fails it may be that for some reason the boot order in your UEFI changed and windows is now on the first place, in this case you need to change the bootorder either in your UEFI settings or using efibootmgr
-
Of course you can install it from the already installed system. In that case
Code: [Select]
update-grub
That did not do the trick
If that fails find out the drive your bootloader resides on and do the
Code: [Select]
grub-install /dev/sdX
if that also fails try what's described here https://forum.siduction.org/index.php?topic=8250.msg66572#msg66572
where /dev/sdX is /dev/sda or an explicit /dev/sda# and # is the number of the partition (in my case 2)???
-
/dev/sdX is just the device e.g. /dev/sda
-
On EFI systems there is much simplier.
grub-install
is all you need, from a bootet siduction (no chroot).
-
On EFI systems there is much simplier.
Code: [Select]
grub-install
is all you need, from a bootet siduction (no chroot).
No that gives me:
grub-install
Installing for x86_64-efi platform.
grub-install: error: cannot find EFI directory.
Same for grub-install /dev/sdX
-
Is the system booted from live system, or is the install booted?
fdisk -l
mount | egrep -i "/dev/sd|/dev/nv"
-
Hi towo this is (part of) the result:
Disk /dev/sdb: 238,47 GiB, 256060514304 bytes, 500118192 sectors
Disk model: KINGSTON RBU-SNS
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 6DD228F8-BABB-4316-A9D4-70EBF5BDF927
Device Start End Sectors Size Type
/dev/sdb1 2048 1023999 1021952 499M Windows recovery environment
/dev/sdb2 1024000 1228799 204800 100M EFI System
/dev/sdb3 1228800 1261567 32768 16M Microsoft reserved
/dev/sdb4 1261568 233877503 232615936 110,9G Microsoft basic data
/dev/sdb5 233877504 500117503 266240000 127G Linux filesystem
Disk /dev/sda: 1,82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: ST2000LM003 HN-M
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 45768881-4C8D-436F-87F3-B469538E2B2A
Device Start End Sectors Size Type
/dev/sda1 2048 2457602047 2457600000 1,1T Linux filesystem
/dev/sda2 2457602048 3292628991 835026944 398,2G Microsoft basic data
/dev/sda3 3292628992 3804678143 512049152 244,2G Linux filesystem
/dev/sda4 3804678144 3907028991 102350848 48,8G Linux filesystem
GPT PMBR size mismatch (6066815 != 15155199) will be corrected by write.
I am aware that sometimes /dev/sdb and /dev/sda are switched after a reboot.
Strange is the last line
-
mount | egrep -i "/dev/sd|/dev/nv"
is missing in your post above.
-
mount | egrep -i "/dev/sd|/dev/nv"
/dev/sdb5 on / type ext4 (rw,relatime,errors=remount-ro)
/dev/sda4 on /home type ext4 (rw,nosuid,nodev,relatime)
/dev/sda1 on /media/work type ext4 (rw,nosuid,nodev,relatime)
/dev/sda2 on /media/workwin type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096)
-
You have to mount /dev/sdb2 as /boot/efi, it is missing in your post!
paste your /etc/fstab!
-
/etc/fstab
UUID=43af36f7-ba98-4253-8043-dd7b1cbf39f9 / ext4 defaults,relatime,errors=remount-ro 0 1
zonzamas://volume1/picopartido /media/picopartido nfs noauto,users 0 0 vers=3
zonzamas://volume1/fotowandern /media/fotowandern nfs noauto,users 0 0 vers=3
UUID=29feb48c-ead8-4133-b541-a1c4ac134d26 /media/work ext4 auto,users,rw,exec,relatime 0 0
UUID=68E58EFC253FF11E /media/workwin ntfs auto,users,rw,exec,relatime 0 0
UUID=efedc021-0618-412f-8f84-5e0a43391e30 /home ext4 auto,users,rw,exec,relatime 0 0
# mount /dev/sdb2 /boot/efi
# grub-install /dev/sdb
Installing for x86_64-efi platform.
Installation finished. No error reported.
-
Hi towo, this did not really work.
After a restart the bootmanager has an entry to boot siduction but it results in grub konsole after selecting it
see image 1
When booting from USB and selecting "detect EFI Bootloaders"
Then I select
/efi/siduction_2018.3.0/grubx64.efi
I also end up in the grub_rescue mode with error:
error: symbol 'grub_is_lockdown' not found(see image 2)
----
Edit:
the command ls in grub_rescue results in
(hd0) (hd0,gpt3) (hd0,gpt2) (hd0,gpt1) (hd1) (hd1,gpt5) (hd1,gpt4) (hd1,gpt3) (hd1,gpt2) (hd1,gpt1) (hd2) (hd2,gpt4) (hd2,gpt3) (hd2,gpt2) (hd2,gpt1) (cd0)
I think that hd0 is the USB stick which is still inserted. hd1 is the ssd and hd2 is the data disk.
But ls (hd1,gpt2) (or any other disk) results in Filesystem is unknown
-
Your fstab is missing the entry for efi!
-
or try supergrub2
https://www.supergrubdisk.org/super-grub2-disk/
-
or 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.
-
step by step
1. boot your siduction#
2. fix your fstab
3. install grub
4. provide us the outpot of
efibootmgr -v5. provide us the output of
lsblk -o NAME,MOUNTPOINT,PTUUID
-
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
-
The best would be, you come to IRC, forum is too slow fur such problems.
I had make a mistake
lsblk -o NAME,MOUNTPOINT,PARTUUIDis the output, i want.
-
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?
-
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.
-
grub-install gives error: install device isn't specified
-
grub-install gives error: install device isn't specified
grub-install /dev/sdX
without a target it only works on EFI systems.
-
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 :
[ This attachment cannot be displayed inline in 'Print Page' view ]
What should I do to get the / correctly mounted?
-
@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!
-
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 /.
-
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.
-
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?
-
Like
# cryptsetup luksOpen /dev/foo foo
# mount /dev/mapper/foo /mnt
?
Only to understand what you are doing!
-
@hendrikL
# 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.
-
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"?
-
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
-
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. ;)
-
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.
-
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?
-
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
-
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
-
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.
-
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
-
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
-
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.