[SOLVED]mount : unknown filesystem type

Aarnaud · 2023-04-28 10:01:01

Hello everyone,

It's my first post here so please let me know if I did anything wrong in it.

I messed a bit with my partitions (/home in xfs, root in btrfs and /boot in vfat). Since then when I boot I get this systemd error :

Failed to mount /home. See systemctl status home.mount for details

and the same for /boot.

So i tried

 systemctl status home.mount

the output was:

/home : unknown filesystem type 'xfs'
failed to mount /home

Mounting manually outputs the same error.

I did some research and saw that this error is often caused by not rebooting after a kernel update.
I rebooted and got the same error both for /home and /boot.
I booted on a live USB and was able to mount everything without problem.So i chrooted and did

 sudo pacman -Syu

and

 pacman -S linux

then rebooted and got the same error.

I don't understand. Why can the partitions be mounted in chroot but not directly in arch??
Any help would be greatly appreciated.

Last edited by Aarnaud (2023-05-23 20:01:56)

schard · 2023-04-28 11:00:30

# pacman -Q linux
# uname -r
# stat /usr/lib/modules/6.2.12-arch1-1/kernel/fs/xfs/xfs.ko.zst

Last edited by schard (2023-04-28 11:01:54)

Aarnaud · 2023-04-28 12:17:58

Thank you for the response.

pacman -Q linux
linux 6.2.12.arch1-1

uname -r
6.2.9-arch1-1

So the kernel versions are different. How can I fix that?

schard · 2023-04-28 12:34:33

Reboot into the new kernel.
Probably the new kernel was installed without /boot mounted and thus is not being detected by the bootloader.
So make sure that your boot partition is mounted properly, then reinstall linux, then reboot.

Last edited by schard (2023-04-28 12:36:47)

Aarnaud · 2023-04-30 09:54:32

Sorry for the late answer.
I started the arch ISO, mounted my root and my /boot, did pacman -Syu and pacman -S Linux.

Everything ran fine, but I still got the same error.

Uname -r is still showing the wrong version of the kernel.

Last edited by Aarnaud (2023-04-30 09:55:36)

Head_on_a_Stick · 2023-04-30 10:55:21

Please share your bootloader configuration file(s) and the output of

efibootmgr -u

Also:

Aarnaud wrote:

I messed a bit with my partitions

I think we need more detail here. Please post the exact, full commands used to "mess" the partitions.

seth · 2023-04-30 14:29:02

