[manjaro@manjaro-mate ~]$ lsblk
sudo fdisk -l
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 192.4M 1 loop /run/miso/sfs/livefs
loop1 7:1 0 457.8M 1 loop /run/miso/sfs/mhwdfs
loop2 7:2 0 1.1G 1 loop /run/miso/sfs/desktopfs
loop3 7:3 0 739.3M 1 loop /run/miso/sfs/rootfs
sda 8:0 0 465.8G 0 disk
└─sda1 8:1 0 465.8G 0 part
└─luks-2e1b47f7-ac28-47f5-ba82-e00da8b4bb99 254:0 0 465.8G 0 crypt /run/media/manjaro/c8cd7c48-37cf-4916-abd6-16316ed0ecb8
sdb 8:16 1 14.9G 0 disk /run/miso/bootmnt
├─sdb1 8:17 1 2.5G 0 part
└─sdb2 8:18 1 4M 0 part
sr0 11:0 1 1024M 0 rom
Disk /dev/sda: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: ST500LM012 HN-M5
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xafef6bd0
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 976768064 976766017 465.8G 83 Linux
Disk /dev/sdb: 14.94 GiB, 16043212800 bytes, 31334400 sectors
Disk model: v210w
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/sdb1 * 64 5215859 5215796 2.5G 0 Empty
/dev/sdb2 5215860 5224051 8192 4M ef EFI (FAT-12/16/32)
Disk /dev/loop0: 192.36 MiB, 201707520 bytes, 393960 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: 457.77 MiB, 480002048 bytes, 937504 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.06 GiB, 1134088192 bytes, 2215016 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
Disk /dev/mapper/luks-2e1b47f7-ac28-47f5-ba82-e00da8b4bb99: 465.76 GiB, 500102103552 bytes, 976761921 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
ok, so its on sda1, so chroot:
sudo cryptsetup -v luksOpen /dev/sda1 cryptDrive
sudo mount /dev/mapper/cryptDrive /mnt
sudo manjaro-chroot /mnt
and post output
it asked for password. i entered password. the out put is
[manjaro@manjaro-mate ~]$ sudo cryptsetup -v luksOpen /dev/sda1 cryptDrive
sudo mount /dev/mapper/cryptDrive /mnt
sudo manjaro-chroot /mnt
Enter passphrase for /dev/sda1:
Cannot use device /dev/sda1 which is in use (already mapped or mounted).
Command failed with code -5 (device already exists or device is busy).
mount: /mnt: special device /dev/mapper/cryptDrive does not exist.
dmesg(1) may have more information after failed mount system call.
mount: /mnt/proc: 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
hi, What may i do next?
well you are not chrooted… so try unmounting it:
sudo umount /dev/sda1
then type:
exit
close terminal, open terminal again, and try chrooting, but run the commands one at a time:
sudo cryptsetup -v luksOpen /dev/sda1 cryptDrive
then:
sudo mount /dev/mapper/cryptDrive /mnt
and:
sudo manjaro-chroot /mnt
manjaro@manjaro-mate ~]$ sudo cryptsetup -v luksOpen /dev/sda1 cryptDrive
Enter passphrase for /dev/sda1:
Cannot use device /dev/sda1 which is in use (already mapped or mounted).
Command failed with code -5 (device already exists or device is busy).
[manjaro@manjaro-mate ~]$ sudo mount /dev/mapper/cryptDrive /mnt
mount: /mnt: special device /dev/mapper/cryptDrive does not exist.
dmesg(1) may have more information after failed mount system call.
[manjaro@manjaro-mate ~]$ sudo manjaro-chroot /mnt
mount: /mnt/proc: 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
[manjaro@manjaro-mate ~]$
please pardon me for delayed response. electricity was gone .
could you please tell me what may i do next?
i hope i will not lose data.
i dont use encyption so have no idea whats with it… but i found another guide for chrooting luks, so try that:
sudo cryptsetup luksOpen /dev/sda1 crypto
sudo mount /dev/mapper/crypto /mnt
sudo manjaro-chroot /mnt
[manjaro@manjaro-mate ~]$ sudo cryptsetup luksOpen /dev/sda1 crypto
Enter passphrase for /dev/sda1:
Cannot use device /dev/sda1 which is in use (already mapped or mounted).
[manjaro@manjaro-mate ~]$ sudo mount /dev/mapper/crypto /mnt
mount: /mnt: special device /dev/mapper/crypto does not exist.
dmesg(1) may have more information after failed mount system call.
[manjaro@manjaro-mate ~]$ sudo manjaro-chroot /mnt
mount: /mnt/proc: 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
[manjaro@manjaro-mate ~]$
well still no chrooted… so try this:
sudo cryptsetup luksOpen /dev/sda1 ssd
sudo mount /dev/mapper/ssd /mnt
sudo manjaro-chroot /mnt
[manjaro@manjaro-mate ~]$ sudo cryptsetup luksOpen /dev/sda1 ssd
Enter passphrase for /dev/sda1:
Cannot use device /dev/sda1 which is in use (already mapped or mounted).
[manjaro@manjaro-mate ~]$ sudo mount /dev/mapper/ssd /mnt
mount: /mnt: special device /dev/mapper/ssd does not exist.
dmesg(1) may have more information after failed mount system call.
[manjaro@manjaro-mate ~]$ sudo manjaro-chroot /mnt
mount: /mnt/proc: 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
Brahma, my friend, i am very grateful for your kind efforts and time to help me. but i am also sad that i am giving you trouble even though i dont want to. what a helpless situation i have.
i have no knowledge about encryption, since i dont use it, and this is one of the reasons…
try running this:
sudo umount /dev/sda1
and:
sudo cryptsetup close encrypted
and then run again:
sudo cryptsetup -v luksOpen /dev/sda1 cryptDrive
and post output from it
[manjaro@manjaro-mate ~]$ sudo umount /dev/sda1
umount: /dev/sda1: not mounted.
[manjaro@manjaro-mate ~]$ sudo cryptsetup close encrypted
Device encrypted is not active.
[manjaro@manjaro-mate ~]$ sudo cryptsetup -v luksOpen /dev/sda1 cryptDrive
Enter passphrase for /dev/sda1:
Cannot use device /dev/sda1 which is in use (already mapped or mounted).
Command failed with code -5 (device already exists or device is busy).
[manjaro@manjaro-mate ~]$
Brahma, what if there might be something wrong with the grub? i guess. maybe.
you may like to check whether all the settings in my grub is correct.
so here it says that its not mounted:
and here it says that it is mounted:
i dont understand…
try this:
dmsetup remove_all
and then again:
sudo cryptsetup -v luksOpen /dev/sda1 cryptDrive
this is not related to grub…
[manjaro@manjaro-mate ~]$ dmsetup remove_all
/dev/mapper/control: open failed: Permission denied
Failure to communicate with kernel device-mapper driver.
Incompatible libdevmapper 1.02.187 (2022-11-10) and kernel driver (unknown version).
Command failed.
[manjaro@manjaro-mate ~]$ sudo cryptsetup -v luksOpen /dev/sda1 cryptDrive
Enter passphrase for /dev/sda1:
Cannot use device /dev/sda1 which is in use (already mapped or mounted).
Command failed with code -5 (device already exists or device is busy).
[manjaro@manjaro-mate ~]$
ok so run it with sudo:
sudo dmsetup remove_all
and post output from it
[manjaro@manjaro-mate ~]$ sudo dmsetup remove_all
[manjaro@manjaro-mate ~]$
it looks like it worked, so run this again:
sudo cryptsetup -v luksOpen /dev/sda1 cryptDrive
[manjaro@manjaro-mate ~]$ sudo cryptsetup -v luksOpen /dev/sda1 cryptDrive
Enter passphrase for /dev/sda1:
Cannot use device /dev/sda1 which is in use (already mapped or mounted).
Command failed with code -5 (device already exists or device is busy).
[manjaro@manjaro-mate ~]$
well thats it from me… i have no idea what to do next, since we cant chroot…
so reboot and in this stuck screen:
can you post picture from this:
sudo blkid
cat /etc/fstab
i will do it now. it may take 2-3 minutes.
Hi it says. You can’t embed media items in a post. What should I do?
so it worked? the commands showed output?
you still not allowed to post pics here, since you are a new user…
you can upload the pics on some image hosting website and post the link here, and use formatting for the link