Slackware64-current fdisk linux partition type 22 instead of 83 and named 'Linux root' instead of 'Linux'

gdiazlo · 04-22-2020, 03:31 PM

Hello

Installting slackware64 current today, I found that fdisk partition type for Linux partition has changed its type and its label and the installation scripts does not figure out this, so It does not format the target partition nor recognize it for mounting in /mnt.

The current fdisk label is "Linux root (x86_64)" instead of just "Linux". I think the installation scripts should allow this naming scheme.

The relevant code seems to be in /usr/lib/setup line 53, the grep should probably check for 'Linux root' instead of 'Linux$'

As a workaround mounting the target partition before setup in /mnt ends with a correct installation.

Alien Bob · 04-22-2020, 03:45 PM

Quote:

Originally Posted by gdiazlo

Hello

Installting slackware64 current today, I found that fdisk partition type for Linux partition has changed its type and its label and the installation scripts does not figure out this, so It does not format the target partition nor recognize it for mounting in /mnt.

The current fdisk label is "Linux root (x86_64)" instead of just "Linux". I think the installation scripts should allow this naming scheme.

The relevant code seems to be in /usr/lib/setup line 53, the grep should probably check for 'Linux root' instead of 'Linux$'

As a workaround mounting the target partition before setup in /mnt ends with a correct installation.

You selected the wrong partition type then. Type 22 is not meant for Desktop Linux partitions. Use 83.

gdiazlo · 04-22-2020, 03:56 PM

Quote:

Originally Posted by Alien Bob

You selected the wrong partition type then. Type 22 is not meant for Desktop Linux partitions. Use 83.

The fdisk on util-linux 2.35.1 (as stated by fdisk --version) on slackware64 current identifies type 83 as VMWare Virtual San. There is only one type for Linux that I can identify which is the type 24 Linux root (x86-64) or 22 (Linux root (x86). Using cfdisk I see the parition type is named the same.

Do I have a wrong version of fdisk? I have the package util-linux-2.25-1-x86_64-4 installed.

Alien Bob · 04-22-2020, 04:14 PM

Quote:

Originally Posted by gdiazlo

The fdisk on util-linux 2.35.1 (as stated by fdisk --version) on slackware64 current identifies type 83 as VMWare Virtual San. There is only one type for Linux that I can identify which is the type 24 Linux root (x86-64) or 22 (Linux root (x86). Using cfdisk I see the parition type is named the same.

Do I have a wrong version of fdisk? I have the package util-linux-2.25-1-x86_64-4 installed.

I don't know what's the matter with your computer but here is a fdisk print of a Slackware64-current machine, and Linux is definitely type 83 here:

Code:

Welcome to fdisk (util-linux 2.35.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.


Command (m for help): p
Disk /dev/sda: 931.53 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: HGST HTS721010A9
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: dos
Disk identifier: 0xdc35c071

Device     Boot      Start        End    Sectors   Size Id Type
/dev/sda1  *          2048     411647     409600   200M 83 Linux
/dev/sda2           411648 1951422463 1951010816 930.3G 83 Linux
/dev/sda3       1951422464 1953519615    2097152     1G 82 Linux swap

Command (m for help):

gdiazlo · 04-22-2020, 05:09 PM

I never saw it before. Did you tried to toggle the linux type to see if type 83 is still on the list? I just did a fresh install on my home system, and know I can't select type 83 when creating the partition, just those I mentioned.

Quote:

Originally Posted by Alien Bob

I don't know what's the matter with your computer but here is a fdisk print of a Slackware64-current machine, and Linux is definitely type 83 here:

Code:

Welcome to fdisk (util-linux 2.35.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.


Command (m for help): p
Disk /dev/sda: 931.53 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: HGST HTS721010A9
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: dos
Disk identifier: 0xdc35c071

Device     Boot      Start        End    Sectors   Size Id Type
/dev/sda1  *          2048     411647     409600   200M 83 Linux
/dev/sda2           411648 1951422463 1951010816 930.3G 83 Linux
/dev/sda3       1951422464 1953519615    2097152     1G 82 Linux swap

Command (m for help):

kingbeowulf · 04-29-2020, 09:16 PM

gdiazlo, are you sure you are not confusing MSDOS with GPT partition tables? Alien Bob's response is correct for MSDOS partitions. I have a mix or both on my main box.

Code:

Command (m for help): p
Disk /dev/sda: 465.78 GiB, 500107862016 bytes, 976773168 sectors
Disk model: WDC WD5000AAKX-0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: CBB027CE-BFCB-48A3-ABE0-D541040F3285

Device         Start       End   Sectors   Size Type
/dev/sda1       2048    206847    204800   100M EFI System
/dev/sda2     206848 167979007 167772160    80G Linux filesystem
/dev/sda3  167979008 976773134 808794127 385.7G Linux filesystem

...

Command (m for help): p
Disk /dev/sdb: 931.53 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC WD10EZEX-00B
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: dos
Disk identifier: 0x000d40f4

Device     Boot      Start        End   Sectors   Size Id Type
/dev/sdb1             2048  972333055 972331008 463.7G 83 Linux
/dev/sdb3        972333056 1951428607 979095552 466.9G 83 Linux
/dev/sdb4       1951428608 1953523711   2095104  1023M 82 Linux swap

cwizardone · 04-29-2020, 09:44 PM

Here you go:

kingbeowulf · 04-29-2020, 10:13 PM

for GPT partitions (via cfdisk) you'll see this.

gdiazlo · 04-30-2020, 01:54 AM

I can see it from an installed system, but was unable to see it when the system had no partitions and I was installing it. I need to double check this, probably my faulty eyes I suppose.

Also I don't remember seeing the Linux root, Linux home, Linux reserved partition types before, I suppose those lead me to confusion. Because I see now the type 22 I was referring to seems to be the order of the list, not the partition type, as it used to be. I guess partition types are something of the past, and UUIDs and names is what we should be using now.

Thanks for taking a look at it.

Didier Spaier · 04-30-2020, 04:54 AM

Quote:

Originally Posted by gdiazlo

I can see it from an installed system, but was unable to see it when the system had no partitions and I was installing it. I need to double check this, probably my faulty eyes I suppose.

Also I don't remember seeing the Linux root, Linux home, Linux reserved partition types before, I suppose those lead me to confusion. Because I see now the type 22 I was referring to seems to be the order of the list, not the partition type, as it used to be. I guess partition types are something of the past, and UUIDs and names is what we should be using now.

Thanks for taking a look at it.

Partition types will not go away any time soon. UUIDs can be used for partitions as well as for file systems, but software that deal with partitions use partition types rather than partitions UUID because they are shorter, thus easier to type or select. What can be confusing is that the partition types (written as numbers) and names vary across tools.