From: Tobias Geerinckx-Rice <me@tobias.gr>
To: znavko@disroot.org
Cc: 36262@debbugs.gnu.org
Subject: bug#36262: cannot install bootloader to root partition
Date: Tue, 18 Jun 2019 04:33:22 +0200 [thread overview]
Message-ID: <87wohjwrkd.fsf@nckx> (raw)
In-Reply-To: <8ac8087c445d45599bb0c00d018242b5@disroot.org>
[-- Attachment #1: Type: text/plain, Size: 1794 bytes --]
Znavko,
znavko@disroot.org wrote:
> I have another laptop (Lenovo G50-30) where Guix works on this
> partition layout I've made manually:
>
> # fdisk -l /dev/sda
> ...
^ You removed the most important part, please don't do this on
help lists.
Still, we can tell that this is an ‘mbr’ layout:
> Device Boot Start End Sectors Size Id Type
> /dev/sda1 2048 230000000 229997953 109.7G 83 Linux
> /dev/sda2 230000640 234441647 4441008 2.1G 82 Linux
> swap / Solaris
^^^^^^^^^^^^^^^^^^^^^^^
> But all the new installations on other two notebooks with the
> same layout do not work.
They aren't the same: the one in your screenshot is a completely
different ‘gpt’ layout.
Hence my unanswered question:
> Did you create this layout manually? If so, why?
Although now I suspect there was no reason and that the installer
isn't to blame.
So you can either:
- throw away your existing layout and create new MBR disklabel.
Your partitioning software will ask you or provide an option
somewhere. Since modern partitioning software leaves a huge gap
before the first partition, GRUB will nestle cosily into that
first unused ~MiB.
- keep it as GPT (it has some minor features MBR doesn't), and
create an additional GPT ‘BIOS boot partition’ as recommended
before. It only needs to be a few 100 KiB, so I use the space
before the first partition (= before the first megabyte; turning
off ‘alignment’ in your partitioning software). This tiny
partition is for use by GRUB, and GRUB alone: do not format or
mount it.
Both options work equally well, but you need to choose.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2019-06-18 2:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 11:25 bug#36262: cannot install bootloader to root partition znavko
2019-06-17 14:53 ` Danny Milosavljevic
2019-06-17 17:09 ` Tobias Geerinckx-Rice
2019-06-17 17:19 ` znavko
2019-06-17 17:08 ` Tobias Geerinckx-Rice
2019-06-17 22:59 ` Mark H Weaver
2019-06-18 2:59 ` Tobias Geerinckx-Rice
2019-06-18 10:22 ` Mark H Weaver
2019-06-17 17:11 ` znavko
2019-06-18 2:33 ` Tobias Geerinckx-Rice [this message]
2019-06-18 8:01 ` pelzflorian (Florian Pelz)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wohjwrkd.fsf@nckx \
--to=me@tobias.gr \
--cc=36262@debbugs.gnu.org \
--cc=znavko@disroot.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).