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

[Stephen Hoffman]

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.

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

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

Guesses...

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.

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.

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.


-- 
Pure Personal Opinion | HoffmanLabs LLC