asked on

Production server - Single Netware Server 4.11 Directory Service Not Loading dsrepair errors out with 618 Help!

Tried Dsrepair (automated and local database) Sys:system\dsrepair.log has 8 errors.

File Partitio.nds pos:0000a0, rec...
ROOT object does not have mandatory flags set
Object ID...
Partition Root identified in the wrong partition
Partition id changed frokm 00000 to ffff
object id:
partition root object does not exit.

7 errors on entry.nds

I CAN DELETE THE NDS and start over - there are 55 users. I can give everyone root access for today and later on, can work and fix the rights.

would the login script work if I start over ?

PLS HELP... It is a production server and it needs to be up in a couple of hours

I don't know if it is appropriate to post here, but I am willing to compensate monetarily if some one can call me and walk me through it

I am unable to restore directory services files from the back up. All data files are backed up and is restorable

Thanks
Pat

patp22

ASKER

I had pulled the hard drives out of this server about 18 months back. I put those drives back in and i am able to start the server without directory services error. There are not much changes (as far as user / trustee rights are concerned). Can i some how get the directory files out of this hard drive and use it to fix the current drive on the server ?

deroode

You can make a backup of the old NDS, Create a new tree (with the same tree name) and restore your NDS backup.
You cannot mess with the directory files.
If you really want to be sure, and up and running fast and reliable you should open an incident with Novell, they will remote in and fix things.

patp22

ASKER

i called novell, they wont support old netware version 4.11. They gave me the phone number for arrow tech 888 347 6305. Arrow wants $1000 per incident and they will not guarantee that whether it will be resolved or not ;-(

The old harddrive is from the same server - but 4 year old - so it has the same tree name.

can u pls tell me how to do a backup to c:\ once i have the old drive mounted
and then
how to restore over the problem ds.

would it let me over write it ?. do i have to delete the tree on the bad ds and then recreate before restoring it

Thanks

deroode

Well, The proper way is of course to create a new NDS with the same treename, then restore NDS from tape. If you don't have a backup you can create an NDS backup from the old drive to tape, then put in the production drives, create a new NDS and then restore. Restoring NDS without restoring the filesystem (of which you don't seem to have a backup???) will however not restore trustees.

patp22

ASKER

i have a backup, but it is not netware aware backup - so restoring will not put the trustees back. i can manually add that

so from where i am now, (DS not loading), could you pls list the steps to
(1) delete the existing NDS (pls confirm none of the data or folders will be deleted)
(2) create a new nds - is it done from 'load install' screen
(3) run nwadmin to create users/groups and login scripts ?

are there any other steps ?

Thanks

deroode

Delete NDS:

http://support.novell.com/docs/Tids/Solutions/10013746.html

LOAD INSTALL - DSREMOVE (or NWCONFIG -DSREMOVE for NW5 or higher) | Directory Options | Remove Directory Services from this server. Press ENTER through any errors. Try removing DS again - it should say: "Directory Services has already been removed". The -DSREMOVE switch will remove directory services from a server despite any errors.

Create a new NDS:
LOAD INSTALL - Directory Options - Install Directory Services onto this server

Then use nwadmin to create users, groups, printqueues, scripts etc.

maques

Or you can get JCMD.NLM (http://www.3net.cz/software/ - first one) - or toolbox.nlm from Novell,
With an unloaded DS, rename _NETWARE directory from the command line (to "_NETWARE.OLD" or whatever), then server would start as there were no NDS on it, still you can keep the NDS files.
Optionally can try to create a new _NETWARE directory (after renaming the old) and copy the *.BAK files (there should be 4 of those AFAIR), rename them to *.NDS, then give a try with those.

But I have a feeling that if NDS is corrupted then there could be some hardware error behind this and would/could corrupt other files too, so, I'd consider checking out that too...

ASKER CERTIFIED SOLUTION

maques

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial