ERROR MESSAGE WHEN INSTALLING VMS831H1I_UPDATE V7.0

[Ana M. García Olivencia]

Hi all.

I have installed the VMS831H1I_UPDATE V7.0 patch and got the following warning:

%EFICP-W-BADCCNT, FS0:\EFI\VMS\TOOLS\ACPIDUMP.EFI actual cluster count of 126 do
es not match the file allocation of 127.

(The current log is at the end of this message)

The system is HP BL870c (1.59GHz/9.0MB) and the system disk is a SAN disk.

It seems that the patch is correctly installed and the system boots without any problem, but I don't know if this warning can have secondary effects in other situations.

Any help will be very appreciated.

Thanks in advance.

Ana

*************
This is part of the log:
....
The following product will be installed to destination:
HP I64VMS VMS831H1I_UPDATE V7.0 DISK$SISTEMA:[VMS$COMMON.]

Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%
%MOUNT-I-F
ATCHECK, volume created by EFI$CP version V5.2-8
checking for errors, repairing, and updating FAT information
.
%EFICP-W-BADCCNT, FS0:\EFI\VMS\TOOLS\ACPIDUMP.EFI actual cluster count of 126 do
es not match the file allocation of 127.
Filesize of 258232 bytes, requires 508 blocks (rounded
to the cluster factor of 4)
508 blocks shown allocated, but 126 actual clusters (5
04 blocks) counted in file
The disk storage (258048 bytes) is smaller than the fi
le size (258232 bytes)
Truncating file! ***CHECK CONTENTS FOR VALIDITY***
%EFICP-I-FATCHECK, 1 errors found, 1 fixed. 18 files in 4 folders checked, 1209
5166 total bytes in 5913 clusters
%EFICP-I-FATCHECK, Updating the FAT EFI$CP version information to V6.0-2, FAT ve
rsion 1
%EFI-I-COPIED, copied FS0:\EFI\VMS\IPB.EXE to PCSI$DESTINATION:[SYSEXE]FLAG_IPB.
EXE
%EFI-I-COPIED, copied PCSI$DESTINATION:[SYSEXE]IPB.EXE to FS0:\EFI\VMS\
%EFI-I-COPIED, copied PCSI$DESTINATION:[SYSEXE]VMS_SHOW.EFI to FS0:\EFI\VMS\
%EFI-I-COPIED, copied PCSI$DESTINATION:[SYSEXE]VMS_SET.EFI to FS0:\EFI\VMS\
%EFI-I-COPIED, copied PCSI$DESTINATION:[SYSEXE]VMS_BCFG.EFI to FS0:\EFI\VMS\
%EFI-I-COPIED, copied PCSI$DESTINATION:[SYSEXE]VMS_LOADER.EFI to FS0:\EFI\VMS\
%EFI-I-COPIED, copied FS0:\EFI\VMS\IPB.EXE to PCSI$DESTINATION:[SYSEXE]CHECK_IPB
.EXE
%EFI-I-COPIED, copied FS0:\EFI\VMS\VMS_BCFG.EFI to PCSI$DESTINATION:[SYSEXE]CHEC
K_VMS_BCFG.EFI
%EFI-I-COPIED, copied FS0:\EFI\VMS\VMS_LOADER.EFI to PCSI$DESTINATION:[SYSEXE]CH
ECK_VMS_LOADER.EFI
%EFI-I-COPIED, copied FS0:\EFI\VMS\VMS_SET.EFI to PCSI$DESTINATION:[SYSEXE]CHECK
_VMS_SET.EFI
%EFI-I-COPIED, copied FS0:\EFI\VMS\VMS_SHOW.EFI to PCSI$DESTINATION:[SYSEXE]CHEC
...100%HOW.EFI

The following product has been installed (and a recovery data set created):
HP I64VMS VMS831H1I_UPDATE V7.0 Patch (maintenance update)

HP I64VMS VMS831H1I_UPDATE V7.0: OpenVMS V8.3-1H1 UPDATE V7.0

VMS831H1I_UPDATE-V0700 Release notes available

Release notes for the VMS831H1I_UPDATE-V0700 kit are available
at SYS$COMMON:[000000.SYSHLP]

[Shriniketan Bhagwat]

Ana,

Please refer the below link which contains the explanation/solution for this problem.
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=110&prodSeriesId=416064&prodTypeId=18964&objectID=c01564964

Regards,
Ketan

[Ian Miller.]

Also note
"%EFICP-I-FATCHECK, 1 errors found, 1 fixed. 18 files in 4 folders checked, 1209
5166 total bytes in 5913 clusters"

[Ian Miller. · Accepted solution]

There are various articles about this. One of them says
"This is a known issue. The OpenVMS 8.3-1h1 kits contain an error regarding the EFI. The Patch Kit sees this and corrects the error:

( %EFICP-I-FATCHECK, 1 errors found, 1 fixed )

So, this is expected behavior. "

I agree it does cause one to wonder - I was doing exactly the same patch kit install on a BL870 last week and saw this.
Perhaps VMS831H1I_UPDATE V8.0 (when it finally appears) will fix this.

[Ana M. García Olivencia]

Shriniketan.

I had seen that article previously but I considered it was solved. Moreover, I had another Itanium (BL860C) where I installed the update V5.0 the first time, without IPB patch, and it worked ok. After that, I installed UPDATE v6.0 and v7.0, and I didn't received those messages. So, I thought the problem had something to do with hardware.

Ian.

Thanks for confirming that the patch sees the error and fixes it. What worried me was the "Truncating file! ***CHECK CONTENTS FOR VALIDITY***" message.

I think I can derive from your comments that it's not necessary to reinstall anything and I can work safely with the system in this state.

Thank you very much to both for your help.

Regards.

Ana