Came in after the weekend to discover one of our servers has crashed. Tried restart but just get NSD error. rebooted the box, still get NSD error. Suspected a particular mail file so tried nupdall mail\mailfile.nsf, this runs the recovery manager against all mail files then NSD error again!. Which doesnt sound correct.Error seen on console “Recovery manager: Database instance ID not found for what was " suspect mail ifle location”
This is getting a bit more urgent since have a site down now. Any help appreciated.
It seems odd that a DB would stop a whole server from running, but never say never! What types of updall have you tried? i.e. have you tried
Load updall databasename -r
and
Load updall databasename -x
FYI: nupdall would just fix index problems on the DB. From the error message relating to the DB UNID, I am not sure that updall will help too much. If there is an actual DB corruption, run FIXUP on it. Check Domino Admin help for console commands and switches (you can run fixup while the server is shutdown from windows command line).
If fixup doesn’t clear the issue, try temporarily moving the DB off the server - can you then start the server? If so, you’ve proved it is the DB at fault. If you fixup/remove DB, and server still errors, you have a bigger problem…
Thank you for your responses. The NSD was sent to IBM who helpdes diagnose a single mail ifle was causing the problem. The fix was to change the note.ini to not perform transaction logs, re-name the trans logs folder.Then a ncompact could be performed on the offending database. The server was started, allowed to complete the startup then re-started to update the trans logs entries inthe notes.ini. The trans log folder ws re-created by the 2nd server startup and the issue was resolved!.