[27375] in Hotline Meeting
Re: Bombardier
daemon@ATHENA.MIT.EDU (Sam Hartman)
Thu Mar 16 00:10:52 1995
To: pmccormi@MIT.EDU
Cc: hotline@MIT.EDU, cprivate@MIT.EDU, rs6kswat@MIT.EDU, hartmans@MIT.EDU
In-Reply-To: Your message of "Wed, 15 Mar 1995 22:11:59 EST."
<9503160312.AA06196@navigator.MIT.EDU>
Date: Thu, 16 Mar 1995 00:10:44 EST
From: Sam Hartman <hartmans@MIT.EDU>
I think bombardier is suffering from a bad hard disk (I'd say
SCSI controller, but that was just replaced). I booted with 3.2.5
installation disks, and it hung on 868 (configuring/detecting
integrated SCSI). Once it got past that code, it got to c31, but
nothing came up on the console.
I booted first with 325.bosboot, then inserted 325.disp.ext
(yes, I made sure I inserted this before display), then I stuck in
325.display. Did I do anything wrong, or should the monitor have
worked?
Anyway, I decided to make sure 3.2.3 didn't work. I booted
with 32.bosboot then 32.display then 32.instl.maint. It let me into a
root shell, but importvg -y rootvg hdisk0 failed. It said it couldn't
open the physical volume (hdisk0) but didn't return an OS errno, so no
useful information was gained.
On the install menu, hdisk0 was listed as a 0Mb disk with
unknown volume ID. This is probably a sign of a hardwere problem.
I suggest that hotline deal with any possible hardware problem
and get a stable version of 3.2.3e (the standard Athena release)
installed. After about a week with the old software, I'll run the
update and see if problems start happening again.
I would appreciate it if rs6kswat continues to be informed,
even while the machine is running 3.2. This way, we can get a
baseline to compare the beta against.
I am sorry for all the down time this has caused. I would
like to thank you for your continued patience in working with us.
--Sam
