Our AlphaServer 400 4/233 crashed last night with a hardware error, unclear
what kind - msgs were:
panic (cpu 0): Machine check - hardware error
trap: invalid memory read access from kernel mod
DUMP: problem with primary swapdev 0xe6f4500
DUMP: no primary swap, no explicit dumpdev
nowhere to put header, giving up
I tried booting the cdrom this a.m. to take a look at things (boot dka400)
and got:
panic (cpu 0): Machine check - hardware error
DUMP: no primary swap, no explicit dumpdev
nowhere to put header, giving up
Urgent questions:
1. What commands can I use at the boot prompt to examine the
scsi disks?
2. If it were the case the boot disk was bad, wouldn't I be able
to boot the cdrom anyway?
3. I added a new swap device yesterday - partition g on a (lone)
disk on a second scsi controller. I added it with swapon, and
added it to /etc/fstab as swap2, just like the swap1 (initial
swap device) that was in there from the install. Could this
be causing this kind of problem?
4. Does DU allocate partition b on every disk by some weird default,
even though you only told it to have a primary swap, on the internal disk?
I'm wondering if having manipulated partition b on the external
disk (via disklabel) could have caused problems.
TIA for (hopefully prompt, as we are dead in the water...) responses!!!!
--
Judith Reed
jreed_at_appliedtheory.com
(315) 453-2912 x335
Received on Thu Jul 17 1997 - 14:38:41 NZST