I've been trying to virtualize two of our NetWare 6.5 servers. My thought
was to install two new virtual servers and migrate the data from the
physical server to the virtual server. However, I've been running into
problems with the NSS volumes on the virtual servers deactivating
themselves ... not exactly the sort of thing you really want happening to
a production box.

When the pools deactivate, the errors displayed are similar to the

10-05-2007 3:36:54am: COMN-3.25-1092 [nmID=A0025]
NSS-3.00-5001: Pool SERVERNAME/IFOLDER is being deactivated.
An I/O error (20204(zio.c[2260])) at block 23602279(file block
3) has compromised pool integrity.

10-05-2007 3:36:56am: SERVER-5.70.1534 [nmID=B0013]
Device "[V358-A2-D2:0] VMware Virtual disk f/w:1.0" deactivated by
due to device failure.

FWIW, the VMware hosts are running ESX 3.0.2 and are connected to a NetApp
3050C filer via fiber channel. There are about 60 other Linux and Windows
virtual machines in the mix, all connected the same way that are not
exhibiting these sorts of issues.

I contacted VMware support regarding the issue and was told to use
VMDK-based disks rather than mapped raw LUNs. When that server
experienced the same issue the tech suggested I use locally attached
storage (!?). Other than that, the only other suggestion he gave to me
was to wait for a new LSIMPTNW.HAM to correct the problem I was

Obviously, many of you are running NetWare 6.5 on VMware...what's the key
for success?