Did you have a rehash in progress? (Meaning that you had started a snapraid rehash)
I'll investigate further to find the possible cause. In general, such internal inconsistencies are caused by memory malfunctions that result in corrupted data being written to the content file. It might be worth running a memtest as well.
Regardless, I don't think it's recoverable. It would be better to start from scratch by deleting the content file and running a new sync.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The newly released version 14.8 will now detect this condition when saving the
content file, preventing it from becoming impossible to load. It makes sense to upgrade to this version.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, seem to be having an issue, all of the copies of the content file give the same message, not sure how to fix!
Self-test...
Loading state from C:/Data/Snapraid/snapraid.content...
Error decoding 'C:/Data/Snapraid/snapraid.content' at offset 1502333000
The CRC of the file is correct!
Internal inconsistency: Missing previous checksum!
Stacktrace of snapraid v14.7, mingw, gcc 11.5.0, 64-bit, PATH_MAX=1024
[bt] 00: 00007ff6133637cc
[bt] 01: 00007ff613345166
[bt] 02: 00007ff61332fe88
[bt] 03: 00007ff61337a64a
[bt] 04: 00007ff6133210cb
[bt] 05: 00007ff613321416
[bt] 06: 00007ffd01c54cb0
[bt] 07: 00007ffd034bedcb
Please report this error to the SnapRAID Forum:
https://sourceforge.net/p/snapraid/discussion/1677233/
Did you have a rehash in progress? (Meaning that you had started a snapraid rehash)
I'll investigate further to find the possible cause. In general, such internal inconsistencies are caused by memory malfunctions that result in corrupted data being written to the content file. It might be worth running a memtest as well.
Regardless, I don't think it's recoverable. It would be better to start from scratch by deleting the content file and running a new sync.
Nope, I wasn't touching it!
I'll give memtest a run but fair, I figured that might be the case
Does look like I've got some silent memory issues, I've rebuilt the parity anyway, thanks for confirming!
The newly released version 14.8 will now detect this condition when saving the
content file, preventing it from becoming impossible to load. It makes sense to upgrade to this version.