GRUB 2 does not start from BIOS anymore

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post please read how to get help
User avatar
gold_finger
Level 9
Level 9
Posts: 2885
Joined: Mon Mar 11, 2013 11:39 pm

Re: GRUB 2 does not start from BIOS anymore

Post by gold_finger »

Moishe wrote:When CSM is not AUTO there are four options for various H/W
For each H/W the options are like Legacy first, only Legacy, or something else or only something else
Tested various options with Legacy a few a few times in the past and it did not help
But can test it again shortly too
Try "only Legacy" if possible.


Side Note: When posting back requested terminal output, please post full output and enclose it in "code" tags as per instructions shown here. The output from your lsblk -fa /dev/sda command was missing information we needed to see (file system type for each partition, partition UUID's, etc.). Doesn't matter now because austin.texas had you run a different command showing UUID's later on to confirm whether they matched what was shown in fstab file; so keep that in mind for future postings.


I don't think having wrong Swap partition UUID would prevent booting, but you might as well fix that. Just boot into the controlling OS and edit the fstab file with your text editor as root and replace wrong UUID with the right one. I don't remember if you told us which OS you're using as the boot controlling one, but if it's Mint 18 (non-KDE), the text editor in command will be "xed". If not Mint 18 it could be "gedit", "pluma", "leafpad", or "kate" (in KDE). If not sure what yours is just open it and go to Help -> About to find out, then use that in the command below in place of "xed".

To open the fstab file with your GUI-based text editor as root, enter the following command:

Code: Select all

gksu xed /etc/fstab
If using a KDE-based distro, the command would be:

Code: Select all

kdesudo kate /etc/fstab
If for some reason you can't figure out what graphical text editor you have, just about all distros include the terminal-based "nano" text editor and you can open the file with that using this command:

Code: Select all

sudo nano /etc/fstab
Find the line for Swap partition and change the UUID to the correct one. Save the file, close the text editor. Reboot computer and maybe we'll all be shocked and it'll boot properly. (I doubt it will actually solve the problem, but who knows?)

If computer still won't boot properly after setting boot mode to Legacy only and also fixing the Swap UUID, I'd have to say I'm completely stumped. Your situation is pretty bizarre. I don't recall seeing anyone else on the forum having this problem and I've never run into anything like this myself.

P.s.
Did you check to see if there is a UEFI/(Bios) update available for your computer/motherboard? Maybe the original is particularly flaky and there has been an update that will fix the problem.
Please add [SOLVED] to your thread if a solution is found. Go to your first post in the thread, hit "Edit" button and add [SOLVED] to the title of the post.

How To Format Your Forum Posts.

Try Linux Beginner Search Engine for Linux questions.
User avatar
Moishe
Level 2
Level 2
Posts: 67
Joined: Thu Jun 02, 2016 6:15 am

Re: GRUB 2 does not start from BIOS anymore

Post by Moishe »

gold_finger wrote: Side Note: When posting back requested terminal output, please post full output and enclose it in "code" tags as per instructions shown here. The output from your lsblk -fa /dev/sda command was missing information we needed to see (file system type for each partition, partition UUID's, etc.). Doesn't matter now because austin.texas had you run a different command showing UUID's later on to confirm whether they matched what was shown in fstab file; so keep that in mind for future postings.
This is the full output on my machine:

Code: Select all

$ lsblk -fa /dev/sda
NAME    FSTYPE LABEL MOUNTPOINT
sda                  
├─sda1               
├─sda2               
├─sda3               
├─sda4               /
├─sda5               
├─sda6               
├─sda7               
├─sda8               
├─sda9               
├─sda10              
├─sda11              
├─sda12              
├─sda13              
├─sda14              
└─sda15  
Have a wonderful day!
"If you're not having fun, you're doing it wrong" - Groucho Marx
User avatar
austin.texas
Level 20
Level 20
Posts: 12046
Joined: Tue Nov 17, 2009 3:57 pm
Location: at /home

Re: GRUB 2 does not start from BIOS anymore

Post by austin.texas »

Moishe wrote:This is the full output on my machine:

Code: Select all

$ lsblk -fa /dev/sda
NAME    FSTYPE LABEL MOUNTPOINT
sda                  
├─sda1               
├─sda2               
├─sda3               
├─sda4               /
├─sda5               
├─sda6               
├─sda7               
├─sda8               
├─sda9               
├─sda10              
├─sda11              
├─sda12              
├─sda13              
├─sda14              
└─sda15  
That result is definitely not what I would expect. For comparison, here is my result of the same command:

Code: Select all

~ $ lsblk -fa /dev/sda
NAME   FSTYPE LABEL           UUID                                 MOUNTPOINT
sda                                                                
├─sda1                                                             
├─sda2 ext4   sda2_LM17.3Cinn a09ad702-6248-41ac-a5c6-af105bb55de9 
└─sda3 ext4   sda3_LM18Cinn   4a6b8a6f-ea6b-45f2-84e0-d184310ed3a6 /
(I only have 3 partitions on that drive.)

To see more info, please post the result of this command:

Code: Select all

 sudo parted --list && lsblk -o name,fstype,size,parttype
The results should resemble this (mine):

Code: Select all

 ~ $  sudo parted --list && lsblk -o name,fstype,size,parttype
Model: ATA SPCC Solid State (scsi)
Disk /dev/sda: 120GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name  Flags
 1      1049kB  2097kB  1049kB                     bios_grub
 2      2097kB  32.2GB  32.2GB  ext4
 3      32.2GB  64.4GB  32.2GB  ext4


Model: ATA WDC WD10EZEX-60M (scsi)
Disk /dev/sdb: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system     Name     Flags
 1      1049kB  5243kB  4194kB                           bios_grub
 2      5243kB  9132MB  9127MB  linux-swap(v1)
 3      9132MB  41.3GB  32.2GB  ext4
 4      41.3GB  73.6GB  32.2GB  ext4
 5      73.6GB  106GB   32.2GB  ext4
 6      106GB   138GB   32.2GB  ext4            LM18KDE
 7      138GB   578GB   440GB   ext4
 8      578GB   610GB   32.2GB  ext4


NAME   FSTYPE   SIZE PARTTYPE
sda           111.8G 
├─sda1            1M 21686148-6449-6e6f-744e-656564454649
├─sda2 ext4      30G 0fc63daf-8483-4772-8e79-3d69d8477de4
└─sda3 ext4      30G 0fc63daf-8483-4772-8e79-3d69d8477de4
sdb           931.5G 
├─sdb1            4M 21686148-6449-6e6f-744e-656564454649
├─sdb2 swap     8.5G 0657fd6d-a4ab-43c4-84e5-0933c84b4f4f
├─sdb3 ext4      30G 0fc63daf-8483-4772-8e79-3d69d8477de4
├─sdb4 ext4      30G 0fc63daf-8483-4772-8e79-3d69d8477de4
├─sdb5 ext4      30G 0fc63daf-8483-4772-8e79-3d69d8477de4
├─sdb6 ext4      30G 0fc63daf-8483-4772-8e79-3d69d8477de4
├─sdb7 ext4     410G 0fc63daf-8483-4772-8e79-3d69d8477de4
└─sdb8 ext4      30G 0fc63daf-8483-4772-8e79-3d69d8477de4
sr0            1024M 
It appears that there is something wrong with your partition table, if the filesystem types and UUID's are not displayed.
(Although, inxi did display that info. )
Mint 18.2 Cinnamon, Quad core AMD A8-3870 with Radeon HD Graphics 6550D, 8GB DDR3, Ralink RT2561/RT61 802.11g PCI
Linux Linx 2018
User avatar
Moishe
Level 2
Level 2
Posts: 67
Joined: Thu Jun 02, 2016 6:15 am

Re: GRUB 2 does not start from BIOS anymore

Post by Moishe »

austin.texas wrote:
Moishe wrote:This is the full output on my machine:

Code: Select all

$ lsblk -fa /dev/sda
NAME    FSTYPE LABEL MOUNTPOINT
sda                  
├─sda1               
├─sda2               
├─sda3               
├─sda4               /
├─sda5               
├─sda6               
├─sda7               
├─sda8               
├─sda9               
├─sda10              
├─sda11              
├─sda12              
├─sda13              
├─sda14              
└─sda15  
That result is definitely not what I would expect. For comparison, here is my result of the same command:

Code: Select all

~ $ lsblk -fa /dev/sda
NAME   FSTYPE LABEL           UUID                                 MOUNTPOINT
sda                                                                
├─sda1                                                             
├─sda2 ext4   sda2_LM17.3Cinn a09ad702-6248-41ac-a5c6-af105bb55de9 
└─sda3 ext4   sda3_LM18Cinn   4a6b8a6f-ea6b-45f2-84e0-d184310ed3a6 /
(I only have 3 partitions on that drive.)

To see more info, please post the result of this command:

Code: Select all

 sudo parted --list && lsblk -o name,fstype,size,parttype
Here it is:

Code: Select all

~ $  sudo parted --list && lsblk -o name,fstype,size,parttype
Model: ATA WDC WD10EZEX-22B (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number  Start   End     Size    File system     Name                  Flags
 1      1049kB  5243kB  4194kB                                        bios_grub
 2      20.0GB  43.0GB  23.0GB  ext4
 3      43.0GB  84.9GB  41.9GB  ext4
13      84.9GB  116GB   31.6GB  ext4
 4      116GB   137GB   20.7GB  ext4
14      137GB   158GB   21.2GB  ext4
 5      158GB   169GB   10.5GB  ext4
 6      169GB   179GB   10.5GB  ext4
 7      179GB   190GB   10.5GB  ext4
 8      190GB   195GB   5264MB  ext4
 9      195GB   200GB   5222MB  ext4
10      200GB   892GB   691GB   ext4
15      892GB   992GB   101GB   ext4
11      992GB   1000GB  7612MB  linux-swap(v1)  Basic data partition
12      1000GB  1000GB  243MB   ext4            UEFI Boot


Model: Generic- SD/MMC (scsi)
Disk /dev/sdb: 126MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End    Size   Type     File system  Flags
 1      1049kB  126MB  125MB  primary  fat32        boot, lba


lsblk: unknown column: parttype

Again important entries are missing in this output and I DID NOT REMOVE ANYTHING.

Why does it say the Name: "UEFI Boot" for position 12 ???
Who gave it this name?
There is no such a label or flag anymore (Gparted does not show any label of flag as they were removed).
Maybe I should remove this partition completely?
Have a wonderful day!
"If you're not having fun, you're doing it wrong" - Groucho Marx
User avatar
Moishe
Level 2
Level 2
Posts: 67
Joined: Thu Jun 02, 2016 6:15 am

Re: GRUB 2 does not start from BIOS anymore

Post by Moishe »

Running

Code: Select all

lsblk -fa /dev/sda
as root (sudo) gives more info but still not all that you suggested we should expect:

Code: Select all


~ $ sudo lsblk -fa /dev/sda
NAME    FSTYPE LABEL         MOUNTPOINT
sda                          
├─sda1                       
├─sda2  ext4   Mint Mate     
├─sda3  ext4   Mint KDE      
├─sda4  ext4   Mint Cinnamon /
├─sda5  ext4   Porteus KDE   
├─sda6  ext4   Porteus Mate  
├─sda7  ext4   Porteus       
├─sda8  ext4   Pup Slacko    
├─sda9  ext4   Pup Tahr      
├─sda10 ext4   DATA          
├─sda11 swap                 
├─sda12 ext4                 
├─sda13 ext4   Ready4OS      
├─sda14 ext4   Elementary OS 
└─sda15 ext4   Ubuntu    

Have a wonderful day!
"If you're not having fun, you're doing it wrong" - Groucho Marx
User avatar
Moishe
Level 2
Level 2
Posts: 67
Joined: Thu Jun 02, 2016 6:15 am

Re: GRUB 2 does not start from BIOS anymore

Post by Moishe »

gold_finger wrote:
Moishe wrote:When CSM is not AUTO there are four options for various H/W
For each H/W the options are like Legacy first, only Legacy, or something else or only something else
Tested various options with Legacy a few a few times in the past and it did not help
But can test it again shortly too
Try "only Legacy" if possible.


Side Note: When posting back requested terminal output, please post full output and enclose it in "code" tags as per instructions shown here. The output from your lsblk -fa /dev/sda command was missing information we needed to see (file system type for each partition, partition UUID's, etc.). Doesn't matter now because austin.texas had you run a different command showing UUID's later on to confirm whether they matched what was shown in fstab file; so keep that in mind for future postings.


I don't think having wrong Swap partition UUID would prevent booting, but you might as well fix that. Just boot into the controlling OS and edit the fstab file with your text editor as root and replace wrong UUID with the right one. I don't remember if you told us which OS you're using as the boot controlling one, but if it's Mint 18 (non-KDE), the text editor in command will be "xed". If not Mint 18 it could be "gedit", "pluma", "leafpad", or "kate" (in KDE). If not sure what yours is just open it and go to Help -> About to find out, then use that in the command below in place of "xed".

To open the fstab file with your GUI-based text editor as root, enter the following command:

Code: Select all

gksu xed /etc/fstab
If using a KDE-based distro, the command would be:

Code: Select all

kdesudo kate /etc/fstab
If for some reason you can't figure out what graphical text editor you have, just about all distros include the terminal-based "nano" text editor and you can open the file with that using this command:

Code: Select all

sudo nano /etc/fstab
Find the line for Swap partition and change the UUID to the correct one. Save the file, close the text editor. Reboot computer and maybe we'll all be shocked and it'll boot properly. (I doubt it will actually solve the problem, but who knows?)

If computer still won't boot properly after setting boot mode to Legacy only and also fixing the Swap UUID, I'd have to say I'm completely stumped. Your situation is pretty bizarre. I don't recall seeing anyone else on the forum having this problem and I've never run into anything like this myself.

P.s.
Did you check to see if there is a UEFI/(Bios) update available for your computer/motherboard? Maybe the original is particularly flaky and there has been an update that will fix the problem.
boot mode to Legacy only: DONE
Swap UUID: FIXED
BIOS: updated

computer still won't boot properly... :-(
Have a wonderful day!
"If you're not having fun, you're doing it wrong" - Groucho Marx
User avatar
Moishe
Level 2
Level 2
Posts: 67
Joined: Thu Jun 02, 2016 6:15 am

Re: GRUB 2 does not start from BIOS anymore

Post by Moishe »

austin.texas wrote:
Moishe wrote:This is the full output on my machine:

Code: Select all

$ lsblk -fa /dev/sda
NAME    FSTYPE LABEL MOUNTPOINT
sda                  
├─sda1               
├─sda2               
├─sda3               
├─sda4               /
├─sda5               
├─sda6               
├─sda7               
├─sda8               
├─sda9               
├─sda10              
├─sda11              
├─sda12              
├─sda13              
├─sda14              
└─sda15  
That result is definitely not what I would expect. For comparison, here is my result of the same command:

Code: Select all

~ $ lsblk -fa /dev/sda
NAME   FSTYPE LABEL           UUID                                 MOUNTPOINT
sda                                                                
├─sda1                                                             
├─sda2 ext4   sda2_LM17.3Cinn a09ad702-6248-41ac-a5c6-af105bb55de9 
└─sda3 ext4   sda3_LM18Cinn   4a6b8a6f-ea6b-45f2-84e0-d184310ed3a6 /
(I only have 3 partitions on that drive.)

To see more info, please post the result of this command:

Code: Select all

 sudo parted --list && lsblk -o name,fstype,size,parttype
The results should resemble this (mine):

Code: Select all

 ~ $  sudo parted --list && lsblk -o name,fstype,size,parttype
Model: ATA SPCC Solid State (scsi)
Disk /dev/sda: 120GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name  Flags
 1      1049kB  2097kB  1049kB                     bios_grub
 2      2097kB  32.2GB  32.2GB  ext4
 3      32.2GB  64.4GB  32.2GB  ext4


Model: ATA WDC WD10EZEX-60M (scsi)
Disk /dev/sdb: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system     Name     Flags
 1      1049kB  5243kB  4194kB                           bios_grub
 2      5243kB  9132MB  9127MB  linux-swap(v1)
 3      9132MB  41.3GB  32.2GB  ext4
 4      41.3GB  73.6GB  32.2GB  ext4
 5      73.6GB  106GB   32.2GB  ext4
 6      106GB   138GB   32.2GB  ext4            LM18KDE
 7      138GB   578GB   440GB   ext4
 8      578GB   610GB   32.2GB  ext4


NAME   FSTYPE   SIZE PARTTYPE
sda           111.8G 
├─sda1            1M 21686148-6449-6e6f-744e-656564454649
├─sda2 ext4      30G 0fc63daf-8483-4772-8e79-3d69d8477de4
└─sda3 ext4      30G 0fc63daf-8483-4772-8e79-3d69d8477de4
sdb           931.5G 
├─sdb1            4M 21686148-6449-6e6f-744e-656564454649
├─sdb2 swap     8.5G 0657fd6d-a4ab-43c4-84e5-0933c84b4f4f
├─sdb3 ext4      30G 0fc63daf-8483-4772-8e79-3d69d8477de4
├─sdb4 ext4      30G 0fc63daf-8483-4772-8e79-3d69d8477de4
├─sdb5 ext4      30G 0fc63daf-8483-4772-8e79-3d69d8477de4
├─sdb6 ext4      30G 0fc63daf-8483-4772-8e79-3d69d8477de4
├─sdb7 ext4     410G 0fc63daf-8483-4772-8e79-3d69d8477de4
└─sdb8 ext4      30G 0fc63daf-8483-4772-8e79-3d69d8477de4
sr0            1024M 
It appears that there is something wrong with your partition table, if the filesystem types and UUID's are not displayed.
(Although, inxi did display that info. )
There is something wrong with my partition table?
Could be...
How to fix it?
Have a wonderful day!
"If you're not having fun, you're doing it wrong" - Groucho Marx
User avatar
austin.texas
Level 20
Level 20
Posts: 12046
Joined: Tue Nov 17, 2009 3:57 pm
Location: at /home

Re: GRUB 2 does not start from BIOS anymore

Post by austin.texas »

It does not really seem that it is a problem with the partition table.
One reason I say that is because of the result of lsblk -o name,fstype,size,parttype that you posted.
You got:
lsblk: unknown column: parttype
That just means that you are not using Mint 18 when you run that command. Do you have Mint 18 installed?
Mint 18.2 Cinnamon, Quad core AMD A8-3870 with Radeon HD Graphics 6550D, 8GB DDR3, Ralink RT2561/RT61 802.11g PCI
Linux Linx 2018
User avatar
gold_finger
Level 9
Level 9
Posts: 2885
Joined: Mon Mar 11, 2013 11:39 pm

Re: GRUB 2 does not start from BIOS anymore

Post by gold_finger »

@austin.texas,

Just thought of something. I no longer have a test system using GPT & Legacy boot so can't confirm answer to the following. Could you check your system and see if the fstab file is using GUID's instead of UUID's? If yes, do you happen to know if it's required to use GUID's instead of UUID's in the fstab file when doing Legacy boots on GPT drives? (Probably just another hopeless shot in the dark, but maybe that's the problem.)

Am bringing that up because I noticed that your output posted for lsblk -fa /dev/sda showed UUID's, but your output from lsblk -o name,fstype,size,parttype shows different ID #'s for the /dev/sda drive, so I'm assuming those are GUID's.

If it does turn out that GUID's may be needed, can OP run sudo blkid -c /dev/null to get a listing of the GUID's in place of the lsblk -o name,fstype,size,parttype command that currently doesn't list them on his/her computer? (Does blkid command give you GUID's or UUID's?)


@Moishe,
Moishe wrote:Why does it say the Name: "UEFI Boot" for position 12 ???
Who gave it this name?
There is no such a label or flag anymore (Gparted does not show any label of flag as they were removed).
Maybe I should remove this partition completely?
Don't know how it got named that, but don't think that should affect anything. In any event it won't hurt anything deleting that partition -- it's not being used for anything now anyway. Delete it if you want to.
Please add [SOLVED] to your thread if a solution is found. Go to your first post in the thread, hit "Edit" button and add [SOLVED] to the title of the post.

How To Format Your Forum Posts.

Try Linux Beginner Search Engine for Linux questions.
User avatar
austin.texas
Level 20
Level 20
Posts: 12046
Joined: Tue Nov 17, 2009 3:57 pm
Location: at /home

Re: GRUB 2 does not start from BIOS anymore

Post by austin.texas »

gold_finger wrote:@austin.texas,
Just thought of something. I no longer have a test system using GPT & Legacy boot so can't confirm answer to the following. Could you check your system and see if the fstab file is using GUID's instead of UUID's? If yes, do you happen to know if it's required to use GUID's instead of UUID's in the fstab file when doing Legacy boots on GPT drives?
My fstab uses UUID's. I have never seen one using GUID's.
The parttype column is not a unique partition identifier - it only reflects the partition type.
You will notice that all my / partitions have the same parttype number, and both my bios_grub partitions have the same parttype number.
Mint 18.2 Cinnamon, Quad core AMD A8-3870 with Radeon HD Graphics 6550D, 8GB DDR3, Ralink RT2561/RT61 802.11g PCI
Linux Linx 2018
User avatar
gold_finger
Level 9
Level 9
Posts: 2885
Joined: Mon Mar 11, 2013 11:39 pm

Re: GRUB 2 does not start from BIOS anymore

Post by gold_finger »

Oh well -- was grasping at straws again. I'm completely stumped at this point -- no idea why computer won't boot properly.
Please add [SOLVED] to your thread if a solution is found. Go to your first post in the thread, hit "Edit" button and add [SOLVED] to the title of the post.

How To Format Your Forum Posts.

Try Linux Beginner Search Engine for Linux questions.
grizzler
Level 5
Level 5
Posts: 652
Joined: Wed Jun 15, 2011 5:19 pm
Location: The Hague, NL

Re: GRUB 2 does not start from BIOS anymore

Post by grizzler »

Join the club. I admire your perseverance. I gave up already.

I stand by what I wrote in my previous posting: this firmware is broken. It simply can't handle legacy booting with a GPT disk.

I did a bit of searching with the name of the motherboard before I wrote that posting and found several forum threads (on other sites) about similar issues. Most people seemed to have 'solved' the problem by switching the disk to an MBR setup and I remember reading about a FreeBSD install that started working after they marked the managing partition as active (i.e. set the boot flag). Has that been tried with this particular disk? The boot flag has been set on other partitions, but not on the one controlling the boot process, if I remember correctly.
User avatar
gold_finger
Level 9
Level 9
Posts: 2885
Joined: Mon Mar 11, 2013 11:39 pm

Re: GRUB 2 does not start from BIOS anymore

Post by gold_finger »

grizzler wrote:I stand by what I wrote in my previous posting: this firmware is broken. It simply can't handle legacy booting with a GPT disk.
You're probably right -- nothing else makes sense.
grizzler wrote:I remember reading about a FreeBSD install that started working after they marked the managing partition as active (i.e. set the boot flag). Has that been tried with this particular disk? The boot flag has been set on other partitions, but not on the one controlling the boot process, if I remember correctly.
No, that hasn't been tried.


@Moishe,

Go ahead and try setting boot flag on root partition of controlling distro as suggested by grizzler. (You'll probably need to do that from either a live dvd/usb or while booted into a different distro because I don't think GParted will let you do that when the partition is in use.)
Please add [SOLVED] to your thread if a solution is found. Go to your first post in the thread, hit "Edit" button and add [SOLVED] to the title of the post.

How To Format Your Forum Posts.

Try Linux Beginner Search Engine for Linux questions.
User avatar
Moishe
Level 2
Level 2
Posts: 67
Joined: Thu Jun 02, 2016 6:15 am

Re: GRUB 2 does not start from BIOS anymore

Post by Moishe »

gold_finger wrote:
@Moishe,

Go ahead and try setting boot flag on root partition of controlling distro as suggested by grizzler. (You'll probably need to do that from either a live dvd/usb or while booted into a different distro because I don't think GParted will let you do that when the partition is in use.)
Do you suggest boot, legacy_boot or bios_grub flag on this partition?
Remove other flags?
Have a wonderful day!
"If you're not having fun, you're doing it wrong" - Groucho Marx
User avatar
gold_finger
Level 9
Level 9
Posts: 2885
Joined: Mon Mar 11, 2013 11:39 pm

Re: GRUB 2 does not start from BIOS anymore

Post by gold_finger »

Try "boot" first. If no effect, change to "legacy_boot". (Don't use "bios_grub" for that partition.)

Honestly, I don't expect setting either of those boot flags to make any difference, but won't hurt anything to try. If neither of the two make any difference just revert partition back to having no flags again when done testing.
Please add [SOLVED] to your thread if a solution is found. Go to your first post in the thread, hit "Edit" button and add [SOLVED] to the title of the post.

How To Format Your Forum Posts.

Try Linux Beginner Search Engine for Linux questions.
User avatar
Moishe
Level 2
Level 2
Posts: 67
Joined: Thu Jun 02, 2016 6:15 am

Re: GRUB 2 does not start from BIOS anymore

Post by Moishe »

gold_finger wrote:Try "boot" first. If no effect, change to "legacy_boot". (Don't use "bios_grub" for that partition.)

Honestly, I don't expect setting either of those boot flags to make any difference, but won't hurt anything to try. If neither of the two make any difference just revert partition back to having no flags again when done testing.
This also did not help.
Maybe this is true that my firmware has poor or no support for Legacy boot from GPT

But we did not talk about the flowing option:
Booting Linux from GPT disks on UEFI systems involves creation of an EFI System partition (ESP), which contains UEFI applications such as bootloaders, operating system kernels, and utility software.[31][32][33] Such a setup is usually referred to as UEFI-GPT, while ESP is recommended to be at least 512 MiB in size and formatted with a FAT32 filesystem for maximum compatibility.

BTW, any possibility to boot from USB flash partition from HDD automatically?
Have a wonderful day!
"If you're not having fun, you're doing it wrong" - Groucho Marx
User avatar
austin.texas
Level 20
Level 20
Posts: 12046
Joined: Tue Nov 17, 2009 3:57 pm
Location: at /home

Re: GRUB 2 does not start from BIOS anymore

Post by austin.texas »

Moishe wrote:But we did not talk about the flowing option:
Booting Linux from GPT disks on UEFI systems involves creation of an EFI System partition (ESP), which contains UEFI applications such as bootloaders, operating system kernels, and utility software.[31][32][33] Such a setup is usually referred to as UEFI-GPT, while ESP is recommended to be at least 512 MiB in size and formatted with a FAT32 filesystem for maximum compatibility.
That describes a UEFI installation. A Legacy installation works differently.
Moishe wrote:BTW, any possibility to boot from USB flash partition from HDD automatically?
Yes, it is possible.
If you boot into your installed Mint on the hard drive you can install the bootloader to the internal hard drive, and you can also install the bootloader to any other drive.
For example, if my internal hard drive is /dev/sda, and my flash drive is /dev/sdb, I can install Grub to /dev/sdb and boot the flash drive. That will give me the Grub menu, and allow me to boot the Mint on the hard drive.
The command to install Grub to the flash drive (sdb) is:

Code: Select all

sudo grub-install /dev/sdb
In fact, I have done exactly that with my USB flash drive which holds 1200 music files. I installed Grub to that USB drive, so the USB drive that I use in the car for music also can boot my Mint on my hard drive. :D
Mint 18.2 Cinnamon, Quad core AMD A8-3870 with Radeon HD Graphics 6550D, 8GB DDR3, Ralink RT2561/RT61 802.11g PCI
Linux Linx 2018
User avatar
Moishe
Level 2
Level 2
Posts: 67
Joined: Thu Jun 02, 2016 6:15 am

Re: GRUB 2 does not start from BIOS anymore

Post by Moishe »

austin.texas wrote:
Moishe wrote:BTW, any possibility to boot from USB flash partition from HDD automatically?
Yes, it is possible.
If you boot into your installed Mint on the hard drive you can install the bootloader to the internal hard drive, and you can also install the bootloader to any other drive.
For example, if my internal hard drive is /dev/sda, and my flash drive is /dev/sdb, I can install Grub to /dev/sdb and boot the flash drive. That will give me the Grub menu, and allow me to boot the Mint on the hard drive.
The command to install Grub to the flash drive (sdb) is:

Code: Select all

sudo grub-install /dev/sdb
In fact, I have done exactly that with my USB flash drive which holds 1200 music files. I installed Grub to that USB drive, so the USB drive that I use in the car for music also can boot my Mint on my hard drive. :D
It works - thanks!
This is a perfect workaround for UEFI-GPT issues!
What is needed is just USB flash with fat 32
No special partition or flags for USB flash are needed.
Have a wonderful day!
"If you're not having fun, you're doing it wrong" - Groucho Marx
User avatar
austin.texas
Level 20
Level 20
Posts: 12046
Joined: Tue Nov 17, 2009 3:57 pm
Location: at /home

Re: GRUB 2 does not start from BIOS anymore

Post by austin.texas »

I am glad it works for you.
Please note that when you install Grub to the MBR of your flash drive it points to (and reads) the grub.cfg on your hard drive. Specifically, the grub.cfg of the operating system where you ran the command sudo grub-install /dev/sdb. That is the controlling OS. If you remove that OS, your boot will fail (because the grub.cfg will not exist).
Mint 18.2 Cinnamon, Quad core AMD A8-3870 with Radeon HD Graphics 6550D, 8GB DDR3, Ralink RT2561/RT61 802.11g PCI
Linux Linx 2018
markfilipak
Level 5
Level 5
Posts: 979
Joined: Sun Mar 10, 2013 8:08 pm

Re: GRUB 2 does not start from BIOS anymore

Post by markfilipak »

Moishe wrote:SYSLINUX boots from USB...
To Moishe.

Your problems seem very much like my problems, just different symptoms -- you're in the 'weeds', but you took a different 'path' to get there.

Is your 'BIOS' setup screen (F2) titled "Phoenix SecureCore Tiano Setup"?

I'm suspecting that we both need to reflash our firmware.
I'm suspecting that we both need to correspond with Phoenix.
I'm suspecting that Mint 18 has corrupted the firmware.

To everyone:
Is there a way to read and save a raw dump of the firmware to compare with known-good firmware?
Is there a way to boot and save a log so that it can be analyzed?

PS: I guess I'm revealing that I'm a hardware engineer. My solution to the problem in this thread, and to the many similar problems I find on the net is to fix, not the installation, but the UEFI. Simply put, the Phoenix 'BIOS' product is defective, but try to get help from them. And when I go to Lenovo -- my laptop is a Lenovo -- the first thing I see is "Your computer is out of warranty" with an offer to sell me an extended warranty. The same happens when I phone Lenovo. So, I guess that working around the lame Phoenix 'BIOS' is the way to go.
Post Reply

Return to “Installation & Boot”