[SOLVED] Can't chroot into /mnt

[versed drift]

nvme0n1     259:0    0   1.8T  0 disk
├─nvme0n1p1 259:1    0   100M  0 part
├─nvme0n1p2 259:2    0   1.3T  0 part
├─nvme0n1p3 259:3    0   300M  0 part
├─nvme0n1p4 259:4    0  31.3G  0 part
└─nvme0n1p5 259:5    0 456.7G  0 part /mnt```

```ts
ls /mnt
@  bin  boot  @cache  dev  etc  @home  @log  proc  @root  run  @srv  sys  @tmp  tmp  var```

```ts
chroot /mnt /bin/bash
chroot: failed to run command ‘/bin/bash’: Permission denied```


```ts
arch-chroot /mnt /bin/bash
mount: /mnt/sys: sys already mounted or mount point busy.
dmesg(1) may have more information after failed mount system call.
==> ERROR: failed to setup chroot /mnt```

can anyone help and when i try to close my terminal it says `bash` process is running

[cunning tangle]

lsblk -f

[versed drift]

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
ntfs         Local Disk        9EA854C6A8549F19
sdb  iso966 Jolie GARUDA_DR460NIZED_RAPTOR
2023-05-01-21-27-23-00
├─sdb1
│    iso966 Jolie GARUDA_DR460NIZED_RAPTOR
│                                   2023-05-01-21-27-23-00                     0   100% /run/miso/bootmnt
└─sdb2
vfat   FAT12 MISO_EFI          CC34-06DF
zram0
[SWAP]
nvme0n1

├─nvme0n1p1
│    vfat   FAT32                   6CF6-2B9A
├─nvme0n1p2
│    ntfs                           A01401A114017C12
├─nvme0n1p3
│    vfat   FAT32                   C146-AA85
├─nvme0n1p4
│    swap   1                       0a15e252-1fbb-4930-ac23-411bb2cbe19a
└─nvme0n1p5
btrfs                          8f9d8323-36db-4639-9e79-349bd9dd2a8f  376.9G    17% /mnt```

[cunning tangle]

The formatting isn't ideal, can you run this

lsblk -f | curl -F 'f:1=<-' ix.io

instead?

[versed drift]

it logged http://ix.io/4ARK

[cunning tangle]

So nvme0n1p5 is where your OS resides?

[versed drift]

yes

[cunning tangle]

Can you post output of findmnt /mnt

[versed drift]

/mnt   /dev/nvme0n1p5 btrfs  rw,relatime,ssd,discard=async,space_cache=v2,subvolid=5,subvol=/```

[cunning tangle]

Are you sure your os tree is at subvolid 5 ?

[versed drift]

no

but i think so

[cunning tangle]

I assume it must be the /@.?
Can you post output of ls /mnt/@

[versed drift]

i have dual boot

bin boot dev etc home lib lib64 mnt opt proc root run sbin srv sys tmp usr var

[cunning tangle]

cat /mnt/@/etc/os-release

[versed drift]

PRETTY_NAME="Garuda Linux"
ID=garuda
ID_LIKE=arch
BUILD_ID=rolling
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://garudalinux.org/"
DOCUMENTATION_URL="https://wiki.garudalinux.org/"
SUPPORT_URL="https://forum.garudalinux.org/"
BUG_REPORT_URL="https://gitlab.com/groups/garuda-linux/"
PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/"
LOGO=garudalinux```

[cunning tangle]

Is the operating system you are trying to chroot into Garuda Linux?

[versed drift]

yes

it broke some days ago

and i read on the forum

that the guy fixed it by going into chroot

[cunning tangle]

So the command to chroot here should be arch-chroot /mnt/@

[versed drift]

but then i messed up my boot

[versed drift]

why?

i mounted it in /mnt

