Please make sure to include JumpStart! version, SRM
version, hardware configuration, and any other relavent
information.
-Jump Start Version 1.4
(downloaded as an ISO and burn with ez
cd creator)
-Alpha Server 1000A 4/266
-512 meg ram
-4.3 gb system disk
from the show command
--------------------------------------------
-os_type unix
-pal VMS PALcode v5.56-7, OSF PALcode
v1.45-12
-version v5.4-107 mar 24 1999 13:58:08
The Problem
------------------------
After entering...
>>> boot dka400 - fl 0
The Machine reboots
(boot dka400.4.0.2000.0 -flags 0)
block 0 of dka400.4.0.2000.0 is a valid
boot block
reading 161 blocks from
dka400.4.0.2000.0
boot strap code read in
FRU table creation disabled
base - 1c2000, image_start = 0,
image_bytes = 14200
initializing HWRPB at 2000
initializing page table at 1ffd0000
initializing machine state
setting affinity to the primary cpu
jumping to bootstrap code
aboot: linux/alpha SRM bootloader
version 0.7
aboot: switching to OSF/1 PALcode
version 1.45
aboot: booting from device 'SCSI 0 2000
0 4 400 0 0'
aboot: no disklabel found.
iso: Max size:119148 Log zone size:2048
iso: First datazone:30 Root inode number
61440
aboot: loading uncompressed
boot/vmlinuz...
aboot: loading compressed
boot/vmlinuz...
aboot: segment 0, 2528840 bytes at
0xfffffc0000310000
aboot: zero-filling 253384 bytes at
0xfffffc0000579648
aboot loading initrd (565653 bytes/552
blocks) at 0xfffffc001fe34000
aboot starting kernel boot/vmlinuz with arguments
root=/dev/ram
-at this time the screen flashes red for
a split second then, returns back to white text on blue
background and returns the following at the bottom...
halted CPU 0
halt code = 6
double error halt
PC = fffffc000031cbcc
Logged In: YES
user_id=294675
Would you please try typing "show dev" at the SRM prompt
(the ">>>"), and tell me what you see? At the moment, I'm a
bit puzzled, but I'm looking into this, and will consult
with an engineer when I can.
Regards,
Mike Lease,
Alpha Technology Solutions Group
Logged In: YES
user_id=294675
>>>show dev
dka0.0.0.2000.0 dka0 RZ29b 0014
dka200.2.0.2000.0 dka200 RZ29B 0014
dka300.3.0.2000.0 dka300 RZ28D 0010
dka400.4.0.2000.0 dka400 RRD45 0436
dka500.5.0.2000.0 dka500 RZ28D 0010
dva0.0.0.1000.0 dva0
mka600.6.0.2000.0 mka600 tlz07 553B
ewa0.0.012.0 ewa0 00-00-f8-01-4d-bc
pka0.7.0.2000.0 pka0 scsi bus ID 7 5.57
I also updated the bios.As follows
>>>show version
version v5.7-83 mar 27 2000 09:42:18
Logged In: YES
user_id=294675
Hi again,
Sorry for the delay, I was out sick for a few days. Anyway,
I have a suspicion about your problem now; we've encountered
problems like this with certain tape drives, which is what I
believe your mka600... device is (there's some kind of boot
conflict that sometimes appears when a tape drive is
installed). There are two things I'd like you to try. First,
please try putting a cartridge into your tape drive during
the boot process (if you haven't already). Sometimes, this
is all it takes to make it work; apparently, if
there's no cartridge in the drive, the failure to sample the
drive causes the boot to fail. Second, if that doesn't help
(or hasn't, if you've tried this already), try unplugging
the tape drive from the controller. That should allow you to
proceed with the installation, at which point, you should be
able to plug the drive back in again.
If neither of those ideas helps, please get back to me; my
email address is mike.lease@compaq.com.
Regards,
Mike Lease,
Alpha Technology Solutions Group
Logged In: YES
user_id=294675
Hello,
I'm assuming, since I haven't heard back, that you're no
longer having problems? If that's not the case, please let
me know; otherwise, we'll close this bug in a few days.
Regards,
Mike Lease,
Alpha Technology Solutions Group