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

Not able to mount or INIT a disk

SOLVED
Go to solution
Joewee
Regular Advisor

Not able to mount or INIT a disk

How to get this fixed?

$ mount/over=id drb0
%%%%%%%%%%% OPCOM 2-JUN-2009 14:20:46.78 %%%%%%%%%%%
Message from user SYSTEM on XXXX
device already allocated to another user

%MOUNT-I-OPRQST, device already allocated to another user
%%%%%%%%%%% OPCOM 2-JUN-2009 14:20:46.78 %%%%%%%%%%%
Request 5, from user SYSTEM on XXXX
device _$1$DRB0: (XXXX) is not available for mounting.

%MOUNT-I-OPRQST, device _$1$DRB0: (XXXX) is not available for mounting.
Interrupt

XXXX4$ stop
%MOUNT-I-OPRQSTCAN, operator request canceled
XXXX$
%%%%%%%%%%% OPCOM 2-JUN-2009 14:20:52.79 %%%%%%%%%%%
Request 5 was canceled

XXXX$ init $1$drb0: arc1
%SYSTEM-W-DEVALLOC, device already allocated to another user
XXXX$ sho dev drb0/full

Disk $1$DRB0: (XXXX), device type 2 Member RAID 0, is online, file-oriented
device, shareable, available to cluster, error logging is enabled.

Error count 0 Operations completed 1242
Owner process "" Owner UIC [SYSTEM]
Owner process ID 00000000 Dev Prot S:RWPL,O:RWPL,G:R,W
Reference count 1 Default buffer size 512
Total blocks 35545088 Sectors per track 64
Total cylinders 34712 Tracks per cylinder 16
Allocation class 1
Device access control list:
(IDENTIFIER=PP$ARCH_READ,ACCESS=READ)








