i have no idea…
post output from:
cat /etc/fstab/
blkid
1 Like
sh-5.1# exit
exit
[manjaro@manjaro-mate ~]$ sudo mount /dev/mapper/cryptDrive /mnt
mount: /mnt: /dev/mapper/cryptDrive already mounted on /mnt.
dmesg(1) may have more information after failed mount system call.
[manjaro@manjaro-mate ~]$ sudo manjaro-chroot /mnt
sh-5.1#
[manjaro@manjaro-mate ~]$ sudo manjaro-chroot /mnt
sh-5.1# cat /etc/fstab/
cat: /etc/fstab/: Not a directory
sh-5.1# blkid
/dev/loop1: TYPE="squashfs"
/dev/sdb2: SEC_TYPE="msdos" LABEL_FATBOOT="MISO_EFI" LABEL="MISO_EFI" UUID="D822-6719" BLOCK_SIZE="512" TYPE="vfat"
/dev/sdb1: BLOCK_SIZE="2048" UUID="2023-01-04-11-28-34-00" LABEL="MANJARO_MATEM_220" TYPE="iso9660"
/dev/loop2: TYPE="squashfs"
/dev/loop0: TYPE="squashfs"
/dev/mapper/cryptDrive: UUID="c8cd7c48-37cf-4916-abd6-16316ed0ecb8" BLOCK_SIZE="4096" TYPE="ext4"
/dev/sda1: UUID="2e1b47f7-ac28-47f5-ba82-e00da8b4bb99" TYPE="crypto_LUKS" PARTUUID="afef6bd0-01"
/dev/loop3: TYPE="squashfs"
sh-5.1#
so here the blkid output shows the correct c8cd7.... uuid, and in the output above it shows a different one… i dont understand this…
and the correct fstab command is:
cat /etc/fstab
and not:
cat /etc/fstab/
1 Like
sh-5.1# cat /etc/fstab
# /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>
/dev/mapper/luks-2e1b47f7-ac28-47f5-ba82-e00da8b4bb99 / ext4 defaults,noatime 0 1
sh-5.1#
this is the uuid the that cant be found:
and this uuid from blkid:
matches this from fstab:
so i dont know what this uuid is, or if it should be also in fstab:?
maybe @xabbu can help us here out…
@salemkhosla
This was a mess - it’s difficult to straighten this out during this game of telephone where important things get overlooked and lost on the way.
Just start from the beginning.
- boot from the USB drive
- do NOT access your encrypted harddrive via the file manager (don’t touch it yet)
post output of
lsblk -f
go from there
1 Like
[manjaro@manjaro-mate ~]$ lsblk -f
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
crypto 1 2e1b47f7-ac28-47f5-ba82-e00da8b4bb99
└─cryptDrive
ext4 1.0 c8cd7c48-37cf-4916-abd6-16316ed0ecb8 302.2G 29% /mnt/mnt
/mnt
sdb iso966 Jolie MANJARO_MATEM_220
2023-01-04-11-28-34-00 0 100% /run/miso/bootmnt
├─sdb1
│ iso966 Jolie MANJARO_MATEM_220
│ 2023-01-04-11-28-34-00
└─sdb2
vfat FAT12 MISO_EFI
D822-6719
sr0
[manjaro@manjaro-mate ~]$
you did not start from the beginning - the encrypted drive is already open and mounted on /mnt/mnt
reboot!
hi, i will reboot and select to boot from usb manjaro. then i will select start eith proprietry drivers.
then i will open mate terminal (previously i was using kde. though)
i will give output result . kindly wait a momwnt.
I’m also missing the unencrypted boot / EFI partition.
that’s up to you - it doesn’t matter as long as you get to a TTY or terminal
[manjaro@manjaro-mate ~]$ lsblk -f
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
crypto 1 2e1b47f7-ac28-47f5-ba82-e00da8b4bb99
sdc iso966 Jolie MANJARO_MATEM_220
2023-01-04-11-28-34-00 0 100% /run/miso/bootmnt
├─sdc1
│ iso966 Jolie MANJARO_MATEM_220
│ 2023-01-04-11-28-34-00
└─sdc2
vfat FAT12 MISO_EFI
D822-6719
sr0
[manjaro@manjaro-mate ~]$
sudo cryptsetup open /dev/sda1 encrypted
it will ask for your password
then:
sudo mount /dev/mapper/encrypted /mnt
and report
lsblk -f
again, please
1 Like
manjaro@manjaro-mate ~]$ sudo cryptsetup open /dev/sda1 encrypted
Enter passphrase for /dev/sda1:
[manjaro@manjaro-mate ~]$ sudo mount /dev/mapper/encrypted /mnt
[manjaro@manjaro-mate ~]$ lsblk -f
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
crypto 1 2e1b47f7-ac28-47f5-ba82-e00da8b4bb99
└─encrypted
ext4 1.0 c8cd7c48-37cf-4916-abd6-16316ed0ecb8 302.2G 29% /mnt
sdc iso966 Jolie MANJARO_MATEM_220
2023-01-04-11-28-34-00 0 100% /run/miso/bootmnt
├─sdc1
│ iso966 Jolie MANJARO_MATEM_220
│ 2023-01-04-11-28-34-00
└─sdc2
vfat FAT12 MISO_EFI
D822-6719
sr0
[manjaro@manjaro-mate ~]$
cat /mnt/etc/fstab
please
1 Like
[manjaro@manjaro-mate ~]$ cat /mnt/etc/fstab
# /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>
/dev/mapper/luks-2e1b47f7-ac28-47f5-ba82-e00da8b4bb99 / ext4 defaults,noatime 0 1
[manjaro@manjaro-mate ~]$
**Hi hi hi . it says you will have to wait for 12 hours then you will be able to write more replies. horrible. kindly tell me how i can contact you. email or telegram or anyway. please. i need help. horrible manjaro. forum. **
KINDLY SEE THIS:
I WILL WRIITE MY REPLY HERE. KINDLY WAIT FOR ME.
manjaro@manjaro-mate ~]$ sudo manjaro-chroot -a /mnt
grub-probe: error: cannot find a GRUB drive for /dev/sdc1. Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdc1. Check your device.map.
==> ERROR: No Linux partitions detected!
[manjaro@manjaro-mate ~]$
Hi Nachlese, what should i do now?
HERE KINDLY NOTICE THIS NACHLESE:
[manjaro@manjaro-mate ~]$ sudo manjaro-chroot /mnt
sh-5.1#
(KINDLY tell me what should i do now, Nachlese?)
Nachlese, i need to get back into my old manjaro. it was kde. i dont care. but i need to prevent file loss and successfully login into my “job” and “…bb99” device . could you please guide me. if possible, please let me write to you on telegram or another communication service. before manjaro owners will block us from writing to each other. they must have informed me of limitations in the begining. i will never ever use archlinux or manjaro specially because of shut blsht sudden limitations
NACHLESE :
WHEN I TRYTO REPLY YOU, I GET THIS GIFT OF MANJARO. COOL.:
An error occurred: We appreciate your enthusiasm, keep it up! That said, for the safety of our community, you’ve reached the maximum number of replies a new user can create on their first day. Please wait 11 hours and you’ll be able to create more replies.
just to be sure:
ls -l /mnt
What is so difficult?
Skip that - but something else instead:
We forgot to check the filesystem, to be sure it is without errors:
sudo umount /mnt
sudo e2fsck -v /dev/mapper/encrypted
sudo mount /dev/mapper/encrypted /mnt
ls -l /mnt
Nice trick - to edit the post above and I wait for a new one which never comes … 
Now you can (try to) chroot:
sudo manjaro-chroot -a /mnt
and run the update again
@salemkhosla
Nice one.
We hit a forum limit - 3 posts from me and none from you in between
I can’t respond to you anymore - just to myself.
Now I have to do the same as you did and edit my own post - hope you see it.
Please respond with a new post - don’t add or edit older posts.
Try without the -a switch:
sudo manjaro-chroot /mnt
… and you did it again:
reply here, please
I will not keep going up and down to see whether you added something and then have to add to my own post.
You are good to go, to run the update:
sudo pacman -Syyu
for the benefit of others reading here:
@salemkhosla is a new user and has, over the course of this thread, exceeded the limit of the number of posts a new user can make on one day (50)
He is frustrated, can’t reply anymore (not today) and may not come back. 
1 Like
hi, lets continue this. please tell me where to proceed?
[manjaro@manjaro-mate ~]$ sudo manjaro-chroot /mnt
mount: /mnt/sys: mount point does not exist.
dmesg(1) may have more information after failed mount system call.
==> ERROR: failed to setup API filesystems in chroot /mnt
What is the limitation for today? This is the second post.
I ran update. Files over 1.5 GB downloaded.
…
checking for file conflicts
After that, a large number of results ending with: …exists in filesystem
Errors occured. No packages were upgraded.
What is advisable to do now?
Thanks everyone whoever has been trying to help me.
What has happend to your system ?
probably none - you are now a seasoned user with 50+ posts under your belt
Your problems stem from an interrupted update - most likely.
You need to force the installation - to overwrite those already existing files.
sudo pacman -Syyu --overwrite
is probably the correct command
That problem has been discussed many times here in the forum and when you search you’ll find how these other people solved it.
1 Like