PDA

View Full Version : Urgent!...Manual Unmount Help Needed...




JoelBC
Dec 6, 2012, 05:59 AM
I have a real and urgent need to unmount a hidden share from my NAS drive...

I am using a WD ShareSpace NAS for TimeMachine...following the instructions contained in another thread [see http://forums.macrumors.com/showthread.php?t=1463343 ]I mounted the NAS' hidden share using the following terminal command

sudo tmutil setdestination afp://wd_backup:backup@192.168.5.150/WD_Backup

where wd_backup = share's user name, backup = share's password, 192.168.5.150 = NAS' address and WD_Backup = share's name

I now need to unmount the drive but can not figure how to do so please help me by providing me with the necessary terminal command to do so [i.e. to be clear, I need / want to unmount the drive so that it DOES NOT appear as a backup device within TimeMachine).

Thanks for all your help,


Joel


PS. Once I have your attention, does anyone know how to access this share on the NAS drive to recover the space with the issue / problem being that it is hidden?



justperry
Dec 6, 2012, 06:28 AM
I have a real and urgent need to unmount a hidden share from my NAS drive...

I am using a WD ShareSpace NAS for TimeMachine...following the instructions contained in another thread [see http://forums.macrumors.com/showthread.php?t=1463343 ]I mounted the NAS' hidden share using the following terminal command

sudo tmutil setdestination afp://wd_backup:backup@192.168.5.150/WD_Backup

where wd_backup = share's user name, backup = share's password, 192.168.5.150 = NAS' address and WD_Backup = share's name

I now need to unmount the drive but can not figure how to do so please help me by providing me with the necessary terminal command to do so.

Thanks for all your help,


Joel


PS. Once I have your attention, does anyone know how to access this share on the NAS drive to recover the space with the issue / problem being that it is hidden?

Since you didn't get a response yet I give it a try, I know OS X fairly well but I don't understand this here.

If a share is mounted it should be in the finder/ on desktop and you can drag it to the trash.
I mount disks/folders over the net with Command-K and they show up in those locations but it depends how your preferences are set.

I could be completely of here so excuse me if I am totally wrong.
Tried to search the net for you but couldn't find the unmount command either.

JoelBC
Dec 6, 2012, 06:36 AM
Since you didn't get a response yet I give it a try, I know OS X fairly well but I don't understand this here.

If a share is mounted it should be in the finder/ on desktop and you can drag it to the trash.
I mount disks/folders over the net with Command-K and they show up in those locations but it depends how your preferences are set.

I could be completely of here so excuse me if I am totally wrong.
Tried to search the net for you but couldn't find the unmount command either.

Appreciate the assistance but unfortunately that did not work...i think -- just guessing here -- that the problem is related to the fact that the terminal command that I issued acts as a "hard / permanent" which is making it difficult to unmount the drive.

Hopefully someone else will have the answer.

Thanks,


Joel

justperry
Dec 6, 2012, 06:46 AM
Appreciate the assistance but unfortunately that did not work...i think -- just guessing here -- that the problem is related to the fact that the terminal command that I issued acts as a "hard / permanent" which is making it difficult to unmount the drive.

Hopefully someone else will have the answer.

Thanks,


Joel

Sorry that did not work, but found this link on Apples site, the Man pages for tmutil. (http://developer.apple.com/library/mac/#documentation/Darwin/Reference/Manpages/man8/tmutil.8.html)

I saw one 'verb' there, disable, might help.

Edit: You might try to look for timemachine preference file and look if there is an entry in it and if so delete the link.

com.apple.TimeMachine.plist

I found two .plist files, but I don't use Timemachine nor shares.

Found the files by using a free app called EasyFind.

JoelBC
Dec 6, 2012, 07:32 AM
Sorry that did not work, but found this link on Apples site, the Man pages for tmutil. (http://developer.apple.com/library/mac/#documentation/Darwin/Reference/Manpages/man8/tmutil.8.html)

I saw one 'verb' there, disable, might help.

Edit: You might try to look for timemachine preference file and look if there is an entry in it and if so delete the link.

com.apple.TimeMachine.plist

I found two .plist files, but I don't use Timemachine nor shares.

Found the files by using a free app called EasyFind.

Again, appreciate the help but no luck in that:

1. The "disable" command simply disables automatic backups...I need a commend that is the opposite of set destination [i.e. I need a remove destination / reset destination or other similar command].

2. I looked at the plist files could find nothing there.


Thanks,


Joel

justperry
Dec 6, 2012, 07:40 AM
Again, appreciate the help but no luck in that:

1. The "disable" command simply disables automatic backups...I need a commend that is the opposite of set destination [i.e. I need a remove destination / reset destination or other similar command].

2. I looked at the plist files could find nothing there.


Thanks,


Joel

What if the TimeMachine is disabled and then enable it again, this can be risky though.
It might be that if it is disabled all settings are lost, this also means a new setup and I don't know what TimeMachine does after it is started again after a new Setup.

JoelBC
Dec 6, 2012, 07:41 AM
What if the TimeMachine is disabled and then enable it again, this can be risky though.
It might be that if it is disabled all settings are lost, this also means a new setup and I don't know what TimeMachine does after it is started again after a new Setup.

I do not care about loosing my backups at this point...I just want to unmount the drive...

justperry
Dec 6, 2012, 07:48 AM
I do not care about loosing my backups at this point...I just want to unmount the drive...

Well, then disable TimeMachine.

Hope this works.

JoelBC
Dec 6, 2012, 07:53 AM
Well, then disable TimeMachine.

Hope this works.

That will not help as the share will still be mounted...I need / want the share gone...

justperry
Dec 6, 2012, 08:02 AM
That will not help as the share will still be mounted...I need / want the share gone...

If this is so I think Apple messed up, it is TM related and it should also disable this share.

There is also this in /Library/Preferences/SystemConfiguration

These are normally all network settings, I don't have shares but I do see some interesting files in the like com.apple.smb.server.plist
There might be a .plist there.
There is more, check them out.

Hope that they are in the same place as your OS, I am on an earlier OS but do have TM.

switon
Dec 6, 2012, 08:24 AM
That will not help as the share will still be mounted...I need / want the share gone...

Hi,

Speed-reading through your posts, I wasn't clear if all you really want is to unmount an afp share. If this is all you wish to do, then have you tried the "umount" Terminal command? (Note that it is "umount" and not "unmount".) Here is an example terminal command that unmounts an AFP share:

umount //username@servermachine._afpovertcp._tcp.local

where you can discover the exact name to use through the "df" terminal command:

df -h

which returns the "//username@servermachine._afpovertcp._tcp.local" for whatever name your share is actually afp mounted as.

Obviously, you will need to have the privileges of "username" in order to execute this command, or you can execute it from a root account or using "sudo" from an Administrator account.

Good luck,
Switon

P.S. The "umount" command has a number of options, such as forced unmounting, that you can read about using "man amount".

P.P.S. By the way, you can use "umount" to also unmount the mount point, as in:

umount /Volumes/share_name

rhoydotp
Dec 6, 2012, 08:25 AM
That will not help as the share will still be mounted...I need / want the share gone...

can you type the command "mount" and share the output

thx

JoelBC
Dec 6, 2012, 09:19 AM
Hi,

Speed-reading through your posts, I wasn't clear if all you really want is to unmount an afp share. If this is all you wish to do, then have you tried the "umount" Terminal command? (Note that it is "umount" and not "unmount".) Here is an example terminal command that unmounts an AFP share:

umount //username@servermachine._afpovertcp._tcp.local

where you can discover the exact name to use through the "df" terminal command:

df -h

which returns the "//username@servermachine._afpovertcp._tcp.local" for whatever name your share is actually afp mounted as.

Obviously, you will need to have the privileges of "username" in order to execute this command, or you can execute it from a root account or using "sudo" from an Administrator account.

Good luck,
Switon

P.S. The "umount" command has a number of options, such as forced unmounting, that you can read about using "man amount".

P.P.S. By the way, you can use "umount" to also unmount the mount point, as in:

umount /Volumes/share_name





Appreciate the response...

A few follow ups as I continue to be confused [and, apologies, as I am new to all this Mac stuff]:

1. Correct, I am looking to do nothing more than unmount an AFP mounted drive albeit one that was mounted using the "tmutil setdestination" command to the extent this makes a difference / matters.

2. I entered the command df -h in terminal as you suggested but did not a response a long the lines suggested above...in its place I got a table with the headings filesystem, size, used....,mounted on.

I therefore do not know how to proceed.

I wonder whether this is because of the method I used to mount the drive per 1. above [i.e. using the "tmutil setdestination" command].

I wonder whether this has to do with the fact that I am at present connected to the network via VPN.

3. In the hope that we can overcome 2. above kindly confirm that the username [and the password that is subsequently requested] is that for the mounted share [as opposed to that for the MacBook, the NAS in general, etc.]

I seem to be way over my head and really wanted this sorted...I have invested 100+ hours trying to make the move from Windows to Mac but everything seems to be a challenge...I am almost there in terms of getting my Mac setup so hope that I can get this done and keep my Mac.

Thanks for all the help.


Joel

switon
Dec 6, 2012, 10:41 AM
Appreciate the response...

A few follow ups as I continue to be confused [and, apologies, as I am new to all this Mac stuff]:

1. Correct, I am looking to do nothing more than unmount an AFP mounted drive albeit one that was mounted using the "tmutil setdestination" command to the extent this makes a difference / matters.

2. I entered the command df -h in terminal as you suggested but did not a response a long the lines suggested above...in its place I got a table with the headings filesystem, size, used....,mounted on.

I therefore do not know how to proceed.

I wonder whether this is because of the method I used to mount the drive per 1. above [i.e. using the "tmutil setdestination" command].

I wonder whether this has to do with the fact that I am at present connected to the network via VPN.

3. In the hope that we can overcome 2. above kindly confirm that the username [and the password that is subsequently requested] is that for the mounted share [as opposed to that for the MacBook, the NAS in general, etc.]

I seem to be way over my head and really wanted this sorted...I have invested 100+ hours trying to make the move from Windows to Mac but everything seems to be a challenge...I am almost there in terms of getting my Mac setup so hope that I can get this done and keep my Mac.

Thanks for all the help.


Joel

Hi Joel,

Sorry, I should have explained more.

Yes, using the "df" command returns a table of all of the mounted volumes, including shared volumes. Hopefully, one of these lines is your mounted TM afp volume. You will have to recognize which line it is. For instance, for my TM backups, the "df" line is:

/dev/disk2s2 1.8Ti 416Gi 1.4Ti 23% 108992788 378777580 22% /Volumes/Time Machine Backups

You can then use the "umount" command as described earlier. Sometimes "umount" fails, then try the "diskutil unmount /dev/disk2s2" where /dev/disk2s2 is the name appropriate to your system.

Lastly, you aren't attempting to use your boot volume also as your TM backup partition, are you? If you are, you won't be allowed to unmount it.

Switon

JoelBC
Dec 6, 2012, 12:08 PM
Hi Joel,

Sorry, I should have explained more.

Yes, using the "df" command returns a table of all of the mounted volumes, including shared volumes. Hopefully, one of these lines is your mounted TM afp volume. You will have to recognize which line it is. For instance, for my TM backups, the "df" line is:

/dev/disk2s2 1.8Ti 416Gi 1.4Ti 23% 108992788 378777580 22% /Volumes/Time Machine Backups

You can then use the "umount" command as described earlier. Sometimes "umount" fails, then try the "diskutil unmount /dev/disk2s2" where /dev/disk2s2 is the name appropriate to your system.

Lastly, you aren't attempting to use your boot volume also as your TM backup partition, are you? If you are, you won't be allowed to unmount it.

Switon


@Switon

Appreciate your explanation and all of your help, truly...

I do not know what happened or how I did it but the afp mounted share is no longer showing itself in TimeMachine...I hope that it is truly gone and does not re-appear when I get back home this evening...in the event that it does I may be back for more help...

I have concluded that I am staying away from AFP, TMUTIL related and other terminal commands until I get more Mac compliant / comfortable...

No -- just to respond to everything -- I was not using my boot volume rather I was using my NAS drive...

The lesson that I have learnt is that while it is possible to use a non-Apple device [i.e. WD ShareSpace NAS] it is far easier not to do so...the number of hours waste on this little exercise was unbelievable.


@ All

Appreciate all the help and hopefully will not be back when I get home as noted in the immediately preceding text...

As far as TimeMachine is concerned I also discovered that it takes snapshots while NOT connected to your TimeMachine device...these are in a hidden volume named MobileBackups....to get rid of these simply enter the command "sudo tmutil disablelocal"

Though I said I would stay away from Terminal commands I would think this would be a good exception given that these slices can become quite large in time.

Though it may be me I am begging to think that TimeMachine is not for me given the challenges / problems that I have experienced over the last two days...perhaps something like backuplist+ [see http://www.macupdate.com/app/mac/21413/backuplist+] or carbon copy cloner [see http://www.macupdate.com/app/mac/7032/carbon-copy-cloner ] would be better and easier...what are your experience / thoughts on this.

Thanks,


Joel

blueroom
Dec 6, 2012, 12:11 PM
IMHO TimeMachine backups are great, I use a Synology NAS though, which is very flexible.

rhoydotp
Dec 6, 2012, 12:38 PM
Though it may be me I am begging to think that TimeMachine is not for me given the challenges / problems that I have experienced over the last two days.

the Timemachine to NAS (AFP/CIFS/SMB/NFS) is a hack. Apple does not officially support it. Timemachine with a disk directly attached to it is great and has been working for a lot of people since it first came out.

JoelBC
Dec 6, 2012, 03:57 PM
I am completely disappointed....I get home and the drive is back again...where to we go from here noting the following:

1. I enter "df -h" and the mount does NOT appear...I see no reference to the drive...


2. I move my cursor over the drive in TimeMachine and I see the following "afp://JoelcHomeNAS/WD_Backup


3. I tried entering "sudo umount //wd_backup@JoelcHomeNAS/WD_Backup"....I get prompted for a password but the drive remains mounted.


4. I tried "sudo diskutil umount //wd_backup@JoelcHomeNAS/WD_Backup"....I get prompted for a password but the drive remains mounted.

This is driving me nuts....please help...

Thanks,


Joel

JoelBC
Dec 6, 2012, 08:36 PM
Guys...I need serious help...I wiped my entire hard drive, did a clean install and to no avail as their must be some reference on the NAS drive that is looping back to the MBA...NOT happy...

Does anybody have any idea as to how to kill this link as my MBA is useless until it is killed...

Thanks,


Joel

JoelBC
Dec 7, 2012, 12:16 AM
Gents, this situation is unbelievable...given that I could not figure out how to unmount this drive I decided that i would try to disassociate it by i) changing the server name ii) changing the static IP address and iii) changing the password but the damn thing morphed in that it still showed as a "TimeMachine available disk"...how can this be given that the command used to mount drive [see post 6 on this thread] contains the server name / IP address and password...

This is getting me to think that through this process something has been put on the server which is finding its way back to my MBA...very disturbing....

Well, the only thing that is obvious is that I need help...

justperry
Dec 7, 2012, 05:00 AM
Guys...I need serious help...I wiped my entire hard drive, did a clean install and to no avail as their must be some reference on the NAS drive that is looping back to the MBA...NOT happy...

Does anybody have any idea as to how to kill this link as my MBA is useless until it is killed...


This is getting me to think that through this process something has been put on the server which is finding its way back to my MBA...very disturbing....

Well, the only thing that is obvious is that I need help...

I will comment on the bold below.

First, I though I would create the situation like yours myself, I do have a AppleTV (version 1) with OS X installed so I made a afp share, but in terminal I could not use the command, seems like my Leopard does not have the tmutil Command.

What I did see though is that when I select a drive for TimaMachine it creates a file on that network drive, it is invisible though and on the drive it is named: .001124413ce8 , I opened it up but did not show much, this is the text : Ÿ∑ATK‰∂,$Ω≤f

Now, on the bold, you said you completely wiped the drive yet it came back, this can mean only one thing, there is a setting on the NAS which will push the drive to mount on your Mac, there is simply no other way it could happen since you wiped the disk.

You could try to delete the file I mentioned, I am not sure though if it is called the same, it was/is at the root level of a disk, I choose another external Firewire disk for TimeMachine to use and it created the same named file, so if you want to know what the name is in your case then just switch on Timemachine on a different disk and see the file created.
Be aware though, it is invisible and you have to make files visible before you can see it.
But, it might also be some other protocol which I am not aware of, lets say the command you entered switched something on in the NAS, it will have it's own setting somewhere and here it gets too difficult to solve.

See Screenshot below.

JoelBC
Dec 7, 2012, 05:12 AM
I will comment on the bold below.

First, I though I would create the situation like yours myself, I do have a AppleTV (version 1) with OS X installed so I made a afp share, but in terminal I could not use the command, seems like my Leopard does not have the tmutil Command.

What I did see though is that when I select a drive for TimaMachine it creates a file on that network drive, it is invisible though and on the drive it is named: .001124413ce8 , I opened it up but did not show much, this is the text : ∑ATK∂,$Ω≤f

Now, on the bold, you said you completely wiped the drive yet it came back, this can mean only one thing, there is a setting on the NAS which will push the drive to mount on your Mac, there is simply no other way it could happen since you wiped the disk.

You could try to delete the file I mentioned, I am not sure though if it is called the same, it was/is at the root level of a disk, I choose another external Firewire disk for TimeMachine to use and it created the same named file, so if you want to know what the name is in your case then just switch on Timemachine on a different disk and see the file created.
Be aware though, it is invisible and you have to make files visible before you can see it.
But, it might also be some other protocol which I am not aware of, lets say the command you entered switched something on in the NAS, it will have it's own setting somewhere and here it gets too difficult to solve.

See Screenshot below.

Thanks, I find this to be totally unbelievable...hopefully someone has an answer...as a start I am going to back up all the data on my NAS today in case I do in fact need to reformat my NAS drive....


Joel

justperry
Dec 7, 2012, 05:17 AM
Thanks, I find this to be totally unbelievable...hopefully someone has an answer...as a start I am going to back up all the data on my NAS today in case I do in fact need to reformat my NAS drive....


Joel

If you do unplug the NAS the share should unmount, probably after a dialogue box in OS X that warns you a disk has unsafely been removed, if not then some ghosts are playing with your mac.

Edit: you did not mention how it is connected, wired, wireless, through an Apple Airport Extreme/Express.

JoelBC
Dec 7, 2012, 05:53 AM
If you do unplug the NAS the share should unmount, probably after a dialogue box in OS X that warns you a disk has unsafely been removed, if not then some ghosts are playing with your mac.

Edit: you did not mention how it is connected, wired, wireless, through an Apple Airport Extreme/Express.

Powering down / powering up the NAS does not remove the problem as it must be some sort of persistent file...

The NAS is hard-wired to my home network...

switon
Dec 7, 2012, 08:52 AM
Hi JoelBC, (is that British Columbia or Boston College or ?)

Wow! What problems you have...

Did you try forcing the unmounting of the shared drive? If someone else has a connection to the drive, then you will not be allowed to unmount it. I believe that forcing (-f) the unmounting will unmount even when others are connected.

Do you have a launch agent or daemon that is continuously mounting this share?

Is this share being mounted by more than one protocol, say afp, smb, and/or nfs? Are you allowing "Guest" SMB connections? Are any of your "neighbors" connecting as Guests?

Are you running Mac OS X Server? If so, could you execute the following command to see what users are connected to the share:

serveradmin command afp:command = getConnectedUsers

Switon

justperry
Dec 7, 2012, 09:29 AM
I have been thinking about this a lot today, the strange thing is you reinstalled and it still mounts.
Then later today I thought about resetting NVRAM(Pram) and SMC, now I went to Apple's site again, SMC has nothing to do with it and on NVRAM it says there are no network settings in NVRAM on that MAN page.
That is not completely true because in my NVRAM (nvram -p) it says skip-netboot?

Earlier I asked you how it was connected, part of the reason was that you can set up a TimeMachine over an Airport Extreme/Express and thought if you had one the problem could be there, or is it in the (i)cloud!!
But since you are hardwired that does not seem to be the case.

Switon seemingly knows quit a bit but in his post above forgot you reinstalled everything (No offence Switon) and if you wiped your machine clean there is no way there is anything left, except clearing the PRAM.

switon
Dec 7, 2012, 10:29 AM
Hi,

justperry: I have to admit that I speed-read these threads looking for pertinent details, especially when I'm busy and the thread has 25+ posts. Thus I'm sure I miss things...although I did notice that JoelBC did a clean install -- but I have to ask if and how he restored. If he restored then chances are that the configuration files were restored too.

I suspect that the share is being mounted by some other user, perhaps as a "Guest" which can be configured to not even require a password. That's why I asked JoelBC to check on how many connections there are to this share. If there are any other connections, even from a guest account on his machine, then he will not be allowed to unmount the share unless the unmount is forced. Perhaps JoelBC's use of the tmutil command configured an automatic launchd agent that keeps the share mounted. Since TM already does auto-mounts and auto-dismounts of shared backup disks once an hour, it is entirely possible that JoelBC's use of tmutil configured an automatic mounting. (Basically, I have used tmuitl to turn off local snapshots, set the destination volume, and restore from a sparse bundle. And in my hands, I don't have the problem of not being able to umount a TM mounted volume -- I tested this myself yesterday, and I could umount the TM mounted volume without issue.)

I would really like to know if JoelBC is using Mac OS X Server to configure the afp, smb, and/or nfs shares? If so, then executing the serveradmin command I gave in my last post should tell JoelBC if some other user has connected to the afp share, such as a guest account. Similar commands could check if there are any smb or nfs connections. There could even be any of a number of other system users, say a _devicemgr, _ftp, _installassistant, _kadmin_admin, _krb_admin, etc. that might connect to the share. Are there any "Home Folder"s on the share?

If JoelBC is not using Mac OS X Server, then perhaps a solution to his problem would be to use this server software to configure the file sharing. He could then better control precisely who gets access and what type of access is granted. I know this is an extreme solution, but I've never had a situation where I could not unmount a shared volume, including a TM volume, especially after making certain there are no other connections.

JoelBC: What if you use tmutil to removedestination for the wd_backup and to set the destination to a different volume? Does this eliminate the WD_Backup from being mounted too? (The 10.8 Time Machine allows for multiple destination volumes, and it will oscillate among destination volumes for its backups. Thus you may need to remove the old destination and not just set a new destination since with the -a option this will only add a new volume to the list and not eliminate the old one.)

Edit: JoelBC, if you execute the command,

sudo defaults read /Library/Preferences/com.apple.TimeMachine

how many hostUUIDs do you have?

Switon

JoelBC
Dec 7, 2012, 05:07 PM
Hi Everyone....

First, thanks for all of the help, greatly appreciated...

And, to those who are interested, here is what I learnt after 30 minutes on the telephone with a WD Level 2 System Engineer [Jeremy (very helpful and nice), case # 120712-633-2496].

1. As far as the WD ShareSpace that I have it is officially supported in OS X 10.7 and earlier [i.e. it is not officially supported in 10.8 and higher.]

2. As far as WD_Backup hidden share i) appearing as a TimeMachine eligible backup disk and ii) showing an AFP path when moused over this is "normal behavior" in that this is how it appeared / worked ans has always been "mounted" (see 3. below) in OS X 10.7 and earlier.

