NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Periodic (daily) Time Machine failures
I am running TM on an iMac with 10.5.8 to a Duo running 4.1.6. However I am getting a failure about once a day where TM pops up a dialog saying the network volume could not be mounted because of a problem with the username or password. It is very odd because it will do its hourly backup just fine for some period of time (a day or maybe a bit longer) before giving me this error. If I go to the TM Preferences I have to re-enter the username and password, then all is fine again for a day or so. This happened again just now and I snagged the Duo logs and also took a look at the Mac log. On there I see this series of possibly related messages:
Aug 16 17:07:40 Kobe kernel[0]: AFP_VFS afpfs_mount: /Volumes/ReadyNAS, pid 4993
Aug 16 17:07:40 Kobe Bonjour Mounter[267]: DiskAppearedCallback diskDescription = {\n DAVolumeKind = afpfs;\n DAVolumeMountable = 1;\n DAVolumeName = ReadyNAS;\n DAVolumeNetwork = 1;\n DAVolumePath = file://localhost/Volumes/ReadyNAS/;\n}
Aug 16 17:07:42 Kobe [0x0-0x14c14c].com.apple.systempreferences[4987]: chown: /Volumes/ReadyNAS/.001ec20ffc9e: Operation not permitted
Aug 16 17:07:43: --- last message repeated 1 time ---
Aug 16 17:07:43 Kobe kernel[0]: AFP_VFS afpfs_unmount: /Volumes/ReadyNAS, flags 0, pid 4998
Aug 16 17:07:43 Kobe Finder[161]: StatusMonitor::volumesChangedCallBack returned -47
Aug 16 17:07:43 Kobe kernel[0]: ASP_TCP do_thread_read: no reqInfo found for reqID 1
Aug 16 17:07:43 Kobe Bonjour Mounter[267]: DiskDisappearedCallback diskDescription = {\n DAVolumeKind = afpfs;\n DAVolumeMountable = 1;\n DAVolumeName = ReadyNAS;\n DAVolumeNetwork = 1;\n DAVolumePath = file://localhost/Volumes/ReadyNAS/;\n}
Aug 16 17:07:43 Kobe kernel[0]: ASP_TCP CancelOneRequest: cancelling slot 29 error 89 reqID 30 flags 0x9 afpCmd 0x14 so 0x7e7a330
In Duo afp.log
Aug 16 17:07:42 cnid_dbd[29190][logger.c:255]: I:Logger: doing log_setup, type 0, level 50, filename "/var/log/netatalk.log"
Aug 16 17:07:42 cnid_dbd[29190][logger.c:395]: D7:Logger: log_file_arr[0] now contains: {log_filename:/var/log/netatalk.log, log_file:(nil), log_level: 50}
Aug 16 17:07:42 cnid_dbd[29190][logger.c:398]: D5:Logger: log_setup[0] done
Aug 16 17:07:42 cnid_dbd[29190][main.c:210]: I:CNID: Setting uid/gid to 0/0
Aug 16 17:07:42 cnid_dbd[29190][main.c:309]: I:CNID: Startup, DB dir /c/.timemachine/.AppleDB
Any idea how I prevent this from happening? It means if I'm not in front of the Mac for awhile the TM backups stop.
Aug 16 17:07:40 Kobe kernel[0]: AFP_VFS afpfs_mount: /Volumes/ReadyNAS, pid 4993
Aug 16 17:07:40 Kobe Bonjour Mounter[267]: DiskAppearedCallback diskDescription = {\n DAVolumeKind = afpfs;\n DAVolumeMountable = 1;\n DAVolumeName = ReadyNAS;\n DAVolumeNetwork = 1;\n DAVolumePath = file://localhost/Volumes/ReadyNAS/;\n}
Aug 16 17:07:42 Kobe [0x0-0x14c14c].com.apple.systempreferences[4987]: chown: /Volumes/ReadyNAS/.001ec20ffc9e: Operation not permitted
Aug 16 17:07:43: --- last message repeated 1 time ---
Aug 16 17:07:43 Kobe kernel[0]: AFP_VFS afpfs_unmount: /Volumes/ReadyNAS, flags 0, pid 4998
Aug 16 17:07:43 Kobe Finder[161]: StatusMonitor::volumesChangedCallBack returned -47
Aug 16 17:07:43 Kobe kernel[0]: ASP_TCP do_thread_read: no reqInfo found for reqID 1
Aug 16 17:07:43 Kobe Bonjour Mounter[267]: DiskDisappearedCallback diskDescription = {\n DAVolumeKind = afpfs;\n DAVolumeMountable = 1;\n DAVolumeName = ReadyNAS;\n DAVolumeNetwork = 1;\n DAVolumePath = file://localhost/Volumes/ReadyNAS/;\n}
Aug 16 17:07:43 Kobe kernel[0]: ASP_TCP CancelOneRequest: cancelling slot 29 error 89 reqID 30 flags 0x9 afpCmd 0x14 so 0x7e7a330
In Duo afp.log
Aug 16 17:07:42 cnid_dbd[29190][logger.c:255]: I:Logger: doing log_setup, type 0, level 50, filename "/var/log/netatalk.log"
Aug 16 17:07:42 cnid_dbd[29190][logger.c:395]: D7:Logger: log_file_arr[0] now contains: {log_filename:/var/log/netatalk.log, log_file:(nil), log_level: 50}
Aug 16 17:07:42 cnid_dbd[29190][logger.c:398]: D5:Logger: log_setup[0] done
Aug 16 17:07:42 cnid_dbd[29190][main.c:210]: I:CNID: Setting uid/gid to 0/0
Aug 16 17:07:42 cnid_dbd[29190][main.c:309]: I:CNID: Startup, DB dir /c/.timemachine/.AppleDB
Any idea how I prevent this from happening? It means if I'm not in front of the Mac for awhile the TM backups stop.
82 Replies
Replies have been turned off for this discussion
pb10006 wrote: Sorry, but the last post to this thread was April 12 - and on March 20 it was noted that NetGear has not addressed this problem.
Yes - 2010- oops - eating my words now *blush*. but still, it is not clear if this has been solved and how ...
peter. - From what I can tell, the error seems to indicate problems with the AFP setup of the share used by TimeMachine (corruption of some kind of some system data).
The fix is quite straight forward (delete that data and allow the NAS to recreate it - this does not impact any user data), but would require you to enable root SSH to login to your NAS via commandline and make some minor changes. Alternatively it *may* be possible to fix via CIFS access to your NAS, but I'm not sure
If you are not comfortable or unable to do any of this for whatever reason, then I would strongly suggest that you instead contact Netgear techsupport. - I'm fine with working directly on my backup machine [ ... linux is linux, right :) ]. do you know which file(s) need to be tossed? i take it such files are re-created whenever time machine posts the next update, right?
the worst that can happen is that i'll lose my history ...
cheers,
p. - When you access a share via AFP, the AFP service running on the NAS (called netatalk) creates a number of hidden directories in the root of the share beginning ".Apple". These directories are used to store Mac specific info. In reality, for the TM share that info is not actually needed - but it is created anyway as part of how the service works - and if it gets corrupted, or for example not upgraded properly when the NAS firmware is updated, then it can create issues accessing the share via AFP.
I have seen this happen before, but not specifically resulting in the error you report - but there are posts on other forums that show a similar error to yours and suggest a similar diagnosis. As the info will get recreated when you access the share again via AFP, and that there is no TM specific data stored there anyway, deleting those directories and allowing the AFP service to recreate them would seem a reasonable debugging step
The specific directories to remove (or just move) are:
/c/.timemachine/.AppleDB
/c/.timemachine/.AppleDouble
/c/.timemachine/.AppleDesktop
(It is possible you do not have all 3 - .AppleDB is the important one)
Good luck - Thanks for the information, but I'm afraid it did not make much of a difference. I've submitted a ticket with NetGear and when this problem is resolved, I'll post the result.
All the best,
peter. - Try rebooting your mac also as I have often found such changes do not properly take effect until your mac reconnects to the NAS
- Alas .. no such luck. Let's see what the NetGear tell me. Just to help me understand, you mentioned netatalk before - where does this run? In the Linux kernel, or is it a user-level service? [don't want to be mucking with the kernel on my backup device, but if it is a user-level service, we may want to start debugging this]
cheers,
p. - netatalk is a service - not part of the kernel - and pretty much the defacto standard for providing AFP access to a *nix server. So if you are having AFP access issues, you can be almost certain the issue is with netatalk.
Something else you could try: Via cmd+k connect to afp://[email protected] and use your TM password to authenticate
Normally, this should allow you to mount the TM share directly and then gain access to the diskimages stored there. Might help to see if that is actually possible and so determine if this really is an AFP access issue as I suspect, or perhaps something more specific to TM
You shoudl then also download your logs and look for the netatalk.log file to see if there is any useful debug info - This is an ongoing problem. I'm running the latest Ultra6 firmware and Mac Os. Time machine starts and gets a few hundred mb, maybe even a gig or two and fails. Time machine says there was and error that might be temporary. I have deleted the backup on the Ultra6, run disk repair on the backup volume and read every posting on the forum.
Is Netgear doing anything to support this forum?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
