Re: rawhide net install image doesn't work with bios partitions

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

 



On 5/28/19 1:04 PM, stan wrote:
On Mon, 27 May 2019 22:27:16 -0600
Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote:
On Mon, May 27, 2019 at 3:55 PM stan <upaitag@xxxxxxxx> wrote:
And, if
I install as UEFI, for some reason it doesn't accept the existing
ext4 partitions on the gpt formatted drive.

What do you mean by it didn't accept them?

That's a separate bug report, also needs installer logs attached.
Same question. Where are they saved?

If the installation is nearly complete, they are probably in /var/log/anaconda on the installed system. Otherwise, they are in /tmp while the installer is running. You can switch to a console to see them or copy them off.

Is must be possible to boot a
GPT drive from a BIOS mbr because it appears that I was doing
that.

I can't parse this.

The existing F28 on this GPT disk was booting just fine before I tried
to install F31.  Turn the machine on, and F28 running resulted.

Yes, that does work and I see you have the BIOS boot partition.

Or, did the hybrid UEFI/BIOS firmware setting allow both?

Running 'efibootmgr' will tell you what firmware is being presented to
the kernel.

# efibootmgr -v
EFI variables are not supported on this system (from F28, /dev/sda5, on
the GPT drive).

So not an EFI boot.

The first two partitions are boot, then swap, then two root
partitions, then data.  The code for the partitions I was trying to
install from the iso to are now 8300, the existing Fedora is 0700.

That's all suspicious because 0700 for a boot volume isn't correct,
and suggests an old version of parted created that partition. Also
partition 3 cannot be a root partition, the type code is for swap.

That confused me at first as well until I realized he meant there are two /boot partitions like the two root partitions.

# fdisk -l /dev/sda
Disk /dev/sda: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 363C9B1D-DBA5-41AE-A74B-6DD5F974ED6D

Device          Start        End    Sectors  Size Type
/dev/sda1     2097152    4194303    2097152    1G Linux filesystem
/dev/sda2     4194304    6291455    2097152    1G Microsoft basic data
/dev/sda3     6291456   48234495   41943040   20G Linux swap
/dev/sda4    48234496  572522495  524288000  250G Linux filesystem
/dev/sda5   572522496 1096810495  524288000  250G Microsoft basic data
/dev/sda6  1096810496 5860532223 4763721728  2.2T Microsoft basic data
/dev/sda7        2048       6143       4096    2M BIOS boot

Partition table entries are not in disk order.

I'm typing from /dev/sda5.  So, 0700 *is* a linux filesystem on this
disk, not Microsoft basic data.

The kernel will mount a partition regardless of what it's labelled as, but the installer might not accept it.
_______________________________________________
test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux