RE: DEC RF30 Integrated Storage Element Service Guide
> -Original Message- > From: cctalk On Behalf Of Glen Slick via > cctalk > Sent: 02 January 2022 18:07 > To: General Discussion: On-Topic and Off-Topic Posts > > Subject: Re: DEC RF30 Integrated Storage Element Service Guide > > On Sun, Jan 2, 2022 at 9:22 AM Rob Jarratt via cctalk > wrote: > > > > Hmm... There was already a terminator installed. I tried to remove it > > in case there was some kind of double termination, but that didn't > > seem to resolve it. The terminator is good because the machine works > > with other disks. > > If other disks work when they are swapped in without making any other > changes, it is probably not a termination issue. Yes, other disks work and I don't think it can be a termination problem. However, I did check your points below and everything does seem to be correct, please see responses below. The problem persists though. > > However, you still might want to double check that the DSSI bus is properly > terminated at both ends. If the M7769 KFQSA is attached to a bulkhead > connector panel, there are two versions, one with a single DSSI connector, > and one with two DSSI connectors. My KFQSA has only one DSSI connector and it is not connected to a bulkhead connector panel. > > If the bulkhead connector panel has a single DSSI connector, there should be > SIP terminators installed on the M7769 KFQSA next to the DSSI connector on > the M7769 KFQSA as one end of the DSSI bus. There are terminators installed behind the DSSI connector. The KFQSA manual says they should be removed if using a bulkhead connector, but I am not. I have the cable coming down from the storage area into the DSSI connector. > > If the bulkhead connector panel has two DSSI connectors, the SIP > terminators should be removed on the M7769 KFQSA next to the DSSI > connector on the M7769 KFQSA, and there should be an external terminator > on one of the two DSSI connectors on the bulkhead connector panel. > > If there is no bulkhead connector panel connected directly to the > M7769 KFQSA, and instead it is connected to an internal DSSI bus cable inside > the chassis, and the M7769 KFQSA is at the end of the internal DSSI bus cable, > there should be SIP terminators installed on the M7769 KFQSA next to the > DSSI connector on the M7769 KFQSA as one end of the DSSI bus. I would > expect the other end of the internal DSSI bus cable to connect to a bulkhead > connector panel, which should have an external terminator attached as the > other end of the DSSI bus. This is indeed the case.
Re: DEC RF30 Integrated Storage Element Service Guide
On Sun, Jan 2, 2022 at 9:22 AM Rob Jarratt via cctalk wrote: > > Hmm... There was already a terminator installed. I tried to remove it in > case there was some kind of double termination, but that didn't seem to > resolve it. The terminator is good because the machine works with other > disks. If other disks work when they are swapped in without making any other changes, it is probably not a termination issue. However, you still might want to double check that the DSSI bus is properly terminated at both ends. If the M7769 KFQSA is attached to a bulkhead connector panel, there are two versions, one with a single DSSI connector, and one with two DSSI connectors. If the bulkhead connector panel has a single DSSI connector, there should be SIP terminators installed on the M7769 KFQSA next to the DSSI connector on the M7769 KFQSA as one end of the DSSI bus. If the bulkhead connector panel has two DSSI connectors, the SIP terminators should be removed on the M7769 KFQSA next to the DSSI connector on the M7769 KFQSA, and there should be an external terminator on one of the two DSSI connectors on the bulkhead connector panel. If there is no bulkhead connector panel connected directly to the M7769 KFQSA, and instead it is connected to an internal DSSI bus cable inside the chassis, and the M7769 KFQSA is at the end of the internal DSSI bus cable, there should be SIP terminators installed on the M7769 KFQSA next to the DSSI connector on the M7769 KFQSA as one end of the DSSI bus. I would expect the other end of the internal DSSI bus cable to connect to a bulkhead connector panel, which should have an external terminator attached as the other end of the DSSI bus.
RE: DEC RF30 Integrated Storage Element Service Guide
Hmm... There was already a terminator installed. I tried to remove it in case there was some kind of double termination, but that didn't seem to resolve it. The terminator is good because the machine works with other disks. Regards Rob > -Original Message- > From: Rob Jarratt > Sent: 02 January 2022 15:52 > To: 'dave.g4...@gmail.com' ; > 'r...@jarratt.me.uk' ; 'General Discussion: On-Topic and > Off-Topic Posts' > Subject: RE: DEC RF30 Integrated Storage Element Service Guide > > I have other DSSI machines to try them in, just a bit less easy to install them > in those machines. Going to check the termination now. > > > -Original Message- > > From: dave.g4...@gmail.com > > Sent: 02 January 2022 15:19 > > To: r...@jarratt.me.uk; 'General Discussion: On-Topic and Off-Topic Posts' > > > > Subject: RE: DEC RF30 Integrated Storage Element Service Guide > > > > Rob, > > If that is not the issue, do you need to try them in the MicroVax 4000 here? > > Dave > > (p.s. can SCSI terminators fit in a DSSI bus socket by mistake) > > > > > -Original Message- > > > From: Rob Jarratt > > > Sent: 02 January 2022 14:05 > > > To: dave.g4...@gmail.com; r...@jarratt.me.uk; 'General Discussion: > > > On- Topic and Off-Topic Posts' > > > Subject: RE: DEC RF30 Integrated Storage Element Service Guide > > > > > > I thought I had checked, but I can double check just to be sure. > > > Thanks > > for > > > the suggestion, it certainly feels like it could be something like this. > > > > > > > -Original Message----- > > > > From: dave.g4...@gmail.com > > > > Sent: 02 January 2022 13:01 > > > > To: r...@jarratt.me.uk; 'Rob Jarratt' > > > > ; > > > 'General > > > > Discussion: On-Topic and Off-Topic Posts' > > > > Subject: RE: DEC RF30 Integrated Storage Element Service Guide > > > > > > > > Rob, > > > > > > > > I know this is probably a stupid suggestion, but are they > > > > terminated correctly? > > > > > > > > Dave > > > > > > > > > > > > > -Original Message- > > > > > From: cctalk On Behalf Of Rob > > > > > Jarratt via cctalk > > > > > Sent: 02 January 2022 07:30 > > > > > To: 'General Discussion: On-Topic and Off-Topic Posts' > > > > > > > > > > Subject: RE: DEC RF30 Integrated Storage Element Service Guide > > > > > > > > > > Can anyone help me to understand why all my RF30 disks report > > > > > the same diagnostic code 0x300B? > > > > > > > > > > Thanks > > > > > > > > > > Rob > > > > > > > > > > > -Original Message- > > > > > > From: Rob Jarratt > > > > > > Sent: 23 December 2021 17:46 > > > > > > To: r...@jarratt.me.uk; 'Rob Jarratt' > > > > > > ; > > > > > 'General > > > > > > Discussion: On-Topic and Off-Topic Posts' > > > > > > > > > > > > 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 > > > > &
RE: DEC RF30 Integrated Storage Element Service Guide
I have other DSSI machines to try them in, just a bit less easy to install them in those machines. Going to check the termination now. > -Original Message- > From: dave.g4...@gmail.com > Sent: 02 January 2022 15:19 > To: r...@jarratt.me.uk; 'General Discussion: On-Topic and Off-Topic Posts' > > Subject: RE: DEC RF30 Integrated Storage Element Service Guide > > Rob, > If that is not the issue, do you need to try them in the MicroVax 4000 here? > Dave > (p.s. can SCSI terminators fit in a DSSI bus socket by mistake) > > > -Original Message- > > From: Rob Jarratt > > Sent: 02 January 2022 14:05 > > To: dave.g4...@gmail.com; r...@jarratt.me.uk; 'General Discussion: On- > > Topic and Off-Topic Posts' > > Subject: RE: DEC RF30 Integrated Storage Element Service Guide > > > > I thought I had checked, but I can double check just to be sure. > > Thanks > for > > the suggestion, it certainly feels like it could be something like this. > > > > > -Original Message- > > > From: dave.g4...@gmail.com > > > Sent: 02 January 2022 13:01 > > > To: r...@jarratt.me.uk; 'Rob Jarratt' ; > > 'General > > > Discussion: On-Topic and Off-Topic Posts' > > > Subject: RE: DEC RF30 Integrated Storage Element Service Guide > > > > > > Rob, > > > > > > I know this is probably a stupid suggestion, but are they terminated > > > correctly? > > > > > > Dave > > > > > > > > > > -Original Message- > > > > From: cctalk On Behalf Of Rob > > > > Jarratt via cctalk > > > > Sent: 02 January 2022 07:30 > > > > To: 'General Discussion: On-Topic and Off-Topic Posts' > > > > > > > > Subject: RE: DEC RF30 Integrated Storage Element Service Guide > > > > > > > > Can anyone help me to understand why all my RF30 disks report the > > > > same diagnostic code 0x300B? > > > > > > > > Thanks > > > > > > > > Rob > > > > > > > > > -Original Message- > > > > > From: Rob Jarratt > > > > > Sent: 23 December 2021 17:46 > > > > > To: r...@jarratt.me.uk; 'Rob Jarratt' > > > > > ; > > > > 'General > > > > > Discussion: On-Topic and Off-Topic Posts' > > > > > > > > > > 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 DefaultType Radix > > > > > - - > > > > > MSCPNVR 2020202020202020 2020202020202020 > > > > > 2020202020202020 2020202020202020 > > > > >
RE: DEC RF30 Integrated Storage Element Service Guide
Rob, If that is not the issue, do you need to try them in the MicroVax 4000 here? Dave (p.s. can SCSI terminators fit in a DSSI bus socket by mistake) > -Original Message- > From: Rob Jarratt > Sent: 02 January 2022 14:05 > To: dave.g4...@gmail.com; r...@jarratt.me.uk; 'General Discussion: On- > Topic and Off-Topic Posts' > Subject: RE: DEC RF30 Integrated Storage Element Service Guide > > I thought I had checked, but I can double check just to be sure. Thanks for > the suggestion, it certainly feels like it could be something like this. > > > -Original Message- > > From: dave.g4...@gmail.com > > Sent: 02 January 2022 13:01 > > To: r...@jarratt.me.uk; 'Rob Jarratt' ; > 'General > > Discussion: On-Topic and Off-Topic Posts' > > Subject: RE: DEC RF30 Integrated Storage Element Service Guide > > > > Rob, > > > > I know this is probably a stupid suggestion, but are they terminated > > correctly? > > > > Dave > > > > > > > -Original Message- > > > From: cctalk On Behalf Of Rob > > > Jarratt via cctalk > > > Sent: 02 January 2022 07:30 > > > To: 'General Discussion: On-Topic and Off-Topic Posts' > > > > > > Subject: RE: DEC RF30 Integrated Storage Element Service Guide > > > > > > Can anyone help me to understand why all my RF30 disks report the > > > same diagnostic code 0x300B? > > > > > > Thanks > > > > > > Rob > > > > > > > -Original Message- > > > > From: Rob Jarratt > > > > Sent: 23 December 2021 17:46 > > > > To: r...@jarratt.me.uk; 'Rob Jarratt' > > > > ; > > > 'General > > > > Discussion: On-Topic and Off-Topic Posts' > > > > 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 DefaultType Radix > > > > - - > > > > MSCPNVR 2020202020202020 2020202020202020 > > > > 2020202020202020 2020202020202020 > > > > 2020202020202020 2020202020202020 > > > > 2020202020202020 2020202020202020StringHex RO > > > > UNITID1502401193918703 0 QuadwordHex RO > > > > ALLCLASS 0 0 ByteDec B > > > > MEDIAID 2264601E 2264601E LongwordHex RO U > > > > UNITNUM 0 0 WordDec U > > > > FIVEDIME 1 1 Boolean0/1 B > > > > FORCEUNI 1 1 Boolean0/1 U > > > > FORCECID 1 1 Boolean0/1 RO > > > > CNT_TMO 6060 WordDec RO > > > > > > > > PARAMS> set unitnum 1 > > > > > > > > PARAMS
RE: DEC RF30 Integrated Storage Element Service Guide
I thought I had checked, but I can double check just to be sure. Thanks for the suggestion, it certainly feels like it could be something like this. > -Original Message- > From: dave.g4...@gmail.com > Sent: 02 January 2022 13:01 > To: r...@jarratt.me.uk; 'Rob Jarratt' ; 'General > Discussion: On-Topic and Off-Topic Posts' > Subject: RE: DEC RF30 Integrated Storage Element Service Guide > > Rob, > > I know this is probably a stupid suggestion, but are they terminated > correctly? > > Dave > > > > -Original Message- > > From: cctalk On Behalf Of Rob Jarratt > > via cctalk > > Sent: 02 January 2022 07:30 > > To: 'General Discussion: On-Topic and Off-Topic Posts' > > > > Subject: RE: DEC RF30 Integrated Storage Element Service Guide > > > > Can anyone help me to understand why all my RF30 disks report the same > > diagnostic code 0x300B? > > > > Thanks > > > > Rob > > > > > -Original Message- > > > From: Rob Jarratt > > > Sent: 23 December 2021 17:46 > > > To: r...@jarratt.me.uk; 'Rob Jarratt' ; > > 'General > > > Discussion: On-Topic and Off-Topic Posts' > > > 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 DefaultType Radix > > > - - > > > MSCPNVR 2020202020202020 2020202020202020 > > > 2020202020202020 2020202020202020 > > > 2020202020202020 2020202020202020 > > > 2020202020202020 2020202020202020StringHex RO > > > UNITID1502401193918703 0 QuadwordHex RO > > > ALLCLASS 0 0 ByteDec B > > > MEDIAID 2264601E 2264601E LongwordHex RO U > > > UNITNUM 0 0 WordDec U > > > FIVEDIME 1 1 Boolean0/1 B > > > FORCEUNI 1 1 Boolean0/1 U > > > FORCECID 1 1 Boolean0/1 RO > > > CNT_TMO 6060 WordDec 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 On Behalf Of Rob > > > > Jarratt via cctalk > > > > Sent: 23 December 2021 09:45 > > > > To: 'General Discussion: On-Topic and Off-Topic Posts' > > > > > > > > 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: > >
RE: DEC RF30 Integrated Storage Element Service Guide
Rob, I know this is probably a stupid suggestion, but are they terminated correctly? Dave > -Original Message- > From: cctalk On Behalf Of Rob Jarratt via > cctalk > Sent: 02 January 2022 07:30 > To: 'General Discussion: On-Topic and Off-Topic Posts' > > Subject: RE: DEC RF30 Integrated Storage Element Service Guide > > Can anyone help me to understand why all my RF30 disks report the same > diagnostic code 0x300B? > > Thanks > > Rob > > > -Original Message- > > From: Rob Jarratt > > Sent: 23 December 2021 17:46 > > To: r...@jarratt.me.uk; 'Rob Jarratt' ; > 'General > > Discussion: On-Topic and Off-Topic Posts' > > 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 DefaultType Radix > > - - > > MSCPNVR 2020202020202020 2020202020202020 > > 2020202020202020 2020202020202020 > > 2020202020202020 2020202020202020 > > 2020202020202020 2020202020202020StringHex RO > > UNITID1502401193918703 0 QuadwordHex RO > > ALLCLASS 0 0 ByteDec B > > MEDIAID 2264601E 2264601E LongwordHex RO U > > UNITNUM 0 0 WordDec U > > FIVEDIME 1 1 Boolean0/1 B > > FORCEUNI 1 1 Boolean0/1 U > > FORCECID 1 1 Boolean0/1 RO > > CNT_TMO 6060 WordDec 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 On Behalf Of Rob > > > Jarratt via cctalk > > > Sent: 23 December 2021 09:45 > > > To: 'General Discussion: On-Topic and Off-Topic Posts' > > > > > > 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 On Behalf Of Rob > > > > Jarratt via cctalk > > > > Sent: 22 December 2021 15:59 > > > > To: General Discussion: On-Topic and Off-Topic Posts > > > > > > > > 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
RE: DEC RF30 Integrated Storage Element Service Guide
Can anyone help me to understand why all my RF30 disks report the same diagnostic code 0x300B? Thanks Rob > -Original Message- > From: Rob Jarratt > Sent: 23 December 2021 17:46 > To: r...@jarratt.me.uk; 'Rob Jarratt' ; 'General > Discussion: On-Topic and Off-Topic Posts' > 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 DefaultType Radix > - - > MSCPNVR 2020202020202020 2020202020202020 > 2020202020202020 2020202020202020 > 2020202020202020 2020202020202020 > 2020202020202020 2020202020202020StringHex RO > UNITID1502401193918703 0 QuadwordHex RO > ALLCLASS 0 0 ByteDec B > MEDIAID 2264601E 2264601E LongwordHex RO U > UNITNUM 0 0 WordDec U > FIVEDIME 1 1 Boolean0/1 B > FORCEUNI 1 1 Boolean0/1 U > FORCECID 1 1 Boolean0/1 RO > CNT_TMO 6060 WordDec 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 On Behalf Of Rob Jarratt > > via cctalk > > Sent: 23 December 2021 09:45 > > To: 'General Discussion: On-Topic and Off-Topic Posts' > > > > 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 On Behalf Of Rob > > > Jarratt via cctalk > > > Sent: 22 December 2021 15:59 > > > To: General Discussion: On-Topic and Off-Topic Posts > > > > > > 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
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 DefaultType Radix - - MSCPNVR 2020202020202020 2020202020202020 2020202020202020 2020202020202020 2020202020202020 2020202020202020 2020202020202020 2020202020202020StringHex RO UNITID1502401193918703 0 QuadwordHex RO ALLCLASS 0 0 ByteDec B MEDIAID 2264601E 2264601E LongwordHex RO U UNITNUM 0 0 WordDec U FIVEDIME 1 1 Boolean0/1 B FORCEUNI 1 1 Boolean0/1 U FORCECID 1 1 Boolean0/1 RO CNT_TMO 6060 WordDec 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 On Behalf Of Rob Jarratt via > cctalk > Sent: 23 December 2021 09:45 > To: 'General Discussion: On-Topic and Off-Topic Posts' > > 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 On Behalf Of Rob Jarratt > > via cctalk > > Sent: 22 December 2021 15:59 > > To: General Discussion: On-Topic and Off-Topic Posts > > > > 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
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 On Behalf Of Rob Jarratt via > cctalk > Sent: 22 December 2021 15:59 > To: General Discussion: On-Topic and Off-Topic Posts > > 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
Re: DEC RF30 Integrated Storage Element Service Guide
Rob Jarratt wrote: 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. If anyone finds one, I would greatly appreciate a copy also. Thanks, Alan Frisbie
