April 10, 201610 yr I got an alert that 34 files on a particular disk are corrupt. "Event: unRAID file corruption Subject: Notice [sPE] - bunker command Description: Found 34 files with SHA256 hash key corruption" First time I've seen this...not sure where to go from here?
April 10, 201610 yr Community Expert I got an alert that 34 files on a particular disk are corrupt. "Event: unRAID file corruption Subject: Notice [sPE] - bunker command Description: Found 34 files with SHA256 hash key corruption" First time I've seen this...not sure where to go from here? this is just telling you that the stored hash does not agree with the current contents. You can get spurious warning if the files could have been updated by a program without changing the time stamp, so whether the warning matters depends on the files. If you think the warning is valid then you need to get replacement copies of the files.
April 10, 201610 yr As itimpi noted, you have to assess whether or not this is a real problem. If the files have been updated without a matching update of the hash, then you simply need to update the hash. If the files have NOT been changed (or at least SHOULD NOT have been changed), then they are actually corrupt, and you should replace them from your backups.
April 13, 201610 yr Author I got an alert that 34 files on a particular disk are corrupt. "Event: unRAID file corruption Subject: Notice [sPE] - bunker command Description: Found 34 files with SHA256 hash key corruption" First time I've seen this...not sure where to go from here? this is just telling you that the stored hash does not agree with the current contents. You can get spurious warning if the files could have been updated by a program without changing the time stamp, so whether the warning matters depends on the files. If you think the warning is valid then you need to get replacement copies of the files. As itimpi noted, you have to assess whether or not this is a real problem. If the files have been updated without a matching update of the hash, then you simply need to update the hash. If the files have NOT been changed (or at least SHOULD NOT have been changed), then they are actually corrupt, and you should replace them from your backups. What's the best way to automate this process so I don't keep getting bunker command notices on files that have been changed/updated (intended changes that is)?
Archived
This topic is now archived and is closed to further replies.