RMS-F-IRC, ILLEGAL RECORD ENCOUNTERED; VBN OR RECORD NUMBER = 3; OPENVMS 6.2

[Nuar]

Hi Open VMS expert

We are running open vms version 6.2 with digital alpha server 1000A 4/266

OS rebooting in normal condition, but an error appear at Decterm terminal

"RMS-F-IRC, ILLEGAL RECORD ENCOUNTERED; VBN OR RECORD NUMBER = 3; "

During the 2nd boot up, blue screen with logs appear, but application not load up (grey screen with cursor).

is there any workaround, solution to solve this issue ? 

[Hein van den Heuvel]

Well, some file got physically corrupted, quit possibly due to a disk hardware error or powerfailure.

If you can get to an OpenVMS command prompt check : $ HELP/MESSAGE/FACILTY=RMS IRC

I'll add it below.

It's going to be challenging to find which file, and indeed there may be many bad files if a disk has gone bad.

I urge you to seek the service of a serious OpenVMS system manager/consultant who can properly evaluate what the system is doing or not.

"blue" and "grey" are good words for kindergarten, not troubleshooting.

Involve your management.

Have them explain what the support structure is that is available to you.

Good luck!

Hein

[Hein van den Heuvel]

Forgot the text, and links:

http://h71000.www7.hp.com/wizard/wiz_1181.html

http://odl.sysworks.biz/disk$vaxdocsep953/decw$book/dy4yaa10.p223.decw$book

http://h71000.www7.hp.com/doc/73final/documentation/pdf/ovms_msg_ref_al.pdf

Is this system run with just a graphics head and DECwindows?

Can you connect to it over the network? 

Can you get a "Username:" prompt using a serial console?

Hein

IRC, illegal record encountered; VBN or record number = 'nnn'

Facility: RMS, OpenVMS Record Management Services

Explanation: The byte count field or the control byte for a record in a
file is invalid. For sequential and indexed files, the status
value (STV) field contains the virtual block number of the
block containing the record. For relative files, the status
value (STV) field contains the record number of the corrupt
record. This error can be caused by any of the following:

o Hardware errors

o System failures or crashes

o Restoring a file that was backed up using the
/IGNORE=INTERLOCK qualifier

o Inadvertent modification of data blocks or buckets in a
file using block I/O or I/O operations other than RMS

User Action: For sequential and indexed files, try to reorganize the file
using the DCL command CONVERT. If necessary, re-create the
file or restore it from a recent backup version.

For relative files, reinsert the bad record using the $PUT
service with the UIF option in the ROP parameter.

If the problem recurs for no known reason, collect as much
information as possible and contact HP Customer Support.

[Nuar]

Hi Hein

Thank you very much on your reply.

Is this system run with just a graphics head and DECwindows? 

Yes

Can you connect to it over the network? 

Able to ping IP Address; but no application load up.

Can you get a "Username:" prompt using a serial console?

We dont have the serial console and cables.

Can i ask,

how do i recover from "bootstrap failure"