Follow the OpenVMS VAX Version 7.3 Upgrade and Installation Manual AA?QSBQD?TE http://h20565.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c04623149&a… <http://h20565.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c04623149&lang=en-us&cc=us> Section 3 takes you through the basics on how create a new disk. I used the same procedure just last week. Good Luck. > On Aug 7, 2015, at 10:26 AM, Holm Tiffe <holm at freibergnet.de> wrote: > > Hi, > > I've got an VAX4000/300 eqipped with an TK70, 2x RF31, 1xRF71 disks, > and an CQD-200/TM. > I've connected an toshiba Xm5701 drive to the SCSI Bus and the machine sses > it as DUA3. I have a VMS7.3 CDROM and want to install it on one of the > disks. > I've read some documents on HPs website but it isn't clear to me > how to boot the cdrom correctly, there is root 1 mentioned. > What bootflag must entered, B/R5:10000000? > ..in the case w/o the R5:10000000 I get a $ Promt finally (here I habe to > read further). With the bootflag the System is complaining that dua3 is > write protected (it is the cdrom)... > > What's the correct way to install VMS on that machine? > > Regards, > > Holm > -- > Technik Service u. Handel Tiffe, www.tsht.de, Holm Tiffe, > Freiberger Stra?e 42, 09600 Obersch?na, USt-Id: DE253710583 > www.tsht.de, info at tsht.de, Fax +49 3731 74200, Mobil: 0172 8790 741 >

Having the CDROM write protected is normal for read-only media. The target drive needs to be write enabled. Before you boot the CD, list the disks you have.

Choose a disk that is unused/empty. Once you get the $ or $$$ prompt, you need to restore the save from the CDROM to your target disk using BACKUP. My installation looked like this. DKA700 is the VAXVMS073 CDROM. DKA0: is the unused disk. Both disks are on the SCSI bus. During the restore, control-T shows the progress. Once I finished the restore of the OS to the new disk, booting from that disk automatically starts the rest of the install process. ------------ $$$ backup/image/verify dka700:vms073.b/save dka0: Restoring file: DKA0:[VMS$COMMON.SYS$LDR]FYDRIVER.EXE;1 Saveset volume:1, saveset block:71 (32256 byte blocks) Restoring file: DKA0:[VMS$COMMON.SYS$LDR]SYSLOA1302.EXE;1 Saveset volume:1, saveset block:143 (32256 byte blocks) Restoring file: DKA0:[VMS$COMMON.SYSMSG]CLIUTLMSG.EXE;1 Saveset volume:1, saveset block:1260 (32256 byte blocks) %BACKUP-I-STARTVERIFY, starting verification pass $$$ log

As Antonio mentioned, the condist VAXVMS073 normally boots into standalone backup mode. The only application that runs is BACKUP. if you boot (BOOT/R5:10000000 DKA700:)

