Disk in UNKNOWN State

Discussion:

(too old to reply)

Dan Barnes

2010-03-12 18:15:20 UTC

Hi -L Gang,

I had a mirrored disk drive in a Jamaica Enclosure go bad yesterday. The
DSTAT below shows that it went into a 'BUSY' state, and nothing short of a
reboot could clear it.

:dstat

LDEV-TYPE STATUS VOLUME VOLUME SET - GEN
---------- ------- ----------------------------------
33-ST34572WC MASTER-MD MEMBER2 IT_UV-0
34-ST39236LC MASTER-MD MEMBER1 IT_UV-0
43-ST34572WC **BUSY
44-ST39175LC MASTER-MD MEMBER1 IT_UV-0

After/During the reboot, I replaced the drive. When the system went
thru "Mount All Volumes" it complained about a duplicate volume, but I had to
wait for the system to come up completely to try to deal with that.

At that point, the system now shows these drives in the following state:

:dstat

LDEV-TYPE STATUS VOLUME VOLUME SET - GEN
---------- ------- ----------------------------------
33-ST34572WC *PENDING-MD MEMBER2 IT_UV-0
34-ST39236LC MASTER-MD MEMBER1 IT_UV-0
43-ST34572WC UNKNOWN
44-ST39175LC MASTER-MD MEMBER1 IT_UV-0

I then try a SCRATCHVOL and get the following:

:volutil

Mirvutil A.70.02, (C) Hewlett-Packard Co., 1991. All Rights Reserved.
volutil: scratchvol 43
^
*Error: Volume mounted in invalid state for desired operation. (volutil 122)
volutil:

I then try a FORMATVOL and get the following:

volutil: formatvol 43
*Verify: Format volume on ldev 43 [Y/N] ?y

DISMOUNT REQUEST FOR LDEV 43 GRANTED (AVR 19)

it just hangs here..........

I can restore the data, so no issue there.

What I am unable at this point to do is resolve this partially mounted volume
issue.

The system is an N4000-100-330 on 7.0 patched up-to-date.

TIA,
Dan

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

Jack Connor

2010-03-12 18:23:53 UTC

Permalink

You might be able to do a NEWMIRRVOL IT_UV:MEMBER2 (33,43) 100 100...although I'm not too confident as 33 is in pending state.
You may have to suspend mirroring on it to get them joined back in.
jack

-----Original Message-----
From: Dan Barnes [mailto:***@LCI-ONLINE.COM]
Sent: Friday, March 12, 2010 1:15 PM
To: HP3000-***@RAVEN.UTC.EDU
Subject: [HP3000-L] Disk in UNKNOWN State

Hi -L Gang,

I had a mirrored disk drive in a Jamaica Enclosure go bad yesterday. The
DSTAT below shows that it went into a 'BUSY' state, and nothing short of a
reboot could clear it.

:dstat

LDEV-TYPE STATUS VOLUME VOLUME SET - GEN
---------- ------- ----------------------------------
33-ST34572WC MASTER-MD MEMBER2 IT_UV-0
34-ST39236LC MASTER-MD MEMBER1 IT_UV-0
43-ST34572WC **BUSY
44-ST39175LC MASTER-MD MEMBER1 IT_UV-0

After/During the reboot, I replaced the drive. When the system went
thru "Mount All Volumes" it complained about a duplicate volume, but I had to
wait for the system to come up completely to try to deal with that.

At that point, the system now shows these drives in the following state:

:dstat

LDEV-TYPE STATUS VOLUME VOLUME SET - GEN
---------- ------- ----------------------------------
33-ST34572WC *PENDING-MD MEMBER2 IT_UV-0
34-ST39236LC MASTER-MD MEMBER1 IT_UV-0
43-ST34572WC UNKNOWN
44-ST39175LC MASTER-MD MEMBER1 IT_UV-0

I then try a SCRATCHVOL and get the following:

:volutil

Mirvutil A.70.02, (C) Hewlett-Packard Co., 1991. All Rights Reserved.
volutil: scratchvol 43
^
*Error: Volume mounted in invalid state for desired operation. (volutil 122)
volutil:

