-
All replies
-
Helpful answers
-
Aug 14, 2016 1:55 PM in response to NZ Bossby LaPastenague,This was a problem we had a few years back but we don't see much now.
You don't seem to have any apple clients at all in your list.
Perhaps tell us a bit more .. what is the full list of clients?
Currently no computers are set to back up to it, or even turned on to access it,
What model and firmware TC is it?
Do you have Apple ID set in TC? It seems to be causing some issues so a full factory reset might be in order.
I would then change the TC name and wireless name.. and slowly go through each client to add the new configuration to find out which is causing the problem.
Continually spinning up the disk is not good so it is important to catch what is causing it.
-
Aug 14, 2016 3:44 PM in response to LaPastenagueby NZ Boss,Thanks for your reply, I was meaning to follow this up with some more detailed info but things got a bit busy!
The problems started occurring a while ago where I couldn't access the drive on my retina MacBook Pro. The other MacBook Pro (non retina) in the house could access it but not backup to it.
Our network setup is one gen 3 I believe 1tb time capsule, a new airport express, an old AirPort Extreme, and the new time capsule with AC wireless that is the one having the issue. They are all connected by Ethernet and all create their own networks under the same name. Sorry I can't be more specific on the model numbers, I'm not at home at the moment.
There are a variety of other clients that are not accessing the hdd in theory (phones, iPads and a Windows pc along with other misc devices).
All the airports have the latest firmware. I will check to see if my Apple ID is setup, that was one of my thoughts on what might be causing it.
Failing that I will look at changing the name then a full factory reset if necessary.
Thanks for your help, I will be sure to update when/if I manage to fix it.
-
Aug 14, 2016 3:55 PM in response to NZ Bossby LaPastenague,One thing we do know.. the Apple mDNS responder and the bonjour sleep proxy are both buggy.
Apple have stated that backup to a TC you are not directly connected to by ethernet or wireless is problematic. The computer will simply forget where the TC is located.. even though you have internet. That could explain some of the issues.. but not the disk spinning up and down.
What OS are the Macs running??
Are any of the airports working as main router?? If all are bridged let me strongly encourage you to at least setup one airport to run DHCP for the rest of the network.. otherwise things can fall to pieces.
I use static IP method.. as here if you have a router in front of the TC.
https://discussions.apple.com/message/25135547?ac_cid=tw123456#
All the airports in the network should be on static IP addresses. Whether you set this on the airport itself or on the main router via dhcp reservations (or both) is up to you. But do not let IP float around.. the DNS system is not up to that.
Post again when you are home with some more details... a few screenshots of the setup from airport utility helps no end.
-
Aug 15, 2016 1:07 AM in response to LaPastenagueby NZ Boss,Thanks for your prompt reply, I'm at home now so hopefully can start to fill in the gaps.
Both the Macs are on 10.11.6 with one primarily connected to ethernet for backups, or in the same room as the TC, and the other with the TC being the closest router to connect to.
Have checked in airport utility and no back to my mac set up, so I don't think its related to having the apple ID connected up.
The current setup is our ISP provided modem connected via ethernet to the TC having the issue which is then daisy chained to the other devices (hopefully the screenshot helps show this).
I have just tried to change the disk password and upon restart have got these warnings, which I have seen occasionally on restart. When we got our new modem a few months ago I was required to change the DNS settings on the TC to use the following static IP addresses 8.8.8.8 and 4.2.2.2. I also had to change settings on the modem to enable DCHP server on the address 192.168.20.11.
Here are the screen shots taken moments before the restart when all seemed to be working fine (apart from the HDD issue).
Sorry for the slightly sporadic information, let me know if there is anything else I could provide that might help. I was basically having new problems until this new modem arrived and everything started mucking up. Needless to say the ISP has been receiving a lot of disgruntled calls from me!
Cheers
-
Aug 15, 2016 1:15 AM in response to NZ Bossby NZ Boss,Sorry, have just completed your instructions on changing the static IP and have removed two of the three warnings. I am now only left with 'Internal disk needs repair', which sounds rather ominous...
-
Aug 15, 2016 2:22 PM in response to NZ Bossby LaPastenague,Ok..
1. The AC (latest model TC) must be replaced. A disk error is basically not repairable without opening the unit and replacing the drive.. not something I would encourage unless you have done that kind of stuff before.
The TC is covered by applecare on a computer, ipad or Apple TV. So if you have any current applecare and the TC is less than 3 years old.. take it to apple for replacement.
If it is less than 2years old and you don't have apple care and nothing that qualifies, buy an Apple TV and applecare for it. Don't open the ATV.. you will return it.. with applecare now covering the TC get apple to replace it. Then return the ATV for refund (unless you happen to need one).
2. You then need to go through the whole setup.. fix up the names.. everything should be short, no spaces and pure alphanumerics. Fixed IP addresses on everything. And use the static IP plus DHCP on that first TC ..
Happy to give more details if you need them.



