I edited the file like you suggested. That didn’t seem to change anything.
I have been adjusting the boot order selecting GRUB first then windows second whenever I’ve been testing out these changes. When I change it to windows first it boots (unsurprisingly) into windows. I’ve also had to adjust the boot priority when booting into the live USB. In other words, I don’t think boot priority is the main issue.
Those error messages are expected in the liveUSB environment. What looks problematic for me is the lack of found kernels in that message. For example, in my system I get this:
[...]
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-6.5-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.5-x86_64.img
Found initrd fallback image: /boot/initramfs-6.5-x86_64-fallback.img
Found linux image: /boot/vmlinuz-6.1-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.1-x86_64.img
Found initrd fallback image: /boot/initramfs-6.1-x86_64-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
[...]
What do you have in /boot/?
ls -al /boot/
I’m sorry, I live in Sweden, I went to bed.
After reading through, it seems your chroot is not working otherwise it looks fine other than you missed the “boot” flag, you need to add that, and I actually forgot the “esp” flag. The drive has to be unmounted when you do it so do it before chroot.
I now also realized KDE partition manager won’t show all flags, so use Gparted (should also be included on your live usb)
Right click your boot partition and choose “manage flags”.
Your mounts seems correct, did your chroot not return any errors? You DID use sudo right or change to root? (the wiki is a bit weird, they use the user “root” instead of using sudo so it can be missed)
When you have loaded the live ISO - depending on environment - open a terminal and switch to root context. Use above mentioned root:password combination.
user $ su
Yes, but neither kernels exists nor grub is in the correct place on that boot partition (only the grub boot code is there, nothing from grub).
Example of my /boot (your might not look exactly the same but the kernels and grub directory is there)
/boot
├── amd-ucode.img
├── efi
│ └── EFI
│ └── manjaro
│ └── grubx64.efi
├── grub
│ ├── fonts
│ │ └── unicode.pf2
│ ├── grub-btrfs.cfg
│ ├── grub.cfg
│ ├── grubenv
│ ├── locale
│ │ ├── ast.mo
│ │ ├── ca.mo
│ │ ├── da.mo
│ │ ├── de.mo
│ │ ├── de@hebrew.mo
│ │ ├── de_CH.mo
│ │ ├── en@arabic.mo
│ │ ├── en@cyrillic.mo
│ │ ├── en@greek.mo
│ │ ├── en@hebrew.mo
│ │ ├── en@piglatin.mo
│ │ ├── en@quot.mo
│ │ ├── eo.mo
│ │ ├── es.mo
│ │ ├── fi.mo
│ │ ├── fr.mo
│ │ ├── gl.mo
│ │ ├── hr.mo
│ │ ├── hu.mo
│ │ ├── id.mo
│ │ ├── it.mo
│ │ ├── ja.mo
│ │ ├── ka.mo
│ │ ├── ko.mo
│ │ ├── lg.mo
│ │ ├── lt.mo
│ │ ├── nb.mo
│ │ ├── nl.mo
│ │ ├── pa.mo
│ │ ├── pl.mo
│ │ ├── pt.mo
│ │ ├── pt_BR.mo
│ │ ├── ro.mo
│ │ ├── ru.mo
│ │ ├── sl.mo
│ │ ├── sr.mo
│ │ ├── sv.mo
│ │ ├── tr.mo
│ │ ├── uk.mo
│ │ ├── vi.mo
│ │ ├── zh_CN.mo
│ │ └── zh_TW.mo
│ ├── themes
│ │ └── starfield
│ │ ├── COPYING.CC-BY-SA-3.0
│ │ ├── README
│ │ ├── blob_w.png
│ │ ├── boot_menu_c.png
│ │ ├── boot_menu_e.png
│ │ ├── boot_menu_n.png
│ │ ├── boot_menu_ne.png
│ │ ├── boot_menu_nw.png
│ │ ├── boot_menu_s.png
│ │ ├── boot_menu_se.png
│ │ ├── boot_menu_sw.png
│ │ ├── boot_menu_w.png
│ │ ├── dejavu_10.pf2
│ │ ├── dejavu_12.pf2
│ │ ├── dejavu_14.pf2
│ │ ├── dejavu_16.pf2
│ │ ├── dejavu_bold_14.pf2
│ │ ├── slider_c.png
│ │ ├── slider_n.png
│ │ ├── slider_s.png
│ │ ├── starfield.png
│ │ ├── terminal_box_c.png
│ │ ├── terminal_box_e.png
│ │ ├── terminal_box_n.png
│ │ ├── terminal_box_ne.png
│ │ ├── terminal_box_nw.png
│ │ ├── terminal_box_s.png
│ │ ├── terminal_box_se.png
│ │ ├── terminal_box_sw.png
│ │ ├── terminal_box_w.png
│ │ └── theme.txt
│ └── x86_64-efi
│ ├── acpi.mod
│ ├── adler32.mod
│ ├── affs.mod
│ ├── afs.mod
│ ├── afsplitter.mod
│ ├── ahci.mod
│ ├── all_video.mod
│ ├── aout.mod
│ ├── appleldr.mod
│ ├── archelp.mod
│ ├── at_keyboard.mod
│ ├── ata.mod
│ ├── backtrace.mod
│ ├── bfs.mod
│ ├── bitmap.mod
│ ├── bitmap_scale.mod
│ ├── bli.mod
│ ├── blocklist.mod
│ ├── boot.mod
│ ├── boottime.mod
│ ├── bsd.mod
│ ├── bswap_test.mod
│ ├── btrfs.mod
│ ├── bufio.mod
│ ├── cacheinfo.mod
│ ├── cat.mod
│ ├── cbfs.mod
│ ├── cbls.mod
│ ├── cbmemc.mod
│ ├── cbtable.mod
│ ├── cbtime.mod
│ ├── chain.mod
│ ├── cmdline_cat_test.mod
│ ├── cmp.mod
│ ├── cmp_test.mod
│ ├── command.lst
│ ├── configfile.mod
│ ├── core.efi
│ ├── cpio.mod
│ ├── cpio_be.mod
│ ├── cpuid.mod
│ ├── crc64.mod
│ ├── crypto.lst
│ ├── crypto.mod
│ ├── cryptodisk.mod
│ ├── cs5536.mod
│ ├── ctz_test.mod
│ ├── date.mod
│ ├── datehook.mod
│ ├── datetime.mod
│ ├── disk.mod
│ ├── diskfilter.mod
│ ├── div.mod
│ ├── div_test.mod
│ ├── dm_nv.mod
│ ├── echo.mod
│ ├── efi_gop.mod
│ ├── efi_uga.mod
│ ├── efifwsetup.mod
│ ├── efinet.mod
│ ├── efitextmode.mod
│ ├── ehci.mod
│ ├── elf.mod
│ ├── eval.mod
│ ├── exfat.mod
│ ├── exfctest.mod
│ ├── ext2.mod
│ ├── extcmd.mod
│ ├── f2fs.mod
│ ├── fat.mod
│ ├── file.mod
│ ├── fixvideo.mod
│ ├── font.mod
│ ├── fs.lst
│ ├── fshelp.mod
│ ├── functional_test.mod
│ ├── gcry_arcfour.mod
│ ├── gcry_blowfish.mod
│ ├── gcry_camellia.mod
│ ├── gcry_cast5.mod
│ ├── gcry_crc.mod
│ ├── gcry_des.mod
│ ├── gcry_dsa.mod
│ ├── gcry_idea.mod
│ ├── gcry_md4.mod
│ ├── gcry_md5.mod
│ ├── gcry_rfc2268.mod
│ ├── gcry_rijndael.mod
│ ├── gcry_rmd160.mod
│ ├── gcry_rsa.mod
│ ├── gcry_seed.mod
│ ├── gcry_serpent.mod
│ ├── gcry_sha1.mod
│ ├── gcry_sha256.mod
│ ├── gcry_sha512.mod
│ ├── gcry_tiger.mod
│ ├── gcry_twofish.mod
│ ├── gcry_whirlpool.mod
│ ├── geli.mod
│ ├── gettext.mod
│ ├── gfxmenu.mod
│ ├── gfxterm.mod
│ ├── gfxterm_background.mod
│ ├── gfxterm_menu.mod
│ ├── gptsync.mod
│ ├── grub.efi
│ ├── gzio.mod
│ ├── halt.mod
│ ├── hashsum.mod
│ ├── hdparm.mod
│ ├── hello.mod
│ ├── help.mod
│ ├── hexdump.mod
│ ├── hfs.mod
│ ├── hfsplus.mod
│ ├── hfspluscomp.mod
│ ├── http.mod
│ ├── iorw.mod
│ ├── iso9660.mod
│ ├── jfs.mod
│ ├── jpeg.mod
│ ├── json.mod
│ ├── keylayouts.mod
│ ├── keystatus.mod
│ ├── ldm.mod
│ ├── legacy_password_test.mod
│ ├── legacycfg.mod
│ ├── linux.mod
│ ├── linux16.mod
│ ├── loadbios.mod
│ ├── loadenv.mod
│ ├── loopback.mod
│ ├── ls.mod
│ ├── lsacpi.mod
│ ├── lsefi.mod
│ ├── lsefimmap.mod
│ ├── lsefisystab.mod
│ ├── lsmmap.mod
│ ├── lspci.mod
│ ├── lssal.mod
│ ├── luks.mod
│ ├── luks2.mod
│ ├── lvm.mod
│ ├── lzopio.mod
│ ├── macbless.mod
│ ├── macho.mod
│ ├── mdraid09.mod
│ ├── mdraid09_be.mod
│ ├── mdraid1x.mod
│ ├── memdisk.mod
│ ├── memrw.mod
│ ├── minicmd.mod
│ ├── minix.mod
│ ├── minix2.mod
│ ├── minix2_be.mod
│ ├── minix3.mod
│ ├── minix3_be.mod
│ ├── minix_be.mod
│ ├── mmap.mod
│ ├── moddep.lst
│ ├── modinfo.sh
│ ├── morse.mod
│ ├── mpi.mod
│ ├── msdospart.mod
│ ├── mul_test.mod
│ ├── multiboot.mod
│ ├── multiboot2.mod
│ ├── nativedisk.mod
│ ├── net.mod
│ ├── newc.mod
│ ├── nilfs2.mod
│ ├── normal.mod
│ ├── ntfs.mod
│ ├── ntfscomp.mod
│ ├── odc.mod
│ ├── offsetio.mod
│ ├── ohci.mod
│ ├── part_acorn.mod
│ ├── part_amiga.mod
│ ├── part_apple.mod
│ ├── part_bsd.mod
│ ├── part_dfly.mod
│ ├── part_dvh.mod
│ ├── part_gpt.mod
│ ├── part_msdos.mod
│ ├── part_plan.mod
│ ├── part_sun.mod
│ ├── part_sunpc.mod
│ ├── partmap.lst
│ ├── parttool.lst
│ ├── parttool.mod
│ ├── password.mod
│ ├── password_pbkdf2.mod
│ ├── pata.mod
│ ├── pbkdf2.mod
│ ├── pbkdf2_test.mod
│ ├── pcidump.mod
│ ├── pgp.mod
│ ├── plainmount.mod
│ ├── play.mod
│ ├── png.mod
│ ├── priority_queue.mod
│ ├── probe.mod
│ ├── procfs.mod
│ ├── progress.mod
│ ├── raid5rec.mod
│ ├── raid6rec.mod
│ ├── random.mod
│ ├── rdmsr.mod
│ ├── read.mod
│ ├── reboot.mod
│ ├── regexp.mod
│ ├── reiserfs.mod
│ ├── relocator.mod
│ ├── romfs.mod
│ ├── scsi.mod
│ ├── search.mod
│ ├── search_fs_file.mod
│ ├── search_fs_uuid.mod
│ ├── search_label.mod
│ ├── serial.mod
│ ├── setjmp.mod
│ ├── setjmp_test.mod
│ ├── setpci.mod
│ ├── sfs.mod
│ ├── shift_test.mod
│ ├── signature_test.mod
│ ├── sleep.mod
│ ├── sleep_test.mod
│ ├── smbios.mod
│ ├── spkmodem.mod
│ ├── squash4.mod
│ ├── strtoull_test.mod
│ ├── syslinuxcfg.mod
│ ├── tar.mod
│ ├── terminal.lst
│ ├── terminal.mod
│ ├── terminfo.mod
│ ├── test.mod
│ ├── test_blockarg.mod
│ ├── testload.mod
│ ├── testspeed.mod
│ ├── tftp.mod
│ ├── tga.mod
│ ├── time.mod
│ ├── tpm.mod
│ ├── tr.mod
│ ├── trig.mod
│ ├── true.mod
│ ├── udf.mod
│ ├── ufs1.mod
│ ├── ufs1_be.mod
│ ├── ufs2.mod
│ ├── uhci.mod
│ ├── usb.mod
│ ├── usb_keyboard.mod
│ ├── usbms.mod
│ ├── usbserial_common.mod
│ ├── usbserial_ftdi.mod
│ ├── usbserial_pl2303.mod
│ ├── usbserial_usbdebug.mod
│ ├── usbtest.mod
│ ├── video.lst
│ ├── video.mod
│ ├── video_bochs.mod
│ ├── video_cirrus.mod
│ ├── video_colors.mod
│ ├── video_fb.mod
│ ├── videoinfo.mod
│ ├── videotest.mod
│ ├── videotest_checksum.mod
│ ├── wrmsr.mod
│ ├── xfs.mod
│ ├── xnu.mod
│ ├── xnu_uuid.mod
│ ├── xnu_uuid_test.mod
│ ├── xzio.mod
│ ├── zfs.mod
│ ├── zfscrypt.mod
│ ├── zfsinfo.mod
│ └── zstd.mod
├── initramfs-6.1-x86_64-fallback.img
├── initramfs-6.1-x86_64.img
├── initramfs-6.6-x86_64-fallback.img
├── initramfs-6.6-x86_64.img
├── linux61-x86_64.kver
├── linux66-x86_64.kver
├── memtest86+
│ ├── memtest.bin
│ └── memtest.efi
├── vmlinuz-6.1-x86_64
└── vmlinuz-6.6-x86_64
11 directories, 370 files
We have to establish that your chroot is going through correctly first.
Then install kernels
Then grub.
Then update system via terminal.
I don’t know, your default grub is certainly not the current default. It is missing GRUB_TIMEOUT_STYLE=menu for example which is why you do not see the grub menu. Add it and then update grub. (revert the changes from bg405 before)
You have to select manjaro (or probably manjaro-grub as you name it so) from the uefi.
If that is the chrooted boot, i mean the hard drive and not the usb.
That is why i guessed he is somehow running update-grub on the usb drive and not on the mounted/chrooted install, as bedna also suggests.
1 Like
At least in the KDE ISO, it looks like this:
/boot
├── amd-ucode.img
├── grub
│ └── grubenv
├── intel-ucode.img
├── linux65-x86_64.kver
├── memtest86+
│ ├── memtest.bin
│ └── memtest.efi
└── vmlinuz-6.5-x86_64
So it doesn’t look like it. It seems to me that, for some reason, he has not any kernels installed.
That is most likely because he just created the new boot partition.
The second we know OP has fixed the flags and chroot working, installing kernel can be found in the link I posted earlier.
He might have installed grub without any kernels present, maybe it only adds the efi then, I simply do not know.
That is why I keep repeating it is very important to know everything is setup correctly before starting to install stuff. And then, install in correct order: kernel > grub > system update
I hope not. Why would he do that at all. If that is the case either he or you doesn’t make the difference between /boot and ESP.
Anyways, the big question is if he has a working chroot. If he has, it is not hard to install some kernel with mhwd or pacman and then update grub and see if it appears in the newly un-hidden grub menu. Actually he will see if it is detected even before from the output of update-grub, which will not be as empty as now.
You should probably re-read the thread if you ask that.
I think that OP made the desition not wanting to deal with this constantly when windows breaks grub on the shared boot partition. At least that is what I am assuming until I see otherwise from OP.
Now we know it officially - you do not make a difference between boot and esp partition. (Hint: kernels have no place on an ESP).
1 Like
That is actually true, I did not think about that. Witch tells us the chroot does NOT go through correctly, the kernels are installed in /boot not /boot/efi.
Exactly. Note that i think he cut out the output of the tree command and forgot to provide ls command output. But if it is really that empty at /boot, something else is wrong. Either not correctly chrooting, ot it is the wrong mount, or he really has no kernels installed. Which will be strange because he did not mention interrupted update or disk problems, and those are pretty much the only ways to lose a kernel.
Ok, lets go with that assumption.
@tcd To give clear instructions on what to do.
Load into your live usb.
Use Gparted to set flags on the new partition.
Chroot and type lsblk to show what gets mounted and where.
On your system, sudo chroot -a should work but it probably will mount the old windows partition instead of the new one, but please do this so we KNOW what is going on exactly. I think it is better to start there.
If chroot -a does not work, do the manual way but please report what errors you get when using the -a option.
If you get into chroot and the wrong boot partition is mounted, we go from there, but we HAVE to know we are working with the correct things here.
Prelude
Thank you all for the help. I will try and be very verbose with these next steps.
Boot Flags and Chroot
-
Open Gparted and set the flags of the newly created partition as boot and esp
-
Open a terminal (KDE Konsole Application) and type:
sudo chroot -achroot: invalid option -- 'a' Try 'chroot --help' for more information.sudo manjaro-chroot -agrub-probe: error: cannot find a GRUB drive for /dev/sda1. Check your device.map. grub-probe: error: cannot find a GRUB drive for /dev/sda1. Check your device.map. ==> Mounting (ManjaroLinux) [/dev/nvme0n1p7] --> mount: [/mnt] --> mount: [/mnt/boot/efi] --> mount: [/mnt/home]lsblkNAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS loop0 7:0 0 71.2M 1 loop loop1 7:1 0 1.2G 1 loop loop2 7:2 0 1.7G 1 loop loop3 7:3 0 668.7M 1 loop sda 8:0 1 29.3G 0 disk |-sda1 8:1 1 3.6G 0 part `-sda2 8:2 1 4M 0 part nvme0n1 259:0 0 476.9G 0 disk |-nvme0n1p1 259:11 0 650M 0 part /boot/efi |-nvme0n1p2 259:12 0 128M 0 part |-nvme0n1p3 259:13 0 280G 0 part |-nvme0n1p4 259:14 0 899M 0 part |-nvme0n1p5 259:15 0 12.1G 0 part |-nvme0n1p6 259:16 0 1.1G 0 part |-nvme0n1p7 259:17 0 48G 0 part / |-nvme0n1p8 259:18 0 76G 0 part /home |-nvme0n1p9 259:19 0 4G 0 part `-nvme0n1p10 259:20 0 100M 0 part
Clarifying
-
I like the idea of having windows and grub bootloaders on separate partitions if “quarantining” them in this way will help resolve future complications.
-
Before the issues with grub started happening I did experience an interrupted update as described in my original post:
-
The output of this command was indeed truncated. I don’t remember the specifics, but the reason I posted the truncated output of
tree /bootwas because I thought only the first few lines were relevant and the output was many times longer. Is there a more accepted way of showing the output of code was truncated perhaps doing something like:/boot |-- efi | `-- EFI | `-- Manjaro-GRUB | `-- grubx64.efi [...](patterning it after the output @cfinnberg provided in an earlier post)
VERY good post, all posts should look like this! xD
A broken update is not good.
As I expected your windows boot gets mounted, lets change that.
To do that we edit fstab, I forgot to ask for -f with lsblk, but unless you removed it, I think it should be the same as before. But you can double check with lsblk -f. Change the boot line to the new UUID
Never use sudo INSIDE chroot, you are logged in as root.
$ nano /etc/fstab
---------------------------
UUID=438E-DBD6 /boot/efi vfat umask=0077
Now exit chroot by typing exit and then enter chroot again (good job with that btw, I totally forgot manjaro-chroot not chroot)
Make sure the NEW partition, #10 is mounted as /boot/efi by checking lsblk
Install kernel anyway, I do not know what you had so I will use 6.1 LTS in this example, change to the kernels you use (remember, no sudo inside chroot).
As a reminder so you don’t have to scroll in the thread: Manjaro Kernels - Manjaro
Read through and understand what you are doing.
mhwd-kernel -i linux61
Then grub:
$ grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck
$ grub-mkconfig -o /boot/grub/grub.cfg
Check GRUB/Restore the GRUB Bootloader - Manjaro and read through it so you understand what you are doing, even if you don’t have to do everything, you might want to do some checks that stuff worked.
Then do an update on your system and pray to… someone it works.
pacman-mirrors -f && pacman -Syu
I would not be surprised if there is errors in the update process since we now know that a broken update was the cause. But let’s start here, maybe we are lucky.
I am partway through those instructions. I figured it would be better to double check before proceeding further as making bad assumptions got me in this mess in the first place 
.
Steps Thus Far
lsblk -f
We were trying to find/verify the UUID ofNAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS loop0 loop1 loop2 loop3 sda |-sda1 `-sda2 nvme0n1 |-nvme0n1p1 558.1M 14% /boot/efi |-nvme0n1p2 |-nvme0n1p3 |-nvme0n1p4 |-nvme0n1p5 |-nvme0n1p6 |-nvme0n1p7 13G 67% / |-nvme0n1p8 35.6G 47% /home |-nvme0n1p9 `-nvme0n1p10nvme0n1p10with this command, but it wasn’t listed. So I then ranvim /etc/fstab(I dabble with Vim a little bit
)
This showed me that I could use# /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=D68C-B595 /boot/efi vfat umask=0077 0 2 UUID=a7817728-0a28-490d-aa51-d8b1b99bcad5 / ext4 defaults,noatime 0 1 UUID=3a59b7d6-336a-4055-bd94-e649bae76616 /home ext4 defaults,noatime 0 2 tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0 UUID=50e53c39-8e21-430f-aa6c-815fcfd00d96 none swap defaults 0 0blkidto find/verify the UUID. Exit Vim thenblkid
Or more specifically:/dev/loop1: BLOCK_SIZE="262144" TYPE="squashfs" /dev/nvme0n1p9: UUID="50e53c39-8e21-430f-aa6c-815fcfd00d96" TYPE="swap" PARTUUID="2b1a6333-1845-b244-875a-37c896faa7f9" /dev/nvme0n1p7: UUID="a7817728-0a28-490d-aa51-d8b1b99bcad5" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="8be7e9a1-dda6-8f4a-b55f-cc91b83c12c2" /dev/nvme0n1p5: LABEL="Image" BLOCK_SIZE="512" UUID="DAEC15B1EC1588C1" TYPE="ntfs" PARTUUID="9b859db3-010e-4fce-944e-da8898751905" /dev/nvme0n1p3: LABEL="OS" BLOCK_SIZE="512" UUID="68BCDFE1BCDFA7B8" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="7d5934e3-72ac-4ff3-9e30-3470311b75e9" /dev/nvme0n1p1: LABEL_FATBOOT="ESP" LABEL="ESP" UUID="D68C-B595" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="9e67e13d-5f32-4365-b0fc-ef845b63f67a" /dev/nvme0n1p8: UUID="3a59b7d6-336a-4055-bd94-e649bae76616" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="8b4ab64e-aa97-9f44-b925-51ab2dbe277c" /dev/nvme0n1p10: UUID="438E-DBD6" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="a2c19012-3acb-4f2a-b69b-3102dc25e984" /dev/nvme0n1p6: LABEL="DELLSUPPORT" BLOCK_SIZE="512" UUID="06F82AF1F82ADF25" TYPE="ntfs" PARTUUID="25aeb11c-9eae-4365-83b1-a33eaf4dafae" /dev/nvme0n1p4: BLOCK_SIZE="512" UUID="3A26F8AD26F86AF1" TYPE="ntfs" PARTUUID="03b1b53f-4735-43a0-a4fc-cad9cc0e18e9" /dev/loop2: BLOCK_SIZE="262144" TYPE="squashfs" /dev/loop0: BLOCK_SIZE="262144" TYPE="squashfs" /dev/sda2: SEC_TYPE="msdos" LABEL_FATBOOT="MISO_EFI" LABEL="MISO_EFI" UUID="EA58-776D" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="ff95a72f-02" /dev/sda1: BLOCK_SIZE="2048" UUID="2023-10-15-12-00-38-00" LABEL="MANJARO_KDE_2304" TYPE="iso9660" PARTUUID="ff95a72f-01" /dev/loop3: BLOCK_SIZE="262144" TYPE="squashfs" /dev/nvme0n1p2: PARTLABEL="Microsoft reserved partition" PARTUUID="f36ac7a7-645d-42ec-916a-8973a53700a5"
blkid /dev/nvme0n1p10/dev/nvme0n1p10: UUID="438E-DBD6" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="a2c19012-3acb-4f2a-b69b-3102dc25e984"vim /etc/fstaband edit the file to look like:# /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=438E-DBD6 /boot/efi vfat umask=0077 0 2 UUID=a7817728-0a28-490d-aa51-d8b1b99bcad5 / ext4 defaults,noatime 0 1 UUID=3a59b7d6-336a-4055-bd94-e649bae76616 /home ext4 defaults,noatime 0 2 tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0 UUID=50e53c39-8e21-430f-aa6c-815fcfd00d96 none swap defaults 0 0- Exit Chroot with
exit - Chroot again with updated settings
sudo manjaro-chroot -a lsblkNAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS loop0 7:0 0 71.2M 1 loop loop1 7:1 0 1.2G 1 loop loop2 7:2 0 1.7G 1 loop loop3 7:3 0 668.7M 1 loop sda 8:0 1 29.3G 0 disk |-sda1 8:1 1 3.6G 0 part `-sda2 8:2 1 4M 0 part nvme0n1 259:0 0 476.9G 0 disk |-nvme0n1p1 259:11 0 650M 0 part |-nvme0n1p2 259:12 0 128M 0 part |-nvme0n1p3 259:13 0 280G 0 part |-nvme0n1p4 259:14 0 899M 0 part |-nvme0n1p5 259:15 0 12.1G 0 part |-nvme0n1p6 259:16 0 1.1G 0 part |-nvme0n1p7 259:17 0 48G 0 part / |-nvme0n1p8 259:18 0 76G 0 part /home |-nvme0n1p9 259:19 0 4G 0 part `-nvme0n1p10 259:20 0 100M 0 part /boot/efi
Is that correct?
100% correct so far, good job!
Edit
But I would like to point out:
Is VERY small… 
What does a df -h give? We do NOT want to run out of space in an update, maybe that was what was happening last time.
df -h
Filesystem Size Used Avail Use% Mounted on
/dev/nvme0n1p7 47G 32G 13G 71% /
/dev/nvme0n1p10 99M 142K 99M 1% /boot/efi
/dev/nvme0n1p8 75G 35G 36G 50% /home
efivarfs 384K 91K 289K 24% /sys/firmware/efi/efivars
udev 7.7G 0 7.7G 0% /dev
shm 7.7G 0 7.7G 0% /dev/shm
run 7.7G 0 7.7G 0% /run
tmp 7.7G 0 7.7G 0% /tmp
overlay 12G 404M 12G 4% /etc/resolv.conf
Its fine. Go ahead and continue. 
