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?

-1 points

That’s what she said.

permalink
report
reply
3 points

Isn’t the default filesystem btrfs? Why did you go with ext4

permalink
report
reply
5 points

@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.

permalink
report
parent
reply
5 points

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.

permalink
report
parent
reply
2 points

@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.

permalink
report
parent
reply
3 points

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

permalink
report
parent
reply
2 points
*
Deleted by creator
permalink
report
parent
reply
4 points

NixOS and ext4 user here with no problems. Care to elaborate?

permalink
report
parent
reply
1 point

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.

permalink
report
parent
reply
8 points

There well may be hardware issues, but with ext4 it rarely corrupts the entire file system. You might end up with some data not flushed so you’ll have some inodes that don’t point to anything that you’ll remove with fsck upon boot, but btrfs, I’ve had it corrupt and lose the entire file system. I’ve used ext2-through-ext4 for as long as they’ve existed and never lost a file system though back in the ext2 days I had to hand repair them a few times, but ext2 was sufficiently simple that that was not difficult, but within two weeks of turning up a btrfs file system it shit itself in ways I could not recover anything, the entire file system was lost. If I did not have backups, which of course I always do, I would have been completely fuxored. It is my opinion that btrfs and xfs, both of which have advantages, are also both not sufficiently stable for production use.

permalink
report
reply
23 points

The error says /home is a symlink, what if you ls -l /home?

Since this is an atomic distro, /home might be a symlink to /var/home.

permalink
report
reply
1 point

the command returns my user dir and a lost+found dir

permalink
report
parent
reply
4 points
Deleted by creator
permalink
report
parent
reply
1 point

What’s in lost+found

permalink
report
parent
reply
6 points

yes it is a symlink to /var/home

permalink
report
parent
reply
8 points

So shouldn’t you mount your home partition on /var/home instead?

permalink
report
parent
reply
3 points

This feels like a winning strategy

permalink
report
parent
reply
6 points
*

rm /home
mkdir /home
make /var/home a symlink to it.
Alternative, edit your /etc/fstab to mount on /var/home.

permalink
report
reply
4 points

Don’t you have that backwards? This is an atomic distro, and you’d want to mkdir /var/home then symlink /home from that, no? Otherwise, you’ll wind up with a home directory that is immutable.

permalink
report
parent
reply
5 points

@Telorand I am not familiar with that distro, I am however familiar with how mount works. As far as what is immutable and what is not, you can set with chattr +i file/directory or chattr -i file/directory.

permalink
report
parent
reply
2 points

editing the /etc/fstab didnt work (I just changed the path but not sure if the uuid plays any part) but ill give the rm/mkdir part a go

permalink
report
parent
reply
2 points

Did you update your initramfs after? The new fstab doesn’t apply until you refresh that

permalink
report
parent
reply
2 points

No but I rebooted the system after the change. do still need to update it regardless the reboot?

permalink
report
parent
reply
1 point

Make sure the uuid matches the uuid of the home partition you want, you can list uuids with blkid I think, big noob here too I just spent my last week trying to figure out why it wouldnt mount my boot partition and the problem was the UUID…

permalink
report
parent
reply

Linux

!linux@lemmy.ml

Create post

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word “Linux” in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

  • Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
  • No misinformation
  • No NSFW content
  • No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

Community stats

  • 8K

    Monthly active users

  • 3.7K

    Posts

  • 47K

    Comments