jimsefton

Interestingly I got rc5 to work and now my timemachine is backing up again.

Just checked and the only older ones I have were from 6.9.2

I don't think so, no. Will double check but I suspect if I do they will be from a much older release

Nice one, that worked.

Done, thanks

ok, diagnostics attached diagnostics-20220428-1450.zip

I tried upgrading from rc4 to rc5 but it detects one of my array drives, my cache drive and a spare drive as "wrong". When I select them from the list the array drive says it will be re-built. Not sure why this is so I rolled back to rc4 and it all works ok now.

Yeah, will have a look when I get chance. Just tried upgrading to latest RC5 and had to roll back as it detected 3 of my drives as “wrong”. Not having much luck at the moment with Unraid.

Sorry I don't know the answer but I have exactly the same error!

Sorry to dig up this old topic, but I have an UNRAID setup on a DL380e using a bunch of RAID0 (for each drive) on the raid controller. It seems to limit the ability to see the health status of the drives. Should I switch the RAID controller to HBA mode? I assume by doing that I will lose all the data? Do I need to find storage for all the data while I make the switch or is there some magic way around doing that?

192GB

Seems like it was a pretty valuable differentiating feature for crashplan. Wonder if it is an opportunity for one of the competition to introduce it. Not expecting it to necessarily be free, but I don't necessarily need/want all my data innthe cloud.

Yeah, and crashplan seemed pretty lightweight compared to most other options

If only someone could replicate the computer to computer crashplan functionality and sell a family licence for it, that would be great. I have a low powered unraid box that crashplan worked fine on, but all these other solutions totally cripple it.

When I tried it that didn't happen, archive was empty... will try that again as it does seem the most effective at syncing so far. EDIT: Tried again, added a file to the shared folder, it appeared on the destination... deleted it from the source and it deleted from the destination. I then clicked view archive (archiving was ticked) on the source machine and it opened up an empty archive. EDIT2: Found out why... so back to square one, this solution is ruled out: " Sync's Archive affects devices other than the one where files are deleted/changed. For example, if you have a folder in Sync across 3 devices; A, B, and C, and you delete a file from the folder on device A, the corresponding file on B and C will be moved to .Sync/Archive on B and C respectively. The .Sync/Archive on A will remain empty. Similarly, if you delete a file from the folder on device B, on devices A and C it will be moved to .Sync/Archive on A and C."

Unless I am missing something if a file is deleted from the source it is deleted from the backup... this makes it a non starter for me.

It seems there are a few options for backing up to the cloud if you are willing to part with some cash. What we are missing is a good peer-to-peer system like we had with "backup to a friend". I used that on Macs and Windows and it was very lightweight and "just worked". In contrast I have experimented today with Syncthing and it is hideously resource intensive and doesn't seem to work well at all. I just can't seem to find a decent lightweight solution comparable to the CrashPlan option. Will keep following this thread in case anyone finds one.

Just to let you know my problem is fixed. I changed the first line to say python2 in the autoprocesstv.py file, but I also needed to do it in the sab2sickbeard file as well. Working well now. Thanks

for some reason I thought it called the autoprocesstv.py script directly, although I guess the reason for the error is likely the same

It works... not like that. You'd have to attach yourself to the actual docker instance. do a "docker ps" and find your container ID. Then "docker exec -i -t 665b4a1e17b6 bash" (replace with the proper ID) and you'll be inside your container. Hi, thanks for that, sorry was half asleep when I posted yesterday. Still no joy getting it working though

Not sure how the docker system works, but I get this from logging into the unraid box: root@Pootle:/mnt/cache/appdata/sabnzbd/config/autoProcessTV# /usr/bin/env python /usr/bin/env: python: No such file or directory root@Pootle:/mnt/cache/appdata/sabnzbd/config/autoProcessTV# /usr/bin/env python2 /usr/bin/env: python2: No such file or directory

No matter if I set it to python or python2 it still gives a similar error OK I will take a look tonight ok i had a look and can confirm there is an env variable defined for python2, output from console for sabnzbd container:- [root@439f7a83371f /]# /usr/bin/env python /usr/bin/env: ‘python’: No such file or directory [root@439f7a83371f /]# /usr/bin/env python2 Python 2.7.11 (default, Dec 6 2015, 15:43:46) [GCC 5.2.0] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> exit() so you can see that "/usr/bin/env python" doesnt exist, but "/usr/bin/env python2" does, i havent changed anything in this regards but it is possible the python package has changed and thus doesnt create the env variable "python" any more, im assuming you had this acript working fine yes?. The odd thing is you said you tried to use /usr/bin/env python2 and that didnt work right?, did you change the first line in the script as well as the line its trying to execute?, as you can probably tell i dont make use of this script at all :-). Hi, Looking at the logs the script was working fine on the 19th Feb but broken on the 22nd Feb (if that helps). I have been trying to keep on top of updates so hopefully that may tie in with something! All I altered was the first line of the autoprocesstv.py script, not sure what else to try. The original script I think didn;t have any first line at all, I just copied it over from sickbeard which referenced python2. I then altered it to python and it still didn't work.

No matter if I set it to python or python2 it still gives a similar error

Thanks for the reply, but I am still getting this /usr/bin/env: python2: No such file or directory