Increased reports since 6.15.3 of corruption within the log tree

Seems like a btrfs bug. Bunch of links in that thread with similar reports and screenshots. They also include the suggested fix.

First

lsblk to get the list of block devices (you can use size to figure out your file system)

Then:
mount -o remount,rw /dev/${name found in previous step} /

Then check for bad entries in your /etc/fstab and fix them

Then check for failed services:
systemctl —failed

Then you should be able to:

systemctl set-default graphical.target to boot

This is the painful part I don't know why my fstab is nuked. It is completely empty. I am writing it rn and it is painful. I have a question to ask tho. After I finish writing it what do I do? Do I reboot?

Edit: Okay after I finish the fstab I do mount -a it did not work. ;). I am not sure if what I did is good though. I just copy fstab of a new installation of arch on my laptop and change the UUID

You don’t need to use the uuid for /etc/fstab (which should make it much easier)

You don’t need to reboot just set the run level via:
systemctl set-default graphical.target

But you will want to clear out the failed systemd services first to ensure that you can boot.

systemctl --failed will list what failed

After you make your /etc/fstab

systemctl daemon-reload will regenerate the units files in /run/systemd/generator but doesn't start new automounts or stop ones removed from fstab.

systemctl start newmount.automount will start the mount. The .automount extension is required, as systemd assumes .service if not extension is specified.

systemctl stop oldmount.automount will remove a mount not longer in fstab

systemctl reset-failed will stop a previously failed removed mount from appearing in status messages

If you can afford it, Honeywell PTM7950. It's very stable and avoids pump out, which is great in a laptop where you don't want to repaste very often. It's a phase change material, not a standard paste. To apply, put it the fridge to cool. Afterwards, cut to size and put it on. Once it warms up, it liquefies to fill all the small gaps.

Otherwise, most other pastes are fine. I'm partial to Arctic MX-4 but they're all pretty the similar. On direct die like a mobile chip I would recommend spreading it out to ensure even coverage as gaps can cause hotspots which may eventually damage the chip.

I would recommend anything Thermal Grizzly:
thermal-grizzly.com/

Simply because the owner has two 1 hour long videos explaining how its made and tested and it actually seems to be one of the best.

Willkommen im Thermal Grizzly Online Shop

Der Thermal Grizzly Online Shop ist die erste Anlaufstelle für unsere Wärmeleitpasten, Flüssigmetalle, Wasserkühler, Wärmeleitpads und vieles mehr!

^{Thermal Grizzly}

Just get a thick thermal paste. By and large any thermal paste is an improvement over stock. Thicker pastes like arctic mx6 won't pump out. I like ic diamond 7 karat but that's out of stock. (all I have left is a random tube of it that I found in storage)

(I do mean any thernal paste is better than stock. I used arctic ceramique 3 once on my i5-7200u laptop and it was still 3C lower than og psste temps)

When I repasted my i5-1135G7 laptop, I dropped 10C after replacing the paste.

All you really need is a tiny blob, one covering the igpu die, other on the cpu.

Mobile CPUs (any any direct-die cooling for that matter) are more prone to pump-out, where the chip and heatsink expand at different rates with temperature changes, and the varying gap between the two creates a pumping action. It's best to use a thicker paste to avoid it, or even better, a thermal pad. Not that it's the best in the long run, but I have gotten away with the thinner MX-4 in my laptop for about a year.

If you have maybe $30 to spare, consider buying some PTM 7950 since it's second only to liquid metal (very hard to get right), and should be good for many years. Be sure to get it from reputable sellers though since there are fakes for PTM 7950.

Okay, so let me break down what I THINK is happening here, which is that you might have a misunderstanding of what what atomic/immutable means.

First, these are made to separate OSspace from UserSpace. Whatever you keep in UserSpace is your responsibility.

Second, the actual running OS is built on layers like containers. The hash of what your OSspace is can be readily gotten to compile the exact same version of it from the repos that hold the presompiled versions of these things. Just like containers.

Third, you don't need to backup any of the OS because of the above.

Lastly, the general idea is that since you don't need to backup anything about the OS, and you should be able to checkout a hash of some sort that can download and be eventually bit-consistant with the OS layer, all you have to worry about is the UserSpace content.

How you manage the UserSpace content is up to you. Back your stuff up, start a bare machine and check the OS out to a specific revision where your previous machine was at, then drop your UserSpace stuff in, and it will "just work".

Timeshift is completely unnecessary. Fedora Atomic's rollbacking is more powerful and avoids certain issues.

You should only be backing up personal files, not OS files. The OS is replaceable, your personal files are not.

I’ve never tried an immutable OS, but I’d love if the ability to do system backups and redeploy to another computer was just part of any OS.

Especially when Linux encourages you to distro hopp.

Clonezilla is great but it already happened to me that one backup wasn’t deployable on another (really old) computer

I think the partitioning itself is fine, but I wouldn't have 3 operating systems on a 256 GB NVMe, because I'd be running out of space a lot.

if you won't ever use Windows, you can nuke it. Then I'd consider making one of the Linux ones a VM - if you're trying out that distro. That will cut down 12 partitions to 5.

Lastly, you can look into btrfs to make better use of space between (the current) p11 and p12: you can make them subvolumes that won't eat up each other's storage when not in use.

If it works, it works. Unless you're working in Espionage, anything is honestly fine as long as your main storage is encrypted. The boot loader exploits still can't unencrypt things, just allow access to the data, which...still can't be decrypted as as we know.

It's fine.