Destination HD Does Not Eject - SD! v3.1.7 v111

[Kurt Todoroff]

I have configured SD! to perform a backup to two separate external hard drives, every night. One backup starts at 11:30 PM. One backup starts at 11:40 PM. Both backup scripts conclude with eject after copy.

The v3.1.7 update now ejects the second external HD (11:40 PM). However, the first external HD (11:30 PM) does not eject. This occurs on two separate systems.

I am using the copy script that I have used prior the first occurrence of the recent SD! failure to eject problem occurring.

[dnanian]

And if you reverse the times for the two drives, does the first one always not eject?

[Kurt Todoroff]

I reversed the times. Then, I subtracted three hours from the two start times (starting at 2040 and 2050, instead of 2340 and 2350), so that I could collect immediate data for you.

Both copy scripts properly ejected the hard drives. I reversed the times, again, such that they were consistent with their original starting time configurations (still adjusted by three hours earlier, plus an additional 20 minutes to account for the time elapsed during the two copy operations.). Again, both copy scripts properly ejected the hard drives. I have reverted the script start times to their original configurations (2340 and 2350). Tomorrow morning, I will examine the results of the two backups.

By the way, each time that I attempted to save the second edited script (with a new start time), SD! would quit unexpectedly. This occurred multiple times, and, was/is reproducible. Saving the first edited script did not cause an unexpected quit. Whether I edited script A or script B, first, did not alter the outcome. Saving the second edited script caused SD! to quit unexpectedly. (e.g. Edit script A. Save edited script A. SD! continues to operate. Then, edit script B. Save script B. SD! quit unexpectedly.)

[dnanian]

Can you send the crash logs via the support email address, Kurt? Thanks.

[Kurt Todoroff]

This morning, both systems did not display their respective external hard drives on the desktop. The corresponding SD! log files reveal that SD! performed all of the backup scripts, properly, last night.

Does re-saving an SD! copy script alter SD!'s behavior in this manner? Should we re-save our copy scripts with each new SD! update?

[dnanian]

No, it doesn't and didn't change the behavior. I just wanted you to change the order to see if it was script-specific.