Internal inconsistency in block size!

[manticore]

I have a problem. I didnt change my config for months but now i get this error message when i try to run a sync:

Decoding error in D:/content.lst at offset 663403666
The file CRC is correct!
Internal inconsistency in block size!

I tried so rename the D:/content.lst, but with the other lst files, same error message :(

What can i do??

[Andrea Mazzoleni]

Hi manticore,

It's an unexpected error. Not really clear why happened.

To recover, you can try to use the special "manticore" version available at:
http://snapraid.sourceforge.net/beta/

And after making a backup copy of your "content" file, you can try the command:

snapraid test-rewrite

This should fix the content file.

Please also keep track of any message printed during the "test-rewrite". They can help me to understand what happened.

After this command, you can revert back to the latest 5.2 version.

Let me know if this works, if not we have other things to try.

Ciao,
Andrea

[rubylaser]

Sorry to necro an old thread, but I am experiencing this same issue. I'm running 8.1 now. The error is this...

Internal inconsistency in opened file for block 1004046

I made copies of all my content files and ran snapraid test-rewrite as shown in your directions, but I'm still faced with the same error. A diff works with no errors, but trying to run a sync fails and give me the message about internal inconsistency. Any ideas?

[rubylaser]

Sorry, I mentioned that diff works and sync does not previously, but the problem isn't the sync, it appears there are a bunch of data errors, and I get the inconsistency error when I try to run snapraid -e fix.

Here's the end of a snapraid sync and then an attempt to run snapraid -e fix.

100% completed, 1124509 MB processed in 0:42
Time for disk: 11% 8% 8% 8% d8:16% 1% 7% 8% 0%
Time for parity: 12% 15%

      15 file errors
       0 io errors
      17 data errors
WARNING! Unexpected file errors!
DANGER! Unexpected data errors! The failing blocks are now marked as bad!
Use 'snapraid status' to list the bad blocks.
Use 'snapraid -e fix' to recover.
Saving state to /var/snapraid/content...
Saving state to /mnt/data/HIT-MJ0351YNG7XK9A/content...
Saving state to /mnt/data/SEA-Z30031NY/content...
Saving state to /mnt/data/SEA-Z3002C2P/content...
Saving state to /mnt/data/HIT-MJ1313YNG1LMJC/content...
Saving state to /mnt/data/HGST-PL2331LAG9056J/content...
root@fileserver:~# snapraid -e fix
Self test...
Loading state from /var/snapraid/content...
Scanning disk d1...
Scanning disk d2...
Scanning disk d5...
Scanning disk d6...
Scanning disk d8...
Scanning disk d10...
Scanning disk d11...
Scanning disk d12...
Scanning disk d13...
Filtering...
Using 3405 MiB of memory.
Initializing...
Fixing...
Internal inconsistency in opened file for block 1004046

Here's the output of snapraid status.

 snapraid status
Self test...
Loading state from /var/snapraid/content...
Using 3362 MiB of memory.
SnapRAID status report:

   Files Fragmented Excess  Wasted  Used    Free  Use Name
            Files  Fragments  GB      GB      GB
   18325      69     563       -    2878      70  97% d1
   11783     136     547    -1.5    3944      52  98% d2
   18580     241    4310    -8.8    3816     170  95% d5
    7481      81     328       -    2918      12  99% d6
   14663      37     765       -    1957      11  99% d8
    2854      49     175       -    2785     164  94% d10
  131510     487    2056       -    2787     163  94% d11
     459      33      43       -     642    2355  21% d12
     554       8      10    -1.3     309    3689   7% d13
 --------------------------------------------------------------------------
  206209    1141    8797     0.0   22041    6689  76%


 92%|                                                  *
    |                                                  *
    |                                                  *
    |                                                  *
    |                                                  *
    |                                                  *
    |                                                  *
 46%|                                                  *
    |                                                  *
    |                                                  *
    |                                                  *
    |                                                  *
    |                                                  *
    |                                                  *
  0%|+_+_+___+__++__+___++___+____+__+_____+_+++___+_+_*_+________+_+_+___+
    16                    days ago of the last scrub                      0

The oldest block was scrubbed 16 days ago, the median 4, the newest 0.

WARNING! The array is NOT fully synced.
You have a sync in progress at 99%.
No rehash is in progress or needed.
DANGER! In the array there are 57896 errors!

They are from block 72954 to 15089445, specifically at blocks: 72954 174495 226841 234447 234667 235023 235151 235271 235609 235732 236298 236418 236771 237014 237341 237912 238495 238609 238742 239079 239202 239355 240374 240515 240831 240939 241087 241429 241525 241655 242087 242240 242656 242805 243134 243224 243383 243838 243991 244578 244895 244994 245591 245738 246068 246331 246653 246771 246922 247206 247478 247885 248479 249067 249554 249630 250154 250236 250395 251899 251904 252587 252596 253282 253286 253968 253979 254664 254669 255352 255361 256044 256050 256733 256741 257505 258096 258179 258321 258893 258899 259584 259585 260275 260278 260964 260966 261655 261659 262344 262345 263036 263039 263723 263725 264415 264420 265103 265105 265793 265798 and 57795 more...

To fix them use the command 'snapraid -e fix'.
The errors will disapper from the 'status' at the next 'scrub' command.

[Andrea Mazzoleni]

Hi rubylaser,

Thank for the report. I'm investigating about it.

It seems something related at the "-e" option.

To workaround the issue, you can likely try to fix only the mentioned block with:

snapraid -S 1004046 -B 1 fix

and then retry the -e fix.

Ciao,
Andrea

[Andrea Mazzoleni]

Hi rubylaser,

You can also try the beta v8.2 that should fix this issue at http://beta.snapraid.it/

There is not big change compared to v8.1, so you can safely use it.

Ciao,
Andrea

[rubylaser]

Thanks, Andrea! I upgraded to 8.2 and ran the snapraid -S 1004046 -B 1 fix command, and that completed successfully. Now, I'm trying to run snapraid -e fix and see how that goes. If that completes, I'll scrub the whole array to make sure everything is okay.

So I understand the first command, this is starting a fix on the bad block and only fixing that one block, correct?

[rubylaser]

[UPDATE] Thanks again Andrea! This is fixed and back in business.

Fixing...
100% completed, 93930 MB processed in 1:15

    2764 errors
    2764 recovered errors
       0 unrecoverable errors
Everything OK

[rubylaser]

Another update. It appears that when it did the repair, it corrupted some of my files. I have a few partially corrupted jpegs and some video files. Oh well, I'll just restore from my backup. Thanks again!

[rubylaser]

dupe