RAIDiator 4.1.8 ReadyNAS NV+ with Lion - CNID DB error

[mattsmith]

Eagarly awaited the upgrade and installed earlier. Performance is very very slow and connection feels like it's struggling (had zero issues before Lion!)

After a minute or so getting this error displayed:

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

So I've rebooted (Mac and the NV+) but still comes up. Help please.

Thanks guys,
Mat

[dumas1]

I'm seeing this too. No messages actually in the log. And it doesn't say which volume has the problem.

[boots1]

I had this problem with my Pro6. Netgear support SSH'd into the NAS and eventually decided that the CNID db needed to be re-built. This fixed the issue for me. I don't know how to trigger a re-build...

James

[thomaswu]

I am having the same problem after upgrading to 4.1.8 on a ReadyNAS NV+, except that my Mac is still on Snow Leopard, not on Lion.

[treaves]

IS there no one from NetGear that will comment on this? This is a series issue, and is impacting me greatly!

[thomaswu]

I have been waiting for 2 days to be able to write to my ReadyNAS, so I decided to revert to RAIDiator 4.1.7.

However, that does not help---I am still getting the same CNID DB error after the downgrade.

So it appears that the upgrade to 4.1.8 has affected my CNID DB in a way that has rendered my ReadyNAS unusable until I get some external help (which I am still hoping for).

[mdgm-ntgr]

Well update to 4.1.8 again.

Have you opened a tech support case?

[thomaswu]

I did submit a tech support case 2 days ago. It has reached only the 2nd level person so far.

Anyway, downgrading to 4.1.7 and then upgrading back to 4.1.8, appears to have fixed the problem. My shares now mount again normally as read/write.

[hellbent1]

i had this message pop up twice for me tonight. it seems to precede my time machine kicking in. and this is on a FRESH 4.1.8 install on my DUO (i actually moved all my data off and did a factory reset). the message comes up and about 2 or 3 minutes later disappears on me. i just noticed on the second pop up the time machine running shortly afterwards.

edit: i just forced a time machine update and maybe a minute after it had started the error popped up again. i'd attach and image of the error message but have no where to host it at the moment.

[dgulbran]

I am getting the same error... I was going to downgrade to 4.1.7, but if that's not working, I'd rather not go through it. *Super* annoying, since I upgraded under the assumption it wouldn't have issues with Lion! (Because the README said it was for greater Lion compatibility!!)

How do we trigger a rebuild of the CNID db??

I would really like to hear from Netgear on this one... it seems others are having the problem, too.

[mdgm-ntgr]

Those of you that haven't yet, please contact NetGear technical support and open a tech support case. It would be a good idea if you could post your case numbers too.

[hellbent1]

I have logged a ticket with netgear support. the case number is 16698310

[thomaswu]

Have you all tried downgrading to 4.1.7 and upgrading to 4.1.8, which worked for me? It's pretty simple to try, and I did not do a factory default at any point.

My case number was 16665917, and I submitted my system logs, but I terminated the case because the downgrade/upgrade solution worked.

[hellbent1]

my original setup was starting from 4.1.7 and going to 4.1.8 but i was having other problems with that so i went with a factory fresh 4.1.8 install. did you start at 4.1.7, upgrade to 4.1.8, downgrade to 7 and then up to 8 again? that sounds like a lot of stuff one should NOT have to do...

new info. i was doing more testing, etc and found that i'm only getting the error when i've got a mapped CIFS/SMB connection and while uploading (maybe downloading too? not sure) to that my time machine kicks off. i can even force it. start a file transfer to the CIFS share and while that is running force a time machine update. sure enough a few seconds later i get the CIND DB error message. both the CIFS and the time machine continue to work fine at the moment but who knows for how long or if something else is going on i don't know about.

[thomaswu]

Yes, I started from 4.1.7, upgraded to 4.1.8, got the CNID DB errors, downgraded to 4.1.7, still got the CNID DB errors, and then upgraded again to 4.1.8, which solved the problem for me.

It makes sense that you are getting the CNID DB error when Time Machine starts, since Time Machine relies on the AFP connection, and that is the one that requires the CNID DB. I was also getting the CNID DB error whenever I tried to mount a share using AFP. The CIFS/SMB connection is irrelevant.

[sydneydownunder]

Hi,

I can confirm upgrading to RAIDiator 4.1.8 with no problem if you umount, eject, remove all the shared volumes that are automounted on Windows, Mac, Linux... clients.

Do not upgrading RAIDiator 4.1.8 while having active connections from clients.

[boots1]

The upgrade process reboots the device - so no clients are connected when the upgrade actually takes place. Not sure if there's any validity to this but. The only sure thing is that something is foo-baring the CNIDDB upgrade process! Maybe don't attempt a connection once the NAS has rebooted for a night... ?

James

[hellbent1]

was on the phone with support today. they eventually had to escalate the ticket to a higher tier that required me to enable ssh access thru my firewall to the NAS for 'someone' to connect to so they can fix it, i assume. how long do i wait with my DUO open to world?!? i found it very odd that the first tech i worked with had gotomypc (essentially) but the next tier up doesn't (so they say) so they have to connect directly to the device rather than working with me thru my workstation. kind of unsettling... more so, i want to know what they're doing to fix the issue.