arch-chroot /mnt/@
==> WARNING: /mnt/@ is not a mountpoint. This may have undesirable side effects.```

[cunning tangle]

Because obviously your OS tree is under btrfs subvolume /@ instead of root subvolume (subvolume=5)

[cunning tangle]

Ignore it

[versed drift]

nothing happend

[cunning tangle]

My 2 cents you haven't read https://wiki.archlinux.org/title/Btrfs at all.

[cunning tangle]

Really?

cat /etc/os-release

[versed drift]

NAME="Garuda Linux"
PRETTY_NAME="Garuda Linux"
ID=garuda
ID_LIKE=arch
BUILD_ID=rolling
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://garudalinux.org/"
DOCUMENTATION_URL="https://wiki.garudalinux.org/"
SUPPORT_URL="https://forum.garudalinux.org/"
BUG_REPORT_URL="https://gitlab.com/groups/garuda-linux/"
PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/"
LOGO=garudalinux```

[cunning tangle]

and

ls /mnt

[versed drift]

i did su username

[versed drift]

doesn't log anything

[cunning tangle]

So something has happened, you are in the chroot in FA.

[versed drift]

FA?

my home folder is empty

[cunning tangle]

It is an illusion that the command does nothing, because you may see the exact same bash prompt before chrooting.

[cunning tangle]

Because you have not mounted it

[versed drift]

oh

so do you know how to you know

[cunning tangle]

Your operating system is installed on a btrfs subvolume, and your /home and other directories are on different btrfs subvolumes.

[versed drift]

fix it

so i can boot into my os

like i did before

with grub

should i do grub-install?

[cunning tangle]

Could you please take a moment to read this straightforward article at https://wiki.archlinux.org/title/Btrfs?

[versed drift]

which paragraph

[cunning tangle]

There are 400 lines in total, so it shouldn't take too long.

In particular, the sub-volume section

[cunning tangle]

What kind of problem is preventing the system from booting?

[versed drift]

i don't see grub interface like i used to before

im scared to reboot cuz all the work will be thrown away

im on my live usb

[cunning tangle]

Could you please run

[[ -d /sys/firmware/efi/efivars ]] && efibootmgr

And post the output

[versed drift]

damn this is big output

i see grub console

where i can write commands

if i change priority of my boot order

[cunning tangle]

Didn't you say you couldn't see the grub interface? Did you actually mean that you couldn't see the grub entry?

[versed drift]

i mean selective menu

like

when you use your arrow buttons to select the os you wanna boot into

[cunning tangle]

Like you system just boot into windows

Without showing grub at all

[versed drift]

no

if i put my ssd in first place

in boot priority

it says GRUB:

and then i can write some commands

but it doesn't have a visual

like

no selection

it used to look like this

now it is like CMD

grub rescue

yes

grub rescue

it says that

[cunning tangle]

Sorry, can you describe the problem with a bit more coherence?

[versed drift]

yes it takes me into grub rescue

i can't boot into my os

so i was told i have to chroot into system to fix grub

[cunning tangle]

cat /mnt/@/etc/fstab

If you are already chrooted, cat /etc/fstab.

[versed drift]

# /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=C146-AA85                            /boot/efi      vfat    defaults,noatime 0 2
UUID=0a15e252-1fbb-4930-ac23-411bb2cbe19a swap           swap    defaults   0 0
UUID=8f9d8323-36db-4639-9e79-349bd9dd2a8f /              btrfs   subvol=/@,defaults,noatime,compress=zstd 0 0
UUID=8f9d8323-36db-4639-9e79-349bd9dd2a8f /home          btrfs   subvol=/@home,defaults,noatime,compress=zstd 0 0
UUID=8f9d8323-36db-4639-9e79-349bd9dd2a8f /root          btrfs   subvol=/@root,defaults,noatime,compress=zstd 0 0
UUID=8f9d8323-36db-4639-9e79-349bd9dd2a8f /srv           btrfs   subvol=/@srv,defaults,noatime,compress=zstd 0 0
UUID=8f9d8323-36db-4639-9e79-349bd9dd2a8f /var/cache     btrfs   subvol=/@cache,defaults,noatime,compress=zstd 0 0
UUID=8f9d8323-36db-4639-9e79-349bd9dd2a8f /var/log       btrfs   subvol=/@log,defaults,noatime,compress=zstd 0 0
UUID=8f9d8323-36db-4639-9e79-349bd9dd2a8f /var/tmp       btrfs   subvol=/@tmp,defaults,noatime,compress=zstd 0 0
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0```

[cunning tangle]

Are you in the chroot?

[versed drift]

yes

[cunning tangle]

First mount the EFI system partition

mount /dev/nvme0n1p3 /boot/efi

[versed drift]

garuda-dr460nized% su
Password:
su: cannot set groups: Operation not permitted```

