From: Bruce Dubbs <bruce.dubbs@gmail.com>
To: Karel Zak <kzak@redhat.com>
Cc: Util-Linux <util-linux@vger.kernel.org>
Subject: Re: fdisk request for functionality (or info)
Date: Wed, 4 Oct 2017 09:41:38 -0500 [thread overview]
Message-ID: <59D4F322.7040805@gmail.com> (raw)
In-Reply-To: <20171004082728.if274peupxjljbxd@ws.net.home>
Karel Zak wrote:
> On Tue, Oct 03, 2017 at 11:57:06AM -0500, Bruce Dubbs wrote:
>> I have been having a problem with fdisk on old computers.
>>
>> What I am doing is installing Debian, but dropping to the command line and
>> creating a GPT manually because Debian seems to want to always create a
>> msdos partition table.
>>
>> After creating the GPT and partitioning, the install proceeds normally, but
>> upon reboot the old bios tells me "No bootable disk".
>>
>> I can fix this by going into rescue mode and setting the pmbr_boot flag
>> using parted.
>>
>> My question is whether this can be done in fdisk. If not, can it be added?
>>
>> I did try going into expert mode and selecting "toggle the legacy BIOS
>> bootable flag", but does not seem to work. I did not see any change to the
>> boot sector when using 'd: print the raw data of the first sector from the
>> device'.
>
> The tricky thing is that fdisks by default see GPT partition, so you
> have to force the tools to ignore GPT and use PMBR. There is more
> ways:
> 2) start fdisk as usually
> - go to expert mode ('r')
There is not an 'r' mode, only 'x' when the current table is gpt.
> - see help ('m')
> - switch to nested label ('M')
> - go to main menu ('r')
> - toggle boot flag ('a')
> - write ('w')
I wasn't sure if the 'pmbr_boot' flag was just the standard mbr boot flag
for partition 1 or not. Would it be reasonable to set that flag by
default when 'g create a new empty GPT partition table' is selected?
-- Bruce
next prev parent reply other threads:[~2017-10-04 14:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 16:57 fdisk request for functionality (or info) Bruce Dubbs
2017-10-04 8:27 ` Karel Zak
2017-10-04 8:59 ` Peter Cordes
2017-10-04 9:47 ` Karel Zak
2017-11-02 12:52 ` Karel Zak
2017-10-04 14:41 ` Bruce Dubbs [this message]
2017-10-05 10:59 ` Karel Zak
2017-10-05 16:04 ` Bruce Dubbs
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=59D4F322.7040805@gmail.com \
--to=bruce.dubbs@gmail.com \
--cc=kzak@redhat.com \
--cc=util-linux@vger.kernel.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.
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 NNTP newsgroup(s).