NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
CaryTheLabelGuy
Dec 22, 2011Aspirant
CNID DB error using AFP in Lion
My rig: late 2011 iMac 27inch 3.1Ghz Quad Core i5 running OS X Lion ReadyNAS NV+ RAIDiator 4.1.8 4x1tb Hitachi drives I'm having an issue whenever I try to use AFP on the ReadyNAS NV+. The pro...
peterw1
Apr 08, 2012Aspirant
I came into this CNID Error problem just recently, approximately 10 days after establishing from scratch a dedicated ReadyNAS Ultra 4 Plus to be the Time Machine for a group of 10.6.8 Macs:
OSX 10.6.8 (all 6 Macs backing up via Time Machine, some hourly as they are running 24/7, others less frequently and only when in use)
Backup Time Machine is a ReadyNAS Ultra 4Plus running RAIDiator 4.2.19.
Backup share allocated size 2.5 TB.
After reading a bunch of posts about people having uncertain but some success by going into the ReadyNAS file system to manually delete ".AppleDB" stuff and whatever else with root tinkering, I wanted to see whether I could get the ReadyNAS to heal itself.
What seems to work for me in getting rid of this error and restoring full Time Machine functionality (continuation of backup to, as well as looking back into existing sparsebundles) is:
1. in Frontview: System > Performance - UNCHECK "Disable full data journaling" <APPLY>
2. Then: System > Shutdown - CHECK "Check and fix quotas on next boot…", select "Shutdown and reboot device" <APPLY>
After the reboot and when the ReadyNAS came back online, I was able to re-enable Time Machine on each Mac, and things picked up where they left off prior to the CNID error. Whether doing "step 1" above shall prevent future CNID errors remains to be seen. But "step 2" seems to fix the exisitng CNID db problem, at least in my case.
Curious to see whether this helps others, especially those who are running OSX 10.7 Lion.
Also curious to understand technically why this CNID error occurs.
OSX 10.6.8 (all 6 Macs backing up via Time Machine, some hourly as they are running 24/7, others less frequently and only when in use)
Backup Time Machine is a ReadyNAS Ultra 4Plus running RAIDiator 4.2.19.
Backup share allocated size 2.5 TB.
After reading a bunch of posts about people having uncertain but some success by going into the ReadyNAS file system to manually delete ".AppleDB" stuff and whatever else with root tinkering, I wanted to see whether I could get the ReadyNAS to heal itself.
What seems to work for me in getting rid of this error and restoring full Time Machine functionality (continuation of backup to, as well as looking back into existing sparsebundles) is:
1. in Frontview: System > Performance - UNCHECK "Disable full data journaling" <APPLY>
2. Then: System > Shutdown - CHECK "Check and fix quotas on next boot…", select "Shutdown and reboot device" <APPLY>
After the reboot and when the ReadyNAS came back online, I was able to re-enable Time Machine on each Mac, and things picked up where they left off prior to the CNID error. Whether doing "step 1" above shall prevent future CNID errors remains to be seen. But "step 2" seems to fix the exisitng CNID db problem, at least in my case.
Curious to see whether this helps others, especially those who are running OSX 10.7 Lion.
Also curious to understand technically why this CNID error occurs.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!