- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Cannot mount user disk after system backup
Operating System - OpenVMS
1753760
Members
4816
Online
108799
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-08-2010 02:56 PM
тАО02-08-2010 02:56 PM
On a rx2600 running VMS 8.3...
We lost a system disk, replaced it, restored it from backup, installed the latest update kit.
Everything ran fine for a week but there were a few disk errors, so we ran a new system backup, replaced the disk yet again, restored the backup and now we get this weird error after boot when trying to mount the user disk. (see below).
Replacing the system disk with the previous one that was getting errors, same problem.
Booting from the upgrade disk, going to DCL, no problem, user disk mounts fine.
After booting up I log into the system account
sho dev dkb200: says "(remote mount)".
so I try to mount it manually:
$ dismount dkb200
%SYSTEM-F-DEVNOTMOUNT, device is not mounted
$ mount/cluster/system dkb200: IVMSUSER
%MOUNT-I-OPRQST, different volume already mounted on this device
%MOUNT-I-OPRQST, Please mount volume IVMSUSER in device _FISH$DKB200:
%MOUNT-I-NOOPR, no operator available to service request
*INTERRUPT*
$ mount/override=id dkb200:
%MOUNT-I-OPRQST, device is already mounted
%MOUNT-I-OPRQST, device _FISH$DKB200: is not available for mounting.
%MOUNT-I-NOOPR, no operator available to service request
*INTERRUPT*
$ dismount dkb200:
%SYSTEM-F-DEVNOTMOUNT, device is not mounted
So mount says it's mounted, dismount says it's not mounted. Any idea what's going on?
We lost a system disk, replaced it, restored it from backup, installed the latest update kit.
Everything ran fine for a week but there were a few disk errors, so we ran a new system backup, replaced the disk yet again, restored the backup and now we get this weird error after boot when trying to mount the user disk. (see below).
Replacing the system disk with the previous one that was getting errors, same problem.
Booting from the upgrade disk, going to DCL, no problem, user disk mounts fine.
After booting up I log into the system account
sho dev dkb200: says "(remote mount)".
so I try to mount it manually:
$ dismount dkb200
%SYSTEM-F-DEVNOTMOUNT, device is not mounted
$ mount/cluster/system dkb200: IVMSUSER
%MOUNT-I-OPRQST, different volume already mounted on this device
%MOUNT-I-OPRQST, Please mount volume IVMSUSER in device _FISH$DKB200:
%MOUNT-I-NOOPR, no operator available to service request
*INTERRUPT*
$ mount/override=id dkb200:
%MOUNT-I-OPRQST, device is already mounted
%MOUNT-I-OPRQST, device _FISH$DKB200: is not available for mounting.
%MOUNT-I-NOOPR, no operator available to service request
*INTERRUPT*
$ dismount dkb200:
%SYSTEM-F-DEVNOTMOUNT, device is not mounted
So mount says it's mounted, dismount says it's not mounted. Any idea what's going on?
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-08-2010 03:07 PM
тАО02-08-2010 03:07 PM
Solution
Is the problem disk still mounted on other
cluster members? If so, I'd vote for
DISMOUNT /ABORT
on all the cluster members where it is.
Cluster members share info, so if one
believes that some volume name is in use
somewhere, then they all tend to believe it.
Otherwise, a little more info about which
disks are where might be useful.
cluster members? If so, I'd vote for
DISMOUNT /ABORT
on all the cluster members where it is.
Cluster members share info, so if one
believes that some volume name is in use
somewhere, then they all tend to believe it.
Otherwise, a little more info about which
disks are where might be useful.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-08-2010 08:27 PM
тАО02-08-2010 08:27 PM
Re: Cannot mount user disk after system backup
That was it, thanks.
I hate being the de facto admin, I'm a programmer.
I hate being the de facto admin, I'm a programmer.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-08-2010 08:38 PM
тАО02-08-2010 08:38 PM
Re: Cannot mount user disk after system backup
This situation is even more annoying when the
disk in limbo is the system disk from which
you're trying to boot. As I recall, you get
some unhelpful message with a hex error code,
and then you need to find a working system
where you can decode the code. (Easier now,
with the Web, than in the old, pre-Web days.)
> I hate being the de facto admin, I'm a
> programmer.
Fun is where you find it.
disk in limbo is the system disk from which
you're trying to boot. As I recall, you get
some unhelpful message with a hex error code,
and then you need to find a working system
where you can decode the code. (Easier now,
with the Web, than in the old, pre-Web days.)
> I hate being the de facto admin, I'm a
> programmer.
Fun is where you find it.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP