TIme Capsule stopped working after 10.10.3

Now, after upgrading to 10.10.3 in a fruitless belief that it would speed up things, I can no longer do a backup with Time Capsule. I have followed all the hints left about deleting old time capsule config files but to no avail. Tried to run disk utility on it but the drive does not show up under disk utility. The backup runs for a period of time then fails.

Ok thanks. Here is the appropriate part of the log file:
4/13/15 2:15:03.000 PM syslogd[41]: Configuration Notice:
ASL Module "com.apple.AccountPolicyHelper" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
4/13/15 2:15:03.000 PM syslogd[41]: Configuration Notice:
ASL Module "com.apple.authd" sharing output destination "/var/log/asl" with ASL Module "com.apple.asl".
Output parameters from ASL Module "com.apple.asl" override any specified in ASL Module "com.apple.authd".
4/13/15 2:15:03.000 PM syslogd[41]: Configuration Notice:
ASL Module "com.apple.authd" sharing output destination "/var/log/system.log" with ASL Module "com.apple.asl".
Output parameters from ASL Module "com.apple.asl" override any specified in ASL Module "com.apple.authd".
4/13/15 2:15:03.000 PM syslogd[41]: Configuration Notice:
ASL Module "com.apple.authd" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
4/13/15 2:15:03.000 PM syslogd[41]: Configuration Notice:
ASL Module "com.apple.awdd" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
4/13/15 2:15:03.000 PM syslogd[41]: Configuration Notice:
ASL Module "com.apple.callhistory.asl.conf" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
4/13/15 2:15:03.000 PM syslogd[41]: Configuration Notice:
ASL Module "com.apple.cloudd" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
4/13/15 2:15:03.000 PM syslogd[41]: Configuration Notice:
ASL Module "com.apple.clouddocs" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
4/13/15 2:15:03.000 PM syslogd[41]: Configuration Notice:
ASL Module "com.apple.commerce.asl" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
4/13/15 2:15:03.000 PM syslogd[41]: Configuration Notice:
ASL Module "com.apple.CoreDuetAdmissionControl" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
4/13/15 2:15:03.000 PM syslogd[41]: Configuration Notice:
ASL Module "com.apple.eventmonitor" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
4/13/15 2:15:03.000 PM syslogd[41]: Configuration Notice:
ASL Module "com.apple.family.asl" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
4/13/15 2:15:03.000 PM syslogd[41]: Configuration Notice:
ASL Module "com.apple.ical" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
4/13/15 2:15:03.000 PM syslogd[41]: Configuration Notice:
ASL Module "com.apple.icloud.FindMyDevice" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
4/13/15 2:15:03.000 PM syslogd[41]: Configuration Notice:
ASL Module "com.apple.install" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
4/13/15 2:15:03.000 PM syslogd[41]: Configuration Notice:
ASL Module "com.apple.iokit.power" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
4/13/15 2:15:03.000 PM syslogd[41]: Configuration Notice:
ASL Module "com.apple.mail" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
4/13/15 2:15:03.000 PM syslogd[41]: Configuration Notice:
ASL Module "com.apple.MessageTracer" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
4/13/15 2:15:03.000 PM syslogd[41]: Configuration Notice:
ASL Module "com.apple.networking.symptoms" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
4/13/15 2:15:03.000 PM syslogd[41]: Configuration Notice:
ASL Module "com.apple.networking.symptoms" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
4/13/15 2:15:03.000 PM syslogd[41]: Configuration Notice:
ASL Module "com.apple.performance" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
4/13/15 2:15:03.000 PM syslogd[41]: Configuration Notice:
ASL Module "com.apple.sandbox.telemetry" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
4/13/15 2:15:03.000 PM syslogd[41]: Configuration Notice:
ASL Module "com.apple.secinitd" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
4/13/15 2:15:03.000 PM syslogd[41]: Configuration Notice:
ASL Module "com.apple.securityd" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
4/13/15 2:15:03.000 PM syslogd[41]: Configuration Notice:
ASL Module "com.apple.securityd" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
4/13/15 2:15:03.000 PM syslogd[41]: Configuration Notice:
ASL Module "com.apple.securityd" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
4/13/15 2:15:03.000 PM syslogd[41]: Configuration Notice:
ASL Module "com.apple.securityd" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
4/13/15 2:15:03.000 PM syslogd[41]: Configuration Notice:
ASL Module "com.apple.securityd" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
4/13/15 2:15:03.000 PM syslogd[41]: Configuration Notice:
ASL Module "com.apple.securityd" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
4/13/15 2:15:03.000 PM syslogd[41]: Configuration Notice:
ASL Module "com.apple.securityd" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
4/13/15 2:15:03.000 PM kernel[0]: Longterm timer threshold: 1000 ms
4/13/15 2:15:03.000 PM kernel[0]: Darwin Kernel Version 14.3.0: Mon Mar 23 11:59:05 PDT 2015; root:xnu-2782.20.48~5/RELEASE_X86_64
4/13/15 2:15:03.000 PM kernel[0]: vm_page_bootstrap: 910220 free pages and 130164 wired pages
4/13/15 2:15:03.000 PM kernel[0]: kext submap [0xffffff7f80a00000 - 0xffffff8000000000], kernel text [0xffffff8000200000 - 0xffffff8000a00000]
4/13/15 2:15:03.000 PM kernel[0]: zone leak detection enabled
4/13/15 2:15:03.000 PM kernel[0]: "vm_compressor_mode" is 4
4/13/15 2:15:03.000 PM kernel[0]: multiq scheduler config: deep-drain 0, urgent first 1, depth limit 4, band limit 127, sanity check 0
4/13/15 2:15:03.000 PM kernel[0]: standard timeslicing quantum is 10000 us
4/13/15 2:15:03.000 PM kernel[0]: standard background quantum is 2500 us
4/13/15 2:15:03.000 PM kernel[0]: mig_table_max_displ = 13
4/13/15 2:15:03.000 PM kernel[0]: AppleACPICPU: ProcessorId=0 LocalApicId=0 Enabled
4/13/15 2:15:03.000 PM kernel[0]: AppleACPICPU: ProcessorId=1 LocalApicId=1 Enabled
4/13/15 2:15:03.000 PM kernel[0]: calling mpo_policy_init for TMSafetyNet
4/13/15 2:15:03.000 PM kernel[0]: Security policy loaded: Safety net for Time Machine (TMSafetyNet)
4/13/15 2:15:03.000 PM kernel[0]: calling mpo_policy_init for AMFI
4/13/15 2:15:03.000 PM kernel[0]: Security policy loaded: Apple Mobile File Integrity (AMFI)
4/13/15 2:15:03.000 PM kernel[0]: calling mpo_policy_init for Sandbox
4/13/15 2:15:03.000 PM kernel[0]: Security policy loaded: Seatbelt sandbox policy (Sandbox)
4/13/15 2:15:03.000 PM kernel[0]: calling mpo_policy_init for Quarantine
4/13/15 2:15:03.000 PM kernel[0]: Security policy loaded: Quarantine policy (Quarantine)
4/13/15 2:15:03.000 PM kernel[0]: Copyright (c) 1982, 1986, 1989, 1991, 1993
4/13/15 2:15:03.000 PM kernel[0]: The Regents of the University of California. All rights reserved.
4/13/15 2:15:03.000 PM kernel[0]: MAC Framework successfully initialized
4/13/15 2:15:03.000 PM kernel[0]: using 16384 buffer headers and 10240 cluster IO buffer headers
4/13/15 2:15:03.000 PM kernel[0]: AppleKeyStore starting (BUILT: Mar 23 2015 11:37:46)
4/13/15 2:15:03.000 PM kernel[0]: IOAPIC: Version 0x20 Vectors 64:87
4/13/15 2:15:03.000 PM kernel[0]: ACPI: sleep states S3 S4 S5
4/13/15 2:15:03.000 PM kernel[0]: AppleIntelCPUPowerManagement: (built 11:31:44 Mar 23 2015) initialization complete
4/13/15 2:15:03.000 PM kernel[0]: pci (build 11:38:56 Mar 23 2015), flags 0xe3000, pfm64 (36 cpu) 0xf80000000, 0x80000000
4/13/15 2:15:03.000 PM kernel[0]: [ PCI configuration begin ]
4/13/15 2:15:03.000 PM kernel[0]: console relocated to 0xf80010000
4/13/15 2:15:03.000 PM kernel[0]: [ PCI configuration end, bridges 7, devices 17 ]
4/13/15 2:15:03.000 PM kernel[0]: FireWire (OHCI) Lucent ID 5901 built-in now active, GUID 002332fffe237c98; max speed s800.
4/13/15 2:15:03.000 PM kernel[0]: USBMSC Identifier (non-unique): 000A270015E647AF 0x5ac 0x1209 0x2, 2
4/13/15 2:15:03.000 PM kernel[0]: mcache: 2 CPU(s), 64 bytes CPU cache line size
4/13/15 2:15:03.000 PM kernel[0]: mbinit: done [64 MB total pool size, (42/21) split]
4/13/15 2:15:03.000 PM kernel[0]: rooting via boot-uuid from /chosen: 23A5910A-3701-38BD-B162-EC1B690CAF5C
4/13/15 2:15:03.000 PM kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
4/13/15 2:15:03.000 PM kernel[0]: com.apple.AppleFSCompressionTypeZlib kmod start
4/13/15 2:15:03.000 PM kernel[0]: com.apple.AppleFSCompressionTypeDataless kmod start
4/13/15 2:15:03.000 PM kernel[0]: com.apple.AppleFSCompressionTypeZlib load succeeded
4/13/15 2:15:03.000 PM kernel[0]: com.apple.AppleFSCompressionTypeDataless load succeeded
4/13/15 2:15:03.000 PM kernel[0]: AppleIntelCPUPowerManagementClient: ready
4/13/15 2:15:03.000 PM kernel[0]: BTCOEXIST off
4/13/15 2:15:03.000 PM kernel[0]: Got boot device = IOService:/AppleACPIPlatformExpert/PCI0/AppleACPIPCI/SATA@1F,2/AppleICH8AHCI/PR T0@0/IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageD river/WDC WD5000AAKX-001CA0 Media/IOGUIDPartitionScheme/Untitled@2
4/13/15 2:15:03.000 PM kernel[0]: BSD root: disk0s2, major 1, minor 2
4/13/15 2:15:03.000 PM kernel[0]: wl0: Broadcom BCM4328 802.11 Wireless Controller
4/13/15 2:15:03.000 PM kernel[0]: 5.10.131.36
4/13/15 2:15:03.000 PM kernel[0]: hfs: mounted Macintosh HD on device root_device
4/13/15 2:15:03.000 PM kernel[0]: VM Swap Subsystem is ON
4/13/15 2:15:03.000 PM kernel[0]: AppleYukon2: Marvell Yukon Gigabit Adapter 88E8055 Singleport Copper SA
4/13/15 2:15:03.000 PM kernel[0]: AppleYukon2: RxRingSize <= 1024, TxRingSize 256, RX_MAX_LE 1024, TX_MAX_LE 768, ST_MAX_LE 3328
4/13/15 2:15:03.000 PM kernel[0]: BootCache: cache size (2182610944 bytes) too large for physical memory (4294967296 bytes), capping at 2147483648 bytes