3. As far as the WD_Backup hidden share being mounted it is NOT mounted but rather appears -- AND ONLY IN TIME MACHINE -- as a mountable drive...the proof / support for this is that one needs to enter credentials were one to select this share as their TimeMachine drive.

4. As far as last night's activities [i.e. creative attempts by me to "break" the AFP link as noted in posts 19 and 20 of this thread] the above behavior explains my lack of success and the adaptive behavior of the NAS to always appear in TimeMachine.

The above also explains why none of Swinton's suggested comamnds worked!!!

5. As far as the concerns / differences between the time when I first reported the problem [let's call this Install 1] and the the current situation [let's call this Install 2 (i.e. after having done a wipe my OS X disk and fresh install)] is that:

-- Install 1 was not appearing to work properly in that the WD_Backup hidden share did not appear in TimeMachine and I had to enter the command "sudo smutil....".

-- Install 2 appears to be working properly in that the WD_Backup hidden share appears in TimeMachine without me having to enter the "sudo smutil ...." command.

What could the cause of the difference be between Install 1 and Install 2...though my MBA is brand new is it possible that the initial install was flawed?


6. As far as the current situation and next steps are concerns it appears that I am in a different situation now in that I have *NOT* mounted the drive and, given the previously problems I had with the AFP mounted drive, I will not do so!