You get a bit more capability to handle disks. You can mount the disks and verify they are accessbile. If you use dump, specify reasonable start and end blocks as interrupts don?t work (!) $set noverify Installing required known files... Configuring devices... System time is: 26-JUL-2015 00:11:19.97 Enter Yes to the next question to leave the system time unchanged (the system clock continues to run unaffected) Enter No to set a new system time Enter ? to redisplay the time * Is this correct? (Y/N/?) y ******************************************************************** You can execute DCL commands and procedures for various "standalone" tasks, such as backing up the system disk. Please choose one of the following: 1) Execute DCL commands and procedures 2) Shut down this system Enter CHOICE or "?" to repeat menu: (1/2/?) 1 WARNING -- The normal OpenVMS startup procedure has not executed. Some commands and utilities will not work as documented. COMPAQ does not support PRODUCT INSTALL and other PRODUCT operations in this environment. Enter DCL commands -- Enter "LOGOUT" when done. When you enter "LOGOUT" a logout message will be displayed, and you will be returned to the menu. $$$ Note the different prompt. $$$ mount/fore dka400: %MOUNT-I-MOUNTED, HD1025 mounted on _DKA400: $$$ sh dev dka400:/full Disk DKA400:, device type SEAGATE ST15230N, is online, allocated, deallocate on dismount, mounted foreign, file-oriented device, shareable, error logging is enabled. Error count 0 Operations completed 5 Owner process "STARTUP" Owner UIC [1,4] Owner process ID 00000023 Dev Prot S:RWPL,O:RWPL,G:R,W Reference count 2 Default buffer size 512 Total blocks 8386733 Sectors per track 111 Total cylinders 3977 Tracks per cylinder 19 Volume label "HD1025" Relative volume number 0 Cluster size 0 Transaction count 1 Free blocks 0 Maximum files allowed 0 Extend quantity 0 Mount count 1 Mount status Process ACP process name "" Volume Status: Unknown ACP type. $$$ > On Aug 7, 2015, at 1:04 PM, Holm Tiffe <holm at freibergnet.de> wrote: > > Jerry Weiss wrote: > >> Having the CDROM write protected is normal for read-only media. The target drive needs to be write enabled. Before you boot the CD, list the disks you have. > > Yes, it's vnormal that the CDR is ro.. > > I have the following devices: > > du3 .. CDROM > and DISK0$DIA0 (RF31) > and DISK1$DIA1 (RF31) > and DISK2$DIA2 (RF71) >> >>>>> sh device >> >> Choose a disk that is unused/empty. >> >> Once you get the $ or $$$ prompt, you need to restore the save from the CDROM to your target disk using BACKUP. >> >> My installation looked like this. DKA700 is the VAXVMS073 CDROM. DKA0: is the unused disk. Both disks are on the SCSI bus. >> >> During the restore, control-T shows the progress. >> Once I finished the restore of the OS to the new disk, booting from that disk automatically starts the rest of the install process. >> >> ------------ >> >> $$$ backup/image/verify dka700:vms073.b/save dka0: >> Restoring file: DKA0:[VMS$COMMON.SYS$LDR]FYDRIVER.EXE;1 >> Saveset volume:1, saveset block:71 (32256 byte blocks) >> Restoring file: DKA0:[VMS$COMMON.SYS$LDR]SYSLOA1302.EXE;1 >> Saveset volume:1, saveset block:143 (32256 byte blocks) >> Restoring file: DKA0:[VMS$COMMON.SYSMSG]CLIUTLMSG.EXE;1 >> Saveset volume:1, saveset block:1260 (32256 byte blocks) >> %BACKUP-I-STARTVERIFY, starting verification pass >> $$$ log > > > I've booted the CD w/o any bootflag in R5 to the $ prompt. > , it asks for the date/time and displays the devices like above > (DISK0$DIA0 but DU3) and asks if that list is correct, yes it is. > After that I've issued: > > $ backup/image/verify dua3:vms073.b/save disk0$dia0: > (dia0 only doesn't work) > > I've get a long list about many files (from the cdrom) > and SYSTEM-F-VOLINF, volume is not software enabled > > > A while ago I've reformated an tested the 3 DSS > I disks with the firmware on them, the disks are all empty. > I think here is a step missing, Do I have to initialize them first? > The disks are ok, the veryfy programs on them saying that.... > > Regards, > > Holm > -- > Technik Service u. Handel Tiffe, www.tsht.de, Holm Tiffe, > Freiberger Stra?e 42, 09600 Obersch?na, USt-Id: DE253710583 > www.tsht.de, info at tsht.de, Fax +49 3731 74200, Mobil: 0172 8790 741 >

On 2015-08-07 18:22, Holm Tiffe wrote: That is all that is to be expected. Not sure what you were expecting, but if you read the VMS installation manuals, you will see that this is where you should end up.

And at this point, you run BACKUP to restore the initial saveset to a disk, and then you boot that disk to continue. And now you know. :-) Johnny

On Aug 8, 2015, at 3:43 AM, Peter Coghlan <cctalk at beyondthepale.ie> wrote: On Sat, 08 Aug 2015 at 08:21:07 +0200, Holm Tiffe <holm at freibergnet.de> wrote: I'm not sure but I think I recall getting that error when trying to mount a disk that had media problems :-( It probably doesn't help much but the online help says this: VOLINV, volume is not software enabled Facility: SYSTEM, System Services Explanation: The volume valid bit is not set for the volume. All physical and logical I/O operations will be rejected until the bit is set. User Action: Check for a programming error. Verify that the volume is mounted and loaded. Check to see that the power is on before retrying the program. Regards, Peter Coghlan.

On Sat, 08 Aug 2015 at 08:21:07 +0200, Holm Tiffe <holm at freibergnet.de> wrote: I'm not sure but I think I recall getting that error when trying to mount a disk that had media problems :-(

It probably doesn't help much but the online help says this: VOLINV, volume is not software enabled Facility: SYSTEM, System Services Explanation: The volume valid bit is not set for the volume. All physical and logical I/O operations will be rejected until the bit is set. User Action: Check for a programming error. Verify that the volume is mounted and loaded. Check to see that the power is on before retrying the program. Regards, Peter Coghlan.

Holm Tiffe wrote: Tried the RF71 and it worked!

After the successful backup the Backup asked for a "YES" if I would do additional actions and I've tried DIA0 agin wich resulted in the same errors.

So I think I must have done something different wit that DSSI DUP utiliy.

Now I'll be snarky, but just for a single paragraph, Holm... :-) Did you ever actually read the full ISE Users Guide manual? Check page 3-7 to 3-12. There you actually have the manual talk about both the software write protect and the hardware write protect. In this context I believe you are going to play with the hardware write protect. Ignore my previous comment about the write protect button, as the RF31 apparently do not have one. It's all done through firmware instead. Check if there are any other parameters that looks like they might be related as well. Johnny --

On 2015-08-08 13:50, Holm Tiffe wrote: Ok. Too bad. That looked so very promising. :-( I'll try assuming less. Ok. Understood. The rubber bumper thing is something that exists in several drives. Search for "sticky heads" and similar phrases if you want to see. Yeah... But it's fun to learn. :-) Good work so far then. Seems like the drive is working fine. Did you try the commands mentioned in the manual? /OVER=ID is good to make MOUNT succeed independent of what labels are on the disk. /NOASSIST to make mount complete directly instead of sending a request to an operator. /WRITE or /NOWRITE for that part. /FOREIGN to mount disks that do not have a VMS filesystem on them. After that, I'd try to just read/write to the disk from VMS. Either it works, and you are happy. Or it fails, at which point you will have a good VMS error log to read from to find more details on what the problem is. VMS can also exercise the disk and analyze it. Johnny

On 08/08/15 12:50, Holm Tiffe wrote: It sounds like you have VMS installed on one disk and at least one other disk doesn't seem to be working. I suspect that it will be much easier to diagnose further issues from VMS rather than from the limited stand-alone environment or the limited console environment. So boot VMS (which should just be BOOT whatever-the-disk-id-is) and then use SHOW DEVICE to look at the state of the disks. One of the ones you could not restore to was (iirc) DIA0. Hopefully it will show up with that name or possibly something$DIA0.

You want to do something like: $ INIT DIA0: label If that completes without error then $ MOUNT/SYSTEM DIA0: label If that works without error then your disk is ready. I assume that in your case the INIT will fail, in which case the SHOW DEVICE DIA0:/FULL will probably be helpful in determining the next step. Antonio

Holm Tiffe wrote: There might be something in the VMS error log: $ ANALYZE /ERROR_LOG As far as I know, DSSI can be used as a VAX cluster interconnect and DSSI disks behave in similar ways to nodes in a VAX cluster. Therefore, it may be more correct to think of your DSSI disks as remotely served disks on another node instead of locally attached disks. In the case of a cluster which is using ethernet as a VAX cluster interconnect, error messages similar to: %PEA0, Port has Closed Virtual Circuit normally indicate ethernet media problems causing difficulty with cluster connections. PEA0 is the "port emulator" device where the ethernet is emulating a "real" CI cluster interconnect - coaxial cables and a transformer. Perhaps your PAA0 errors indicate some sort of errors with the DSSI connections rather than the disk media? There should be more details on this in the VMS error log. Regards, Peter Coghlan.

Johnny Billquist wrote: Hmm.. I'm not sure if you read what I previously wrote..I can hear you laughing but I don't think that this is really helpful..

What I've expected was an behavior like that described in the manuals, the manuals are telling stuff with boot flags that seems to not applicable here.

W/o any flag I end up at the prompt of a standalone backup wich is fine for me..

I'm starting the image restore and now I have a problem that the DSSI disks are "not software enabled".

Shure?

Regards, Holm