I then try a FORMATVOL and get the following:

volutil: formatvol 43
*Verify: Format volume on ldev 43 [Y/N] ?y

DISMOUNT REQUEST FOR LDEV 43 GRANTED (AVR 19)

it just hangs here..........

I can restore the data, so no issue there.

What I am unable at this point to do is resolve this partially mounted volume
issue.

The system is an N4000-100-330 on 7.0 patched up-to-date.

TIA,
Dan

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

Be sure to ask us about short term and long term rentals on servers, workstations, storage and more!

CONFIDENTIALITY NOTICE: This communication with its contents may contain confidential information. It is solely for the use of the intended recipient(s). Unauthorized interception, review, use or disclosure is prohibited and may violate applicable laws including the Electronic Communications Privacy Act. If you are not the intended recipient, please contact the sender and destroy all copies of the communication.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

Craig Lalley

2010-03-12 19:01:48 UTC

Permalink

--- On Fri, 3/12/10, Gary Robillard <***@Q.COM> wrote:

The formatvol command can take hours to complete...

Just say NO to FORMATVOL on MPE!

Take the drive out of the box, hook it up to a PC and do it there... but you won't live long enough to do it on MPE.

Unless of course it is an N-Class, then never mind.

-Craig

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

Gilles Schipper

2010-03-12 21:31:07 UTC

Permalink

Further to last ....

You really should NOT need to do a FORMATVOL.

I've only once actually ever needed to do that - and I did not do it
with MPE, which is extremely slow.

A simple VOLUTIL replacemirrvol should do the trick after you've
replaced the drive. The fact that the drive is in an "UNKNOWN" state
is perfectly normal for the situation you described.

Thanks for all the suggestions gang.
I was able to do the SUSPENDMIRRVOL and gets things into somewhat of
a better/more workable state.
:dstat all
LDEV-TYPE STATUS VOLUME VOLUME SET - GEN
---------- ------- ----------------------------------
1-C2300WDR1 MASTER MEMBER1 MPEXL_SYSTEM_VOLUME_SET-0
2-C2300WDR1 MEMBER MEMBER2 MPEXL_SYSTEM_VOLUME_SET-0
28-ST318406LC MASTER MEMBER1 DISKDUMP-0
29-ST318406LC MEMBER MEMBER2 DISKDUMP-0
31-ST34371N MASTER-MD MEMBER1 AVAIL-0
32-ST34371N MEMBER-MD MEMBER2 AVAIL-0
33-ST34572WC MEMBER-MD MEMBER2 IT_UV-0
34-ST39236LC MASTER-MD MEMBER1 IT_UV-0
41-ST34573WC MASTER-MD MEMBER1 AVAIL-0
42-ST34572WC MEMBER-MD MEMBER2 AVAIL-0
43-ST34572WC *DISABLED-MD MEMBER2 IT_UV-0
44-ST39175LC MASTER-MD MEMBER1 IT_UV-0
50-MAS3184NC MASTER-MD MEMBER1 A_UV-0
51-ST318452LC MEMBER-MD MEMBER2 A_UV-0
52-ST318452LC MASTER-MD MEMBER1 B_UV-0
53-ST318452LC MEMBER-MD MEMBER2 B_UV-0
60-ST318452LC MASTER-MD MEMBER1 A_UV-0
61-MAS3184NC MEMBER-MD MEMBER2 A_UV-0
62-ST318452LC MASTER-MD MEMBER1 B_UV-0
63-ST318452LC MEMBER-MD MEMBER2 B_UV-0
What I am going to do at this point is do a store-to-disk of the
volume contents, create a buildjob with the accounts that love
there, then vsclose, scratch, then rebuild the volume set.
Thanks!
Dan
Dan Barnes
LCI-Lawinger Consulting
106 Central Avenue, Suite A
Osseo, MN, 55369-1243
Tel: 763-425-1639 :: Fax: 763-425-5483
Cell: 612-240-2136 :: Pager: 952-394-0132
-----Original Message-----
Behalf Of Craig Lalley
Sent: Friday, March 12, 2010 1:02 PM
Subject: Re: [HP3000-L] Disk in UNKNOWN State
The formatvol command can take hours to complete...
Just say NO to FORMATVOL on MPE!
Take the drive out of the box, hook it up to a PC and do it there...
but you won't live long enough to do it on MPE.
Unless of course it is an N-Class, then never mind.
-Craig
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

