Admins:
The last post:
I was able to get the file system up by
boot -fi "genvmunix" -fl "s" <device name>
then I did a scu
scu> scan edt
scu>show edt
found that they moved one buss
cd /etc/fdmns/usr_domain
did a ls and found
rz16b -> /dev/rz16b
rm 16b (removed soft link)
then ln -s /dev/rz24b
mount -a
sizer -n HOSTNAME
umount /usr
rm /etc/fdmns/usr_domain/rz24b
cd /etc/fdmns/usr_domain
ln -s /dev/rz16b
reboot the system with old kernel
found the new entry for ewa0 (the fibre channel card)
entered the buss and controllers listings in the /sys/conf/HOSTNAME
configuration file with it named as SCSI4 instead of SCSI3
doconfig -c HOSTNAME
reboot
This fixed my problem. It appears that the card I added to the system will not
effect my orginal kernel (it doesn't recognize it) but does effect genvmunix
booting(it does recognize it) The kernel was numbering the new adapter as SCSI3
and moving the other devices to SCSI4 and making new device files; thus throwing
off my /usr mount and making getty unavailable.
As for the last part
>From Dr. Blinn,
If you are adding new hardware that was NOT supported in V4.0F *and*
is not already supported in your system (by an existing instance of
the adapter, say), then you need the new hardware supplement, which
is probably what the Admin has on the CD. The *current* one is the
"NHD 3" kit, it's been out for some time. If you have the latest
set of V4.0F patches installed, you may not need the NHD kit, since
it's really targetted at unpatched systems. Find the documentation
for both the NHD kit and the patch kit and READ THEM before you do
anything rash.
Thanks for the reponses,
Lee Brewer
Received on Fri Jun 15 2001 - 13:49:36 NZST