if by that you mean nvme0n1p1 then it is set as esp and boot
Been a while but after checking it would be
Boot - nvme0n1p1
Root - nvme0n1p11
Home - sda2
I haven’t done anything with the space, so it is still unallocated where nvme 2 and 4-10 was previously
If I did it may be lost to time
Ok.
When it comes to resizing partitions, there is always a risk, but in my experience its pretty darn small since I have not had any trouble with it for years. But there is a minimal risk.
Unless you in the very close future use that space, I would recommend you use gparted, unmount the drives and resize root partition to not having free space before or after.
I will assume you know how to do this otherwise tell me and I hold your hand a bit.
OR if you prefer not doing it at all, tell me and we move forward.
not fussed at expanding it at the moment, but if needed or when the time arises I can do.
If needed I do have storage space off of that pc and/ extra drives if needed to dump stuff off.
No problem, I was asking because now would be a perfect environment to add the space to root, you wont be able to do that if you have it mounted.
Also had the idea to help you name your partitions so they have names in dolphin instead of nvme0n1p11. But no worries, lets move on.
Unmount everything you have mounted in dolphin.
And mount root, in terminal:
sudo mount /dev/nvme0n1p11 /mnt
Then make sure UUID of root, home, boot and swap are the same in fstab.
sudo nano /mnt/etc/fstab
If you have questions, feel free to ask.
Made an assumption that it would be, as there was no matching flags and nothing was mentioned in the past but I should not assume.
Never even occurred to me that it would be a thing but as i was under the impression that is was meant to be somewhat static, similar to uuid for things like fstab.
Would like to learn about it and if there are any good practices for them.
They all match
Just label the filesystems in gparted with the name you want them to have. I think you named your boot to ESP f.ex.
Lets try with manjaro-chroot and see how it reacts, but before that, unmount root from /mnt
sudo umount /mnt
sudo manjaro-chroot -a
Edit
In the future, instead of saying “they are the same” press the </> and then pate something to confirm the fact, in this case your fstab file.
SO much easier for us here giving support to ACTUALLY confirm. It’s not about not trusting you, there can be small errors you did not think of. 
Not sure how or when it happened
You are right, (Im guessing) hand waiving got me into this mess in the first place
devil is in the detail
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=F7CE-D10A /boot/efi vfat umask=0077 >
UUID=b2683235-d9b1-4a6f-b0fb-141a1ced512c / ext4 noatime >
UUID=480d2b75-9789-4800-b8ad-764019c85d26 /home ext4 noatime >
UUID=8a065abc-8719-4231-9f15-03d795b01065 swap swap noatime >
tmpfs /tmp tmpfs noatime,mode=1777 >
//192.168.10.90/Media /home/waffel360/nas/Media cifs rw,uid=1000,gid=1000,user=waffel360,vers=3.0,noauto,noserverino,x-systemd.automount,x-systemd.mount-timeout=30,_netdev,credentials=/home/waffel360/nas/smbcred 0 0
UUID=67E3-17ED none vfat users
.
==> Detected systems:
--> 0) ManjaroLinux
--> 1) ManjaroLinux1
==> Select system to mount [0-1] :
Yepp, what is this?
Remount root to /mnt, edit your fstab and comment that line out (put a # in front of it). Unmount and retry chroot
Checked after saving and this it as conformation
#UUID=67E3-17ED none vfat users
but after I still get the following
~ sudo mount /dev/nvme0n1p11 /mnt INT ✘ 1m 19s
~ sudo nano /mnt/etc/fstab ✔
~ sudo umount /mnt ✔ 3m 49s
~ sudo manjaro-chroot -a ✔
==> Detected systems:
--> 0) ManjaroLinux
--> 1) ManjaroLinux1
==> Select system to mount [0-1] :
Not sure exactly how manjaro-chroot -a tag works so lets do it manually.
sudo mount /dev/nvme0n1p11 /mnt
sudo mount /dev/nvme0n1p1 /mnt/boot/efi
sudo manjaro-chroot /mnt /bin/bash
It will probably complain not finding a home, but we don’t care about that right now.
You can find the procedure here, and the next we are going to do awell if this works here
worked
sudo mount /dev/nvme0n1p11 /mnt ✔
sudo mount /dev/nvme0n1p1 /mnt/boot/efi
sudo manjaro-chroot /mnt /bin/bash
[manjaro /]#
[manjaro /]# pacman -Syu grub
:: Synchronizing package databases...
core 146.6 KiB 239 KiB/s 00:01 [############################] 100%
extra 8.6 MiB 1151 KiB/s 00:08 [############################] 100%
community 29.0 B 349 B/s 00:00 [############################] 100%
multilib 145.0 KiB 929 KiB/s 00:00 [############################] 100%
:: Some packages should be upgraded first...
resolving dependencies...
looking for conflicting packages...
Packages (3) archlinux-keyring-20231113-1 manjaro-keyring-20230719-2
manjaro-system-20230401-1
Total Download Size: 1.26 MiB
Total Installed Size: 1.72 MiB
Net Upgrade Size: -0.58 MiB
:: Proceed with installation? [Y/n]
:: Retrieving packages...
archlinux-keyring-2... 1173.6 KiB 2.00 MiB/s 00:01 [############################] 100%
manjaro-keyring-202... 84.7 KiB 576 KiB/s 00:00 [############################] 100%
manjaro-system-2023... 29.0 KiB 223 KiB/s 00:00 [############################] 100%
Total (3/3) 1287.2 KiB 888 KiB/s 00:01 [############################] 100%
(3/3) checking keys in keyring [############################] 100%
(3/3) checking package integrity [############################] 100%
(3/3) loading package files [############################] 100%
(3/3) checking for file conflicts [############################] 100%
(3/3) checking available disk space [############################] 100%
:: Running pre-transaction hooks...
(1/1) Creating Timeshift snapshot before upgrade...
==> skipping timeshift-autosnap due skipRsyncAutosnap in /etc/timeshift-autosnap.conf set to TRUE.
:: Processing package changes...
(1/3) upgrading archlinux-keyring [############################] 100%
==> Appending keys from archlinux.gpg...
==> Locally signing trusted keys in keyring...
-> Locally signed 1 keys.
==> Importing owner trust values...
gpg: inserting ownertrust of 4
==> Disabling revoked keys in keyring...
-> Disabled 7 keys.
==> Updating trust database...
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 1 signed: 21 trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1 valid: 21 signed: 95 trust: 0-, 0q, 0n, 21m, 0f, 0u
gpg: depth: 2 valid: 73 signed: 27 trust: 73-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2023-12-31
==> Delete expired Key by Jonas Strassel
==> Updating trust database...
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 1 signed: 21 trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1 valid: 21 signed: 95 trust: 0-, 0q, 0n, 21m, 0f, 0u
gpg: depth: 2 valid: 73 signed: 27 trust: 73-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2023-12-31
==> Delete expired Key by Jonas Strassel
==> ERROR: The key identified by A44C644D792767CED7941AFEABB2075D5F310CF8 could not be found locally.
error: command failed to execute correctly
(2/3) upgrading manjaro-keyring [############################] 100%
==> Appending keys from manjaro.gpg...
==> Locally signing trusted keys in keyring...
-> Locally signed 2 keys.
==> Importing owner trust values...
gpg: setting ownertrust to 4
==> Updating trust database...
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 1 signed: 22 trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1 valid: 22 signed: 95 trust: 0-, 0q, 0n, 22m, 0f, 0u
gpg: depth: 2 valid: 73 signed: 27 trust: 73-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2023-12-31
(3/3) upgrading manjaro-system [############################] 100%
==> Checking for 'os-prober' setup ...
'os-prober' was already enabled by the user.
:: Running post-transaction hooks...
(1/3) Reloading system manager configuration...
Skipped: Running in chroot.
(2/3) Arming ConditionNeedsUpdate...
(3/3) Refreshing PackageKit...
Error connecting: Could not connect: No such file or directory
error: command failed to execute correctly
:: Starting full system upgrade...
:: Replace appstream-qt with extra/appstream-qt5? [Y/n]
:: Replace attica with extra/attica5? [Y/n]
:: Replace baloo with extra/baloo5? [Y/n]
:: Replace bluez-qt with extra/bluez-qt5? [Y/n]
:: Replace frameworkintegration with extra/frameworkintegration5? [Y/n]
:: Replace kactivities with extra/kactivities5? [Y/n]
:: Replace kactivities-stats with extra/kactivities-stats5? [Y/n]
:: Replace karchive with extra/karchive5? [Y/n]
:: Replace kauth with extra/kauth5? [Y/n]
:: Replace kbookmarks with extra/kbookmarks5? [Y/n]
:: Replace kcmutils with extra/kcmutils5? [Y/n]
:: Replace kcodecs with extra/kcodecs5? [Y/n]
:: Replace kcompletion with extra/kcompletion5? [Y/n]
:: Replace kconfig with extra/kconfig5? [Y/n]
:: Replace kconfigwidgets with extra/kconfigwidgets5? [Y/n]
:: Replace kcontacts with extra/kcontacts5? [Y/n]
:: Replace kcoreaddons with extra/kcoreaddons5? [Y/n]
:: Replace kcrash with extra/kcrash5? [Y/n]
:: Replace kdbusaddons with extra/kdbusaddons5? [Y/n]
:: Replace kdeclarative with extra/kdeclarative5? [Y/n]
:: Replace kded with extra/kded5? [Y/n]
:: Replace kdesu with extra/kdesu5? [Y/n]
:: Replace kdnssd with extra/kdnssd5? [Y/n]
:: Replace kdoctools with extra/kdoctools5? [Y/n]
:: Replace kdsoap with extra/kdsoap-qt5? [Y/n]
:: Replace kfilemetadata with extra/kfilemetadata5? [Y/n]
:: Replace kglobalaccel with extra/kglobalaccel5? [Y/n]
:: Replace kguiaddons with extra/kguiaddons5? [Y/n]
:: Replace kholidays with extra/kholidays5? [Y/n]
:: Replace ki18n with extra/ki18n5? [Y/n]
:: Replace kiconthemes with extra/kiconthemes5? [Y/n]
:: Replace kidletime with extra/kidletime5? [Y/n]
:: Replace kimageformats with extra/kimageformats5? [Y/n]
:: Replace kio with extra/kio5? [Y/n]
:: Replace kitemmodels with extra/kitemmodels5? [Y/n]
:: Replace kitemviews with extra/kitemviews5? [Y/n]
:: Replace kjobwidgets with extra/kjobwidgets5? [Y/n]
:: Replace knewstuff with extra/knewstuff5? [Y/n]
:: Replace knotifications with extra/knotifications5? [Y/n]
:: Replace knotifyconfig with extra/knotifyconfig5? [Y/n]
:: Replace kpackage with extra/kpackage5? [Y/n]
:: Replace kparts with extra/kparts5? [Y/n]
:: Replace kpeople with extra/kpeople5? [Y/n]
warning: kpeoplevcard: local (0.1+r38.32d50a9-1) is newer than extra (0.1-2)
:: Replace kpty with extra/kpty5? [Y/n]
:: Replace kquickcharts with extra/kquickcharts5? [Y/n]
:: Replace krunner with extra/krunner5? [Y/n]
:: Replace kservice with extra/kservice5? [Y/n]
:: Replace ktexteditor with extra/ktexteditor5? [Y/n]
:: Replace ktextwidgets with extra/ktextwidgets5? [Y/n]
:: Replace kunitconversion with extra/kunitconversion5? [Y/n]
:: Replace kuserfeedback with extra/kuserfeedback5? [Y/n]
:: Replace kwallet with extra/kwallet5? [Y/n]
:: Replace kwayland with extra/kwayland5? [Y/n]
:: Replace kwidgetsaddons with extra/kwidgetsaddons5? [Y/n]
:: Replace kwindowsystem with extra/kwindowsystem5? [Y/n]
:: Replace kxmlgui with extra/kxmlgui5? [Y/n]
:: Replace libkdcraw with extra/libkdcraw5? [Y/n]
:: Replace libqaccessibilityclient with extra/libqaccessibilityclient-qt5? [Y/n]
:: Replace mangohud-common with extra/mangohud? [Y/n]
:: Replace modemmanager-qt with extra/modemmanager-qt5? [Y/n]
:: Replace networkmanager-qt with extra/networkmanager-qt5? [Y/n]
:: Replace plasma-framework with extra/plasma-framework5? [Y/n]
:: Replace prison with extra/prison5? [Y/n]
:: Replace purpose with extra/purpose5? [Y/n]
:: Replace qqc2-desktop-style with extra/qqc2-desktop-style5? [Y/n]
:: Replace solid with extra/solid5? [Y/n]
:: Replace sonnet with extra/sonnet5? [Y/n]
:: Replace syndication with extra/syndication5? [Y/n]
:: Replace syntax-highlighting with extra/syntax-highlighting5? [Y/n]
:: Replace tbb with extra/onetbb? [Y/n]
:: Replace texlive-core with extra/texlive-basic? [Y/n]
:: Replace threadweaver with extra/threadweaver5? [Y/n]
resolving dependencies...
:: There are 2 providers available for glfw:
:: Repository extra
1) glfw-wayland 2) glfw-x11
Enter a number (default=1):
Ok, I guess I did not tell you, but, DO NOT DO STUFF NOT TOLD TO DO!
Tell me if it worked or not. All I wanted was to help you sort out so you can boot. the Update procedure is a whole other thing.
You might just have made things worse for yourself, but maybe you are lucky. We’ll see.
We need to reinstall grub.
So tell me the end result, what you did was to sync to a database and update your whole system, without a home. NO idea how manjaro will do things then.
You then tried to reinstall grub, that is allready installed. What we have to do is install grub to the PARTITION. It’s in the wiki I just posted.
But tell me the end result and we go from there, again… :-/
Sorry that was the next one on my screen
One possible cause why you are reading this document - is an unfinished update - which in turn can be caused by several situations - situation we will not dive into. To fix what ever caused this you should run a full system update including grub to ensure everything is in place.
root # pacman -Syu grub COPY TO CLIPBOARD
When the transaction as completed continue below using the section matching your system
You want me to ctrl + c as I haven’t confirmed wayland or x11?
ok, good.
Since you are allready running as root, there is no need for you should not use sudo.
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck
grub-mkconfig -o /boot/grub/grub.cfg
I think it runs an update-grub, but just to be sure, run update-grub anyway.
Then type exit, cross your fingers, reboot (and remove your usb) and make sure your bios detects the partition and boot into your manjaro.
:: There are 2 providers available for glfw:
:: Repository extra
1) glfw-wayland 2) glfw-x11
Enter a number (default=1): ^C
Interrupt signal received
[manjaro /]# grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck
grub-mkconfig -o /boot/grub/grub.cfg
Installing for x86_64-efi platform.
EFI variables are not supported on this system.
EFI variables are not supported on this system.
grub-install: error: efibootmgr failed to register the boot entry: No such file or directory.
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.19-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.19-x86_64.img
Found initrd fallback image: /boot/initramfs-5.19-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.15-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.15-x86_64.img
Found initrd fallback image: /boot/initramfs-5.15-x86_64-fallback.img
Found linux image: /boot/vmlinuz-4.19-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.19-x86_64.img
Found initrd fallback image: /boot/initramfs-4.19-x86_64-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
ERROR: mkdir /var/lock/dmraid
Found Manjaro Linux (21.3.6) on /dev/nvme0n1p3
Root filesystem isn't btrfs
If you think an error has occurred, please file a bug report at "https://github.com/Antynea/grub-btrfs"
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
done
[manjaro /]# update-grub
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.19-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.19-x86_64.img
Found initrd fallback image: /boot/initramfs-5.19-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.15-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.15-x86_64.img
Found initrd fallback image: /boot/initramfs-5.15-x86_64-fallback.img
Found linux image: /boot/vmlinuz-4.19-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.19-x86_64.img
Found initrd fallback image: /boot/initramfs-4.19-x86_64-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Found Manjaro Linux (21.3.6) on /dev/nvme0n1p3
Root filesystem isn't btrfs
If you think an error has occurred, please file a bug report at "https://github.com/Antynea/grub-btrfs"
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
done
[manjaro /]#
I think it will work, but the first thing you have to do is make sure you sort out your kernels, some are old lts and are fine. Make sure to NOT boot into 5.19, that one is gone.
Hold shift while booting and the grub menu should show.
You can also edit /etc/default/grub and make sure following is included in the file:
GRUB_TIMEOUT=5
GRUB_TIMEOUT_STYLE=menu
Then update-grub (with sudo if not in chroot/live usb) and menu will be visible for 5s each boot.
Edit
This ladies and gentlemen is why you ALWAYS use UUID or PARTUUID instead of /dev
In the uefi boot menu both
UEFI OS (WDS500G2X0C-00L350)
and
WDS500G2X0C-00L350
show
error: unknown filesystem.
Entering rescue mode...
grub rescue>
only difference being “UEFI OS” one is a slightly more appropriate resolution for the screen
And you DID format the boot partition before we started correct?
Wait, I trolled myself, it finds the manjaro on that partition (3), not the 11. What exactly is on that one?
On 11?
root
on partition 3?
Edit
Ah, I get it, its another manjaro install, you have 2.
THAT’S why chroot acted that way.