[SOLVED] Setup program not recognizing partition table correctly

turtlebeach · 06-18-2023, 10:03 AM

I'm trying to install slackware 15.0 on my nvme drive, and I keep running into this issue where the setup program doesn't recognize the swap partition that I created with fdisk.

When I print the partition table, I get:

Code:

Disk /dev/nvme0n1p1: 465.76 GiB, 500106788864 bytes, 976771072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimal/optimal): 512 bytes / 512 bytes
Disklabel thpe: gpt
Disk identifier: D5FEF1AB-D461-8245-92F9-BB95C4AE1A2B

Device                 Start       End   Sectors  Size Type
/dev/nvme0n1p1p1        2048 954206207 954204160  455G Linux Filesystem
/dev/nvme0n1p1p2   954206208 976771038  22564831 10.8G Linux Swap

I can write the changes to disk just fine, it appears the same way in cfdisk, but when I run the setup program and select ADDSWAP I get a message saying I didn't set up a swap partition.

I've tried switching the order of the filesystem and swap partitions, leaving those 10.8G free with the intention of formatting it to swap after I'm done installing, and trying the same thing but setting the type to various other partition types, and the setup program still only see one 466G linux filesystem partition.

michaelk · 06-18-2023, 12:05 PM

Welcome to LinuxQuestions.

Quote:

Disk /dev/nvme0n1p1
Device Start End Sectors Size Type
/dev/nvme0n1p1p1 2048 954206207 954204160 455G Linux Filesystem
/dev/nvme0n1p1p2 954206208 976771038 22564831 10.8G Linux Swap

It looks like you created partitions within an existing partition. while partitioning tools allow you to do this it does not work in operation. Is this a dual boot computer? How is it partitioned? Post the output of the command

fdisk -l /dev/nvme0n1

turtlebeach · 06-18-2023, 01:47 PM

Quote:

Originally Posted by michaelk

It looks like you created partitions within an existing partition.

Thanks, that seems to be exactly the issue.

I'm not dual booting, so I'm not sure how that happened, but creating the filesystem/swap partitions on /dev/nvme0n1 worked.