That would seem to indicate that somebody is pressing the backup button, and you either have no tasks assigned to it or one of the backup jobs configured for it has become obsolete (like by removing a share) but the job somehow wasn't removed (as it should be when you delete a share).
Just checked the logfiles. There were two errors two days ago, backup mistake due to usb hdd without access to the files. Restarting the nas solved the problem. Not sure if this relates top the recent backup button problem.
Did you have any backups tied to the backup button? If so, I think that will stop the messages. But whether your button is really being pressed, or worse, the hardware thinks it is when it's not, will be determined by whether or not a backup now takes place based on that "button push".
Yep, I had a two backup jobs tied to the button, but that was at least one year ago. What do you mean with " If so, I think that will stop the messages." ? Recently no backup takes place by using the button. My backup plan is based on a backup schedule only.
Recently no backup takes place by using the button.
Perhaps create a dummy backup job (that backs up a share to a non-existent device), and tie that to the backup button. Then see if the error disappears.
A rsync task to other location or device comes in conflict with (the btrfs root volume) /data and /data/data
FWIW, I recommend not doing this anyway, as it will disrupt SMB access with admin credentials (since both the share and the volume have the same name).
My conjecture was that the ReadyNAS at least thought the button was pushed and attempted to do a backup, finding an error in one or more of the jobs. So fixing the job errors would stop the messages, though not fix the issue with the false button pushes. But if that were the case, and you have jobs assigned to the button that are now good, you should see those jobs being performed other than when scheduled. Do you still have any valid jobs assigned to the button (whether you typically use the button or not)? If so, does the log show any done when you didn't expect it? If not, linking the button to a valid job (existing or new) and checking for this may help.
I'm confused on the fake backup job thing. Did the error messages go away when you fixed the jobs and then return when you intentionally created a bad one? If that's the case, then the question is why the NAS is checking the jobs: because it does think the button is pushed or a bug that directs it when it shouldn't. Or maybe it's not really checking the jobs and it's sending the wrong error message (wouldn't be the first of this sort in an OS update). In that case, we need to find what the real error is.
BTW, please don't "tack on" completely unrelated discussions. Start a new thread. Threads with multiple topics are hard to follow and it may be unclear to which issue a question or solution relates.
