4 Sep
2015
4 Sep
'15
12:01 p.m.
Johnny Billquist wrote:
Such small drives was meant for paging/swap locally, not more.
This makes sense in a cluster environment where the machine boots from
network and the Users data are on the net also.
Regards,
Holm
--
Technik Service u. Handel Tiffe, www.tsht.de, Holm Tiffe,
Freiberger Stra?e 42, 09600 Obersch?na, USt-Id: DE253710583
www.tsht.de, info at tsht.de, Fax +49 3731 74200, Mobil: 0172 8790 741
On 2015-09-04 18:19, Glen Slick wrote:
The can dump out several statistices and even registers from the MC68000
CPU at the time the error was occuring, that's documented, but not more.
The Users Manual says that the error codes could be found in the service
manual, but I don#?t think that there is one available for the DSSI disks
on the net.
I just acquired a KA640 VAX in a BA215 (thanks
Josh) which has one
working RF30 and one dead RF30 with failure code 300B(X). I don't have
copies of any manuals which list the error codes. I just figure at
this point that the drive is dead and there is nothing that can be
done to try to fix it.
You could/should try and run some diagnostics. Maybe they can print out
something more intelligible than just an error code? The working 150MB RF30 is too small for a useful
VMS system although
it would be a decent size if I set up the system as a PDP-11 with an
M7554-PB KDJ11-SB CPU instead of the VAX KA640.
Be aware that no PDP-11 system knows about DSSI. There is one Qbus DSSI
controller that looks like a simple MSCP controller, and that one should
work fine. Any that exposes more of DSSI will be a non-starter with a
PDP-11.
Johnny