• Please review our updated Terms and Rules here

Replacing One of Three Disk Drive VAX 4000

billdeg

Technician
Joined
Nov 18, 2003
Messages
3,885
Location
Landenberg, PA USA
My VAX 4000-200 is in a BA430 enclosure (the larger floor unit).
The drives in "Mass Storage Shelf" of BA430 are:
ISE 2 | ISE 1 | ISE 0 | Tape Drive

I replaced the RF72 in ISE 2. So now I guess I need to initialize the drive, but the directions on this page don't work
http://labs.hoffmanlabs.com/node/193

If anyone is interested I could post more info, see if maybe someone can help.

Bill
 
Last edited:
What do you mean the control panel started "squealing"? Was it flashing the fault LED? Did you try running the built in diagnostics through the >>> SET HOST/DUP/DSSI interface?

What exactly goes wrong when you try to initialize the replacement drive? At a minimum you should only need to use INITIALIZE ddcu: label
 
Yes, I run INITIALIZE ddcu: label, but the drive has no label. I can't go any farther. I am actually documenting a little more clearly exactly what I have so I can answer more detailed questions. The old drive is out of the machine at this point.

Honestly I am trying to understand conceptually what the three drives represent logically, what the system expects, etc.

If you or anyone would like to telnet in, I can PM the info you'd need to take a look, the system is on now, or I can turn it on tomorrow, etc..

Bill
 
Log from Session

Log from Session

Welcome to OpenVMS VAX V6.2

Username:
Username: SYSTEM
Password:
Welcome to OpenVMS VAX version V6.2
Last interactive login on Wednesday, 18-NOV-2015 19:57
Last non-interactive login on Wednesday, 18-NOV-2015 14:23
$ SHOW DEV /PAGE
Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
MPLHST$RCD0: Offline 0
NFS0: Online 0
$1$DIA0: (RF72A) Mounted 0 VMS062 709740 185 1
$1$DIA1: (RF72B) Online 0
$255$DIA5: (RF72) Online 0

Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
MPLHST$RMT0: Offline 0
T885EQ$MIA6: Online 1

Device Device Error
Name Status Count
FTA0: Offline 0
NTY0: Online 0
NTY1: Online 0
OPA0: Online 0

Device Device Error
Name Status Count
RETURN/SPACE=More, PREV/NEXT=Scroll, INS/REM=Pan, SELECT=80/132, CTRL/Z=QuitDevice Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count C
MPLHST$RMT0: Offline 0
T885EQ$MIA6 Online 1

Device Device Error
Name Status Count
FTA0: Offline
NTY0: Online 0
NTY1: Onlin 0
OPA0: Online 0

Device Devic Error
Name Status Count
EZA0: Onlin 0
EZA2: Online 0
EZA5 Online
LAV
PAA0
PT1
PUA0: Online 2
PWIP0: Onlin 0
XQA0: Online 0
*** End *** | PREV/NEXT=Scroll, INS/REM=Pan, SELECT=80/132, CTRL/Z=Quit
$ SHOW DEV DIA0

Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
$1$DIA0: (RF72A) Mounted 0 VMS062 709740 185 1
$ SHOW DEV DIA1

Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
$1$DIA1: (RF72B) Online 0
$ SHOW DEV DIA5

Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
$255$DIA5: (RF72) Online 0
$ INITIALIZE ddcu: label -$ $ INITIALIZE DIA5: label -$ $ INITIALIZE DIA5: BACKUPISE2
%SYSTEM-W-NOSUCHDEV, no such device available
$ MOUNT DIA5:
_Label: TEST
_Log name: TEST
%MOUNT-F-NOSUCHDEV, no such device available
$
 
Welcome to OpenVMS VAX V6.2

Username:
Username: SYSTEM
Password:
Welcome to OpenVMS VAX version V6.2
$ SHOW DEV /PAGE
Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
MPLHST$RCD0: Offline 0
NFS0: Online 0
$1$DIA0: (RF72A) Mounted 0 VMS062 709740 185 1
$1$DIA1: (RF72B) Online 0
$255$DIA5: (RF72) Online 0

Does one need to change the $255 value to match the other drives?

