NW 6.5 SP4 NSS SYS volume

[dschaldedfg]

Hi,

dschaldedfg wrote:
> >
> > Yes I understand that we should not be running SP4, this was my first
> > time in the environment, hopefully we can boost that if we can get the
> > server to rebuild. That being said I saw another message about doing a
> > NSS /poolrebuild /purge is that something that we should be running as
> > well? Also I have seen where we need to first need to run the following
> > commands
> > server -ns > startup > loadstage 1 > loadstage 2 > nss /poolrebuild=sys
> > /purge does that sound correct? I might be back on the site or try
> > working through this with the person by phone so would like to make it
> > as simple as possible.

In your case, it really shouldn't matter either way. The poolrebuild
should run just fine from the prompt you're seeing when the server boots
up as it does now normally, and the /purge shouldn't be necessary to get
it back again.

CU,
--
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
Untitled Document

Okay I understand that we don't need to be using the /purge command along with the nss /poolrebuild=sys, is there anything else that we need to do once this runs, and if it errors again would you have any other suggestions as to how we might be able to get this server working again? Or should we try to follow TID # 3338221 and see if we can remove the crashed server from the tree, and try to reinstall that server into its own tree in an attempt to pull the data off that Vol1? That right now seems to the be the important part, they don't seem to be overly worried about how eDirectory is synching right now. Thank you,