(SOLVED) NVME SDD changes name after each reboot

flowerpummeler · 2024-10-16 22:41:43

hi yall, very new to linux, ive installed and configured arch with little problem, the only exception being my SSD, which switches name each time i reboot my laptop which sends me to emergency mode and forces me to change the fstab and remount the drives on each reboot, any idea what could be causing this?

lsblk lists this:

nvme1n1
|-nvme1n1p1 1G
|-nvme1n1p2 4G
|-nvme1n1p3 471,9G
nvme0n1
|-md127 0B

so in this case if i were to reboot, a name switch would occur in which nvme1n1 becomes nvme0n1 and vice-versa

Last edited by flowerpummeler (2024-10-19 21:08:34)

V1del · 2024-10-16 22:47:34

This is completely normal if you have multiple nvme ssds. Which is why it's strongly recommended to use persistent device naming in all places of relevance, your fstab and your bootloader config first and foremost.

flowerpummeler · 2024-10-17 00:26:43

working on this, set a label for each nvme partition, should i replace the /dev/nvme with LABEL=NAME in fstab or set it above with the UUID?

flowerpummeler · 2024-10-17 01:20:11

update on this, i set a label for each nvme partition, set them in fstab the following way:
/dev/disk/by-label/nvmeroot / ext4

/dev/disk/by-label/nvmeboot /boot/efi vfat

/dev/disk/by-label/nvmeswap none swap

i also made sure to mount boot the boot partition and proceded to install and config grub in it, it doesnt unmount each reboot but i am stuck in nvmeroot: clean, number/number files, number/number blocks and had to switch to a second terminal using ctrl alt f2 to check fstab config, not sure what im doing wrong

Last edited by flowerpummeler (2024-10-17 01:21:41)

seth · 2024-10-17 06:51:16

it doesnt unmount each reboot but i am stuck in nvmeroot: clean, number/number files, number/number blocks and had to switch to a second terminal using ctrl alt f2

English, please…?

When do you expect what to unmount?
Is this on boots, shutdowns or reboots only?

So, first of all, just because something is the last line in the boot process doesn't at all mean it's related to your issues (unless of course it's an error)
Second, if you can switch the TTY and login and inspect /etc/fstab, the system has most likely fully booted and mounted all relevant partitions.
Check

lsblk -f

Your issue is most likely your display server or lack thereof, so please elaborate on that.
In doubt please post your complete system journal for the boot (from TTY2):

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

flowerpummeler · 2024-10-17 10:45:12

apologies for my wonky english, its not my first language. what i meant with it "doesnt unmount each reboot" is that before i labeled my nvme partitions, they changed names each reboot and unmounted. so if i have nvme0n1p1 mounted to /boot/efi if i did a shutdown it would change names to nvme1n1p1 and no longer be mounted to /boot/efi, this happened anytime i rebooted or shut down my system. i fixed this by labeling them and using those labeled partitions in my fstab and grub bootloader (and mounting them using the /mount command)

by doing this, i fixed that issue, however when i boot up my system now, it gets stuck on "nvmeroot: clean, 1234/12345 files 1234/12345 blocks, i am able to switch tty but i cannot start my WM because xorg gives me the "no display" error

ill provide journal file when im back home, i am busy right now.

seth · 2024-10-17 12:07:45

before i labeled my nvme partitions, they changed names each reboot

That part is completely normal, the device names are first-come-first-serve and therefore the order not deterministic.

The more important question is whether and what is the problem *now*.

(it's btw. less of a syntax issue, the sentence just doesn't make a whole lot of sense logically

flowerpummeler · 2024-10-18 22:23:54

hi, i finally got time to upload my journal file to 0x0, here is the link: https://0x0.st/XIhk.txt

seth · 2024-10-19 07:21:57

I thought there was gonna be some asmmive issues in that 8MB log, but it's just 38 boots since october 14th…
Next time please don't omit the journalctl parameters (in this case "-b") and generally don't type random stuff into a terminal

On topic

oct 18 19:10:32 archvivobook systemd[1]: Started Light Display Manager.
oct 18 19:10:32 archvivobook lightdm[777]: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
oct 18 19:10:32 archvivobook systemd[1]: Reached target Graphical Interface.
oct 18 19:10:32 archvivobook systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
oct 18 19:10:32 archvivobook systemd[1]: lightdm.service: Failed with result 'exit-code'.

You lightdm log is in /var/log/ - inspect/upload that, it should tell more about the failure.
Also please post your Xorg.0.log log

flowerpummeler · 2024-10-19 12:57:42

ahaha sorry i tend to just press keys when im bored. ill make sure to upload those logs as well.

flowerpummeler · 2024-10-19 19:17:08

hello, i got the log files
https://pastebin.com/s9gZCYbc - journalctl with boot option

https://pastebin.com/3stWGAGp - lightdm log

https://pastebin.com/wQLh1HvV - Xorg log

seth · 2024-10-19 20:39:50

[+0.04s] DEBUG: Process 973 exited with return value 1
[+0.04s] DEBUG: XServer 0: X server stopped

[     5.798] Parse error on line 4 of section InputClass in file /etc/X11/xorg.conf.d/00-keyboard.conf
	Unexpected EOF. Missing EndSection keyword?
[     5.798] (EE) Problem parsing the config file
[     5.798] (EE) Error parsing the config file

=> fix that file.

flowerpummeler · 2024-10-19 20:54:31

FIXED!!! TYSM seth and v1del for your help i cant believe a keyboard config was the culprit

Arch Linux

#1 2024-10-16 22:41:43

(SOLVED) NVME SDD changes name after each reboot

#2 2024-10-16 22:47:34

Re: (SOLVED) NVME SDD changes name after each reboot

#3 2024-10-17 00:26:43

Re: (SOLVED) NVME SDD changes name after each reboot

#4 2024-10-17 01:20:11

Re: (SOLVED) NVME SDD changes name after each reboot

#5 2024-10-17 06:51:16

Re: (SOLVED) NVME SDD changes name after each reboot

#6 2024-10-17 10:45:12

Re: (SOLVED) NVME SDD changes name after each reboot

#7 2024-10-17 12:07:45

Re: (SOLVED) NVME SDD changes name after each reboot

#8 2024-10-18 22:23:54

Re: (SOLVED) NVME SDD changes name after each reboot

#9 2024-10-19 07:21:57

Re: (SOLVED) NVME SDD changes name after each reboot

#10 2024-10-19 12:57:42

Re: (SOLVED) NVME SDD changes name after each reboot

#11 2024-10-19 19:17:08

Re: (SOLVED) NVME SDD changes name after each reboot

#12 2024-10-19 20:39:50

Re: (SOLVED) NVME SDD changes name after each reboot

#13 2024-10-19 20:54:31

Re: (SOLVED) NVME SDD changes name after each reboot

Board footer