Strange install on ssd

looks strange, i have 2 unalocated parts for no reason, and is it normal that boot partition is that big. i went with default recommendation. what is the optimal boot partition size?

Nothing looks too strange to me…
First off - the unallocated at the front I assume to be aligning the sectors to a given byte boundary to enable simple usage for different file systems.
The second is quite small, actually - it is MiB not GiB. This is actually a good size for the boot/efi, as you not likely to run out!
The main system covers everything else, and should work fine. If you need/want to split stuff off (on another drive?) it is easily done, and explained on request.
The final chunk I am not sure, but I suspect the same reason - it is so small that it can’t be used with the block size of your chosen file system.
Hope this helps - or an actual expert may be along with a better explanation!

so almost one gigabyte is a good size… what would be a small amount then? when i installed garuda on another computer, on a 2tb ssd, it defaulted on 300 mb fat32 and the rest btrfs, and here is 250gb ssd and i got almost one gb fat32 and the rest btrfs

While 300 is a workable size, and 500 is fine, having more leaves room for the unexpected. One such thing might be the addition of other systems without needing another efi partition. With one that large, you COULD add several should you ever wish to…

My almost two years old EOS installation also shows a 300 MiB /boot/efi partition, so maybe the recommended size changed since then. And i got these small unallocated areas as well.

EndeavourOS switched from mkinitcpio to dracut during that time. One thing I have noticed is dracut tends to create bigger images because it includes more stuff.

1 Gig is definitely a good size if you are using dracut. I tried to manually convert from mkinitcpio to dracut and my efi partition was simply too small for the images dracut was creating. I didn’t wanna reinstall, so I decided to stick with mkinitcpio


so do you need to reinstall os to change partition size, can it be done after in kde partition manager? im getting a bit nervous that the other system that i have that boot partition would be too small

You can do it without reinstalling. It is just riskier and slower because it involves growing and shrinking partitions.

Yeah you can do it after the fact, but backup all your data before doing so. Also it is recommended to do this from a live image and not the currently running system.

aha. and how do i do it? boot live usb than go into kde partition manager and do something there?

Some unallocated space at the end of the disk is need for the GPT, else you would maybe get warnings about corrupted GPT when the file system wrote there, and the file system data would get corrupted when GPT was fixed.

I’m not a user of KDE Partition Manager, so don’t know how it handles that, and it could also just be an artifact of how the installer installed the disk anyway.

From what I have heard, NVidia drivers can take 100s of MiB for initrds, so 1GiB for EFI is a reasonable default choice, it not what you want. I guess you could fine tune that choice on install depending upon your selections, or you could reorg the partitions with gparted live USB post install, or you could not bother and leave it alone which I think is the smartest option.

1 Like

Yeah pretty much. This isn’t something that I would do though, so I am not familiar with the steps. Perhaps you can adapt this guide for gparted to kde partition manager if you are dead set on using that.

oh yes, another thing, when installing there is option no swap and something other swap enable i dont know, i chose that swap enable, what is the deal with that and what is best?

You are probably referring to the swap option in the installer. Swap space is disk space that is reserved for use as system memory to be used in conjunction with your system’s physical ram. A lot of programs expect at least some amount of swap space, so the best thing is to make sure that you have some. As for how much. that has been debated for quite some time. If you plan to use the hibernate and or sleep functions of the OS though. It is recommended to set swap space to be equal to the amount of physical ram.

Yes. If you are choosing systemd-boot, the installer defaults to a 1000 MB for ESP.

That is because the ESP in this case will house your kernel images and depending on how many kernels you have installed, how the images are generated and what is included in them (as the mentioned Nvidia drivers) they can take up some good amount of space.

I would suggest to leave it as is for not running into issues later on.

1 Like

well i chose grub when installing but i think it installed sysd anyway, so im little lost there… so when someone picks grub instead how large would be optimal?

If that is what has actually happened, I would suggest to file a bug report and provide the install log for the developers to look into.

Here is the ArchWiki’s recommendation:

this is how it looks like when the system boots, is this sysd or grub? looks like sysd, i installed before(then i reinstalled with grub checked) with sysd checked and it looked like that

That is Grub.
You can also see that in the top right of the screen.

hahaha, well officialy im dumb, i was totaly focusing on the highligted text there… what also confused me i have setup snapshots, like i have on garuda, and i don’t see that option when booting