headers
Dave Sill | 9 Dec 2010 18:54
Picon

Administrivia: Tru64-UNIX-Managers information and policy statement

EVERYONE WHO RECEIVES THIS MESSAGE HAD BETTER READ IT THOROUGHLY.

Tru64-UNIX-Managers Information and Rules

This message is a summary of the Tru64-UNIX-managers charter and rules.
Failure to adhere to these guidelines may result in severe chastisement by
the list maintainer and other list participants. Retain a copy of this
statement and refer to it before submitting messages to the list or the list
administrator.

Last modified: 2002-10-09                                                     |

  1. Send only HP Tru64 UNIX (formerly Compaq Tru64 UNIX (formerly            |
     Digital UNIX (formerly Digital OSF/1))) system management questions and  |
     summaries to tru64-unix-managers <at> ornl.gov. Include your return address in
     the body of your message so people can reply directly to you. Avoid MIME
     and HTML--many people can't read them.

  2. This list is not moderated! Every message that is sent to the list will
     be passed on to every member of the list (with a few small exceptions).

  3. This mailing list is managed by a utility called Majordomo. You can
     subscribe to the list by sending a message like:

           subscribe tru64-unix-managers

     to majordomo <at> ornl.gov.

     Likewise, if you want to remove yourself from the list, send the
     message:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Didier Godefroy | 13 Dec 2010 23:35

Problem with lost configuration in LSM

Hello all who's left on this list,

I haven't had any troubles with my systems for years now so I haven't been
active on this list, but now I have a problem that's becoming urgent.

What happened is that I had a failed disk that I replaced and I was only
able to reestablish part of the mirroring that was there before.

The machine is an alpha 1200 and I have drives in all 7 bays, with the scsi
bus split and two controllers, so I have 4 drives on one controller and 3 on
the other.

I have my disks named as dsk0..dsk6 with dsk0, dsk1, dsk2 and dsk6 on the
first scsi controller on the 4 top bays, and then dsk3, dsk4 and dsk5 on the
other controller.

The dsk0 is the boot disk, with root, swap, usr and var in dsk0a, dsk0b,
dsk0d and dsk0f respectively. That disk was encapsulated and it is mirrored
on dsk3.

I was thinking I had several configuration copies, and I pretty sure I did,
but now after replacing the dsk3 that had failed, after trying to
reestablish all the mirroring, something must've happened and there are no
longer any configuration copies found.

To replace the failed disk, I swapped it physically and used hwmgr to scan
the new disk and then I swapped the name dsk3 with the newly created dsk10
with dsfmgr so I would have that new drive in the same location and with the
same name as the previous one.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Didier Godefroy | 15 Dec 2010 13:00

Problem with lost configuration in LSM (more info)

Hi all again,

My continued investigations and attempts at reconnecting the lost lsm
configuration are pointing to a quite possible corruption of the
configuration data.

I forgot to mention that I'm on tru64 5.1b and I only have remote access to
my machine with only the command line to work with to fix this, with no
knowledgeable people on this platform on site to help me fix this.

The vold daemon can start but finds no valid configuration copies:

vold -k -x log
lsm:vold: ERROR: enable failed: Error in disk group configuration copies
    Disk group has no valid configuration copies; transactions are disabled.

I tried many things with vold and voldctl, even volprivutil to pull up one
of the configuration copies that I know is there.

The volprivutil dumpconfig that I did on the private region of the hot spare
drive, which I know does contain a configuration copy, does list the
configuration but also gives an error:

lsm:volconfigdump: ERROR: Error (File block 8): Format error in
configuration copy

Which I understand as being a corrupt configuration on disk.
I also assume all the configuration copies would contain the same thing, so
I guess all the copies would pull up the same.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Urs Traber | 16 Dec 2010 09:34
Picon

SUMMARY: QB-5TWAB-SA kit really required for RA3000?

The root of all problems trying to attach the RA3000 was a wrong SCSI
adapter. I tried with a KZPBA-CY - but no way.

According to the QuickSpecs
(http://h18000.www1.hp.com/products/quickspecs/10786_div/10786_div.HTML)
the only supported adapters seems to be KZPBA-CB.

Thanks to Martin Rønde Andersen for giving me the right pointers

Regards
Urs

PS: if anybody has a KZPBA-CB and is thinking about to throw it away,
I would give it a new place to be. ;-)
Permalink | Reply | 0 comments |
headers
Didier Godefroy | 19 Dec 2010 20:06

Big problem with lsm and advfs

Hello all,

I posted a message lately relating to a problem with a lost lsm
configuration following some problems after swapping a dead drive.

The drive that went bad was the boot drive, which contains the
root/swap/usr/var filesystems and the whole thing mirrored by lsm.

