I need a gdisk list of a UEFI system

Post by Bit Twister
Would some kind person with a UEFI booting system please post the
results of the following 2 root terminal commands
gdisk -l /dev/sda
blkid -s device -s LABEL -s TYPE -s PARTLABEL | sort -V

This from Ubuntu i=16.04 if that's okay.

GPT fdisk (gdisk) version 1.0.1

Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/nvme0n1: 1000215216 sectors, 476.9 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): F8499EEA-DE2E-4BAC-86EE-9DCCDD07EC45
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1000215182
Partitions will be aligned on 2048-sector boundaries
Total free space is 2669 sectors (1.3 MiB)

Number Start (sector) End (sector) Size Code Name
1 2048 1050623 512.0 MiB EF00 EFI System Partition
2 1050624 933412863 444.6 GiB 8300
3 933412864 1000214527 31.9 GiB 8200
/dev/nvme0n1p1: TYPE="vfat" PARTLABEL="EFI System Partition"
/dev/nvme0n1p2: TYPE="ext4"
/dev/nvme0n1p3: TYPE="swap"
/dev/sda1: LABEL="guests" TYPE="ext4"
/dev/sda2: TYPE="ext4"

--
Marek Novotny
https://github.com/marek-novotny

Bit Twister

2016-06-11 21:40:30 UTC

This from Ubuntu i=16.04 if that's okay.
1 2048 1050623 512.0 MiB EF00 EFI System Partition
/dev/nvme0n1p1: TYPE="vfat" PARTLABEL="EFI System Partition"

Thank you, I was looking for the data needed for an EFI boot partition:
vfat 512.0 MiB EF00 EFI System Partition

What I was looking into is what's used for a legacy bios boot which
requires this partition information for a "MBR install"
cleared 260+ MiB EF02=bios_grub

dlbendigo

2016-06-12 03:44:44 UTC

This from Ubuntu i=16.04 if that's okay.
1 2048 1050623 512.0 MiB EF00 EFI System Partition
/dev/nvme0n1p1: TYPE="vfat" PARTLABEL="EFI System Partition"

vfat 512.0 MiB EF00 EFI System Partition
What I was looking into is what's used for a legacy bios boot which
requires this partition information for a "MBR install"
cleared 260+ MiB EF02=bios_grub

Mageia used to say: create a 300 Mb partition (the 260+.) Windows
creates one of 100 MB, and mine isn't nearly full.
For the filesystem, there is a specific one (use gdisk/fdisk, list
partitions,
second screen, near the bottom) but FAT32 is good enough, and
what is usually recommended.

HTH,

Doug.

--

dlbendigo

2016-06-12 03:52:30 UTC

This from Ubuntu i=16.04 if that's okay.
1 2048 1050623 512.0 MiB EF00 EFI System Partition
/dev/nvme0n1p1: TYPE="vfat" PARTLABEL="EFI System Partition"

vfat 512.0 MiB EF00 EFI System Partition
What I was looking into is what's used for a legacy bios boot which
requires this partition information for a "MBR install"
cleared 260+ MiB EF02=bios_grub

The "protective MBR" on Marek's listing is apparently created with
every
EFI filesystem, according to the documentation, for compatibility.
It crossed my mind that you don't dual-boot Windows, so the filesystem
could perhaps be a Linux one. All the examples I have seen are for
dual-booting with Windows. Making it FAT32 would do no harm.
--

Bit Twister

2016-06-12 07:21:52 UTC

This from Ubuntu i=16.04 if that's okay.
1 2048 1050623 512.0 MiB EF00 EFI System Partition
/dev/nvme0n1p1: TYPE="vfat" PARTLABEL="EFI System Partition"

vfat 512.0 MiB EF00 EFI System Partition
What I was looking into is what's used for a legacy bios boot which
requires this partition information for a "MBR install"
cleared 260+ MiB EF02=bios_grub

Mageia used to say: create a 300 Mb partition (the 260+.) Windows
creates one of 100 MB, and mine isn't nearly full. For the
filesystem, there is a specific one (use gdisk/fdisk, list
partitions, second screen, near the bottom) but FAT32 is good enough,
and what is usually recommended. Making it FAT32 would do no harm.

Forgot where I read it, but suggestion was to format it VFAT since all
bios can read VFAT. Good possibility Secure boot bios can read FAT32,
but I'll stick with a VFAT recommendation.

Post by dlbendigo
The "protective MBR" on Marek's listing is apparently created with
every EFI filesystem, according to the documentation, for
compatibility.

Just one more example of sticking with VFAT.

