Networks

Ask something
Discussion Locked

Netware v3.12/ Volume not mounted

0 helpful
7 replies

by ncebapanda

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I'm using Netware3.12 server with 64MB Ram. When ever I try to mount volume sys: I get the following message: Insufficient memory for directory tables. Volume SYS not mounted.
1.1.39 Cache memory allocator out of available memory.
How can I resolve this as the server is now unusable?

7 replies

by vinnyd

If the server was working in this configuration before, run the vrepair on the sys volumne.

At the command prompt type load vrepair

Then follow the instructions on the screen.

by pierrejamme

TID11192 says: When the user added the data to his VOL1, apparently more directory entries were allocated causing the system to require more memory than was available before the memory above 16MB was registered.

The SYS: volume was automatically mounting when the disk drivers were loaded in the STARTUP.NCF file and before the memory above 16MB was registered with the REGISTER MEMORY command in the AUTOEXEC.NCF. This clone EISA machine would not automatically-register the memory above 16MB.Solutions
Novell instructed the user to do the following to solve the problem:

Move the AUTOEXEC.NCF to the C: partition and load the disk drivers from the AUTOEXEC.NCF instead of the STARTUP.NCF. This kept SYS: volume from mounting automatically.

Put the REGISTER MEMORY command before the MOUNT command so that the volumes could use more than 16MB when mounting. This allowed VOL1 to mount.

EXAMPLE:

In AUTOEXEC.NCF ON C:\

File server name xxxxxx
ipx internal net xxxxx
load disk driver
REGISTER MEMORY xxxxxx xxxxxx
MOUNT SYS
MOUNT VOL1

With drivers other than Adaptec's, it is not always necessary to load the driver below 16MB.

TID2910044 says: The limit has reached the maximum for directory and file that can be create on a netware volume.

The maximum number of files which can reside on a volume will vary according to the directory structure and the number of name spaces supported on the volume.

Solutions

applying latest patches and increasing the block size on the additional volume solved the problem

While neither are exact matches they give you an idea of what has happened to your SYS volume and how to correct.

by q2ggirl

I had a similiar problem with a 3.11 server.

I had to download a newer version of vrepair from Novell's website than what I had and I also had to run bindfix. It took a really long time to run.

Afterwards, I purged all files from the SYS volume. Rebooted the server and the volume mounted as it should.

This discussion is closed to new replies.