$ SHOW DEV DIA0

Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
$1$DIA0: (RF72A) Mounted 0 VMS062 709740 185 1
$ SHOW DEV DIA1

Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
$1$DIA1: (RF72B) Online 0
$ SHOW DEV DIA5

Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
$255$DIA5: (RF72) Online 0
$ INITIALIZE ddcu: label -$ $ INITIALIZE DIA5: label -$ $ INITIALIZE DIA5: BACKUPISE2
%SYSTEM-W-NOSUCHDEV, no such device available
$ MOUNT DIA5:
_Label: TEST
_Log name: TEST
%MOUNT-F-NOSUCHDEV, no such device available
$

I used "TEST" just to push through.

DIA1: has standalone backup installed, FYI and you can boot to it.

and of course - what is the primary purpose of the drive in storage shelf unit ISE 2

Here is background about my system:
http://vintagecomputer.net/browse_thread_record.cfm?id=608&tid=13

photos, more....
http://vintagecomputer.net/browse_thread_record.cfm?id=608

Bill
 
Last edited:
It should be fairly easy. This what I just did on one my systems right now. I see you posted more information while I was doing that. I'll take a look at that information after I finish this post.

KA640-A V5.3, VMB 2.7
Performing normal system tests.
41..40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..
25..24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..
09..08..07..06..05..04..03..
Tests completed.
>>>SHOW DSSI
DSSI Node 0 (VMSSYS)
-DIA0 (RF31)

DSSI Node 1 (VMSUSR)
-DIA1 (RF30)

DSSI Node 7 (*)
>>>SET HOST/DUP/DSSI 1
Starting DUP server...

DSSI Node 1 (VMSUSR)
Copyright © 1988 Digital Equipment Corporation
DRVEXR V1.1 D 5-MAY-1989 13:18:42
DRVTST V1.1 D 5-MAY-1989 13:18:42
HISTRY V1.0 D 5-MAY-1989 13:18:42
ERASE V1.3 D 5-MAY-1989 13:18:42
PARAMS V1.2 D 5-MAY-1989 13:18:42
DIRECT V1.0 D 5-MAY-1989 13:18:42
End of directory

Task Name? ERASE
Copyright © 1988 Digital Equipment Corporation
Write/read anywhere on medium? [1=Yes/(0=No)] 1
User data will be corrupted. Proceed? [1=Yes/(0=No)] 1
6 minutes to complete.
VMSUSR::MSCP$DUP 5-MAY-1989 13:22:22 ERASE CPU=00:00:02.50 PI=922
VMSUSR::MSCP$DUP 5-MAY-1989 13:22:42 ERASE CPU=00:00:04.15 PI=1858
VMSUSR::MSCP$DUP 5-MAY-1989 13:23:02 ERASE CPU=00:00:05.43 PI=2792
VMSUSR::MSCP$DUP 5-MAY-1989 13:23:23 ERASE CPU=00:00:06.25 PI=3712
VMSUSR::MSCP$DUP 5-MAY-1989 13:23:43 ERASE CPU=00:00:07.05 PI=4632
VMSUSR::MSCP$DUP 5-MAY-1989 13:24:03 ERASE CPU=00:00:07.90 PI=5558
VMSUSR::MSCP$DUP 5-MAY-1989 13:24:23 ERASE CPU=00:00:09.51 PI=6476
VMSUSR::MSCP$DUP 5-MAY-1989 13:24:43 ERASE CPU=00:00:10.74 PI=7382
VMSUSR::MSCP$DUP 5-MAY-1989 13:25:03 ERASE CPU=00:00:12.08 PI=8298
VMSUSR::MSCP$DUP 5-MAY-1989 13:25:23 ERASE CPU=00:00:13.71 PI=9220
VMSUSR::MSCP$DUP 5-MAY-1989 13:25:44 ERASE CPU=00:00:15.71 PI=10146
VMSUSR::MSCP$DUP 5-MAY-1989 13:26:04 ERASE CPU=00:00:16.63 PI=11064
VMSUSR::MSCP$DUP 5-MAY-1989 13:26:24 ERASE CPU=00:00:17.76 PI=11974
VMSUSR::MSCP$DUP 5-MAY-1989 13:26:44 ERASE CPU=00:00:19.28 PI=12880
VMSUSR::MSCP$DUP 5-MAY-1989 13:27:04 ERASE CPU=00:00:20.96 PI=13804
VMSUSR::MSCP$DUP 5-MAY-1989 13:27:24 ERASE CPU=00:00:21.82 PI=14732
VMSUSR::MSCP$DUP 5-MAY-1989 13:27:44 ERASE CPU=00:00:23.03 PI=15664
Erase complete.

