home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.vms
- Path: sparky!uunet!gatech!destroyer!ncar!noao!stsci!stsci.edu!merrill
- From: merrill@stsci.edu (Clark Merrill)
- Subject: Re: Bypassing missing F11BXQP on startup ?
- Message-ID: <29DEC199213352375@stsci.edu>
- News-Software: VAX/VMS VNEWS 1.50
- Sender: news@stsci.edu
- Organization: Space Telescope Science Institute
- References: <9212290827.AA18530@ucbvax.Berkeley.EDU>
- Date: Tue, 29 Dec 1992 18:35:00 GMT
- Lines: 31
-
- In article <9212290827.AA18530@ucbvax.Berkeley.EDU>, simons/G=Colin/I=CB/S=Sewell/O=H.A.Simons.Ltd/OU=CORP@mhs.attmail.com writes...
- >
- >write sys$output f$message(%x07280b4)
- >%MOUNT-F-VOLALRMNT, another volume of same label already mounted
- >
- >write sys$output f$message(%x00018272)
- >%RMS-E-DNR, device not ready, not mounted, or unavailable
- >
- I do this another way,
-
- exit %x07280b4
- %MOUNT-F-VOLALRMNT, another volume of same label already mounted
-
- exit %x00018272
- %RMS-E-DNR, device not ready, not mounted, or unavailable
-
- Same results, just a different method.
-
- For the original problem, I have had this error occur where the HSC is
- not listing the booted disk as $1$DUAx, but as hsc00x$DUAx. A reboot of
- my HSC cleared the problem up. I discovered that this was the problem by
- backing up the system disk to a free spindle and changing the volume name.
- then booting from the new system disk. All disks on the HSC came up as
- hsc00x$DUAx. Like I said before a reboot of the HSC cleared the problem.
-
- Good Luck
-
- Clark B. Merrill
- Space Telescope Science Institute
- Baltimore, Maryland
- merrill@stsci.edu
-