Date: Mon, 24 Apr 2000 10:19:11 -0500 (CDT)
From: Don Holmgren
Subject: Re: 2.5m obslog 000422 (MJD 51657)
On Sun, 23 Apr 2000, s. a. snedden wrote:
> APACHE POINT OBSERVATORY SDSS 2.5M
>
>                                  OBSERVING LOG
>
>                             Thursday April 22 2000
>
>                                   (MJD 51657)
...
>                            PROBLEMS IN DETAIL:
>                            ===================
>
> DA started out in paused state:
> -------------------------------
> The afternoon checkout was started using v3_13_2 of IOP. Everything
> appeared okay until we started an imager bias drift. The archiver was in
> a paused state and did not start archiving until an archResume was
> issued. At this point we got the
>  following error for all nodes:
>
> Apr 22 18:48:18 sdssid1    dArch      dsc_E_ivFrameCtx Invalid Frame
> context
>
> After the pool cleared out (after the archResume) and a new bias was
> started, archiving progressed normally. We are a little confused by this
> as the pool appeared to have old data in it, and a poolInit was done as
> part of the checkout.
I can't say for sure what happened, but one possibility is that the
archiver command queues had some old commands and the archivers were
paused.  If a poolInit happened before the archResume, those commands
would refer to frames no longer in the pool and we'd see this error
following the archResume.
If that explanation doesn't fit, this error causes me a bit of worry.
Please call me at the next occurrance.
>
>
> id3 Rimfire Failure:
> --------------------
>
> While bias drift 1397 was in progress, id3-1 complained with:
>
> Apr 22 19:51:26 sdssid3    dArch      dsc_I_archFailMsg Rimfire failure
> ID = 1
>  Status = 0xf1150401 0x1194080
> Apr 22 19:51:26 sdssid3    dArch      dsc_E_trcErr dscArch_CheckPrevOp:
> rstatus
> = 0x80014104, drive 1
> Apr 22 19:51:26 sdssid3    dArch      dsc_E_archShutDown1 Archiver
> shutting down
>  first drive
> Apr 22 19:51:26 sdssid3    dArch      dsc_E_archWrFail Tape write error
> while ar
> chiving frame 1397 22.43
>  .
>  .
>  .
> Apr 22 19:51:31 sdssid3    dArch      TEXTONLY Archiver: starting
> auto-recover,
> bad drive: 0, other drive: 1
> Apr 22 19:51:31 sdssid3    dArch      TEXTONLY Archiver: auto-recover
> rewinding
> good drive
>
> The autorecovery was successful.
This decodes as a "Hardware Error - Random Mechanical Positioning Error".
We should keep track of any drive reporting this sort of error - perhaps
the log book at the tape drives would be best.  This is the first time
that I've seen this error reported by a DLT.
Don H.