Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

Mystery drive keep showing up after reboot

 
SOLVED
Go to solution
Jorge Cocomess
Super Advisor

Re: Mystery drive keep showing up after reboot

Guenther,

This device mounted after the server was rebooted. This device was removed from syslogicals.com file and replaced with a mirrored_set $1$dga19 labeled disk19 instead.

I've searched and purged all the syslogicals.com or any files that had the old mount command.

The funny thing is, the old dka300 device get mounted first, therefore, the new disk19 can't be mounted because of the same name label.

Jorge
Martin Hughes
Regular Advisor

Re: Mystery drive keep showing up after reboot

A couple of things I would check;

1. SYSMAN startups;

$ MC SYSMAN STARTUP SHOW FILE

2. Make sure you don't have an older version of a startup procedure (SYSTARTUP_VMS or SYLOGICALS etc) lurking in SYS$SPECIFIC.

3. Is it possible that there is a data-file used to specify disks, labels etc for the mounting process?. This would explain why the DKA300 string is not found in your command procedure search.
For the fashion of Minas Tirith was such that it was built on seven levels, each delved into a hill, and about each was set a wall, and in each wall was a gate. (J.R.R. Tolkien). Quote stolen from VAX/VMS IDSM 5.2
Steven Schweda
Honored Contributor

Re: Mystery drive keep showing up after reboot

If the disk is mounted /SYSTEM (or /CLUSTER),
I'd search for the label (which must be
specified in the MOUNT command) rather than
the device name (which could be almost
anything).

And, for starters, rather than try to guess a
likely place, I'd search
sys$sysdevice:[000000...]*.com. If that
failed, I might try the same on other disks.
Then I might try *.*. (What else does the
system have to do?)

If I got more desperate, I'd start looking
for MOUNT commands.

If I got _really_ desperate, I might try
unplugging the disk drive and waiting for the
mount failure.
Joseph Huber_1
Honored Contributor

Re: Mystery drive keep showing up after reboot


Finally, does SHOW MEMORY/FILES list the disk for using page/swap files ?

A search through all command-files should have found it...
Usually (secondary-)page/swap files/disks are mounted in sys$system:sypagswap or satellite_page.com .
http://www.mpp.mpg.de/~huber
Steven Schweda
Honored Contributor

Re: Mystery drive keep showing up after reboot

> A search through all command-files should
> have found it...

Not around here. I have a disk-mounting
procedure which reads a data file,
SYS$MANAGER:LOCAL_DISKS.DAT. For example:

! 7 September 2005. SMS.
!
! ALP's Local Disks (as seen from ALP$DKA0:).
!
! Format: CODE DEVICE LABEL
!
! Code: N: non-system disk, R: read-only non-system disk, S: system disk.
! LABEL = "*" for any label on non-system disks.
! For the best messages, place the system disk last.
!

! N DKA200: ALP_SCSI_2

N DKA100: UTIL5ALPX

N DKB400: VMS073ALPX

N DKB300: TEST

S DKA0: VMS073ALP

! r dka500: *
! r dka400: *
R DKA600: *

[The CD-ROM drive keeps migrating around.]

Other cluster members can DECnet in when they
start up, read the same file, and mount this
system's disks, too. The scheme works pretty
well, but you could look at every .COM file
in the room and still not find these data.
Kelly Stewart_1
Frequent Advisor

Re: Mystery drive keep showing up after reboot

And of course it's possible that there are command files that aren't named ".com". For instance we use custom command file types in our startup mechanism, just where a rouge MOUNT command might be.

Kelly
MarkOfAus
Valued Contributor

Re: Mystery drive keep showing up after reboot

Jorge,

How about a listing of show dev/full $1$dga19 and show dev/full dka300?

Regards
Mark
John Gillings
Honored Contributor

Re: Mystery drive keep showing up after reboot

Jorge,
Brute force approach. Assuming there is a physical device DKA300... If it's in a storage shelf, just remove it! If it's an internal drive and you don't want to open the case to unplug or remove it, then change the volume name:

$ SET VOLUME/LABEL=NOTDISK19 DKA300
$ DISMOUNT/CLUSTER DKA300

Next reboot even if you haven't found the MOUNT command, mounting that disk will fail because the volume labels no longer match.
A crucible of informative mistakes