All Shared Volumes Do Not Mount

I have setup personal sharing across a wireless network and three Mac laptops. They all connect, but all the volumes from one Powerbook (a Smartdisk 250Gb Crossfire drive used to store music and photos) do not mount. The other Smartdisk Firelite shows up across the network. Problems printing, but that's probably a different question.

McGilli wrote:
I only have my ADMIN account on the Air... not using the Guest account. it is like this on both machines....
Hmmm - on my iMac i get an icon on my desktop - a picture of a drive with 3 people holding hands on it. It goes right beside my time machine, and external hdd icons...
The air doesn't get anything new on the desktop even after it mounts it in the device ...
attaching an external drive brings up a desktop icon on the Air.
I don't mean the login Guest account. When you log into a remote computer, if you do not click, "Connect as" and login with a regular account you default to a guest-like account.
If that is the case, click "disconnect" in Finder and then "Connect as" You should get a popup login window for the other computer. Otherwise you have limited privileges on the remote machine.

Similar Messages

NEED HELP Xsan volume is not mounted (strange problem)

I ask the help in solving the volume mount problem. (advance I am sorry for my english)
All began with the fact that the MDC is rebooted and on the two LUNs were gone XSAN label. I relabeled these LUNs using commands:
cvlabel -c >label_list
then in the file label_list I corrected unknown disks on the label with a same names that were. Then I ran the cvlabel label_list command. Finally I got the correct label on all drives.
# cvlabel -l
/dev/rdisk14 [Raidix meta_i          3365] acfs-EFI "META_I"Sectors: 3906830002. Sector Size: 512. Maximum sectors: 3906975711.
/dev/rdisk15 [Raidix QSAN_I          3365] acfs-EFI "QSAN_I"Sectors: 7662714619. Sector Size: 4096. Maximum sectors: 7662714619.
/dev/rdisk16 [Raidix meta_ii         3365] acfs-EFI "META_II"Sectors: 3906830002. Sector Size: 512. Maximum sectors: 3906975711.
/dev/rdisk17 [Raidix 2k_I            3365] acfs-EFI "2K_I"Sectors: 31255934943. Sector Size: 512. Maximum sectors: 31255934943.
/dev/rdisk18 [Raidix 2k_II           3365] acfs-EFI "2K_II"Sectors: 31255934943. Sector Size: 512. Maximum sectors: 31255934943.
/dev/rdisk19 [Raidix QSAN_II         3365] acfs-EFI "QSAN_II"Sectors: 7662714619. Sector Size: 4096. Maximum sectors: 7662714619.
The volume [2K] starts successfully.
but not mounted on the MDC and client.
I ran a volume check:
sh-3.2# cvfsck -wv 2K
Checked Build disabled - default.
BUILD INFO:
#!@$ Revision 4.2.2 Build 7443 (480.8) Branch Head
#!@$ Built for Darwin 12.0
#!@$ Created on Mon Jul 29 17:01:44 PDT 2013
Created directory /tmp/cvfsck3929a for temporary files.
Attempting to acquire arbitration block... successful.
Creating MetadataAndJournal allocation check file.
Creating Video allocation check file.
Creating Data allocation check file.
Recovering Journal Log.
Super Block information.
FS Created On               : Wed Oct 2 23:59:20 2013
Inode Version               : '2.7' - 4.0 big inodes + NamedStreams (0x207)
File System Status          : Clean
Allocated Inodes            : 4022272
Free Inodes                 : 16815
FL Blocks                   : 79
Next Inode Chunk            : 0x51a67
Metadump Seqno              : 0
Restore Journal Seqno       : 0
Windows Security Indx Inode : 0x5
Windows Security Data Inode : 0x6
Quota Database Inode        : 0x7
ID Database Inode           : 0xa
Client Write Opens Inode    : 0x8
Stripe Group MetadataAndJournal             ( 0) 0x746ebf0 blocks.
Stripe Group Video                          ( 1) 0x746ffb60 blocks.
Stripe Group Data                           ( 2) 0xe45dfb60 blocks.
Inode block size is 1024
Building Inode Index Database 4022272 (100%).
   4022272 inodes found out of 4022272 expected.
