If a rebranding error is encountered while upgrading a non-VSI OpenVMS system disk to a VSI version of OpenVMS, stop the upgrade, preserve the complete error output, and make a verified backup before changing the disk. Follow the installation and upgrade manual for the exact target OpenVMS release. The following checks are historical service guidance, not a replacement for that release's procedure:

•Confirm the target release's file-system and hard-link prerequisites. Do not convert the system disk or enable features solely because an earlier Avanti topic recommended doing so.

•For V8.4-2L2, check the SYSCOMMON/VMS$COMMON directory aliasing using Section 4.6.2, Checking the SYSCOMMON Directories, in the VSI OpenVMS Alpha Version 8.4-2L2 Installation and Upgrade Manual. If the directory file identifiers differ, do not attempt an ad hoc repair; obtain assistance from your OpenVMS support provider. Use the corresponding instructions for another target release.

Earlier field guidance also suggested using DFU from the OpenVMS Freeware media to analyze or repair the disk. That repair route has not been validated for Avanti 5.1.0 or against the current VSI upgrade procedure. Do not use it on the only copy of a system disk; obtain release-matched support before any repair.