There’s something there…lets see what we can learn from the output @TriMoon requested.
or
parted --list
Welp, that’s it. I know absolutely nothing about LUKS/encryption, so I’m out.
Good luck, though.
I opened the partition using instructions here, then ran fsck on it.
I wouldn’t expect the encryption to be related to the kernel module error or manjaro-chroot error, no?
It would. AFAIK there’s a special type of instructions for chroot with encryption. But as I mentioned, I know absolutely nothing about it, so the possibility that I’m wrong does exist.
I got manjaro-chroot to work using instructions here. I ran the command you first posted above as a solution. I’ll see if it fixed the module error.
@Mirdarthos, after running this command, I get to this point
Resolving dependencies...
Checking inter-conflicts...
To build (20):
anaconda 2022.10-1 (2022.05-1) AUR
atom 1.61.0beta0-3 (1.61.0beta0-2) AUR
ceph-libs 17.2.5-5 (15.2.17-1) AUR
metis 5.1.0.p11-1 (5.1.0.p10-2) AUR
coin-or-ipopt 3.14.11-1 (3.14.10-1) AUR
gn-m85 0.1792.7d7e8dee-1 AUR
python2 2.7.18-8 (2.7.18-5) AUR
electron9 9.4.4-6 (9.4.4-5) AUR
voro++ 0.4.6-2 AUR
gmsh 4.11.1-1 (4.11.0-1) AUR
gnome-icon-theme 3.12.0-7 (3.12.0-6) AUR
google-chrome 110.0.5481.77-1 (109.0.5414.74-1) AUR
scotch 7.0.3-1 (7.0.1-1) AUR
mmg 5.7.1-1 (5.6.0-2) AUR
python-conda-package-handling 1.8.1-1 (1.7.3-2) AUR
python-conda 4.14.0-1 (4.12.0-2) AUR
python-ezdxf 1.0.1b1-1 (0.17.2-1) AUR
python-multimethod 1.9.1-1 (1.9-1) AUR
qpdfview 0.5.0-1 (0.4.18-2) AUR
yay-git 11.3.1.r92.gc40e949-1 (11.1.2.r4.ged62496-1) AUR
Edit build files : [e]
Apply transaction ? [e/y/N]
Typing y yields:
Cloning anaconda build files...
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
Error: Failed to build anaconda
There was an error upgrading the system. AUR packages not upgraded.
What happens when you do just:
pamac upgrade
no errors, but when I go back and try to log in again, I just get a filepath /dev/mapper.... and a blinking cursor. Previously, this is where the kernel module error would show up. The error is no longer here, but nothing is happening…
perhaps I should admit defeat
Sometimes it is quicker.
As long as you learned something.
yes… don’t force shutdown on manjaro
Don’t on any system no matter which distro or operating system 
2 Likes
A very good lesson, except…
You shouldn’t force shutdown. FULL STOP
1 Like
And there are file systems that don’t throw up when they’re forcefully shut down.
- jffs2 (tested on 30,000 devices over >12 years)
- btrfs (tested on 20,000+ devices over > 5 years)
There may be others among the file systems that keep a journal. But I haven’t tested them. (This may not be true for encrypted systems, and not for all DE’s)
But any file system is happy not to be violently treated
These have an extra layer that needs to flush actual data to the device for the changes to be permanently stored, so no matter the filesystem inside it could still be broken by a forced power-off…
Bottom line: Forced power off = Always asking for trouble…
This is the Manjaro Linux forum and has absolutely nothing to do with any version of Windows.
@moderators should this be on here?
1 Like
IMHO, no…
Especially if you look at the account age…
Exactly!