Page 1 of 4 123 ... LastLast
Results 1 to 10 of 32

Thread: Cannot boot into GRUB on legacy BIOS system

  1. #1

    Unhappy Cannot boot into GRUB on legacy BIOS system

    Hi,

    I went through the installation process for openSUSE Tumbleweed. I used the recommended partitioning. When I rebooted, I got a BIOS error that an operating system could not be found. I am using legacy BIOS. I was able to boot into to the system using the live usb, and everything was working.

    Does anyone know the issue?

    Thanks.
    Rohan

  2. #2
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    29,658
    Blog Entries
    15

    Default Re: Cannot boot into GRUB on legacy BIOS system

    Quote Originally Posted by gnurohan View Post
    Hi,

    I went through the installation process for openSUSE Tumbleweed. I used the recommended partitioning. When I rebooted, I got a BIOS error that an operating system could not be found. I am using legacy BIOS. I was able to boot into to the system using the live usb, and everything was working.

    Does anyone know the issue?

    Thanks.
    Rohan
    Hi and welcome to the Forum
    Can you boot from the live usb, open a terminal and show the output from the following fdisk command;

    Code:
    su -
    fdisk -l
    exit
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  3. #3
    Join Date
    Sep 2012
    Posts
    5,905

    Default Re: Cannot boot into GRUB on legacy BIOS system

    Quote Originally Posted by gnurohan View Post
    Does anyone know the issue?
    Boot live linux, run https://github.com/arvidjaar/bootinf...bootinfoscript, upload results to https://susepaste.org/.

  4. #4

    Default Re: Cannot boot into GRUB on legacy BIOS system

    IMHO you need to manually set legacy BIOS booting during installation.
    Partitioning differs from UEFI, etc.

  5. #5

    Default Re: Cannot boot into GRUB on legacy BIOS system

    Quote Originally Posted by Svyatko View Post
    IMHO you need to manually set legacy BIOS booting during installation.
    Partitioning differs from UEFI, etc.
    Installed TW netinstall on a Coreboot machine last weekend, no such thing as a BIOS/UEFI selection menu here...

    Wanted to boot a BIOS TW on a Gigabyte board set to BIOS yesterday, the board didn't find the SSD with TW until I chose in the BIOS options "reset to failsafe defaults". Afterwards the SSD and a HDD were identfied as bootable with BIOS installs...
    Kind regards

    raspu

  6. #6

    Default Re: Cannot boot into GRUB on legacy BIOS system

    Quote Originally Posted by suse_rasputin View Post
    Installed TW netinstall on a Coreboot machine last weekend, no such thing as a BIOS/UEFI selection menu here...

    Wanted to boot a BIOS TW on a Gigabyte board set to BIOS yesterday, the board didn't find the SSD with TW until I chose in the BIOS options "reset to failsafe defaults". Afterwards the SSD and a HDD were identified as bootable with BIOS installs...
    Turn on "CSM Support" in mobo settings. Then proceed with installation. For disk partitioning you need MBR, not GPT.
    (GPT with Linux is possible, but I not tried it yet, and Windows requires [BIOS+MBR or UEFI+GPT]).

    CSM Support
    Enables or disables UEFI CSM (Compatibility Support Module) to support a legacy PC boot process.
    Enabled
    Enables UEFI CSM. (Default)
    Disabled
    Disables UEFI CSM and supports UEFI BIOS boot process only.
    From https://opensuse-guide.org/installation.php :


  7. #7

    Default Re: Cannot boot into GRUB on legacy BIOS system

    For disk partitioning you need MBR, not GPT.
    Yepp, but that's been the default here for any TW I installed (though I always use EXT4, not BTRFS...).
    Kind regards

    raspu

  8. #8

    Default Re: Cannot boot into GRUB on legacy BIOS system

    Hi,

    Sorry, I meant the Install USB, not the Live USB. I booted from the Install USB and selected the "Load Linux Kernel", then I selected /dev/sda1, and it booted into the installed system. I think the only problem is the bootloader.

    Here is the output for fdisk:

    Code:
    rohan@XPS-L702X:~> sudo fdisk -l
    [sudo] password for root: 
    Disk /dev/sda: 238.49 GiB, 256060514304 bytes, 500118192 sectors
    Disk model: SAMSUNG SSD PM83
    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: CD225F90-F864-4A27-A6A6-3691A4C44708
    
    Device         Start       End   Sectors   Size Type
    /dev/sda1       2048 495923199 495921152 236.5G Linux filesystem
    /dev/sda2  495923200 500118158   4194959     2G Linux swap
    
    
    Disk /dev/sdb: 14.93 GiB, 16008609792 bytes, 31266816 sectors
    Disk model: Cruzer          
    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: dos
    Disk identifier: 0x4b07bb88
    
    Device     Boot Start     End Sectors  Size Id Type
    /dev/sdb1        3480   12047    8568  4.2M ef EFI (FAT-12/16/32)
    /dev/sdb2  *    12048 9082879 9070832  4.3G 17 Hidden HPFS/NTFS
    rohan@XPS-L702X:~>
    fdisk print command:

    Code:
    Disk /dev/sda: 238.49 GiB, 256060514304 bytes, 500118192 sectors
    Disk model: SAMSUNG SSD PM83
    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: CD225F90-F864-4A27-A6A6-3691A4C44708
    First LBA: 34
    Last LBA: 500118158
    Alternative LBA: 500118191
    Partition entries LBA: 2
    Allocated partition entries: 128
    
    Device         Start       End   Sectors Type-UUID                            UUID                                 Name Attrs
    /dev/sda1       2048 495923199 495921152 0FC63DAF-8483-4772-8E79-3D69D8477DE4 F56A8F79-4A3B-421A-BB56-1BEE50BD3AA6      LegacyBIOSBootable
    /dev/sda2  495923200 500118158   4194959 0657FD6D-A4AB-43C4-84E5-0933C84B4F4F D1A644EA-39F2-479A-8F6F-6D2D7B2BD4C9
    Thanks,
    Rohan

  9. #9
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    29,658
    Blog Entries
    15

    Default Re: Cannot boot into GRUB on legacy BIOS system

    Quote Originally Posted by gnurohan View Post
    Hi,

    Sorry, I meant the Install USB, not the Live USB. I booted from the Install USB and selected the "Load Linux Kernel", then I selected /dev/sda1, and it booted into the installed system. I think the only problem is the bootloader.

    Here is the output for fdisk:

    Code:
    rohan@XPS-L702X:~> sudo fdisk -l
    [sudo] password for root: 
    Disk /dev/sda: 238.49 GiB, 256060514304 bytes, 500118192 sectors
    Disk model: SAMSUNG SSD PM83
    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: CD225F90-F864-4A27-A6A6-3691A4C44708
    
    Device         Start       End   Sectors   Size Type
    /dev/sda1       2048 495923199 495921152 236.5G Linux filesystem
    /dev/sda2  495923200 500118158   4194959     2G Linux swap
    
    
    Disk /dev/sdb: 14.93 GiB, 16008609792 bytes, 31266816 sectors
    Disk model: Cruzer          
    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: dos
    Disk identifier: 0x4b07bb88
    
    Device     Boot Start     End Sectors  Size Id Type
    /dev/sdb1        3480   12047    8568  4.2M ef EFI (FAT-12/16/32)
    /dev/sdb2  *    12048 9082879 9070832  4.3G 17 Hidden HPFS/NTFS
    rohan@XPS-L702X:~>
    fdisk print command:

    Code:
    Disk /dev/sda: 238.49 GiB, 256060514304 bytes, 500118192 sectors
    Disk model: SAMSUNG SSD PM83
    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: CD225F90-F864-4A27-A6A6-3691A4C44708
    First LBA: 34
    Last LBA: 500118158
    Alternative LBA: 500118191
    Partition entries LBA: 2
    Allocated partition entries: 128
    
    Device         Start       End   Sectors Type-UUID                            UUID                                 Name Attrs
    /dev/sda1       2048 495923199 495921152 0FC63DAF-8483-4772-8E79-3D69D8477DE4 F56A8F79-4A3B-421A-BB56-1BEE50BD3AA6      LegacyBIOSBootable
    /dev/sda2  495923200 500118158   4194959 0657FD6D-A4AB-43C4-84E5-0933C84B4F4F D1A644EA-39F2-479A-8F6F-6D2D7B2BD4C9
    Thanks,
    Rohan
    Hi
    Disk /dev/sda does not have the boot flag set.

    Code:
    fdisk /dev/sda
    a
    1
    w
    The a for set boot flag, the 1 to select sda1, the w to write, then you should see the * against /dev/sda1 from the fdisk -l output.
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  10. #10

    Question Re: Cannot boot into GRUB on legacy BIOS system

    Quote Originally Posted by malcolmlewis View Post
    Hi
    Disk /dev/sda does not have the boot flag set.

    Code:
    fdisk /dev/sda
    a
    1
    w
    The a for set boot flag, the 1 to select sda1, the w to write, then you should see the * against /dev/sda1 from the fdisk -l output.
    Hi,

    The command a in fdisk does not work when I tried it, and it doesn't come up on the help screen.

    When I typed x to go to expert mode, there was a command A to "toggle the legacy BIOS bootable flag". Is that the one you are talking about? /dev/sda1 already shows "LegacyBIOSBootable" when typing p.

    Thanks,
    Rohan

Page 1 of 4 123 ... LastLast

Tags for this Thread

Posting Permissions

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