Partitioning Ubuntu 24.04.2 after last bug resolved

Asked by Nick Mortel

On my last fixed issue for gdm3-fails-to-start-after-package-updates-in-ubuntu-24-04 which was resolved by Manfred Hampl I now am at a loss as to what sizes I should make my partitions on my drive to give my pc more space.

GParted was not used during install of Ubuntu 24.04.2 and in time I arrived at my last resolved/fixed bug. Thanks Manfred.

Now I am unsure of what sizes to give each partition for best performance/efficiency of my system.

On GParted it lists the following.......
Partition Name Filesystem Mount Point Label Size Used Unused (No Flags)
/dev/nvme1n1p1 EFI fat32 /boot/efi 'EFI System 600MiB 27.07MiB 572.93MiB boot, esp
/dev/nvme1n1p2 fat32 PQSERVICE 5.80GiB --- --- boot, esp
/dev/nvme1n1p3 - ext4 / 1.86TiB 482.90GiB 1.39TiB
(key symbol)

This is all confusing to me - I also have another partition called /dev/nvme0n1p1 MS reserved partition unknown 128.00MiB with 1.86TiB unallocated which carries this warning flag on it - Unable to detect filesystem! Possible reasons are:
- The filesystem is damaged
- The filesystem is unknown to GParted
- There is no filesystem available (unformatted)
- The device entry /dev/nvme0n1p1 is missing

/dev/nvme/1n1p2 above carries the same Warning on it.

lsblk - NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 1 976.6G 0 disk
├─sda1 8:1 1 5.9G 0 part
├─sda2 8:2 1 5M 0 part
└─sda3 8:3 1 300K 0 part
nvme0n1 259:0 0 1.9T 0 disk
└─nvme0n1p1 259:1 0 128M 0 part
nvme1n1 259:2 0 1.9T 0 disk
├─nvme1n1p1 259:3 0 600M 0 part /boot/efi
├─nvme1n1p2 259:4 0 5.8G 0 part
└─nvme1n1p3 259:5 0 1.9T 0 part /

lsblk -f -
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda iso966 Jolie Ubuntu 24.04.2 LTS amd64 2025-02-15-09-15-26-00
├─sda1
│ iso966 Jolie Ubuntu 24.04.2 LTS amd64 2025-02-15-09-15-26-00
├─sda2
│ vfat FAT12 ESP B5A5-8010
└─sda3

nvme0n1

└─nvme0n1p1

nvme1n1

├─nvme1n1p1
│ vfat FAT32 'EFI System 8C6E-FEE8 572.9M 4% /boot/efi
├─nvme1n1p2
│ vfat FAT32 PQSERVICE 8C81-6C92
└─nvme1n1p3
     ext4 1.0 f3528e7c-d2f5-4ee1-b340-e9805b012a6a 1.3T 24% /

sudo fdisk -l -
Disk /dev/nvme0n1: 1.86 TiB, 2048408248320 bytes, 4000797360 sectors
Disk model: SAMSUNG MZVL22T0HDLB-00BLL
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: 5B9130C2-CC7C-4F2B-8CA6-0631BA01703C

Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 264191 262144 128M Microsoft reserved

Disk /dev/nvme1n1: 1.86 TiB, 2048408248320 bytes, 4000797360 sectors
Disk model: SAMSUNG MZVL22T0HDLB-00BLL
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: 2EB3F19D-552A-4DC9-851D-D3404AF49B0E

Device Start End Sectors Size Type
/dev/nvme1n1p1 2048 1230847 1228800 600M EFI System
/dev/nvme1n1p2 1230848 13394327 12163480 5.8G EFI System
/dev/nvme1n1p3 13395968 4000796671 3987400704 1.9T Linux filesystem

GPT PMBR size mismatch (12389099 != 2047999999) will be corrected by write.
The backup GPT table is not on the end of the device.

Disk /dev/sda: 976.56 GiB, 1048576000000 bytes, 2048000000 sectors
Disk model: ProductCode
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: B0EF6CA3-60D1-4A21-98D9-17C385A8B6F8

Device Start End Sectors Size Type
/dev/sda1 64 12378291 12378228 5.9G Microsoft basic data
/dev/sda2 12378292 12388435 10144 5M EFI System
/dev/sda3 12388436 12389035 600 300K Microsoft basic data

sudo parted -l
Warning: Not all of the space available to /dev/sda appears to be used, you can
fix the GPT to use all of the space (an extra 2035610900 blocks) or continue
with the current setting?
Fix/Ignore? Fix
Model: VendorCo ProductCode (scsi)
Disk /dev/sda: 1049GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
 1 32.8kB 6338MB 6338MB ISO9660 hidden, msftdata
 2 6338MB 6343MB 5194kB Appended2 boot, esp
 3 6343MB 6343MB 307kB Gap1 hidden, msftdata

Model: SAMSUNG MZVL22T0HDLB-00BLL (nvme)
Disk /dev/nvme0n1: 2048GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
 1 1049kB 135MB 134MB Microsoft reserved partition msftres

Model: SAMSUNG MZVL22T0HDLB-00BLL (nvme)
Disk /dev/nvme1n1: 2048GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
 1 1049kB 630MB 629MB fat32 EFI boot, esp
 2 630MB 6858MB 6228MB fat32 boot, esp
 3 6859MB 2048GB 2042GB ext4

I have now tutored myself on GParted via this youtube video https://www.youtube.com/watch?v=Q1vybl1X3_s

Would you have any recommendations for sizing my partitions please. I am not too sure what sizes I should give and would my allocating /home partition on my other drive be advisable as it does contain many books, magazines, whitepapers which is ever growing and so taking up some space. I think I can then place a link to that drive on my desktop for ease and quick reference access.
Your thoughts greatly appreciated.

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Nick Mortel (sludgemariner) said :
#1

I only have Ubuntu on my Lenovo ThinkStation P3 Tiny although Windows is mentioned on one of the partitions (Do not know why).

Revision history for this message
Nick Mortel (sludgemariner) said :
#2

Nothing heard or question acknowledgement not received yet.

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#3

The Microsoft Reserved Partition (MSR) is a special partition created on hard drives using the GUID Partition Table (GPT) layout. It's required by Windows for proper functioning and is used for internal purposes, such as managing partitions and storing boot files. It doesn't contain user data and isn't assigned a drive letter.

Key points about the MSR:
Purpose: The MSR is used by the operating system for various functions, including partition management and storing boot files.

Size: The MSR typically has a size of 16MB on GPT disks.

Visibility: It is usually hidden and not accessible to the user.

Necessity: While it's not essential for everyday use, it's important for tasks like system recovery and updates.

Not for User Data: The MSR does not store any user files or data.

GPT Requirement: It's a part of the GPT disk layout and is created during the initial disk partitioning.

Why is it important?
Partition Management: The MSR assists in the management of other partitions on the drive.

Boot Files: It can store boot files necessary for the operating system to start.

System Recovery: It plays a role in system recovery and repair operations.

Updates and Upgrades: It can be involved in the update and upgrade processes of the Windows operating system.

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#4

I think you can just ignore it. Looks like some GPT fluff from when Windows on it

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#5

Others may know better. I just used AI

:)

Can you help with this problem?

Provide an answer of your own, or ask Nick Mortel for more information if necessary.

To post a message you must log in.