It’s not important which Linux you use.
Any will do.
If you want to “fix” your cloned system, to use the whole space on the disk,
you’d use gparted to move and grow your main partition
which should be quite easy - contrary to what I said.
Yes, indeed! I used Timeshift and many other programs to clone or produce an image, without success. I was able to accomplish what I wanted to do by creating my parts in order, one after the other, and then copying and pasting them with Gparted. It’s fast, simple and effective! The only problem: the computer doesn’t boot on the internal 1TB SSD.
I was not aware that one can even do that - but I may be misunderstanding what you did.
What do you see of the contents of your cloned 1TB drive when you boot a live system to access it?
and: make sure you have only this disk connected - not the original as well
they are clones - there will be conflicts
1 Like
the contents of the partitions
mount each partition and verify that it contains what it should contain
tAlready done ! 
Everything is ok.
Then you should be able to mount the second partition - which contains the root filesystem
to /mnt (for example)
and mount the first partition, which contains the /boot/efi directory
to it at /mnt/boot (to stay with the example
mount /dev/nvmen0n1p2 /mnt
mount /dev/nvmen0n1p1/mnt/boot
and then use the chroot procedure to chroot into your system
and inspect and repair it from there
This is much easier when you use a Manjaro live ISO or an Arch ISO - then the whole, multi step chroot procedure is automated by the command manjaro-chroot or arch-chroot.
But first:
make sure that /dev/nvmen0n1p1 is marked as EFISYS or EFI
I cannot remember which it is, but it will be an option in gparted
The properties tell me among other things :
mount point: /boot/efi
Is this it ?
mount: /mnt: only the superuser can use mount.
dmesg(1) may have more information after a failed mount system call.
mount: /dev/nvmen0n1p1/mnt/boot: impossible to find in /etc/fstab.
Ok, got it, I will create a bootable iso of manjaro.
no, that is not it
right click the partiton - from the context menu choose: manage flags
and check “boot” and “esp”
of course - use sudo or run the command as root
you don’t have to - it’s just a bit more cumbersome
as you can see from the procedure, it involves multiple mount commands
but yes, I’d advise to do that
although the picture looks like you are already running a manjaro system
sudo mount /dev/nvmen0n1p2 /mnt 1 ✘
mount /dev/nvmen0n1p1/mnt/boot
[sudo] Password for manjaro-rescue :
mount: /mnt: the special device /dev/nvmen0n1p2 does not exist.
dmesg(1) may have more information after a failed mount system call.
mount: /dev/nvmen0n1p1/mnt/boot: impossible to find in /etc/fstab. 
one line at a time - don’t just copy/paste
and check that the name is correct - I had to glean it from your picture
By clicking right, I don’t have this option that I have already tested!
well - what options do you have?
sudo mount /dev/nvmen0n1p2 /mnt 
[sudo] Password for manjaro-rescue :
mount: /mnt: the special device /dev/nvmen0n1p2 does not exist.
dmesg(1) may have more information after a mount system call fails.
~ mount /dev/nvmen0n1p1/mnt/boot 32 ✘ 7s
mount: /dev/nvmen0n1p1/mnt/boot: impossible to find in /etc/fstab.
~
check mounting point; check, save
as I said:
check whether the name is correct
I had to read it from your picture and then type it
… and misread
it’s: /dev/nvme0n1p1
not: /dev/nvmen0n1p1
same for the other one
use lsblk -f
and you’ll see and can also copy/paste from there
In fact, in the properties of the partitions, it is specified that it is impossible to find the mount point.
That doesn’t make any sense to me.
It is not necessary to be mounted - in fact: it should not be
(we are now talking of gparted, right? - I’m)