this post was submitted on 10 Jan 2025
325 points (95.5% liked)
linuxmemes
21752 readers
1167 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Bootloader no worky can be caused by a hundred different issues. The installer may have removed the kernel or a CPIO archive (initramfs or processor microcode) that the bootloader needs. You could be missing some EFI program. If the boot entry is set to identify the root filesystem by its UUID, formatting/reinstalling would have changed the real UUID and then the bootloader wouldn't be able to find it. Maybe installing the OS simply wiped or damaged that partition.
If you have to reinstall the OS, you should also reinstall the bootloader (the OS installer usually lets you do that from the GUI), or if you're confident, update the boot entries to reflect the state of the computer. I strongly recommend using btrfs as your root filesystem instead of ext4, and use Timeshift to set up regular snapshots (btrfs) or backup clones (ext4) in case this happens again.
Darn, wish I would have read this prior to restarting the install after wiping the disk. I would have tried btrfs, it defaulted to ext4 as the machine was using mbr previously and not uefi for the boot, so I Rufus popped up with ext4 recommended and I ran with it
Ext4 is still perfectly fine. It's a mature technology, and much more stable than btrfs. Your experience will not be any different because of this.
I still recommend using Timeshift. The only downside is that only the Rsync backup method will be available, which creates a full on-disk copy of your system files.
Thanks I'll try it out once I set up the media server and figure out storage setup. Right now it just has an old 256ssd (sata) for the boot drive, originally was just taking 50gb for that and was going to use old 7200 drives for media storage. I assume I'll need to have the time shift backups running to one of the other drives or it would be useless if the drive dies.
Yes, it's best to store them on a separate hard drive. The target partition must be formatted as a Linux filesystem (ext2/3/4 or btrfs) in order to retain file ownership and permissions. I have a 512 GB partition on a hard drive reserved for the last three weekly backups and never ran out of space.