[26946] in Hotline Meeting
Bombardier reinstalled
daemon@ATHENA.MIT.EDU (Sam Hartman)
Sat Feb 18 20:18:32 1995
Date: Sat, 18 Feb 1995 20:18:24 -0500
From: Sam Hartman <hartmans@MIT.EDU>
To: cprivate@MIT.EDU, rs6kswat@MIT.EDU
Cc: hotline@MIT.EDU
I shoed up today, and bombardier wasn't booting; it was
cycling through numbers sometimes getting far enought o get to its
screen. After two attempts to cath the number where it was starting
over, I decided to give up and try booting with maintinance disks.
Mount warned that /usr was marked dirty and refused to mount it; this
alone would have explained most of the problems. However, fsck didn't
look like it was going to be particularly successful, so I decided
that solving the problem wasn't worth it.
Instead, I tested Richard's new bos.test image by reinstalling
the system with it.I believe the install was successful, but have not
confirmed this. (I will do so Sunday.)
As far as future action, I propose that we try installing the
update on other systems that are installed from the bos.325 image and
see if any problems result. While I don't know exactly what was wrong,
I suspect it is related to the fact that bombardier was already 3.2.5
when the update was applied. Hopefully, some fixes Richard made to
the scripts will prevent future problems, but we should test it out a
few more times.
Also, are there any machines in clusters already running
3.2.5? If not, then even if the update procedure does fail on two or
three machines, it should be a manageable problem.
--Sam
