Re: [lfs-support] boot partition advice

[Trent]

On 10/23/19 3:12 PM, Bruce Dubbs wrote:

On 10/23/19 3:08 PM, Trent wrote:

Hello all,

After something like 10 tries on building version 9.0 with having 
endless partition issues, and with all your help, I was finally able 
to get it booting into a command line.


What was the final solution?

  -- Bruce

As the advice mentioned, make two partitions, one unformatted, and the 
other for the build.


I then ran the "grub-install /dev/sdX --target i386-pc" and it took it.

I may go back and try that troublesome SSD (Taiwan HyperX brand) which 
required bios_grub.


Trent


--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] boot partition advice

[Bruce Dubbs]

On 10/23/19 3:08 PM, Trent wrote:

Hello all,

After something like 10 tries on building version 9.0 with having 
endless partition issues, and with all your help, I was finally able to 
get it booting into a command line.


What was the final solution?

  -- Bruce

--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] boot partition advice

[Trent]

Hello all,

After something like 10 tries on building version 9.0 with having 
endless partition issues, and with all your help, I was finally able to 
get it booting into a command line.


Now on to BLFS!

Thanks again!


Trent
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] boot partition advice

[Trent]

On 10/23/19 1:57 PM, Ed Batalha wrote:

Trent wrote:



On 10/19/19 11:38 AM, Pierre Labastie wrote:



On 19/10/2019 17:07, Trent wrote:



On 10/17/19 6:26 AM, hazel debian wrote:




You should not mount the "BIOS boot" partition at /boot or 
anywhere else. In fact you don't even need to have a filesystem on 
it.  GRUB installs its second part on that empty partition, and 
the first part (which is in the dummy MBR) should locate it by its 
physical address.


I think you may be confusing this with the "boot partition" 
mentioned in the book, which is actually something quite 
different. It is a normal partition with a filesystem on it that 
is used to contain kernels when you are multibooting LFS with 
other Linuxes.  The team recommend having this common boot 
partition for all your systems and mounting it on /boot in each of 
them.




I  finished the rebuild on a single partition, with the "bios_grub" 
flag set.




Hmm, it's not what Hazel has written. On a GPT partition system,
you need at least two partitions (OK not mandatory, but easiest): 
one which is the "bios boot"
(flag bios_grub in parted), which can be very small (1MB), and 
another one for the system.
Of course, you may have more partitions if you want separate 
partitions for /boot, /home, or /usr.
Do not format the "bios boot" partition, do not try to mount it. 
Mount the second partition on /mnt/lfs instead. Build your system on 
it, then you can install grub.


Pierre



Okay, I am already back on this again. I rebuilt the system again on 
that branded SSD I mentioned I would try this time. I ran into an odd 
problem during grub-install so I decided to rebuild again. The 
rebuild is about halfway done.


On the first try for this SSD, I put only one partition on it of type 
ext4.


When I ran "grub-install /dev/sdX --target i386-pc" it came back with 
"grub does not support ext2."


Wow.

Rather than spend time on trying to figure that out, I went ahead and 
cleared the drive out, then made two partitions.


/dev/sdX1 Unformated

"One quirk is that this magic “32kb gap” between sector 1 and the 
first partition that is created /by convention/ for msdos-partitioned 
disks does not exist in GPT. The solution is to create a specific 
partition to hold the “embedded” copy of core.img; this partition must 
have type |BIOS_BOOT|. The “grub-setup” utility (called by 
grub-install) searches the GPT for the first partition of that type 
and writes core.img there."


"For GPT (recommended), you need something like:

Number  Start (sector)    End (sector)  Size   Code  Name
   1    2048    4095   1024.0 KiB  EF02  grub
   2    4096 1052671   512.0 MiB   8300  boot
   3 1052672    39456767   18.3 GiB    8300  debian
   4    39456768    60428287   10.0 GiB    8200  Linux swap
   5   429604864   468666367   18.6 GiB    8300 lfs-20190801
   ...
  14   307765248   370679807   30.0 GiB    8300  lfs-9.0 "

The fist, unformatted partition needs to be type BIOS_BOOT, which is 
code EF02 in Bruce's printout.



/dev/sdX2 ext

I am building now on /dev/sdX2.

With that, that is one thing not specifically clear. Do I run the 
grub-install command for /dev/sdX, or for the unformatted partition 
of  /dev/sdX1?



For /dev/sdX



Thanks again!

Trent


I don't have GPT on my computers so I'm writing this based only on 
what I've read previously about this subject.


Regards,
Ed



Thanks a bunch, Ed!


I was reading the URL you sent over on grub.

http://moi.vonos.net/linux/Booting_Linux_on_x86_with_Grub2/#installing-grub

It does mention, "The Grub utilities provide a command “grub-install” 
which creates the files in |/boot/grub| and writes a program to a disk’s 
Master Boot Record (MBR)."


I just wanted to be sure I am clear on it.


Trent



-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] boot partition advice

[Ed Batalha]

Trent wrote:



On 10/19/19 11:38 AM, Pierre Labastie wrote:



On 19/10/2019 17:07, Trent wrote:



On 10/17/19 6:26 AM, hazel debian wrote:




You should not mount the "BIOS boot" partition at /boot or anywhere 
else. In fact you don't even need to have a filesystem on it.  GRUB 
installs its second part on that empty partition, and the first 
part (which is in the dummy MBR) should locate it by its physical 
address.


I think you may be confusing this with the "boot partition" 
mentioned in the book, which is actually something quite different. 
It is a normal partition with a filesystem on it that is used to 
contain kernels when you are multibooting LFS with other Linuxes.  
The team recommend having this common boot partition for all your 
systems and mounting it on /boot in each of them.




I  finished the rebuild on a single partition, with the "bios_grub" 
flag set.




