[3121] in SIPB-AFS-requests
bloom-picayune and rosebud2 hardware changes
daemon@ATHENA.MIT.EDU (mhpower@MIT.EDU)
Tue Aug 18 03:11:23 1998
From: mhpower@MIT.EDU
To: rtfm-maintainers@MIT.EDU, sipb-afsreq@MIT.EDU
Date: Tue, 18 Aug 1998 03:11:02 EDT
I added a third external disk to bloom-picayune because svalente
wanted to provide a RedHat-Athena install server on that machine.
The disk is a Micropolis 3243 (4 Gb). As I understand it, it had at
one time been an AFS disk and was taken out a service due to some type
of problem. Since then, jhawk has tested the disk extensively and
found no remaining problems. At one time, the disk was going to be
used for testing Solaris 2.5.1 on bloom-beacon, but that project isn't
currently being pursued. In any case, it currently has two 2 Gb
partitions, one mounted on /redhat and one mounted on /u3. It has SCSI
id 4 and is at the end of the bloom-picayune SCSI chain.
In order to shut down bloom-picayune to connect the disk, I turned on
its monitor, which immediately failed in a rather spectacular way
(very loud popping noises and bright flashes). I took the monitor
off of the table and put it on the floor nearby, with a note taped to
it stating its condition. I then moved the rosebud2 monitor to
bloom-picayune. Since the space on top of rosebud2 was freed up by
this, I put the bloom-picayune disk there. Presumably when it's
necessary to connect a monitor to rosebud2, the monitor can be taken
off of bloom-picayune and temporarily set on top of this disk. It's
also possible that we'd want to move another DECstation monitor into
the machine room for the short term, depending on the status of the
rosebud2 replacement mentioned in [3120].
Matt
