× NETGEAR will be terminating ReadyCLOUD service by July 1st, 2023. For more details click here.
Orbi WiFi 7 RBE973
Reply

Re: Lion, 4.2.18, CNI DB error when opening Time Machine sha

tpbrown
Aspirant

Lion, 4.2.18, CNI DB error when opening Time Machine share

Hi there,

I'm running 4.2.18 on my Ultra 4 and Lion on my MacBook. Even with the update I'm unable to mount the Time Machine share in anything but read-only mode.

Chain of events, and logs below. Any guidance would be appreciated! [I've already scanned the forums, restarted AFP, restarted ReadyNAS, restarted my Mac, etc. without change]

Thanks!

~Tim

-
connect to ReadyNAS Time Machine share via Finder->Connect to Server->afp://servername/ReadyNAS:
After authenticating an error message displays "Something wrong with the volume's CNID DB, using temporary CNID DB instead.Check server messages for details. Switching to read-only mode."

On the ReadyNAS itself:
syslog:
Jul 24 11:05:33 nas-home cnid_dbd[17301]: Set syslog logging to level: LOG_NOTE
Jul 24 11:05:33 nas-home cnid_dbd[17302]: Set syslog logging to level: LOG_NOTE
Jul 24 11:05:34 nas-home cnid_metad[17303]: Multiple attempts to start CNID db daemon for "/c/.timemachine" failed, wiping the slate clean...
Jul 24 11:05:34 nas-home cnid_dbd[17303]: Set syslog logging to level: LOG_NOTE
Jul 24 11:05:34 nas-home cnid_dbd[17303]: main: too many CNID db opening attempts, wiping the slate clean
Jul 24 11:05:35 nas-home cnid_dbd[17306]: Set syslog logging to level: LOG_NOTE

netatalk.log:
Jul 24 11:05:25.070126 afpd[17269] {dsi_tcp.c:212} (I:DSI): AFP/TCP session from 10.0.1.21:57288
Jul 24 11:05:25.088372 afpd[3357] {main.c:183} (I:AFPDaemon): child[17268]: exited 1
Jul 24 11:05:25.088791 afpd[3357] {main.c:185} (I:AFPDaemon): child[17269]: done
Jul 24 11:05:33.300733 afpd[17286] {dsi_tcp.c:212} (I:DSI): AFP/TCP session from 10.0.1.21:57290
Jul 24 11:05:33.302661 afpd[17286] {uams_dhx2_pam.c:321} (I:UAMS): DHX2 login: ReadyNAS
Jul 24 11:05:33.533081 afpd[17286] {uams_dhx2_pam.c:210} (I:UAMS): PAM DHX2: PAM Success
Jul 24 11:05:33.535768 afpd[17286] {uams_dhx2_pam.c:653} (I:UAMS): DHX2: PAM Auth OK!
Jul 24 11:05:33.535837 afpd[17286] {auth.c:269} (N:AFPDaemon): AFP3.3 Login by ReadyNAS
Jul 24 11:05:33.562099 afpd[17286] {volume.c:2036} (I:AFPDaemon): CNID server: localhost:4700
Jul 24 11:05:33.719349 afpd[17286] {socket.c:163} (E:AFPDaemon): read: Connection reset by peer
Jul 24 11:05:33.730550 afpd[17286] {socket.c:163} (E:AFPDaemon): read: Connection reset by peer
Jul 24 11:05:34.752274 afpd[17286] {socket.c:163} (E:AFPDaemon): read: Connection reset by peer
Jul 24 11:05:35.764066 afpd[17286] {socket.c:163} (E:AFPDaemon): read: Connection reset by peer
Jul 24 11:05:36.765805 afpd[17286] {socket.c:163} (E:AFPDaemon): read: Connection reset by peer
Jul 24 11:05:37.767748 afpd[17286] {socket.c:163} (E:AFPDaemon): read: Connection reset by peer
Jul 24 11:05:38.769673 afpd[17286] {socket.c:163} (E:AFPDaemon): read: Connection reset by peer
Jul 24 11:05:39.771280 afpd[17286] {socket.c:163} (E:AFPDaemon): read: Connection reset by peer
Jul 24 11:05:40.772775 afpd[17286] {socket.c:163} (E:AFPDaemon): read: Connection reset by peer
Jul 24 11:05:41.774140 afpd[17286] {socket.c:163} (E:AFPDaemon): read: Connection reset by peer
Jul 24 11:05:42.775541 afpd[17286] {socket.c:163} (E:AFPDaemon): read: Connection reset by peer
Jul 24 11:05:43.776987 afpd[17286] {socket.c:163} (E:AFPDaemon): read: Connection reset by peer
Jul 24 11:05:44.778090 afpd[17286] {socket.c:163} (E:AFPDaemon): read: Connection reset by peer
Jul 24 11:05:45.779439 afpd[17286] {socket.c:163} (E:AFPDaemon): read: Connection reset by peer
Jul 24 11:05:46.780349 afpd[17286] {socket.c:163} (E:AFPDaemon): read: Connection reset by peer
Jul 24 11:05:47.782077 afpd[17286] {socket.c:163} (E:AFPDaemon): read: Connection reset by peer
Jul 24 11:05:48.784727 afpd[17286] {socket.c:163} (E:AFPDaemon): read: Connection reset by peer
Jul 24 11:05:49.786190 afpd[17286] {socket.c:163} (E:AFPDaemon): read: Connection reset by peer
Jul 24 11:05:50.787754 afpd[17286] {socket.c:163} (E:AFPDaemon): read: Connection reset by peer
Jul 24 11:05:51.789690 afpd[17286] {socket.c:163} (E:AFPDaemon): read: Connection reset by peer
Jul 24 11:05:52.791589 afpd[17286] {socket.c:163} (E:AFPDaemon): read: Connection reset by peer
Jul 24 11:05:53.792954 afpd[17286] {socket.c:163} (E:AFPDaemon): read: Connection reset by peer
Jul 24 11:05:54.794761 afpd[17286] {socket.c:163} (E:AFPDaemon): read: Connection reset by peer
Jul 24 11:05:54.794870 afpd[17286] {cnid_dbd.c:439} (E:CNID): transmit: Request to dbd daemon (db_dir /c/.timemachine) timed out.
Jul 24 11:05:54.794919 afpd[17286] {file.c:264} (E:AFPDaemon): Reopen volume /c/.timemachine using in memory temporary CNID DB.
Jul 24 11:05:59.803980 afpd[17383] {dsi_tcp.c:212} (I:DSI): AFP/TCP session from 10.0.1.21:57293
Jul 24 11:05:59.804244 afpd[3357] {main.c:183} (I:AFPDaemon): child[17382]: exited 1
Jul 24 11:05:59.806228 afpd[3357] {main.c:185} (I:AFPDaemon): child[17383]: done
Jul 24 11:06:04.821952 afpd[17400] {dsi_tcp.c:212} (I:DSI): AFP/TCP session from 10.0.1.21:57295
Jul 24 11:06:04.822243 afpd[3357] {main.c:183} (I:AFPDaemon): child[17399]: exited 1
Jul 24 11:06:04.858867 afpd[3357] {main.c:185} (I:AFPDaemon): child[17400]: done
Message 1 of 6
tpbrown
Aspirant

Re: Lion, 4.2.18, CNI DB error when opening Time Machine sha

I trashed .AppleDB, .AppleDesktop, and .AppleDouble from /c/.timemachine and it _appears_ to have resolved the CNIB DB error.

Testing now.
Message 2 of 6
jhannah
Aspirant

Re: Lion, 4.2.18, CNI DB error when opening Time Machine sha

Any result here? I'm getting the same error. Read-only.
Message 3 of 6
tpbrown
Aspirant

Re: Lion, 4.2.18, CNI DB error when opening Time Machine sha

Upgrade to the beta.
Message 4 of 6
jhannah
Aspirant

Re: Lion, 4.2.18, CNI DB error when opening Time Machine sha

Sorry, was already on the beta.

Got these errors after upgrading.

Came back to it 12 hours later and seems to have fully sorted itself out -- problems just went away.
Message 5 of 6
mdgm-ntgr
NETGEAR Employee Retired

Re: Lion, 4.2.18, CNI DB error when opening Time Machine sha

Yes the NAS updates the CNID Database. This can take quite some time, particularly if your Time Machine backup includes a huge number of files (which it probably would).
Message 6 of 6
Top Contributors
Discussion stats
  • 5 replies
  • 3091 views
  • 0 kudos
  • 3 in conversation
Announcements