Hmm, it's not what Hazel has written. On a GPT partition system,
you need at least two partitions (OK not mandatory, but easiest): one 
which is the "bios boot"
(flag bios_grub in parted), which can be very small (1MB), and 
another one for the system.
Of course, you may have more partitions if you want separate 
partitions for /boot, /home, or /usr.
Do not format the "bios boot" partition, do not try to mount it. 
Mount the second partition on /mnt/lfs instead. Build your system on 
it, then you can install grub.


Pierre



Okay, I am already back on this again. I rebuilt the system again on 
that branded SSD I mentioned I would try this time. I ran into an odd 
problem during grub-install so I decided to rebuild again. The rebuild 
is about halfway done.


On the first try for this SSD, I put only one partition on it of type 
ext4.


When I ran "grub-install /dev/sdX --target i386-pc" it came back with 
"grub does not support ext2."


Wow.

Rather than spend time on trying to figure that out, I went ahead and 
cleared the drive out, then made two partitions.


/dev/sdX1 Unformated

"One quirk is that this magic “32kb gap” between sector 1 and the first 
partition that is created /by convention/ for msdos-partitioned disks 
does not exist in GPT. The solution is to create a specific partition to 
hold the “embedded” copy of core.img; this partition must have type 
|BIOS_BOOT|. The “grub-setup” utility (called by grub-install) searches 
the GPT for the first partition of that type and writes core.img there."


"For GPT (recommended), you need something like:

Number  Start (sector)End (sector)  Size   Code  Name
   120484095   1024.0 KiB  EF02  grub
   24096 1052671   512.0 MiB   8300  boot
   3 105267239456767   18.3 GiB8300  debian
   43945676860428287   10.0 GiB8200  Linux swap
   5   429604864   468666367   18.6 GiB8300 lfs-20190801
   ...
  14   307765248   370679807   30.0 GiB8300  lfs-9.0 "

The fist, unformatted partition needs to be type BIOS_BOOT, which is 
code EF02 in Bruce's printout.



/dev/sdX2 ext

I am building now on /dev/sdX2.

With that, that is one thing not specifically clear. Do I run the 
grub-install command for /dev/sdX, or for the unformatted partition 
of  /dev/sdX1?



For /dev/sdX



Thanks again!

Trent


I don't have GPT on my computers so I'm writing this based only on what 
I've read previously about this subject.


Regards,
Ed
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] boot partition advice

[Bruce Dubbs]

On 10/20/19 10:26 AM, Pierre Labastie wrote:



On 19/10/2019 22:10, Bruce Dubbs wrote:

On 10/19/19 12:13 PM, Pierre Labastie wrote:


Actually, I do not have a separate boot partition anymore. Usually,
I have one major distro + one or more LFS on my systems. I use
the /boot/grub/grub.cfg of the distro to boot everything, and even,
I now use "update-grub"  to update the config for the lfs systems.
It generates a pretty correct config _if_ I have a /boot/grub/grub.cfg
file on each lfs partition for the corresponding lfs system. That works
pretty well with debian ubuntu suse (not tried fedora).


The problem with that is knowing which grub.conf to change.  Which 
partition is the grub using for booting?  If you want to edit it to 
change, for instance, a kernel command line option,  how do you do that?


Let's take an example: on one of my systems:
/dev/sda1: debian
/dev/sda2: swap
/dev/sda3: /home

/dev/sdb1: lfs1
/dev/sdb2: lfs2
/dev/sdb3: lfs3

Each of those lfs has a /boot partition. On lfs1, create 
/boot/grub/grub.cfg:


|set root=(hd1,1) menuentry "GNU/Linux, Linux 5.2.8-lfs-SVN-20190815" { 
linux /boot/vmlinuz-5.2.8-lfs-SVN-20190815 root=/dev/sdb1 ro initrd 
/boot/microcode.img } On lfs2, create /boot/grub/grub.cfg with: ||set root=(hd1,2) menuentry "GNU/Linux, Linux 5.2.8-lfs-SVN-20190815" { 
linux /boot/vmlinuz-5.2.8-lfs-SVN-20190815 root=/dev/sdb2 ro initrd 
/boot/microcode.img } and same (changing the appropriate entries) for 
lfs3 Then, on debian, run "update-grub". The lines "linux ..." and 
"initrd ..." from each lfs are copied into debian's grub.cfg. Note that 
there is no need to run grub-install, since debian had already done it. 
All in all, it is much easier than manually maintaining a grub.cfg for 
all the distros on the disks. And there are functions which allow to 
choose which system will be booted when rebooting (using grub-editenv)... |||




grub-mkconfig is terribly verbose.  For a new install of debian, with 
only one distro, grub.conf is 197 lines.  I can build LFS and have a 
dual boot system in about 15 lines.   There is MUCH more flexibility 
with a single boot partition.


Except that when debian updates its kernel, it runs update-grub, which 
ruins the existing grub.cfg. With the method
I propose, the lfs systems are still available after an update... With 
your method, you need a copy of
grub.cfg, and to merge it with the one generated by debian after the 
update...



That's true.  You do need a backup because distros run grub-mkconfig and 
make something simple into a horrible mess.


The merge should only add about 3-4 lines.

  -- Bruce

--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] boot partition advice

[Pierre Labastie]

On 19/10/2019 22:10, Bruce Dubbs wrote:

On 10/19/19 12:13 PM, Pierre Labastie wrote:


Actually, I do not have a separate boot partition anymore. Usually,
I have one major distro + one or more LFS on my systems. I use
the /boot/grub/grub.cfg of the distro to boot everything, and even,
I now use "update-grub"  to update the config for the lfs systems.
It generates a pretty correct config _if_ I have a /boot/grub/grub.cfg
file on each lfs partition for the corresponding lfs system. That works
pretty well with debian ubuntu suse (not tried fedora).


The problem with that is knowing which grub.conf to change.  Which 
partition is the grub using for booting?  If you want to edit it to 
change, for instance, a kernel command line option,  how do you do that?


Let's take an example: on one of my systems:
/dev/sda1: debian
/dev/sda2: swap
/dev/sda3: /home

/dev/sdb1: lfs1
/dev/sdb2: lfs2
/dev/sdb3: lfs3

Each of those lfs has a /boot partition. On lfs1, create 
/boot/grub/grub.cfg:


|set root=(hd1,1) menuentry "GNU/Linux, Linux 5.2.8-lfs-SVN-20190815" { 
linux /boot/vmlinuz-5.2.8-lfs-SVN-20190815 root=/dev/sdb1 ro initrd 
/boot/microcode.img } On lfs2, create /boot/grub/grub.cfg with: ||set root=(hd1,2) menuentry "GNU/Linux, Linux 5.2.8-lfs-SVN-20190815" { 
linux /boot/vmlinuz-5.2.8-lfs-SVN-20190815 root=/dev/sdb2 ro initrd 
/boot/microcode.img } and same (changing the appropriate entries) for 
lfs3 Then, on debian, run "update-grub". The lines "linux ..." and 
"initrd ..." from each lfs are copied into debian's grub.cfg. Note that 
there is no need to run grub-install, since debian had already done it. 
All in all, it is much easier than manually maintaining a grub.cfg for 
all the distros on the disks. And there are functions which allow to 
choose which system will be booted when rebooting (using grub-editenv)... |||




grub-mkconfig is terribly verbose.  For a new install of debian, with 
only one distro, grub.conf is 197 lines.  I can build LFS and have a 
dual boot system in about 15 lines.   There is MUCH more flexibility 
with a single boot partition.


Except that when debian updates its kernel, it runs update-grub, which 
ruins the existing grub.cfg. With the method
I propose, the lfs systems are still available after an update... With 
your method, you need a copy of
grub.cfg, and to merge it with the one generated by debian after the 
update...




For GPT (recommended), you need something like:

Number  Start (sector)    End (sector)  Size   Code Name
   1    2048    4095   1024.0 KiB  EF02 grub
   2    4096 1052671   512.0 MiB   8300 boot
   3 1052672    39456767   18.3 GiB    8300 debian
   4    39456768    60428287   10.0 GiB    8200 Linux swap
   5   429604864   468666367   18.6 GiB    8300 lfs-20190801
   ...
  14   307765248   370679807   30.0 GiB    8300 lfs-9.0


grub should always be 1 MiB
boot can be smaller than 512 MiB, but I suggest no smaller than 100 MiB.
swap is actually optional but I recommend at least 2 GiB
For the LFS partition, 30 GiB gives enough room to build all of BLFS, 
but can be much smaller.  Currently I don't recommend anything less 
than 10 GiB.


My grub.cfg is fairly easy to understand:

# Begin /boot/grub/grub.cfg
set default=1
set timeout=5

insmod ext2
set root=(hd0,2)

menuentry "Linux 4.18.5 (lfs-SVN-20180902) /dev/sda7" {
    linux /vmlinuz-4.18.5-lfs-SVN-20180902 root=/dev/sda7 ro 
consoleblank=120

    initrd /microcode.img
}

menuentry "Linux 4.20.0 (lfs-8.4) /dev/sda13" {
    linux /vmlinuz-4.20.8-lfs-SVN-20190214 root=/dev/sda13 ro 
consoleblank=120

    initrd /microcode.img
}

...
11 more entries.


On another system, a commercial distro entry looks like:

menuentry 'Linux Mint 17.2 Xfce 64-bit' {
   insmod gzio
   linux /vmlinuz-3.16.0-38-generic 
root=UUID=3b35b7db-f76b-4a32-baa7-814538d95ee1 ro

   initrd   /initrd.img-3.16.0-38-generic
}

  -- Bruce




-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] boot partition advice

[Bruce Dubbs]

On 10/19/19 12:13 PM, Pierre Labastie wrote:


Actually, I do not have a separate boot partition anymore. Usually,
I have one major distro + one or more LFS on my systems. I use
the /boot/grub/grub.cfg of the distro to boot everything, and even,
I now use "update-grub"  to update the config for the lfs systems.
It generates a pretty correct config _if_ I have a /boot/grub/grub.cfg
file on each lfs partition for the corresponding lfs system. That works
pretty well with debian ubuntu suse (not tried fedora).


The problem with that is knowing which grub.conf to change.  Which 
partition is the grub using for booting?  If you want to edit it to 
change, for instance, a kernel command line option,  how do you do that?


grub-mkconfig is terribly verbose.  For a new install of debian, with 
only one distro, grub.conf is 197 lines.  I can build LFS and have a 
dual boot system in about 15 lines.   There is MUCH more flexibility 
with a single boot partition.


For GPT (recommended), you need something like:

Number  Start (sector)End (sector)  Size   Code  Name
   120484095   1024.0 KiB  EF02  grub
   24096 1052671   512.0 MiB   8300  boot
   3 105267239456767   18.3 GiB8300  debian
   43945676860428287   10.0 GiB8200  Linux swap
   5   429604864   468666367   18.6 GiB8300  lfs-20190801
   ...
  14   307765248   370679807   30.0 GiB8300  lfs-9.0


grub should always be 1 MiB
boot can be smaller than 512 MiB, but I suggest no smaller than 100 MiB.
swap is actually optional but I recommend at least 2 GiB
For the LFS partition, 30 GiB gives enough room to build all of BLFS, 
but can be much smaller.  Currently I don't recommend anything less than 
10 GiB.


My grub.cfg is fairly easy to understand:

# Begin /boot/grub/grub.cfg
set default=1
set timeout=5

