If you cannot create an NSS pool or volume, consider these possible causes:
Your server might not have enough free space to create more storage pools or NSS volumes. Ensure you have enough free space to create another NSS storage pool or NSS volume. See Section 7.9, Viewing Partitions on a Device.
Each NSS volume must be part of an NSS pool. If you cannot create the pool at the same time as the volume, try creating a pool to use first.
If you cannot create a pool on a device you can see in NSSMU, NSS might not own the free space you want to use for a storage pool. If the device you want to use is managed by LVM instead of EVMs, NSS does not recognize the device as being available and does not create the pool.
SLES 9 uses LVM, but NSS requires EVMS. The Linux 2.6 kernel prevents multiple volume managers from managing the same device. As a result, EVMS might display free space that it cannot actually manage.
To prevent display of space that is unavailable to EVMS, edit the /etc/evms.conf file to add the device to the exclude list of the sysfs_devices section.
For example, if your hda device is your boot device and contains the root volume, it cannot be used to create pools on. Edit the /etc/evms.conf file as follows:
sysfs_devices {
...
exclude = [hda]
}
To make a device that is being managed by another device manager available to EVMS, you can use one of the following options:
Install SLES 9 with EVMS as the default volume manager
See Mounting Your Root File System through EVMS for more information.
Patch the 2.6 kernel
See BD-Claim Patch for more information.
Convert LVM volumes to EVMS volumes after SLES installation
See Converting to EVMS for more information.
If you cannot create an NSS volume on your NetWare® server, you might not be able to create and mount an NSS volume if you exceed the maximum number of 256 volumes mounted at a time on the server.