Technical article 102443

Mount fails with "unexpected error: can't read mountList, no such variable"

OpenServer 5.0.0

Written · Last revised

Problem

The command:
# mount -f NFS servername:/filesystemname /mountpoint
works properly, however if I try to use the Filesystem Manager to
mount the same remote NFS filesystem by selecting 'Mount'
the mount fails with this error message:
unexpected error: can't read mountList, no such variable

Solution

This error message is due to a problem with the /opt/K/SCO/Unix/5.0.0Cl/sa/filesystem/filesystemGUI vtcl script.

The problem has been corrected and no longer exists in the /opt/K/SCO/Unix/5.0.2Dp/sa/filesystem/filesystemGUI vtcl script. In other words, this problem no longer exists in SCO OpenServer Enterprise System and SCO OpenServer Desktop System Release 5.0.2.

If you have SCO OpenServer Release 5.0.0, follow these steps to correct the problem:

1. Enter single-user mode.

2. Make a backup copy of your filesystemGUI file:

# cd /opt/K/SCO/Unix/5.0.0Cl/sa/filesystem
# cp filesystemGUI filesystemGUI.orig

3. Edit the filesystemGUI file and look for these two lines:

proc ValidateMountPoint {dialog} { global mountList fsInputs managedHost createDir

Right below them, insert 3 lines _exactly_ as shown below:

if { ! [info exists mountList] } {
       set mountList {}
}

This part of the file should now look like the following:

proc ValidateMountPoint {dialog} {
    global mountList fsInputs managedHost createDir
if { ! [info exists mountList] } {
       set mountList {}
}

Save your changes and exit the editor.

4. Update the Product Database:

Run the Software Manager and select the following software:

SCO OpenServer Enterprise (or Desktop) System --> SCO OpenServer Enterprise (or Desktop) UNIX --> SCO OpenServer Enterprise (or Desktop) System Core OS --> Base Operating System --> Run Time System Administration --> Filesystem Administration --> filesystemGUI package

Then, through the menu, choose the following command:

Software --> Advanced Options --> Update Product Databases

Alternatively, you can use customextract(ADM) to extract the /opt/K/SCO/Unix/5.0.2Dp/sa/filesystem/filesystemGUI file from a Release 5.0.2 distribution CD. Once the new file has been extracted, change its name back to /opt/K/SCO/Unix/5.0.0Cl/sa/filesystem/filesystemGUI. This will replace the defective 5.0.0Cl file with the newer 5.0.2Dp version. Next, update the Product Database (see step 4).

It is also possible to copy the file over from a Release 5.0.2
system over to your Release 5.0.0 system into the 5.0.0Cl
subdirectory structure.  Next, update the Product Database
(see step 4).

See also

customextract(ADM)

From the Xinuos technical article database, record 102443. Reproduced with permission. The original is at www.sco.com/ta/102443, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.