I'd like to thank all those that replied. My problem, however, turned out
not to be the result of the upgrade but a scsi disk with an identity crisis.
The problem didn't manifest itself until the upgrade rebooted, therefore my
jumping to the conclusion that it was the upgrade that caused it. One of the
scsi disks on the BA350 cabinet thought he was one of the other disks in the
cabinet. This lead to the strange errors that I reported.
Thanks again,
Sheila
==========================================================================
Hi!
I have a DEC3000-800S. I decided to upgrade from 3.0 to 3.0B. I used
the installupdate script from CDROM. After the upgrade, the system
rebooted. When it came back up, two of my scsi disks have invalid
addresses (lots of CAM_ERROR logger messages). Also a couple of the
other drives have dirty file systems and didn't mount either. I could
run fsck on the drives with the dirty file systems and mount them.
However everytime the system comes up, I get the same problems. Also
no matter what I try, I can't get the two drives with invalid addresses
to mount. I tried upgrading the firmware to 5.2 with hopes that might
help. Alas no.
What happened and how do I fix it?!?!?!? Any help would be greatly
appreciated!!
Thanks,
Sheila
Received on Wed Mar 01 1995 - 09:19:49 NZDT