Time Capsule "Data" Volume won't Mount

I've been using a Time Capsule (4th Gen/2TB) for both my rMBP Time Machine backups and as a NAS device. After upgrading to Mountain Lion, I've experienced some problems. For the past few weeks, my Time Machine backups have been frequently interrupted with an error message stating that my Backup Disk is non-journaled and non-extended, and to please choose an alternate disk. Although unsettling, after pressing return - and upon connecting the power cord (as I opted only to backup when using the power cord), Time Machine has always propmtly resumed. This has probably occurred daily.
Today however, I've been unable to actually mount the Data volume, although my network is functioning properly, and I can access the Internet. The Time Capsule status indicator is green, its icon appears in the Finder sidebar, and Airport Utility recognizes it and displays its correct settings. Upon trying to connect (via Finder), however, an error message states that the server (in this case, the Time Capsule, I guess) can't be located, and suggets I check my network settings and try again. Needless to say, the settings appear fine.
An admittedly brief search within this forum yielded no discussions concerning this specific problem, but I'm hoping the community's more knowledgable members will be able to at least provide some helpful insights, if not a solution to this problem.
The inability to back up my rMBP, access my spasebundle, or manage my externally stored files is very disconcerting. Any solutions, or insights regarding this issue will be gratefully received.
Michael Henke

There is clearly a bug in Lion that was exacerbated in Mountain Lion, which Apple is yet to fess up to. This loss of connection happens and there is no fix I can give you other than reboot to get the network running again.
I would strongly recommend against using the TC as a NAS.. it is designed as a backup target for Time Machine.
If you want a NAS then buy a true NAS, synology or Qnap, being the top products in that field. They have raid and automatic backup with units where you can access hard disks and can replace them. TC is a sealed unit without any way to back itself up. The design was never as a NAS.
Since your TC is an older one, can you try running 7.5.2 firmware. None of the TC made in the last year or more can go back that far.. they are all stuck on 7.6, the earlier Gen4 did have 7.5.2 which I think has better stability..
Now exactly what issues come up with ML I am not sure, but I would be interested to hear your experience.
Please do a backup particularly of your itunes before you start fiddling.
Is the TC main router in the network or is it bridged? I have a few suggestions for each type of setup, which may keep it running longer.. but nothing is absolute fix.
Note also the TC seems to be the main problem device.. but the OS does still have issues.. some changes were made with AFP security at Lion, which have not worked very well.

Similar Messages

My Airport Extreme and Time Capsule both cannot do not mount my Seagate USB external hard.

My Airport Extreme and Time Capsule both cannot do not mount my Seagate USB external hard.
I am running OS 10.7.5
Both the TC and AE are updated to 7.6.1
The Seagate drive in formatted: Journaled HFS+
I tried everything on Apple's Article: HT1331 and the basic reboots and restarts.
"Next"

It sounds like you may be confusing "mount" with "recognize".
Connect the drive to the USB port on the AirPort Extreme
Open Macintosh HD > Applications > Utilities > AirPort Utility
Click on the AirPort Extreme icon, then click Edit
Click the Disks tab
Does the AirPort Extreme "recognize" your hard drive? If yes, it will be displayed in the window.
See example below of a WD 500 GB drive connected to the AirPort Extreme.
If your drive is formatted HFS+ and it does not appear here, then you will almost certainly need to use a powered USB hub with the hard drive.....even if the hard drive has its own power supply. The USB port on the AirPort Extreme and Time Capsule is under powered.
Post back when the drive is "recognized" and we will next "mount" the drive.....although you likely already know how to do this.

Replacing an Airport Express with a Time Capsule but it won't connect to the internet.

Hello, I hope somebody can help.
I am trying to replace an Airport Express with a 2TB Time Capsule but it won't connect to the internet, via an ADSL modem.
I have tried everything I can think of, powering down all devices, re-setting all devices, but nothing seems to solve the problem.
When I first tried to set up the Time Capsule, there was an option to replace the Airport Express using the same settings.
But there were repeated error messages of 'No DNS Servers' and 'PPPoE server couldn't be found'.
I also had messages that the password for PPPoE wasn't correct, but when I plug the Airport Express back in again, everything works fine.
What could the problem be?

99% of issues with authentication are wrong password or wrong username.. eg it can be strange like the user name is missing the domain.. whereas the Airport Express works fine without it.
Ring your ISP and make doubly sure you have exactly the correct username and password.
If it still doesn't work, put the adsl modem back into router mode and try it again directly on the modem.. if it works ok on the modem but fails on the TC that is possible and can be caused by pppoe client using incorrect authentication type, CHAP or PAP which the TC does not allow you to select AFAIK.. some ISP do not give enough time to get the router to switch on auto to the correct authentication method.
In the end run the modem as router and bridge the TC. It will work just as well for most installations in bridge as the modem in bridge.

Is it possible to sync time capsule data to a external hard drive

Is it possible to sync time capsule data to a external hard drive connected to time capsule via usb. (as an precaution just incase time capsule fails)
Thanks

Yes, if the USB drive has been previously formatted correctly in Mac OS Extended (Journaled) format.
Open AirPort Utility - Click Manual Setup
Click the Disks icon
Click the Disks tab below the icon
Click Archive
Allow plenty of time for the copy process to occur. You will not be able to make Time Machine backups from your Mac until the Archive process has completed.

How can I move (copy) my Time Capsule date to a new 2T hard drive and then wipe the TC and start as a new (clean) Time MACHINE backup?

How can I move (copy) my Time Capsule date to a new 2T hard drive and then wipe the TC and start as a new (clean) Time MACHINE backup?

Just use the archive utility on the disk page of the airport utility manual setup..
If you have lion and v6 airport utility.. it missed out. On lots of things.
Download and install the real.. UTILITY
5.6 http://support.apple.com/kb/DL1482

WD mycloud fehler 004 : Data volume failed to mount

Hallo, Seit einiger zeit habe ich nurnoch eine rote LED und kein zugriff auf meine WD Mycloud 2TB ins Mycloud daschboard komme ich noch sporadisch. zeigt aber fehler 004 Haupsächlich hatte ich die mycloud als speicher für fotos genutzt, die natürlich nirgendwo anderst gespeichert sindKomme ich irgendwie wieder an meine Fotos ?? DankeMatthias

Hast Du mal über das Dashboard "nur System" auf Werkseinstellungen zurück gesetzt? Wenn es dann icht geht, kannst Du den Support kontaktieren. Die werden Dir aber vermutlich nicht dabei helfen Deine Daten wiederzubekommen, sondern bestenfalls ein neues/repariertes Gerät ohne Deine Daten senden. Ansonsten hatte hier jemand das gleiche Problem lösen können:http://community.wd.com/t5/WD-My-Cloud/Data-volume-failed-to-mount/td-p/631497Versuchen kannst Du es: This is "my" solution, may not work for everyone. But it would seem that datablocks would corrupt when power is abruptly cut to the drive. SSH must be enabled for this to work. 1. Log onto the drive, root and welc0me are the default username/password combo.2. Make sure your paritions are intact. # parted -l will tell you this.3. Type # mke2fs -n /dev/sda4. This will get you the filesystem, but more importantly at the end give you the superblock backup locations by block location.4. Pick one, then enter this command. e2fsck -b blocknumber /dev/sda4 It will look for bad blocks and ask for your confirmation to continue/ignore then write over any corrupted ones. Yes to ignore, yes to rewrite. It will do up to five passes of diagnostics, prompting if it finds anything out of the ordinary such as file countes and errant inodes. I answered yes to everything. When it is complete it will either report "Killed" or a summary. Type # reboot and let the drive rebuild its library. 30-ish minutes later (depending on how much data you had on it) you should have access to your files.

How do I transfer time capsul data to external hard drive to free up space?

How do I transfer time capsule data to external hard drive to free up space?

The fastest method is straight copy and paste..
Plug a suitable hard disk into your computer.. format it Mac OS extended journaled (if not already).
Select the folders/files you want to move.. copy and paste them to the external drive..
Double check that the files are copied because the next step will delete the files forever.. there is no trash on the TC.
Delete the files on the TC.
You can also do a full archive of the TC disk to a USB plugged into it by USB.. it must be formatted Mac OS Extended Journaled. It must be big enough to hold all data on the TC disk.. best idea is to buy the same size or bigger.. so if you use 2TB TC buy a 2TB or bigger external drive.
In airport utility select archive.
That will copy everything on the TC disk to the USB drive.. you could then Erase the disk of the TC.. this is super fast if you choose quick erase.. just a few minutes. But the archive will take many hours.. say for 2TB about 12-24hours.. and you cannot use the disk in the TC during that time.

