Hi folks,

i've just set up our 2nd OES2 server. As far as partitioning
is concerned, i set it up according to


As soon as i reboot the machine, any previously created (and working!) nss volume
fails to mount during system startup

syslog says
NSSLOG ==> [Error] comnVol.c[2985]
Aug 7, 2008 5:17:30 pm NSS<COMN>-4.10a-660:
Volume DAT not found. Verify Media, Devices, Drivers and power
to subsystem. Try NSS /Activate=DAT and or type NSS /volumes and
verify spelling of the volume
Volume Change State failed. Error = 20801

mounting the volume manually doesn't work either:
# mount DAT
mount: wrong fs type, bad option, bad superblock on DAT,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so


On our other OES2 machine i didn't use EVMS for / or swap. The NSS volume
resides on a second disk on either server and i didn't have any problems
so far with the 1st one. It's used for production for more than 8 months
now. That server is a physical hp Proliant. The 2nd one with the nss problem
runs virtualized under VMWare ESX 3. NSS Storage hasn't been installed during
system installation, i added it later. The system has all current patches

Is there any possibility to get my nns volume working without having to reinstall
the entire system and start over again?

Thanks for helping me out,