insmod ext2
set root=(hd0,2)

menuentry "Linux 4.18.5 (lfs-SVN-20180902) /dev/sda7" {
linux /vmlinuz-4.18.5-lfs-SVN-20180902 root=/dev/sda7 ro 
consoleblank=120

initrd /microcode.img
}

menuentry "Linux 4.20.0 (lfs-8.4) /dev/sda13" {
linux /vmlinuz-4.20.8-lfs-SVN-20190214 root=/dev/sda13 ro 
consoleblank=120

initrd /microcode.img
}

...
11 more entries.


On another system, a commercial distro entry looks like:

menuentry 'Linux Mint 17.2 Xfce 64-bit' {
   insmod gzio
   linux /vmlinuz-3.16.0-38-generic 
root=UUID=3b35b7db-f76b-4a32-baa7-814538d95ee1 ro

   initrd   /initrd.img-3.16.0-38-generic
}

  -- Bruce


--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] boot partition advice

[Bruce Dubbs]

See below.

On 10/19/19 2:07 PM, Chris6 wrote:

Unsubscribe

--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] boot partition advice

[Chris6]

Unsubscribe

Sent from ProtonMail mobile

 Original Message 
On Oct 19, 2019, 1:13 PM, Pierre Labastie wrote:

> On 19/10/2019 18:52, hazel debian wrote:
>
>> On Sat, Oct 19, 2019 at 5:39 PM Pierre Labastie  
>> wrote:
>>
>>> On 19/10/2019 17:07, Trent wrote:
>>>
 On 10/17/19 6:26 AM, hazel debian wrote:

> You should not mount the "BIOS boot" partition at /boot or anywhere else. 
> In fact you don't even need to have a filesystem on it.  GRUB installs 
> its second part on that empty partition, and the first part (which is in 
> the dummy MBR) should locate it by its physical address.
>
> I think you may be confusing this with the "boot partition" mentioned in 
> the book, which is actually something quite different. It is a normal 
> partition with a filesystem on it that is used to contain kernels when 
> you are multibooting LFS with other Linuxes.  The team recommend having 
> this common boot partition for all your systems and mounting it on /boot 
> in each of them.

 I  finished the rebuild on a single partition, with the "bios_grub" flag 
 set.
>>>
>>> Hmm, it's not what Hazel has written. On a GPT partition system,
>>> you need at least two partitions (OK not mandatory, but easiest): one which 
>>> is the "bios boot"
>>> (flag bios_grub in parted), which can be very small (1MB), and another one 
>>> for the system.
>>> Of course, you may have more partitions if you want separate partitions for 
>>> /boot, /home, or /usr.
>>> Do not format the "bios boot" partition, do not try to mount it. Mount the 
>>> second partition on /mnt/lfs instead. Build your system on it, then you can 
>>> install grub.
>>>
>>> Pierre
>>> --
>>
>> I've always dual-booted LFS with other LInuxen and I've never actually 
>> needed to use a separate /boot partition. But maybe that's because I always 
>> used lilo (and more recently elilo) as my bootloader and not grub as 
>> recommended.
>
> Actually, I do not have a separate boot partition anymore. Usually,
> I have one major distro + one or more LFS on my systems. I use
> the /boot/grub/grub.cfg of the distro to boot everything, and even,
> I now use "update-grub"  to update the config for the lfs systems.
> It generates a pretty correct config _if_ I have a /boot/grub/grub.cfg
> file on each lfs partition for the corresponding lfs system. That works
> pretty well with debian ubuntu suse (not tried fedora).
>
> Pierre-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] boot partition advice

[Chris6]

Unsubscribe

Sent from ProtonMail mobile

 Original Message 
On Oct 19, 2019, 2:03 PM, Ed Batalha wrote:

> Trent wrote:
>>
>> On my first try with LFS, I did version 8.4 systemd on an SSD with all
>> files in one partition.
>>
>> It boots just fine.
>>
>> I just did version 9.0 systemd on another SSD, all in one partition also.
>>
>>
>> However, in Chapter 8.4.3 Setting Up the Configuration, I ran into an
>> issue with this different SSD
>>
>> (grub-install /dev/sda)
>>
>> http://www.linuxfromscratch.org/lfs/view/stable-systemd/chapter08/grub.html
>>
>> Since I would not be booting with UEFI, I picked the "|--target i386-pc."|
>>
>> |What I got in return from this, unlike the previous SSD:|
>>
>> |
>> |
>>
>> |Installing for i386-pc platform.
>> grub-install: warning: this GPT partition label contains no BIOS Boot
>> Partition; embedding won't be possible.
>> grub-install: warning: Embedding is not possible. GRUB can only be
>> installed in this setup by using blocklists. However, blocklists are
>> UNRELIABLE and their use is discouraged..
>> grub-install: error: will not proceed with blocklists.|
>>
>> |Doing some research, I see would need to create a boot partition.|
>>
>> |Using gparted, I reduced the size of the single partition, and moved
>> it away from the start of the drive. I then made an ext2 partition,
>> and marked it with a flag of bios_grub as what I read I should do.
>> However, now it is being labeled as sdX2, if that makes any difference.
>> |
>>
>> |
>> |
>>
>> |I then when and remounted the LFS partition, and also the new boot
>> partition. I reran the grub command ||and returned:|
>>
>> |Installing for i386-pc platform.
>> Installation finished. No error reported.|
>>
>> |This was the same result as the previous SSD on a single partition,
>> but now got the boot partition.|
>>
>> |
>> |
>>
>> |I then set up fstab again with the following:|
>>
>> |
>> |
>>
>> |# Begin /etc/fstab
>> # file system mount-point type options dump fsck
>> # order
>> |
>>
>> |/dev/sda2 /boot ext2 defaults 0 2
>> /dev/sda1 / ext4 defaults 1 1
>> |
>>
>> | #/dev/ swap swap pri=1 0 0 (no swap)
>> # End /etc/fstab
>> EOF
>> |
>>
>> |
>> |
>>
>> |
>> |
>>
>> |I then copied all the files from /mnt/lfs/boot to the now mounted
>> boot partition I have verified they are in the boot partition.|
>>
>> |I then stuck the drive in the system I want to boot.|
>>
>> |All I am getting on screen is:|
>>
>> |"GRUB _ <-(blinking cursor)"|
>>
>> |Any advice on what I did wrong?|
>>
>> |
>> |
>>
>> |Thanks!
>> |
>>
> Hi,
>
> This article explains really well the way that Grub2 works and why it
> works the way it does.
>
> http://moi.vonos.net/linux/Booting_Linux_on_x86_with_Grub2/
>
> I hope you're able to find the answers you need here.
>
> Regards,
> Ed Batalha
> --
> http://lists.linuxfromscratch.org/listinfo/lfs-support
> FAQ: http://www.linuxfromscratch.org/blfs/faq.html
> Unsubscribe: See the above information page
>
> Do not top post on this list.
>
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
>
> http://en.wikipedia.org/wiki/Posting_style-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] boot partition advice

