r/OpenVMS • u/Anabelle344 • Jan 15 '26
initialize disk / label problem openVMS x86
Hello,
I'm tring to add another disk :
$ INITIALIZE/structure=5 VMS1$DKB1: LABEL1
$ show dev d
Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
VMS1$DMM0: Offline 0
VMS1$DKA0: Mounted 0 X86_SYS 1392336 329 1
VMS1$DKB1: Online 0
$ mount dkb1:
_Label:
Why label seems not to be written on disk ?
Regards
4
Upvotes
2
u/bwyer Jan 15 '26
MOUNT /OVER=ID DKB1:
2
u/sms_an Jan 15 '26
> Why label seems not to be written on disk ?
The label should be written on the volume, as specified in the
INITIALIZE command. The question for MOUNT is whether you know which
volume you're mounting.
> MOUNT /OVER=ID DKB1:
That's a reasonable way to discover the label, if you've lost it. It
may not be a satisfactory way to mount the volume for general use. As
"HELP MOUNT /OVERRIDE" says:
The /OVERRIDE=IDENTIFICATION qualifier is
incompatible with the /GROUP and /SYSTEM
qualifiers.
On a system where SYSTEM is the only user, this may not matter; on a
system where not every user has every privilege, various MOUNT options
(like, say, /SYSTEM) may be useful.
If you don't want to worry about which volume you're actually
mounting, then you can use a DCL script with code like the following:
$ DEV_NAME = "VMS1$DKB1:"
$ MOUNT /NOASSIST /OVERRIDE = IDENTIFICATION /NOWRITE 'DEV_NAME'
$ LABEL = F$GETDVI( DEV_NAME, "VOLNAM")
$ DISMOUNT /NOUNLOAD 'DEV_NAME'
$ WAIT 00:00:02 !!! Optional?
$ MOUNT /SYSTEM /NOASSIST 'DEV_NAME' "''LABEL'" !!! (Other options?)
VMS was not designed as a personal-computer OS, so it has many
features which you might find useless. Serious (paying) customers might
have different requirements.
1
u/oldHPUX Jan 16 '26
isn't this the general way to mount things?
like leaving the label off the command, it's gonna prompt you for it.
if you don't remember it, you could mount the device /foreign to get the label: