Orange circle means something were update but haven't export or build.

On 12/8/2019 at 1:26 AM, dbinott said:

I thought I remember seeing a legend somewhere

Turn on Help in the GUI and you'll get a lot of extra information.

Hello everyone a few weeks back I installed this Dynamix File Integrity plugin and have been really enjoying it on my Unraid Build V6.7.2 but a few days ago i thought i would upgrade to V6.8.0 that is when i noticed that when i try to set the time for it to start the scan and it does not turn on and scan at that time that i set it to when using the "File Integrity Settings" page it does not seem to work not sure why, i thought i must be doing something wrong so i tried many times but it doesn't seem to work for some reason so i though maybe it was the unraid build V6.8.0 so i down graded it back to V6.7.2 and it all works just fine again so then i upgraded it again to V6.8.0 and it does not work again, anyways i'm sure someone has reported this already but in case not i thought i would write this and let everyone know.  p.s i have a question when running this Dynamix file integrity plugin when it gets done say that it finds corrupt files how would i be able to know witch files went bad so i can fix them thank you?  "I want to say thanks to everyone that has made Unraid and all the wonderful plugins for it! Hope everyone has a Merry Christmas! 🎄🎁 JP   

If you read a few of the recent posts it would seem to indicate that your files are likely just fine and the plugin might not be workng properly.

Ok Thank you for your reply is there a way i could read more about this i'm kinda new to this forms stuff and not very good at it  is there some program that i can use to double check my files to make sure they don't have file corruptions like when it would finish it had a SHA2 hash file and i would download it and then make it a .txt extention so i could read it but its just a bunch of files with hash's i need a way to know witch file to check to find what one to fix if it is corrupt i hope this makes sense Thanks for the help    

Frankly, I would be more inclined to believe you have exactly zero corrupt files, and are simply one of a few of us that are reporting that the plugin doesn't seem to behave properly for.  Files don't usually go corrupt on people when simply sitting on a hard drive.  The hard drive's electronics work with algorithms designed to detect whether or not a read was successful.  They can detect when a read was faulty and the data was corrupt.  If you are not seeing the drive reporting that there have been read errors, I would not worry about whether or not your data is corrupt.  It likely isn't if no read errors are being reported.  For whatever reason, the plugin doesn't seem to be behaving properly for everyone that has tried it.  Some of us, perhaps a very small minority, have seen reports of corruption from the plugin, but we also have other hashes from other hashing tools on hand that say the files haven't actually changed.  The plugin is saying they have changed, but since the other hashing tools are still reporting the original hashes for those files, it stands to reason that the files have not changed and that something is behaving incorrectly with the plugin.  If the other hash tools were giving different results then we might suspect actual file corruption.  But with other hash tools still agreeing with previously established hashes, that narrows it down to the plugin being the only one misbehaving.

 

If you're not getting read errors reported from the hard drive, I wouldn't worry about it, and I'd simply uninstall the plugin.  It would be nice to have an automated hashing system in place, but if it doesn't seem to be working properly it isn't of much use.

Ok Thank you for your fast and detailed reply i really appreciate it!  Have a awesome week and a Merry Christmas!🎄🎁😎 

On 12/24/2019 at 7:29 PM, JP s said:

Hello everyone a few weeks back I installed this Dynamix File Integrity plugin and have been really enjoying it on my Unraid Build V6.7.2 but a few days ago i thought i would upgrade to V6.8.0 that is when i noticed that when i try to set the time for it to start the scan and it does not turn on and scan at that time that i set it to when using the "File Integrity Settings" page it does not seem to work not sure why, i thought i must be doing something wrong so i tried many times but it doesn't seem to work for some reason so i though maybe it was the unraid build V6.8.0 so i down graded it back to V6.7.2 and it all works just fine again so then i upgraded it again to V6.8.0 and it does not work again, anyways i'm sure someone has reported this already but in case not i thought i would write this and let everyone know.  p.s i have a question when running this Dynamix file integrity plugin when it gets done say that it finds corrupt files how would i be able to know witch files went bad so i can fix them thank you?  "I want to say thanks to everyone that has made Unraid and all the wonderful plugins for it! Hope everyone has a Merry Christmas! 🎄🎁 JP   

 

Unless it has been fixed recently (I'm away at the moment and can't check) this is still a problem: 

 

So while it was a conscious decision to exclude cache, but me and many others like to store some data longer term on cache.  Is it possible to have an option to check cache disks for integrity?

 

It happens to be my only disk without Btrfs, so no scrub is available either

Seems unnecessary to me.  I'm sure your drive is taking care of that for you just fine.  Not like this tool can be trusted anyway.

On 10/27/2019 at 12:19 PM, bonienl said:

You are right.

Need to correct that. Thanks

