system corrupted without apparent reason [Solved]

[Adrian]

Timeshift only save difference between files on the same disk, if the disk dies you don't have anything left to recover -- thus "not a backup" it's however good if you want to recover previous versions of file in case of non-disk related problems.

[CharlesV]

Timeshift only save difference between files on the same disk, if the disk dies you don't have anything left to recover -- thus "not a backup" it's however good if you want to recover previous versions of file in case of non-disk related problems.

Precisely. In my case, its really all abut the system and the config files

[harrykar]

Yes, I use Timeshift for a regular timed backup and then I have BackInTime for my big backup, and then SpiderOak backing up off site every 15 min. I run my /home a little different than most, carrying only confg's and a small amount of data there. 99% of my data ( docs, pictures, everything else) is on a completely different drive, and I have links to get there . ( ie my ~/Documents ~/Pictures etc are all symlinks )

Tnx for the hints. Tell me your opinion about BackInTime(was discontinued or remember bad?) and SpiderOak
You have used rsync ? If yes what's your opinion?

Yes, people say not to use Timeshift to 'backup' your data. And I believe the main reason is that a restore will drop you BACK to where you were when it last run. (ie you LOSE all data since that timeshift!)

As I thought about that on TimeShift(TS). But that's not the behaviour of other backup tools too?

... So.. easy to do as long as you remember, if your going to restore using TImeShift you either a) make another TImeShift right before you restore, or you copy out your entire ~/ ... and replace anything 'new' since that TimeShift that you restored. ( obviously ... better to NOT do this - but I like the timed save, and I have SpiderOak too.)

I'm not sure what you mean can you translate it in steps(1. 2. 3. etc)?
I Notice that TS do automatically a snapshot point before do a snaphot IIRC.
Note: On btrfs do (or restore from) a (till now did only system's) snapshot are literally a snap, really impressive IMHO.I Have to be more accustomed with that awesome tool

For your xscreensaver, there is a ~/.xscreensaver that holds all config data, I would remove that and see if it resolves your black saver. (also - mine does that on occasion, but is always good the next round - but then I rarely shut my machines down, locking them each time i walk away. )

Good strategy I will bare it in mind just in case because without do anything xscreensaver showed his colorful screens, maybe back screen is one of his screens?
I will observe it

[harrykar]

Timeshift only save difference between files on the same disk, if the disk dies you don't have anything left to recover -- thus "not a backup" it's however good if you want to recover previous versions of file in case of non-disk related problems.

@Adrian Thanks got it Timeshift behave like 'a hard link than can't go a out of a partition'

[CharlesV]

Tnx for the hints. Tell me your opinion about BackInTime(was discontinued or remember bad?) and SpiderOak
You have used rsync ? If yes what's your opinion?

BackInTime is currently under production. ( https://github.com/bit-team/backintime )

While I really like SpiderOak... it has started to become bogged down and problematic on several clients machines (windows - but the service ) .. I am currently evaluating it on my machines, but starting to fall out of favor with it - which is to bad as I *really* like it.

Looking at borgBase and Vorta.

I have used rsync, and it works well.. but I am more GUI driven and rsync was failing to write to my NAS (synology ).

As I thought about that on TimeShift(TS). But that's not the behaviour of other backup tools too?

Yes, it is really. However, I typically restore to some other location when I use the other backup utils - but yes you are correct.

... So.. easy to do as long as you remember, if your going to restore using TImeShift you either a) make another TImeShift right before you restore, or you copy out your entire ~/ ... and replace anything 'new' since that TimeShift that you restored. ( obviously ... better to NOT do this - but I like the timed save, and I have SpiderOak too.)

I'm not sure what you mean can you translate it in steps(1. 2. 3. etc)?

The safest way I have found to restore with timeshift is:
1) Make a new timeshift snapshot (saving current ) ( Call this one "snapshot of today" )
2) Restore previous timeshift ( call this one 'yesterdays')
3) after your all back up and good, then using fsearch and thunar pluck out of "snapshot of today" the files that are later than "yesterdays".

I Notice that TS do automatically a snapshot point before do a snaphot IIRC.
Note: On btrfs do (or restore from) a (till now did only system's) snapshot are literally a snap, really impressive IMHO.I Have to be more accustomed with that awesome tool

If your talking about MX snapshot, yes I agree. it is an awesome tool for keeping things rolling along. (I make one once a month minimum, or sooner if I feel the need ;-p )