Problems accessing time capsule data "The operation can't be completed because the original [...]"

So as my title would suggest, I'm having time capsule issues.
First of all, I'm running a MBPret late 2013. Currently I'm trying to setup my time capsule in my university dorm room for two reasons:
1) I want to use the internet they provide us.
2) I want to use time capsule as a backup drive.
I am not permitted to use wifi as per my contract with the university, unfortunate, but fine, I can use ethernet, I have the ethernet -> thunderbolt adapter.
Now, thus far, I've setup my time capsule normally (this is second setup not the first) and I performed a hard reset before connecting it all here. Before here it was setup at my previous house. After that I disabled the wireless and enabled secure shared disks "with device password".
I don't have internet access yet, though I believe this is a problem on the administrator side not mine, but the real problem is that I cannot access the data folder on my time capsule in finder. I've tried erasing the volume, hard resetting and setting up again, I keep getting the same error message:
"The operation can’t be completed because the original item for "Data" can't be found"
Any suggestions?
Regards

If you don't have applecare you will need to pay if you want the genuine article but your problem is familiar and Apple support is likely to say your the first person they have ever heard of with this problem.. even when every second post here refers to it.
Here is my standard list. Work through it and tell me if you succeed.
The cause is Yosemite btw.
A factory reset of the TC is the start.. it is required so you can find it again.
Factory reset universal
Power off the TC.. ie pull the power cord or power off at the wall.. wait 10sec.. hold in the reset button.. be gentle.. power on again still holding in reset.. and keep holding it in for another 10sec. You may need some help as it is hard to both hold in reset and apply power. It will show success by rapidly blinking the front led. Release the reset.. and wait a couple of min for the TC to reset and come back with factory settings. If the front LED doesn’t blink rapidly you missed it and simply try again. The reset is fairly fragile in these.. press it so you feel it just click and no more.. I have seen people bend the lever or even break it. I use a toothpick as tool.
N.B. None of your files on the hard disk of the TC are deleted.. this simply clears out the router settings of the TC.
Setup the TC again.
ie Start from a factory reset. No files are lost on the hard disk doing this.
Then redo the setup from the computer with Yosemite.
1. Use very short names.. NOT APPLE RECOMMENDED names. No spaces and pure alphanumerics.
eg TCgen5 and TCwifi for basestation and wireless respectively.
Even better if the issue is more wireless use TC24ghz and TC5ghz with fixed channels as this also seems to help stop the nonsense. But this can be tried in the second round.
2. Use all passwords that also comply but can be a bit longer. ie 8-20 characters mixed case and numbers.. no non-alphanumerics.
3. Ensure the TC always takes the same IP address.. you will need to do this on the main router using dhcp reservation.. or a bit more complex setup using static IP in the TC. But this is important.. having IP drift all over the place when Yosemite cannot remember its own name for 5 min after a reboot makes for poor networking. If the TC is main router it will not be an issue.
4. Check your share name on the computer is not changing.. make sure it also complies with the above.. short no spaces and pure alphanumeric.. but this change will mess up your TM backup.. so be prepared to do a new full backup. Sorry.. keep this one for second round if you want to avoid a new backup.
5. Mount the TC disk in the computer manually.
In Finder, Go, Connect to server from the top menu,
Type in SMB://192.168.0.254 (or whatever the TC ip is which you have now made static. As a router by default it is 10.0.1.1 and I encourage people to stick with that unless you know what you are doing).
You can use name.. SMB://TCgen5.local where you replace TCgen5 with your TC name.. local is the default domain of the TC and doesn't change.
However names are not so easy as IP address.. nor as reliable. At least not in Yosemite they aren't. The domain can also be an issue if you are not plugged or wireless directly to the TC.
6. Make sure IPv6 is set to link-local only in the computer. For example wireless open the network preferences, wireless and advanced / TCP/IP.. and fix the IPv6. to link-local only.
There is a lot more jiggery pokery you can try but the above is a good start.. if you find it still unreliable.. don't be surprised.
You might need to do some more work on the laptop itself. eg Reset the PRAM.. has helped some people. Clean install of the OS is also helpful if you upgrade installed.
Tell us how you go.
Someone posted a solution.. See this thread.
Macbook can't find Time Capsule anymore
Start from the bottom and work up.. I have a list of good network practice changes but I have avoided Yosemites bug heaven.
This user has had success and a few others as well.
RáNdÓm GéÉzÁ
Yosemite has serious DNS bug in the networking application.. here is the lets say more arcane method of fixing it by doing a network transplant from mavericks.
http://arstechnica.com/apple/2015/01/why-dns-in-os-x-10-10-is-broken-and-what-yo u-can-do-to-fix-it/

