Invalid HWRPB Errors

[Volker Halle]

Amaresh,

it may be a question of the SCSI adapter configuration. There have been AlphaServers 800 around, which did work with V6.2-1H3.

If you have an integrated UltraSCSI controller, then you may need V7.1-1H1 or ALPSCSI patches for V6.2-1H3.

Volker.

[Swain]

$$$ MOUNT/OVER=ID/NOWRITE DKC0:
$$$ sh dev dkc0
Device Device Error Volume Free Trans Mnt

Name Status Count Label Blocks Count Cnt

DKC0: Mounted alloc 0 ALPHAVMS015 6965775 1 1

$$$ ANAL/DISK DKC0:

Analyze/Disk_Structure for _DKC0: started on 29-JAN-2010 12:07:41.50

%ANALDISK-I-OPENQUOTA, error opening QUOTA.SYS
-SYSTEM-W-NOSUCHFILE, no such file
%ANALDISK-W-BADHEADER, file (6,7,1)
invalid file header
-ANALDISK-I-FIDNUM_ZERO, file number zero but not a valid deleted header
-ANALDISK-I-INVHEADER_BUSY, invalid file header marked "busy"
in index file bitmap
%ANALDISK-W-BADDIRENT, invalid file identification in directory entry
[SYS0.SYSCOMMON.SYSMGR]AMARESHS.DIR;1
-ANALDISK-I-BAD_DIRHEADER, no valid file header for directory
%ANALDISK-W-BADDIRENT, invalid file identification in directory entry
[SYS0.SYSCOMMON.SYSMGR]AMS$RESULT.CFG;1
.
.
.
.
$$$ DIR DKC0:[*...]SYSBOOT.EXE/FULL

Directory DKC0:[SYS0.SYSCOMMON.SYSEXE]

SYSBOOT.EXE;1 File ID: (14671,131,0)
Size: 647/648 Owner: [1,4]
Created: 26-APR-1996 12:45:10.64
Revised: 14-MAY-1996 14:16:58.56 (15)
Expires:
Backup:
Effective:
Recording:
File organization: Sequential
Shelved state: Online
File attributes: Allocation: 648, Extend: 0, Global buffer count: 0
No version limit, Contiguous best try, MoveFile disabled
Record format: Fixed length 512 byte records
Record attributes: None
RMS attributes: None
Journaling enabled: None
File protection: System:RWED, Owner:RWED, Group:RE, World:RE
Access Cntrl List: None

Total of 1 file, 647/648 blocks.

Directory DKC0:[VMS$COMMON.SYSEXE]

SYSBOOT.EXE;1 File ID: (14671,131,0)
Size: 647/648 Owner: [1,4]
Created: 26-APR-1996 12:45:10.64
Revised: 14-MAY-1996 14:16:58.56 (15)
Expires:
Backup:
Effective:
Recording:
File organization: Sequential
Shelved state: Online
File attributes: Allocation: 648, Extend: 0, Global buffer count: 0
No version limit, Contiguous best try, MoveFile disabled
Record format: Fixed length 512 byte records
Record attributes: None
RMS attributes: None
Journaling enabled: None
File protection: System:RWED, Owner:RWED, Group:RE, World:RE
Access Cntrl List: None

Total of 1 file, 647/648 blocks.

Grand total of 2 directories, 2 files, 1294/1296 blocks.
$$$

[Volker Halle]

Amaresh,

try a diagnostic boot and capture the output:

>>> b -fl 0,30000 DKC0

This should give very detailled information about the disk IOs of APB (Alpha Primary Bootstrap) trying to load SYSBOOT.EXE...

Volker.

[Volker Halle]

Amaresh,

please find attached the full diagnostic boot output from an OpenVMS V6.2-1H3 successful load of SYSBOOT.EXE

Use it for reference to compare it with your failing boot.

Volker.

[Volker Halle]

Amaresh,

please also note:

%ANALDISK-W-BADHEADER, file (6,7,1)
invalid file header

