You are not logged in.
~ ❯ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 1 0B 0 disk
zram0 253:0 0 4G 0 disk [SWAP]
nvme0n1 259:0 0 238.5G 0 disk
├─nvme0n1p1 259:1 0 100M 0 part
├─nvme0n1p2 259:2 0 16M 0 part
├─nvme0n1p3 259:3 0 68.4G 0 part
├─nvme0n1p4 259:4 0 772M 0 part
└─nvme0n1p5 259:5 0 169.2G 0 part /
~ ❯ lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda
zram0 swap 1 zram0 a034298b-eb2a-45ce-89f0-28504c34eb1a [SWAP]
nvme0n1
├─nvme0n1p1 vfat FAT32 B2B0-C7F5
├─nvme0n1p2
├─nvme0n1p3 BitLocker 2 428da671-c9a8-446b-ab83-d59b75d471c9
├─nvme0n1p4 ntfs BC9252749252335E
└─nvme0n1p5 ext4 1.0 d58d7076-4468-43e6-a7c3-72a528f5b9e6 120.8G 22% /This is my first arch installation more than a month ago. I did it to dual boot with windows 11 just in case if I might need it. But it has come to my attention that the partitions is not entirely correct. Now it does work on dual boot. But I don't know if this is something I need to worry about or not.
Last edited by Surtrz (2026-05-26 18:11:33)
Offline
What are you worried about concretely? This will generally work fine if you want to retain the ability to boot Windows, space will likely be a bit tight there, but there's generally not too much available. Depending on how and which bootloader you picked you might have to ensure p1 is mounted to /boot, but if you used e.g. GRUB and configured it properly it will be able to read the kernel image off of the ext4 partition and that will generally work fine.
Last edited by V1del (2026-05-26 17:42:10)
Online
I was worried if windows 11 would overwrite GRUB if it gets an update.
Last edited by Surtrz (2026-05-26 17:56:41)
Offline
It "should"™ not, most often it's your mainboard that reacts allergic to Windows adding it's entry and might potentially remove existing ones, but that can relatively easily be fixed. Windows itself hasn't really changed or manipulated this in any way (case in point I have a dual boot on UEFI systems since 11 years and never had problems with this)
Online
fine - for the sake of providing a proper answer:
windows causing trouble with other bootloaders is a real risk and a common issue
it mostly depends on how exactly you setup your bootloader and how well your systems firmware implementation behave
if you have setup your bootloader as <ESP>\Boot\BOOT<arch>.EFI it's pretty much guaranteed to get overwritten as windows will do so (although M$ is one of the big players in the uefi group - they violate the rules they agreed upon)
if you have setup your bootloader anywhere else it should be fine
as for "disappearing boot entry": depending on how your systems firmware is implemented it CAN happen that by starting windows it will either change or overwrite the boot order
you MIGHT get around by chain windows from the linux bootloader instead of starting it directly from the uefi selection - but there's no guarantee for this and highly depends on the uefi
// F5'ed ...
Last edited by cryptearth (2026-05-26 18:07:41)
Offline
I was worried it would mess up grub and I won't be able to boot to arch or windows.
Offline