[Info-vax] Weird problem with non-booting AlphaServer 800.

[Jan-Erik Soderholm]

Thanks all so far! :-)

A few comments and answers...

Stephen Hoffman wrote 2013-01-07 18:13:
> On 2013-01-07 16:49:14 +0000, Jan-Erik Soderholm said:
>>
>>  >>>boot dka100 -flags 0,1
>> (boot dka100.1.0.5.0 -flags 0,1)
>> block 0 of dka100.1.0.5.0 is a valid boot block
>> reading 1168 blocks from dka100.1.0.5.0
>> bootstrap code read in
>> base = 1d6000, image_start = 0, image_bytes = 92000
>> initializing HWRPB at 2000
>> initializing page table at 7ffce000
>> initializing machine state
>> setting affinity to the primary CPU
>> jumping to bootstrap code
>>
>> [hanging indefinitley here...]
>
> That's gotten through the primitive boot stuff and has tried to transition
> to what looks to be the OpenVMS Alpha V7.3-2 APB primary bootstrap.

This is a 8.2 system. At least it was before the reboot attempt... :-)

Or, wait, DKA100: is the second systemdisk. If you are sure that this is
a 7.3-2 disk, it might the leftover disk from the 8.2 upgrade that
was never re-mounted in the shadowset... Hmm...

DKA0: is the primary system disk and *that* should be a 8.2 system.
I do not have the output from that boot attempt, though...




>
> Enable the verbose boot-time diagnostics (add 30000 to the boot flags), and
> see what gets posted from APB, if anything.

OK.
Must have someone power cycle the system first. It's 170 Km away.
I'll try that tomorrow and post the output.
And thanks to Dan/abrsvc suggesting the same thing.

>
> Try booting from a different disk, a distro, or booting as a diskless
> satellite.

Tried a second system disk on the same system with the same result.
That is, DKA100: instead of DKA0:.

>
> Guesses...

As good as anything at the moment... :-)

>
> Might be a device name problem (particularly if allocation classes are in
> play), or it could be a failing disk, or failing disk controller, or
> incorrect termination, etc.

Hm, the system worked just fine up to the reboot attempt.
I also had the second system disk mounted just to check the
label before the reboot. No problem there. The same disk
that I tried to boot with the same result.

> I'd probably replace the battery, too, as that's cheap (if that box uses a
> coin cell), and a failing battery can sometimes cause weird errors.

Good thought.

>
> Some troubleshooting <http://labs.hoffmanlabs.com/node/192> details.
>
> Or alternatively, retire this box and roll in a less-fossil Alpha; an EV6
> or later.

Yes, it will be replaced by a DS20e. It has been delayed due to some
problem with FC and Ethernet network istallations in a new location.
But that is another "issue"...

Anyway, prio 1 right now is to get a replacement system on-site.

Jan-Erik.


>
>