Task Name? EXIT

Stopping DUP server...
>>>BOOT DIA0
(BOOT/R5:0 DIA0)

2..
-VMSSYS$DIA0
1..0..

%SYSBOOT-I-SYSBOOT Mapping the SYSDUMP.DMP on the System Disk
%SYSBOOT-I-SYSBOOT SYSDUMP.DMP on System Disk successfully mapped
%SYSBOOT-I-SYSBOOT Mapping PAGEFILE.SYS on the System Disk
%SYSBOOT-I-SYSBOOT SAVEDUMP parameter not set to protect the PAGEFILE.SYS
OpenVMS (TM) VAX Version V7.3 Major version id = 1 Minor version id = 0



Welcome to OpenVMS (TM) VAX Operating System, Version V7.3

Username: SYSTEM
Password:
Welcome to OpenVMS (TM) VAX Operating System, Version V7.3 on node BA215
Last interactive login on Saturday, 14-NOV-2015 17:33
Last non-interactive login on Saturday, 14-NOV-2015 17:27

$ SHOW DEV /FULL DIA0:

Disk $1$DIA0: (VMSSYS), device type RF31, is online, mounted, file-oriented
device, shareable, available to cluster, error logging is enabled.

Error count 0 Operations completed 3071
Owner process "" Owner UIC [SYSTEM]
Owner process ID 00000000 Dev Prot S:RWPL,O:RWPL,G:R,W
Reference count 55 Default buffer size 512
Total blocks 744400 Sectors per track 50
Total cylinders 1861 Tracks per cylinder 8
Host name "VMSSYS" Host type, avail RF31, yes
Allocation class 1

Volume label "OVMSVAXSYS" Relative volume number 0
Cluster size 9 Transaction count 219
Free blocks 160290 Maximum files allowed 37220
Extend quantity 5 Mount count 1
Mount status System Cache name "_$1$DIA0:XQPCACHE"
Extent cache size 64 Maximum blocks in extent cache 16029
File ID cache size 64 Blocks currently in extent cache 15579
Quota cache size 0 Maximum buffers in FCP cache 341
Volume owner UIC [1,1] Vol Prot S:RWCD,O:RWCD,G:RWCD,W:RWCD

Volume Status: ODS-2, subject to mount verification, protected subsystems
enabled, file high-water marking, write-through caching enabled.

$ SHOW DEV /FULL DIA1:

Disk $1$DIA1: (VMSUSR), device type RF30, is online, file-oriented device,
shareable, available to cluster, error logging is enabled.

Error count 0 Operations completed 0
Owner process "" Owner UIC [SYSTEM]
Owner process ID 00000000 Dev Prot S:RWPL,O:RWPL,G:R,W
Reference count 0 Default buffer size 512
Host name "VMSUSR" Host type, avail RF30, yes
Allocation class 1

$ INITIALIZE $1$DIA1: OVMSVAXUSR

$ MOUNT /SYSTEM $1$DIA1: OVMSVAXUSR
%MOUNT-I-MOUNTED, OVMSVAXUSR mounted on _$1$DIA1: (VMSUSR)

$ SHOW DEV /FULL DIA1:

Disk $1$DIA1: (VMSUSR), device type RF30, is online, mounted, file-oriented
device, shareable, available to cluster, error logging is enabled.

Error count 0 Operations completed 58
Owner process "" Owner UIC [SYSTEM]
Owner process ID 00000000 Dev Prot S:RWPL,O:RWPL,G:R,W
Reference count 1 Default buffer size 512
Total blocks 293040 Sectors per track 37
Total cylinders 7920 Tracks per cylinder 1
Host name "VMSUSR" Host type, avail RF30, yes
Allocation class 1

Volume label "OVMSVAXUSR" Relative volume number 0
Cluster size 3 Transaction count 1
Free blocks 292965 Maximum files allowed 36630
Extend quantity 5 Mount count 1
Mount status System Cache name "_$1$DIA0:XQPCACHE"
Extent cache size 64 Maximum blocks in extent cache 29296
File ID cache size 64 Blocks currently in extent cache 0
Quota cache size 0 Maximum buffers in FCP cache 341
Volume owner UIC [SYSTEM] Vol Prot S:RWCD,O:RWCD,G:RWCD,W:RWCD

