Nice, more problems!

And less solutions

I never use uuids in fstab... but looks like you do

Dual booting with Windows?

@jonas-w I was thinking why not. They shouldn't change, right?

@asgs fuck no

Looks like a hardware problem with a disk, it's connection or the chipset. Or, if you are a boomer, it could be a hardware raid currently rebuilding itself...

@Oktokolo Thanks for the hints, I'm new to this scenario. I've taken them out and inserted them again, but I can't find a problem with the connection or anything. They also appear on filesystem just fine and smartctl couldn't find any errors so far.

I've tried some things and @jonas-w comment is onto something. There's 2 harddrives (sda and sdb) in a software raid0 and I tried looking for them in /dev/by-uuid and couldn't find them, but they're listed under by-partuuid, by-id and by-diskseq. I honestly don't know much about this topic, but if switchkng to partuuid would solve it, I'd be happy. I'm just worried that the software raid might screw up

@Awlex they can, if you repartition

@jonas-w would be cool if that doesn't happen out of nowhere the next time you turn on your machine

@Awlex i guess i'm just lazy, i know that nvme0n1p3 is my root and i put it in fstab and it works and don't need to look up uuids

@Awlex Software raid i don't know much about... But are you sure, that that UUID is actually the one of the whole raid and not just representing a single physical disk of it?

@Oktokolo It's for a single disk. My bad, if I made it sound otherwise

@Oktokolo Welp, I'm stupid, the uuid belonged to the raid. So after a lon search I just created the same array again, assembled it with force, updated the fstab. And then it just worked