Verifying NT Security Descriptors
Found 13 NT Security Descriptors: all are good
Verifying Free List Extents.
Scanning inodes 4022272 (100%).
Sorting extent list for MetadataAndJournal pass 1/1
Updating bitmap for MetadataAndJournal extents 21815 ( 0%).
Sorting extent list for Video pass 1/1
Updating bitmap for Video extents 3724510 ( 91%).
Sorting extent list for Data pass 1/1
Updating bitmap for Data extents 4057329 (100%).
Checking for dead inodes 4022272 (100%).
Checking directories 11136 (100%).
Scanning for orphaned inodes 4022272 (100%).
Verifying link & subdir counts 4022272 (100%).
Checking free list. 4022272 (100%).
Checking pending free list.
Checking Arbitration Control Block.
Checking MetadataAndJournal allocation bit maps (100%).
Checking Video allocation bit maps (100%).
Checking Data allocation bit maps (100%).
File system '2K'. Blocks-5784860352 free-3674376793 Inodes-4022272 free-16815.
File System Check completed successfully.
check not helping
sh-3.2# cvadmin
Xsan Administrator
Enter command(s)
For command help, enter "help" or "?".
List FSS
File System Services (* indicates service is in control of FS):
1>*2K[0]                located on big.local:64844 (pid 5217)
Select FSM "2K"
Created           :          Wed Oct 2 23:59:20 2013
Active Connections:          0
Fs Block Size     :          16K
Msg Buffer Size   :          4K
Disk Devices      :          5
Stripe Groups     :          3
Fs Blocks         :          5784860352 (86.20 TB)
Fs Blocks Free    :          3665561306 (54.62 TB) (63%)
Xsanadmin (2K) > show
Show stripe groups (File System "2K")
Stripe Group 0 [MetadataAndJournal] Status:Up,MetaData,Journal,Exclusive
Total Blocks:122088432 (1.82 TB) Reserved:0 (0.00 B) Free:121753961 (1.81 TB) (99%)
MultiPath Method:Rotate
    Primary Stripe [MetadataAndJournal] Read:Enabled Write:Enabled
Stripe Group 1 [Video] Status:Up
Total Blocks:1953495904 (29.11 TB) Reserved:270720 (4.13 GB) Free:129179 (1.97 GB) (0%)
MultiPath Method:Rotate
    Primary Stripe [Video] Read:Enabled Write:Enabled
Stripe Group 2 [Data] Status:Up
Total Blocks:3831364448 (57.09 TB) Reserved:270720 (4.13 GB) Free:3665432127 (54.62 TB) (95%)
MultiPath Method:Rotate
    Primary Stripe [Data] Read:Enabled Write:Enabled
