Shirt Pocket Discussions - How do you get your money back?

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

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

- - How do you get your money back? (https://www.shirt-pocket.com/forums/showthread.php?t=2740)

How do you get your money back?

During my first backup, there are hundreds of these messages:

| 05:14:01 PM | Info | WARNING: Caught I/O exception(5): Input/output error
| 05:14:01 PM | Info | WARNING: Source: /Users/adamshopis/Documents/Final Cut Pro Documents/Capture Scratch/Untitled Project 1/Untitled3, lstat(): 0
| 05:14:01 PM | Info | WARNING: Target: /Volumes/Macintish HD Clone/Users/adamshopis/Documents/Final Cut Pro Documents/Capture Scratch/Untitled Project 1/Untitled3, lstat(): 0

Finally, after 6BG have been written, there is an ERROR and not a warning:

| 05:14:01 PM | Info | Attempting to copy file using copyfile().
| 05:14:01 PM | Info | Attempting to copy file using ditto.
| 05:14:02 PM | Error | ditto: /Volumes/Macintish HD Clone/Users/adamshopis/Documents/Final Cut Pro Documents/Capture Scratch/Untitled Project 1/Untitled3: Input/output error

Contrary to what some suggest, THE FILES ARE PERFECTLY FINE! Including the one that caused the ERROR. Or, the files are good enough to be read by applications which really is all one needs.

SD should simply copy all bits on USER files and not halt the copying even on an error. (Just skip the file.) At worse, after a Restore, one would have the same bits that one had before the Backup. If the bits are the same, then if one finds one can't open a file after a Restore, one couldn't do it before the Backup.

A list of the files with "errors" with their path could then be written to the Source and Target. Now you could see and find the problems for yourself.

SD seemed like it was a good program, but there are others reporting the same problem.

How do you get your money back? :(

Steve:

This is not due to any kind of problem with SuperDuper!

The problem -- based on the log you included with your email, which repeats some of this information -- is that you're backing up to a network drive that's either formatted as FAT32 or the protocol you're using is an outdated version of AFP. I go over this in some detail in the User's Guide...

Quote:

Originally Posted by dnanian (Post 13523)

The problem is that you're backing up to a network drive that's either formatted as FAT32 or the protocol you're using is an outdated version of AFP. I go over this in some detail in the User's Guide...

1) My drive is EXT3 not FAT32.

2) I did read your manual and then searched it -- there is no reference to AFP. So I've got no idea what you are talking about. Or, how to fix it.

3) These aren't my messages, they are in a post of another person's who is having the same problem. There was no SAVE LOG button on the log dialog box so I couldn't send you mine. But, looking at the ones I posted:

| 05:14:01 PM | Info | WARNING: Caught I/O exception(5): Input/output error
| 05:14:01 PM | Info | WARNING: Source: /Users/adamshopis/Documents/Final Cut Pro Documents/Capture Scratch/Untitled Project 1/Untitled3, lstat(): 0

Despite the warnings, these files all get copied. So if there are disk errors as the SD manual claims, how can it be the files get copied?

4) Looking at the ERROR:

| 05:14:01 PM | Info | Attempting to copy file using copyfile().
| 05:14:01 PM | Info | Attempting to copy file using ditto.
| 05:14:02 PM | Error | ditto: /Volumes/Macintish HD Clone/Users/adamshopis/Documents/Final Cut Pro Documents/Capture Scratch/Untitled Project 1/Untitled3: Input/output error

Since the error is "Input/output error" how do you the problem was on the Write and not the Read?

5) If the ERROR is on the NAS -- am I correct that SD will work with a FireWire drive. But what about all the WARNINGS?

THANK YOU
Steve

They're not getting copied: one of the retries is not generating an error as it should (ditto).

AFP is the Appletalk Filing Protocol. Many NAS drives use an old version of AFP that doesn't support files larger than 2GB. If you mount with SMB instead (use Cmd+k in Finder, then enter smb://the-drive), that should help, given that the drive is ext3.

You'll want to delete and recreate the image...

Quote:

Originally Posted by dnanian (Post 13534)

If you mount with SMB instead (use Cmd+k in Finder, then enter smb://the-drive), that should help, given that the drive is ext3.

THANK YOU!

1) My Mount was -- "cifs://WORKGROUP;STEVE@250/NETHDD"

2) So I made a new mount --

"smb://WORKGROUP;STEVE@250/NETHDD"

The disk mounted fine.

3) I'm assuming smb can move >4GB files. Correct?

4) When I try to select a folder I previously created on the NAS, SD failed. Am I correct that the Image File must be written to the root of the NAS and not into a Folder?

5) If you ever update the manual it might be nice to make it clear what the ERASE TARGET does when writing to a NAS. Since one picks the NAS one worries that the NAS would be erased. Also, a comment that if no Image file exists, the erase does nothing.

6) You said to erase the Image File. Does that mean SD would not have done so?

Steve
:o

cifs should be the same as smb, so... How large was the image file on the share?

Quote:

Originally Posted by dnanian (Post 13536)

cifs should be the same as smb, so... How large was the image file on the share?

It was 6GB.

Is there a chance SD automatically wrote the log to disk? Where would it be?

Automatically wrote what log? We always log copies -- Window > Show Log.

No, "/./" just means "current folder.

If you could, immediately after you get an error, generate a system profiler report and send it into support. I'd like to take a look at the logs during the error.