[Ed Batalha]

Trent wrote:


On my first try with LFS, I did version 8.4 systemd on an SSD with all 
files in one partition.


It boots just fine.

I just did version 9.0 systemd on another SSD, all in one partition also.


However, in Chapter 8.4.3 Setting Up the Configuration, I ran into an 
issue with this different SSD


(grub-install /dev/sda)

http://www.linuxfromscratch.org/lfs/view/stable-systemd/chapter08/grub.html

Since I would not be booting with UEFI, I picked the "|--target i386-pc."|

|What I got in return from this, unlike the previous SSD:|

|
|

|Installing for i386-pc platform.
grub-install: warning: this GPT partition label contains no BIOS Boot 
Partition; embedding won't be possible.
grub-install: warning: Embedding is not possible.  GRUB can only be 
installed in this setup by using blocklists.  However, blocklists are 
UNRELIABLE and their use is discouraged..

grub-install: error: will not proceed with blocklists.|

|Doing some research, I see would need to create a boot partition.|

|Using gparted, I reduced the size of the single partition, and moved 
it away from the start of the drive. I then made an ext2 partition, 
and marked it with a flag of bios_grub as what I read I should do. 
However, now it is being labeled as sdX2, if that makes any difference.

|

|
|

|I then when and remounted the LFS partition, and also the new boot 
partition. I reran the grub command ||and returned:|


|Installing for i386-pc platform.
Installation finished. No error reported.|

|This was the same result as the previous SSD on a single partition, 
but now got the boot partition.|


|
|

|I then set up fstab again with the following:|

|
|

|# Begin /etc/fstab
# file system mount-point  type  options   dump fsck
#   order
|

|/dev/sda2/bootext2 defaults0   2
/dev/sda1/ext4   defaults1   1
|

| #/dev/ swap swap pri=1 0 0 (no swap)
 # End /etc/fstab
 EOF
|

|
|

|
|

|I then copied all the files from /mnt/lfs/boot to the now mounted 
boot partition I have verified they are in the boot partition.|


|I then stuck the drive in the system I want to boot.|

|All I am getting on screen is:|

|"GRUB _ <-(blinking cursor)"|

|Any advice on what I did wrong?|

|
|

|Thanks!
|


Hi,

This article explains really well the way that Grub2 works and why it 
works the way it does.


http://moi.vonos.net/linux/Booting_Linux_on_x86_with_Grub2/

I hope you're able to find the answers you need here.

Regards,
Ed Batalha
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] boot partition advice

[Pierre Labastie]

On 19/10/2019 18:52, hazel debian wrote:



On Sat, Oct 19, 2019 at 5:39 PM Pierre Labastie 
mailto:pierre.labas...@neuf.fr>> wrote:




On 19/10/2019 17:07, Trent wrote:



On 10/17/19 6:26 AM, hazel debian wrote:




You should not mount the "BIOS boot" partition at /boot or
anywhere else. In fact you don't even need to have a filesystem
on it. GRUB installs its second part on that empty partition,
and the first part (which is in the dummy MBR) should locate it
by its physical address.

I think you may be confusing this with the "boot partition"
mentioned in the book, which is actually something quite
different. It is a normal partition with a filesystem on it that
is used to contain kernels when you are multibooting LFS with
other Linuxes.  The team recommend having this common boot
partition for all your systems and mounting it on /boot in each
of them.



I  finished the rebuild on a single partition, with the
"bios_grub" flag set.



Hmm, it's not what Hazel has written. On a GPT partition system,
you need at least two partitions (OK not mandatory, but easiest):
one which is the "bios boot"
(flag bios_grub in parted), which can be very small (1MB), and
another one for the system.
Of course, you may have more partitions if you want separate
partitions for /boot, /home, or /usr.
Do not format the "bios boot" partition, do not try to mount it.
Mount the second partition on /mnt/lfs instead. Build your system
on it, then you can install grub.

Pierre
-- 

I've always dual-booted LFS with other LInuxen and I've never actually 
needed to use a separate /boot partition. But maybe that's because I 
always used lilo (and more recently elilo) as my bootloader and not 
grub as recommended.



Actually, I do not have a separate boot partition anymore. Usually,
I have one major distro + one or more LFS on my systems. I use
the /boot/grub/grub.cfg of the distro to boot everything, and even,
I now use "update-grub"  to update the config for the lfs systems.
It generates a pretty correct config _if_ I have a /boot/grub/grub.cfg
file on each lfs partition for the corresponding lfs system. That works
pretty well with debian ubuntu suse (not tried fedora).

Pierre
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] boot partition advice

