linux4noobs

1340 readers

1 users here now

linux4noobs

Noob Friendly, Expert Enabling

Whether you're a seasoned pro or the noobiest of noobs, you've found the right place for Linux support and information. With a dedication to supporting free and open source software, this community aims to ensure Linux fits your needs and works for you. From troubleshooting to tutorials, practical tips, news and more, all aspects of Linux are warmly welcomed. Join a community of like-minded enthusiasts and professionals driving Linux's ongoing evolution.

Seeking Support?

Mention your Linux distro and relevant system details.
Describe what you've tried so far.
Share your solution even if you found it yourself.
Do not delete your post. This allows other people to see possible solutions if they have a similar problem.
Properly format any scripts, code, logs, or error messages.
Be mindful to omit any sensitive information such as usernames, passwords, IP addresses, etc.

Community Rules

Keep discussions respectful and amiable. This community is a space where individuals may freely inquire, exchange thoughts, express viewpoints, and extend help without encountering belittlement. We were all a noob at one point. Differing opinions and ideas is a normal part of discourse, but it must remain civil. Offenders will be warned and/or removed.
Posts must be Linux oriented
Spam or affiliate links will not be tolerated.

founded 1 year ago

MODERATORS

PlutoParty@programming.dev

After install completes, booting into Nobara gives "Failed to start initrd-switch-root.service (sh.itjust.works)

submitted 1 year ago by MonkCanatella@sh.itjust.works to c/linux4noobs@programming.dev

9 comments fedilink hide all child comments

I'm running the nvidia official version, i have a 4090.

journalctl -xe gives "failed to switch root: specificed switch root path /ssysroot doesnot seem to be on OS tree. os-release file is missing"

I've seen some mention to try rebooting into a different kernel. I have no idea how to do that. Everything I have seen suggests commands that do not exist in the emergency mode. and I can't boot at all so I don't konw what to do.

Please advice. I asked in the discord but no one even responded and I'm not sure where to get help with this distro

you are viewing a single comment's thread
view the rest of the comments

[–] root@aussie.zone 3 points 1 year ago (1 children)

Long short but maybe the iso you downloaded was somehow corrupted?

If you tried the official, maybe try the KDE version or the pure gnome version instead? Also do checksum compare to make sure everything is fine before flashing it to your usb drive.

There is also Ventoy if you're not already using it. Makes it easy to try different distros by simply copying the iso onto the drive instead of flashing them as needed.

Good luck.

[–] MonkCanatella@sh.itjust.works 1 points 1 year ago* (last edited 1 year ago) (1 children)

I figured it out actually. it requires a /boot partition as well as a /boot/efi partition. I've installed 5-6 other distros and never had to make that partition so that's what was tripping me up. I use manual partitioning for all my installs and decided i may try the replace partition option and noticed that it was trying to add that /boot partition to a different hard drive so I just manually created that partition and it was able to boot after install. 🐧

Ventoy sounds like it could be perfect actually.

Edit: Checked out ventoy. I don't see much point to it aside from being able to use it to install multiple distros without having to run balena etcher or media writer every time you want to install a different distro.

It may be useful for testing out desktop environments, but that's about it. You only are able to try demo mode off of Ventoy. Still a cool tool

[–] AProfessional@lemmy.world 1 points 1 year ago (1 children)

I don’t think it requires two partitions, but efi must be fat32. Fedora prefers kernels going on a better filesystem and splits them.

[–] MonkCanatella@sh.itjust.works 1 points 1 year ago

Huh. I did a 1024mb fat32 partition set as /boot/efi and flagged as boot. I did that at least 7 times. It only started working when I added the extra /boot partition