Volume Status: ODS-2, subject to mount verification, file high-water marking,
write-back caching enabled.

$ DIR $1$DIA1:[000000...]

Directory $1$DIA1:[000000]

000000.DIR;1 BACKUP.SYS;1 BADBLK.SYS;1 BADLOG.SYS;1
BITMAP.SYS;1 CONTIN.SYS;1 CORIMG.SYS;1 INDEXF.SYS;1
SECURITY.SYS;1 VOLSET.SYS;1

Total of 10 files.
 
$ INITIALIZE DIA5: BACKUPISE2
%SYSTEM-W-NOSUCHDEV, no such device available
$

While you can SHOW DEV DIA5: without the leading $255$ you need to include the leading $255$ when you initialize and mount the volume on your system. For example on my system:

$ INITIALIZE DIA1: OVMSVAXUSR
%SYSTEM-W-NOSUCHDEV, no such device available
$ INITIALIZE $1$DIA1: OVMSVAXUSR
$ MOUNT /SYSTEM $1$DIA1: OVMSVAXUSR
%MOUNT-I-MOUNTED, OVMSVAXUSR mounted on _$1$DIA1: (VMSUSR)
 
it's that easy? Just include the leading $255$

INITIALIZE $255$DIA5: vmsbak

One last question - Am I correct that DIA5 is the new / replaced drive? Can I change the 255 to a 1 so all drives match or does that not matter?

OK...one more question - why does this system come with 3 drives? I need to learn more about what you do with three drives to optimize a system like this.
 
$ SHOW DEV
$1$DIA0: (RF72A) Mounted 0 VMS062 709740 185 1
$1$DIA1: (RF72B) Online 0
$255$DIA5: (RF72) Online 0

Does one need to change the $255 value to match the other drives?
Bill

I would probably go ahead and change the drive allocation class to match the other drives just in case that might cause unexpected issues somewhere. I'm not sure where it really matters if you are not running a VMS cluster configuration.

Here is an an example of how to change the drive allocation class through the console interface. On your system it would be node 5 instead of node 1 on my system.

>>>SHOW DSSI
DSSI Node 0 (VMSSYS)
-DIA0 (RF31)

DSSI Node 1 (VMSUSR)
-DIA1 (RF30)

DSSI Node 7 (*)
>>>SET HOST/DUP/DSSI 1
Starting DUP server...

DSSI Node 1 (VMSUSR)
Copyright © 1988 Digital Equipment Corporation
DRVEXR V1.1 D 5-MAY-1989 13:18:42
DRVTST V1.1 D 5-MAY-1989 13:18:42
HISTRY V1.0 D 5-MAY-1989 13:18:42
ERASE V1.3 D 5-MAY-1989 13:18:42
PARAMS V1.2 D 5-MAY-1989 13:18:42
DIRECT V1.0 D 5-MAY-1989 13:18:42
End of directory

Task Name? PARAMS
Copyright © 1988 Digital Equipment Corporation

PARAMS> SHOW ALLCLASS

Parameter Current Default Type Radix
--------- ---------------- ---------------- -------- -----
ALLCLASS 255 0 Byte Dec B

PARAMS> SET ALLCLASS 1

PARAMS> WRITE
Changes require controller initialization, ok? [Y/(N)] Y

Stopping DUP server...
>>>
 
Thank you very much. Tomorrow morning I will initialize the drive, I have an evening appointment and I don't want to leave the system running without being in the room. This really helps me understand things. I want to keep learning more about VAX stuff.
Bill
 
One last question - Am I correct that DIA5 is the new / replaced drive?

Well that should be obvious from the process of physically replacing the drive. When you replaced the drive you physically attached the drive to a control panel with a DSSI node ID plug. If the number on the node ID plug on that control panel is a 5 then the replacement drive would appear as DIA5 on your system. It doesn't matter which of the three slots the drive is installed in, the only thing that matters is the DSSI node ID plug on the control panel connected to the drive.

If it was my system and I had a spare DSSI node ID plug number 2 available I would probably use that just so I had DIA0, DIA1, and DIA2 in my system, unless the system was previously running with a DIA5 and something in the software configuration of the system was hard coded to that somewhere and I wasn't doing a clean installation to wipe everything.
 