18 REPLIES
Hakan Zanderau ( Anders
Trusted Contributor

Re: Not able to mount or INIT a disk

Try,

$ MCR SYSMAN
SYSMAN> SET ENV/CLU
SYSMAN> DO SHOW DEV/FILE DRB0

This will show what process in the cluster has
an open file on the disk.

Hakan
Don't make it worse by guessing.........
marsh_1
Honored Contributor

Re: Not able to mount or INIT a disk

hi,

unfortunately the only reliable method of fixing this is to reboot. ensure you are up to date with patches and firmware for this box and storage. do you know which process /user died while doing things with this device to leave it in this state ?

fwiw

Hakan Zanderau ( Anders
Trusted Contributor

Re: Not able to mount or INIT a disk

Oooops, maybe I was to fast reading again...

"available to cluster"

Is the node a clustermember ??

Hakan
Don't make it worse by guessing.........
Joewee
Regular Advisor

Re: Not able to mount or INIT a disk

No Not in cluster... Standalone.
Peter Zeiszler
Trusted Contributor

Re: Not able to mount or INIT a disk

show dev drb0
show dev/files drb0

See if something has files open. If the files are installed in memory you will have to remove them from memory.

If a process that is active has the disk already mounted then check what that process is and contact the owner.
Richard W Hunt
Valued Contributor

Re: Not able to mount or INIT a disk

A SHOW DEVICE/FILES $1$DRB0 might tell you what is open on the volume. Until you close what is open, you will never dismount that volume short of something drastic and dangerous.

What interests me is that your system somehow thinks this disk is in a cluster environment, yet you say it is not. Was it EVER in a cluster environment? Do you have VMSCLUSTER set to something other than 0 in SYSGEN for that node?

Is this by any chance a SAN device and some other member of the SAN currently has the device locked up in some way?
Sr. Systems Janitor
Hoff
Honored Contributor

Re: Not able to mount or INIT a disk

Is this the OpenVMS Alpha V7.1-1H2 box that encountered severe disk data corruptions a while back? This one:

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1343166

That OpenVMS Alpha box was badly corrupted.

And whether or not the AlphaServer 2000 4/275 and the SWXCR Mylex DAC960 hardware involved was failing was (and probably is) an open question here, too.

That OpenVMS Alpha V7.1-1H2 release (also) has various known errors that look rather similar to this one; disks could get locked in odd states, etc. There were a large number of ECO kits released for that version, and the V7.1-2 roll-up (and its respective ECO kits) then became available as part of simplifying the ECO management on V7.1, V7.1-1H1 and V7.1-1H2.
RBrown_1
Trusted Contributor

Re: Not able to mount or INIT a disk

Richard said "What interests me is that your system somehow thinks this disk is in a cluster environment".

My testing seems to indicate that even on a non-clustered system, show dev/full of most disk drives include the phrase "available to cluster".

FWIW
Jur van der Burg
Respected Contributor

Re: Not able to mount or INIT a disk

This is the key:

>Reference count 1

The disk is not mounted, but there's a process with a reference to it. You can find out which one by doing this:

$ ana/sys
SDA> set out x.x
SDA> show proc/chan all
SDA> exit
$ search x.x drb0/window=20

Then you may find the offending process.

Jur.
Joewee
Regular Advisor

Re: Not able to mount or INIT a disk

Hi All,

Thanks for your replies.

The actual problem is the disk is a raw disk which was replaced and im not able to initialize it itself.

The disk is online and its not allocated to any process

XXXX$ show dev drb0

Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
$1$DRB0: (MSUK04) Online 0
XXXX$ show dev/files drb0
%SYSTEM-F-NOTFILEDEV, device is not file structured

SDA> set out sys$manager:drb_err.out
SDA> show proc/chan all
SDA> exit
XXXX$ sea sys$manager:drb_err.out drb0
00A0 00000000 $1$DRB0:
XXXX$


>> Hoff >>

Yes, its the same machine. But its almost gonna be scrapped and they need this application for last few days to get it ported.

>> >>

The main thing is though I try to initialize this disk first after the reboot then also it gives me the same problem.

This is in stripe set i.e raid 0 with another disk could that be a reason for this kind of act?

And, How shall I log in to the controller from VMS?

Thanks again,
Joe








marsh_1
Honored Contributor

Re: Not able to mount or INIT a disk

hi,

you would probably use swxcr, hoff has some good info on the tools required on his site here :-

http://labs.hoffmanlabs.com/node/564

hth

Jur van der Burg
Respected Contributor

Re: Not able to mount or INIT a disk

>XXXX$ sea sys$manager:drb_err.out drb0
>00A0 00000000 $1$DRB0:
>XXXX$

Ok, that poves my point that there's a process with a channel assigned. If you added '/windows=20' to the search you may see which process (or open the file in an editor and look for DRB0). Then see which process it is and stop it.

Jur.
Joewee
Regular Advisor

Re: Not able to mount or INIT a disk

Here is the output. Im not sure which process is that...


sea sys$manager:drb_err.out drb0/win=(20,20)
Process index: 001F Name: SWXCR$MON_DRB Extended PID: 0000021F





Process active channels
-----------------------

Channel Window Status Device/file accessed
------- ------ ------ --------------------
0010 00000000 $1$DRA0:
0020 80D55440 $1$DRA0:[VMS$COMMON.SYSEXE]SWXCR$MONITOR.EXE;1
0030 80CA9FC0 $1$DRA0:[VMS$COMMON.SYSLIB]LIBOTS.EXE;1 (section file)
0040 80CA6180 $1$DRA0:[VMS$COMMON.SYSLIB]MAILSHR.EXE;1 (section file)
0050 80CA9A80 $1$DRA0:[VMS$COMMON.SYSLIB]LIBRTL.EXE;1 (section file)
0060 80CA2DC0 $1$DRA0:[VMS$COMMON.SYSLIB]MAILSHRP.EXE;1 (section file)
0070 80CAAE40 $1$DRA0:[VMS$COMMON.SYSLIB]DECC$SHR.EXE;2 (section file)
0080 80CAA880 $1$DRA0:[VMS$COMMON.SYSLIB]DPML$SHR.EXE;1 (section file)
0090 80CAA500 $1$DRA0:[VMS$COMMON.SYSLIB]CMA$TIS_SHR.EXE;1 (section file)
00A0 00000000 $1$DRB0:
Jur van der Burg
Respected Contributor
Solution

Re: Not able to mount or INIT a disk

Ok, so the SWXCR monitor process is still looking at the device. Just do a stop/id on it, and it you start it somewhere in your startup disable it.

Jur.
comarow
Trusted Contributor

Re: Not able to mount or INIT a disk

I believe you could also override = checks, but
there is a possible that one file could become
corrupt.

Bob Comarow
Jur van der Burg
Respected Contributor

Re: Not able to mount or INIT a disk

/override=checks is meaningless here. The reference count on the device is elevated meaning mount will refuse to mount the device.

Jur.
Joewee
Regular Advisor

Re: Not able to mount or INIT a disk

Hi Jur,

You were right... I had to reboot this machine.. I commented the SWXCR monitor DRB command.. and the system was back fine and i have initialized and then restored the data and mounted it back.. Thanks a lot for your help....

Later I found that if we give $swxcr monitor command then after that we can mount the disk only with the qualifier /system or above. with this situation is it not possible to mount that disk as foriegn??

Jur van der Burg
Respected Contributor

Re: Not able to mount or INIT a disk

You can't mount it foreign if the reference count is > 0, and you can't init it either. If you mount it /system you can mount it with the reference count > 0 if you have SHARE privilege. You probably did it from the system account which has this privilege.

Jur.