Problem with SMB Shares and Volume Menus
I've been running into an oddball issue with the volume selection menus in 2.5. When I have an SMB share mounted by root (and unreadable by users), the source and target menus are both grayed out. When the "Options" button is clicked, both the "General" and "Advanced" tabs and screens behave as expected, but the "Okay" button doesn't seem to do anything. Deleting the settings or preferences doesn't fix the problem, but dismounting the SMB share does.
I suspect that the same thing might happen if any volume that SD! doesn't have read/execute privileges on is mounted. Unfortunately, I haven't had an opportunity to verify that scenario. System info: PM G5 dual 2GHz w/ 4GB 10.5.5 Two internal drives (desired SD! source and target volumes) External FW drive (Time Machine volume) Drobo/DroboShare (SMB share) |
I just mounted a read-only iDisk volume and SD! seems fine, jtk. Try removing the "saved settings" folder in your Library/Application Support/SuperDuper! folder and repeat the test.
|
Quote:
Also, I'm not sure whether this problem will occur with locally connected volumes, or only with network shares. I can reliably duplicate this with SMB shares, but haven't tested it with AFS or NFS volumes. Might be interesting to try, if a way can be found to keep them from getting unmounted when the root user logs out. Just guessing here, but it looks to me like this has something to do with the way SD! or Cocoa handles the list of available volumes. |
Do you get any errors in the console/system logs?
|
Indeed.
From the console (identical info is system.log): Code:
11/11/2008 12:26:21 SuperDuper![18365] .scriptSuite warning for attribute 'boundsAsQDRect' of class 'NSWindow' in suite 'NSCoreSuite': 'NSData<QDRect>' is not a valid type name. |
Yes, indeed: the system call we're using to retrieve the list of volumes is throwing an exception. OK, thanks.
|
ping...?
Any solution to this, current or planned?
|
We've got it logged. If the API is tossing an exception, it's not something we can fix, though... but we'll look at it when we get time (it's not a high priority item, since you're the only person who seems to be reporting it -- sorry).
|
I have the same problem here. Came in this morning; scheduled SD backup had failed with "can't find target volume" error. Restarted SD and got an error about volume "(null)". Per advice here, removed "Saved Settings" folder; SD launched but vol selection controls were grayed out. Removed other stuff in App Support/SuperDuper and same result. Tried clicking "Options"; got options dialog, but OK button does nothing, and label on first checkbox says
"Repair permissions on SDSourceVolume.name" Console messages as follows: Quote:
|
I ejected the JungleDisk volumes and now SD seems to be OK. jtk, are you using JungleDisk? Maybe there's some compatibility issue there, or their driver isn't doing something properly... I have a friend who works there, so I'd be glad to help make a technical contact if it'd help.
|
Quote:
|
Quote:
|
I'll note also that I've remounted the JD drives, and SuperDuper does start successfully now, so the problem is transient and may not be reproducible here.
|
I believe there's an issue with Jungle Disk volumes whose connection fails: the mount points become invalid in a weird way.
|
All times are GMT -4. The time now is 02:26 AM. |
Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2024, vBulletin Solutions, Inc.