Can't boot Tru64 V5.0

[stuartl]

Looking for some help.

I have 'inherited' the support of an AS800 system. It's been working fine for a number of years but now won't boot.  My Unix knowledge is very limited so I'm struggling on where to even start with this.

The story goes that there was an attempt to delete some files from the \usr\var\join directory and this led to the boot issue. Whether files were deleted from the wrong directory or not I don't know. Someone else has had a look at fixing this but I don't think they made any progress.

Below is a log showing the contents of 'show conf', 'show', 'boot', 'boot -file genvmunix' and 'boot -flag s -file genvmunix'.

I therefor ethink the problem is a corrupt disk, I don't believe the disk is faulty so any pointers at all that someone can give would be greatly appeciated.

Thank you.

>>>show conf
Digital Equipment Corporation
AlphaServer 800 5/500

Firmware
SRM Console: V5.2-113
ARC Console: v5.64
PALcode: VMS PALcode V1.20-3, OSF PALcode V1.22-5
Serial Rom: V1.2

Processor
DECchip (tm) 21164A-2 500MHz

System
Motherboard Revision: 54-24803-02 Rev A

Memory
640 Meg of System Memory
Bank 0 = 128 Mbytes(32 MB Per DIMM) Starting at 0x20000000
Bank 1 = 512 Mbytes(128 MB Per DIMM) Starting at 0x00000000

Slot Option Hose 0, Bus 0, PCI
5 QLogic ISP1020 pka0.7.0.5.0 SCSI Bus ID 7
dka0.0.0.5.0 COMPAQ BD036635C5
dka100.1.0.5.0 COMPAQ BD036635C5
dka200.2.0.5.0 RZ1CB-CS
dka300.3.0.5.0 RZ1CB-CS
dka400.4.0.5.0 RRD46
6 S3 Trio64/Trio32
7 Intel 82375 Bridge to Bus 1, EISA
11 DE500-AA Network Con ewa0.0.0.11.0 00-00-F8-10-CB-1B
12 DEC PCI FDDI fwa0.0.0.12.0 08-00-2B-A2-36-99
13 DEC PCI MC Rev: 22, mca0
14 000112AE/600A1011

Slot Option Hose 0, Bus 1, EISA
>>>
>>>
>>>show
auto_action BOOT
boot_dev dka0.0.0.5.0
boot_file
boot_osflags A
boot_reset OFF
bootdef_dev dka0.0.0.5.0
booted_dev dka0.0.0.5.0
booted_file genvmunix
booted_osflags A
bus_probe_algorithm new
char_set 0
com1_baud 9600
com1_flow SOFTWARE
com1_modem OFF
com2_baud 9600
com2_flow SOFTWARE
com2_modem OFF
console serial
controlp ON
d_bell off
d_cleanup on
d_complete off
d_eop off
d_group field
d_harderr halt
d_loghard on
d_logsoft off
d_omit
d_oper on
d_passes 1
d_quick off
d_report full
d_runtime 0
d_softerr halt
d_startup off
d_status off
d_trace off
d_verbose 0
dump_dev
enable_audit ON
ewa0_arp_tries 3
ewa0_bootp_file
ewa0_bootp_server
ewa0_bootp_tries 3
ewa0_def_ginetaddr 0.0.0.0
ewa0_def_inetaddr 0.0.0.0
ewa0_def_inetfile
ewa0_def_sinetaddr 0.0.0.0
ewa0_def_subnetmask 0.0.0.0
ewa0_ginetaddr 0.0.0.0
ewa0_inet_init bootp
ewa0_inetaddr 0.0.0.0
ewa0_inetfile
ewa0_loop_count 2
ewa0_loop_inc d0
ewa0_loop_patt ffffffff
ewa0_loop_size 100
ewa0_lp_msg_node 8
ewa0_mode Twisted-Pair
ewa0_protocols MOP
ewa0_sinetaddr 0.0.0.0
ewa0_tftp_tries 3
fru_table ON
full_powerup_diags ON
fwa0_arp_tries 3
fwa0_bootp_file
fwa0_bootp_server
fwa0_bootp_tries 3
fwa0_def_ginetaddr 0.0.0.0
fwa0_def_inetaddr 0.0.0.0
fwa0_def_inetfile
fwa0_def_sinetaddr 0.0.0.0
fwa0_def_subnetmask 0.0.0.0
fwa0_ginetaddr 0.0.0.0
fwa0_inet_init bootp
fwa0_inetaddr 0.0.0.0
fwa0_inetfile
fwa0_loop_count 3e8
fwa0_loop_inc a
fwa0_loop_patt ffffffff
fwa0_loop_size 2e
fwa0_lp_msg_node 1
fwa0_protocols MOP
fwa0_sinetaddr 0.0.0.0
fwa0_tftp_tries 3
kbd_hardware_type PCXAL
language 36
language_name English (American)
license MU
os_type UNIX
pal VMS PALcode V1.20-3, OSF PALcode V1.22-5
pci_parity off
pka0_host_id 7
pka0_soft_term on
reset_boot_arg0
reset_boot_arg1
reset_boot_arg2
scsi_poll ON
srm2dev
sys_serial_num AY84555167
tga_sync_green 0
tt_allow_login 1
tty_dev 0
version V5.2-113 May 28 1998 11:00:45
wwid0
wwid1
wwid2
wwid3
wwid4
>>>
*********************************************************
>>>boot
(boot dka0.0.0.5.0 -flags A)
block 0 of dka0.0.0.5.0 is a valid boot block
reading 18 blocks from dka0.0.0.5.0
bootstrap code read in
base = 1c8000, image_start = 0, image_bytes = 2400
initializing HWRPB at 2000
initializing page table at 27ff0000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code

