9 Mar
2004
9 Mar
'04
2:26 p.m.
O Gurus assembled - hear my story:
Was at Mike Quinn's in the Area of the Bay on Saturday after a nice visit
to Sellam's ..... um.... place of business. ;}
Found a forlorn VAXStation 3100 M38 upside down in a stack of PCs, and
bought same for about twice the going rate. Of course, that amount of
money would still not get one a decent burrito, so I didn't pay much.
Getting it home and hooked up, it goes thru the usual VAXStation boot
sequence ending in the >>> chevron prompt.
Attempting to boot, >>> b (ret)
produces a 1 minute wait and returns
40 NOSUCHDEV
06 HLT INST
PC=00000C66
the first time after power-up and
40 NOSUCHDEV
84 FAIL
subsequently to [back-panel button] resetting and re-attempting a boot.
This was a DEC-owned machine, it has a DEC property/asset tag on it, and
the drive is a DEC RZ23-E (Connor). If it's running, it's the damn
quietest HD I've ever encountered. The drive is getting it's proper
voltages, +5 and +12, and upon power up the faintest of 'clicks' can be
heard within it (parking solenoid??) and then nothing.
I have tried the judicious use of repetitive impulse torque normal to
the plane of rotation of the platters (I held it and banged a corner with
the handle of a screwdriver) in case the spindle was perhaps stuck.
SO: I'd love to know what's on this HD, but it's possible to also form
the assumption that it has gone to be with it's Honorable Ancestors and
will not return this way again.
Any thoughts / ideas?
Thanking Y'all in advance:
Cheers
John
9 Mar
9 Mar
3:05 p.m.
This was a DEC-owned machine, it has a DEC
property/asset tag on it, and
the drive is a DEC RZ23-E (Connor). If it's running, it's the damn
<snip>
SO: I'd love to know what's on this HD, but
it's possible to also form
the assumption that it has gone to be with it's Honorable Ancestors and
will not return this way again.
If it's an RZ23 the VAXstation most likely booted off of a cluster disk, and
used the RZ23 as a swap disk. The RZ23 is only about 100MB. Find yourself
a RZ25 or RZ26 and replace it. If you're going to be running V7.2 or later,
any 1GB SCSI HD should work nicely as the boot disk.
Zane
3:06 p.m.
Getting it home and hooked up, it goes thru the
usual VAXStation boot
sequence ending in the >>> chevron prompt.
Attempting to boot, >>> b (ret)
produces a 1 minute wait and returns
40 NOSUCHDEV
06 HLT INST
PC=00000C66
the first time after power-up and
40 NOSUCHDEV
84 FAIL
Not a real guru, but: you might try SHO DEV at the chevron. My
4000VLC could be set to boot from a device (like the ethernet) that's
not working, and I'm not so sure it would necessarily spin the hard
drive if it wasn't trying to boot from it. SHO DEV seems to do that,
though, as well as telling whether the drive electronics are
correctly describing it over the SCSI cable, SCSI is working, etc.
Is that available on a 3100? Gurus? Anyone there?
--
- Mark
210-522-6025, page 888-733-0967
3:59 p.m.
On Tue, 9 Mar 2004, Mark Tapley wrote:
Not a real guru, but: you might try SHO DEV at the
chevron. My
4000VLC could be set to boot from a device
O my yes but you *are* The Guru! That's exactly what was needed - 'SHO
DEV' at the chevron spun up the poor unoffending disk that Neanderthal
Sysop was so recently beating on.
And then I could:
>> SHO BOOT
DKA300
but of course
>>B DKA300:
42 NOSUCHFILE
84 FAIL
because there's no OS, it's most likely just a swap device as Zane points
out below.
But I
SET BOOT DKA300
so at least
>>B
tries to boot from the RZ23, which naturally tells me to go away.
So now I'll plug a SCSI CDROM into it and give it a real OS and then
maybe I can still see if there's anything mind-altering on the drive
Anyway, if nothing else I have another known good working base system,
should something Permanent happen to my other 3100. Plus I learned various
cool things in the process.
Tremendous T-H-A-N-X to Y'All!!
Cheers
John
7:39 p.m.
On Tue, 9 Mar 2004, John Lawson wrote:
Attempting to boot, >>> b (ret)
produces a 1 minute wait and returns
40 NOSUCHDEV
06 HLT INST
PC=00000C66
the first time after power-up and
40 NOSUCHDEV
84 FAIL
OK. This means that it tried, but could not find or use the
device that was defined as "default boot device" in the NVRAM.
This was a DEC-owned machine, it has a DEC
property/asset tag on it, and
the drive is a DEC RZ23-E (Connor). If it's running, it's the damn
quietest HD I've ever encountered. The drive is getting it's proper
voltages, +5 and +12, and upon power up the faintest of 'clicks' can be
heard within it (parking solenoid??) and then nothing.
OK, that sounds like an RZ23
allright.
Try to see what is in there by doing a
>> show dev
at the prompt. This will give you a list of disks, tapes, and whatnot.
Assuming DEC followed its own config rules, the RZ23 is at SCSI ID#3,
meaning it will show up as DKA3: in that list. You can (or, should be
able to) boot it with
>> boot dka3:
if it still has a valid system on it. If not, you need to get together
with someone who know how to install or net-install it :)
Fred
--
Fred N. van Kempen, DEC (Digital Equipment Corporation) Collector/Archivist
Visit the VAXlab Project at http://VAXlab.pdp11.nl/
Visit the Archives at http://www.pdp11.nl/
Email: waltje(a)pdp11.nl BUSSUM, THE NETHERLANDS / Mountain View, CA, USA
11:32 p.m.
Assuming DEC followed its own config rules, the RZ23
is at SCSI ID#3,
meaning it will show up as DKA3: in that list. You can (or, should
be able
to) boot it with
>> boot dka3:
Wouldn't SCSI ID 3 show up as DKA300:? And you'd want to do a
>> boot DKA300:
Anyway, you should just follow whatever the "SHOW DEV" command shows you for
disks. It's probably that the default stored in the NVRAM is not correct
(maybe a drive was removed), never set, or the NVRAM is invalid.
- Bob
7593
days inactive
7594
days old
5 comments
5 participants
participants (5)
-
bob_lafleur＠technologist.com -
healyzh＠aracnet.com -
jpl15＠panix.com -
mtapley＠swri.edu -
waltje＠pdp11.nl