kalidus

I mean the previous version wich throwed the "this is not a tar" error.

I was going to post about the same problem that @Yanos! has, but now is just a confirmation that @KluthR `s fix makes it restore again. Thank you! Just out of curiosity...are backups made with the "faulty" version usable?

Correct me if i am wrong but, isn't it a bad idea to copy between user and disk folders? Source:

Maybe this can help you::

As i said, i researched all of that and there is absolutely no disk activity, open files, dockers, vms, scheduled tasks interfering.... I also said that the plugin caused an unclean shutdown, i didn't force it. Theres some posts of other users with the same problem in this and other forums so, forgive me but categorically saying it's not the plugin just by seeing a log seems precipitate for me. However, i can't certify if it is or not. Thanks anyways.

Here's my log. I can't manage to see what's wrong. XXXX parts are just for ID's, ip's and such. Thank you! syslog

How can i do that? There are no more log options to check

This is the only thing i get in the flash log: 19:17:32 XXXX s3_sleep: Disk activity on going: sdb 19:17:32 XXXX s3_sleep: Disk activity detected. Reset timers.

Thanks for your answer, but unfortunately is not my case. In fact, the only log i get is repetead again and again...: Jun 7 18:02:20 XXX s3_sleep: Disk activity on going: sdd Jun 7 18:02:20 XXX s3_sleep: Disk activity detected. Reset timers. i have no pre or post scripts, no disk activity at all, no files being opened, no IO activity, no dockers, no vms...

Hi! like another users, im having unclean shutdowns and parity check with the s3 plugin. Has this issue been adressed yet? no dockers/vm at the moment triggers are array unactivity with counters only, because status trigger detects activity every minute and never sleeps (XXXXXX s3_sleep: Disk activity on going:). Even tried the spin down button, no luck. domain,isos, appdata and system set to cache prefer. Thank you!