-
Time Machine error 19 "Operation not supported by device"
Interestingly I got rc5 to work and now my timemachine is backing up again.
-
jimsefton started following 3 Drives reported "wrong" after upgrade from rc4 to rc5
-
3 Drives reported "wrong" after upgrade from rc4 to rc5
Upgraded to rc5 from rc4, rebooted and get 3 drives reported wrong. I can roll back to rc4 ok and everything works as expected but each time I upgrade to RC5 it does the same thing. Machine is a HP DL380 Gen 8, if that helps. diagnostics-20220428-1450.zip
-
Time Machine error 19 "Operation not supported by device"
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.
-
jimsefton started following Unraid OpenVPN and Giganews , Time Machine error 19 "Operation not supported by device" , Unable to use Time Machine share for Mac OS 12 Monterey and 6 others
-
Time Machine error 19 "Operation not supported by device"
Sorry I don't know the answer but I have exactly the same error!
-
[SOLVED] unRAID with HP p420i RAID card in HP ProLiant DL380p G8...
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?
-
How much RAM do you have installed in your unRAID server?
192GB
-
[CONTAINER] CrashPlan & CrashPlan-Desktop
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.
-
[CONTAINER] CrashPlan & CrashPlan-Desktop
Yeah, and crashplan seemed pretty lightweight compared to most other options
-
[CONTAINER] CrashPlan & CrashPlan-Desktop
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.
-
[CONTAINER] CrashPlan & CrashPlan-Desktop
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."
-
[CONTAINER] CrashPlan & CrashPlan-Desktop
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.
-
[CONTAINER] CrashPlan & CrashPlan-Desktop
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.
-
[Support] binhex - SABnzbd
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
-
[Support] binhex - SABnzbd
for some reason I thought it called the autoprocesstv.py script directly, although I guess the reason for the error is likely the same
-
[Support] binhex - SABnzbd
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