Post by dlbendigo
It crossed my mind that you don't dual-boot Windows,

Very true. Sticking with winders in a VirtualBox guest. :)

Post by dlbendigo
so the filesystem could perhaps be a Linux one.

You are a bit loose with the terminology for my problem.

The problem started when Mageia dropped grub legacy support
on clean installs on release 6. Only option is grub2.
Legacy grub users will still be using legacy if they upgrade.

All my systems are configured as legacy boot bios with MBR
install using GPT drives.

grub2 install requires either an efi or bios_grub partition when using
GPT drives.

Non-EFI users with drives setup as GPT will have to create the
bios_grub partition. Using gparted makes it really easy and much safer
than using (g,f)disk.

I clicked the last partition on /dev/sda, use the resize feature to
free up space for the 260+ partition, clicked the free space and set
partition type as "bios_grub" and format as "cleared".

mcc->Boot->Set up boot system where I selected grub2 graphical.
It converted from grub legacy to grub2 with no problems.

I thought the Probe for foreign OS was for dual boot doze/linux.
It is not. You need it checked if you have a multiboot
setup. Unchecked will only give you selections for the current install. :(

dlbendigo

2016-06-12 09:35:36 UTC

This from Ubuntu i=16.04 if that's okay.
1 2048 1050623 512.0 MiB EF00 EFI System Partition
/dev/nvme0n1p1: TYPE="vfat" PARTLABEL="EFI System Partition"

vfat 512.0 MiB EF00 EFI System Partition
What I was looking into is what's used for a legacy bios boot which
requires this partition information for a "MBR install"
cleared 260+ MiB EF02=bios_grub

Mageia used to say: create a 300 Mb partition (the 260+.) Windows
creates one of 100 MB, and mine isn't nearly full. For the
filesystem, there is a specific one (use gdisk/fdisk, list
partitions, second screen, near the bottom) but FAT32 is good enough,
and what is usually recommended. Making it FAT32 would do no harm.

Forgot where I read it, but suggestion was to format it VFAT since all
bios can read VFAT. Good possibility Secure boot bios can read FAT32,
but I'll stick with a VFAT recommendation.

Isn't that the same thing? I thought that VFAT was a more general
term for FA16 and FAT32. Anyway, it worked for you. The file type
shown in fdisk is similar, with a couple of extra characters. I am in
the middle of a major version update of Win10 at the moment. Their
partition manager calls the partition "EFI System Partition," but
that may be its function, not its file system.

Post by dlbendigo
The "protective MBR" on Marek's listing is apparently created with
every EFI filesystem, according to the documentation, for
compatibility.

Just one more example of sticking with VFAT.

Post by dlbendigo
It crossed my mind that you don't dual-boot Windows,

Very true. Sticking with winders in a VirtualBox guest. :)

Post by dlbendigo
so the filesystem could perhaps be a Linux one.

I didn't know that was possible. Dave said that updated Ext4 can't use
Legacy Grub, and all my partitions are Ext4 unless there is a good
reason
not to. Mageia were going to make btrfs the default. On a clean
install,
that may be already the case, but it wasn't so when I installed
Cauldron.

If you want a UEFI system, set your BIOS to boot your installation
media as
UEFI. The startup screen looks very different. Otherwise, you
will have a
BIOS-type installation. There are comparative screenshots somewhere.

Post by Bit Twister
grub2 install requires either an efi or bios_grub partition when using
GPT drives.
Non-EFI users with drives setup as GPT will have to create the
bios_grub partition. Using gparted makes it really easy and much safer
than using (g,f)disk.

You could do it with diskdrake, but it needs to be there before
you start to install.

