Conference vaxaxp::vmsnotes

222.0. "upgrade hsz40 from 2.7z two 3.0z eco 2 " by MDR01::GREGORIO (MCS Madrid) Wed Feb 19 1997 11:40

	********* CROSSPOSTED in VMSNOTES and HSZ40_PRODUCT *****************

Hello, the customer upgrade hsz40 from 2.7z two 3.0z eco 2 (12-JAN-1997)

    The customer began to detect the problems 32-JAN-1997

In this moment the customer has several messages in a disk (Mirror).

When I ana/disk :
    
$ ana/disk dka202:
Analyze/Disk_Structure for _PROVE1$DKA202: started on 19-FEB-1997 17:07:30.39

%ANALDISK-I-OPENQUOTA, error opening QUOTA.SYS
-SYSTEM-W-NOSUCHFILE, no such file
%ANALDISK-W-ALLOCCLR, blocks incorrectly marked allocated
        LBN 4718673 to 4721084, RVN 1
%ANALDISK-W-BADDIRENT, invalid file identification in directory entry
        [SIRIO_PROVE.DATOS.FACTURACION.ENT]FLT970219-120258-001.001TMP;1
-ANALDISK-I-BAD_DIRHEADER, no valid file header for directory
%ANALDISK-W-BADDIRENT, invalid file identification in directory entry
        [SIRIO_PROVE.DATOS.TARIFICACION.ENT]LT970219-120258-001.001TMP;1
-ANALDISK-I-BAD_DIRHEADER, no valid file header for directory
%ANALDISK-W-BADDIRENT, invalid file identification in directory entry
        [SIRIO_PROVE.DATOS.TARIFICACION.ENT]LT970219-165305-001.005;1
-ANALDISK-I-BAD_DIRHEADER, no valid file header for directory
%ANALDISK-W-BADDIRENT, invalid file identification in directory entry
        [SIRIO_PROVE.DATOS.TARIFICACION.ENT]LT970219-165423-001.003;1
-ANALDISK-I-BAD_DIRFIDSEQ, invalid file sequence number in directory file ID
%ANALDISK-W-BADDIRENT, invalid file identification in directory entry
        [SIRIO_PROVE.DATOS.TARIFICACION.ENT]LT970219-165433-001.009TMP;1
-ANALDISK-I-BAD_DIRHEADER, no valid file header for directory
%ANALDISK-W-BACKLINK, directory (27,1,1) [SIRIO_PROVE.DATOS.TARIFICACION]HIS.DIR
;1
        incorrect back link for entry LT970219-115848-001.006;1
%ANALDISK-W-BACKLINK, directory (16,1,1) [SIRIO_PROVE.DATOS.FACTURACION]HIS.DIR;
1
        incorrect back link for entry FLT970219-112109-001.011;1
%ANALDISK-W-BADHEADER, file (4833,1,1)
        invalid file header
-ANALDISK-I-BAD_FIDSEQ, unexpected FID_SEQ field
%ANALDISK-W-FREESPADRIFT, free block count of 7060896 is incorrect (RVN 1);
        the correct value is 7060842

$ ana/disk dka202:
Analyze/Disk_Structure for _PROVE1$DKA202: started on 19-FEB-1997 17:09:28.31

%ANALDISK-I-OPENQUOTA, error opening QUOTA.SYS
-SYSTEM-W-NOSUCHFILE, no such file
%ANALDISK-W-FUTCREDAT, file (4927,1,1)
        creation date is in the future
%ANALDISK-W-ALLOCCLR, blocks incorrectly marked allocated
        LBN 6119505 to 6120818, RVN 1
%ANALDISK-W-BADDIRENT, invalid file identification in directory entry
        [SIRIO_PROVE.DATOS.TARIFICACION.ENT]LT970219-165658-001.007;1
-ANALDISK-I-BAD_DIRHEADER, no valid file header for directory
%ANALDISK-W-BADDIRENT, invalid file identification in directory entry
        [SIRIO_PROVE.DATOS.TARIFICACION.ENT]LT970219-165802-001.004TMP;1
-ANALDISK-I-BAD_DIRHEADER, no valid file header for directory
%ANALDISK-W-BACKLINK, directory (16,1,1) [SIRIO_PROVE.DATOS.FACTURACION]HIS.DIR;
1
        incorrect back link for entry FLT970219-112122-001.008;1
%ANALDISK-W-FREESPADRIFT, free block count of 7056198 is incorrect (RVN 1);
        the correct value is 7056117

The errors change without he uses "/REPAIR".

I don't understand these changes. Is it normal?


The aplication use the rename of files of this disk continously.
    
OpenVMS V6.2-1H3
    
The list of patch:

ALPHA_UCX033.RELEASE_NOTES;1            ALPMANA01_062.RELEASE_NOTES;1
ALPSALV01_062.RELEASE_NOTES;1           ALPSCSI02_070.RELEASE_NOTES;1
ALPSCSI03_062.RELEASE_NOTES;1           ALPSMUP01_070.RELEASE_NOTES;1


Any persone can help me. Please I need help
Thanks 
Goyo Fdez.
 

    

re .0
    
>    The customer began to detect the problems 32-JAN-1997
                                                ^
    No worries then. (-:
    
>The errors change without he uses "/REPAIR".
>I don't understand these changes. Is it normal?
    
    That's right. If you use /REPAIR then the volume is locked against
    certain changes that could adversely affect the analyse. If you don't
    use /REPAIR then the volume is not locked and errors can be spurious.

    I suggest you do one pass with /REPAIR/CONFIRM but don't confirm
    anything ("Just say 'No'."). If you still get most of the above errors
    then the disk is in a seriously bad state and it would need professional
    help.

    Is any disk defragmenter in use?

    SORRY ;
    The customer began to detect the problems 31-JAN-1997
    
    $ ana/disk dka202:/repai/conf
    Analyze/Disk_Structure/Repair for _PROVE1$DKA202: started on
    20-FEB-1997 08:59:2
    6.34
    
    %ANALDISK-I-OPENQUOTA, error opening QUOTA.SYS
    -SYSTEM-W-NOSUCHFILE, no such file
    %ANALDISK-I-BBLHEADER, file (15,1,1)
    [SIRIO_PROVE.DATOS.FACTURACION]ENT.DIR;1
            contains suspected bad blocks
    
    
    I think that I have a serious problem in this disk.
    The customer have 20 HSZ40 with 3.0z (In several systems) eco 2 but only 
    in this disk he has problems, we have moved the information of this disk to 
    other controler and disk, but the problem continues.
    >>  Is any disk defragmenter in use?
    NO. 
    
    I have mounted the disk with /data_check=(write,read)
    
    What can I do? 
    Please I need help, because I don't know how I must continue.
    Thanks in Advance.
    Goyo Fdez.
    MSCD Spain.
    
    
     

>    I think that I have a serious problem in this disk.

Yes, true.

>    The customer have 20 HSZ40 with 3.0z (In several systems) eco 2 but only 
>    in this disk he has problems, we have moved the information of this disk to 
>    other controler and disk, but the problem continues.

Did the problem continue on this disk or on the disk where you moved the data?
If it was on the original disk you should replace it.

Jur.

    
    Hello,
    
     %ANALDISK-I-OPENQUOTA, error opening QUOTA.SYS
        -SYSTEM-W-NOSUCHFILE, no such file
        %ANALDISK-I-BBLHEADER, file (15,1,1)
        [SIRIO_PROVE.DATOS.FACTURACION]ENT.DIR;1
                contains suspected bad blocks
    This problem is in the new this, and I create a new directorio in this
    disk and I move de files of ent.dir to this new directory.
    I rename the name of directories. And four hours later the problem is
    reproduced.
    $ ana/disk /repair /conf dka202:
    Analyze/Disk_Structure/Repair for _PROVE1$DKA202: started on
    20-FEB-1997 16:06:2
    9.62
    
    %ANALDISK-I-OPENQUOTA, error opening QUOTA.SYS
    -SYSTEM-W-NOSUCHFILE, no such file
    %ANALDISK-I-BBLHEADER, file (15,1,1)
    [SIRIO_PROVE.DATOS.FACTURACION]OLD_ENT.DIR;
    1
            contains suspected bad blocks
    %ANALDISK-I-BBLHEADER, file (2444,2,1)
    [SIRIO_PROVE.DATOS.FACTURACION]ENT.DIR;1
            contains suspected bad blocks
    
    I Think that I must escale this problem, but I don't know if escalate
    to OpenVMS or HSZ40.
    In the errorlog there are not error in this device.
    
    Thanks.
    Goyo Fdez
    

	The disk is bad, and getting worse. Get FS to replace the disk.

Vern

I've seen more weird problems with scsi disk which were clearly in error
but did not log any error in the errorlog. Again, replace the disk.

Jur.

      Hi,
    
        I escalated this problem
        Thanks for your attention
        Goyo Fdez.