-------------------------------------------------------------------------------------------------
Gilles Schipper
GSA Inc.
HP System Administration Specialists
300 John Street, Box 87651 Thornhill, ON Canada L3T 7R4
Tel: 416.702.7900
email: ***@gsainc.com web: http://www.gsainc.com
-------------------------------------------------------------------------------------------------

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

Gilles Schipper

2010-03-12 20:43:03 UTC

Permalink

You should be good to go.

The suspendmirrvol was the right thing to do.

After you've replaced the drive (which is now), you simply:

volutil
replacemirrvol IT_UV:member2 43

Really no need to perform a store-to-disk and buldjob stuff.

But if really want to do that, I would first perform a directory store, as:

:store
command.pub.sys;directory;onvs=mpexl_system_volume_set,diskdump,it_uv,a_uv,b_uv;*t;show

Then, store the files on it_uv, ..
Then, after vsclosing, etc,
:restore *t;;directory;show

Then restore of files on that volset - with the
;olddate;create;keep;partdb options.
But I don't think any of those latter steps (from vsclose onwards)
will be necessary.

Dan Barnes

2010-03-12 19:06:49 UTC

Permalink

Thanks for all the suggestions gang.

I was able to do the SUSPENDMIRRVOL and gets things into somewhat of a better/more workable state.

I now have the drives in the following state:

:dstat all
LDEV-TYPE STATUS VOLUME VOLUME SET - GEN
---------- ------- ----------------------------------
1-C2300WDR1 MASTER MEMBER1 MPEXL_SYSTEM_VOLUME_SET-0
2-C2300WDR1 MEMBER MEMBER2 MPEXL_SYSTEM_VOLUME_SET-0
28-ST318406LC MASTER MEMBER1 DISKDUMP-0
29-ST318406LC MEMBER MEMBER2 DISKDUMP-0
31-ST34371N MASTER-MD MEMBER1 AVAIL-0
32-ST34371N MEMBER-MD MEMBER2 AVAIL-0
33-ST34572WC MEMBER-MD MEMBER2 IT_UV-0
34-ST39236LC MASTER-MD MEMBER1 IT_UV-0
41-ST34573WC MASTER-MD MEMBER1 AVAIL-0
42-ST34572WC MEMBER-MD MEMBER2 AVAIL-0
43-ST34572WC *DISABLED-MD MEMBER2 IT_UV-0
44-ST39175LC MASTER-MD MEMBER1 IT_UV-0
50-MAS3184NC MASTER-MD MEMBER1 A_UV-0
51-ST318452LC MEMBER-MD MEMBER2 A_UV-0
52-ST318452LC MASTER-MD MEMBER1 B_UV-0
53-ST318452LC MEMBER-MD MEMBER2 B_UV-0
60-ST318452LC MASTER-MD MEMBER1 A_UV-0
61-MAS3184NC MEMBER-MD MEMBER2 A_UV-0
62-ST318452LC MASTER-MD MEMBER1 B_UV-0
63-ST318452LC MEMBER-MD MEMBER2 B_UV-0

What I am going to do at this point is do a store-to-disk of the volume contents, create a buildjob with the accounts that love there, then vsclose, scratch, then rebuild the volume set.

Thanks!
Dan

Dan Barnes
LCI-Lawinger Consulting
106 Central Avenue, Suite A
Osseo, MN, 55369-1243
Tel: 763-425-1639 :: Fax: 763-425-5483
Cell: 612-240-2136 :: Pager: 952-394-0132
***@lci-online.com
***@mmm.com

