help-grub
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: If two drives are marked bootable what happens?


From: Michael D. Setzer II
Subject: Re: If two drives are marked bootable what happens?
Date: Sat, 03 Apr 2021 23:31:28 +1000

One quick question? Is the boot up process using the 
device locations or uuid process.

Usually, the blkid uuid is different for each drive, but if 
one copied disks they can have the same ids, so that it 
can throw off the boot process. Maintain the the G4L disk 
imaging process, so noticed this as a problem if having 
two cloned disk in the same machine at boot time. 

So, might want to validate the blkids are different.


On 3 Apr 2021 at 12:39, Steve wrote:

From:                   Steve <steve@easy2boot.com>
Date sent:              Sat, 3 Apr 2021 12:39:55 +0100
Subject:                Re: If two drives are marked bootable what 
happens?
To:                     help-grub@gnu.org

> Disk boot order is set in the BIOS?
> 
> On Sat, 3 Apr 2021 at 12:31, Chris Green <cl@isbd.net> wrote:
> 
> > A friend has been having trouble with a SATA SSD that his system won't
> > recognise so I have been playing with it a bit to see if I can work
> > out what the problem is.
> >
> > This question isn't really related to the above problem.  I plugged
> > the SATA SSD into a system of mine which happens to have an eSATA
> > connector and 'fdisk -l' then shows:-
> >
> >     Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
> >     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: 0xff18eec4
> >
> >     Device     Boot     Start       End   Sectors   Size Id Type
> >     /dev/sda1  *           63 964189169 964189107 459.8G 83 Linux
> >     /dev/sda2       964189170 976768064  12578895     6G  5 Extended
> >     /dev/sda5       964189233 976768064  12578832     6G 82 Linux swap /
> > Solaris
> >
> >
> >     Disk /dev/sdb: 149.1 GiB, 160041885696 bytes, 312581808 sectors
> >     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: 0xfa947ad3
> >
> >     Device     Boot Start       End   Sectors   Size Id Type
> >     /dev/sdb1  *     2048 312580095 312578048 149.1G 83 Linux
> >
> >
> > The system has booted from /dev/sda1 (its internal disk drive), why does
> > it
> > choose to boot from this drive rather than /dev/sda1 since both are marked
> > bootable?
> >
> > --
> > Chris Green
> >
> >


+------------------------------------------------------------+
 Michael D. Setzer II - Computer Science Instructor 
(Retired)     
 mailto:mikes@guam.net                            
 mailto:msetzerii@gmail.com
 Guam - Where America's Day Begins                        
 G4L Disk Imaging Project maintainer 
 http://sourceforge.net/projects/g4l/
+------------------------------------------------------------+






reply via email to

[Prev in Thread] Current Thread [Next in Thread]