[hazel debian]

On Sat, Oct 19, 2019 at 5:39 PM Pierre Labastie 
wrote:

>
>
> On 19/10/2019 17:07, Trent wrote:
>
>
> On 10/17/19 6:26 AM, hazel debian wrote:
>
>
>
>
> You should not mount the "BIOS boot" partition at /boot or anywhere else.
> In fact you don't even need to have a filesystem on it.  GRUB installs its
> second part on that empty partition, and the first part (which is in the
> dummy MBR) should locate it by its physical address.
>
> I think you may be confusing this with the "boot partition" mentioned in
> the book, which is actually something quite different. It is a normal
> partition with a filesystem on it that is used to contain kernels when you
> are multibooting LFS with other Linuxes.  The team recommend having this
> common boot partition for all your systems and mounting it on /boot in each
> of them.
>
>
> I  finished the rebuild on a single partition, with the "bios_grub" flag
> set.
>
>
> Hmm, it's not what Hazel has written. On a GPT partition system,
> you need at least two partitions (OK not mandatory, but easiest): one
> which is the "bios boot"
> (flag bios_grub in parted), which can be very small (1MB), and another one
> for the system.
> Of course, you may have more partitions if you want separate partitions
> for /boot, /home, or /usr.
> Do not format the "bios boot" partition, do not try to mount it. Mount the
> second partition on /mnt/lfs instead. Build your system on it, then you can
> install grub.
>
> Pierre
> --
>
> I've always dual-booted LFS with other LInuxen and I've never actually
needed to use a separate /boot partition. But maybe that's because I always
used lilo (and more recently elilo) as my bootloader and not grub as
recommended.
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] boot partition advice

[Pierre Labastie]

On 19/10/2019 17:07, Trent wrote:



On 10/17/19 6:26 AM, hazel debian wrote:




You should not mount the "BIOS boot" partition at /boot or anywhere 
else. In fact you don't even need to have a filesystem on it.  GRUB 
installs its second part on that empty partition, and the first part 
(which is in the dummy MBR) should locate it by its physical address.


I think you may be confusing this with the "boot partition" mentioned 
in the book, which is actually something quite different. It is a 
normal partition with a filesystem on it that is used to contain 
kernels when you are multibooting LFS with other Linuxes.  The team 
recommend having this common boot partition for all your systems and 
mounting it on /boot in each of them.




I  finished the rebuild on a single partition, with the "bios_grub" 
flag set.




Hmm, it's not what Hazel has written. On a GPT partition system,
you need at least two partitions (OK not mandatory, but easiest): one 
which is the "bios boot"
(flag bios_grub in parted), which can be very small (1MB), and another 
one for the system.
Of course, you may have more partitions if you want separate partitions 
for /boot, /home, or /usr.
Do not format the "bios boot" partition, do not try to mount it. Mount 
the second partition on /mnt/lfs instead. Build your system on it, then 
you can install grub.


Pierre
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] boot partition advice

[Trent]

On 10/17/19 6:26 AM, hazel debian wrote:



On Wed, Oct 16, 2019 at 11:21 PM Trent > wrote:


On my first try with LFS, I did version 8.4 systemd on an SSD with
all files in one partition.

It boots just fine.

I just did version 9.0 systemd on another SSD, all in one
partition also.


However, in Chapter 8.4.3 Setting Up the Configuration, I ran into
an issue with this different SSD

(grub-install /dev/sda)

http://www.linuxfromscratch.org/lfs/view/stable-systemd/chapter08/grub.html

Since I would not be booting with UEFI, I picked the "|--target
i386-pc."|

|What I got in return from this, unlike the previous SSD:|

|
|

|Installing for i386-pc platform.
grub-install: warning: this GPT partition label contains no BIOS
Boot Partition; embedding won't be possible.
grub-install: warning: Embedding is not possible. GRUB can only be
installed in this setup by using blocklists.  However, blocklists
are UNRELIABLE and their use is discouraged..
grub-install: error: will not proceed with blocklists.|

|Doing some research, I see would need to create a boot partition.|

|Using gparted, I reduced the size of the single partition, and
moved it away from the start of the drive. I then made an ext2
partition, and marked it with a flag of bios_grub as what I read I
should do. However, now it is being labeled as sdX2, if that makes
any difference.
|

|
|

|I then when and remounted the LFS partition, and also the new
boot partition. I reran the grub command ||and returned:|

|Installing for i386-pc platform.
Installation finished. No error reported.|

|This was the same result as the previous SSD on a single
partition, but now got the boot partition.|

|I then set up fstab again with the following:|

||

|# Begin /etc/fstab
# file system mount-point  type  options dump fsck
#   order
|

|/dev/sda2    /boot    ext2 defaults    0   2
/dev/sda1    /    ext4   defaults 1   1
|

| #/dev/ swap swap pri=1 0 0 (no swap)
 # End /etc/fstab
 EOF
|

|
|

|
|

|I then copied all the files from /mnt/lfs/boot to the now mounted
boot partition I have verified they are in the boot partition.|

|I then stuck the drive in the system I want to boot.|

|All I am getting on screen is:|

|"GRUB _ <-(blinking cursor)"|

|Any advice on what I did wrong?|

|
|

|Thanks!
|


You should not mount the "BIOS boot" partition at /boot or anywhere 
else. In fact you don't even need to have a filesystem on it.  GRUB 
installs its second part on that empty partition, and the first part 
(which is in the dummy MBR) should locate it by its physical address.


I think you may be confusing this with the "boot partition" mentioned 
in the book, which is actually something quite different. It is a 
normal partition with a filesystem on it that is used to contain 
kernels when you are multibooting LFS with other Linuxes.  The team 
recommend having this common boot partition for all your systems and 
mounting it on /boot in each of them.




