My rig:late 2011 iMac 27inch 3.1Ghz Quad Core i5 running OS X LionReadyNAS NV+ RAIDiator 4.1.84x1tb Hitachi drivesI'm having an issue whenever I try to use AFP on the ReadyNAS NV+. The problem just started happening out of the blue. I upgraded to RAIDiator 4.1.8 several weeks ago and never had a problem. The error i'm now getting is "Something wrong with the volume's CNID DB, using temporary CNID DB instead". Time machine still works perfectly and my back-ups are completing without any errors. I've read about this issue being a problem with netatalk, but I have no idea how to troubleshoot the issue or even how to restart netatalk. For now I'm connecting with CIFS. I might just stay with CIFS and disable AFP is I can't get this issue resolved. Thanks in advance for your help. It's greatly appreciated.

Can somebody at least explain how to restart netatalk?? I'm totally in the dark here.

I would suggest you open a tech support (http://www.readynas.com/support) case. Please post your case number.

I am experiencing the same issue, this is my first attempt at accessing the ReadyNas via AFP after the 4.1.8 update and my new machine is running Lion. I was able to do a time machine backup ok. But when I try to access my AFP share it gives the CNID DB error. Does anyone have a solution to make this go away and start working again?

mdgm,Thanks that appears to be what was going on as this morning I was able to mount the volume in read write mode and everything is working as expected. Thank you for the prompt and informative reply.

CNID DB error using AFP in Lion | NETGEAR Communities

36 Replies

Replies have been turned off for this discussion

CaryTheLabelGuy
Aspirant
Dec 23, 2011
Can somebody at least explain how to restart netatalk?? I'm totally in the dark here.
mdgm-ntgr
NETGEAR Employee Retired
Dec 24, 2011
I would suggest you open a tech support (http://www.readynas.com/support) case. Please post your case number.
eightpointacres
Aspirant
Jan 08, 2012
I am experiencing the same issue, this is my first attempt at accessing the ReadyNas via AFP after the 4.1.8 update and my new machine is running Lion. I was able to do a time machine backup ok. But when I try to access my AFP share it gives the CNID DB error. Does anyone have a solution to make this go away and start working again?

mdgm-ntgr

NETGEAR Employee Retired

Jan 08, 2012

eightpointacres:

yoh-dah wrote:
The AFP service in 4.1.8 updates the CNIB DB on first access, and during that access, writes are disabled on the share. If you have a ton of files in that share, it may take awhile to update the DB. Once the update process is complete, you should have full read/write access to the share.

eightpointacres
Aspirant
Jan 08, 2012
mdgm,
Thanks that appears to be what was going on as this morning I was able to mount the volume in read write mode and everything is working as expected. Thank you for the prompt and informative reply.
spie
Aspirant
Jan 09, 2012
I'm confused. I have this issue with the CNID DB and opened a case at netgaer support. But it seems, that netgear support is not able to provide a solution. Is this possible?
mdgm-ntgr
NETGEAR Employee Retired
Jan 09, 2012
spie, Is this with your Ultra?

I would suggest you start a new thread with your case number as it's likely to get more attention.
macgupta
Aspirant
Jan 25, 2012
I got the CNID DB error only after a couple of weeks after upgrade to OS X Lion and RAIDiator 4.1.8
Hostname: nas-01-2E-17

Model: ReadyNAS NV+ [X-RAID]
Serial: 000da2012e17
Firmware: RAIDiator 4.1.8 [1.00a043]
Memory: 1024 MB [2.5-3-3-7]

Fortunately, rebooting the NAS solved the problem.
But if it proves necessary, how do I manage the Time Machine (ReadyNAS) volume by ftp?
sphardy1
Apprentice
Jan 28, 2012
macgupta wrote:

But if it proves necessary, how do I manage the Time Machine (ReadyNAS) volume by ftp?

You can't - it is only accessible via AFP
nealjane
Aspirant
Feb 15, 2012
im having the same issue as well with our work nv+,

it seems to appear about 1 a week - CNIB DB error message.

ive restarted the server and it then goes away for a while - We cant go on with is its becoming a big issue as its being used as our work server...