From: Andrew Raine (Andrew.Raine@mrc-dunn.cam.ac.uk)
Date: Mon Feb 10 2003 - 10:56:02 EST
Dear Managers,
I apologise for the delay in summarising the reposnses to my question -
I was very busy at the time, and I've been away since...
Many thanks to Tim Brown, Pat O'Brien, Colin Bull, Michael Polnick,
Mark Deiss, Joe Carrico, Rich Glazier and Shawn Cromer.
Most of whom told me the reaon that the alarm went off when I pulled
the disk out of the shelf - I han't done a "delete DISKXXXXX" first, so
the controller (reasonably) thought that it had failed.
As to why the bus-stalling buttons stopped working, Pat O'Brien had the
answer: "Every once in a while, one of my little buttons will move
up/down depending on perspective, and not come all the way backup
bumping into the faceplate on the controller."
Gentle application of my swiss-army-knife tweezers resulted in the
button popping out a little further, and everything reverting to
normal...
So, thanks again guys!
Regards,
Andrew
Original Question:
> Dear Managers,
>
> I wonder if anyone can shed some light on my latest problem?
>
> Our Tru64 cluster storage was recently migrated from an HSZ80
> controller to an HSG80 (which went fine!) but I'm now having problems
> adding new disks to the system.
>
> With the system running, I pressed the little button to stall one of
> the SCSI-buses, waited until all the orange lights came on on the disks
> on that bus, and pulled out one of those disks. As it happens, this
> was a disk which hadn't been allocated to any storageset yet.
>
> The storage system alarm came on, so I silenced it, waited for the
> system to quiesce, stalled the bus again, and replaced the disk.
>
> Then I proceded with two other buses, inserting new disks each time.
> After the second insertion, all the six bus-stalling buttons started
> flashing green, and eventually went out. However, now I can't insert
> any more disks, because none of the bus-stalling buttons do anything any
> more.
>
> Looking at the console, I saw an event had been logged (see below for
> the output). I'm not sure when this was, but I presume that this was
> when the alarm went off.
>
> I did a "run config" and the two new disks are recognised, but when I
> did a "locate diskXXXXX" none of the amber lights come on.
>
> So, I'm a bit stuck! The system is in production, so I'd rather not
> restart it, but perhaps this is essential?
>
> Can anyone offer any advice?
>
> Regards,
>
> Andrew
>
> --
> Dr. Andrew Raine, Head of IT, MRC Dunn Human Nutrition Unit,
> Wellcome Trust/MRC Building, Hills Road, Cambridge, CB2 2XY, UK
> phone: +44 (0)1223 252830 fax: +44 (0)1223 252835
> web: www.mrc-dunn.cam.ac.uk email: Andrew.Raine@mrc-dunn.cam.ac.uk
>
> Event log message on HSG80 console:
>
> %EVL--HSG--24-JAN-2003 14:47:13-- Instance Code: 030C4002
> Template: 81.(51)
> Occurred on 24-JAN-2003 at 14:47:13
> Power On Time: 0. Years, 134. Days, 11. Hours, 58. Minutes, 56. Seconds
> Controller Model: HSG80
> Serial Number: ZG02804764 Hardware Version: E12(2A)
> Software Version: V86F-10(BA)
> Unit Number: 111.(006F)
> Unit Software Version: 1.(01) Unit Hardware Version: 56.(38)
> Retry Level: 1. Retries: 0.
> Port: 1. Target: 11. LUN: 0.
> SCSI Device Type: 31.(1F)
> Device ID: "BD03664553" Device Serial Number: "2248CD8W"
> Device Software Revision Level: "3B08"
> SCSI Command Opcode: 0.(00)
> Sense Data Qualifiers: 0.(00)
> SCSI Sense Data:
> Error Code: 0.(00) {reserved}
> Information field is invalid
> Segment: 0.(00)
> Sense Key: 4.(04) HARDWARE ERROR
> ILI: 0 EOM: 0 FM: 0
> Information: 00000000
> Additional Sense Length: 0.(00)
> Command-Specific Information: 00000000
> ASC: 63.(3F) ASCQ: 133.(85)
> FRU: 0.(00) Sense-Key Specific: 000000
> Instance Code: 030C4002
-- Dr. Andrew Raine, Head of IT, MRC Dunn Human Nutrition Unit, Wellcome Trust/MRC Building, Hills Road, Cambridge, CB2 2XY, UK phone: +44 (0)1223 252830 fax: +44 (0)1223 252835 web: www.mrc-dunn.cam.ac.uk email: Andrew.Raine@mrc-dunn.cam.ac.uk
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:07 EDT