From: Charles Ballowe (hangman@steelballs.org)
Date: Sat Mar 15 2003 - 15:38:21 EST
I have a system that seems to have corrupted it's hardware database. In the
past, I've had success doing something that I found in a former summary --
http://www.ornl.gov/cts/archives/mailing-lists/tru64-unix-managers/2002/09/msg00280.html
(steps listed at the end)
The rm /cluster/members/member/etc/dfsl.* step is returning with 2 files
that it fails to remove claiming that the file names are invalid arguements.
An 'ls' shows the files, but an 'ls -l' lists them as not existing.
When the system reboots, it does not recreate its hardware database as desired.
any ideas?
-charlie
system is an ES40 running 5.1A PK3
rm ./etc/dec*
rm ./etc/dccd.*
rm ./etc/dcdd.*
rm ./etc/dfsc.*
rm ./etc/dfsl.*
rm ./cluster/members/member/etc/cfginfo
rm ./etc/cfginfo
rm ./cluster/members/member/etc/dfsl.*
rm ./dev/tty0*
rm ./dev/lp*
rm ./dev/kevm*
rm ./dev/scp*
for dir in cport disk rdisk changer tape ntape; do
rm -rf ./devices/$dir
rm -rf ./cluster/members/member/$dir
rm ./dev/$dir
done
rm ./cluster/members/member/.Booted
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:11 EDT