7. Other interesting tidbits in my attempt to completely separate the WD_Backup hidden share from my MBA...

a) There is no way to roll back to earlier firmware versions which DO NOT have the AFP broadcast feature.


b) There is no way to turn off AFP within the NAS drive...therefore the only way to stop the WD_backup hidden share from appearing in TimeMachine is to disable AFB in OS X which I am not going to do.

c) There WD_Backup hidden share has been designed from day one to be i) "mapped" and then mounted AFP ii) not directly accessible from within OS X.

d) This means that even formatting the drives will change not a thing...good thing I was patient this morning as I was considering doing this!


8. Those interested in a TimeMachine compatible drive should get a MyBook Live [this was the WD engineer's suggestion] as it has the ability to i) backup to other shares in TimeMachine and ii) not appear in Timemachine...seems my drive is old in the tooth....

*****

Two final closing points / thoughts...

1. Thanks to all who tried to help me as you concern, effort, and time are greatly appreciated and is what makes this a great community.

2. Would be interested in your thoughts and comments on the above.

Thanks,


Joel


PS. It follows that technology is great when it works and a huge frustration and time waster when it does not...that said, I remain interested as to why the WD_backup share did not automatically appear in Install 1.

JoelBC
Dec 7, 2012, 06:03 PM
@Swinton...to answer your questions....

1. No, I did a fresh install and then reloaded all my applications...I did not use any backups as I knew that this would only corrupt things.

2. No, there are no Guests or other users...just me... :)

3. No, I am new to OS X and did not want to start with OS X Server as this would have been more that I could handle at this point.


Joel

switon
Dec 7, 2012, 08:52 PM
Hi JoelBC,

Glad you were able to solve your problem...so the drive wasn't mounted all along, hummm...

Well, the take home story is that it is always good to call the manufacturer --- I'm glad that WD was so helpful.

I apologize for not being any help to you.

Switon

JoelBC
Dec 8, 2012, 08:40 AM
Hi JoelBC,

Glad you were able to solve your problem...so the drive wasn't mounted all along, hummm...

Well, the take home story is that it is always good to call the manufacturer --- I'm glad that WD was so helpful.

I apologize for not being any help to you.

Switon

A few additional points:

1. Am not sure agreed with you as to whether the drive was or was not mounted...I would argue that in Install 1 the drive was mounted as I issues the "sudo smutil setdestination..." command and actually used the drive for bakup [i.e. it had to be mounted]...in Install 2 I believe that the drive is NOT mounted...

2. Completely agree that calling technical support is helpful...the problem is that it takes a while to get to the right person as I wasted 2 days on this and nearly decided to reformat my drive...this would have been a disaster...

3. Nothing to apologize for as you were very helpful...much thanks..


Joel

switon
Dec 8, 2012, 09:05 AM
A few additional points:

