Netware 5 server will not load nss volume
Hello all
I was portlocking my server for a server migration to a new platform and hardware. The current server was running NW5 and when I started the process of the portlock I received a bad superblock error. I aborted the operation and reboot the server. The sys volumes loaded but the nss volume associated with the NSS drive did not mount. I tried a mount all to no avail. Any thoughts?
Sincerely
Lost in Cyberspace
I was portlocking my server for a server migration to a new platform and hardware. The current server was running NW5 and when I started the process of the portlock I received a bad superblock error. I aborted the operation and reboot the server. The sys volumes loaded but the nss volume associated with the NSS drive did not mount. I tried a mount all to no avail. Any thoughts?
Sincerely
Lost in Cyberspace
I'm guessing christopadilla is referring to one of the Portlock Software packages, presumably to back up the NetWare box prior to doing some kind of unspecified migration.
I don't think Portlock provides migration-specific tools, so unless it was one of their products that, for example, migrates traditional FAT to NSS, the process shouldn't have been invasive, and shouldn't have damaged anything, so unless christopadilla says otherwise, I think the "portlocking" was incidental to the problem. It would be nice to know what Portlock software was being used, though.
So, as PsiCop asked already: christopadilla, we need to know more about the server (version/SP) and the disk/volume configuration, and what errors you're now getting, to help more. NSS SYS: volumes were not available with NW5.0, so if it was 5.0, it makes sense that the SYS: vol would be unaffected by an NSS issue, but it's best not to gues...
Also, was the bad superblock error from the Portlock software or was it from a NetWare service? Did you make note of the >exact< error message, and if so, what was it?
I don't think Portlock provides migration-specific tools, so unless it was one of their products that, for example, migrates traditional FAT to NSS, the process shouldn't have been invasive, and shouldn't have damaged anything, so unless christopadilla says otherwise, I think the "portlocking" was incidental to the problem. It would be nice to know what Portlock software was being used, though.
So, as PsiCop asked already: christopadilla, we need to know more about the server (version/SP) and the disk/volume configuration, and what errors you're now getting, to help more. NSS SYS: volumes were not available with NW5.0, so if it was 5.0, it makes sense that the SYS: vol would be unaffected by an NSS issue, but it's best not to gues...
Also, was the bad superblock error from the Portlock software or was it from a NetWare service? Did you make note of the >exact< error message, and if so, what was it?
ASKER
You are correct on the Portlock defintion, I am using the cloning product. I apologize for not clearing that up in my post. We are running NW5.0 sp3. The sys volume is a traditional volume. It mounts without a problem. The NSS volume mounts but not with Vol1, my data drive.
The original error was in Portlock regarding the bad superblocks. The exact error was Bad Superblocks found.
My question is there any netware utils that I can to reactivate the volume again?
Thanks
The original error was in Portlock regarding the bad superblocks. The exact error was Bad Superblocks found.
My question is there any netware utils that I can to reactivate the volume again?
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If the SYS: Volume mounted (not "loaded" - drivers load, Volumes mount), that suggests that the disk subsystem driver is loading. Assuming that the SYS: Volume is on the same physical drive/array and controller as the other Volumes that won't mount. Is that the case, or are the other Volumes on a different drive/array or controller?
What are the *exact* error messages when you try to mount the other Volumes?
Is the SYS: Volume FAT or NSS?
NetWare v5.0 or v5.1?
What Support Pack level of NetWare?