Just received this message from Unraid, no idea what it means and where it comes from:

Event: unRAID file corruption
Subject: Notice [F] - bunker verify command
Description: Found 18 files with SHA256 hash key corruption
Importance: alert

SHA256 hash key mismatch, /mnt/disk1/Spiele/Star Trek - Resurgence/MD5/QuickSFV.EXE is corrupted
SHA256 hash key mismatch, /mnt/disk1/Spiele/Star Trek - Resurgence/MD5/QuickSFV.ini is corrupted
SHA256 hash key mismatch, /mnt/disk1/Spiele/Star Trek - Resurgence/MD5/fitgirl-bins.md5 is corrupted
SHA256 hash key mismatch, /mnt/disk1/Spiele/Star Trek - Resurgence/Verify BIN files before installation.bat is corrupted
SHA256 hash key mismatch, /mnt/disk1/Spiele/Star Trek - Resurgence/fg-01.bin is corrupted
SHA256 hash key mismatch, /mnt/disk1/Spiele/Star Trek - Resurgence/fg-02.bin is corrupted
SHA256 hash key mismatch, /mnt/disk1/Spiele/Star Trek - Resurgence/fg-03.bin is corrupted
SHA256 hash key mismatch, /mnt/disk1/Spiele/Star Trek - Resurgence/fg-04.bin is corrupted
SHA256 hash key mismatch, /mnt/disk1/Spiele/Star Trek - Resurgence/setup.exe is corrupted
SHA256 hash key mismatch, /mnt/disk1/Spiele/Star Trek Prodigy - Supernova/MD5/QuickSFV.EXE is corrupted
SHA256 hash key mismatch, /mnt/disk1/Spiele/Star Trek Prodigy - Supernova/MD5/QuickSFV.ini is corrupted
SHA256 hash key mismatch, /mnt/disk1/Spiele/Star Trek Prodigy - Supernova/MD5/fitgirl-bins.md5 is corrupted
SHA256 hash key mismatch, /mnt/disk1/Spiele/Star Trek Prodigy - Supernova/Verify BIN files before installation.bat is corrupted
SHA256 hash key mismatch, /mnt/disk1/Spiele/Star Trek Prodigy - Supernova/fg-01.bin is corrupted
SHA256 hash key mismatch, /mnt/disk1/Spiele/Star Trek Prodigy - Supernova/fg-02.bin is corrupted
SHA256 hash key mismatch, /mnt/disk1/Spiele/Star Trek Prodigy - Supernova/fg-03.bin is corrupted
SHA256 hash key mismatch, /mnt/disk1/Spiele/Star Trek Prodigy - Supernova/fg-selective-german.bin is corrupted
SHA256 hash key mismatch, /mnt/disk1/Spiele/Star Trek Prodigy - Supernova/setup.exe is corrupted

What I did yesterday was to move the 2 folders of the games into a new folder, the files are there and also readable and fine. Now this "bunker" (which is not available as a command on the shell ?!?!?) complains about the old paths?

I think I will ignore this message, but still am curious where and why it is coming from?

That's the file integrity plugin

BLAKE3 hash key mismatch (updated), /mnt/disk5/Magnon-Box/NAS Windows Einstellung/Neues Textdokument.txt was modified

Edited August 11, 2025Aug 11 by Mainfrezzer

28 minutes ago, Mainfrezzer said:

That's the file integrity plugin

I've guessed it already. But why "corrupted"? those files do not exist anymore at that location. They have been moved elsewhere.

DMCA? Yes hello,

I am calling to report this MAM59 he committed the evil crime of possessing a fitgirl ISO 😝

On 8/11/2025 at 8:27 AM, MAM59 said:

They have been moved elsewhere.

The plugin can't know, all it knows is there was a file there with a certain hash when it last scanned and that doesn't match anymore. You'd ned to have it rescan to pick up the changes.

22 minutes ago, Kilrah said:

The plugin can't know, all it knows is there was a file there with a certain hash when it last scanned and that doesn't match anymore. You'd ned to have it rescan to pick up the changes.

Yes and no.

There WAS a file, not there is NO FILE anymore

So the plugin can safely assume, that the file is gone which is different from having been tampered with (internally).

So the "corruption" warning is more than misleading.

31 minutes ago, MonadProxy said:

I am calling to report this MAM59 he committed the evil crime of possessing a fitgirl ISO 😝

Too late, the file is gone, that was the reason of my "complain" here.

And, I have never seen fitgirl producing an publishing an ISO...

The wording could be better and there could be a "missing file" warning instead of "corrupted" when that's what's happening, but in the context of what this plugin is for it doesn't really matter. Whole point of it is "that stuff should never change", it sent an alert when it did so it did its job.

Just now, Kilrah said:

stuff should never change", it sent an alert when it did so it did its job.

yeah ok, can live with this.

But I often "move" files/folders around and this was the first and only (so far) warning...

Still a bit puzzled.

5 hours ago, MAM59 said:

yeah ok, can live with this.

But I often "move" files/folders around and this was the first and only (so far) warning...

Still a bit puzzled.

The file integrity plugin is supposed to watch the file file system for changes using inotify and automatically hash and rehash files when they are changed or moved (assuming that functionality is turned on). Unfortunately for large filesystems this uses a lot of inotify resources. You might check to make sure that your inotify watch limit hasnt been exceeded.

11 minutes ago, primeval_god said:

You might check to make sure that your inotify watch limit hasnt been exceeded.

Ok, but you are aware that the stupid question instantly follows: how do I check this???

:-)