Post by Bit Twister
I clicked the last partition on /dev/sda, use the resize feature to
free up space for the 260+ partition, clicked the free space and set
partition type as "bios_grub" and format as "cleared".
mcc->Boot->Set up boot system where I selected grub2 graphical.
It converted from grub legacy to grub2 with no problems.
I thought the Probe for foreign OS was for dual boot doze/linux.
It is not. You need it checked if you have a multiboot
setup. Unchecked will only give you selections for the current install. :(

True. It probes for other entries to go in your bootup menu. I
have a
DVDfor Android. I haven't got it to run properly, but the docs
say it can
be added to a Grub2 menu.
--

Bit Twister

2016-06-12 13:04:12 UTC

Post by Bit Twister
Forgot where I read it, but suggestion was to format it VFAT since all
bios can read VFAT. Good possibility Secure boot bios can read FAT32,
but I'll stick with a VFAT recommendation.

Isn't that the same thing?

Nope. gparted complained my partition was too small when attempting
vfat format, fat32 selection did not complain.

Post by dlbendigo
I am in
the middle of a major version update of Win10 at the moment. Their
partition manager calls the partition "EFI System Partition," but
that may be its function, not its file system.

That would be Partition Label and gdisk should show the EF00 Code
indicating a EFI/UEFI install.

Post by Bit Twister
All my systems are configured as legacy boot bios with MBR
install using GPT drives.

I didn't know that was possible.

Depends on the bios. My newest system had secure boot.
I had the salesman get into the bios menu on a few systems to see if
it could boot a legacy drive. That was an eye opener for me.
Some systems could not be accessed because the network was down. :(

Post by dlbendigo
Dave said that updated Ext4 can't use Legacy Grub, and all my
partitions are Ext4 unless there is a good reason not to.

Just to put your mind at ease on that point. All my Linux partitions
were created ext4 when I decided to go with GPT partitioned drives and
all are a few years old and my conversion from grub legacy to grub2
is working just fine on my test bed node.

Post by dlbendigo
Mageia were going to make btrfs the default. On a clean
install,
that may be already the case, but it wasn't so when I installed
Cauldron.

I'll stick with ext4. :)
I always partition/format/label my drives prior to any install and all
installs are a clean install.

Post by dlbendigo
If you want a UEFI system, set your BIOS to boot your installation
media as UEFI. The startup screen looks very different. Otherwise,
you will have a BIOS-type installation.

Post by Bit Twister
Non-EFI users with drives setup as GPT will have to create the
bios_grub partition. Using gparted makes it really easy and much safer
than using (g,f)disk.

You could do it with diskdrake, but it needs to be there before
you start to install.

Kinda makes you wonder how that statement is going to work when
someone picks the Use whole disk or had to replace their drive. :-D

<snip>

Post by dlbendigo
True. It probes for other entries to go in your bootup menu. I
have a DVDfor Android. I haven't got it to run properly, but the
docs say it can be added to a Grub2 menu.

Yup. It is just a simple matter of getting the image boot line
correct after you find it. :)

Spent an hour figuring out how to find then boot my systemrescue.iso stanza.

Maurice

2016-06-12 14:01:27 UTC

Post by Bit Twister
gdisk -l /dev/sda
blkid -s device -s LABEL -s TYPE -s PARTLABEL | sort -V

[***@probook ~]# gdisk -l /dev/sda
GPT fdisk (gdisk) version 0.8.10

The protective MBR's 0xEE partition is oversized! Auto-repairing.

Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 976773168 sectors, 465.8 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 7836D858-A36C-4A9B-8EBD-AF15D4AD5B3A
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 976773134
Partitions will be aligned on 2048-sector boundaries
Total free space is 672776173 sectors (320.8 GiB)

Number Start (sector) End (sector) Size Code Name
1 2048 739327 360.0 MiB EF00 EFI system partition
2 739328 1001471 128.0 MiB 0C01 Microsoft reserved ...
3 1001472 95338495 45.0 GiB 0700 Basic data partition
4 95338496 126943231 15.1 GiB 0700 Basic data partition
5 126943232 233418751 50.8 GiB 0700 Basic data partition
6 233418752 249937919 7.9 GiB 0700 Basic data partition
7 249937920 266070015 7.7 GiB 0700 Basic data partition
8 938833920 940584959 855.0 MiB 2700 Basic data partition
9 940584960 972568575 15.3 GiB 2700 Basic data partition
10 972568576 976762879 2.0 GiB 2700 Basic data partition

[***@probook ~]# blkid -s device -s LABEL -s TYPE -s PARTLABEL | sort -V
/dev/sda1: LABEL="SYSTEM" TYPE="vfat" PARTLABEL="EFI system partition"
/dev/sda2: PARTLABEL="Microsoft reserved partition"
/dev/sda3: LABEL="Windows" TYPE="ntfs" PARTLABEL="Basic data partition"
/dev/sda4: LABEL="Mageia-5-root" TYPE="ext4" PARTLABEL="Basic data partition"
/dev/sda5: LABEL="Mageia-5-home" TYPE="ext4" PARTLABEL="Basic data partition"
/dev/sda6: TYPE="swap" PARTLABEL="Basic data partition"
/dev/sda7: LABEL="photos" TYPE="ext4" PARTLABEL="Basic data partition"
/dev/sda8: LABEL="WINRE" TYPE="ntfs" PARTLABEL="Basic data partition"
/dev/sda9: LABEL="Recovery Image" TYPE="ntfs" PARTLABEL="Basic data partition"
/dev/sda10: LABEL="HP_TOOLS" TYPE="vfat" PARTLABEL="Basic data partition"
[***@probook ~]#

--
/\/\aurice
(Replace "nomail.afraid" by "bcs" to reply by email)

Bit Twister

2016-06-12 15:45:02 UTC

Post by Maurice

Post by Bit Twister
gdisk -l /dev/sda
blkid -s device -s LABEL -s TYPE -s PARTLABEL | sort -V

GPT fdisk (gdisk) version 0.8.10
The protective MBR's 0xEE partition is oversized! Auto-repairing.

Hmm, that did not look good.

Post by Maurice
Number Start (sector) End (sector) Size Code Name
1 2048 739327 360.0 MiB EF00 EFI system partition
2 739328 1001471 128.0 MiB 0C01 Microsoft reserved ...
3 1001472 95338495 45.0 GiB 0700 Basic data partition
4 95338496 126943231 15.1 GiB 0700 Basic data partition
5 126943232 233418751 50.8 GiB 0700 Basic data partition
6 233418752 249937919 7.9 GiB 0700 Basic data partition
7 249937920 266070015 7.7 GiB 0700 Basic data partition
8 938833920 940584959 855.0 MiB 2700 Basic data partition
9 940584960 972568575 15.3 GiB 2700 Basic data partition
10 972568576 976762879 2.0 GiB 2700 Basic data partition
/dev/sda1: LABEL="SYSTEM" TYPE="vfat" PARTLABEL="EFI system partition"
/dev/sda2: PARTLABEL="Microsoft reserved partition"
/dev/sda3: LABEL="Windows" TYPE="ntfs" PARTLABEL="Basic data partition"
/dev/sda4: LABEL="Mageia-5-root" TYPE="ext4" PARTLABEL="Basic data partition"
/dev/sda5: LABEL="Mageia-5-home" TYPE="ext4" PARTLABEL="Basic data partition"
/dev/sda6: TYPE="swap" PARTLABEL="Basic data partition"
/dev/sda7: LABEL="photos" TYPE="ext4" PARTLABEL="Basic data partition"
/dev/sda8: LABEL="WINRE" TYPE="ntfs" PARTLABEL="Basic data partition"
/dev/sda9: LABEL="Recovery Image" TYPE="ntfs" PARTLABEL="Basic data partition"
/dev/sda10: LABEL="HP_TOOLS" TYPE="vfat" PARTLABEL="Basic data partition"

Looking like your partition setup might be a bit old.

I noticed a few of the 'Code' values are incorrect or could be set to
more valid values. Just one example from my setup

gdisk line 1 2048 16386047 7.8 GiB 8200 swap
blkid line /dev/sdb1: LABEL="swap" TYPE="swap" PARTLABEL="swap"

Post by Maurice
/dev/sda6: TYPE="swap" PARTLABEL="Basic data partition"

Since you do not have the correct Code value for your swap partition
you blkid output does _NOT_ display the TYPE value of swap in the
above line. :-(

In my opinion your ext4 partitions Code 0700 should be 8300

You might also consider changing the PARTLABEL to something descriptive
besides Basic data partition.

Mine looked pretty much like yours until I changed the Code values to
match the partition type and while I was at it, I set the PARTLABEL to
match the LABEL values on my system.

I can recommend gparted for playing with partitions. You would right
click the desired partition and use Flags to change the 'Code' and
name partition to change the PARTLABEL field.

I can recommend the systemrescuecd iso from http://www.sysresccd.org/Download
If you use it, third icon bottom right is gparted.

To install on a USB thumb drive I used the
B) Recommended USB installation method from Linux
instructions from
http://www.system-rescue-cd.org/Sysresccd-manual-en_How_to_install_SystemRescueCd_on_an_USB-stick

Advantage of that is; it contains a newer release of gparted than Mageia 5
which does not have the Name Partition feature/function.

Pretty sure it is going to be fairly hard to make your root/home
changes while they are mounted. :)

Maurice

2016-06-12 18:02:59 UTC

Post by Bit Twister
I noticed a few of the 'Code' values are incorrect or could be set to
more valid values.

Thanks for the headsup, but - being a Taurean - I'm not wanting to
change something that works in case the result doesn't...

--
/\/\aurice (Currently on the somewhat soggy coast of Picardy)
(Replace "nomail.afraid" by "bcs" to reply by email)

Bit Twister

2016-06-12 19:28:21 UTC