Problem
When using the SCOadmin Software Manager or custom to verify either system or software it fails. The following error message is displayed to the screen (the exact syntax may be different):
Error verifying file attributes Error verifying component "SCO:Unix 5.0.5Eb" Error processing files in "SCO:Unix:RTS 5.0.5Eb" Error parsing file list ".//opt/K/SCO/Unix/5.0.5Eb/.softmgmt/<filename>" at line 540 Error parsing file checksum field
SCOadmin Software Manager will then fail to verify any further software.
Cause
The /opt/K/SCO/Unix/5.0.5Eb/.softmgmt/<filename> file is corrupt. This file holds information about the characteristics of files on your system, such as checksum values, sizes, permissions, ownership, group membership and the file name.
The above message indicates that one of these fields is missing or corrupt and that the checksum value is either corrupt or missing.
Solution
The recommended solution is to restore this file from a known
valid backup. Insert the appropriate tape into your tape drive,
preferably the newest backup available, and enter this command
(the file name may be different, this is the file where the
error originated from):For a tar backup:# tar xv8 /opt/K/SCO/Unix/5.0.5Eb/.softmgmt/<filename>For a cpio backup:# cpio -vicdumB -I /dev/rct0 /opt/K/SCO/Unix/5.0.5Eb/.softmgmt/<filename>Now run SCOadmin Software Manager, or custom, and attempt to
verify the software again. It is possible that more than one
file is corrupt and the restore will have to be done of the other
file(s) that SCOadmin Software Manager can't read properly.NOTES: Another method of correcting this problem involves manually
editing /opt/K/SCO/Unix/5.0.5Eb/.softmgmt/<filename>. This
is not recommended, but may be necessary. As always, when
manually editing files like this, create a backup first.In the above example, the line that is incorrect may look similar to this:
FILE 0555 bin bin 1 1011703058 I - - 0 0 ./usr/lib/libc.so.1
There is a field missing from this file, specifically the field
for size. The SCOadmin Software Manager complains about the
checksum value because it is trying to process the "I" for the
checksum. "I" is not a valid checksum, so the above error
message is displayed.The method to fix this is to get the size value for this file (/usr/lib/libc.so.1) and insert it in the appropriate field. The following two commands will tell you which value is missing:
# sum -rl /usr/lib/libc.so.1
1011703058 727 /usr/lib/libc.so.1
# cksum /usr/lib/libc.so.1
2460100647 372116 /usr/lib/libc.so.1In this case, 1011703058 is the value that is present and the
size, 372116, is missing. Edit the
/opt/K/SCO/Unix/5.0.5Eb/.softmgmt/<filename> file to add the size
value in the appropriate field. The line will now look like this:FILE 0555 bin bin 1 372116 1011703058 I - - 0 0 ./usr/lib/libc.so.1
Save this file and run:SCOadmin Software Manager -> software -> Verify System -> Thorough
The error should no longer occur. See also
ta105411, "Filesystem Repair Utilities for SCO OpenServer 5.0.0, 5.0.2, and 5.0.4."
ta105410, "Filesystem Repair Utilities for SCO UNIX Release 3.2 Version 4.2."
ta107202, "How to recover from a system crash under SCO UNIX System V/386."
ta104411, "How to recover root filesystem after crash if backups, boot/root exist. 4.2."
ta105315, "UnixWare 2.0.*, How to recover from a system crash if the root filesystem is unmountable."
ta104781, "fsck(ADM) is reporting read errors on block 0 of my root device."
ta104767, "Recover OpenServer 5 root filesystem after crash if backups, boot/root exist."
ta103182, "How to contact a data recovery service provider."
ta105316 "UnixWare 2.1.x, How to clean root filesystem after crash if system won't boot and emergency boot or backups don't work."