1 Jan
2022
1 Jan
'22
11:29 p.m.
Can anyone help me to understand why all my RF30 disks report the same
diagnostic code 0x300B?
Thanks
Rob
-----Original Message-----
From: Rob Jarratt <robert.jarratt at ntlworld.com>
Sent: 23 December 2021 17:46
To: rob at jarratt.me.uk; 'Rob Jarratt' <robert.jarratt at ntlworld.com>;
'General
Discussion: On-Topic and Off-Topic Posts'
<cctalk at classiccmp.org>
Subject: RE: DEC RF30 Integrated Storage Element Service Guide
I have tried three different RF30 disks, two of them from one source and
one
from a completely different source, so completely
different histories.
They
all give me the same diagnostic error code, 0x300B,
which seems to be too
much of a coincidence, so I think it may be something in my configuration.
I am using a MicroVAX 3800 (KA655 with KFQSA). When I power on, the fault
light comes on and then goes out after a while. This I believe is normal
behaviour. However, as soon as I try to access the disk (e.g. SHOW DEVICES
in the console firmware) the fault light come on and when I boot to VMS
(from a different disk), VMS can't see the drive.
I thought it might be some kind of DSSI ID conflict because I have an RF72
in
the machine at ID 0. Removing the RF72 does not change
the behaviour.
Installing an ID=0 plug on the RF30 does not change the behaviour. I set
the
DIP switches on the RF30s to have an ID=1 and still it
doesn't work and
PARAMS reports UNITNUM=0. I followed this page
http://mcmanis.com/chuck/computers/vaxen/dssi-plug.html but it didn't
work:
PARAMS> sho /mscp
Parameter Current Default Type Radix
--------- ---------------- ---------------- -------- -----
MSCPNVR 2020202020202020 2020202020202020
2020202020202020 2020202020202020
2020202020202020 2020202020202020
2020202020202020 2020202020202020 String Hex RO
UNITID 1502401193918703 0000000000000 Quadword Hex RO
ALLCLASS 0 0 Byte Dec B
MEDIAID 2264601E 2264601E Longword Hex RO U
UNITNUM 0 0 Word Dec U
FIVEDIME 1 1 Boolean 0/1 B
FORCEUNI 1 1 Boolean 0/1 U
FORCECID 1 1 Boolean 0/1 RO
CNT_TMO 60 60 Word Dec RO
PARAMS> set unitnum 1
PARAMS> set forceuni 0
PARAMS> write
Failed to acquire unit, cannot WRITE
Am I doing something wrong?
Thanks
Rob
> -----Original Message-----
> From: cctalk <cctalk-bounces at classiccmp.org> On Behalf Of Rob Jarratt
> via cctalk
> Sent: 23 December 2021 09:45
> To: 'General Discussion: On-Topic and Off-Topic Posts'
> <cctalk at classiccmp.org>
> Subject: RE: DEC RF30 Integrated Storage Element Service Guide
>
> I wonder if anyone knows what diagnostic code 300B means?
>
> >>>set host/dup/uqssp/disk 2 params
> PARAMS> status config
>
> Configuration:
> Node DIA0 is an RF30 controller
> Software RFX V103 built on 5-MAY-1989 13:18:42
> Electronics module name is EN94019334
> Unit is inoperative, error code 300B(X)
> Last known unit failure code 300B(X)
> In 60233 power-on hours, power has cycled 189 times
> System time is 5-MAY-1989 13:19:46
>
> Regards
>
> Rob
>
> > -----Original Message-----
> > From: cctalk <cctalk-bounces at classiccmp.org> On Behalf Of Rob
> > Jarratt via cctalk
> > Sent: 22 December 2021 15:59
> > To: General Discussion: On-Topic and Off-Topic Posts
> > <cctalk at classiccmp.org>
> > Subject: DEC RF30 Integrated Storage Element Service Guide
> >
> > I am looking for the service guide for the RF30 DSSI disk. It is not
> > on
> Manx and
> > not on BitSavers. Does anyone know of a copy? The part number is
> > apparently EK-RF30D-SV.
> >
> >
> >
> > Thanks
> >
> >
> >
> > Rob