I did not notice the ID number when I replaced the drive. I used the cable from the orig. drive, and kept the one that came with the replacement as a spare. Who knows what number it is, it could be 2, but it could be anything. At least now I understand what the numbers represent, thanks.
b
 
I did not notice the ID number when I replaced the drive. I used the cable from the orig. drive, and kept the one that came with the replacement as a spare. Who knows what number it is, it could be 2, but it could be anything. At least now I understand what the numbers represent, thanks.
b

http://vintagecomputer.net/digital/VAX_4000-200/VAX_4000-200.jpg

The Bus ID plug on the left most drive is indeed a 5 in that photo so that drive would be DIA5.
 
On a completely different subject, one note of caution about your system. If there is currently a NiCad battery pack installed inside the H3602 console bulkhead panel attached to the M7626 KA660 module you should remove it immediately, even if it seems fine now. If it hasn't started leaking already it is only a matter of time before it does start leaking and destroying things, which will really ruin your day.

When you remove the bulkhead panel from the chassis you have to remove 4 screws on the back of the panel holding the PCB in place to remove the battery. On the front of the panel you also have to remove the nut on the Ethernet BNC and you might also have to remove the 2 screws on the Ethernet AUI locking bracket to remove the PCB.

Just a couple of days ago I went to fire up my VAX 4000-200 after being idle for a year or so and the power supply would only briefly turn on before shutting down. I though the RF72 might be causing a problem but removing that didn't help. I then pulled the CPU and memory boards and was shocked to realize that I hadn't taken my own advice and left the NiCad pack installed which was starting to leak, although there didn't appear to be any real damage to the H3602 panel yet. The power supply still wouldn't come up with all disks and modules removed from the chassis and just an M9060-YA minimum load module installed. OK, I thought, maybe just some caps on the power supply have died. I then pulled the M9715-AA module behind the panel next to the power supply and noticed strange corrosion on it. Maybe some of the caps on that module went bad and leaked, but I wasn't sure if that would explain what I was seeing. I wondered if a leaking NiCad battery pack could emit any vapors that could cause corrosion beyond the immediate area of the battery pack. Or maybe something in the failing H7874 supply could cause corrosion outside of the power supply itself. I haven't opened up the H7874 supply yet to look for any obvious failures.

In any case now my VAX 4000-200 is dead unless I can repair or replace the dead H7874 power supply and the M9715-AA module. If the leaking NiCad battery pack contributed to any of the failures that is unfortunate and could have been easily prevented.
 
Last edited:
On a completely different subject, one note of caution about your system. If there is currently a NiCad battery pack installed inside the H3602 console bulkhead panel attached to the M7626 KA660 module you should remove it immediately, even if it seems fine now. If it hasn't started leaking already it is only a matter of time before it does start leaking and destroying things, which will really ruin your day.

When you remove the bulkhead panel from the chassis you have to remove 4 screws on the back of the panel holding the PCB in place to remove the battery. On the front of the panel you also have to remove the nut on the Ethernet BNC and you might also have to remove the 2 screws on the Ethernet AUI locking bracket to remove the PCB.

<snip>

In any case now my VAX 4000-200 is dead unless I can repair or replace the dead H7874 power supply and the M9715-AA module. If the leaking NiCad battery pack contributed to any of the failures that is unfortunate and could have been easily prevented.

Sorry to hear yours died, hopefully only temporarily. I was able to locate and remove the battery. There was no corrosion, I assume the battery was dead as the system asks me to enter the date every time I cold boot.

I will let you know how the drive initialization went, assuming I put this complicated processor panel together correctly. I took photos.

Bill
 
I replaced the NICad battery pack and cleaned everything while the system was open. I will post pictures on my site asap.

Next I initialized the new hard drive, using this command:

INITIALIZE $255$DIA5: vmsbak

I initiated a backup to make a bootable image of the primary hard drive. This way if the primary drive fails I have a copy that will boot.

(from page 44 of the OpenVMS System Management Guide : )

dismount/nounload $255$dia5:
(response - "device is not mounted")
mount/foreign $255$dia5:
(response was "..mounted..")
backup /image/ignore=interlock $1$dia0: $255$dia5:

Backup in progress....The back and forth activity of the two drives' lights looks promising.

Thanks for your help.

UPDATE - Works! Done!
b
 
Last edited:
Back
Top