On Mon, Jul 18, 2016 at 5:18 PM, Samuel Sieb wrote:
> On 07/18/2016 01:07 PM, Chris Murphy wrote:
>>
>> On Mon, Jul 18, 2016, 1:40 PM Samuel Sieb > <mailto:sam...@sieb.net>> wrote:
>> Since you are creating a bios boot partition, you must be using t
On 07/18/2016 01:07 PM, Chris Murphy wrote:
On Mon, Jul 18, 2016, 1:40 PM Samuel Sieb mailto:sam...@sieb.net>> wrote:
Since you are creating a bios boot partition, you must be using the
non-GPT partition table.
BIOS Boot is where the core.img is embedded when using GPT partitionin
On Mon, 2016-07-18 at 20:04 +, Chris Murphy wrote:
> Use gdisk, partition type code EF02. Do this on both disks, install
> normally, post install do
>
> grub2-install /dev/SDA /dev/and
>
> Done.
>
Setting the partition type using gdisk was the necessary step to make
grub2-install happy.
I
On Mon, Jul 18, 2016, 1:40 PM Samuel Sieb wrote:
>
> Since you are creating a bios boot partition, you must be using the
> non-GPT partition table.
BIOS Boot is where the core.img is embedded when using GPT partitioning
with BIOS firmware.
---
Chris Murphy
--
users mailing l
Use gdisk, partition type code EF02. Do this on both disks, install
normally, post install do
grub2-install /dev/SDA /dev/and
Done.
---
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/use
boot.
Since you are creating a bios boot partition, you must be using the
non-GPT partition table. In that case, there is no actual type for a
"bios boot" partition. Look at what gparted identifies the partition on
sda as. However, was there anything else you wanted to keep alrea
Hi
I did a f24 installation using swraid on 4TB disks (predefined swraid
because I am still unhappy with complex tasks and the level disk
abstraction in anaconda, but thats not the point).
I was not able to write bios boot twice (sda and sdb), it was only
written on sda (there is plenty of space
as you add
member devices.
Yes, that was what I ended up doing.
I partitioned /dev/sda as I wanted, with space for BIOS boot partition,
and also an EFI partition if I ever would need one (more or less a setup
as described in <https://bugzilla.redhat.com/show_bug.cgi?id=1061478> I
ha
aconda/program.log
And it will show you the command used. It should list all member devices. So
long as each member drive has a BIOS Boot partition, grub2-install will find it
automatically and insert core.img there, as well as the specific jump code in
the first 440 bytes of the (protective) MBR to
On Aug 28, 2014, at 12:21 PM, Bruno Wolff III wrote:
>
> I think using raid 1 (with the 1.0 header format) can work well for that.
> There can still grub issues with having a boot just work, but at least you
> have the stuff you need available.
GRUB2 can locate vmlinuz/initramfs on md/mdadm r
l partitioning to get everything as I wanted. When this was
> ready I got the error message that I also needed a BIOS boot partition (I
> gather that this due to being rather large disks). I tried to create one of
> those, but it seemed to only be created on one of the discs in the raid
&
they are setup as GPT (GUID Partition Table), and they then
> also need a BIOS boot partition to work on non UEFI based systems (if I
> have understood it correctly).
>
> So, to be able to boot from any of the disks, I need a BIOS boot
> partition on all disks, but anaconda seem
problem here seem to be that due to the disks being large (larger
than 1TB) they are setup as GPT (GUID Partition Table), and they then
also need a BIOS boot partition to work on non UEFI based systems (if I
have understood it correctly).
So, to be able to boot from any of the disks, I need a BIOS
On Thu, Aug 28, 2014 at 11:10:54 -0700,
Rick Stevens wrote:
I think you need to reserve some small space on all the drives (and
with 3TB drives you can afford to sacrifice a few MB), use the remainder
as your RAID, and let the system put the boot partition in that reserved
space on the primary
as I wanted. When this was
ready I got the error message that I also needed a BIOS boot partition
(I gather that this due to being rather large disks). I tried to create
one of those, but it seemed to only be created on one of the discs in
the raid array, I wanted it created on all disks, just as the
I also needed a BIOS boot partition
(I gather that this due to being rather large disks). I tried to create
one of those, but it seemed to only be created on one of the discs in
the raid array, I wanted it created on all disks, just as the raid
partitions. This to be able to boot from any of the
with the kickstart option part biosboot
--fstype=biosboot --size=1. However, in the case that a disk has an
existing biosboot partition, adding a "part biosboot" option is
unnecessary.
how can I create this bios boot partition using parted ?
I will use this in a pre-section of a kickst
On Sun, Nov 13, 2011 at 04:44:11PM -0800, Bryce Hardy wrote:
> On Sun, Nov 13, 2011 at 4:24 PM, Tom Horsley wrote:
> > All excellent questions which I would have thought deserved at least
> > a bit of text in the release notes rather than just firing a barrel
> > full of acronyms at you :-).
>
On 11/14/2011 05:54 AM, Tom Horsley wrote:
> On Mon, 14 Nov 2011 00:11:03 +
> Marko Vojinovic wrote:
>
>> Now, I gather from the text above that the boot partition is necessary only
>> for "non-EFI" systems with a "GPT-labelled" disk. What does this mean? How
>> can
>> I check whether my sy
nd is necessary to take advantage of
> the disks bigger than 2TB that are getting common these days).
>
> http://en.wikipedia.org/wiki/GUID_Partition_Table
Ah, ok, this was useful to read, thanks! :-)
> If you actually needed a bios boot partition and didn't make
> one, your s
On Sun, Nov 13, 2011 at 4:24 PM, Tom Horsley wrote:
> All excellent questions which I would have thought deserved at least
> a bit of text in the release notes rather than just firing a barrel
> full of acronyms at you :-).
Even worse, the official Installation Guide for F16 doesn't even
mention
titioned, you don't have a GPT disk. Apparently
GPT is a brand new partitioning scheme that breaks free of
the old DOS scheme (and is necessary to take advantage of
the disks bigger than 2TB that are getting common these days).
http://en.wikipedia.org/wiki/GUID_Partition_Table
If you actually need
disklabels (partition tables) instead of MSDOS
disklabels. On these systems, when booting from a GPT-labelled disk, it is
strongly recommended (not necessarily required in all cases, depending on the
system's BIOS/firmware) to create a small (1MiB) BIOS boot partition. This
partition will be us
23 matches
Mail list logo
