FILE NAME: ERRORS.DOC
DATE: 7 Jun 1993
PROGRAM: 2XUPGRDE.NLM v1.10
NETWIRE: NOVLIB Library 6, file 2XTO3X.EXE
System Error Messages
for
NetWare In-Place Upgrade
(2XUPGRDE-1.10)
Key to error message numbers:
o All 1xx messages are critical and cause the upgrade to abort.
o All 2xx messages are non-critical.
o The second digit in each error message indicates the phase that
generated the message. For example:
x0x - NLM initialization
x1x - Phase 1: System analysis
x2x - Phase 2: Disk analysis
x3x - Phase 3: Disk modification
x4x - Phase 4: Bindery
x5x - All phases
NOTE: All references to NetWare v2.1x imply NetWare v2.2 also.
101: An invalid command line parameter was encountered.
Explanation: An unrecognized command line parameter was entered.
Valid command line parameters include /B, /H, /?, /P, and /R.
Allowable syntax for specifying parameters includes three options:
parameters may be preceded by a forward slash (/), a minus sign (-)
or be separated by spaces. Parameters are not case sensitive.
Action: Check for typographical errors and try again.
102: The operating system is unable to get the required resource and/or
process tags to begin the upgrade.
Explanation: The upgrade process was unable to get the necessary
resources to run the upgrade.
Action: Unload all unnecessary NLMs from memory so the required
resources can be freed-up.
103: The new screen for the In-Place Upgrade cannot be opened.
Explanation: The resources needed to open a new screen for the
upgrade process are not available.
Action: Unload all unnecessary NLMs from memory so the required
resources can be freed-up.
111: No disks can be found to upgrade. Ensure that the correct disk
drivers have been loaded. The In-Place Upgrade process is now being
aborted.
Explanation: The upgrade process cannot find any disks that need
upgrading. This situation occurs when disk drivers were not loaded,
or when all of the disks have already been upgraded to NetWare v3.x.
Action: Load the appropriate disk drivers and restart the upgrade
process.
112: No NetWare v2.1x or v2.2 volumes can be found on any of the disks.
Check for disk drivers that are loaded without any disks attached.
The In-Place Upgrade process is now being aborted.
Explanation: Either no volumes were found, or the volumes found were
already labeled as NetWare v3.x volumes. This situation occurs when
incorrect disk drivers are loaded or when hard disks have been
accidently disconnected from their drivers.
Action: Make sure the correct disk drivers were loaded and that the
disks have not already been upgraded. Also check for loose cables to
the hard disks.
113: This hard disk contains more than 8 volumes. NetWare v3.x allows a
maximum of only 8 volumes per hard disk. The In-Place Upgrade
process is now being aborted.
Explanation: NetWare v2.1x allows for a maximum of 16 volumes per
hard disk, while NetWare v3.x is limited to a maximum of 8 volumes
per hard disk.
Action: Use an upgrade method other than this in-place process.
114: Macintosh files were found, but the Macintosh name space module was
not loaded. Load MAC.NAM then restart the upgrade process. The In-
Place Upgrade process is now being aborted.
Explanation: During the System Analysis phase Macintosh files and
folders where found on the disks. The Macintosh name space module,
MAC.NAM, was not loaded before starting the upgrade. Without this
module loaded, the volumes with the Macintosh files will not mount.
If the SYS: volume has any Macintosh files, then the SYS: volume
will not mount during the Bindery phase and the bindery will not get
upgraded.
Action: Exit the In-Place upgrade, load MAC.NAM, then restart the
upgrade. MAC.NAM is usually found on the System 1 or System 2
diskette.
121: The Directory Entry Table cannot be read due to a bad disk block.
The In-Place Upgrade process is now being aborted.
Explanation: The NetWare v2.1x Directory Entry Table (DET) could not
be read from the disk. The disk has a bad block. Without the DET,
files and directories will be lost or corrupted.
Action: Run the NetWare v2.1x VREPAIR utility.
122: The file "DIRSTAMP.SYS" cannot be found. The Directory Entry Table
is either corrupt or it is from a version of NetWare not supported
by this upgrade program. The In-Place Upgrade process is now being
aborted.
Explanation: The file DIRSTAMP.SYS is used to store information
about Macintosh files. This file could not be found when a portion
of the NetWare v2.1x Directory Entry Table (DET) was accessed.
Without this file, the directories cannot be read.
Action: If the DET is corrupt, then run VREPAIR to repair it. Ensure
that you are upgrading from NetWare v2.1x or v2.2 only.
123: The file "DIRSTAMP.SYS" cannot be read. Volume <volume name>:'s FAT
Table is corrupt. The In-Place Upgrade process is now being
aborted.
Explanation: DIRSTAMP.SYS is the first file on every v2.x volume.
If the File Allocation Table (FAT) is corrupt, then this file will
not be read properly. This error message aborts the upgrade,
preventing the paddle wheel from spinning endlessly while in the
Disk Analysis phase. If the FAT is corrupt, then a symptom may be
that only the first 4 KB of each file can be read, causing utilities
to "hang" abnormally after being loaded.
Action: Your server may have some serious hardware problems. Bring
up your v2.x server and get it into a working state before retrying
the In-Place Upgrade.
131: The disk's Partition Table cannot be written to (status = <status
number>). The Disk Modification Phase cannot be completed without
first modifying the Partition Table to recognize NetWare v3.x
partitions. The In-Place Upgrade process is now being aborted.
Explanation: This error occurs after the disk is first written to at
the start of Phase 3. The status indicates the cause of the failure.
If the status is equal to 2 or 3, then no data has been lost.
Otherwise, all data on this disk has been lost.
Action: If you have lost your volumes, restore the disk from your
backups, then upgrade using another upgrade method.
132: The disk which contains the SYS: volume cannot be written to. The
In-Place Upgrade process is now being aborted.
Explanation: The first disk, which contains the SYS: volume, cannot
be written to. The upgrade is aborted. This message is always
followed by message 231.
Action: See message 231.
133: The Hot Fix Redirection Area in the NetWare v3.x disk partition
cannot be created. The In-Place Upgrade process is now being
aborted.
Explanation: A call to the operating system which creates the Hot
Fix Redirection Area has failed. Your hard disk may be faulty.
Action: Make sure your hard disk is still working.
134: The Logical Partition on this disk cannot be opened (status =
<status number>). The In-Place Upgrade process is now being aborted.
Explanation: The disk's Logical Partition, which stores the system
tables and volume segments, cannot be opened. The status indicates
the underlying cause of the error.
Action: Make sure your hard disk is still working.
135: The Mirror Information Table in the NetWare v3.x disk partition
cannot be created. The In-Place Upgrade process is now being
aborted.
Explanation: The table containing disk mirroring information,
located inside the Hot Fix Redirection Area, cannot be created.
Your hard disk may be faulty. Version 1.00 of the In-Place Upgrade
NLM did not create the Mirror Information Table. The v3.1x INSTALL
NLM automatically creates this table if it does not already exist.
Action: Consider replacing your hard disk or performing a low level
format to mark any bad disk blocks.
141: The NetWare v2.1x or v2.2 bindery files cannot be opened. User
accounts, including passwords, will not be upgraded. The In-Place
Upgrade process is now being aborted.
Explanation: At this point, the file system has been upgraded to
NetWare v3.1x, but it has no bindery. The NetWare v2.1x bindery
consists of two files located in the SYS:SYSTEM directory:
NET$BIND.SYS (for objects and properties), and NET$BVAL.SYS (for
property data sets). These bindery files contain the names of users,
their rights, their passwords, etc. One or both of these files could
not be found or opened.
This error can be produced when the server has enough memory to
upgrade the file system, but not enough to mount the SYS: volume
afterwards. This happens when the Permanent Memory Pool and the
Alloc Memory Pool take memory but do not release it back to the
Cache Buffers. Simply rebooting the server to free these memory
pools may solve the problem.
Action: Reboot the server, then restart the upgrade process with the
new /BINDERY option. The /BINDERY option skips directly to the
Bindery phase of the In-Place upgrade. See message #244 for more
details.
151: This NetWare server has insufficient memory to complete the upgrade.
The In-Place Upgrade process is now being aborted.
Explanation: Your server does not have enough free memory to run the
upgrade. Servers using large hard disks or having many directories
may need additional memory when upgrading. (The upgrade process uses
approximately 8 KB of memory for each directory, 3 KB for every 19
directory entries (files, directories, trustee entries), and 2 KB
for each megabyte of your hard disk.)
Action: Temporarily install more memory in your server and restart
the upgrade.
152: This NetWare server has insufficient free hard disk space to
complete the upgrade. The In-Place Upgrade process is now being
aborted.
Explanation: Your server does not have enough free hard disk space
to run the upgrade. You will need about 10% more disk space to
accommodate the NetWare v3.x file system than was required by
NetWare v2.1x. NetWare v3.x directories use up to four times more
disk space than NetWare v2.1x directories. Even more disk space is
needed for a DOS partition; NetWare v4.0 requires a minimum of 5 MB.
Action: Remove non-system files until approximately 10% of the disk
is free, or specify a smaller DOS partition size during the upgrade.
153: The In-Place Upgrade process has been aborted by the user. The In-
Place Upgrade process is now being aborted.
Explanation: During the upgrade process, the user is given the
option to abort the upgrade. This option is given only in Phases #1
and #2. The In-Place Upgrade NLM is unloaded and the user is
returned to the Console prompt (:).
Action: None.
201: The number of megabytes specified on the command line for a DOS
partition is too large. 32 megabytes are being reserved for a DOS
partition.
Explanation: You used the /P parameter on the command line with an
invalid number for the size of the DOS partition. Valid numbers
include 0-32 only, with no fractions. Because the number entered was
greater than the maximum of 32 MB, the maximum was assigned instead.
Action: If you do not want a 32 MB DOS partition, unload the upgrade
process and start over. Do this by pressing <Alt><Esc> to return to
the console prompt; then type UNLOAD 2XUPGRDE.
202: WARNING: Trustee assignments do not get upgraded when using the
/BINDERY option. New trustee rights need to be granted after
upgrading the bindery using this option.
Explanation: The /BINDERY option can be used to upgrade the v2.1x
bindery if the upgrade failed after modifying a disk but before the
bindery phase was completed. In some rare instances, the server has
enough memory to complete the file system upgrade but not enough to
mount the SYS: volume afterwards. The /BINDERY option is provided
for this situation, however, trustee rights are lost for all users
except SUPERVISOR and GUEST. This problem was discovered too late
into the testing cycle to fix it in version 1.10.
Action: Use the NetWare v3.x GRANT utility or the v4.0x RIGHTS
utility to create new trustees after completing the upgrade.
211: The maximum number of upgradable disks (32) has been exceeded. This
disk (disk #<disk number>) will not be upgraded.
Explanation: The upgrade program can upgrade a maximum of 32 disks.
Action: Load 3.1x disk drivers for no more than 32 disks at a time
by physically disconnect the remaining disks. Repeat this process
until all the disks have been upgraded.
212: The SYS: volume cannot be found. Without this volume, NetWare v3.x
will not operate.
Explanation: The SYS: volume was not present on any of the disks.
Both NetWare v2.1x and v3.x require a volume named SYS: in which to
store system files. The upgrade process is not automatically aborted
because some users may want to upgrade disks that were not connected
to the server after the initial upgrade.
Action: After pressing any key to continue, answer "Y" to continue
with the upgrade without the SYS: volume or answer "N" to exit the
upgrade.
213: The DOS partition will be placed on the same EXTERNAL hard disk as
the SYS: volume. Many computers cannot boot from a DOS partition on
an external hard disk.
Explanation: The SYS: volume is on an external hard disk such as a
Disk Coprocessor Board (DCB) or an IDE disk. The DOS partition is
placed on the same disk as the SYS: volume. The requested DOS
partition will still be created, however DOS currently does not
support external hard disks. A DOS partition makes booting a NetWare
v3.x server considerably faster; however, it is not necessary for
NetWare v3.x. A DOS partition of at least 5 MB is required by
NetWare v4.0.
Action: Do one of the following:
* If you have a Novell 386 AE server with a DCB controller, do
nothing. It is one of the few computers which can boot from a
DOS partition on an external DCB disk.
* Complete the upgrade; then add a new internal hard disk for the
SYS: volume and the DOS partition.
* Reconfigure the server before performing the upgrade, placing
the SYS: volume on a internal hard disk, especially if you plan
to upgrade later to v4.0.
221: A directory entry with no parent exists in the Directory Entry
Table. The Directory Entry Table translation process should proceed
normally.
Explanation: A directory was found without a complete path to it.
The directory and its files cannot be accessed.
Action: Do one of the following:
* Run the VREPAIR utility and restart the upgrade.
* Complete the upgrade and run VREPAIR afterwards.
222: Disk #<disk number> cannot be opened. Ensure that its disk driver is
properly loaded.
Explanation: The disk cannot be opened for reads and writes.
Action: Make sure the correct disk drivers have been loaded
properly.
224: WARNING: Directory name "<old directory name>" will be renamed to
"<new directory name>".
Explanation: An illegal directory name was found. NetWare v2.1x
allowed for directory names up to 14 characters long. NetWare v3.x
shortened the length to 12 characters to conform to DOS's 8.3
format. With 8.3 format, directories can have up to 8 characters
before the period (.) and up to 3 characters after the period. If a
name conflict occurs, the directory will be given a numbered
extension starting with ".001".
Action: Make note of the new directory names.
225: WARNING: File name "<old file name>" will be renamed to "<new file
name>".
Explanation: An illegal file name was found. NetWare v2.1x allowed
for file names up to 14 characters long. NetWare v3.x shortened the
length to 12 characters to conform to DOS's 8.3 format. With 8.3
format, files can have up to 8 characters before the period (.) and
up to 3 characters after the period. If a name conflict occurs, the
file will be given a numbered extension starting with ".001".
Action: Make note of the new file names.
231: The new NetWare v3.x partition number cannot be found after writing
it to the disk's Partition Table. This disk cannot be upgraded. The
disk has been restored to its original state BEFORE the upgrade so
no data has been lost. This error may have been produced by faulty
hardware.
Explanation: This error occurs after the disk is first written to at
the start of Phase 3. It has been known to occur on certain faulty
PS/2 model 80 mother boards which handle 32-bit addressing
incorrectly (ECA 048). The following PS/2 mother boards may produce
this message:
Model# Serial# Range
------ ------- --------------
8580 111 600 - 6101499
8580 121 45000 - 49999
8580 121 9000 - 9014999
8580 311 65000 - 6553499
8580 321 92000 - 9215499
Action: Check your PS/2 model 80 mother board's serial number.
Replace your mother board if it has one of the above serial numbers.
After your hardware is working correctly, retry the upgrade.
241: The Logical Partition on disk #<disk number> cannot be opened.
Trustee rights and file owner information on this disk will be lost.
Explanation: The disk's Logical Partition, which stores the system
tables and volume segments, cannot be opened. The bindery has been
upgraded successfully at this point; however, the trustees and the
file ownership information cannot be recorded. The status indicates
the underlying cause of the error.
Action: Reassign file ownership and trustee rights using the FILER
and GRANT commands or using SYSCON.
242: The Directory Entry Table cannot be read as needed to update new
object ID's. Trustee rights and file owner information will be lost.
Explanation: The directory cannot be read into memory. Information
such as file ownership and trustee rights are lost.
Action: Reassign file ownership and trustee rights using the FILER
and GRANT commands or using SYSCON.
243: The Directory Entry Table cannot be written to as needed to update
new object ID's. Trustee rights and file owner information will be
lost.
Explanation: The directory cannot be written to. Information such as
file ownership and trustee rights are lost.
Action: Reassign file ownership and trustee rights using the FILER
and GRANT commands or using SYSCON.
244: The bindery property at offset <offset number> cannot be read.
Explanation: A bindery property could not be read from the file
NET$BIND.SYS. The NetWare v2.1x bindery may have been corrupted or
the NET$BIND.SYS file failed to open. At this point, the file
system has been upgraded to NetWare v3.x, however the 2.1x bindery
and trustee rights have not been upgraded.
Action: From your backups, copy your v2.1x bindery files,
NET$BIND.OLD and NET$BVAL.OLD, into the v3.1x SYS:SYSTEM directory.
Rename these files to NET$BIND.SYS and NET$BVAL.SYS. Next, restart
the In-Place Upgrade NLM and use the /BINDERY option. Finally, use
the v3.1x GRANT utility to restore trustee rights. If the v2.1x
bindery files are corrupt, use a previous backup of the bindery
files.
245: A particular NetWare v2.1x or v2.2 bindery value cannot be written
to the NetWare v3.x bindery.
Explanation: A bindery value read from NetWare v2.1x's NET$BVAL.SYS
could not be written to NetWare v3.x's NET$VAL.SYS. The NetWare
v2.1x bindery may have been corrupted. At this point, the file
system has been upgraded to NetWare v3.x, however the 2.1x bindery
and trustee rights have not been upgraded.
Action: From your backups, copy your v2.1x bindery files,
NET$BIND.OLD and NET$BVAL.OLD, into the v3.1x SYS:SYSTEM directory.
Rename these files to NET$BIND.SYS and NET$BVAL.SYS. Next, restart
the In-Place Upgrade NLM and use the /BINDERY option. Finally, use
the v3.1x GRANT utility to restore trustee rights. If the v2.1x
bindery files are corrupt, use a previous backup of the bindery
files.
246: The random passwords file named "NEW.PWD" cannot be created. No
passwords will be assigned to the users.
Explanation: User passwords cannot be transferred from NetWare
v2.1x's bindery to NetWare v3.x's bindery. New user passwords were
generated, but could not be saved into a file named NEW.PWD in
SYS:SYSTEM. Users are given no passwords because passwords cannot be
recorded.
Action: Manually assign users new passwords after the upgrade has
completed.
247: A random password cannot be assigned to user <user name>.
Explanation: User passwords cannot be transferred from NetWare
v2.1x's bindery to NetWare v3.x's bindery. An attempt to assign a
newly generated password to the user failed. No new password is
given to this user.
Action: Manually assign users new passwords after the upgrade has
completed.
248: The File Server bindery object has been renamed from "<old server
name>" to "<new server name>" to correspond with the server's new
name.
Explanation: The name of the server is stored inside the bindery.
When the v3.x server operating system was loaded, the server was
given a different name than that of the v2.x server. The File
Server bindery object was renamed to reflect the newly given name.
This prevents the SLIST utility from erroneously seeing the old
server name which is no longer available.
Action: If you do not like the server's new name, then simply down
the server and bring it back up again, giving it the desired name.
You may need to change a line inside the AUTOEXEC.NCF file in the
SYS:SYSTEM directory.
249: WARNING: The file NEW.PWD in the SYS:SYSTEM directory already
exists. It has been renamed to "<new name>". Random passwords for
this upgrade session will still be written to NEW.PWD.
Explanation: The file name used to store user's random passwords
already exists. Other NetWare utilities which create NEW.PWD are
NetWare Name Service (NNS) and the Across-The-Wire Migration
utility. The old NEW.PWD file will be renamed to NEWPWD.xxx where
xxx is a numbered extension starting with ".001".
Action: Take note of the name change so the old file can be deleted
if it is no longer needed.
251: The NetWare operating system produced an internal error while
attempting to release the disk device.
Explanation: The upgrade process is unable to give the hard disk
resource back to the operating system.
Action: This may be a symptom of an operating system failure. Reboot
the system and restart the upgrade process.
252: The disk device lock has been revoked by the operating system. This
hard disk may have just failed.
Explanation: The disk device information was temporarily lost by the
operating system. This may have been caused by a hard disk failure.
Action: Make sure your hard disk is still working.
