cant mount home on boot
cant mount home on boot
Im giving a go fedora silverblue on a new laptop but Im unable to boot (and since im a linux noob the first thing i tried was installing it fresh again but that didnt resolve it).
its a single drive partitioned to ext4 and encrypted with luks (its basically the default config from the fedora installation)
any ideas for things to try?
You're viewing a single thread.
Isn't the default filesystem btrfs? Why did you go with ext4
@possiblylinux127 @evasync I can't speak for them, but I've had btrfs blow up in ways I could not fix. I didn't just lose a file but the entire file system. I have NEVER had this happen in many years with ext4.
Was that in the last 5 years? If it was btrfs is now far more stable. It has never blown up for me and it has in fact saved my data a few times.
@possiblylinux127 It was this year. Glad it's working for you. I'll stick with what works for me and has provided adequate performance for years.
I've only had this happen once and it turned out it was because my ram was shitting out errors that were saved to disk so it ended up not being btrfs's fault
Permanently Deleted
NixOS and ext4 user here with no problems. Care to elaborate?
Permanently Deleted
Seems like this can be prevented from reaching that point by properly deleting old generations regularly though right?
Permanently Deleted
20 or 30 generations 😹
I have space for 1 😭
Edit: you've got me worried now, is the behavior you're referring to normal running out of inodes behavior or some sort of bug? Is this specific to ext4 or does it also affect btrfs nix stores?
I've run across the information that ext4 can be created with extra inodes but cannot add inodes to an existing filesystem.
Permanently Deleted
Thank you for providing the quote!!
Lol same thing happened to me about 6 months ago. Overheating and/or a failing M2 and system corruption. btrfs got weird and troubleshooting only made it worse.