This is a very disturbing message ! FID (6,6,0) should be the File ID of VOLSET.SYS and it should NEVER change. Could this disk have been mounted into some volume set by operator error ?

Volker.

[Volker Halle]

Amaresh,

I've analyzed the sequence of Boot QIOs when loading SYSBOOT.EXE. This will allow you to immediately diagnose, which boot QIO fails and which file or file hdr is corrupted:

%APB-I-BOOTVOL, Mounting boot volume
Boot QIO: LEN=0200 LBN=00000001 ! Home block
Boot QIO: LEN=0200 LBN=00049430 ! INDEXF.SYS File Hdr
Boot QIO: LEN=0200 LBN=00049433 ! 000000.DIR File Hdr
Boot QIO: LEN=2800 LBN=00000006 ! 000000.DIR contents
%APB-I-SYSROOT, System root is [SYS0.]
Boot QIO: LEN=0200 LBN=0004943A ! [000000]SYS0.DIR File Hdr
Boot QIO: LEN=0200 LBN=0004943A ! [000000]SYS0.DIR File Hdr
Boot QIO: LEN=0200 LBN=00064B30 ! [000000]SYS0.DIR contents
Boot QIO: LEN=0200 LBN=00049C81 ! [SYS0]SYSEXE.DIR File Hdr
Boot QIO: LEN=0200 LBN=00029610 ! [SYS0]SYSEXE.DIR contents
Boot QIO: LEN=0200 LBN=0004943B ! [SYS0]SYSCOMMON.DIR File Hdr
Boot QIO: LEN=0400 LBN=00064B42 ! [SYS0]SYSCOMMON.DIR contents
Boot QIO: LEN=0200 LBN=000495BE ! [SYS0.SYSCOMMON]SYSEXE.DIR File Hdr
Boot QIO: LEN=01E00 LBN=0006CEC4 ! [SYS0.SYSCOMMON]SYSEXE.DIR Contents
Boot QIO: LEN=0200 LBN=00049671 ! [SYS0.SYSCOMMON.SYSEXE]SYSBOOT.EXE File Hdr
%APB-I-LOADFILE, Loading [SYS0.SYSCOMMON.SYSEXE]SYSBOOT.EXE;1
Boot QIO: LEN=0200 LBN=000790A4 ! [SYS0.SYSCOMMON.SYSEXE]SYSBOOT.EXE Image Hdr
Boot QIO: LEN=50A00 LBN=000790A6 ! [SYS0.SYSCOMMON.SYSEXE]SYSBOOT.EXE contents
%APB-I-SECBOOT, Transferring to secondary bootstrap

Volker.

[Swain]

Hi,

what is the feasibility of building a DR on Charon-AXp?

Thanks,
Amaresh

[Volker Halle]

Amaresh,

using a CHARON-AXP for the DR site may work well. The CPU performance will even be better than with the older Alphas (e.g. AlphaServer 800 5/400). V6.2-1H3 is supported. You just need to check, if there are any 'unusual' interface cards in the existing Alpha - this would be unusual, but should be checked.

Volker.

Disclaimer: Invenate is a CHARON reseller.

[Steve Reece_3]

If this is a DR system, preumably the live system (the 1000A 5/400) has the UltraSCSI patch installed on it? If this is the case, why not restore the system disk off the live box onto the DR, then rename the system to have the identity and update the licenses so that they reflect the DR system?

For the restore, it won't matter what version of VMS you run the restore with as long as the system is supported by it.

Steps for renaming the system will be found in the VMS FAQ which I'm sure is on Hoff's website. Disabling the live system's licenses is a case of running the LICENSE utility, same for reloading the DR system's own licenses.

If this doesn't work then the AlphaServer 800 really doesn't fulfil the needs of a DR system...

Steve

[Swain]

Volker,

Charon option looks convincing.

Steve,

>>UltraSCSI patch installed on it?

How can I get details of patch?

Thanks,
Amaresh