Also mabe the result, "lsblk -f" (from the iso, don't chroot)
And "cat /proc/cmdline" from the failing boot.

Aarnaud · 2023-05-01 21:27:05

Here's my refind.conf :
https://hastebin.com/share/uzeyowomuh.graphql

My fstab:
https://hastebin.com/share/gucuxaleza.ini

seth wrote:

I think we need more detail here. Please post the exact, full commands used to "mess" the partitions.

I don't remember exactly. I used Gparted. I moved my boot partition and expanded my root.

cat /proc/cmdline

root=PARTUUID=8937f3ad-0e8b-494b079b-8cb06a3a8418 rw initrd=\intel-ucode.img rootflags=subvol=@ initrd=\initramfs-linux.img

The others commands have very long outputs and I don't know how to save them. If someone could help me I'd update this post with the necessary information.

Edit :

 lsblk-f

returns https://0x0.st/HP0b.txt

efibootmgr -u for some reason returns a .bin file that I cannot open. Help would be welcome here.

Last edited by Aarnaud (2023-05-02 17:25:46)

seth · 2023-05-01 21:31:41

lsblk -f | curl -F 'file=@-' 0x0.st

Aarnaud · 2023-05-07 13:59:09

I post this reply just to say that I tried to include all the necessary information, and to thank in advance anyone who could help me.

seth · 2023-05-07 14:50:32

├─nvme1n1p5 vfat FAT32 BOOT B811-7B61
├─nvme0n1p6 vfat FAT32 BOOT B811-7B61

This looks like trouble - you've two nvme's and the same VFAT on both.
Depending on which device you boot from you might have mounted the wrong boot partition.
Try the other and re-install the kernel.

Also root=PARTUUID=8937f3ad-0e8b-494b079b-8cb06a3a8418 might be off

lsblk -o PATH,FSTYPE,FSVER,LABEL,UUID,PARTUUID,FSAVAIL,FSUSE%,MOUNTPOINTS

Aarnaud · 2023-05-08 09:10:59

seth wrote:

Depending on which device you boot from you might have mounted the wrong boot partition.
Try the other and re-install the kernel.

I did that and arch is booting. Thank you so much!

But my display manager doesn't start. Arch seems to boot normally but my screen is just blinking gray and black every second. I can't open tty2 because my screen just turns off.
Of course I've never had this issue before.
If this is relevant I'm using optimus-manager for my Nvidia and Intel GPU. My display manager is lightDM.

Last edited by Aarnaud (2023-05-08 09:11:28)

seth · 2023-05-08 12:07:13

Boot the multi-user.target (2nd link below) and post your xorg and lightdm logs (in /var/log) and the journal of the previous boot (the one trying to start lightdm)

sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st

Aarnaud · 2023-05-08 13:32:25

My Xorg.0.log :
https://0x0.st/HZxb.txt

My lightdm.log :
https://0x0.st/HZxA.txt

My boot log :
https://0x0.st/HZxB.txt

seth · 2023-05-08 13:39:16

[   749.791] (WW) Warning, couldn't open module glxserver_nvidia
[   749.791] (EE) NVIDIA: Failed to load module "glxserver_nvidia" (module does not exist, 0)
[   749.791] (EE) NVIDIA(0): Failed to initialize the GLX module; please check in your X
[   749.791] (EE) NVIDIA(0):     log file that the GLX module has been loaded in your X
[   749.791] (EE) NVIDIA(0):     server, and that the module is the NVIDIA GLX module.  If
[   749.791] (EE) NVIDIA(0):     you continue to encounter problems, Please try
[   749.791] (EE) NVIDIA(0):     reinstalling the NVIDIA driver.
[   749.791] (II) NVIDIA: The X server does not support PRIME Render Offload.

ModulePath doesn't get extended, nvidia driver is loaded because of config, not because of a match.

https://wiki.archlinux.org/title/NVIDIA … de_setting
Set "nvidia_drm.modeset=1" and make sure that either the nvidia modules and i915 are in the MODULES list of your mkinitcpio (don't forget to rebuild the initramfs)

Did you fix the FS UUID collision?
Otherwise make sure the proper partition is mounted before regenerating the initramfs.

Aarnaud · 2023-05-10 09:14:31

I set "nvidia_drm.modeset=1" in my refind.conf, I added i915 in my MODULES section of mkinitcpio.conf and ran

 pacman -S linux

All of that in both my boot partitions.
I still get the same issue.

seth · 2023-05-10 11:14:53

Please post an udpated xorg log and system journal.

Aarnaud · 2023-05-16 12:59:58

My systemctl boot log
0x0.st/HNw4.txt
My lightDm log
0x0.st/HNwJ.txt
My xorg.0.log
0x0.st/HNwy.txt

seth · 2023-05-16 14:57:13

[    12.316] (==) Log file: "/var/log/Xorg.0.log", Time: Tue May 16 13:31:02 2023
[    12.317] (==) Using config file: "/etc/xorg.conf"
…
[    12.339] (WW) Warning, couldn't open module glxserver_nvidia
[    12.339] (EE) NVIDIA: Failed to load module "glxserver_nvidia" (module does not exist, 0)
[    12.339] (EE) NVIDIA(0): Failed to initialize the GLX module; please check in your X

Exact same situation.

mai 16 13:30:53 ArchBTW kernel: Linux version 6.3.1-arch1-1 (linux@archlinux) (gcc (GCC) 13.1.1 20230429, GNU ld (GNU Binutils) 2.40.0) #1 SMP PREEMPT_DYNAMIC Mon, 01 May 2023 17:42:39 +0000
mai 16 13:30:53 ArchBTW kernel: Command line: root=PARTUUID=8937f3ad-0e8b-494b-079b-8cb06a3a8418 rw initrd=\intel-ucode.img rootflags=subvol=@ nvidia_drm.modeset=1 initrd=\initramfs-linux.img
…
mai 16 13:30:53 ArchBTW kernel: i915 0000:00:02.0: vgaarb: deactivate vga console
mai 16 13:30:53 ArchBTW kernel: i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem
mai 16 13:30:53 ArchBTW kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
mai 16 13:30:53 ArchBTW kernel: [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 0
…
mai 16 13:30:56 ArchBTW kernel: nvidia: loading out-of-tree module taints kernel.
mai 16 13:30:56 ArchBTW kernel: nvidia: module license 'NVIDIA' taints kernel.
mai 16 13:30:56 ArchBTW kernel: Disabling lock debugging due to kernel taint
mai 16 13:30:56 ArchBTW kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel
mai 16 13:30:56 ArchBTW kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 510
mai 16 13:30:56 ArchBTW kernel: 
mai 16 13:30:56 ArchBTW kernel: nvidia 0000:01:00.0: enabling device (0000 -> 0003)
mai 16 13:30:56 ArchBTW kernel: nvidia 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=none
mai 16 13:30:56 ArchBTW kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  530.41.03  Thu Mar 16 19:48:20 UTC 2023

The nvidia module still loads extremely late

I added i915 in my MODULES section of mkinitcpio.conf and ran

seth wrote:

make sure that either the nvidia modules and i915 are in the MODULES list of your mkinitcpio (don't forget to rebuild the initramfs)

Bad english, I guess: all of them. i915 and all the nvidia modules in the article.

Aarnaud · 2023-05-17 09:33:54

Seth wrote:

all the nvidia modules in the article.

I can't find what Nvidia modules I am supposed to add. I added

nvidia_modeset

and

nvidia

and regenerated the initramfs. I got the same error.
Btw I fixed the UUID collision.

seth · 2023-05-17 12:00:28

I can't find what Nvidia modules I am supposed to add.

seth wrote:

https://wiki.archlinux.org/title/NVIDIA … de_setting

Aarnaud · 2023-05-17 15:01:43

I added all modules listed and got the same error.
I can start my WM using

startx

But running

systemctl start lightDM

cause the same error.

seth · 2023-05-17 15:11:01

Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Aarnaud · 2023-05-18 09:36:03

Now whenever I want to send a file to 0x0.st I get

curl:URL using bad/illegal format or missing URL

I'm connected to the internet and I can access 0x0.st through Firefox.

seth · 2023-05-18 13:23:58

You need to use the above verbatim, the single quotes are single quotes and not graves/acutes or whatever you may have typed there.

Arch Linux

#1 2023-04-28 10:01:01

[SOLVED]mount : unknown filesystem type

#2 2023-04-28 11:00:30

Re: [SOLVED]mount : unknown filesystem type

#3 2023-04-28 12:17:58

Re: [SOLVED]mount : unknown filesystem type

#4 2023-04-28 12:34:33

Re: [SOLVED]mount : unknown filesystem type

#5 2023-04-30 09:54:32

Re: [SOLVED]mount : unknown filesystem type

#6 2023-04-30 10:55:21

Re: [SOLVED]mount : unknown filesystem type

#7 2023-04-30 14:29:02

Re: [SOLVED]mount : unknown filesystem type

#8 2023-05-01 21:27:05

Re: [SOLVED]mount : unknown filesystem type

#9 2023-05-01 21:31:41

Re: [SOLVED]mount : unknown filesystem type

#10 2023-05-07 13:59:09

Re: [SOLVED]mount : unknown filesystem type

#11 2023-05-07 14:50:32

Re: [SOLVED]mount : unknown filesystem type

#12 2023-05-08 09:10:59

Re: [SOLVED]mount : unknown filesystem type

#13 2023-05-08 12:07:13

Re: [SOLVED]mount : unknown filesystem type

#14 2023-05-08 13:32:25

Re: [SOLVED]mount : unknown filesystem type

#15 2023-05-08 13:39:16

Re: [SOLVED]mount : unknown filesystem type

#16 2023-05-10 09:14:31

Re: [SOLVED]mount : unknown filesystem type

#17 2023-05-10 11:14:53

Re: [SOLVED]mount : unknown filesystem type

#18 2023-05-16 12:59:58

Re: [SOLVED]mount : unknown filesystem type

#19 2023-05-16 14:57:13

Re: [SOLVED]mount : unknown filesystem type

#20 2023-05-17 09:33:54

Re: [SOLVED]mount : unknown filesystem type

#21 2023-05-17 12:00:28

Re: [SOLVED]mount : unknown filesystem type

#22 2023-05-17 15:01:43

Re: [SOLVED]mount : unknown filesystem type

#23 2023-05-17 15:11:01

Re: [SOLVED]mount : unknown filesystem type

#24 2023-05-18 09:36:03

Re: [SOLVED]mount : unknown filesystem type

#25 2023-05-18 13:23:58

Re: [SOLVED]mount : unknown filesystem type

Board footer