I checked the availability of LUNs on MDC and client, there also all right.
But, unfortunately, the Volume is not mounted
xsanctl mount 2K
mount command failed: Unable to mount volume `2K' (error code: 5)
Please help me to figure out this situation, I will be grateful for any information.
Thanks

That looks like an I/O error. You may have an issue with one or more of the data LUNs. Check the system log for errors.

Our XServe-RAID volume does not mount anymore...

Our XServe-RAID volume does not mount anymore.
On /var/log/system.log I could find the following.
Feb 22 09:52:29 ogre kernel: jnl: open: journal magic is bad (0xf433f != 0x4a4e4c78)
Feb 22 09:52:29 ogre kernel: hfs: early jnl init: failed to open/create the journal (retval 0).
It appears the the journaling is badly screwed.
I tryed to disable the journaling with no success.
Here is what I get.
ogre:/var/log root# diskutil disablejournal disk2s3
The selected journaling request does not appear to be valid
After some googling I foud this :
--- QUOTE ---
The more serious problem occurs when the contents of the journal file are corrupted in such a way that the operating system does not proceed to mount the volume. Fortunately, this problem is extremely rare (I have seen three reports of corrupted journal files at the MacFixIt Forums and Apple Discussion Forums since journaling was introduced).
Starting the journaling process is one of the first things that happens when a volume is recognized by the operating system. There appears to be no way to intervene in single-user mode before the journal file is examined. A message about �bad journal magic� appears. Unfortunately, every tool that can turn off journaling requires that the volume already be mounted.
If the Macintosh can boot under Mac OS 9, dealing with a corrupted journal file involves restarting under Mac OS 9 and using a utility (such as our free TechTool Lite 3.0.4) to make visible these two invisible files at the root level of the volume:
/.journal
/.journalinfoblock
Once these files are made visible, they can be deleted. Mac OS 9 does not support journaling, and recognizes nothing special about these files. Neither of these files can be seen in Terminal or in single-user mode in Mac OS X, because they are considered part of the disk directory.
If the Macintosh cannot boot under Mac OS 9, but the drive has Mac OS 9 drivers installed, the drive can be put into a Macintosh that can boot under Mac OS 9, or an ATA/IDE drive can be put into a suitable FireWire enclosure.
The possibility that you may need to remove these two journaling files under Mac OS 9 is a good reason for making sure that all volumes you use have Mac OS 9 drivers installed. The drivers must be installed when the drive is formatted.
--- [END] QUOTE ---
Well, my disk is part of a RAID 5 matrix.... so the solution proposed does not work.
Does any one of you has any idea ?
XServe Mac OS X (10.3.9)

I've seen an article about volumes not mounting and was wondering if this relates to your problem;
http://discussions.apple.com/thread.jspa?messageID=1239224&#1239224
The thread doesn't refer to journalling but may be of use?
HTH

Time Machine backup volume will not mount

Once I goy Time Machine up and running over almost two years ago, I have had little cause for concern. A few lengthy backups here and there but I have been able to restore without any problems whatsoever. It has been extremely useful many times.
A couple of days ago, I noticed that the backup volume was not mounted (I backup to one of my four internal drives) and launched Time Machine. I got the error:
The storage location for Time Machine backups can't be found.
When I run Disk Utility the generic disk icon is in the left hand pane but not the volume. None of the tasks are available except Erase and Partition - there is no option to Verify Disk, Repair Disk, Verify Disk Permissions or Repair Disk Permissions.
According to my logs, the last backup at 18:12 on 20th November was successful. I didn't notice that the volume had not mounted the until the next day.
I'm very concerned that I have lost almost two years of data security. Is there any way I can repair the disk or recover the backups?
Thanks.

If Disk Utility can't see any partitions, it's not good.
First, turn TM off.
Then try ejecting, disconnecting and powering the drive off for a few minutes, then reattaching it. Then try again with Disk Utility. If still no help, the drive is likely dead.
There's a very small chance that +Disk Warrior+ (version 4.1.1 or 4.2 only), or another heavy-duty disk repair app can fix it, if you already have one. But I wouldn't suggest spending the $$ for one unless you think you'll need it in the future -- DW is about $100.
Most likely, your disk is dead. There's a small chance that a +Data Recovery+ app such as +Data Rescue+ can recover some of the data. Check via Google, VersionTracker.com, or MacUpdate.com for +Data Recovery.+ There are services and apps, none cheap. Some of the apps have a free demo or test mode that will tell you if there's anything that can be recovered, and perhaps actually recover a single file; then you pay for it and recover whatever else can be recovered. You'll need another external disk to receive the recovered items.
You won't get the normal Time Machine folder structure, though, just "raw" files. Even if you do recover files, you'll most likely have to figure out what goes where and copy them to the right places manually.
So I'd suggest immediately getting a new drive and doing a new TM backup to it, so you have something. Put a second partition on it that you can use for the recovered files if and when you do that.
If those are your only backups, I'd recommend getting a second external, perhaps a portable one, and using CarbonCopyCloner or SuperDuper to make a full "bootable clone" to it, then take it to your safe deposit box, workplace, relative's house, or other secure location. And/or, you might want to look at Mozy, Carbonite, or other online backup services.

Volume will NOT mount

We have much the same issue as others here in other threads have spoken about - after a reboot a raid volume will not mount.
Disk Utility can 'see' the drive and array, but will not mount it. RAID Admin reports no problems. I tried updating the firmware to no avail.
Then I tried a new FC card in the server, a different controller card in the xRAID, different cables and connecting the FC cable to a different XServe. No mount with any of these attempts.
XServe 2 ea 2.3Ghz G5, 2GB RAM, 1 80GB drive (cluster node config)
OSX Server 10.3.9
7 ea 180GB drives, RAID5; 1 TB array
RAID Admin 1.5 (controller firmware - now: 1.5/1.50f)
Any ideas what to try next? And no we don't have 100% backups, close but no... ;-( so any ideas worth trying appreciated!
Tks, Mark

Mark,
We recently had a similar problem. We have an XServe RAID fully populated -- split into 2 volumes. One volume would mount the other would not (after a reboot). Tried swapping fibre channel cables, re-seating fibre channel cards, etc. Our solution was replacing the PCI-Fibre card in the XServe.
Another thing we have had happen is, after reboot, one volume mounts and the other mounts about 15 mins later -- after completing fsck.
Hope this helps.
--Bonnie

Hyper V hosts with Cluster Shared Volume do not provide Shared VHDX ability

Hi there, i've configured a pair of Hyper V hosts (UCS B230 M2) with SAN-Boot and access to a Shared Fiber Channel LUN.
No matter what I try, when I add a SCSI Adapter and one VHDX virtual disk to a VM, the option for "Advanced" never shows up therefore I can not share the VHDX file between another VM, which prevents any VM based clustering from working (IE: Clustered
SQL server)
Here are the settings I have configured:
The LUN has been formatted with NTFS
The Hyper V hosts have been configured as a Windows Cluster with an IP address and the Fiber Channel LUN configured as a Cluster Shared Volume
I follows the guides below
Create a CSV
https://technet.microsoft.com/en-us/library/dn265980.aspx
Create a shared VHDX
https://technet.microsoft.com/en-us/library/dn282283.aspx
Further details:
Two HyperV server core hosts built
Both joined to AD
Both joined to a Windows failover cluster
One 2TB Fibre Channel LUN presented from an EMC VNX array to both hosts
LUN formatted as NTFS
LUN created as a Cluster Shared Volume
Cluster Shared Volume present on both HyperV hosts
VM created within the Cluster Shared Volume
VM Booted up and Windows 2012 has been installed
VM gracefully shut down
Through the HyperV Manager, going in to VM settings,create a SCSI adapter, create a new VHDX file inside the CSV, the “Advanced” option for the VHDX is not present, therefore the option to make the VHDX file shared is not available
I have followed all steps in the Microsft Technet pages to create a CSV and a VM with Shared VHDX
I’ve cleared all settings and restarted multiple times, but this option is not present

Hi Sir,
>>No matter what I try, when I add a SCSI Adapter and one VHDX virtual disk to a VM, the option for "Advanced" never shows up therefore I can not share the VHDX file between another VM
>>Yes we are using Hyper-V Server 2012 R2
As we know Hyper-v server 2012R2 is a free version without GUI , I'm afraid you are not using Win 8.1 or other windows server 2012R2 to manage that free version hyper-v server .
Shared vhdx is a new feature came with 2012R2 , if use previous windows to manage 2012R2 you will not see "advanced" option (The blue circle belongs 2012 , the red circle belongs to 2012R2 ):
Best Regards,
Elton Ji
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

XServe RAID volume does not mount

Without any modification to the system, a panic log from our XServe indicates:
"Thu Jan 18 17:28:58 2007
panic(cpu 0): HFS: corrupt VH on PBSRaid1, sig 0x4100, ver 0, blksize 0"
The volume PBSRaid1 does not mount anyway from that date.
Diskutil reports:
"Verifying volume “disk2s3”
Checking HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Invalid extent entry
The volume PBSRaid1 needs to be repaired.
Volume check failed."
DiskUtil is unable to repair the volume.
My configuration is:
XServe bi-G3 1GHz, MacOSX Server 10.3.9
XServe RAID with 5 disks RAID5 on the left side (OK) and 4 disks RAID5 on the right side (the bad volume)
All the controls are "green" and nothing wrong appeared in the events log obtained via RAID ADmin.
Any suggestion to repair are welcome, as we have many data from confocal microscopy on that volume.
Thanks
Jean-Pierre
XServe bi G3-1GHz (oct 2003)+ XServe RAID Mac OS X (10.3.9)

Right, Dave.
DW 4 rebuilt a preview folder which contains all the files in correctly named folders.Only 3 files among thousands has been saved in a Rescue folder !
It also restored the right volume label, lost in DiskUtil, fsck, pdisk and others.
Very nice tool.
While DW was building its preview, the disk 9 lighted red and a lot of failures of the controler 2 appear in the events log of the XServe RAID.
At this time, the RAID is rebuilding with our spare disk.
I think we have to change both the disk 9 and the controler 2 despite it lights green currently.
Jean-Pierre
XServe RAID (2003- 5xIBM 180Go RAID 5) +(2005 -4xHitachi 250Go RAID5) Mac OS X (10.3.9)

Network drives volumes will not mount

Hi can anyone help me. At my wits end here. Have upgraded 2 machines in our office. 1 Intel Pro mac and 1 Intel iMac, upto 10.6.6
Problem is now when i log onto the ehternet network server drives or random LOCAL USB drives (basically anything external) the connecting machines restart the desktop environment and refuse to mount the drive or folder in question, sometimes it can be infinite loop style reload of the desktop until it finds what its looking for or not. Not all the time just occasionally. Have re installed the combo update but still not fixed it. Could it be a faulty Snow Leopard disc?
Should have mentioned that the server machine is running 10.4 and was running perfectly with the machines on 10.5, so presuming its not that rather the snow leopard upgrade..
Message was edited by: smuuudge

I am having the same issue at our school district. If i wipe out the account and network folder, then recreate it individually it works on both Mac and Windows. So definitely on the server end.

Finder sees a shared volume, but cannot mount it

I have a problem with a G5 that is on a network with a Mini and a G4, both set to up for Sharing. The Mini is also a print server.
(1) The G5 cannot log onto either the Mini or the G5. The G5 Finder sees and identifies both in Server Browse. It just no longer will mount them, displaying no message why.
(2) The G5 can print using the Mini as a print server, though!
(3) The G4 can log onto the Mini.
(4) The Mini can log onto the G4.
Any ideas?

I think those aren't simple files, though...
/Library/Preferences/SystemConfiguration/preferences.plist
and some others may hold some of them.
I think most of the problem lies in the files/folders at Root called Automount, Network, and Servers.
If you wish to try to eradicate them with sudu Terminal commands I can gelp.
I've used Xupport to turn off hiding those Hidden files so it's easier to see those things, though I've been admonished for suggesting the regular User do such things... I hate the concept of Hidden Files... well, when everything goes right, they're not a problem, but over here, when things go wrong and Apple can't fix them, then most are at a loss.

VM using cluster shared volume will not run if the CSV is owned by a different node.

If a VM is owned by node "A" and the VHD file is on a CSV that is owned by node "B", it will fail to start. Hyper-v manager popup says that the VHD file is not accessible. If you change the owner of the CSV file to
node "A", it works. This would imply that the node cannot access the files on the CSV it does not own. However, the you can logon to the nodes and all have access to the csv.
This is a Server 2008 R2 cluster. I would appreciate any help in solving this.

Hi Dana,
No you don't need to destroy the cluster.
If you run cluster validation from fail over cluster manager it will allow you to run all checks. It will mention that you have resources that are using some of the CSV but then give you the option to take those cluster resources offline during the test
to check all storage. Or to leave those CSV out of the test depending on which you choose. All other test should be possible with the cluster up and it will NOT need to be destroyed to run them.
Open validation wizard
Select "Run all test (recommended)
On the next window check all storage and then run the checks.
NOTE: This will take all resources offline so if checking CSV with VMs on it would be probably best to shut them down first.
Kind Regards
Michael Coutanche
Blog:Twitter:LinkedIn:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Xsan 4 will not mount volume on client

I recently upgraded my MDC and my client computer to Yosemite. I went through the migration process the best I could and created a Configuration Profile on my MDC for my client computer. I installed the profile successfully but the volume will not mount on the client computer. On the client computer within Profiles, the Xsan Configuration Profile has in red "Unsigned" underneath it, is that what is causing the problem?
Also a few notes: there are two other client computers that haven't been upgraded and are running Maverick and the volume does mount to those computers. The volume is also mounted on the MDC and if I go to Disk Utilities on the client computer I do see the volume, just not mounted.
Any help would be great! Thank you.

Thank you Claudio,
After doing much research and testing I believe you are onto something with my fsmpm or my .auth_secret file not being created. After using Server.app on the MDC I used the configure profile within Server.app. After installing the profile on my client computer it didn't mount and when looking within the Library/Preferences/Xsan folder there was no files (including the hidden .auth_secret file). So I then I used the web profile interface to create the configuration profile and this time it installed the fsnameservers and config.plist files but not the hidden auth_secret file and still no mount.
To answer some of you questions, I did try several times the "sudo xsanctl mount Volume Name" but had no success. I was previously running 10.9 on the MDC and my client computer. I am not sure if the MDC already had an Open Directory Master before upgrading and I did have a little bit of problems activating Xsan, because some of my DNS settings had changed. I got that all squared away and Xsan started working.
The reason I believe it is a fsmpm issue is because when I executed the command "sudo xsanctl i" (views the volumes connected to Xsan) I go a message reading "fsmpm not running error3". So after reading this forum Xsan: "fsmpm not running" message in Xsan Admin - Apple Support I copied the .auth_secret from the MDC to my client and still no mount. I tried again with all the files within Library/Preferences/Xsan folder and nothing. I then got the .auth_secret file from another client computer running 10.9 and still no mount, BUT when I copied all the files within the 10.9 client's Library/Preferences/Xsan the volume appeared! YEAH! But I'm not sure if this is a fix I should be happy with or continue to figure out why its not working the proper way? That way in the future I'm not running into this issue over and over again.
So I need to figure out either how to get my fsmpn running in 10.10 or figure out why my my Server.app on the MDC won't create the auth_sect file. I read somewhere that within the Xsan screen in the Sever app it should show the Authentication Secret, but I do not see this on my Xsan screen. Should it be there and if so is this where my problem steams from? Any thoughts? Thank you so much!

USB 3 external drive volume not mounting on restart

I've bought an external USB 3 full size hard drive enclosure case and put in a 2TB drive. The drive is partitioned into 3 volumes. I've noticed from time to time that the volumes have gotten dismounted some how. If I unplug the USB cable and plug it back in the volumes mount again. After a long time I finally figured it out that what's really happening is that the volumes are not mounting when I do a restart, I just didn't notice it before. Once the volumes are mounted they stay mounted until the next restart. I replaced the enclosure and cable with a different and more expensive brand but that didn't make a difference. No matter what I do the volumes never mount on restart.

I think this might be due to the fact that my iMac as a fusion drive and it boots so fast that the exteranl drive isn't finished starting up when OS X is looking for drives durring it's bootup.

The backup volume could not be found

Spent a fair amount of time on the phone with Apple last night trying to get my Macbook Air to work with Time Machine/Time Capsule.
Symptoms of my problem included Time Machine Preferences giving the error "The backup volume could not be found"
Console messages complaining about not being able to find the MAC address for machine:
(console is accessed by clicking Go -> Utilities -> Console from the Finder, and then selecting All Messages)
11/7/08 11:06:13 AM System Preferences[123] *Time Machine failed to get MAC address for machine.*
11/7/08 11:13:09 AM /System/Library/CoreServices/backupd[1603] Starting standard backup
11/7/08 11:13:09 AM /System/Library/CoreServices/backupd[1603] Network mountpoint /Volumes/Time Capsule not owned by backupd... remounting
11/7/08 11:13:09 AM kernel AFP_VFS afpfs_mount: /Volumes/Time Capsule-1, pid 1604
11/7/08 11:13:09 AM /System/Library/CoreServices/backupd[1603] Network volume mounted at: /Volumes/Time Capsule-1
11/7/08 11:13:09 AM /System/Library/CoreServices/backupd[1603] *Volume at path /Volumes/Time Capsule-1 does not appear to be the correct backup volume for this computer. (Cookies do not match)*
11/7/08 11:13:09 AM /System/Library/CoreServices/backupd[1603] Backup requested due to disk attach
11/7/08 11:13:14 AM /System/Library/CoreServices/backupd[1603] *Backup failed with error: 18*
And my only network interface was showing up as en1 (instead of en0). You can check this by using Network Utilities:
- On the Finder main menu bar click Go -> Utilities -> Network Utilities
If "Network Interface (en0)" is not an option in the drop down list under "Please select a network interface for information" (mine was showing as en1), then the following steps will probably solve your problem:
1) Enable the root user
- Open the finder
- On the Finder main menu bar click Go -> Utilities -> Directory Utility
- On the menu bar click Edit -> Enable Root User
- set a password (they suggested using the same password as is used for the main user account)
2) Login as the newly enabled root user
- Click Log Out... from the Apple menu on the main menu bar
- select "Other" at the login screen
- enter the user name "root" and the password you set in step 1
3) Drag Preferences folder to the desktop
- open the finder, and click on Macintosh HD and then Library
- drag the Preferences folder onto the desktop
4) Restart the computer
- Click Restart from the Apple menu on the main menu bar
After this, the Network utility should show "Network Interface (en0)", and Time Machine should work.

Jackson,
See this article for the reasons why you see "Time Capsule-1 does not appear to be the right volume..."
[http://discussions.apple.com/thread.jspa?messageID=8116036&#8116036]
As for the error message you are getting, here are several reasons why you would see this message...
*_"Backup Volume Could Not Be Found"_*
First, it is important to distinguish this error message from another, similar Time Machine error that states, “The backup volume could not be mounted”. This is important as the causes and cures for these two errors can be very different.
*Reselect Your Time Machine Disk*
(http://support.apple.com/kb/TS1329)
In the Finder, go up to the "Go" menu and select "Connect to Server".
Click the "Browse" button at the dialogue box.
In the Network window that opens, do you see your TM drive?
Double click it to mount the drive.
Now let's try to reselect it for Time Machine use.
Go to System Preferences --> Time Machine.
Click the "Change Disk..." button.
Select "None" and click "Stop Backing Up".
Now click "Choose Backup Disk" and reselect your drive again.
Close System Preferences and try backing-up again.
On the other hand, does your Time Machine drive NOT appear at all? Is it appearing on your desktop? If it is still connected try disconnecting the cable, waiting a few seconds and then reconnecting the cable. Does the drive mount on the desktop? Try initiating a backup now.
*Disk Fails to Wake From Sleep*
“If your external HD has a sleep function that does not wake for Time Machine backups. Time Machine will alert you that "The backup volume could not be found", and backups will not be made.” [http://support.apple.com/kb/TS1337]
*3rd-Party Disk Utilities* #
Many external hard disks come with software for maintaining/monitoring hard disk activities. It may have come on a separate CD or been installed on the drive itself. If these programs have been installed they may interfere with Time Machine backups, generate erratic behavior, or cause the drive to ‘disappear’ altogether.
You may never know these applications are there as they may be running in the background. Go to System preferences --> Accounts. Select your account in the pane on the left. Click “Login Items”. Are there any items listed there that might refer to hard disk utilities. If so remove them using the “-” button at the bottom.
*Delete Time Machine Preference .plist*
It may be that the preference list that stores the name of your designated backup disk has become corrupted.
Go to --> Macintosh HD / Library / Preferences (Note: NOT Home / Library / Preferences).
Drag the .plist file labeled,
com.apple.TimeMachine.plist
to the root level of your Macs’ hard drive.
Reboot your computer.
This .plist file is automatically recreated at startup if it is missing.
Now try choosing the external HD in the TM Prefs for backup.
*Time Capsule Has a Long Name*
“When using your Time Capsule for Time Machine backups in Mac OS X 10.5 Leopard or later, the Time Capsule backup volume may not mount and Time Machine may not be able to back up to it. This alert may appear: "Backup volume cannot be found". This can happen if the Time Capsule disk has a long name. [http://support.apple.com/kb/HT1170]
Open AirPort Utility (in /Applications/Utilities).
Click your Time Capsule's icon.
Click "Manual Setup".
Enter the password for the Time Capsule if prompted.
Click the Disks icon.
Highlight the volume name that appears under "Time Capsule Disk".
In the Name field, enter a name for the volume that is less than 27 characters long.
Click Update.
After Time Capsule restarts, on the Mac(s)using Time Machine, open Time Machine preferences and reselect the Time Capsule volume.”
Let us know if any of these suggestions help.
Cheers!

Color Lables on Shared Volumes

Hi Everyone,
I have just found out that when a user changes the label color for a folder on a shared volume the changes are not reflected real-time. That's to say If I change the colour of a folder called Templates to "Red" another user on another mac who also sees the shared volume will not see the label color change made to the Templates folder. He/She will need to disconnect the shared volume and reconnect in order to see the change. Has anyone out there seen this problem? It's not 100% essential but would be good if there was a solution of some sort.
Just to add did not have this problem on my old mac server which was running 10.2.x our new server is running 10.4.8.
Thanks,
Kwong.

Hi Russell, Sorry been away for a few days. The InDesign documents are already on a shared volume and it wouldn't be feasible to save anywhere else as there is a particular hierarchy on the server as to where files are stored, so that all documents are within their relevant job folders, with images, image bank images & graphics etc stored on other shares. However all acl's are the same for all users, so this shouldn't be an issue. I still can't work out whether this is an Apple OS or an Adobe problem.

Everything was OK - now have "The backup volume could not be found" error

Setup:
* MacBook Air
* MacBook 10.5.5
* Mac Mini with external hard drive with 2 partitions, one of which is called "Time Machine", 10.5.5
What was working:
MacBook Air and MacBook would backup with Time Machine over wireless connection to .sparseimage files on the "Time Machine" volume connected to the Mac Mini.
Change:
Had to give the MacBook Air back to my old employer, so I "merged" the MacBook Air onto the MacBook (the merge was somewhat convoluted, and unrelated to my issue I think: I used SuperDuper to copy the MacBook Air hard drive onto a new SATA notebook drive. Then I installed that drive in the MacBook. Then I used Migration Assistant to copy the user from the original MacBook SATA drive onto the new drive in the MacBook. Now I have two users on the MacBook, whereas before I had one use on each of two computers).
Symptom:
Now I cannot use Time Machine to backup the MacBook to the "Time Machine" volume. Everything I've tried causes Time Machine to briefly "prepare" the backup, then return the error "The backup volume could not be found". Things I've tried:
* Mounting the volume "Time Machine" on the MacBook, under either user, works fine - I can write, read, and delete from the volume.
* Deleting the old .sparseimage backup files from the "Time Machine" volume.
* Erasing the "Time Machine" volume with Disk Utility on the Mac Mini.
* Using "Change Disk..." in Time Machine to re-select the volume "Time Machine"
* Using "Change Disk..." in Time Machine to select None, then restarting, then re-selecting the volume "Time Machine"
* Making the volume "Time Machine" read/write by guests, then connecting to it from the MacBook as a guest instead of as an admin user.
* Repairing permissions and/or repairing disks using Disk Utility on all applicable volumes.
* Tried all of the above under both users on the MacBook (both of whom are Admin users)
None of these things have worked, they all exhibit the same symptom when I manually start a time machine, or when I wait for Time Machine to automatically start the backup.
Any ideas of what I can try next?

Consider these reasons for this error...
*_"Backup Volume Could Not Be Found"_*
First, it is important to distinguish this error message from another, similar Time Machine error that states, “The backup volume could not be mounted”. This is important as the causes and cures for these two errors can be very different.
*Reselect Your Time Machine Disk*
(http://support.apple.com/kb/TS1329)
In the Finder, go up to the "Go" menu and select "Connect to Server".
Click the "Browse" button at the dialogue box.
In the Network window that opens, do you see your TM drive?
Double click it to mount the drive.
Now let's try to reselect it for Time Machine use.
Go to System Preferences --> Time Machine.
Click the "Change Disk..." button.
Select "None" and click "Stop Backing Up".
Now click "Choose Backup Disk" and reselect your drive again.
Close System Preferences and try backing-up again.
On the other hand, does your Time Machine drive NOT appear at all? Is it appearing on your desktop? If it is still connected try disconnecting the cable, waiting a few seconds and then reconnecting the cable. Does the drive mount on the desktop? Try initiating a backup now.
*Disk Fails to Wake From Sleep*
“If your external HD has a sleep function that does not wake for Time Machine backups. Time Machine will alert you that "The backup volume could not be found", and backups will not be made.” (http://support.apple.com/kb/TS1337)
*3rd-Party Disk Utilities* #
Many external hard disks come with software for maintaining/monitoring hard disk activities. It may have come on a separate CD or been installed on the drive itself. If these programs have been installed they may interfere with Time Machine backups, generate erratic behavior, or cause the drive to ‘disappear’ altogether.
You may never know these applications are there as they may be running in the background. Go to System preferences --> Accounts. Select your account in the pane on the left. Click “Login Items”. Are there any items listed there that might refer to hard disk utilities. If so remove them using the “-” button at the bottom.
*Time Capsule Has a Long Name*
“When using your Time Capsule for Time Machine backups in Mac OS X 10.5 Leopard or later, the Time Capsule backup volume may not mount and Time Machine may not be able to back up to it. This alert may appear: "Backup volume cannot be found". This can happen if the Time Capsule disk has a long name. [http://support.apple.com/kb/HT1170]
Open AirPort Utility (in /Applications/Utilities).
Click your Time Capsule's icon.
Click "Manual Setup".
Enter the password for the Time Capsule if prompted.
Click the Disks icon.
Highlight the volume name that appears under "Time Capsule Disk".
In the Name field, enter a name for the volume that is less than 27 characters long.
Click Update.
After Time Capsule restarts, on the Mac(s)using Time Machine, open Time Machine preferences and reselect the Time Capsule volume.”
Let us know if any of these suggestions help.
Cheers!
Message was edited by: Glenn Carter

All Shared Volumes Do Not Mount

Similar Messages

Maybe you are looking for