-----Original Message-----
From: HP-3000 Systems Discussion [mailto:HP3000-***@RAVEN.UTC.EDU] On Behalf Of Craig Lalley
Sent: Friday, March 12, 2010 1:02 PM
To: HP3000-***@RAVEN.UTC.EDU
Subject: Re: [HP3000-L] Disk in UNKNOWN State

--- On Fri, 3/12/10, Gary Robillard <***@Q.COM> wrote:

The formatvol command can take hours to complete...

Just say NO to FORMATVOL on MPE!

Take the drive out of the box, hook it up to a PC and do it there... but you won't live long enough to do it on MPE.

Unless of course it is an N-Class, then never mind.

-Craig

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

Gary Robillard

2010-03-12 18:58:46 UTC

Permalink

The formatvol command can take hours to complete...

(but you should see the light blinking (albeit slowly) on the drive being formatted)

Gary

Date: Fri, 12 Mar 2010 13:39:08 -0500
Subject: Re: Disk in UNKNOWN State
Funny thing about drives, if they were used before, the system will
"notice" the volume name it had in a previous life. If it happens to be
one of the volume_set names you already have, the system gets confused
while it tries to reconcile it. If I retire a drive that isn't bad, I
usually scratch it upon retirement so that won't happen upon re-use.
However the UNKNOWN state should have been perfectly good to use as a
NEWVOL, SCRATCHVOL should have been unneccesary.
Tracy Johnson
Office 1-757-766-4318

Post by Jack Connor
-----Original Message-----
From: HP-3000 Systems Discussion
Sent: Friday, March 12, 2010 1:15 PM
Subject: [HP3000-L] Disk in UNKNOWN State
Hi -L Gang,
I had a mirrored disk drive in a Jamaica Enclosure go bad
yesterday. The
DSTAT below shows that it went into a 'BUSY' state, and
nothing short of a
reboot could clear it.
:dstat
LDEV-TYPE STATUS VOLUME VOLUME SET - GEN
---------- ------- ----------------------------------
33-ST34572WC MASTER-MD MEMBER2 IT_UV-0
34-ST39236LC MASTER-MD MEMBER1 IT_UV-0
43-ST34572WC **BUSY
44-ST39175LC MASTER-MD MEMBER1 IT_UV-0
After/During the reboot, I replaced the drive. When the system went
thru "Mount All Volumes" it complained about a duplicate
volume, but I had to
wait for the system to come up completely to try to deal with that.
At that point, the system now shows these drives in the
:dstat
LDEV-TYPE STATUS VOLUME VOLUME SET - GEN
---------- ------- ----------------------------------
33-ST34572WC *PENDING-MD MEMBER2 IT_UV-0
34-ST39236LC MASTER-MD MEMBER1 IT_UV-0
43-ST34572WC UNKNOWN
44-ST39175LC MASTER-MD MEMBER1 IT_UV-0
:volutil
Mirvutil A.70.02, (C) Hewlett-Packard Co., 1991. All Rights
Reserved.
volutil: scratchvol 43
^
*Error: Volume mounted in invalid state for desired
operation. (volutil 122)
volutil: formatvol 43
*Verify: Format volume on ldev 43 [Y/N] ?y
DISMOUNT REQUEST FOR LDEV 43 GRANTED (AVR 19)
it just hangs here..........
I can restore the data, so no issue there.
What I am unable at this point to do is resolve this
partially mounted volume
issue.
The system is an N4000-100-330 on 7.0 patched up-to-date.
TIA,
Dan
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

Johnson, Tracy

2010-03-12 18:39:08 UTC

Permalink

Funny thing about drives, if they were used before, the system will
"notice" the volume name it had in a previous life. If it happens to be
one of the volume_set names you already have, the system gets confused
while it tries to reconcile it. If I retire a drive that isn't bad, I
usually scratch it upon retirement so that won't happen upon re-use.

However the UNKNOWN state should have been perfectly good to use as a
NEWVOL, SCRATCHVOL should have been unneccesary.

Tracy Johnson
Office 1-757-766-4318

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

Jeff Kell

2010-03-12 19:04:03 UTC

Permalink

Unless you really, really need that formatvol, a scratchvol works wonders (if it is accepted).

Jeff

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *