Something wrong with the volume's CNID DB using temporary DB

Sounds like (a guess perhaps) there may be a problem with the .AppleDB file in the root of the share. Did you do a clean install of 4.2.12 or upgrade from earlier firmware?

In future, please don't post issues with current firmware in the beta forum. Issues with stable releases should go in the relevant forums e.g. in this case the "Mac / OS X" forum.

BigRedDog wrote:

Brand new Pioneer Pro, with current firmware (4.2.12). Put data on the share - seemed OK. Logged into share via my Mac and got the following message immediately... "Message from server <server name>" Something wrong with the volume's CNID DB, using temporary CNID DB instead. Check server messages for details. Switching to read-only mode. It is an OK message box, which I dismissed. There was a pretty long wait for the share to be shown in Finder. It displayed the <above> message, then opened the share. This share holds my itunes database and media. Any thoughts? I guess I get to call tech support again tomorrow (3rd time in 3 days of ownership - LOL). Maybe they'll call me back this time. Argh.

Hi BigRedDog,

When you have a chance send us your logs and we will take a look. Thanks.

mdgm wrote:
Sounds like (a guess perhaps) there may be a problem with the .AppleDB file in the root of the share. Did you do a clean install of 4.2.12 or upgrade from earlier firmware? In future, please don't post issues with current firmware in the beta forum. Issues with stable releases should go in the relevant forums e.g. in this case the "Mac / OS X" forum.

mdgm,

First, sorry about posting in the wrong forum (and thanks for moving it - I guess). I intended to post in the right forum, but was searching through the forums for a similar problem before posting. I did find one in the beta, but decided not to post on the end - because it was beta. However, when I actually made the post, I must have got my windows mixed up and posted to the beta forum in the end... LOL - so, I get it, and sorry about that. I moderate a couple forums myself, and understand the issue.

Back to the problem... it was a new Pioneer Pro... so, it came with older firmware. Unfortunately, I needed to insert disks and initialize the array (XRaid2) to get to the point where I could get to the UI. I think it shipped with 4.2.7... I guess if it matters specifically, I could go check the logs... but, alas, it was older firmware initially. After the array was initialized and the NAS came online, I immediately upgraded the firmware... but of course, the volume was created by then. After the upgrade to current firmware, 4.2.12, I created shares, configured the NAS, and did a backup (from old NV to new Pro) to get data in the share. Once the backup was complete, I rebooted the NAS, did volume scan to make sure all was well, and mounted the NAS on my Mac, via AFP. It was then that the error occurred.

So, the volume was probably an upgrade, but there was no data on the volume when the upgrade was done. When data was eventually copied, the NAS had current firmware.

Thanks for the help.

Han Solo wrote:
Hi BigRedDog, When you have a chance send us your logs and we will take a look. Thanks.

Logs sent, made email to your attention.

TIA

BigRedDog wrote:
Han Solo wrote: Hi BigRedDog, When you have a chance send us your logs and we will take a look. Thanks. Logs sent, made email to your attention. TIA

OK, we have them now. We will take a look and let you know what we find out.

So, you don't have to go through them line by line... here is the time (as in when the error was found... from the system.log)...

Hope this makes your job a bit easier...
Cliff

Jul 21 00:41:12 RNASPRO afpd[2294]: server_child[1] 15971 done
Jul 21 00:41:12 RNASPRO afpd[2294]: server_child[1] 16024 exited 1
Jul 21 00:41:12 RNASPRO afpd[16025]: AFP/TCP session from 10.0.1.105:52193
Jul 21 00:41:12 RNASPRO afpd[2294]: server_child[1] 16025 done
Jul 21 00:41:19 RNASPRO afpd[16026]: AFP/TCP session from 10.0.1.105:52194
Jul 21 00:41:19 RNASPRO afpd[16026]: dhx login: Cliff
Jul 21 00:41:19 RNASPRO afpd[16026]: uams_dhx_pam.c :PAM: PAM Success
Jul 21 00:41:19 RNASPRO afpd[16026]: uams_dhx_pam.c :PAM: PAM Auth OK!
Jul 21 00:41:19 RNASPRO afpd[16026]: login Cliff (uid 1015, gid 100) AFP3.2
Jul 21 00:41:19 RNASPRO afpd[16026]: CNID server localhost:4700
Jul 21 00:41:23 RNASPRO last message repeated 3 times
Jul 21 00:41:23 RNASPRO cnid_dbd[16027]: Set syslog logging to level: LOG_NOTE
Jul 21 00:41:34 RNASPRO afpd[16026]: dbd_rpc: Error reading header from fd (db_dir /c/MusicLossy): Resource temporarily unavailable
Jul 21 00:41:45 RNASPRO afpd[16026]: dbd_rpc: Error reading header from fd (db_dir /c/MusicLossy): Resource temporarily unavailable
Jul 21 00:41:45 RNASPRO afpd[16026]: transmit: Request to dbd daemon (db_dir /c/MusicLossy) timed out.
Jul 21 00:41:45 RNASPRO afpd[16026]: Reopen volume /c/MusicLossy using in memory temporary CNID DB.
Jul 21 00:42:48 RNASPRO afpd[2294]: server_child[1] 16064 exited 1
Jul 21 00:42:48 RNASPRO afpd[16065]: AFP/TCP session from 10.0.1.105:52202
Jul 21 00:42:48 RNASPRO afpd[2294]: server_child[1] 16065 done
Jul 21 00:42:48 RNASPRO afpd[16026]: CNID server localhost:4700
Jul 21 00:42:48 RNASPRO afpd[16026]: CNID server localhost:4700
Jul 21 00:42:48 RNASPRO afpd[2294]: server_child[1] 16078 exited 1
Jul 21 00:42:48 RNASPRO afpd[16079]: AFP/TCP session from 10.0.1.105:52208
Jul 21 00:42:48 RNASPRO afpd[2294]: server_child[1] 16079 done
Jul 21 00:45:07 RNASPRO afpd[16026]: logout Cliff

Thanks fro the info Cliff. Not sure at the moment why you are getting resource temporarily unavailable messages. Need to try and replicate this issue here to better debug it.

BigRedDog wrote:
...and did a backup (from old NV to new Pro) to get data in the share. Once the backup was complete, I rebooted the NAS, did volume scan to make sure all was well, and mounted the NAS on my Mac, via AFP. It was then that the error occurred.

Can you describe the method you used to do the backup?

Hey Anakin!

My son would be very jealous if he knew I had your ear.

On the Pro, I created a share that matched the share on the NV. I created and ran the backup job from the Pro. The remote machine (old NV) was set up as a Windows/NAS. I used an IP address instead of a hostname. I entered the share name as the path and used my credentials for logging into the remote share. For the local machine (the Pro), I selected the share name I just created.

Then ran the backup manually from the backup jobs page.

Hope that helps. Sorry posting from iPhone and not sure I don't have some typos.

Edit: it might be worth noting, nothing else was accessing either machine during the process. Except for me via Frontview.

Hello!

I Googled my way here as the exact same problem occurred on my Pro Pioneer. Has been running fine for almost a year. I'm running firmware 4.2.12. I'll send the logs, too. Just to let you know that this same issue affects some other users, too.