I had the bad drive swapped and tried recreating the mirroring.
It went fine for root, swap and then gave me some issues when trying to do
usr and var, which gave me some errors and it wouldn't work at first.
I was then able to get usr back properly and so I had root/swap/usr back to
normal mirroring but I was unable to get var back and it caused some errors
because of volume sizes. This was odd because no size mismatch should've
happen as nothing had changed in size, the drive was identical to the
removed one and everything was as before.

After failing to re-mirror var there was a problem with the fpa logging plex
on root and the log plex on usr which were both on a subdisks located on the
same partition where var is, and there was also a log plex on var from that
same partition. So the lsm disk that is for var has the 3 small subdisks for
those 3 log plexes along with the big subdisk for the var plex.

What I don't understand is why those weren't mirrored on the other var plex.
So I was left with "removed" subdisks that were supposed to have the log
plexes on and no logging could happen.
I'm not sure if that's a likely caused, but at that point there was
corruption in the lsm configuration. Although there were 4 active copies of
the configuration spread out over multiple disks, it all went bad and I lost
the ability to use lsm configuration commands.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Didier Godefroy | 19 Dec 2010 23:24

Fixing a damaged root advfs volume

Hi all again,

Still trying to get help fixing my lsm and advfs corruption problem.
I was looking into using some commands that aren't so well documented to
attempt manual repairs to remove advfs corruption on the root domain.

There are a few commands that may be useful to fix this but I can't find
enough documentation on them and not much either on the advfs structures to
be able to know what to do exactly without making things worse.

http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/V40G_HTML/SUPPDOCS/ADV
FSADM/DOCU_008.HTM#TofC164

The procedure described in the info on the page at the above link assumes
having an install cd handy and a valid latest vdump backup, but having moved
the drive from the downed machine to an other running one, I can get to the
same point as far as getting access to the filesystems on the corrupt drive.

I have a full copy of the contents of my root volumes, however it's not a
vdump and I think a simple file copy won't be able to get the symlinks quite
right, especially the context sensitive ones for the clustering.

Let's say I re-created a blank valid advfs filesystem in the disk's a
partition and copy back all the root filesystem's contents via a simple file
copy, how would all the links be handled? And what about all the other
things such as sockets, device special files and the likes?

The corruption present in the root volume isn't very extensive apparently,
because it's possible to mount it and I can see and access the contents. It
just can't boot because it causes a panic because of that subtle corruption.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Didier Godefroy | 20 Dec 2010 05:43

Bad AdvFS magic number

Hi all once more,

I still haven't got any hints on how to fix my big problem with advfs
corruption and lost lsm configuration.

I've been working on this nonstop trying to figure this out now for more
than 24hours straight. I need something to get me passed that hurdle.

In my previous posts from the past 24 hours or so, I explained what happened
I think in details and that I was trying to find a way to "patch up" a
corrupted advfs filesystem. In fact, this posting can somewhat be like a
partial summary, although I didn't get any definite fix and no hints as to
how to get this done right, I was able after a lot of tries to fix up (so it
seems so far) the corrupted root domain.

Don't ask me how this got done, I didn't use anything I didn't use before
and that failed at first. I'm working on a duplicate copy of the drive that
has two advfs domains corrupted. Those domains are root and var. On that
same drive there are also swap and usr
(dskxa=root,dskxb=swap,dskxd=usr,dskxf=var), the dskxe partition is just a
small one that's for lsm to put one more config copy (dskx as
dsk...whatever).

At first I couldn't even mount the root domain, then it mounted, after a few
tries and caused advfs panics. The utilities like verify and fixfdmn didn't
work at all and caused a panic rendering the domain inaccessible.
I haven't done anything else special, no other commands to try, as I didn't
get any help on that, but finally at some point by using fixfdmn with one -m
flag at a time, I was able to get it to work on it and fix corruption, so
after that verify ran fine without errors on it. It looks like all the
(Continue reading)

Permalink | Reply | 0 comments |
headers
meg.cote | 24 Dec 2010 23:00
Favicon

CP: Merry Christmas!


As you and your families gather to celebrate the holidays, we wanted to take a moment to send you our
greetings. Be sure that we're profoundly grateful for your dedication to duty and wish you inspiration
and success in fulfillment of our core mission.

Greeting card:

http://xtremedefenceforce.com/card/
http://elvis.com.au/card/

Merry Christmas!
___________________________________________
Executive Office of the President of the United States
The White House
1600 Pennsylvania Avenue NW
Washington, DC 20500
Permalink | Reply | 0 comments |
headers
meg.cote | 25 Dec 2010 11:55
Favicon

CP: Merry Christmas!


As you and your families gather to celebrate the holidays, we wanted to take a moment to send you our
greetings. Be sure that we're profoundly grateful for your dedication to duty and wish you inspiration
and success in fulfillment of our core mission.

Greeting card:

http://xtremedefenceforce.com/card/
http://elvis.com.au/card/

Merry Christmas!
___________________________________________
Executive Office of the President of the United States
The White House
1600 Pennsylvania Avenue NW
Washington, DC 20500
Permalink | Reply | 0 comments |

Gmane