[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference ssdevo::hsz40_product

Title:HSZ40 Product Conference
Moderator:SSDEVO::EDMONDS
Created:Mon Apr 11 1994
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:902
Total number of notes:3319

814.0. "lost delayed write error ofrom Nt 3.51" by KAOT01::B_CORBIN (dtn 640-7420 ) Tue Mar 18 1997 16:28

    Looking for info on an error message in the NT 3.51 event log that
    occured during the mid point of a raid 5 rebuild operation on an hsz40
    A brief description of the errors in the event log was " lost delayed
    write data."  and goes on the list the file. The array has 6 Rz29b's.
    I'm not sure how they are spread over the channels  
    
    A tech was onsite and replaced a failed member of the raid 5 array.
    The storageset policy was nopolicy.
    so the engineer 
    		1. deleted the failedset.
    		2. set raidset replaced=disk
    
    about mid- way through the reconstruct NT logged the error.
    Their were no error at the cli level
    show unit did not show any " lost data" at the cli level.
    
    Is their a way to do a "parity check on the Raid5 array similar to the 
    SWXCR array ?  Is this error logged by NT serious? Any comments welcome
    Brian
T.RTitleUserPersonal
Name
DateLines
814.1SSDEVO::T_GONZALESWed Mar 19 1997 15:565
    Since the reconstruct is transparent to the host system, i don't think
    that this error would be seen if it was due to a failure of the
    reconstruct, was i/o going to the raid set from the nt system?
    
    also was the event logged aginst the hszdisk?