Results 1 to 2 of 2

Thread: Broken system : unable to boot - Question 4

  1. #1
    Join Date
    Jun 2008
    Location
    South-West France
    Posts
    1,024

    Default Broken system : unable to boot - Question 4

    I have a lot of questions about how to repair a broken system. I have already read a lot of things on your forum.
    As I did not want to mix different questions with different answers I am going to open a thread for each subject.

    Before system got broken :
    Code:
     uname -a
    Linux linux-u6go 4.4.104-39-default #1 SMP Thu Jan 4 08:11:03 UTC 2018 (7db1912) x86_64 x86_64 x86_64 GNU/Linux
    Hardware info : http://paste.opensuse.org/80894240
    --- ! ---

    Question 4 .

    To update the nvidia driver ( the hardway ) I use to use the following script after rebooting in text mode ( init 3 ) :
    http://paste.opensuse.org/41878300

    When running the command
    Code:
    CMD="zypper rm drm-kmp-default
    echo "$CMD"
    eval "$CMD"
    I did not pay attention that the zypper command was going to remove the kernel
    And I have silly accepted the command.

    Then zypper removed the kernel, leaving the system unbootable.

    How is it possible ?
    Thanks for helping. JCD
    __________

    server leap 15-- ASUS g75vw KDE leap 42.3 -- ASUS g750JZ KDE leap 42.3 -- acer aspire s13 win 10 home -- HP Omen win 10 home - scan EPSON V500 - Brother HL2250DN - Samsung CLP-325W

  2. #2
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    12,356
    Blog Entries
    3

    Default Re: Broken system : unable to boot - Question 4

    Quote Originally Posted by jcdole View Post
    I did not pay attention that the zypper command was going to remove the kernel
    And I have silly accepted the command.

    Then zypper removed the kernel, leaving the system unbootable.

    How is it possible ?
    I would not have expected that to happen.

    Once, a long time ago (maybe 2006), I found myself without a kernel. That was before the multi-version kernel setup. So the updater (I think it was called "zen" back then) deleted the current kernel. Then it failed to install the new kernel because there wasn't enough space in "/boot".

    I was lucky. I noticed it before rebooting. So I cleared some space in "/boot", and used Yast to install a kernel.

    Back to your problem.

    You will need a way of booting. Either boot to the installer in rescue mode. Or maybe used the Tumbleweed Rescue live CD.

    If you can boot to that, then:

    Mount your root file system at "/mnt".
    Mount all other file systems as appropriate, relative to "/mnt". For example you would mount the "/home" file system to "/mnt/home" and any "/boot" file system to "/mnt/boot". And if this is an EFI box, mount the EFI partition to "/mnt/boot/efi".

    When you have that all done:
    Code:
    mount --bind /dev /mnt/dev
    mount --bind /proc /mnt/proc
    mount --bind /sys /mnt/sys
    At that point, you should be able to chroot into the mounted system
    Code:
    chroot /mnt
    You will be in a bash shell. You can run yast (the command line ncurses version) to install a kernel. Or you can use zypper to install a kernel.

    Then exit from "chroot" shell, reboot and you should be back in business.
    openSUSE Leap 15.1; KDE Plasma 5;

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •