Btrfs system crash, howto recover?

[Kobold]

@birdibird

And yes, I prefer to not use the rsync but the btrfs snapshots of timesync exactly for the reason of the power of btrfs.
But now that I need it, it doesn’t work

@Molski

Kobold will recommend Timeshift with rsync pseudo snapshots to anyone, regardless of your setup, needs, or filesystem type(s).

Well i don’t wrote Rsync recommendation this time… because i was thinking that he maybe wants exactly this.

On the otherside, he has no way to restore his system with a simple rollback now.

The valid question is now… was it worth to use Timeshift this way?

I think its a clear no, but on the otherside he saved time to create snapshots… Snapshots where he can’t rely on it now.

@birdibird

If I boot into the liveusb I can see them in the Timeshift gui, but clicking restore there doesn’t give me a bootable solution.

You are not the first one who run into this exact problem, where your (BTRFS/Rootstored) Snapshots are gone now.

Its exactly as @Nachlese wrote here:
BTRFS is a advanced filesystem, use it only if you know what you doing.

@Molski That doesn’t mean that im against BTRFS or in a war against this Filesystem, the user just should get his homework done before he start using it and if the user isn’t willing to do this, BTRFS shouldn’t be recommend then to this user.

And i saw you get caught on surprise recently in another BTRFS Topic, where you didn’t know that repairing a file with FSCK can lead to even more dangerous situation, when the whole BTRFS Partition is in the read mode. (if i understand that recently topic, correctly).

@Zesko

There are some reasons:

• File corruption is not the same as filesystem corruption:
  • If only specific files are corrupted but the filesystem itself (including metadata) works properly (i.e., It can be mounted and read), this is usually not an error at the Btrfs level.
  • File corruption can happen due to checksum mismatches, often caused by bit failures in hardware, it doesn’t mean the whole filesystem needs to be repaired. This is why it’s recommended to use btrfs scrub instead of btrfs check --repair
• btrfs check --repair is designed to repair critical filesystem corruption, especially when the filesystem cannot be mounted or is severely damaged. However, sometimes it succeeds (luckily), while other times it can lead to data loss after running the repair option.
• Running btrfs check --repair on the working filesystem can be risky, as it might inadvertently cause more harm to the metadata or data structure.