Problem ASM with bootstrap

[Nerom]

Hello all,
We have the next error message:

* backup.mtorres.com:bootstrap save: cannot start external ASM `nsrmmdbasm' in E:\legato\nsr\mm\: unknown error 193 (0xc1)
* backup.mtorres.com:bootstrap save: E:\legato\nsr\mm\mmvolume6 was not successfully saved
* backup.mtorres.com:bootstrap save: RPC error: RPC cannot encode arguments
* backup.mtorres.com:bootstrap save: save of bootstrap to backup.mtorres.com failed
* backup.mtorres.com:bootstrap 3 retries attempted

We have found the error "unknown error 193" asociated to binaries issue but we have installed Networker and the problem doesn´t disapear.
This problem shows from we moved the Backup server to another machine.

Thanks for all,

 

[TDun]

I have only seen this before on client indexes at version 5 of Networker. It was always a case of a corrupt index. Check your media index.

 

[605]

I agree. This points to a defective media database. Try to
solve it with "nsrck -X". If this fails, you might have to
recover an older bootstrap.

 

[Serbtastic]

I think the question here is how did you move your Networker server to another machine? Specifically, how did you move the media database?

 

[Nerom]

We didn`t move the server, our customer was who do it. I am agree with you it`s possible that the problem is wth media database, I'm going to try to apply a scaveriong procedure and if it doesn´t work try to recover the Media database.

Thanks for all,

Note: when we have any result we contact with you.

 

[605]

Oops, i did not notice that you moved the NW server. This
is possible but you have to follow certains rules that are
not easy to explain.

1. I hope that you moved from Windows to Windows and you
are using the same flavour (2000 or NT). Under certain
circumstances you may even move between Linux and Windows
but this depends on the internal data processing method
of the processor (little endian vs. big endian).

2. I hope you installed NW on the same partition in the
same directory. If not, your bootstrap recovery may fail.
I have never tested this, but this is for sure: the
bootstrap will only recover to the original path.
So at least the source partition must be available and
be formatted with the same file system (FAT or NTFS).

3. Be careful - you need to replace the old server name in
the resource files, but you cannot do this globally. The
reason is that they also contain volume names.
Following the default label templates, they will also
include the hostname, but the volume names must remain
untouched.

Right now, i think that you have not installed NW under the
same path.

 

[ww1977]

I am currently having this problem. I ran nsrck -X and this is what I recieved. How do I fix a problem with the media database.

Also if I recover the bootstrap I should choose one from before I began to expereince this problem right. Or it doesn't matter?

 

[ww1977]

Sorry forgot to include the attachement

nsrck: checking index for 'pluto'
nsrck: WARNING the media database is not responding
nsrck: WARNING: no valid save times for client 'pluto' - cross check not performed
nsrck: /nsr/index/pluto contains 417837 records occupying 48 MB
nsrck: Completed checking 59 client(s)

I'm running legato 6.0 on Sun