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

Hello,

it seems the problem has been resolved. All I did was reboot the ReadyNAS and check the disk. Something was found and fixed, but the probem persisted. Then I booted both my Mac and the ReadyNAS and the problem was gone.

Hi BigRedDog,

What release is your NV running? Is it in share security mode or user mode? Also have you rebooted the Pro since the backup job was created? Did you ever try to run the backup job again and where you accessing the destination share at the same time the backup was occurring?

NV is running current release, I think it was 4.1.6, but I could check.

NV is User mode security and fwiw, as the pro is also, I set the users and uuids to match between machines.

After the backup job was created, I ran the job. I rebooted just before I created the backup job (after I finished configuring the Pro). But not before I ran the job. I Aldo have rebooted several times since I finished the back job.

I have not run the backup job again for the share which gave me the error. I have not been using the share because of the error. I did run other backup jobs though.

I had accidentally scheduled a volume check and scrub to run during the backup (the two items in the volume maintenance section). I thought I set the up then turned the scheduling off. Instead, I left them on, and they ran during the backup. Only once though ;)

BigRedDog wrote:
"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.

Having the same issues here.

Went on holidays in June, when I came back had been upgraded to 4.2.12. All seemed fine, but now getting the CNID DB error, and often things freeze when streaming. Timemachine sometimes can't see drive, yet when I manually check 2 minutes later it works fine.

Ready NAS Pro Pioneer here. 5 x 1.5 TB drives in it. Mac OSX 10.4 running.

I have exactly the same problem on a Pioneer with 4.2.12. Went back from holidays and it started to misbehave like that. Any idea, this is really worrying.

Sacha

slaboure wrote:
I have exactly the same problem on a Pioneer with 4.2.12. Went back from holidays and it started to misbehave like that. Any idea, this is really worrying.

I downgraded to 4.2.11 and everything is working perfectly again. Have also turned off automatic updates to avoid this happening again.

