Page 2 of 2 FirstFirst 12
Results 11 to 19 of 19

Thread: No boot

  1. #11

    Default Re: No boot

    Done but I got the same error message:
    Code:
    error: no such device: 18f012b4...
    error: unknown filesystem.
    Entering rescue mode...
    of course, there is no device named 18fo12b4.. in /dev/disk/by_uuid
    my root partition /dev/sdb8 has another uuid
    but the yast boot manager doesn't acknowledge that

    by the way
    , when I boot and reboot, my boot disk often leaps from sda to sdb and backwards

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

    Default Re: No boot

    Quote Originally Posted by lader1 View Post
    by the way
    , when I boot and reboot, my boot disk often leaps from sda to sdb and backwards
    I have had that happen. It was a hardware problem -- actually a problem with the disk cable connector. The system sees a fault. And then when it next sees the disk it assigns a new device name.
    openSUSE Leap 15.1; KDE Plasma 5;
    testing Leap 15.2Alpha

  3. #13

    Default Re: No boot

    But what about the non-existing uuid ? 18f... How to change it when configuring the bootloader ?

  4. #14

    Default Re: No boot

    I noticed one thing: in the /boot/grub2/grub.cfg, the root partition is correctly set, but the installation process doesn't seem to write the good data for the bootloader.

  5. #15
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    12,739
    Blog Entries
    3

    Default Re: No boot

    Quote Originally Posted by lader1 View Post
    But what about the non-existing uuid ? 18f... How to change it when configuring the bootloader ?
    Without seeing the actual error message, it is hard to know the implications.
    openSUSE Leap 15.1; KDE Plasma 5;
    testing Leap 15.2Alpha

  6. #16
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    12,739
    Blog Entries
    3

    Default Re: No boot

    Quote Originally Posted by lader1 View Post
    I noticed one thing: in the /boot/grub2/grub.cfg, the root partition is correctly set, but the installation process doesn't seem to write the good data for the bootloader.
    I have no idea what that means.

    I still do not know whether you are booting with UEFI or with traditional BIOS booting. And if it is traditional BIOS booting, I do not know whether you are booting from the MBR or from the boot sector of another partition. And the meaning of "good data for the bootloader" presumably depends on that.
    openSUSE Leap 15.1; KDE Plasma 5;
    testing Leap 15.2Alpha

  7. #17

    Default Re: No boot

    Quote Originally Posted by nrickert View Post
    I have no idea what that means.

    I still do not know whether you are booting with UEFI or with traditional BIOS booting. And if it is traditional BIOS booting, I do not know whether you are booting from the MBR or from the boot sector of another partition. And the meaning of "good data for the bootloader" presumably depends on that.
    I don't either...

    no UEFI, but a classical BIOS based computer. yast says that it should boot from MBR, Doesn't write generic boot code in MBR.
    In grub.cfg, I have several references to the correct uuid partition, such as --set root=6076e49b...etc...

  8. #18
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    12,739
    Blog Entries
    3

    Default Re: No boot

    When you try to boot, does it read the correct "grub.cfg"?
    openSUSE Leap 15.1; KDE Plasma 5;
    testing Leap 15.2Alpha

  9. #19

    Wink Re: No boot

    PROBLEM SOLVED !

    I had to disconnect all the disks, but the main one, then reinstall with yast, halt the system, reconnect all the disks and reboot. That's all

    Thx anyway for your care about my difficulties with a not so easy conundrum.

Page 2 of 2 FirstFirst 12

Posting Permissions

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