From: Alex Harkema (harkemaa@vertis.nl)
Date: Thu Feb 20 2003 - 05:41:40 EST
Hi all,
I just tried to upgrade from Tru64 v5.0a to v5.1a. It got me into a lot
of trouble:
configuration: alphaserver 4100 running tru64 v5.0a, no patchkits
applied
Alpha Systems firmware was V5.5-5
setld -i | grep -i hardware showed OSFHWBASE505
Put system in Single User mode, all checks (verify, quotacheck,
cdslinvchk) passed 100% OK: no warnings, no problems there.
I started the /sbin/installupdate
No optional kernel components
Not saving obsolete files
Checks on filetype(conflicts), obsolete files and filesystemspace.. all
OK: so far so good.
During de update process, the kernel build fails: "don't know how to
make kern/lockinfo.c Stop"
This seems to be an know bug.
I completed upgrade, ran "find /usr/sys -mtime +1500 -exec touch {} \;"
to touch the timestamps on those files.
Then the kernel build succeeds.
But, then, after that the next boot shows lots of errors, like:
Unlocking Ptys
make: don't know how to make aliases STOP
and
evmd: warning
evmd could not be started
and more like that
Graphical login comes up, but login failes (after couple of seconds
login returns)
cmdline login succeeds, but even commands like ping coredumps :-( Still
a great deal of files have the 1970 timestamp and /var/adm/messages
(even in their original location in member0/adm) don't have any new
entries (not even about last boot errors)
Files in /var/adm/smlogs don't seem to contain any scary messages: so
what is the problem?
Anyone encountered this before?? Is there a solution to this?
Thanks for responses in advance!
Alex
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:08 EDT