after upgrading Pro BE from 4.2.11 to 4.2.13 I got the same error message when opening time machine.
(at that moment I already had another share from the Pro BE mounted, don't know whether that matters)

I then looked and found this topic, and downgraded to 4.2.11.

I downloaded the Pro BE logs (after the error, and once again after downgrading and opening time machine again),
and saw in afp.log the following error lines that seem related:

afp.log:9978:Aug 18 22:24:45.627137 afpd[3480] {cnid_dbd.c:325} (E:CNID): dbd_rpc: Error reading header from fd (db_dir /c/.timemachine): Resource temporarily unavailable
afp.log:9979:Aug 18 22:24:56.626994 afpd[3480] {cnid_dbd.c:325} (E:CNID): dbd_rpc: Error reading header from fd (db_dir /c/.timemachine): Resource temporarily unavailable
afp.log:9980:Aug 18 22:24:56.627110 afpd[3480] {cnid_dbd.c:411} (E:CNID): transmit: Request to dbd daemon (db_dir /c/.timemachine) timed out.
afp.log:9981:Aug 18 22:24:56.627148 afpd[3480] {file.c:246} (E:AFPDaemon): Reopen volume /c/.timemachine using in memory temporary CNID DB.

also the system.log on the mac seems to contain related error messages.

Aug 18 22:24:34 Hostname kernel[0]: AFP_VFS afpfs_mount: /Volumes/ReadyNAS, pid 826
Aug 18 22:24:34 Hostname [0x0-0xc00c].com.apple.finder[167]: Unexpected reply from backup server - ignored
Aug 18 22:24:34 Hostname /System/Library/CoreServices/backupd[825]: Mounted network destination using URL: afp://ReadyNAS@nas-EA-29-C1.local/ReadyNAS
Aug 18 22:24:34 Hostname /System/Library/CoreServices/backupd[825]: Backup destination mounted at path: /Volumes/ReadyNAS
Aug 18 22:25:05 Hostname hdiejectd[836]: running
Aug 18 22:25:05 Hostname [0x0-0xc00c].com.apple.finder[167]: Unexpected reply from backup server - ignored
Aug 18 22:25:06 Hostname /System/Library/CoreServices/backupd[825]: Disk image /Volumes/ReadyNAS/Hostname_01234567890abcdef.sparsebundle mounted at: /Volumes/Backup of Hostname
Aug 18 22:26:33 Hostname [0x0-0x58058].com.apple.systempreferences[850]: Unexpected reply from backup server - ignored
Aug 18 22:26:36 Hostname [0x0-0xc00c].com.apple.finder[167]: Unexpected reply from backup server - ignoredUnexpected reply from backup server - ignored
Aug 18 22:26:36 Hostname [0x0-0xb00b].com.apple.systemuiserver[166]: Unexpected reply from backup server - ignored
Aug 18 22:26:36 Hostname [0x0-0x58058].com.apple.systempreferences[850]: Unexpected reply from backup server - ignored

I think I have seen the 'Unexpected reply from backup server - ignored' before, but typically at most one at a time.

Axel.

Hi-

I am also seeing this on my NAS. I recently upgraded to the latest 4.2.13 and did a Factory Reset. I can access the /* but if I try to view /media/*/ then the Finder will hang. This is true for all 3 Bonjour services (AFP, CIFS, etc).

I am using a ReadyNas Pro with 4 disks. A quick snippet from the afp.log:

Sep 01 23:11:09.457771 afpd[7958] {volume.c:1850} (I:AFPDaemon): CNID server localhost:4700
Sep 01 23:11:09.994624 afpd[7958] {volume.c:1850} (I:AFPDaemon): CNID server localhost:4700
Sep 01 23:11:12.468497 afpd[7958] {volume.c:1850} (I:AFPDaemon): CNID server localhost:4700
Sep 01 23:11:25.893833 afpd[7958] {cnid_dbd.c:325} (E:CNID): dbd_rpc: Error reading header from fd (db_dir /c/media): Resource temporarily unavailable
Sep 01 23:11:47.352737 afpd[7958] {cnid_dbd.c:325} (E:CNID): dbd_rpc: Error reading header from fd (db_dir /c/media): Resource temporarily unavailable
Sep 01 23:11:47.352881 afpd[7958] {cnid_dbd.c:411} (E:CNID): transmit: Request to dbd daemon (db_dir /c/media) timed out.
Sep 01 23:11:47.352909 afpd[7958] {file.c:246} (E:AFPDaemon): Reopen volume /c/media using in memory temporary CNID DB.

I can access the SMB share via the Go To (command+K) in the Finder and entering the IP address of the NAS. Also, in daemon.log I found:

Sep  1 17:31:50 nas-EA-42-F9 avahi-daemon[3519]: Service "ReadyNAS Discovery [nas-EA-42-F9]" (/etc/avahi/services/readynas.service) successfully established.
Sep  1 17:31:50 nas-EA-42-F9 avahi-daemon[3519]: Service "FrontView on nas-EA-42-F9" (/etc/avahi/services/frontview.service) successfully established.
Sep  1 17:31:50 nas-EA-42-F9 avahi-daemon[3519]: Service "nas-EA-42-F9 (CIFS)" (/etc/avahi/services/cifs.service) successfully established.
Sep  1 17:31:50 nas-EA-42-F9 avahi-daemon[3519]: Service "nas-EA-42-F9 (AFP)" (/etc/avahi/services/afp.service) successfully established.

This leads me to believe that this is due to bonjour broadcasting services on an invalid hostname. I have, as part of the Raidar setup process, set the hostname for the NAS to readynas. nas-EA-42-F9 was the original hostname.

Any thoughts/feedback would be greatly appreciated. If support is interested in the rest of the logs, just let me know where to send them :)

Thanks

Hi-

I should add..

The iMac and ReadyNas are connected with a (Netgear) Gigabit switch. Interestingly enough, my MacBook over wireless (different subnet) has no issues listing the directory contents.

Thanks again

I'm having the same issue with my Pro Business using 4.2.13. I rebooted the NAS and did a scan. Seems fine now but the problem and error message have returned periodically. Not exactly confidence building. Having a further problem where the AFP access is denied via a 'connection failed' message. CIFS access is fine. To fix the AFP access I have to do a complete reboot. Will post this problem separately.

-mw