Polite little bump - I'm sure you just forgot about this.

# Generated file integrity check schedule:
10 0 * * * /boot/config/plugins/dynamix.file.integrity/integrity-check.sh &> /dev/null

 

11 minutes ago, pluginCop said:

Polite little bump - I'm sure you just forgot about this.

Sure, you are sure ... made a note in my todo list!

Hi,  what does bunker: failed to export  with the corresponding xx files skipped messages signify?

I've built/rebuilt/lexported and reexported and still get the same files flagged in the syslog ...

9 hours ago, superloopy1 said:

Hi,  what does bunker: failed to export  with the corresponding xx files skipped messages signify?

I've built/rebuilt/lexported and reexported and still get the same files flagged in the syslog ...

It means these files do not have their hash key set. You need to do a "build" action to add missing keys.

Thanks but I mentioned that i had already done that a number of times, including re-exporting following each build to check against. Seems the hashing won't stick with the files? I'm guessing i just relocate the offending files and see if they present problems on a different disk?

Sent from my CLT-L09 using Tapatalk
 

Edited January 18, 20206 yr by superloopy1

On 1/6/2020 at 3:08 AM, John_M said:

 

Unless it has been fixed recently (I'm away at the moment and can't check) this is still a problem: 

 

yeah it still is not working i have upgraded to Unraid V6.8.1 and the Dynamix file integrity plugin wont run on the weekly schedule but everything eles on it works fine just not that one part not sure why ?   JP 

7 hours ago, JP s said:

not sure why ?

As I said, on the previous page,

Quote

Likely a consequence of the permissions change on the boot flash device [that was introduced with Unraid 6.8] that now prevents scripts from being executed directly from the flash?

which was confirmed by the author of the plugin.

Thanks but I mentioned that i had already done that a number of times, including re-exporting following each build to check against. Seems the hashing won't stick with the files? I'm guessing i just relocate the offending files and see if they present problems on a different disk?

Sent from my CLT-L09 using Tapatalk
 

I did move the offending files to another disk and, sure enough, the problem persists. So just what's wrong?

Sent from my CLT-L09 using Tapatalk

2 hours ago, John_M said:

As I said, on the previous page,

which was confirmed by the author of the plugin.

Ok Thank you John! for the update i really appreciate it! Hopefully it will be fixed in a future update that would be awesome 😎JP 

1 hour ago, JP s said:

Hopefully it will be fixed in a future update

It will because the plugin is broken at the moment. It's a trivial thing to fix but bonienl is a busy guy.

2 hours ago, superloopy1 said:

I did move the offending files to another disk and, sure enough, the problem persists. So just what's wrong?

What are the "offending files"? Are they mostly static or are they temporary or updated regularly? The plugin works well for files than seldom change. Temporary files and those that change over time are best excluded.

Sorry, but randomly giving incorrect hash errors on files that haven't changed is not something that I would call working well.

On 1/19/2020 at 1:26 PM, _Shorty said:

Sorry, but randomly giving incorrect hash errors on files that haven't changed is not something that I would call working well.

That's not very constructive. It works well for me, apart from the problem with the cron job not running, mentioned above. If you've experienced problems perhaps there's an underlying issue with your server that needs to be fixed.

As has been said by more than one user, when this plugin says there are hash errors but external tools say the hashes/files have not changed, you cannot blame anything but this plugin.  My server is 100% fine.  If it were not, there would be other issues rearing their heads.  This plugin incorrectly stating files have changed is a problem with this plugin.  Again, I am not the only person that has reported this issue.  And it's not like I'm here fuming mad about an issue the dev(s) are unaware of.  I'm simply reporting, again, that the plugin does not properly do what it is designed to do.  It really does not matter to me at all if it ever works, as the more I think about it there isn't even much purpose to it.  Other hash tools report unchanged hashes.  Parity does not complain.  So is my file actually corrupt because the plugin states it is?  Incredibly unlikely.  If you take half a dozen hash tools and they all report the same hash, at some point you have to believe the hash is correct.  What bothers me is person after person trickling into this thread every now and then reporting, seemingly full of anxiety and in a panic, that their file(s) are being reported as corrupt.  When the fact of the matter is their files are more than likely 100% fine, and the plugin simply is malfunctioning.  Reporting that it is not functioning correctly for everyone and to not trust it as a result is most certainly constructive.

Shorty .... my problem is not what you are describing which I believe to be the reporting of 'corrupt' files. In my case the files are not having the hashes built in the first place so any subsequent 'export' jobs fail those files. Why they can't be built is my question? Obviously I can just ignore them, there's only a few. But an answer as to why the extended attributes can't be set on only a handful of files would be more helpful. Other than that the plugin seems to be working just fine. No corrupt files for me.