My laptop will not boot. It goes to windows rescuesystem thatfails as there is no windows. I can boot from the rescue USB device but I do not know what to do next. I tried “chroot /Dev/media/Linux/whatever” followed by “grub2-install /Dev/sda” but itsaid there was no /Dev
What should I do?
Apologies for the capital Dev but predictive text on Android…
You first mount the root partition. I usually mount at “/mnt”. But you seem to have mounted at “/Dev/media/Linux/whatever”. I’ll use “/mnt” in my description of what to do. But replace that with the actual mount point.
Next steps:
mount --bind /dev /mnt/dev
mount --bind /proc /mnt/proc
mount --bind /sys /mnt/sys
Again, remember to change the “/mnt” to whatever it should be.
After that do the “chroot”
chroot /mnt
mount -a ### this mounts everything else that might be needed.
You can then do the “grub2-install”. But the actual command to use depends on whether you are using UEFI or legacy booting. If you use the legacy booting version (as you did), that will probably work anyway. I think “grub2-install” will ignore options that don’t make sense and do a UEFI install anyway if you are booted with UEFI.
When finished, and you are able to boot into your system, it is probably a good idea to use Yast bootloader to do this again. That way Yast bootloader will update any pointers that it might need in future.
Many thanks. I knew I needed to do something to make /dev available after the chroot.
Now I am stuck with thee response to grub2-install, which is
Installing for x86_64-efi platform.
grub2-install: error: cannot find EFI directory.
In /boot I see an EFI directory which is empty.
What now?
Update. I realised I forgot the mount -a
With that it appeared to work saying it was ok. But when I tried to reboot without the rescue disk it startedd the windows recovery so i still have a problem.
Booting from the. Rescue disk but choosing boot from hard disk it saysthere is no EFI directory and returns to the boot menu.
Try repeating the entire chroot process, including mount -a. Once in, check the UEFI state:
efibootmgr
then use the text mode YaST to update the bootloader. On exit from YasT bootloader, do efibootmgr again to see that there is an opensuse entry first listed. If not, report back so we can try setting up creation of an entry manually and/or a BIOS reset. Also, provide us a look at bootinfoscript output via https://susepaste.org.
BootOrder: 0001,001B,0010,0011,0012,0013,001A,001C,0017,0018,0019,001D,0000,0022
Boot0000 Windows Boot Manager
Boot0001* opensuse
Boot0010 Setup
Boot0011 Boot Menu
Boot0012 Diagnostic Splash Screen
Boot0013 Lenovo Diagnostics
Boot0014 Startup Interrupt Menu
Boot0015 Rescue and Recovery
Boot0016 MEBx Hot Key
Boot0017* USB CD
Boot0018* USB FDD
Boot0019* NVMe0
Boot001A* ATA HDD1
Boot001B* ATA HDD0
Boot001C* USB HDD
Boot001D* PCI LAN
Boot001E* IDER BOOT CDROM
Boot001F* IDER BOOT Floppy
Boot0020* ATA HDD
Boot0021* ATAPI CD
Boot0022* PCI LAN
localhost:/ #
BootOrder: 0001,001B,0010,0011,0012,0013,001A,001C,0017,0018,0019,001D,0000,0022
Boot0000 Windows Boot Manager
Boot0001* opensuse
Boot0010 Setup
Boot0011 Boot Menu
Boot0012 Diagnostic Splash Screen
Boot0013 Lenovo Diagnostics
Boot0014 Startup Interrupt Menu
Boot0015 Rescue and Recovery
Boot0016 MEBx Hot Key
Boot0017* USB CD
Boot0018* USB FDD
Boot0019* NVMe0
Boot001A* ATA HDD1
Boot001B* ATA HDD0
Boot001C* USB HDD
Boot001D* PCI LAN
Boot001E* IDER BOOT CDROM
Boot001F* IDER BOOT Floppy
Boot0020* ATA HDD
Boot0021* ATAPI CD
Boot0022* PCI LAN
localhost:/ #
Which is why I repeat again and again - under SUSE “update-bootloader --reinit” does the right thing always (as long as system configuration is correct) and matches exactly what YaST would do. You do not need to care whether system is using legacy or UEFI or Secure Boot.
Thanks.
It would be nice if
update-bootloader --help
would give some useful information. But it just seems to freeze (on Leap 15.1).
If I scroll through the script, it does have a little information there, and seems to say that “–help” should work. But I don’t see a mention of “–reinit”.
I think my last message got lost.
I can now boot as it was.
Now back to the original issue of no wireless connection, probably related to f8 key and me not knowing what combination of f shift and control does what.
Hi,
Use
man update-bootloader
It does not really freeze, it just silently executes bootloader configuration. I fully agree, there is room for improvement here. Care to open bug report?