Most likely you experimented with different Linux distributions and somehow that messed up your Grub config in the ESP, which selects the partition to use for finding it’s other config files.
Check the contents of grub.cfg inside the ESP directory where grub is started…
To check which grub is used to boot you can check with:
efibootmgr --verbose
Also keep in mind to always use UUID in that config instead of hd2 and similar…
Disk /dev/sda: 223.57 GiB, 240057409536 bytes, 468862128 sectors
Disk model: KINGSTON SV300S3
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: 6417DBB6-7CE4-3548-B55D-6D731B19974E
Device Start End Sectors Size Type
/dev/sda1 321538048 468856991 147318944 70.2G Linux swap
/dev/sda2 2048 321538047 321536000 153.3G Linux filesystem
Partition table entries are not in disk order.
Disk /dev/sdb: 74.51 GiB, 80000000000 bytes, 156250000 sectors
Disk model: ST380815AS
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: dos
Disk identifier: 0xc8e73050
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 2048 1187839 1185792 579M 7 HPFS/NTFS/exFAT
/dev/sdb2 1187840 156246015 155058176 73.9G 7 HPFS/NTFS/exFAT
Disk /dev/nvme0n1: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: WDS500G2X0C-00L350
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: BEE49EBE-AC08-4F84-926F-D695E5160D07
Device Start End Sectors Size Type
/dev/nvme0n1p1 34 4196351 4196318 2G EFI System
/dev/nvme0n1p2 4196352 12584959 8388608 4G EFI System
/dev/nvme0n1p3 12584960 548937727 536352768 255.8G Linux filesystem
/dev/nvme0n1p4 548937728 550021119 1083392 529M Windows recovery environment
/dev/nvme0n1p5 550021120 550225919 204800 100M EFI System
/dev/nvme0n1p6 550225920 551309311 1083392 529M Windows recovery environment
/dev/nvme0n1p7 551309312 551514111 204800 100M EFI System
/dev/nvme0n1p8 551514112 552597503 1083392 529M Windows recovery environment
/dev/nvme0n1p9 552597504 552802303 204800 100M EFI System
/dev/nvme0n1p10 729634816 730861566 1226751 599M EFI System
/dev/nvme0n1p11 730861567 976773134 245911568 117.3G Linux filesystem
Disk /dev/sdc: 14.42 GiB, 15483273216 bytes, 30240768 sectors
Disk model: DataTraveler 2.0
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: DE81451B-B5E8-4BDA-ACC9-9DD0F9CC0005
Device Start End Sectors Size Type
/dev/sdc1 2048 4095 2048 1M BIOS boot
/dev/sdc2 4096 2101247 2097152 1G Linux filesystem
/dev/sdc3 2101248 30238719 28137472 13.4G Linux filesystem
Disk /dev/mapper/ubuntu--vg-ubuntu--lv: 13.41 GiB, 14403239936 bytes, 28131328 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
and /etc/fstab
contains the following
# /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=0C93-8D63 /boot/efi vfat umask=0077 0 2
UUID=b2683235-d9b1-4a6f-b0fb-141a1ced512c / ext4 noatime 0 1
UUID=480d2b75-9789-4800-b8ad-764019c85d26 /home ext4 noatime 0 2
UUID=8a065abc-8719-4231-9f15-03d795b01065 swap swap noatime 0 0
tmpfs /tmp tmpfs noatime,mode=1777 0 0
//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
That is a total mess…
Each Drive should only contain 1 single EFI Partition if at all, all the rest won’t be recognized by your UEFI-BIOS as boot medium normally…
Can you provide the contents of /tmp/uuids.txt after performing the following command: (Don’t edit stuff of the contents while pasting here)
ls -la /dev/disk/by-{partuuid,uuid} > /tmp/uuids.txt
No in your case it would be /boot/efi/EFI/Manjaro/grub.cfg if such file exists…
Actually it’s the file /EFI/Manjaro/grub.cfg inside the $ESP, but you have so many we need to find the ESP first…
The used ESP is most likely (99.99%) your /dev/nvme0n1p1 partition…
I agree
Over the course of learning, systems have become unusable (audio has completely stopped except for remote desktop streaming or the computer shuts down after 20~25 minutes and so on) and I needed a computer to work or apply for jobs and such, so I needed to do it at the time but I still had open tabs and and such I wanted to recover but haven’t known how so I avoided the problem.
I have spent time learning other areas on Linux, so I have not known how to merge grub’s/
and I previously duel booted windows but that was causing so much chaos (and I got comfortable with Linux) so I stopped using windows.
I have not touched partitions (other than shrinking them) as I don’t know what will break things.
both /boot/efi/EFI/Manjaro/grub.cfg /EFI/Manjaro/grub.cfg
does not exist
however there is an efi binary /boot/efi/EFI/Manjaro/grubx64.efi
(can post if needed).
There is nothing else in the /boot/efi/EFI/Manjaro/ tree
Ill try to reply again tomorrow as it is past midnight now here.
Until then think about what you like to do:
A Total wipe of your SSD and start from scratch using a fresh GPT partitioning and new partitions?
Want to manually copy over stuff from one partition on your SSD to another one on same SSD.
Plus remove the Micro$@$ partitions. This will be a LONG and HARD job…
With the info from my previous reply we can conclude:
We only have to consider these SSD partitions from your current system:
/dev/nvme0n1p2 for the kernel, initrd and as ESP.
/dev/nvme0n1p11 for your root filesystem
All the EFI-type partitions on the SSD should be merged into /dev/nvme0n1p1 because that is the only one that an UEFI-BIOS will consider by default. (It only considers the first ESP per device)
See: The UEFI-Bios section of my tutorial.
All the Micro$@$ specific partitions on the SSD can be removed because we wont use that OS… This will gain us at least 529*3= 1587MB [±1.5GB] plus possibly 3*100MB from the related EFI partitions, totaling ±1.8GB.
To accomplish these tasks we should be using a LIVE-USB to boot.
That way we can backup stuff from one place to another on the SSD without crippling the system we work on.
Things to do:
Temporarily mount /dev/nvme0n1p11 somewhere so we can modify it as needed.
Temporarily mount all the ESP’s on the SSD in turn, to copy their contents into a sub-dir of (1).
Delete all partitions on the SSD EXCEPT/dev/nvme0n1p11 which will hold our current system and EFI backups.
Create a new /dev/nvme0n1p1 as ESP partition, with enough space to hold the contents of the EFI backups in (2) This needs to be a FAT32 partition.
Create a new /dev/nvme0n1p2 as root filesystem partition to hold everything from /dev/nvme0n1p11 minus the EFI backups. I would suggest formatting this partition as a BTRFS filesystem as it will be easier to expand. But that is your own choice…
Change the fstab of the new system in /dev/nvme0n1p2 to use:
/dev/nvme0n1p1 as /boot/efi
/dev/nvme0n1p2 as root filesystem /.
Configure and use sd-boot as bootloader in /dev/nvme0n1p1 to help initial booting into the new system because it is way easier to configure as Grub until we are able to regenerate the Grub config.
Change the UEFI-BIOS boot entry, to use /dev/nvme0n1p1 as boot partition, using efibootmgr and the bootloader to use.
Chroot into /dev/nvme0n1p1 and regenerate the initrd so the above changes will be used while booting.
Try to boot from (8) and fix eventual problems that went wrong.
If all went “Okay” we can delete /dev/nvme0n1p11 and enlarge /dev/nvme0n1p2 to use all available space left on the SSD.
As you can see this is a hard road to walk and is your choice if you don’t want to start with a fresh install after resetting the SSD’s partitioning.
I need to learn at some point so no better time and I am happy to learn as much as I can.
So I have been reading through the The UEFI-Bios
and have learned things from it but there was nothing about rebuilding or merging partition.
So far I have the following remaining
the first EFI boot should be FAT, however the first EFI boot should be FAT, however nvme0n1p1 is ext4 so based on that I should not be able to boot however, it now tries to boot into my old manjaro system (I can tell as its manjaro loading screen would always not render in the correct resolution) but never manages to, so I am more lost as there are no FAT partitions on any drive in the system.
I have been trying to do the list of thing to do but have been getting stuck
So far I have wiped nvme0n1p1 and replaced it with a FAT32 partition and have updated the fstab (I believe correctly)
I was intending to keep both nvme0n1p3 and nvme0n1p11 for the moment(I am only working on fixing nvme0n1p11 for the moment to not complicate things).
I am unsure of what sd-boot is
I am unsure of what sd-boot is but I am booting into a majaro live system so cant I use that to boot and then manjaro-chroot in to it?
on both live and chroot when putting efibootmgr I get the following.
EFI variables are not supported on this system.
when looking this up almost every result is redhat related (and account locked) and the ones that dont say to use something called dracut?
I havent been able to do some of the prevous steps so got grub rescue
but when entering
I now get
error: file '/boot/grub/i386-pc/normal.mod' not found.
fdisk -l
now gives the following
Disk /dev/sda: 223.57 GiB, 240057409536 bytes, 468862128 sectors
Disk model: KINGSTON SV300S3
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: 6417DBB6-7CE4-3548-B55D-6D731B19974E
Device Start End Sectors Size Type
/dev/sda1 321538048 468856991 147318944 70.2G Linux swap
/dev/sda2 2048 321538047 321536000 153.3G Linux filesystem
Partition table entries are not in disk order.
Disk /dev/nvme0n1: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: WDS500G2X0C-00L350
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: BEE49EBE-AC08-4F84-926F-D695E5160D07
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 8390655 8388608 4G EFI System
/dev/nvme0n1p3 12584960 548937727 536352768 255.8G Linux filesystem
/dev/nvme0n1p11 730861567 976773134 245911568 117.3G Linux filesystem
Disk /dev/sdc: 115.5 GiB, 124017180672 bytes, 242221056 sectors
Disk model: DataTraveler 3.0
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: dos
Disk identifier: 0x3e951a66
Device Boot Start End Sectors Size Id Type
/dev/sdc1 * 2048 242155519 242153472 115.5G 7 HPFS/NTFS/exFAT
/dev/sdc2 242155520 242221055 65536 32M ef EFI (FAT-12/16/32)
Disk /dev/mapper/ventoy: 3.57 GiB, 3837536256 bytes, 7495188 sectors
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: dos
Disk identifier: 0x00000000
Device Boot Start End Sectors Size Id Type
/dev/mapper/ventoy-part1 * 64 7486995 7486932 3.6G 0 Empty
/dev/mapper/ventoy-part2 7486996 7495187 8192 4M ef EFI (FAT-12/16/32)
Disk /dev/loop0: 29.7 MiB, 31137792 bytes, 60816 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop1: 896.48 MiB, 940027904 bytes, 1835992 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop2: 1.87 GiB, 2007453696 bytes, 3920808 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop3: 739.35 MiB, 775262208 bytes, 1514184 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
and /etc/fstab
contains the following
# /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 0 2
UUID=b2683235-d9b1-4a6f-b0fb-141a1ced512c / ext4 noatime 0 1
UUID=480d2b75-9789-4800-b8ad-764019c85d26 /home ext4 noatime 0 2
UUID=8a065abc-8719-4231-9f15-03d795b01065 swap swap noatime 0 0
tmpfs /tmp tmpfs noatime,mode=1777 0 0
//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
