Something wrong with the volume's CNID DB (16910762)

[wwalkersd]

Reference tech support case 16910762

In the evolving saga of upgrading my NV+ to 4.1.8 (which started back when I tried up upgrade to 4.1.7, see the saga here: http://www.readynas.com/forum/viewtopic.php?f=65&t=47494), I think I've got it down to one remaining issue, which is Mac-specific. When I try to access my one non-home share ("Family") over AFP, I get a dialog saying:

"Something wrong with the volume's CNID DB, using temporary CNID DB instead.Check server messages for details. Switching to read-only mode."

and I only have read-only access to the share, which is rather useless.

I saw a tip here about mounting the share under CIFS, and then using the terminal to access the share and renaming the .AppleDB file. I tried that, and the only hidden files I can find at /Volumes/Family-1 are .DS_Store, .TemporaryItems, and .vbt5. I AM mounting the share via clicking on "WalkerNAS (CIFS)" in the finder window sidebar. Do I get different results via "Connect to Server"?

I've tried rebooting. I've tried turning off AFP, rebooting, and turning AFP back on. I've tried running a file system check. I've tried changing the default access mode to the share over AFP to read/write, rather than "no access" with write access allowed for my group. I'm fresh out of ideas. I've sent my logs to Tech Support, but they haven't gotten back to me yet.

Do any of you wizards have anything else I can try? Thanks in advance for your help!

[Ex Chemist]

I'm having the same problem on a ReadyNAS Duo. Problem started three days after upgrading to 4.1.8. I received a message from Time Machine (Lion version) that it needed to wipe the previous backups and create a new one. The backup failed about 1/4 the way through and now I get this error whenever I try to mount the share or use Time Machine from any Mac computer, including those running Snow Leopard.

Please help!

[stvsimons]

First problem is you are attempting to rely on a hobbyist product - ReadyNAS support is as good as the product's performance - ps-poor. Otherwise what you read will fix your problem, but you won't be able to SSH into the box unless you've added a hack or plugin to enable SSH and I was unable to get the AppleDB directory to appear in CIFS either. Fortunately you can accomplish the same thing by enabling FTP within the Admin Services panel, then got to the Shares panel and enabled read/write FTP for the Share(s) with the problem (you can set either anonymous or user login - if you aren't using FTP normally you'll want to turn it off when you are done). Once you apply that, connect to your NAS via FTP using the same credentials you use to login via AFP (guest or user/password). If you are using a Mac it's easy with Transmit, Fetch, etc., or you can do it from Terminal via command line - you'll just need to now how to use FTP via command line. Once you connect via FTP, you will see a directory per Share, cd into the share directory and there will be a .AppleDB folder (if using an FTP application you may need to turn the option to view 'invisible' files on - stuff that starts with '.'). Be sure you are not logged in via AFP to that share, then delete the directory - the OS will recreate what's missing when you log in via AFP next).

[wwalkersd]

I wish I'd known about that tip to access via FTP. Tech support was not clear at all on how I was supposed to find that .AppleDB folder, and as you say, it won't show up under either AFP or CIFS. I had previously installed the EnableRootSSH add-on, but hadn't reinstalled it since doing a factory default and upgrading to 4.1.8. I was surprised to find that I could still connect via SSH! Getting rid of the .AppleDB folder, and then resetting the permissions on all the files in the share from FrontView, solved the issue for me.

[mdgm]

Unless you reinstalled the EnableRootSSH add-on or you restored a config backup from before the factory reset then you wouldn't be able to connect via SSH.

[wwalkersd]

Unless you reinstalled the EnableRootSSH add-on or you restored a config backup from before the factory reset then you wouldn't be able to connect via SSH.

Ah, that's it, then. I restored a config backup.

[skindoc]

All. Had same problem after upgrade and went into aFP settings turned off, applied and turned on again and it worked. Can copyand paste again to from said share from my macbookair.