You are not logged in.
Hi all,
When I boot my system, I get
Starting version 246.6-1-arch
/dev/sc3: clean, .../... files .../... blocks
mount: /new_root: unknown filesystem type 'ext4'
sh: can't access tty: job control turned off
rootfs#
So far, I've already booted to an installation USB and reinstalled the base "linux" package and rebuilt the initramfs and redid "genfstab".
I installed arch for UEFI so my /boot folder is a separate FAT partition that's mounted to root. I made sure the boot partition was mounted in root when I redid the initramfs.
I disabled all the other mount points for my other two drives when a redid the fstab so they aren't a factor.
I performed an fsck on all the drives and they all check out so I can't tell where the unknown filesystem error is coming from.
I'm really baffled.
Last edited by RobinLikesToCode (2020-11-12 23:09:34)
Offline
How are you booting? Bootloader? efibootmgr?
Share your boot parameters
Last edited by icar (2020-11-12 00:52:49)
Offline
How are you booting? Bootloader? efibootmgr?
Share your boot parameters
I use GRUB.
my kernel parameters are:
loglevel=3 quiet nvidia-drm.modset=1 resume=UUID=blahblahblah
I'm certain the kernel parameters aren't the problem. The errors aren't related to video cards.
Another weird detail is that the ext4 driver for Windows can't load my root partition now. It used to work fine in the past.
Offline
From archiso, mount root and boot, then try:
lsinitcpio /boot/initramfs-linux.ing | grep ext
Is the fallback image derped as well?
Also post the mkinitcpio.conf
If using a pastebin, preferably use a plaintest pastebin like ix.io
Offline
From archiso, mount root and boot, then try:
lsinitcpio /boot/initramfs-linux.ing | grep ext
Is the fallback image derped as well?
Also post the mkinitcpio.confIf using a pastebin, preferably use a plaintest pastebin like ix.io
The only two lines on my configuration file that do anything are,
MODULES=(nvidia nvidia_modset nvidia-uvm nvidia_drm)
HOOKS=(base udev autodetect modconf block keyboard consolefont fsck resume filesystem)
My fallback image has the same error.
grep-ing ext with both the normal and the fallback images outputs,
usr/bin/fsck.ext2
usr/bin/fsck.ext3
usr/bin/fsck.ext4
usr/lib/libext2fs.so.2
Is it possible I'm missing a "libext4fs.so"?
Last edited by RobinLikesToCode (2020-11-12 02:53:21)
Offline
usr/lib/modules/5.9.8-arch1-1/kernel/fs/ext4/ext4.ko.xz is not in the initrd?
Offline
usr/lib/modules/5.9.8-arch1-1/kernel/fs/ext4/ext4.ko.xz is not in the initrd?
No, apparently not, because grep would have picked it up from the lsinitcpio output.
Offline
Boot live media, chroot in, then what is the output of:
pacman -Qkk linux
mkinitcpio -v -p linux
Offline
what do you have in /lib/modules/ in the initramfs?
Edit: nevermind, I see the problem. You have a typo in your hooks, it's filesystems, not filesystem.
Last edited by Scimmia (2020-11-12 05:21:39)
Online
what do you have in /lib/modules/ in the initramfs?
Edit: nevermind, I see the problem. You have a typo in your hooks, it's filesystems, not filesystem.
The typo was actually with my post here. "filesystems" is used in the HOOKS section (otherwise it would yell at me that "filesystem" wasn't found).
The mystery continues!
Offline
Last update, I backed up the home directory and wiped + reinstalled.
The problem's gone now.
The one explanation I could think of was that the actual filesystem for the root partition was corrupted at some point and became unrecognizable.
Offline
Use [SOLVED] if you gave up, at this point since you wiped that and erased whatever was wrong...
If you consider this thread to be of no further use for the forums due to its obscure nature and inconclusive issue/solution, request deletion to a mod with the magic words using report on the first post.
Offline
Please do not use [CLOSED] - that is for the forum to indicate administratively closed threads.
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline