partition manager de KDE.
can you not just copy/paste from terminal
and not use images
please
It looks like you still have both disks connected.
Is that so?
don’t do that.
The two boot partitions have an identical UUID - this will bite you - it probably currently already is biting you
Oh, sorry! I thought Gparted and Partition Manager were similar. I’m switching to Gparted.
use gparted - I do not know the KDE partition manager and how it works
I certainly can’t give you advise on how to use it
First partition in fat 32 : flags on boot & esp. The mount on option is on boot/efi
Second partition in ext4 : no flags
ok -
but you still have two disks with identical UUID - once again: don’t do that
What do you suggest?
I asked Gparted to renew UUID. I restart and see what happens. It’s really complex! It was easier with Bios.
this is the same no matter whether Bios or UEFI is used
use a live system, like a Manjaro ISO, take out the original drive
I am there. Another proposal?
you are where?
in image manjaro usb.
so: mount the two partitions like described above
and use
manjaro-chroot -a
or
manjaro-chroot /mnt
to get into your system
manjaro-chroot -a
==> Mounting (ManjaroLinux) [/dev/nvme0n1p2]
→ mount: [/mnt]
→ mount: [/mnt/boot/efi]
mount: /mnt/boot/efi: special device /dev/disk/by-uuid/792D-9FFD does not exist.
dmesg(1) may have more information after failed mount system call.
[manjaro /]#
exit chroot again (CTRL+D or just type exit)
the automatic procedure failed
you have to mount the two partitions yourself
then use manjaro-chroot /mnt
can you also give the result of:
lsblk -f
(without being in chroot)
sudo mount /dev/nvmen0n1p2 /mnt ✔
mount: /mnt: special device /dev/nvmen0n1p2 does not exist.
dmesg(1) may have more information after failed mount system call.
~ mount /dev/nvmen0n1p1/mnt/boot 32 ✘
mount: /dev/nvmen0n1p1/mnt/boot: can't find in /etc/fstab.
~ lsblk -f 1 ✘
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
loop0
squash 4.0 0 100% /run/miso/sfs/livefs
loop1
squash 4.0 0 100% /run/miso/sfs/mhwdfs
loop2
squash 4.0 0 100% /run/miso/sfs/desktopfs
loop3
squash 4.0 0 100% /run/miso/sfs/rootfs
sda
├─sda1
│ exfat 1.0 Ventoy
│ 522A-E565
│ └─ventoy
│ iso966 Jolie MANJARO_KDE_220
│ 2022-12-24-05-28-59-00 0 100% /run/miso/bootmnt
└─sda2
vfat FAT16 VTOYEFI
1968-9ADA
nvme0n1
├─nvme0n1p1
│ vfat FAT32 NO_LABEL
│ 4AA6-65B8
├─nvme0n1p2
│ ext4 1.0 7d52b9e7-c3de-4231-b641-fa3d13551c8b 716.5G 14% /run/media/manjaro/7d52b9e7-c3de-4231-b641-fa3d13551c8b
└─nvme0n1p3
swap 1 686f5e7b-19cf-4d70-a70c-27d726f3a2e2
~
can you please format terminal output as “preformatted text”
this symbol: → </> in the editor window
you, again, used a wrong partition name - you copy/pasted from my erroneous post
I will not abuse your patience. It seems more reasonable to me to reinstall Manjaro and set all the parameters.
Would you please have a protocol for saving my system settings? Unless you think it is more stable to do without.
I plan to use a backup software for my software and my home. What do you say?
I’m happy to assist you, as you can see - but do whatever you deem best.
What settings would that be?
Did you even make changes to the system settings (changed something in /etc)?
Thank you very much, and I wish it was more than just words. It’s very kind of you, but I don’t make it easy for you and I think that what I’m doing is too complex.
I want to avoid setting everything after the installation: language, keyboard, theme …