Environment
Novell iManager 2.7
Novell NetWare 6.5 Support Pack 8
Novell ConsoleOne 1.3.6
Novell Cluster Services 1.8.3
Novell Cluster Services 1.8.4
Novell NetWare 6.5 Support Pack 8
Novell ConsoleOne 1.3.6
Novell Cluster Services 1.8.3
Novell Cluster Services 1.8.4
Situation
Trying to browse the contents of a cluster enabled volume in
ConsoleOne would show what is an apparently empty volume. Doing the
same thing in iManager would return the following error
message
(Error -152) The network operating system has tried to access a volume but
cannot find the volume in the system definition files.
Migrating to a certain node in cluster appeared to resolve the issue. This issue only affected some volumes.
Using Novell Remote Manager would allow you to browse the contents of the volume.
Users where not affected by this issue.
eDir Search Failure
(Error -152) The network operating system has tried to access a volume but
cannot find the volume in the system definition files.
Migrating to a certain node in cluster appeared to resolve the issue. This issue only affected some volumes.
Using Novell Remote Manager would allow you to browse the contents of the volume.
Users where not affected by this issue.
Resolution
Each volume has an attribute known as "host server" this in the
case of a cluster enabled volume should point to the name of the
virtual server object. In the case of this customer it was pointing
to a physical server. This explains why when the volume was mounted
on the particular physical server the administrator could
successfully browse the volume either in ConsoleOne or iManager. but
not when it was mounted on a different server.
To resolve this open ConsoleOne and select the volume object, then in "page options" (bottom left hand side) select the "general" folder and disable it. Close the window and reopen it, so that the changes are applied. Now go to the "other" tab and you will now see the "host server" attribute can be edited, point it to the correct virtual server object, save the changes and re-enable the "general" tab. This should resolve the errors.
To resolve this open ConsoleOne and select the volume object, then in "page options" (bottom left hand side) select the "general" folder and disable it. Close the window and reopen it, so that the changes are applied. Now go to the "other" tab and you will now see the "host server" attribute can be edited, point it to the correct virtual server object, save the changes and re-enable the "general" tab. This should resolve the errors.