NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
DeltaTee
Jul 22, 2011Aspirant
[4.1.8-T5]: SPARC CNID DB error under Lion AFP [Resolved]
After updating my ReadyNAS NV to RAIDiator 4.1.8-T5 I get the following error when attempting to connect to it via AFP in OSX Lion: "Something wrong with the volume's CNID DB, using temporary CNID DB instead.Check server messages for details. Switching to read-only mode."
Connecting with SMB works properly.
Connecting with SMB works properly.
23 Replies
Replies have been turned off for this discussion
- ChrisMc73AspirantSame here, backups to Time Machine (which I believe is AFP) work fine as well. But when I browse the network in Finder, and connect to the NAS via AFP it only shows the ReadyNAS share, not my other two shares.
I can connect to those shares via CIFS fine, but I want to use AFP. Any ideas?
Whats really odd is my newer MBP can see the shares via AFP (over WiFi) and all the files on the NAS, where my MacPro can't, which is hard wried ethernet (which is what I'm referring to above).
I wonder why this is? - ChrisMc73AspirantOk, I just disconnected, using the little button, and reconnected as a GUEST I guess, and its working on AFP now. So much to learn about these NAS drives and the drive technology.
- snipesAspirantI get the same problem with the x86 4.2.18 release on one of my shares. I am connecting as guest so that tip doesn't help me. Like with the OP, CIFS access works fine and AFP works to 3 other shares I have.
I haven't even upgraded to Lion yet, still running 10.6.8. So it looks like a problem introduced/detected by the new Netatalk version. - mdgm-ntgrNETGEAR Employee RetiredEdit: I think I misunderstood Netatalk version numbers.
- Amadeus2AspirantI have had the same issue which was accompanied by a lack of permission to write (or delete) any files.
I solved this by first rebooting the NAS once more and then rebooting my Mac. I have done both of that and have not had the CNID DB error nor any permission errors since.
Hopefully this helps others, too.
Edit: I just realize this is a thread for the SPARC. My experience (albeit otherwise identical) was on Pioneer. - wybren1971AspirantI have the same problem. Connecting to a share with CIFS is no problem. Time Machine seems to be working. But connecting to a share with AFP results in a CNID DB error.
- FerroAspirant
Amadeus wrote:
I solved this by first rebooting the NAS once more and then rebooting my Mac. I have done both of that and have not had the CNID DB error nor any permission errors since.
this solved for me.
I've a NV+ Sparc.
-upgrade to 4.1.8-T5
-turn off AFP
-turn on AFP
-reboot NV+
-reboot Macbook
all ok, i'm writing to my DMGs inside the NAS - PeterO1AspirantI too got the "CNID DB" error after upgrading, but nothing in the reboot log so presume it was erroneous. I can now access the NAS from Lion, but cannot change or add files or folders in the root directories of my two shares. This occurs both on my laptop running Lion with wireless access, and on my desktop running Snow Leopard with ethernet. The permissions of the shares are indicated as "everyone - no access" and "(unknown) - Read and Write" on my laptop, and as "everyone - no access" and "partner - Read & Write" on my desktop. The permissions don't stick when I try to change them in the Get Info window. I have no problem changing or adding folders or files to the folders that already existed on each share (everyone has Read & Write permissions on both the laptop and desktop).
Turning AFP on and off and rebooting the NAS again as suggested by Ferro did not resolve. Any other advice or suggestions would be appreciated.
Cheers,
Peter O. - dfilerAspirantNV+ was throwing this error with the beta in question.
A whole bunch of rebooting of the NAS and my iMac, along with starting and stopping AFP, eventually fixed the problem. Also fixed the 2MB/sec read read performance. Happy camper now. :)
Edit:
Time machine works again too! - Amadeus2AspirantI believe the reason for not being able to change/write any files is because the OS operates on a copy of the original, so any changes would not actually be done on the NAS. Some people have resolved this by unchecking the 'locked' flag of the drive (CMD-I) but in my view there's a reason that flag is set so I'd not recommend it (admittedly I don't fully understand the reason for it happening in the first place so I'm perhaps overly cautious).
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!