I  finished the rebuild on a single partition, with the "bios_grub" flag 
set.



I am still getting the same result as before. "GRUB _"



-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] boot partition advice

[Trent]

On 10/17/19 6:26 AM, hazel debian wrote:



On Wed, Oct 16, 2019 at 11:21 PM Trent > wrote:


On my first try with LFS, I did version 8.4 systemd on an SSD with
all files in one partition.

It boots just fine.

I just did version 9.0 systemd on another SSD, all in one
partition also.


However, in Chapter 8.4.3 Setting Up the Configuration, I ran into
an issue with this different SSD

(grub-install /dev/sda)

http://www.linuxfromscratch.org/lfs/view/stable-systemd/chapter08/grub.html

Since I would not be booting with UEFI, I picked the "|--target
i386-pc."|

|What I got in return from this, unlike the previous SSD:|

|
|

|Installing for i386-pc platform.
grub-install: warning: this GPT partition label contains no BIOS
Boot Partition; embedding won't be possible.
grub-install: warning: Embedding is not possible. GRUB can only be
installed in this setup by using blocklists.  However, blocklists
are UNRELIABLE and their use is discouraged..
grub-install: error: will not proceed with blocklists.|

|Doing some research, I see would need to create a boot partition.|

|Using gparted, I reduced the size of the single partition, and
moved it away from the start of the drive. I then made an ext2
partition, and marked it with a flag of bios_grub as what I read I
should do. However, now it is being labeled as sdX2, if that makes
any difference.
|

|
|

|I then when and remounted the LFS partition, and also the new
boot partition. I reran the grub command ||and returned:|

|Installing for i386-pc platform.
Installation finished. No error reported.|

|This was the same result as the previous SSD on a single
partition, but now got the boot partition.|

|I then set up fstab again with the following:|

||

|# Begin /etc/fstab
# file system mount-point  type  options dump fsck
#   order
|

|/dev/sda2    /boot    ext2 defaults    0   2
/dev/sda1    /    ext4   defaults 1   1
|

| #/dev/ swap swap pri=1 0 0 (no swap)
 # End /etc/fstab
 EOF
|

|
|

|
|

|I then copied all the files from /mnt/lfs/boot to the now mounted
boot partition I have verified they are in the boot partition.|

|I then stuck the drive in the system I want to boot.|

|All I am getting on screen is:|

|"GRUB _ <-(blinking cursor)"|

|Any advice on what I did wrong?|

|
|

|Thanks!
|


You should not mount the "BIOS boot" partition at /boot or anywhere 
else. In fact you don't even need to have a filesystem on it.  GRUB 
installs its second part on that empty partition, and the first part 
(which is in the dummy MBR) should locate it by its physical address.


I think you may be confusing this with the "boot partition" mentioned 
in the book, which is actually something quite different. It is a 
normal partition with a filesystem on it that is used to contain 
kernels when you are multibooting LFS with other Linuxes.  The team 
recommend having this common boot partition for all your systems and 
mounting it on /boot in each of them.


Thanks for the response. I started messing around with the partitions, 
and it broke the install. I started over.


I will get back with the result once I am done.


Trent

-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] boot partition advice

[hazel debian]

On Wed, Oct 16, 2019 at 11:21 PM Trent  wrote:

> On my first try with LFS, I did version 8.4 systemd on an SSD with all
> files in one partition.
>
> It boots just fine.
>
> I just did version 9.0 systemd on another SSD, all in one partition also.
>
>
> However, in Chapter 8.4.3 Setting Up the Configuration, I ran into an
> issue with this different SSD
>
> (grub-install /dev/sda)
>
> http://www.linuxfromscratch.org/lfs/view/stable-systemd/chapter08/grub.html
>
> Since I would not be booting with UEFI, I picked the "--target i386-pc."
>
> What I got in return from this, unlike the previous SSD:
>
>
> Installing for i386-pc platform.
> grub-install: warning: this GPT partition label contains no BIOS Boot
> Partition; embedding won't be possible.
> grub-install: warning: Embedding is not possible.  GRUB can only be
> installed in this setup by using blocklists.  However, blocklists are
> UNRELIABLE and their use is discouraged..
> grub-install: error: will not proceed with blocklists.
>
> Doing some research, I see would need to create a boot partition.
>
> Using gparted, I reduced the size of the single partition, and moved it
> away from the start of the drive. I then made an ext2 partition, and marked
> it with a flag of bios_grub as what I read I should do. However, now it is
> being labeled as sdX2, if that makes any difference.
>
>
> I then when and remounted the LFS partition, and also the new boot
> partition. I reran the grub command and returned:
>
> Installing for i386-pc platform.
> Installation finished. No error reported.
>
> This was the same result as the previous SSD on a single partition, but
> now got the boot partition.
>
> I then set up fstab again with the following:
>
> # Begin /etc/fstab
> # file system mount-point  type  options   dump fsck
> #   order
>
> /dev/sda2/bootext2   defaults0   2
> /dev/sda1/ext4   defaults1   1
>
>  #/dev/ swap swap pri=1 0 0 (no swap)
>  # End /etc/fstab
>  EOF
>
>
>
> I then copied all the files from /mnt/lfs/boot to the now mounted boot
> partition I have verified they are in the boot partition.
>
> I then stuck the drive in the system I want to boot.
>
> All I am getting on screen is:
>
> "GRUB _ <-(blinking cursor)"
>
> Any advice on what I did wrong?
>
>
> Thanks!
>
> You should not mount the "BIOS boot" partition at /boot or anywhere else.
In fact you don't even need to have a filesystem on it.  GRUB installs its
second part on that empty partition, and the first part (which is in the
dummy MBR) should locate it by its physical address.

