Conference iosg::all-in-1_v30

1284.0. "%A1-E-NOANS after I aborted 3.0 upgrade" by DENVER::BAILEYR (OICU812!) Thu Aug 20 1992 23:36

I was in the process of upgrading from 2.4 US ENGLISH to 3.0 US ENGLISH 
when the upgrade encountered a corrupt save-set (A1030.I) on the disk I was
using for the distribution.  Turns out the original save-set on the dist.
tape was fine (neither here nor there at this point). 
.
.
%VMSINSTAL-I-RESTORE, Restoring product save set H ...
%VMSINSTAL-I-RESTORE, Restoring product save set I ...
%BACKUP-E-READERRS, excessive error rate reading DJA30:[A1030]A1030.I;1
-RMS-F-RER, file read error
-NONAME-W-NOMSG, Message number 00000000
%BACKUP-I-SPECIFY, specify option (QUIT or CONTINUE)

BACKUP> continue
.
.
So I watched from another terminal as the error count on DJA30 went crazy and 
I decided to abort the upgrade via a CTRL/Y.

After several minutes (cleanup) the VMSINSTAL procedure finally finished 
with the %VMSINSTAL-E-INSFAIL msg.

In the meantime I obtained another copy of A1030.I and verified the REST of 
save-sets and tried the upgrade again.
.
.
* Which option do you wish to perform [1]:<cr>

    This is an UPGRADE of ALL-IN-1 V2.4 to ALL-IN-1 V3.0

%A1-E-NOANS, Could not find OA$BUILD:A1LINK.ANS

                             ***CAUTION***
   The installation cound not determine the state of your system. If you
   have a MULTI-LINGUAL system you must upgrade all additional languages
   after you have upgraded your base system  You will not be able to use
   your additional language systems until they have been upgraded to the
   same version as your base system
 
* Does this product have an authorization key registered and loaded [YES]?
.
.
At this point I bailed out with another CTRL/Y.  Thinking the first upgrade 
attempt may have changed some directory pointers, I decided to reboot and 
have run into the same wall.  Looks like [ALLIN1]SOURCES.DIR got renamed to
[ALLIN1]SOURCES_SHARE.DIR during the "upgrade".  But if I "bailed out" of
the installation, shouldn't the installation have renamed SOURCES_SHARE.DIR 
back to SOURCES.DIR?  Perhaps it was due to the point at which I killed the 
installation.

Would it be easier to restore the OA$DATA/OA$LIB disks back to their 
original condition and start COMPLETELY over, or are there some tricks 
someone has up their sleeves?  We have the luxury of performing the upgrade 
on a non-production system, so it's not the end of the world to have to 
restore, just an inconvenience.

So far:  DIAMOND = 1
              me = 0

Randy

    Randy,
    
    What about Installation Guide Part 1 Chapter 9 entitled "installation
    errors and failure" specifically section 9.3 ?
    
    It talks about the SOURCES directory and describes the situation
    you are reporting.
    
    Regards,
    
    Andrew.D.Wicks