Target volume not unmounting

[msbc]

Dave,

Absolutely no messages in system log from SuperDuper or anything else at the time the scheduled jobs run. Are there any options to have SD log messages?

[dnanian]

No, no options to do this. Drop me a note to support; I want to get a bit more information about your setup.

[Michael@wengam]

I am also experiencing this since 2.6/2.61 (whenever it was that we had to do schedules reset). I have one single-partition working drive in my MacPro and three internal drives that are each SD! clones (Daily, Weekly and Monthly). Previously SD! would automatically mount and unmount the internal clone drives, but since 2.6.1, although it mounts and backs up OK, the program is unable to also unmount the drives.

Incidentally, I had forgotten to put the clones in Spotlight's 'no search' privacy preference, but still have this behavior after doing so.

[dnanian]

"The drives" meaning it does not unmount any of them, Michael, on quit?

[Michael@wengam]

Only my main drive is mounted when I turn on the machine and log in, thanks to a login script that unmounts each other volume, one at a time, by name.

I said drives (plural) because I have seen the unmount fail for each my three scheduled SD! backups (Daily, Weekly, Monthly) to their respective drives.

Normally, I only have the main drive mounted and when SD! runs it mounts the one drive it needs, then unmounts it.

[dnanian]

Is it consistent in its failure? That is, does it always fail to Daily/Weekly/Monthly but not for others?

[Michael@wengam]

Not sure I understand the question. These three schedules are the only SD! backups I run to real internal hard drives. And all three now leave their target drives mounted after the SD! run.

My drives are actually called OSX_metal, Daily_OSX_metal, Weekly_OSX_metal and Monthly_OSX_metal

They occupy the four hard drive bays of my MacPro