should i exit chroot?

[cunning tangle]

arch-chroot should put you in root instead of this regular account, so log out of it.

Wait, what is the output of whoami

[versed drift]

bash: arch-chroot: command not found

oh i already logged out

/mnt is empty

[cunning tangle]

OK, let's start all over again, following the bash commands exactly as they appear.

[cunning tangle]

Or ctrl+alt+f3 to bring up another virtual console.

[versed drift]

no im in garuda iso

i have konsole

also /mnt is empty

i need to mount

i think

[cunning tangle]

No, at the bash prompt, type exit repeatedly until konsole exit

Then open another konsole window and arch-chroot /mnt/@

[versed drift]

ok

[cunning tangle]

After chroot is done, do not type another other commands

[versed drift]

ok im inside

ok

[cunning tangle]

Ok, now

findmnt /boot/efi

[versed drift]

it logs nothing

[cunning tangle]

next, mount ESP with

mount /dev/nvme0n1p3 /boot/efi

[versed drift]

ok i did

[cunning tangle]

Can you post the output of

ls /boot/efi

[versed drift]

dev proc run sys 'System Volume Information'

[cunning tangle]

Finally run

grub-install --efi-directory=/boot/efi

Then post the output

[versed drift]

Installing for x86_64-efi platform.
grub-install: error: cannot find a device for /boot/grub (is /dev mounted?).```

😦

[cunning tangle]

Did you use arch-chroot, which automatically mounts /dev, /sys, etc?

In the previous chroot step

[versed drift]

yes

100% sure

i did

[cunning tangle]

Can you post output of df -h

[versed drift]

/dev/nvme0n1p3  300M   32K  300M   1% /boot/efi
udev             16G     0   16G   0% /dev
shm              16G     0   16G   0% /dev/shm
run              16G     0   16G   0% /run
tmp              16G     0   16G   0% /tmp
overlay          24G  2.1G   22G   9% /etc/resolv.conf```

[cunning tangle]

So finally we have to actually mount the subvolume /@, because grub is stubborn.

Sorry for any inconvenience

Now, exit the chroot

[versed drift]

no i appreciate your help

ok so i ishould write exit?

[cunning tangle]

just type exit, then enter

[versed drift]

ok

[cunning tangle]

umount -l /mnt/boot/efi
umount -l /mnt
mount -o subvol=/@ /dev/nvme0n1p5 /mnt
mount /dev/nvme0n1p3 /mnt/boot/efi

Next,

arch-chroot /mnt

Finally,

grub-install --efi-directory=/boot/efi

If there's an error, please post it

[versed drift]

mount: /mnt: /dev/nvme0n1p5 already mounted on /mnt.
dmesg(1) may have more information after failed mount system call.```

[cunning tangle]

Sorry, I forgot the umount.

The previous message was edited using umount commands.

[versed drift]

sudo umount /mnt
umount: /mnt: target is busy.```

[cunning tangle]

You can unmount them lazily with flag -l
umount -l /mnt

[versed drift]

GDBus.Error:org.freedesktop.Notifications.Error.ExcessNotificationGeneration: Created too many similar notifications in quick succession

[cunning tangle]

This seems to be unrelated, so let's ignore it for now

[versed drift]

ok

[cunning tangle]

Is the /mnt and /mnt/boot/efi now mounted?

[versed drift]

yes I followed your instructions

