From: Ambrose_Earle@shamrockfoods.com
Date: Sat Jul 27 2002 - 18:37:36 EDT
Apparently we own the third server to ever experience this anomaly.
Our es40/5.1/PK3 was ungracefully shutdown by a power outage. We brought
it back up just fine, but then had a few hardware issues to deal with.
Once a few components were replaced.... it wouldn't boot. We could take it
into single user mode, but we were basically seeing everything mentioned
below. Looking at /etc/sia showed a "bad" matrix.conf - an ls of the
directory would say that it was missing and a cp over the top would say bad
argument. We moved /etc/sia to /etc/siax, recreated sia and then copied
back what we could. We renamed .new..matrix.conf to matrix.conf and were
able to bring it out of single user mode. At that point we recreated
matrix.conf again (siacfg -l BSD libc.so) and then rebooted and it's been
fine ever since.
----- Forwarded by Ambrose Earle/IS/ShamrockPhx/US on 07/27/2002 03:35 PM
-----
Alex Harkema
<HarkemaA@vertis.nl> To: "'tru64-unix-managers@ornl.gov'" <tru64-unix-managers@ornl.gov>
Sent by: cc:
tru64-unix-managers-own Subject: (somewhat like a) SUMMARY: lsm fails to start
er@ornl.gov
09/21/2001 10:31 AM
Hi all,
There was a pretty good reasen why the system did not let me start the lsm
daemons (nor any, for that matter): In /etc/sia was the matrix.conf file
missing... This is 'the security integration architecture config file' (see
the man page for details) Patchkit 3 was installed.
However, I cannot find a single reason why this file was missing.
At the point we found out about this missing file, I already had taken my
OS disk(s) out of the lsm configuration (by editing all related files, like
sysconfigtab, inittab, fstab etcetera and adjusting the fdmns directories)
Still not able to mount those disks (as advfs domains) I reinstalled the
OS, reconfigured them to be lsm disks, and all seems fine again :-)
What worries me, is that the visiting Compaq Engineer encountered the
(almost exact) same thing (the missing matrix.conf) on another tru64 v5.1
machine (also lsm configured) a couple of weeks ago.
I have no idea when something is considered a bug; anyone seen this before?
Then this could be very well one!
Regards,
Alex Harkema
-----Original Message-----
From: Alex Harkema
Sent: Monday, September 17, 2001 4:09 PM
To: 'tru64-unix-managers@ornl.gov'
Subject: lsm fails to start
Hi managers,
An ES40 running tru64 v5.1 crashed a couple of hours ago (w/o any warning)
At startup I had to attach a serial console, for the system did not go to
the graphics console. (just a blue screen, not the prompt)
A show dev shows all the devices an in el is nothing worrying.
Booting in single user mode succeeds, but after that I am not able to start
de lsm volumes!
ps -ef | grep vol shows "vold -k boot" running.
The system says that I'm not privileged to run voldctl or voldisk (!)
mount -u / succeeds, but lsmbstart gives:
vold not enabled for transactions.
vold -k -m enable doesn't solve anything.
mount /usr (or any other volume) says:
/dev/vol/rootdg/usrvol is an invalid device or cannot be opened
I also tried to boot from the os mirror disk (dkb100 instead of dkb0)
This doesn't solve anything. (all the same errors)
I have no idea what to try next.
Any ideas, hints?
regards,
Alex Harkema
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:47 EDT