Similar Messages

Time capsule stopped working after installing software update, no lights and reset did nothing. What do I do?

I can't get my time capsule to turn on after a software update. Reset button does nothing and it is pluged in to a live outlet. Is my time capsule dead?

Welcome to Apple Discussions, Freepisces
I have all the latest updates on my Macs, and I have no problem at all.
If you applied the latest (7.4.1) QT update, your problem may be due to the fact that the System Requirements for QuickTime 7.4.1 for Tiger include Mac OS X 10.4.9 or later, and you show that you are using Mac OS X (10.4.3). You can check which QT version you have installed using the QuickTime Player > About QuickTime Player menu command.
If your QT version is an older one that is compatible with your Mac OS, and if you have not done so since you applied the QT update, repairing permissions may help you.
If the problem is somehow related to your iSight rather than to your QT software, Apple's How to Troubleshoot iSight may help you identify and fix your problem.
Unless you have a compelling reason for not doing so, you should consider updating to the latest version of Tiger (10.4.11). To find out what improvements you are missing by staying with 10.4.3, see some of the "About the Mac OS X 10.4.xx Update" documents for updates later than 10.4.3. A couple of examples are:
• About the Mac OS X 10.4.6 Update (combo) and
• About the Mac OS X 10.4.11 Update
If you are interested, other "About..." documents are linked in this search list.
Because System Requirements for the latest combo applicable to your MacBook, Mac OS X 10.4.11 Combo Update (Intel), are for Mac OS X 10.4.4 or later, you will need at least two steps to upgrade from your Mac OS X (10.4.3), so pay careful attention to the System Requirements of any updates you plan to apply.
EZ Jim
PowerBook 1.67 GHz w/Mac OS X (10.4.11) G5 DP 1.8 w/Mac OS X (10.5.1) External iSight