Installing for x86_64-efi platform.
Installation finished. No error reported.```

yay

does it mean that it works now?

[cunning tangle]

It seems fine. Can you test it with a reboot?

[versed drift]

Yes i will reboot now

yea it didn't work

it said GRUB _

[cunning tangle]

Does it still show you a Grub Recuse prompt?

[versed drift]

no

it only says GRUB _

and i can't write anything

[cunning tangle]

Do you have a picture of it?

[versed drift]

its like black screen and on top left it says GRUB _

_ is blinking

i don't have a picture

also in my bios menu it only showed windows boot manager not grub boot manager

[cunning tangle]

like this?

[versed drift]

let me send you picture

it will take like 5 mins tho

is it okay?

[cunning tangle]

No problem, just ping me when you are done.

[versed drift]

ok

@cunning tangle

[cunning tangle]

.Can you go back to the live ISO and rebuild the grub config?

grub-mkconfig -o /boot/grub/grub.cfg

[versed drift]

in chroot?

sudo grub-mkconfig -o /boot/grub/grub.cfg
/usr/bin/grub-probe: error: failed to get canonical path of `overlay'.```

it says this when im not in chroot

[cunning tangle]

Yes repeat the commands above in chroot

mount -o subvol=/@ /dev/nvme0n1p5 /mnt
mount /dev/nvme0n1p3 /mnt/boot/efi
arch-chroot /mnt
grub-mkconfig -o /boot/grub/grub.cfg

[cunning tangle]

If you are still in the chroot, please post the output of fdisk -l.

[versed drift]

sorry for inconvenience my internet cut off

[cunning tangle]

What a coincidence, my internet was also cut due to the router overheating.

[versed drift]

😄

should i reboot?

[cunning tangle]

What is the output of efibootmgr ?

[cunning tangle]

That doesn't look right.

[versed drift]

Boot0003 and 4 is my usb

[cunning tangle]

BBS can stand for BIOS Boot Specification, which means your system will boot in BIOS mode with the second entry.

the Boot0001

[cunning tangle]

Can you arch-chroot /mnt and

grub-install --target=x86_64-efi --bootloader-id=GRUB --efi-directory=/boot/efi --recheck

post the output of efibootmgr again?

[versed drift]

yea i did it

[cunning tangle]

Ok, try to reboot

[versed drift]

Ok

[cunning tangle]

Don't use BBS in your firmware

[versed drift]

Bbs?

[cunning tangle]

It seems that your firmware is trying to boot using lagecy BIOS

[versed drift]

its disabled

[cunning tangle]

Can you try to find options in your firmware to boot the drive in UEFI mode?

[versed drift]

what should i look for?

this is my bios

https://youtu.be/ZpuXugFenPI

[cunning tangle]

In the settings\boot select something like [UEFI GRUB] or [UEFI Hard Disk]

[cunning tangle]

Can you post a picture of the settings\boot of your firmware setup?

[versed drift]

If i change it to uefi

Omly

It reboots and takes me to bios again

[cunning tangle]

Change the boot mode to [UEFI] instead of [UEFI+legacy].

[versed drift]

Then i cant see my ssd

[cunning tangle]

It was probably marked as something like [UEFI hard disk ...].

Just give it a try.

[versed drift]

This

[cunning tangle]

What is in the UEFI Hard Drive BBS Priorities

[versed drift]

It is diabled

There is option to enable windows boot manager

[cunning tangle]

When you click on Boot Option #1, what happens?

[versed drift]

I get to choose devices

[cunning tangle]

Does this firmware have a boot menu (which can be accessed by pressing f12 during boot)?

[versed drift]

Yes

[cunning tangle]

Can you bring up the boot menu and post a pictureo f it?

[versed drift]

Ok

It only works in uefi + legacy

[cunning tangle]

Well, here is one possibility, from your lsblk and fdisk output I can see that you have two ESPs (EFI System Partition) on the same drive. The first ESP only has the window boot manager on it, and the second has the grub efi binary on it.

Although the practice of having multiple ESPs on the same drive is not strictly forbidden, it is discouraged by the UEFI specification and is known to cause problems with some UEFI implementations.

For example, the firmware won't let you select EFI binaries (boot loaders) from the second ESP.

[versed drift]

But it was working before

I just had disabled windows boot manager

And it was taking me to grub

I need to access some folders on my linux

Its important

[cunning tangle]

Your system was set up with Lagecy+UEFI. This means that you probably installed GRUB in the past to boot with the BIOS instead of UEFI.

[versed drift]

I had windows first

Then i installed grub

[cunning tangle]

May I know what broke your boot before all this happened?

[versed drift]

trying to chroot