I think you may be confusing this with the "boot partition" mentioned in
the book, which is actually something quite different. It is a normal
partition with a filesystem on it that is used to contain kernels when you
are multibooting LFS with other Linuxes.  The team recommend having this
common boot partition for all your systems and mounting it on /boot in each
of them.
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] boot partition advice

[Trent]

On 10/16/19 5:20 PM, Trent wrote:


On my first try with LFS, I did version 8.4 systemd on an SSD with all 
files in one partition.


It boots just fine.

I just did version 9.0 systemd on another SSD, all in one partition also.


However, in Chapter 8.4.3 Setting Up the Configuration, I ran into an 
issue with this different SSD


(grub-install /dev/sda)

http://www.linuxfromscratch.org/lfs/view/stable-systemd/chapter08/grub.html

Since I would not be booting with UEFI, I picked the "|--target i386-pc."|

|What I got in return from this, unlike the previous SSD:|

|
|

|Installing for i386-pc platform.
grub-install: warning: this GPT partition label contains no BIOS Boot 
Partition; embedding won't be possible.
grub-install: warning: Embedding is not possible.  GRUB can only be 
installed in this setup by using blocklists.  However, blocklists are 
UNRELIABLE and their use is discouraged..

grub-install: error: will not proceed with blocklists.|

|Doing some research, I see would need to create a boot partition.|

|Using gparted, I reduced the size of the single partition, and moved 
it away from the start of the drive. I then made an ext2 partition, 
and marked it with a flag of bios_grub as what I read I should do. 
However, now it is being labeled as sdX2, if that makes any difference.

|

|
|

|I then when and remounted the LFS partition, and also the new boot 
partition. I reran the grub command ||and returned:|


|Installing for i386-pc platform.
Installation finished. No error reported.|

|This was the same result as the previous SSD on a single partition, 
but now got the boot partition.|


|
|

|I then set up fstab again with the following:|

|
|

|# Begin /etc/fstab
# file system mount-point  type  options   dump fsck
#   order
|

|/dev/sda2    /boot    ext2 defaults    0   2
/dev/sda1    /    ext4   defaults    1   1
|

| #/dev/ swap swap pri=1 0 0 (no swap)
 # End /etc/fstab
 EOF
|

|
|

|
|

|I then copied all the files from /mnt/lfs/boot to the now mounted 
boot partition I have verified they are in the boot partition.|


|I then stuck the drive in the system I want to boot.|

|All I am getting on screen is:|

|"GRUB _ <-(blinking cursor)"|

|Any advice on what I did wrong?|

|
|

|Thanks!
|

|
|




Just an update, something I left out and tried to do (no, not resolved)

I did not create or copy the grub.cfg file over to the boot partition

I just created what I had (working from version 8.4 booting from sda1) 
then copied it over to the boot partition.


Turns out that was incorrect as it gave me the same result when booted.

More closely reading 8.4.4. Creating the GRUB Configuration File, I see 
I needed to make some changes from the "Note" box.



So here is what I got in grub/grub.cfg:

*

# Begin /boot/grub/grub.cfg
set default=0
set timeout=5
insmod ext2
set root=(hd0,2)
menuentry "GNU/Linux, |Linux 5.2.8-lfs-9.0-systemd|" {
linux /|vmlinuz-5.2.8-lfs-9.0-systemd |root=/dev/sda2 ro
}



Remember, I have the boot partition as an ext2 with "bios_grub" flag 
set, and in this case the machine is boots on, makes the partition sda2 
(The example in the book shows an identical setup in grub.cfg).



Seems not even those changes worked out and still getting that "GRUB" 
message on boot with the blinking cursor next to it.




-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

[lfs-support] boot partition advice

[Trent]

On my first try with LFS, I did version 8.4 systemd on an SSD with all 
files in one partition.


It boots just fine.

I just did version 9.0 systemd on another SSD, all in one partition also.


However, in Chapter 8.4.3 Setting Up the Configuration, I ran into an 
issue with this different SSD


(grub-install /dev/sda)

http://www.linuxfromscratch.org/lfs/view/stable-systemd/chapter08/grub.html

Since I would not be booting with UEFI, I picked the "|--target i386-pc."|

|What I got in return from this, unlike the previous SSD:|

|
|

|Installing for i386-pc platform.
grub-install: warning: this GPT partition label contains no BIOS Boot 
Partition; embedding won't be possible.
grub-install: warning: Embedding is not possible.  GRUB can only be 
installed in this setup by using blocklists.  However, blocklists are 
UNRELIABLE and their use is discouraged..

grub-install: error: will not proceed with blocklists.|

|Doing some research, I see would need to create a boot partition.|

|Using gparted, I reduced the size of the single partition, and moved it 
away from the start of the drive. I then made an ext2 partition, and 
marked it with a flag of bios_grub as what I read I should do. However, 
now it is being labeled as sdX2, if that makes any difference.

|

|
|

|I then when and remounted the LFS partition, and also the new boot 
partition. I reran the grub command ||and returned:|


|Installing for i386-pc platform.
Installation finished. No error reported.|

|This was the same result as the previous SSD on a single partition, but 
now got the boot partition.|


|
|

|I then set up fstab again with the following:|

|
|

|# Begin /etc/fstab
# file system mount-point  type  options   dump fsck
#   order
|

|/dev/sda2    /boot    ext2 defaults    0   2
/dev/sda1    /    ext4   defaults    1   1
|

| #/dev/ swap swap pri=1 0 0 (no swap)
 # End /etc/fstab
 EOF
|

|
|

|
|

|I then copied all the files from /mnt/lfs/boot to the now mounted boot 
partition I have verified they are in the boot partition.|


|I then stuck the drive in the system I want to boot.|

|All I am getting on screen is:|

|"GRUB _ <-(blinking cursor)"|

|Any advice on what I did wrong?|

|
|

|Thanks!
|

|
|

|
|



-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style