Shirt Pocket Discussions

Shirt Pocket Discussions (https://www.shirt-pocket.com/forums/index.php)

- General (https://www.shirt-pocket.com/forums/forumdisplay.php?f=6)

- - SD! Failure (https://www.shirt-pocket.com/forums/showthread.php?t=6127)

Your backup drive is full. Try an erase-then-copy (see the Troubleshooting section of the User's Guide for a discussion).

Quote:

Originally Posted by dnanian (Post 28926)

Your backup drive is full. Try an erase-then-copy (see the Troubleshooting section of the User's Guide for a discussion).

After the SD! failure, I discovered some rather large duplicate files on my internal drive (not sure what I did to create them...I think they may have appeared as a result of my playing with my Time Machine drive while half asleep at 2 AM! :eek: ). I deleted them in the hopes that would overcome the problem. But it didn't, at which point I posted the question.

1. Why didn't deletion of those duplicate files (bringing the internal drive back "down to size") remedy the problem? Wouldn't SD! see, during its Smart Update operation, that there were fewer files on the internal drive, and make the necessary changes to the SD! drive?

2. Why is it necessary to do a full Erase, then Copy? Why couldn't I simply delete those extraneous files from my SD! drive (the ones that were initially copied to my SD! drive, but which I subsequently deleted from my internal drive) and then run the Smart Update?

Did you reference the Troubleshooting section of the User's Guide? It answers your first question.

You can delete the files if you'd like and know what they are...

Quote:

Originally Posted by dnanian (Post 28931)

Did you reference the Troubleshooting section of the User's Guide? It answers your first question.

Yes, I did read through it...guess I'll need to read it again.

Quote:

You can delete the files if you'd like and know what they are...

I'll give it a try.

[QUOTE=dnanian;28931]Did you reference the Troubleshooting section of the User's Guide? It answers your first question.[/QUOTE

Well, maybe I'm blind, but I didn't see the answer.

Quote:

You can delete the files if you'd like and know what they are...

Since my SD! volume is on a partitioned drive, and I now am operating from a much larger internal drive, I decided to modify the external drive to one with a completely erased, single-partition volume via Disk Utility. I'm now going to use this much larger single-partition drive for my SD! backups.

Is there any reason I need to begin with an initial "Erase, then Copy" backup? I just initiated the backup as a Smart Update, and it seems to be quite happy doing it. (In fact, I don't know when I'd ever want to select an "Erase, then copy"—even on a previously used drive that still contained (now unwanted) data—if Smart Update accomplishes the same result.)

The answer is that if it hits files to copy before it hits files to delete, as it says in the guide, it won't be able to copy. Erase, then copy would alleviate that situation, since it would 'delete' (everything) first.

Quote:

Originally Posted by dnanian (Post 28934)

Hmmm... I'm not blind....just dumb.:o

Quote:

Originally Posted by dnanian (Post 28926)

Your backup drive is full. Try an erase-then-copy (see the Troubleshooting section of the User's Guide for a discussion).

BTW, I meant to ask:

Is the error message "result=256 errno=22 (Unknown error: 0)" SuperDuper!'s way of saying that the backup drive is full? If so, how would an ordinary mortal know? (I didn't see it in the Guide—though it could be there, staring me in the face! :() If not, what in the log indicates that the drive is full?

It's a crappy error message, no question. The readable part of it, for some reason, gets truncated on occasion, something that's logged as a bug.

The thing that indicates that it's full, though, is right at the top: look at the line describing the destination.

Quote:

Originally Posted by dnanian (Post 28940)

It's a crappy error message, no question. The readable part of it, for some reason, gets truncated on occasion, something that's logged as a bug.

Well, at least this time I wasn't being dumb. ;)

Quote:

The thing that indicates that it's full, though, is right at the top: look at the line describing the destination.

...but apparently, I was quite blind! :o

I don't know if this is related, but I've been receiving an "Unable to detect new versions" dialog box when I run/attempt to run SD! backups. When I then click on the Manual Check button, I get another dialog box stating that the version check failed due to a "Could not connect to the server" error, and suggesting that I contact tech support.

Like I said, I'm not sure it's at all related to the full disk problem; it may be related to the fact that I've moved everything over to a new machine, and am now trying to run SD! on that new machine. In any event, I never received such messages before, so I don't quite know what to make of it.

No, I don't think that's related. Try deleting the 'com.blacey...' folder in Library/Caches off your Home.

Quote:

Originally Posted by dnanian (Post 28943)

... . Try deleting the 'com.blacey...' folder in Library/Caches off your Home.

Didn't help. :(

Are you using any kind of outbound firewall, like Little Snitch?