Time Capsule Shows in Finder Locations, but Won't Connect or Add to TCSMB #267
|
I downloaded and installed TCSMB a few days ago, and all seemed to be well accessing the TC as a network drive and performing Time Machine backups. Today, I got a TM backup error. In the past, I would remove and re-add the TC in TM, then start a fresh backup. Today, that didn't work. I tried uninstalling TCSMB from the TC, but that failed. I removed my TC from the TCSMB list of devices, and tried to re-add. That failed. The errors appear to be when Checking SSH. I also got a device compatibility error before I removed the TC from TCSMB to re-add. I can see my TC in the list available devices in both TCSMB and Locations in Finder, but it cannot connect in either place. Can anyone provide advice/instructions to get this back up and running? I am NOT tech-savvy when it comes to coding and scripting, so please be as descriptive as possible with suggested solutions. Thank you for your assistance. |
Replies: 7 comments 7 replies
|
The device appearing under Finder Locations only proves that Bonjour discovery is seeing an advertisement; it does not prove that SSH or the new SMB service is working. Since the app now fails at Checking SSH, do not erase the Time Capsule disk or create a new Time Machine backup yet. Try this recovery sequence in the GUI:
If this is a Gen 1–4 Time Capsule and it rebooted, also press Activate after it comes back unless you previously installed the persistent boot hook. Those older models do not automatically start Samba after every reboot on stock firmware. If the manual-IP add still stops at Checking SSH, please post the exact error text/screenshot plus the Time Capsule model, macOS version, and TimeCapsuleSMB app version. In particular, say whether the app reports Password Rejected, Unsupported, or a timeout; those lead to different fixes. At that point the failure is in local access/credential/SSH setup, before Time Machine itself, so repeatedly removing the backup destination will not help. |
|
Thank you for the prompt reply. In the intervening time, I attempted another power cycle of the TC. Now AU shows a dimmed TC icon, but advises that it cannot be found. It also is no longer visible in TCSMB. The Checking SSH error was a timeout. I'm afraid I don't know the model number of my TC. MacOS v. 26.5.2, TCSMB v. 2.2.9. Could it be that the uninstall I attempted before corrupted something? |
|
The failed uninstall is unlikely to have caused this. TimeCapsuleSMB's uninstall removes only its managed Samba payload/boot files; it does not change the AirPort's base network configuration or erase the backup disk. Also, a timeout means the app could not reach SSH, so that attempt may not have changed anything at all. A dimmed icon with “device not found,” followed by disappearance from both apps, means we should first restore basic network reachability. Please do not erase the disk or choose “Restore Default Settings.”
The model number is printed on the bottom/base and begins with For reference, the project's FAQ lists exactly what uninstall removes and says the existing disk data is not deleted. |
The model number is indeed A1470 (those characters sure are small!). So, is it likley this is actually a hardware failure? |
|
Not necessarily. Flashing amber is an “attention/configuration required” indication, not by itself proof of failed hardware. The stronger symptom is that an A1470 remains unavailable in AirPort Utility even during the reset window. The next test removes the “same network” uncertainty:
If it still cannot be discovered while directly connected, the next escalation is Apple's hard reset: hold reset for about five seconds until the amber light flashes rapidly, then release and look in AirPort Utility again. This resets the base station's network configuration, but it does not erase the files/Time Machine backups on the internal disk. Do not choose the factory-default/erase-disk options. Only if AirPort Utility still cannot see it over direct Ethernet during/after that hard-reset state would I call hardware failure likely. At that point the likely area is the base station/power supply/Ethernet hardware, not TimeCapsuleSMB and not damage from its uninstall. The fact that it reaches green briefly shows it is booting at least partway, so doing this direct-cable test is worthwhile before concluding it has failed. |
|
I'm afraid I don't have an Ethernet adapter. I've ordered one from Amazon that should be here tomorrow. I will advise what I learn after following the steps you described. Thank you again for helping me with this. |
|
You're welcome. Waiting for the adapter is the right next step, and there is no need to change anything else meanwhile. When you test tomorrow, please note two separate results before trying the hard reset: (1) what System Settings → Network → Ethernet reports with Wi‑Fi off, and (2) whether AirPort Utility shows the A1470 under Other Wi‑Fi Devices after the brief reset. Those two observations will tell us whether the Mac is reaching the base station at all. Please continue to avoid any erase-disk option. |
|
I connected my Mac to the TC via an ethernet cable and adapter. While the Thunderbolt Ethernet does not show as "connected", there is a self-assigned IP address for a device named AX88179B. After pressing the reset button, the TC did not immediately show up in AU, but the device named AX88179B was listed in "Other Wi-Fi" devices. At first, it showed that I needed to enter the password for the TC. I entered the password but it failed to connect, even after several attempts. Now AU is again showing the alert that the TC cannot be found. I've tried pressing the reset button, but to no avail. As a troubleshooting step the connection lights on both the TC and the Ethernet adapter are lit. The data transfer light on the Ethernet adapter was flashing, too. |
|
More info. I did another power cycle on the TC, and it is visible again, but only via Ethernet connection, and is again asking for the password. After additional password attempts, the AU is again showing the TC is not available. |
|
Any ideas? |
|
The TC was visible again in TCSMB, so I ran the connect function. I got the following error (sorry that it's a screenshot with small text. I couldn't hight the text to copy it.). Does this point to anything that might help narrow down what we can do to get this operating? |
|
This is a SSH command timeout during the early arch check step, which means the device is busy somehow. I've seen this a few times, but I haven't figured out what causes it. The most obvious guess is "you just restarted the device and it's still starting up" but that may or may not be true. Without more info, the best thing you can do is just turn it off, wait 5 minutes, turn it on, wait 30 minutes so you can be sure it's fully started up, and then try again. |
|
TL/DR; Do a hard reset, and establish a new network within the five-minute time limit. Then add the "new" TC to TC SMB I've got some good news. I don't recall if you advised doing a hard reset. I'd tried one before, and it didn't seem to work. I since learned that upon performing he hard reset steps, I have five minutes to take action, or the TC reverts to the previous network settings. I was more timely now, and was able to establish a new network using the APU. I was then able to connect add the "new" TC to the TCSMB, as well as mount it to my MacBook Pro as an external drive. Thank you again for your assistance. |
|
Cool, glad you got it resolved |
TL/DR; Do a hard reset, and establish a new network within the five-minute time limit. Then add the "new" TC to TC SMB
I've got some good news. I don't recall if you advised doing a hard reset. I'd tried one before, and it didn't seem to work. I since learned that upon performing he hard reset steps, I have five minutes to take action, or the TC reverts to the previous network settings. I was more timely now, and was able to establish a new network using the APU. I was then able to connect add the "new" TC to the TCSMB, as well as mount it to my MacBook Pro as an external drive.
Thank you again for your assistance.