And update of garuda

It was giving me error

When booting

[cunning tangle]

where were you chroot from

[versed drift]

Live iso

[cunning tangle]

Why do you use Live ISO to chroot into your system and update?

[versed drift]

Because i cant boot in the system

[cunning tangle]

I mean before all that. what breaks your system in first place

[versed drift]

Like before problems i updated garuda then shut down my pc

When i turned it on

In grub i selected linux

And it was giving me some error I don’t remember

After that i searched that error and i had to solve it by going in chroot

[cunning tangle]

Ok, let's focus on the problem at hand for now. Can you go back to Live ISO?

[versed drift]

Yes

[cunning tangle]

The Live ISO typically uses a hybrid BIOS and UEFI setup, so it should support booting in UEFI mode without changing the current firmware settings

[versed drift]

I cant boot in with uefi

Lemme try

[cunning tangle]

Can you post a picture of f12 boot menu if you can't boot in UEFI mode?

[versed drift]

It booted

Its loading now

[cunning tangle]

stat /sys/firmware/efi/efivars

[versed drift]

Its installing some drivers first

stat /sys/firmware/efi/efivars/
File: /sys/firmware/efi/efivars/
Size: 0               Blocks: 0          IO Block: 4096   directory
Device: 0,33    Inode: 19609       Links: 2
Access: (0755/drwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2023-07-18 11:02:32.777291836 +0000
Modify: 2023-07-18 10:59:11.220052622 +0000
Change: 2023-07-18 10:59:11.220052622 +0000
Birth: -```

[cunning tangle]

mount /dev/nvme0n1p3 /mnt
ls /mnt

[versed drift]

dev EFI proc run sys 'System Volume Information'

[cunning tangle]

ls /mnt/EFI

[versed drift]

garuda GRUB

[cunning tangle]

tree /mnt/EFI

if there is no tree, install it with pacman -S tree

[versed drift]

yea i know that

/mnt/EFI
├── garuda
│   └── grubx64.efi
└── GRUB
└── grubx64.efi```

[cunning tangle]

umount /mnt
mount /dev/nvme0n1p1 /mnt
tree /mnt/EFI

[cunning tangle]

umount /mnt

[versed drift]

ok i did it

[cunning tangle]

OK. The second ESP only contains EFI files for grub, so we will stop marking it as an ESP and install grub on the first ESP. This may solve the problem if it was caused by the firmware not regonising the second ESP.

This won't interfere with the Windows boot manager as UEFI supports multi-boot natively.

[versed drift]

Ok i don't know what we are doing but i trust you 😄

[cunning tangle]

However I need to say this before continue

Disclaimer of Liability
Whilst I will endeavour to take reasonable measures in aiding you with the issue at hand in good faith, there is no guarantee of absolute efficacy of such measures. In providing any assistance or advice concerning your matter, I hereby disclaim any and all responsibility or liability for any potential loss or damage to physical or digital data, equipment or property wihch may arise as a result of any action taken or counsel given. By heeding the advice proffered, you acknowledge and accept this disclaimer.

Do you wish to continue?

[versed drift]

Yes 😄

whatever happens happens

[cunning tangle]

Well first use fdisk to mark /dev/nvme0n1p3 as "Linux Filesystem"

[versed drift]

its already broken so

[versed drift]

how?

[cunning tangle]

fdisk /dev/nvme0n1

Then type t at the fdisk prompt.

[versed drift]

then it asks for partition number

[cunning tangle]

When asked

Partition number (1,2, default 5):

type 3

It will display

Partition type or alias (type L to list all): 

type 20

The output should be

Changed type of partition 'EFI System' to 'Linux filesystem'.

Command (m for help): 

[versed drift]

yes

😄

[cunning tangle]

Then type w and enter

[versed drift]

excactly

ok i did it

[cunning tangle]

Let's verify that,

fdisk -l /dev/nvme0n1

[versed drift]

Disk /dev/nvme0n1: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: Samsung SSD 980 PRO 2TB
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: gpt
Disk identifier: 8E576950-BE10-498D-8DD7-6AEA26EDC11E

Device              Start        End    Sectors   Size Type
/dev/nvme0n1p1       2048     206847     204800   100M EFI System
/dev/nvme0n1p2     206848 2883024895 2882818048   1.3T Microsoft basic data
/dev/nvme0n1p3 2883024896 2883639295     614400   300M Linux filesystem
/dev/nvme0n1p4 2883639296 2949175295   65536000  31.3G Linux swap
/dev/nvme0n1p5 2949175296 3907029134  957853839 456.7G Linux filesystem```

[cunning tangle]

Sehr gut.
Next, mount the OS tree

mount -o subvol=/@ /dev/nvme0n1p5 /mnt
mount /dev/nvme0n1p1 /mnt/boot/efi
arch-chroot /mnt

[versed drift]

ok done

[cunning tangle]

Change the 8th line of your /etc/fstab
from

UUID=C146-AA85 /boot/efi vfat defaults,noatime 0 2

to

UUID=6CF6-2B9A /boot/efi vfat defaults,noatime 0 2

Afterwards

mkinitcpio -P

Finally, reinstall grub

grub-install --target=x86_64-efi --bootloader-id=GRUB --efi-directory=/boot/efi --recheck

Post the output of efibootmgr when it is finished.

[versed drift]

No presets found in /etc/mkinitcpio.d

[cunning tangle]

pacman -Qkk mkinitcpio

[versed drift]

pacman -Qkk mkinitcpio
warning: mkinitcpio: /etc (Permissions mismatch)
warning: mkinitcpio: /usr (Permissions mismatch)
warning: mkinitcpio: /usr/bin (Permissions mismatch)
warning: mkinitcpio: /usr/lib (Permissions mismatch)
warning: mkinitcpio: /usr/lib/initcpio (Permissions mismatch)
warning: mkinitcpio: /usr/lib/initcpio/hooks (Permissions mismatch)
warning: mkinitcpio: /usr/lib/initcpio/install (Permissions mismatch)
warning: mkinitcpio: /usr/lib/initcpio/udev (Permissions mismatch)
warning: mkinitcpio: /usr/lib/kernel (Permissions mismatch)
warning: mkinitcpio: /usr/lib/kernel/install.d (Permissions mismatch)
warning: mkinitcpio: /usr/lib/systemd (Permissions mismatch)
warning: mkinitcpio: /usr/lib/systemd/system (Permissions mismatch)
warning: mkinitcpio: /usr/lib/tmpfiles.d (Permissions mismatch)
warning: mkinitcpio: /usr/share (Permissions mismatch)
warning: mkinitcpio: /usr/share/bash-completion (Permissions mismatch)
warning: mkinitcpio: /usr/share/bash-completion/completions (Permissions mismatch)
warning: mkinitcpio: /usr/share/libalpm (Permissions mismatch)
warning: mkinitcpio: /usr/share/libalpm/hooks (Permissions mismatch)
warning: mkinitcpio: /usr/share/libalpm/scripts (Permissions mismatch)
warning: mkinitcpio: /usr/share/man (Permissions mismatch)
warning: mkinitcpio: /usr/share/man/man1 (Permissions mismatch)
warning: mkinitcpio: /usr/share/man/man5 (Permissions mismatch)
warning: mkinitcpio: /usr/share/man/man8 (Permissions mismatch)
warning: mkinitcpio: /usr/share/zsh (Permissions mismatch)
warning: mkinitcpio: /usr/share/zsh/site-functions (Permissions mismatch)
mkinitcpio: 84 total files, 25 altered files```

[cunning tangle]

 stat /etc /usr /usr/bin /usr/share  

[versed drift]

File: /etc
Size: 4752            Blocks: 0          IO Block: 4096   directory
Device: 0,66    Inode: 274         Links: 1
Access: (0777/drwxrwxrwx)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2023-07-18 15:27:12.204464530 +0400
Modify: 2023-07-18 15:27:11.676467679 +0400
Change: 2023-07-18 15:27:11.676467679 +0400
Birth: 2023-05-31 04:45:19.658561823 +0400
File: /usr
Size: 80              Blocks: 0          IO Block: 4096   directory
Device: 0,66    Inode: 278         Links: 1
Access: (0777/drwxrwxrwx)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2023-07-18 15:27:11.753467219 +0400
Modify: 2023-07-18 15:27:11.753467219 +0400
Change: 2023-07-18 15:27:11.753467219 +0400
Birth: 2023-05-31 04:45:19.658561823 +0400
File: /usr/bin
Size: 84248           Blocks: 0          IO Block: 4096   directory
Device: 0,66    Inode: 1177        Links: 1
Access: (0777/drwxrwxrwx)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2023-07-18 15:27:11.597468150 +0400
Modify: 2023-07-18 15:27:11.598468144 +0400
Change: 2023-07-18 15:27:11.598468144 +0400
Birth: 2023-05-31 04:45:20.030556991 +0400
File: /usr/share
Size: 5046            Blocks: 0          IO Block: 4096   directory
Device: 0,66    Inode: 1182        Links: 1
Access: (0777/drwxrwxrwx)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2023-07-18 15:27:11.596468156 +0400
Modify: 2023-07-18 15:25:53.011936802 +0400
Change: 2023-07-18 15:25:53.011936802 +0400```

[cunning tangle]

I will say that your system is more broken than you have described.
World read write execute permissions on important directories like /etc, /usr, /usr/bin is no good,
Have you done any sort of chroot -R / in the past?

[cunning tangle]

stat /etc/shadow

[versed drift]

yes i did chroot -R 777

[versed drift]

File: /etc/shadow
Size: 1197            Blocks: 8          IO Block: 4096   regular file
Device: 0,66    Inode: 1468220     Links: 1
Access: (0777/-rwxrwxrwx)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2023-07-18 12:23:10.279937328 +0400
Modify: 2023-07-04 23:20:26.970996764 +0400
Change: 2023-07-18 11:54:57.539615963 +0400
Birth: 2023-07-04 23:20:26.970996764 +0400```

[cunning tangle]

!!!

stat /etc/sudoers

[versed drift]

File: /etc/sudoers
Size: 3319            Blocks: 8          IO Block: 4096   regular file
Device: 0,66    Inode: 1131        Links: 1
Access: (0777/-rwxrwxrwx)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2023-05-31 04:45:20.008557276 +0400
Modify: 2023-03-06 21:55:35.000000000 +0400
Change: 2023-07-18 11:54:57.536615991 +0400
Birth: 2023-05-31 04:45:20.008557276 +0400```

[cunning tangle]

Ja, your system is finished. everyone is root in principle.

[versed drift]

what does it mean?

[cunning tangle]

Every file on your system has permission 777 (full read write execute permission for everyone)

[versed drift]

is it bad? 😄

i don't have sketchy stuff

[cunning tangle]

even your /etc/shadow (related to password) /etc/sudoers is 777

This is madness in its purest form

I suggest a reinstall

[versed drift]

but i have a project

on that partition

that's why i wanna get into it

[cunning tangle]

Copy your important project files from the Live ISO to another location.

[versed drift]

how can i access it?

[cunning tangle]

Exit the chroot and umount /mnt/boot/efi, /mnt
You can mount the home subvolume with

mount -o subvol=/@home /dev/nvme0n1p5 /mnt

[versed drift]

mount: /mnt: /dev/nvme0n1p5 already mounted on /mnt.
dmesg(1) may have more information after failed mount system call.```

[cunning tangle]

umount -l /mnt/boot/efi
umount -l /mnt
mount -o subvol=/@home /dev/nvme0n1p5 /mnt

[versed drift]

ok i did it

yay

i see my stuff

[cunning tangle]

your home directory is now mounted in /mnt, so you can copy your stuff now

[versed drift]

Thank you so much

man

you don't even know how much you helped me

[cunning tangle]

You are welcome

If you maintained a marvelous snapshot of subvolume /@ before this magnificent chmod 777 mayhem. Mending your machine might be possible.

[versed drift]

nah imma just install some other os

i wanted to reinstall it too for quite a while

should i close this post?

[cunning tangle]

Yes, mayhap a more measured maneuver is a reinstallation.

[cunning tangle]

OK. change to title to [SOLVED] Can't chroot into /mnt

[versed drift]

Thanks 🙂