UNIX boot - Tue Jul 20 21:02:13 EDT 1999

can't open vmunix
trying /etc/sysconfigtab.27.5
Loading /etc/sysconfigtab.27.5 ...
Loading at fffffc0000200000
Linking 135 objects: 135 Can't open /sys/BINARY/PINTAKE.mod

halted CPU 0

halt code = 5
HALT instruction executed
PC = 200104f0
boot failure
>>>
****************************************************************
>>>boot -file genvmunix
(boot dka0.0.0.5.0 -file genvmunix -flags A)
block 0 of dka0.0.0.5.0 is a valid boot block
reading 18 blocks from dka0.0.0.5.0
bootstrap code read in
base = 1c8000, image_start = 0, image_bytes = 2400
initializing HWRPB at 2000
initializing page table at 27ff0000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code

UNIX boot - Tue Jul 20 21:02:13 EDT 1999

can't open genvmunix

Enter <kernel_name> [option_1 ... option_n]
Press Return to boot default kernel 'genvmunix':
*****************************************************************
>>>boot -flag s -file genvmunix
(boot dka0.0.0.5.0 -file genvmunix -flags s)
block 0 of dka0.0.0.5.0 is a valid boot block
reading 18 blocks from dka0.0.0.5.0
bootstrap code read in
base = 1c8000, image_start = 0, image_bytes = 2400
initializing HWRPB at 2000
initializing page table at 27ff0000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code

UNIX boot - Tue Jul 20 21:02:13 EDT 1999

can't open genvmunix

Enter <kernel_name> [option_1 ... option_n]
Press Return to boot default kernel 'genvmunix':

[Steven Schweda]

> [...] \usr\var\join directory [...]

   So, you're a Windows guy?  For UNIX: "\" -> "/".

> can't open vmunix

> can't open genvmunix

   Apparently, all the likely kernels have been lost/destroyed.

   You should be able to boot from a Tru64 installation CD-ROM.  I don't
think that I've ever had to deal with anything this badly scrambled, but
my notes say:

      Boot from installation CD-ROM.  "3) Exit Installation"

      Create normal devices: dn_setup -boot

   After that, you should be able to mount the root file system (at
least), and start poking around.  Possibly interesting if you're looking
for file systems:

      ls -l /dev/rdisk

then, to find plain-old UNIX file system data:

      disklabel -p dskX         (X = 0, 1, 2, ...)

   My Tru64 system has a dead power supply, so I can't try much here.
If you're using AdvFS (a logical volume manager), then I'd need to do
some reading to see how to obtain any useful info on the logical volumes
without being able to read "/etc/fstab".  You might find some info in
"/etc/fdmns".  I'd be looking for names like "root_domain_0" and
"usr_domain_0".

   My quick guess is that you'll end up reinstalling Tru64.  How good
are the backups?

[stuartl]

Thanks for the reply, I had a feeling it didn't look promising. How good are the backups? I guess I'm about to find out!