[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxaxp::vmsnotes

Title:	VAX and Alpha VMS
Notice:	This is a new VMSnotes, please read note 2.1
Moderator:	VAXAXP::BERNARDO

Created:	Wed Jan 22 1997
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	703
Total number of notes:	3722

368.0. "Sysdisk writelocked during upgrade" by KAOFS::M_COTE (Management Challenged) Fri Mar 21 1997 16:21

    
    Customer is attempting to upgrade 2100 4/275 from 6.2 to 6.2-1h2 
    in preparation for a 4100. During upgrade, customer is prompted
    for target device. Customer's target is DRA0 which is a Jbod
    device off SwXCR. '?' identifies the device as available.
    After selecting Dra0, the procedure again prompts for target
    device. ? shows Dra0 now as write locked. The system boots
    from sysdisk fine. Has anyone seen this problem when booting
    from the Binary CD?


    Thanks,
    mike 





 VMS Pal 5.48-117.

T.R	Title	User	Personal Name	Date	Lines
368.1		EVMS::MORONEY		`Fri Mar 21 1997 16:38`	5
	Is the system disk normally shadowed? (I noticed this updating a system with a shadowed system disk, apparently the CD procedure doesn't issue a $ MOUNT/OVERRIDE=SHADOW, so it gets mounted writelocked. I'll enter a QAR)
368.2	Any Errors?	XDELTA::HOFFMAN	Steve, OpenVMS Engineering	`Fri Mar 21 1997 17:13`	11
	Not an answer, but check the SWXCR firmware version, and upgrade to OpenVMS Alpha V6.2-1H3 for the AlphaServer 4100. (OpenVMS Alpha V6.2-1H2 is below the minimum version for Rawhide...) See MVBLAB::SABLE note 1837.* and 1957.* -- and see what the SWXCR GUI says about the drive status, and check the SWXCR firmware revision. Are these disks part of a shadow-set or other layered software? Any error messages being output at any time during the bootstrap?
368.3	WRONG UPGRADE PROCEDURE	STAR::HAMMOND	Charlie Hammond -- ZKO3-04/S23 -- dtn 381-2684	`Mon Mar 24 1997 14:36`	23
	> Customer is attempting to upgrade 2100 4/275 from 6.2 to 6.2-1h2 > in preparation for a 4100. During upgrade, customer is prompted > for target device. Customer's target is DRA0 which is a Jbod > device off SwXCR. '?' identifies the device as available. > After selecting Dra0, the procedure again prompts for target > device. ? shows Dra0 now as write locked. The system boots > from sysdisk fine. Has anyone seen this problem when booting > from the Binary CD? You DO NOT BOOT THE CD to upgrade from V6.2 to V6.2-1h2. This does not work right and IS NOT SUPPORTED. The correct thing to do is to boot the system and execute VMSINSTAL. This performs an "update". The CD is booted ONLY for new installations. PLEASE read the documentation. (This applieas to all V6.2 hardware releases; it will applie to V7.1 hardware releases too.) If you had got past the write-lock problem (whatever its cause) the procedure would have told you NOT to continue. In the future you may be able to perform this sort of "update" just as you now do major version upgrades, so please continue to READ the documentation for each release BEFORE you try to install it.