My time capsule stopped working. amber light comes on for a few seconds then turns off.

my time capsule stopped working. When I try to power it up the amber light comes on for about 10 seconds and then turns off. That's as far as it gets. Any ideas on how to solve this problem.

Kazandjaz, Welcome to the fourm! There is a 99.5% chance that your problem is caused by a failed internal power supply unit (PSU)! If you have operated it for about 18 months or so, that is the cause. Take it to your nearest Apple dealer and ask them to check it out.

My Time Capsule stopped working suddenly. The led won't lit up even if I do a hard reset.

Suddenly I noticed that my Time Capsule stopped working. The led doesn't light up any more and there's no noticeable activity in it.
Is it possible to recover my backups?

Dead TC power supply syndrome is standard on all Gen1 and Gen2 TC.
It has plenty of info on the web.
https://sites.google.com/site/lapastenague/a-deconstruction-of-routers-and-modem s/apple-time-capsule-repair
As far as HD is concerned it will mostly be ok. Either fix or remove the TC hard drive and use in USB box, as mentioned.
If it is Gen3 there is a different problem.
Tell us the actual model number from the rubber base.

Time Capsule stopped working - suggestions please

I'm now extremely unhappy about having bought a Time Capsule... after about 12 months of valuable service it has given up on me, out of warranty, and there appear to be no cost-effective repair options. I'm interested in any suggestions for either fixing the overpriced piece of *&%$ or turning it into something more useful than a square frisbee.
Brief summary of problem: it's a 1TB Time Capsule, bought in the UK in April 2008. A couple of months ago it stopped backing up in Time Machine, and won't allow connections in Airport Utility or via ethernet, though it will still act as a wireless base station if plugged into a broadband modem/router. According to the Genius Bar there's a hardware-related network problem of some kind, and there is no alternative to buying a new one (at full price) or putting it in for an out-of-warranty repair which could cost almost as much as a new box. Hmmmm. A 12 month warranty seems fair for a laptop, but for a box that I cannot open and that spends its entire life sitting on a shelf - it's ridiculous. To pay this much for something to fail so soon after so short a warranty expires, and then be told "sorry, that's just tough", really is adding insult to injury.
So: I have a useless, very expensive white brick that I need to put to good use. I am prepared to crack it open with whatever it takes, and tinker with whatever is inside - any detailed information that anyone can provide about how to troubleshoot/fix/replace/hack would be gratefully received. I don't have much of a clue about how that kinda thing (I've replaced hard drives in iPods, but that's about my limit), but I have nothing to lose so here goes... Alternatively, any information on how to launch a 3.5 pound white brick through the windows of 1 Infinite Loop all the way from central London would be handy.
Paul

Thanks Bob,
The disassembly link is v handy. Sounds like board swapping is the way to go, though without some kind of hardware troubleshooting guide I'm not sure of an alternative to replacing boards one by one until it starts working again.
Do you happen to know whether Apple will supply these boards to someone who's not an authorised service agent? I can see that might be a problem, and neither the service/support page nor my other enquiries have so far thrown up an answer on that?
I hear what you say about it being worth getting an estimate, but the Genius Bar advised that the repair would likely cost almost as much as a new unit, which I am simply not prepared to pay - just feels too much like extortion. Paying £329 in the first place hurt a little, but when it works the TC is fab so it's well worth it. Paying out the same again merely for a guarantee that the thing will work for another 90 days, having previously expired just out of warranty, looks like a very bad bet.
Paul

Time Capsule Stopped Working Without Warning

I purchased my iMac & Time Capsule (802.11n) back in 2006. Last Wednesday (17 Mar 2010) evening, and without any type of warning, the capsule stopped working. The little green light went out and I have not been able to get it running since. My DSL connection runs through the capsule to the computer. Thus, I have not been able to go online. I'm a family history researcher and I need my Mac for email, research, and family websites. I might also add that I'm NOT a computer nerd; I'm just an older lady with basic computer knowledge, and I need it to work.
I've had to dust off my old unreliable windows based pc, set it all up again, download updates to the Ya-Ya, set up another email addy ([email protected]) - just to be able to get online to find out what I can or should do with this problem.
Can anyone help me please?
Thanks! TJ