1. Am not sure agreed with you as to whether the drive was or was not mounted...I would argue that in Install 1 the drive was mounted as I issues the "sudo smutil setdestination..." command and actually used the drive for bakup [i.e. it had to be mounted]...in Install 2 I believe that the drive is NOT mounted...

2. Completely agree that calling technical support is helpful...the problem is that it takes a while to get to the right person as I wasted 2 days on this and nearly decided to reformat my drive...this would have been a disaster...

3. Nothing to apologize for as you were very helpful...much thanks..


Joel

Hi Joel,

(1.) The "tmutil setdestination" command does not actually mount the drive, rather it configures the drive so that TM can mount and unmount it when it needs to for its backup. So, unless you actually mounted the drive or TM mounted it and then did not unmount it correctly, the drive was most likely not mounted (TM only mounts the drive for its backup, it unmounts it after the backup is finished). It was my mistake to think that it was mounted when I made suggestions on how to unmount it. I believe the fact that "df" did not find the drive means that in fact it was not mounted (at least at the time you attempted my suggestions for unmounting it).

I'm just glad that you solved your problem.

And, believe it or not, it does get much easier. I know your experience was not very pleasant, but hang in there and you will gain unix experience quickly.

Switon

JoelBC
Dec 8, 2012, 09:10 AM
Hi Joel,

(1.) The "tmutil setdestination" command does not actually mount the drive, rather it configures the drive so that TM can mount and unmount it when it needs to for its backup. So, unless you actually mounted the drive or TM mounted it and then did not unmount it correctly, the drive was most likely not mounted (TM only mounts the drive for its backup). It was my mistake to think that it was mounted when I made suggestions on how to unmount it. I believe the fact that "df" did not find the drive means that in fact it was not mounted (at least at the time you attempted by suggestions for unmounting it).

I'm just glad that you solved your problem.

And, believe it or not, it does get much easier. I know your experience was not very pleasant, but hang in there and you will gain unix experience quickly.

Switon

Thanks for the encouragement...


Joel