Can't connect to old Time Capsule data after installing Lion

I recently installed Lion, and when I set up Time Machine to my old Time Capsule I've been using since TCs were released, and the software only shows data as if I've never backed up before, as well as saying "Oldest Backup" and "Latest Backup" as "none." I have used this TC through Leopard and Snow Leopard, and there is lots of old backups on the drive. The TC storage amount shows 91 of 500 GB available, so I know my data is still there. I need TM to recognize the old backup data on the TC so I can access some old backups I have. Please help if anyone knows what to do here!

Mount the "Data" volume of the Time Capsule and look at the dates of the "sparsebundle" files there. If there seem to be two there for your MacBook Pro, then your old data is still there in the older backup. To see that data, click-and-hold or control-click on the Time Machine icon and select "Browse Other Time Machine Disks".

Can I copy time capsule data and use new external HD

Hi All-
I've been scouring the net and cant seem to find an answer. Hopefully someone here can help.
I have a Time Capsule that is nearly filled. It is giving me error messages each night it tries to backup saying that there is too much on my computer to backup.
So, I went out and bought a 4TB Western Digital external drive. I want to copy all the data from the time capsule onto the new hard drive (so I dont loose any of my older backups) and then have the time capsule use that same WD drive as my new backup.
I have seen there are ways to copy from time machine drives to new drives, but I was under the impression time machine uses a different kind of backup method than a time capsule. Is that true? Can someone point me to a place that explains how exactly I would copy the drive in the time capsule... (I understand I need to use Disk Util, but I cant get the TC drive to show up in that program)...
Also, is there a way to instruct time capsule to stop using its own internal drive and use the drive connected to its USB for the backups? I think Apple's answer is no, but I dont know if thats really the case or not...
Thanks much-
Daber