I also had a TC fail. However, I did the mod with the fan to keep it cool (http://sites.google.com/site/lapastenague/a-deconstruction-of-routers-and-modems /apple-time-capsule-repair/apple-time-capsule-fan-mod), and then it failed a month later.
I changed the capacitors on the powersupply board of the TC with instructions from: http://sites.google.com/site/lapastenague/a-deconstruction-of-routers-and-modems /apple-time-capsule-repair/apple-time-capsule-repair-type2
Now it is back up and running, will see how long it lasts.
BTW I went to MacMall in Santa Monica, CA and I was told since I did the fan mod, I lost any chance at a warranty repair/exchange.
My advice: try and get a new one from Apple before you do anything, and do not do the fan mod, it does not completely prevent the failure.... and then one is out of luck with regards to Applecare. Apparently, you can attach the TC to any Applecare/warranty that you have for an Apple CPU. So, if you are under warranty with any CPU, the age of the TC is not an issue (according to my readings).
Good luck....

HT201514 Time capsul stopped working and now cannot be mounted

After hourly backups for the last month (since I bought Time Capsul), Time Machine just stopped. Initially, the message in Time Machine was "backup delayed". I clicked on "backup now" and that message disappeared -- so did Time Capsul. Now Airport Utility no longer "sees" Time Capsul.
-- Time Capsul is the 3TB model, purchased a little more than one month ago.
-- I am backing up roughly 700 GB of data
-- Both My iMac and my Macbook Pro run on OS X 10.7.5
My iMac is connected to Time Capsul by Ethernet cable.
My Macbook Pro is connected wirelessly
Neither the iMac nor the Macbook Pro can "see" the Time Capsul, or find it in Airport Utility. Both my iMac and my Macbook Pro have been backing up flawlessly for more than a month. The backup stopped yesterday with the message "backup delayed", as previously stated.
Is there an explanation and a fix for this problem? That's a pretty short life span for a month old $500.00 purchase.

My Mac book Pro does, in fact, see Time Capsule and is able to do a backup via wireless connection.
My Internet connection works fine -- Time Capsule light is green.
As to your question of: "Did you upgrade to 10.7.5 after the first faulty update was released?", I can't answer that question. I have no memory of a notification of a faulty update. I do, however, have the build 11G63 installed.
Would it be beneficial to do a factory reset?
Don't you just love it when nothing makes sense.. !!
Yes, do a factory reset of the TC..
Using the airport utility, on whichever computer can connect.. give the TC SMB names for everything.. TC network name, wireless names, and hard disk name.. that means, short, no spaces, pure alphanumeric.
In Lion use the 5.6 utility.
http://support.apple.com/kb/DL1482
The v6 airport is a toy.. plastic hammer.. suitable for toyland networks.
You might need to reset the TM in the computers..
A4 here. http://pondini.org/TM/Troubleshooting.html
Are you using the TC as router or in bridge? What broadband do you have?
Check for instance the ethernet is working from the connectivity led on the ethernet port of the TC.. it will show green.

Wireless connection between D-Link WiFi router and Time capsule stopped working

We have an ISP provided D-Link wireless router (DIR-615) to which we wirelessly connected our 2Tb Time Capsule for back up and to connect a USB printer to out network. This worked perfectly for 3 1/2 years, until about a month ago, when the time capsule suddenly decided to go "off line". ie we could no longer access it or the printer via our wireless network. We had changed nothing - just one day it stopped working.
We tried to get it back online with no success. As the 2Tb Time Capsule was almost 7 years old and had had some HDD issues in the passed, we figured it had got old and died and that it was time to replace it; so we bought a new 3Tb Time Capsule, thinking this would get everything back to normal.
However much as we tried, we were also unable to get the new 3Tb Time Capsule to connect wirelessly to the D-Link wireless router. The Airport Utility did not show the D-Link wireless router or its wireless network, although we were (and are) able to see it in Systems Preferences>Networks from all our multiple devises. This in itself seemed odd. No matter what we tried, the Airport Utility would not find the D-Link wireless router and hence we could not add the 3Tb Time Capsule to the existing wireless network.
At the end of the day we got fed up with trying to add the 3Tb Time Capsule to the D-Link wireless network, and connected it via a LAN cable to the D-Link router instead. We then set it up as its own network. Worked gerat. Having done that we thought maybe the old 2Tb Time Capsule might not have been the problem after all, so we tried extending our new 3Tb Time Capsule wireless network using the 2Tb Time Capsule wirelessly. This worked perfectly! And we are now almost back to what we wanted.
So although we have a work around, this means now have 2 separate wireless networks as opposed to the original single wireless network where everything talked to everything else.
Can anyone shed any light on any of the following:-
1. Why the original wireless network connection between the D-Link router and the 2Tb Time Capsule just stopped working? Was there some software change from Apple that "decided" D-Link wireless routers were no longer secure; and therefore the TCs could no longer connect to them?
2. Why it was not possible to extend the existing D-Link wireless network using the the new 3Tb Time Capsule?
3. Is there is anyway that we can get back to a single wireless network based around the D-Link wireless router as the primary router connecting to the modem, where the 2 Time Capsules connect as "wireless satellite base stations"?

1. Why the original wireless network connection between the D-Link router and the 2Tb Time Capsule just stopped working? Was there some software change from Apple that "decided" D-Link wireless routers were no longer secure; and therefore the TCs could no longer connect to them?
A firmware update to the TC came along and you agreed to it without perhaps even noticing.. it then smashed your setup because Apple do not recommend the setup you were using and it is very poor.
2. Why it was not possible to extend the existing D-Link wireless network using the the new 3Tb Time Capsule?
Because it is such a poor setup that Apple have taken away your ability to choose it unless you know exactly what you are doing.
3. Is there is anyway that we can get back to a single wireless network based around the D-Link wireless router as the primary router connecting to the modem, where the 2 Time Capsules connect as "wireless satellite base stations"?
Yes, this I can help you with.
I have several ways around the problem.. but the first one is.. why use the DIR-615 at all.. it is not a modem.. it is a very ordinary bottom end, poor single band slow wireless router.
Why don't you simply remove the DIR-615 from the network completely.. plug whatever it is the ISP supplies you.. an ethernet connection from whatever that modem is you mentioned into the WAN port of the Time Capsule. And use the TC in some router mode.. same as the DIR-615 was setup.. dhcp or pppoe or whatever.. I doubt the TC cannot match it.
If you have issues please post a few screenshots from the DIR-615 to show how it is setup from the WAN side.. and as long as you are given the username and password or whatever the ISP uses to authenticate then chuck out the DIR-615.
Tell me if that is a goer.. if not we can work out a few other methods..
eg. Simply turn off the wireless in the DIR-615. It is poor cf the TC and there is no need for it.. with the TC in bridge only use the TC for wireless as well as wireless extend with your old TC.
Or setup roaming network where everything uses the same SSID.
Then you will have one wireless network. And it won't matter what as long as it connects.. although IMHO this is not right as the TC is such a superior router now you are wasting your new TC.

Time machine stopped working after upgrading to lion

After upgrading to lion my time machine has not been able to back up. It takes a long time preparing and trying to back up and then stops with an error (without an error message being shown to the user). The status is delayed and it claims that the backup disk cannot be found (Im using a time capsule).
The system log contains the following entries (filtering on "time"):
Aug 18 21:58:48: --- last message repeated 2 times ---
Aug 18 22:00:06 Macintosh-2 mtmd[2132]: Set snapshot time:1313697608 (current time:1313697606)
Aug 18 22:01:27 Macintosh-2 com.apple.backupd[3318]: Network destination already mounted at: /Volumes/Soren Helsted's Time Capsul
Aug 18 22:02:10 Macintosh-2 fseventsd[17]: event logs in /Volumes/Time Machine Backups/.fseventsd out of sync with volume. destroying old logs. (280 2 3619)
Aug 18 22:02:11 Macintosh-2 fseventsd[17]: log dir: /Volumes/Time Machine Backups/.fseventsd getting new uuid: 06F2B428-D8B5-46F7-9505-DCF33818C3FC
Aug 18 22:02:11 Macintosh-2 com.apple.backupd[3318]: Disk image /Volumes/Soren Helsted's Time Capsul/Soren Helsted’s Computer.sparsebundle mounted at: /Volumes/Time Machine Backups
Aug 18 22:02:12 Macintosh-2 com.apple.backupd[3318]: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
Aug 18 22:05:39: --- last message repeated 81 times ---
Aug 18 22:05:39: --- last message repeated 14 times ---
Aug 18 22:05:39 Macintosh-2 mds[68]: (/Volumes/Time Machine Backups/.Spotlight-V100/Store-V1/Stores/A0B6A325-88A2-4408-AF3F-319C76E5E58C)(E rror) IndexGeneral in fd_pread:pread(120 /Volumes/Time Machine Backups/.Spotlight-V100/Store-V1/Stores/A0B6A325-88A2-4408-AF3F-319C76E5E58C/1. indexPostings, o:0, s:262144) err:5
Aug 18 22:05:41: --- last message repeated 1427 times ---
Aug 18 22:05:41 Macintosh-2 mds[68]: (/Volumes/Time Machine Backups/.Spotlight-V100/Store-V1/Stores/A0B6A325-88A2-4408-AF3F-319C76E5E58C)(E rror) IndexCI in ci_ftruncate:ftruncate(86 /Volumes/Time Machine Backups/.Spotlight-V100/Store-V1/Stores/A0B6A325-88A2-4408-AF3F-319C76E5E58C/tm p.merge.0.indexIds, 0) error:5
Aug 18 22:05:42: --- last message repeated 737 times ---
Aug 18 22:05:42: --- last message repeated 43 times ---
Aug 18 22:05:42 Macintosh-2 fseventsd[17]: disk logger: failed to open output file /Volumes/Time Machine Backups/.fseventsd/00000000032488f5 (Input/output error). mount point /Volumes/Time Machine Backups/.fseventsd
Aug 18 22:05:42: --- last message repeated 1 time ---
Aug 18 22:05:42: --- last message repeated 11 times ---
Aug 18 22:05:42 Macintosh-2 mds[68]: (/Volumes/Time Machine Backups/.Spotlight-V100/Store-V1/Stores/A0B6A325-88A2-4408-AF3F-319C76E5E58C)(E rror) IndexCI in open_index_file:open file error: 5, tmp.merge.1.indexHead
Aug 18 22:05:42: --- last message repeated 32 times ---
Aug 18 22:05:42: --- last message repeated 1 time ---
Aug 18 22:05:42: --- last message repeated 1 time ---
Aug 18 22:06:07: --- last message repeated 61 times ---
A

I finally figured out what was the problem. The disk utility tool found an error in the backup disk and fixed it. I guess some error occurred while the upgrade to Lion was on the way.

New time capsule stops working with http connections

I have the latest 2TB Time Capsule. I've been getting a weird issue where my I can no longer can do http connections (i.e. browse the internet) but I can still use other internet capable services like Skype or Steam. It seems that traffic through port 80 just seems to stop working. All of my devices on my network experience the issue. I have even exchanged Time Capsules but the issue still presists.
Does anyone have any ideas?

Here's a traceroute when things work:
traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 3.637 ms 1.030 ms 0.924 ms
2 69.254.248.1 (69.254.248.1) 10.644 ms 10.237 ms 10.590 ms
3 te-7-1-ur02.olathe.ks.indepen.comcast.net (68.87.234.209) 10.453 ms 10.177 ms 10.519 ms
4 te-4-4-ar02.independence.mo.indepen.comcast.net (68.87.234.5) 10.464 ms 11.360 ms 13.087 ms
5 68.87.234.29 (68.87.234.29) 11.762 ms 12.583 ms 13.066 ms
6 be-20-702-cr01.sanjose.ca.ibone.comcast.net (68.86.89.37) 28.948 ms 21.847 ms 24.969 ms
7 he-0-11-0-0-pe04.350ecermak.il.ibone.comcast.net (68.86.83.58) 22.267 ms 22.081 ms 21.251 ms
8 * * *
9 * * *
10 72.14.237.110 (72.14.237.110) 26.647 ms
    72.14.237.108 (72.14.237.108) 25.617 ms
    72.14.237.110 (72.14.237.110) 53.230 ms
11 72.14.232.141 (72.14.232.141) 33.403 ms 33.622 ms
    209.85.248.228 (209.85.248.228) 34.010 ms
12 216.239.46.193 (216.239.46.193) 33.824 ms 33.433 ms 34.014 ms
13 * * *
14 google-public-dns-a.google.com (8.8.8.8) 37.414 ms 34.587 ms 34.306 ms
Here's the output when it doesn't:
traceroute 8.8.8.8
traceroute: unknown host 8.8.8.8
I just changed my DNS. I'll report back in a day to say if it fixed anything.

Time Capsule not working after a restore

I recently had to restore from my TM/TC backup after a standard software update made it so I could no longer log into my account. Now, my TC is not working properly. I can still access all of my past updates on mu TC, but it is not working for making new backups. Instead of backing up the new files, TM wants to do a whole new backup from scratch (all 140 gigs). Worse still, it is unbelievably slow (as in it took over 3 hours just to do 1 gig last night on my wireless.)
If I can still access all my old files on the TC and I restored my Mac using the TC files, why is it that TM wants to start an entire new backup now instead of continuing to update the original one? And, why is the updating crawling along at such a terribly slow speed. Any thoughts/proposed solutions to this very much appreciated.

I found this article which describes a fix:
http://www.macosxhints.com/article.php?story=20080128003716101
I'm testing it on my Time Capsule now, I'll let you know how it goes.

Time Capsule not working after last software update

I bought my time capsule 3 weeks ago. Set up and worked like a charm (I use airport express for my wireless network). After I downloaded the latest software updates a week or so ago, I got a message that my computer could no longer recognize my time capsule. Since then the time capsule light only flashes amber and wont appear in airport utility.
Any ideas?
Thanks

I was having problems with the 7.3.1 firmware as well. For me, in manifest as though the internal disk had went bad--a blinky amber light and a "Disk needs repair" error. Rolling back the firmware solved it for me.
To do this:
--Open AirPort Utility.
--Click on your TC.
--Click on the "Manual Setup" button.
--When the configuration summary pops up, click on the word "Version".
--From the "Upload" drop-down list that is on the new pane that pops up, select "7.3", and click "Ok".
--Once it reboots, it'll be at 7.3.
Hope this helps. I'll be waiting a few weeks after 7.3.2 comes out to upgrade. I'm not real impressed with 7.3.1. As far as I can tell, it broke more than it fixed.

Time Capsule Not Working After Hard Reset

A few weeks ago my MacBook Pro started slowing down to a crawl. Eventually ralised it was due to Time Machine not finding the Time Capsule - a known problem.
Reset the Time Capsule (2TB, 8 months old) but although the Internet is working the light is still flashing amber. Carried out a hard reset and still get back to the same situation - the internet is working through the Time Capsule's wireless network but I am getting the flashing amber light.
My internet connection comes into the house and into a wireless modem. An ethernet cable from the back of this modem comes up to my office where the Time Capsule is located into a fast ethernet swtich and then an ethernet cable goes from the switch and is then plugged into the back of the Time Capsule in one of the three internet ports with the <<->> markings.
AirPort Utility shows me that the internet is working and has a green light whereas the Time Capsule has a flashing amber light and 2 errors. When I click the Time Capsule it tells me that the status is:
- Double NAT
- Ethernet Unplugged
Does anybody have any ideas?
TIA

I was having problems with the 7.3.1 firmware as well. For me, in manifest as though the internal disk had went bad--a blinky amber light and a "Disk needs repair" error. Rolling back the firmware solved it for me.
To do this:
--Open AirPort Utility.
--Click on your TC.
--Click on the "Manual Setup" button.
--When the configuration summary pops up, click on the word "Version".
--From the "Upload" drop-down list that is on the new pane that pops up, select "7.3", and click "Ok".
--Once it reboots, it'll be at 7.3.
Hope this helps. I'll be waiting a few weeks after 7.3.2 comes out to upgrade. I'm not real impressed with 7.3.1. As far as I can tell, it broke more than it fixed.

Time Machine stopped working after using two external drives

I'm using a MacPro OS x 10.5.8. I started using Time Machine in April 2011 to back up my files to a 2TB Lacie external drive connected via firewire. Everything has been working fine until recently. A friend needed some files transfered from Seagate 1TB to another external drive. I bought a Lacie 1TB USB 3 drive and connected it to my Mac to make the file transfer. After doing this I noticed that the generic drive icon for my 2TB Lacie backup drive had disappeared. I could see the generic icon for the new 1TB Lacie drive. Then I noticed a Lacie icon on my desktop. I clicked on it and found it was my 2TB backup drive.
I decided to check Time Machine to see if it was still working properly. When I tried to restore to a previous time, the restore button stayed grayed out and didn't respond. Other times it would light up and respond when I clicked on it but I got an error message. I would like to restore my system back before I connected the two ext hard drives used for file transfering in case that was what caused the problem. Could connecting another new Lacie 1TB USB 3 external drive have caused my problem? I haven't had this problem with other external drives.

First, merely connecting another drive could not have caused Time Machine to stop working.
Since your backup is in a doubtful state, your highest priority should be to protect your data by making another backup to a different drive. You need more than one backup anyway. Connect an empty drive, select it in the TM preference pane, and start a new backup set. Once that's done, I suggest you run "Repair Disk" in Disk Utility on the old backup volume.

Airport Extreme/Time Capsule not working after downloading 7.6

Downloaded airport 7.6 last night and now time capsule/airport extreme doesn't work. I can't even reset the tc to factory default settings. Not sure what to do now.

Hi, today I got the same problem after 7.6 update for my Time Capsule. I tried to downgrade to 7.5.2, but afterwards the problem was not solved. Then I tried to set fixed channnels - and it works! For 2.4 Ghz I used channel 12 and for 5Ghz channel 48. Beforehand I used "automatic" for both. Hope it works for you too. I don't know, how Apple's test team spend the whole day ;-)

TIme Capsule stopped working after 10.10.3

Similar Messages

Maybe you are looking for