CDrom booting & Firmware woes.

From: Parris B. Wood <pwood_at_widomaker.com>
Date: Tue, 21 Apr 1998 21:54:23 -0400 (EDT)

Hi,

        After repeatedly trying to upgrade the firmware on my Dec
Multia/UDB from Srm V3.7-628 to V4.7 and from Arc V4.33 to V4.5 What
follows are the error messages I get when booting off of firmware cds V3.9
and V5.0.

*** Soft Error - Error #23 - SCSI
  sense key = 'Not Ready' (04|01) from dka0.0.0.6.0

Diagnostic Name ID Device Pass Test Hard/Soft 21-APR-2046
boot 00000073 0 0 0 12 21:46:17
*** End of Error ***

        At first I thought the culprit was the scsi card inside the multia
because the errors used to listed pka or dka0 randomly. The scsi card was
replaced by my vendor. There same error(s) persisted. I removed the hard
drive thinking there might be a conflict with the Segate drive (vendor
noted conflicts with segate, however it seems to be a happy clam).
Detaching the drive left only the cdrom on the chain. Same error. With
problems continuing after the removal of the seagate I changed the current
Toshiba for a Sun cdrom. No letup, both cdroms seem work in other
machines. Finally, I just linked the cdrom directly to the NCR card in
the multia to make sure the case was not defective. Brick wall.

        Well these errors usually do not prevent (95% of the time) the
firware cd or the digital unix os media cd from booting, but I run into
the following problem when trying to update the firmware from the update
cd:

Apu -> update srm
APU-I VERIFY LOADED ROM IMAGE
 0x52400
APU-I LOADED ROM IMAGE VERIFIED
APU-E ROM JUMPER ON ?

        At the end I see the "... JUMPER ON ?" message so I attempted to
verify the update. Below is what I got after verifying srm.
   
Apu -> verify srm
APU-I VERIFY LOADED ROM IMAGE
0x52400
APU-I LOADED ROM IMAGE VERIFIED
---> Rom2 offset 0x2 Loaded Value 0x8 Actual 0x4
0x3
Rom Verify Error
  
        I can't make any sense out of those messages as I do not recall
needing to set any jumpers on the multia to upgrade the firmware (although
the service manual never says anything on updating the firmware). I am
almost sure the booting error and failed rom update are related (probally
showing some ignorance here), but I am out of ideas at this point. Thanks
for your time and any help. Will summarize.

-
Parris Wood
  pawood_at_vt.edu.
  pwood_at_wilma.widomaker.com.


p.s. Digitla Unix V4.0B seems to be happy with my current hardware if that
helps in diagnosing the situation.
Received on Wed Apr 22 1998 - 03:50:26 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:37 NZDT