🚀 go-pugleaf

I wonder if anybody can help ? Our explorer crashed in the
middle of a KEE session, and on re-booting, failed to find the FILE partition.
This is because it is failing to recognise the existence of the user hard disk
(unit 1). Commands such as print-disk-label give "illegal unit number" when 1 is
given as an argument. We've checked all the connections, and they appear solid.
All the systems software is on disk 0, which is being recognised, and all user
files are on disk 1. Booting works fine up until its tries to find the FILE
partition, when it aborts.

It is the only explorer in this country, with the result that there are no
available service engineers, without paying multiple amounts of cash to have
one flown in from England (there's no maintenance contract ...). Temporarily,
there is no systems manager, either.

Are there any safe actions (i.e non-disk-corrupting) which a
non-systems-manager-but-good-programmer type of person (me) can take to see
if we can fix the problem, before having to call in the engineers ?
Is there some entry in a system table somewhere which needs modification ?
If so, how ?

				Thanks,

					Brian Mathews.

P.S. This is kind of urgent - there's a whole thesis implementation on that
     disk, which is due in October. And it's not possible to transfer to another
     machine with the back-ups, 'cos there is no other machine ...


E-mail : bmathews@tcdcs.uucp
S-mail : c/o Dept. of Computer Science, Trinity College, Dublin 2, Ireland.