David Bertman wrote:
The backup was via an ethernet cable from the mac to the TC. (I also have it set up to run via wifi. Would that affect things?) Would there be different symptoms if the backup had stalled midway through?
Just trying to rule out a bad WIFI connection, and it will be much faster via Ethernet.
I didnt repair the backups first (I'm not really sure how to do that --- is it through disk utils and repair permissions like a normal drive?) I get nervous messing around with the "Backups.backupdb" files so I generally leave them alone.
Close. It's +*repair disk+*, not permissions. See #A5 in Time Machine - Troubleshooting (or use the link in *User Tips* at the top of this forum), for a brief explanation and instructions.
If the backups on the TC were corrupted, that would have been copied to the external HD, potentially causing Time Machine to start a new set.
But, I did enter time machine and saw that the old backups were there (and when I did your other suggestion of going to the browse option, it now shows two identically named backups -- one from the original TV and one from the new 4tb drive. But when I enter each they are separate backups -- the original one with the older backups and the new one with the single 1 day backup.
That confirms it -- for whatever reason, Time Machine started a new set.
You asked if there were two sparce bundles... I dont see any sparce bundles. I'm ONLY seeing the "backup.backups" folders when I mount the drives... Should I be seeing sparce bundles? Could that be an issue?
The Backups.backupdb folder should be inside a sparse bundle named the same as your computer. All backups done over a network (via Ethernet or WIFI) are done that way; those done to a locally-connected drive have that folder at the top level of the drive.
If you look at the external HD via the Finder, you'll see them; if you then double-click either, it will mount, and you can see the Backups.backupdb folder inside it. And you're right; be +*very careful+* not to move, change, or delete anything there.
I'd suggest this: Turn Time Machine off, and use Airport Utility to disconnect the external from the TC (start Airport Utility, click +Manual Setup,+ then Disks in the toolbar, then +Disconnect all Users.+ Each user will then get a message).
Then connect the external directly to your Mac. Repair the old sparse bundle, per #A5 (it will take a long time, but be much faster this way). If it has errors that Disk Utility can't fix, see the pink box in #A5.
If there are no problems, or they're fixed, delete the new sparse bundle via the Finder. That may take a while. Then eject the disk, reconnect it to the Time Capsule, and do a "full reset" per #A4 in Troubleshooting. Then re-select the external as your TM volume, and start a backup. Open the external disk via the Finder; if Time Machine again creates a new sparse bundle, you're pretty much stuck with it making a separate set of backups.

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.

Multiple Users Can't Access Time Capsule Data

My wife and I have two separate Apple MacBooks that share a Time Capsule. We have different account names on these respective computers. I initially set up my Time Capsule and created folders that I can access from Finder.app when I connect over our wireless network. In Airport Utility.app, under the "Disks" tab, I set up the shared disks "with device password", so that she and I can mutually access all the data on the Time Capsule. However, when I try to access it from her computer, I click on the Time Capsule in Finder.app and get this dumb Sharepoint icon--a total dead end. I created another account on her computer with the same name as the account on my own computer, and from that account, I'm able to access all of the data on the Time Capsule. This therefore seems to be a permissions issue, but I've checked all of the files and folders on the Time Capsule and ensured that they all have "everyone read & write" access, so there should be no restrictions on access to this data.
Why are the volumes on my Time Capsule sensitive to the user accessing them? How do I set up data repositories on the Time Capsule that can be accessible to all users on my network? I'm out of ideas.

Are both computers actually running Mavericks??
This is very typical Yosemite problem.
For some reason which I don't yet understand Yosemite is horrible at handling network drives.
dumb Sharepoint icon
Sharepoint is a dlink app?? If you have ever had some app loaded that uses a different product to apple then it can mess your access.
WD share stuff seems to be the worst and causes no end of problems.
What you are seeing btw is the TC is not a NAS.. you are trying to use it as one.. but it isn't.

Airport Extreme/Time Capsule backup volume could not be found?

I am having problem with Time Machine. When I try to backup using Time Machine, I get an error message, " The backup volume could not be found." Strangely, Time Machine recognized the drive when setting the Time Machine preferences, but not when I backup.
If i select from the 'select disk' again and try again i get Keychain Access error 25299 and have to delete that in the Keychain for it to even get to the point of counting down to start back up
I have erased my Time Capsule recently and was starting fresh but now i cannot get time machine running again...
In the shared section of the finder the time machine backup is only appearing in the network area rather than directly there...
Any ideas?
Many thanks.

Hi there.
I would suggest First Aid of your Keychain, but that hardly ever works (especially in this situation).
What I would do first, is go to ~/Library/Keychains/, grab the login.keychain and move it to the desktop. Log out, and log back in again. If that fixes it, then get the old login.keychain from the desktop and put it in the trash. (You will lose all your saved passwords for networks etc.)
If that doesn't work, unfortunately the only option would be to do an Archive & Install.
So you just need to put your 10.6 disk in again and install over the system.
Your personal data/files should still remain intact. Although I would still suggest making a backup (ironic considering the situation)
Cheers
Taylor

Time capsule data unaccessible

Hello,
I have a time capulse Apple 2TB Time Capsule 802.11n Wi-Fi Hard Drive MB996LL/A Model A1302 Dual Band.
I connected this to my Macbook via ethernet cable (WAN -> LAN connection) and the LED light turns on saying the connection has been established. I can see the disk in my Finder and when I access it there is one folder called "Time Capsule". This has all my data (movies/music/time machine backup etc.) but when I click on the folder to access it, the finder closes and I get a message saying the Time Capsule folder doesn't exist.
The weird thing is, I've setup my time machine to backup to the time capsule and it runs fine - I get hourly time machine backups without any issues. I accessed Time machine and can see and select my Time Capsule disk. So, the time capsule is there but for some reason I can't access any of my data...
Any thoughts? I have disabled the Wifi option on the time capsule...essentially just making it a external harddrive that I have connected to my macbook via ethernet cable (as mentioned earlier)
Thanks,
Sud

1st question.. no.. the default is auto and Yosemite gets it wrong constantly.
You have to manually set it to link-local only.
2nd question.. has your TC been running ok since Yosemite.. that is Oct last year or something.. if this only started recently on the Mac then it is more likely the patch to 10.10.2
Here is the standard set of instructions. Having issues with Yosemite.. no big surprise.. but windows at the same time.. suggest you have a hardware problem.. perhaps.. not just software.. a Gen2 TC is old man. I would be more inclined to be looking at replacement.. anyway here is where I would start.
A factory reset of the TC is the start.. it is required so you can find it again.
Factory reset universal
Power off the TC.. ie pull the power cord or power off at the wall.. wait 10sec.. hold in the reset button.. be gentle.. power on again still holding in reset.. and keep holding it in for another 10sec. You may need some help as it is hard to both hold in reset and apply power. It will show success by rapidly blinking the front led. Release the reset.. and wait a couple of min for the TC to reset and come back with factory settings. If the front LED doesn’t blink rapidly you missed it and simply try again. The reset is fairly fragile in these.. press it so you feel it just click and no more.. I have seen people bend the lever or even break it. I use a toothpick as tool.
N.B. None of your files on the hard disk of the TC are deleted.. this simply clears out the router settings of the TC.
Setup the TC again.
ie Start from a factory reset. No files are lost on the hard disk doing this.
Then redo the setup from the computer with Yosemite.
1. Use very short names.. NOT APPLE RECOMMENDED names. No spaces and pure alphanumerics.
eg TCgen5 and TCwifi for basestation and wireless respectively.
Even better if the issue is more wireless use TC24ghz and TC5ghz with fixed channels as this also seems to help stop the nonsense. But this can be tried in the second round.
2. Use all passwords that also comply but can be a bit longer. ie 8-20 characters mixed case and numbers.. no non-alphanumerics.
3. Ensure the TC always takes the same IP address.. you will need to do this on the main router using dhcp reservation.. or a bit more complex setup using static IP in the TC. But this is important.. having IP drift all over the place when Yosemite cannot remember its own name for 5 min after a reboot makes for poor networking. If the TC is main router it will not be an issue.
4. Check your share name on the computer is not changing.. make sure it also complies with the above.. short no spaces and pure alphanumeric.. but this change will mess up your TM backup.. so be prepared to do a new full backup. Sorry.. keep this one for second round if you want to avoid a new backup.
5. Mount the TC disk in the computer manually.
In Finder, Go, Connect to server from the top menu,
Type in SMB://192.168.0.254 (or whatever the TC ip is which you have now made static. As a router by default it is 10.0.1.1 and I encourage people to stick with that unless you know what you are doing).
You can use name.. SMB://TCgen5.local where you replace TCgen5 with your TC name.. local is the default domain of the TC and doesn't change.
However names are not so easy as IP address.. nor as reliable. At least not in Yosemite they aren't. The domain can also be an issue if you are not plugged or wireless directly to the TC.
6. Make sure IPv6 is set to link-local only in the computer. For example wireless open the network preferences, wireless and advanced / TCP/IP.. and fix the IPv6. to link-local only.
There is a lot more jiggery pokery you can try but the above is a good start.. if you find it still unreliable.. don't be surprised.
You might need to do some more work on the laptop itself. eg Reset the PRAM.. has helped some people. Clean install of the OS is also helpful if you upgrade installed.
Tell us how you go.
Someone posted a solution.. See this thread.
Macbook can't find Time Capsule anymore
Start from the bottom and work up.. I have a list of good network practice changes but I have avoided Yosemites bug heaven.
This user has had success and a few others as well.

Volume won't mount - xsanctl returns error 5

Dear List,
One of our Volumes has failed to remount following scheduled software updates and cvfsck disk utility run. PromiseGroups, the problem volume starts, shows up in cvadmin and the GUI but won't mount either through the GUI or CLI.
Recent filtered fsmpm Log displays the following:
713 17:37:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:38:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:39:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:40:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:41:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:42:40] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:43:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:44:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:45:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:46:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:47:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:48:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:49:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:50:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:51:36] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:52:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:53:36] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:54:11] 0xa033f720 (debug) NSS: FSS mount list for client 10.0.0.8 (id 129.11.67.18) - Promise1, XRAIDScratch, Promise2, PromiseGroups
[0713 17:54:13] 0xa033f720 INFO NSS: Vote call for FSS PromiseGroups is inhibited - vote dis-allowed.
[0713 17:54:19] 0xa033f720 NOTICE PortMapper: FSS 'PromiseGroups' disconnected.
[0713 17:54:19] 0xa033f720 (debug) FSS 'PromiseGroups' REGISTERED -> DYING, next event in 60s
[0713 17:54:19] 0xa033f720 INFO NSS: Vote call for FSS PromiseGroups is inhibited - vote dis-allowed.
[0713 17:54:19] 0xb040f000 (debug) Portmapper: FSS 'PromiseGroups' (pid 6192) exited with status 18 (transient error)
[0713 17:54:19] 0xb040f000 (debug) FSS 'PromiseGroups' DYING -> RELAUNCH, next event in 10s
[0713 17:54:19] 0xa033f720 INFO NSS: Active FSS 'PromiseGroups[1]' at 129.11.67.19:55742 (pid 6192) - dropped.
[0713 17:54:19] 0xa033f720 (debug) NSS: removing vote inhibitor for FSS 'PromiseGroups'.
[0713 17:54:23] 0xa033f720 INFO NSS: Vote call for FSS PromiseGroups is inhibited - vote dis-allowed.
[0713 17:54:28] 0xb040f000 (debug) FSS 'PromiseGroups' RELAUNCH -> LAUNCHED, next event in 60s
[0713 17:54:28] 0xb040f000 NOTICE PortMapper: RESTART FSS service 'PromiseGroups[1]' on host xsanmdp.leeds.ac.uk.
[0713 17:54:28] 0xb040f000 NOTICE PortMapper: Starting FSS service 'PromiseGroups[1]' on xsanmdp.leeds.ac.uk.
[0713 17:54:28] 0xa033f720 (debug) FSS 'PromiseGroups' LAUNCHED -> REGISTERED
[0713 17:54:28] 0xa033f720 NOTICE PortMapper: FSS 'PromiseGroups'[1] (pid 7545) at port 63518 is registered.
[0713 17:54:29] 0xa033f720 INFO NSS: Standby FSS 'PromiseGroups[1]' at id 129.11.67.19 port 63518 (pid 7545) - registered.
[0713 17:54:29] 0xa033f720 (debug) Heartbeat from ID 129.11.67.19 updating LOCAL PromiseGroups to 10.0.0.9:63518
[0713 17:54:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:55:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:56:16] 0xa033f720 INFO NSS: Starting vote for FSS PromiseGroups using 1 voting member: 129.11.67.19.
[0713 17:56:18] 0xa033f720 (debug) localfssvote: WINNER PromiseGroups at 10.0.0.9:63518.
[0713 17:56:18] 0xa033f720 (debug) tally_member:FSS/PromiseGroups COUNTED 0 vote for 10.0.0.8:60597 from member 129.11.67.19:49153
[0713 17:56:18] 0xa033f720 (debug) tally_member:FSS/PromiseGroups COUNTED 1 vote for 10.0.0.9:63518 from member 129.11.67.19:49153
[0713 17:56:18] 0xa033f720 INFO NSS: Vote selected FSS 'PromiseGroups[1]' at 10.0.0.9:63518 (pid 7545) - attempting activation.
[0713 17:56:18] 0xa033f720 INFO NSS: Vote call for FSS PromiseGroups is inhibited - vote dis-allowed.
[0713 17:56:23] 0xa033f720 NOTICE PortMapper: FSS 'PromiseGroups' disconnected.
[0713 17:56:23] 0xa033f720 (debug) FSS 'PromiseGroups' REGISTERED -> DYING, next event in 60s
[0713 17:56:23] 0xb040f000 (debug) Portmapper: FSS 'PromiseGroups' (pid 7545) exited with status 18 (transient error)
[0713 17:56:23] 0xb040f000 (debug) FSS 'PromiseGroups' DYING -> RELAUNCH, next event in 10s
[0713 17:56:24] 0xa033f720 INFO NSS: Active FSS 'PromiseGroups[1]' at 129.11.67.19:63518 (pid 7545) - dropped.
[0713 17:56:24] 0xa033f720 (debug) NSS: removing vote inhibitor for FSS 'PromiseGroups'.
[0713 17:56:33] 0xb040f000 (debug) FSS 'PromiseGroups' RELAUNCH -> LAUNCHED, next event in 60s
[0713 17:56:33] 0xb040f000 NOTICE PortMapper: RESTART FSS service 'PromiseGroups[1]' on host xsanmdp.leeds.ac.uk.
[0713 17:56:33] 0xb040f000 NOTICE PortMapper: Starting FSS service 'PromiseGroups[1]' on xsanmdp.leeds.ac.uk.
[0713 17:56:33] 0xa033f720 (debug) FSS 'PromiseGroups' LAUNCHED -> REGISTERED
[0713 17:56:33] 0xa033f720 NOTICE PortMapper: FSS 'PromiseGroups'[1] (pid 7563) at port 63713 is registered.
[0713 17:56:34] 0xa033f720 INFO NSS: Standby FSS 'PromiseGroups[1]' at id 129.11.67.19 port 63713 (pid 7563) - registered.
[0713 17:56:34] 0xa033f720 (debug) Heartbeat from ID 129.11.67.19 updating LOCAL PromiseGroups to 10.0.0.9:63713
[0713 17:56:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:57:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:58:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:59:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:00:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:01:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:02:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:03:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:04:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:05:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:06:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:07:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:08:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:09:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:10:36] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:11:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:12:40] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:13:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:14:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:15:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:16:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:17:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:18:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:19:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:20:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:21:36] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:22:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:23:36] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:24:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:25:36] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:26:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:27:36] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:28:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
Does anyone have a fix for this problem?
Geoff Cross - Systems Administrator (Macintosh)
 Apple Certified XSAN 2 Administrator • BakBone NetVault Certified Administrator
 ACTC 10.6  ACSP 10.6  ACS Deployment, Security & Mobility
Sections of Oncology and Biostatistics and Epidemiology
Leeds Institute of Molecular Medicine, Cancer Research UK Centre
Wellcome Trust Brenner Building, St James's University Hospital
Beckett Street, Leeds LS9 7TF

Here is system.log:
(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:38:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:38:42: --- last message repeated 1 time ---
Jul 30 09:38:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:39:43 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:39:43: --- last message repeated 1 time ---
Jul 30 09:39:43 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:40:12 xsanmdp mDNSResponder[31]: ERROR: getOptRdata - unknown opt 4
Jul 30 09:40:42: --- last message repeated 8 times ---
Jul 30 09:40:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:40:42: --- last message repeated 1 time ---
Jul 30 09:40:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:40:48 xsanmdp mDNSResponder[31]: ERROR: getOptRdata - unknown opt 4
Jul 30 09:41:18: --- last message repeated 11 times ---
Jul 30 09:41:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:41:42: --- last message repeated 1 time ---
Jul 30 09:41:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:42:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:42:42: --- last message repeated 1 time ---
Jul 30 09:42:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:43:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:43:42: --- last message repeated 1 time ---
Jul 30 09:43:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:44:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:44:42: --- last message repeated 1 time ---
Jul 30 09:44:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:45:47 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:45:47: --- last message repeated 1 time ---
Jul 30 09:45:47 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:46:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:46:43: --- last message repeated 1 time ---
Jul 30 09:46:43 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:47:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:47:42: --- last message repeated 1 time ---
Jul 30 09:47:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:48:43 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:48:43: --- last message repeated 1 time ---
Jul 30 09:48:43 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:49:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:49:42: --- last message repeated 1 time ---
Jul 30 09:49:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:50:43 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:50:43: --- last message repeated 1 time ---
Jul 30 09:50:43 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:51:02 xsanmdp mDNSResponder[31]: ERROR: getOptRdata - unknown opt 4
Jul 30 09:51:32: --- last message repeated 19 times ---
Jul 30 09:51:32 xsanmdp mDNSResponder[31]: ERROR: getOptRdata - unknown opt 4
Jul 30 09:51:42: --- last message repeated 2 times ---
Jul 30 09:51:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:51:42: --- last message repeated 1 time ---
Jul 30 09:51:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:51:43 xsanmdp mDNSResponder[31]: ERROR: getOptRdata - unknown opt 4
Jul 30 09:52:13: --- last message repeated 2 times ---
Jul 30 09:52:43 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:52:43: --- last message repeated 1 time ---
Jul 30 09:52:43 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:53:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:53:42: --- last message repeated 1 time ---
Jul 30 09:53:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:54:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:54:42: --- last message repeated 1 time ---
Jul 30 09:54:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:55:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:55:42: --- last message repeated 1 time ---
Jul 30 09:55:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:56:23 xsanmdp mDNSResponder[31]: ERROR: getOptRdata - unknown opt 4
Jul 30 09:56:42: --- last message repeated 6 times ---
Jul 30 09:56:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:56:42: --- last message repeated 1 time ---
Jul 30 09:56:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:56:53 xsanmdp mDNSResponder[31]: ERROR: getOptRdata - unknown opt 4
Jul 30 09:57:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:57:43: --- last message repeated 1 time ---
Jul 30 09:57:43 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:58:35 xsanmdp servermgrd[99274]: xsan: [99274/2425EA0] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:58:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:58:42: --- last message repeated 1 time ---
Jul 30 09:58:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Cheers, Geoff

Time Capsule "Data" Volume won't Mount

Similar Messages

Maybe you are looking for