That's the thing. DTSTAT ALL shows LDEV 2 as LONER MEMBER2 and MPEXL_SYSTEM_VOLUME_SET.
I personally did a LISTF on @.SYS account when I booted it as a production machine. FSCHECK showed all was well about a month ago. DISCFREE showed it about a month ago. The NPCONFIG has the correct date for when I placed it production.
Chuck [log in to unmask] Consulting, Inc.59 Doe Ave.Laconia, NH 03246Phone: (603) 219-1500
On Sunday, February 15, 2015 11:47 AM, Ralph Bagen <[log in to unmask]> wrote:
Chuck:
As Ryan / Craig / Gilles are suggesting, perhaps LDEV 2 was never previously configured...
However, even although you find LDEV 2 in a LONER state, a :DSTAT ALL should show any previous volume label... how does it appear there?
Was an fscheck clean?
Ralph Bagen
MPE Support Group, LLC
E-mail: [log in to unmask]
-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On Behalf Of Chuck Trites
Sent: Sunday, February 15, 2015 9:01 AM
To: [log in to unmask]
Subject: [HP3000-L] System_Volume LDev 2 went from Member Status to Loaner?
I have an A500 that was put into production from a DR machine about a month and half ago. This system has 2 System volumes and a Raid array as it's own volume set. The LDEV 2 system volume is now showing as Loner status. Has anyone ever seen this happen? How else but a SCRATCHVOL or replacement of drive can the status go from Member to Loaner? System running fine and full backup doesn't show any errors. There aren't many files on Ldev 2, but I would think the full backup would have had a problem trying to store those files. Chuck [log in to unmask] Consulting, Inc.59 Doe Ave.Laconia, NH 03246Phone: (603) 219-1500
* 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 *
|
