Author Topic: Invalid state - Unexpected EOF on 001971.flxr  (Read 874 times)

Offline kevin.r

  • Newbie
  • *
  • Posts: 33
  • Karma: +0/-0
    • View Profile
Invalid state - Unexpected EOF on 001971.flxr
« on: January 29, 2018, 08:27:38 am »
Not sure what to do here. This error on 001971.flxr has shown up on 3 different validations that I performed in the past (it's at 26% which I've seen the parity creation fail on in the past). Each time I rebuilt the parity from scratch and I've even replaced the drive it was stored on assuming the drive was the issue (was using a Drobo storage array, now I'm just using plain external disks).

Any recommendations? I'm guessing my best bet is to go back to a previous version of Flexraid.

Quote
[2018-01-28 17:46:11,101] INFO : [verify] started at: Sun Jan 28 17:46:11 EST 2018
[2018-01-28 17:49:11,491] INFO : Using RAID engine Tx
[2018-01-28 17:49:12,211] INFO : Starting verify at: 0 - Number of bytes: 7950897774592
[2018-01-29 01:35:07,018] ERROR: Invalid state - Unexpected EOF on P:1:0\001971.flxr
java.io.IOException: Invalid state - Unexpected EOF on P:1:0\001971.flxr
   at com.tchegbe.lib.common.io.d.a(Unknown Source)
   at com.tchegbe.lib.common.io.d.a(Unknown Source)
   at com.tchegbe.lib.common.io.i.<unknown>(Unknown Source)
   at com.tchegbe.lib.common.io.parity.e.a(Unknown Source)
   at com.tchegbe.lib.common.io.e.f.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source)
[2018-01-29 01:37:30,652] INFO : Verify failure: operation aborted!
[2018-01-29 01:37:30,652] INFO : [verify] completed at: Mon Jan 29 01:37:30 EST 2018

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,547
  • Karma: +204/-16
    • View Profile
Re: Invalid state - Unexpected EOF on 001971.flxr
« Reply #1 on: January 29, 2018, 11:29:06 pm »
Basically, reading that file fails prematurely. Run chkdsk to fix any potential file system issue or force bad sector reallocation.

Offline kevin.r

  • Newbie
  • *
  • Posts: 33
  • Karma: +0/-0
    • View Profile
Re: Invalid state - Unexpected EOF on 001971.flxr
« Reply #2 on: January 31, 2018, 04:34:53 pm »
Basically, reading that file fails prematurely. Run chkdsk to fix any potential file system issue or force bad sector reallocation.

No luck, did a full scan, including bad sector; see screenshot. (oh, and I tried a validate (not quick) and it locked up at exactly 90%.

So, I've seen this error in multiple configurations, with different harddrives as ppu1, but the error is always on 001971.flxr. Any other suggestions? Should I try a forced sync verify?
fyi, the setup is 14 drives (6x 8tb, 6x 4tb, 2x 5tb, ppu1 2x 4tb, ppu2 3x 3tb)

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,547
  • Karma: +204/-16
    • View Profile
Re: Invalid state - Unexpected EOF on 001971.flxr
« Reply #3 on: January 31, 2018, 08:09:32 pm »
Have you tried copying that file out to see if it does without issues?
Maybe it is not that file but one of the data files that compute into it. So, chkdsk the data disks also.

Offline kevin.r

  • Newbie
  • *
  • Posts: 33
  • Karma: +0/-0
    • View Profile
Re: Invalid state - Unexpected EOF on 001971.flxr
« Reply #4 on: February 01, 2018, 06:37:16 am »
Have you tried copying that file out to see if it does without issues?
Maybe it is not that file but one of the data files that compute into it. So, chkdsk the data disks also.
That would make more sense. Just found out you can only run one chkdsk at a time, this is going to take a week :-/ Skipping the 6 empty drives for now; recycle bin feature of flexraid disabled, so they are actually blank).
Just noticed I was out ram during this check disk (22GB of 24GB going to dllhost.exe), doubt it's related but worth mentioning.

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,547
  • Karma: +204/-16
    • View Profile
Re: Invalid state - Unexpected EOF on 001971.flxr
« Reply #5 on: February 01, 2018, 09:50:06 pm »
That would make more sense. Just found out you can only run one chkdsk at a time, this is going to take a week :-/ Skipping the 6 empty drives for now; recycle bin feature of flexraid disabled, so they are actually blank).
Just noticed I was out ram during this check disk (22GB of 24GB going to dllhost.exe), doubt it's related but worth mentioning.
Run a virus scan and malware tools promptly.

Offline kevin.r

  • Newbie
  • *
  • Posts: 33
  • Karma: +0/-0
    • View Profile
Re: Invalid state - Unexpected EOF on 001971.flxr
« Reply #6 on: February 03, 2018, 03:26:44 pm »
Run a virus scan and malware tools promptly.
Just checked just in case, nothing found.
It's only during the checkdisk that it does that. FYI, the computer is isolated and only runs Flexraid.

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,547
  • Karma: +204/-16
    • View Profile
Re: Invalid state - Unexpected EOF on 001971.flxr
« Reply #7 on: February 04, 2018, 06:51:36 pm »
I would wipe the OS and start fresh. Whether it is a virus or corrupted OS, I would not risk it.

Offline kevin.r

  • Newbie
  • *
  • Posts: 33
  • Karma: +0/-0
    • View Profile
Re: Invalid state - Unexpected EOF on 001971.flxr
« Reply #8 on: February 05, 2018, 04:47:00 pm »
I would wipe the OS and start fresh. Whether it is a virus or corrupted OS, I would not risk it.

I've scanned 7 of the 15 drives so far, all came back clean so far. 2 DRUs with content remain, then 6 empty DRUs.

PS
I'm certain it's nothing. It's only during check disk that the RAM usage spikes, maybe it's because I don't have a page file? Did a system filechecker (sfc) just in case; everything's fine there too.
(Just confirmed that's a "feature" of chkdsk lol, https://superuser.com/questions/328165/why-is-chkdsk-using-90-of-my-ram)
« Last Edit: February 05, 2018, 06:56:56 pm by kevin.r »

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,547
  • Karma: +204/-16
    • View Profile
Re: Invalid state - Unexpected EOF on 001971.flxr
« Reply #9 on: February 05, 2018, 11:12:10 pm »
Ah, ok if it is a known bug. I would not call it normal, but if there is not fix for it, then it is what it is.

Offline kevin.r

  • Newbie
  • *
  • Posts: 33
  • Karma: +0/-0
    • View Profile
Re: Invalid state - Unexpected EOF on 001971.flxr
« Reply #10 on: February 07, 2018, 11:08:20 am »
FYI, chkdsk came back clean for all drives. Going to just do a forced sync verify and hope for the best.

Offline kevin.r

  • Newbie
  • *
  • Posts: 33
  • Karma: +0/-0
    • View Profile
Re: Invalid state - Unexpected EOF on 001971.flxr
« Reply #11 on: February 08, 2018, 08:08:13 am »
Quote
An exception has occurred!
See logs for full message.
Error message: Invalid state - Unexpected EOF on P:1:0\001970.flxr
Forced Sync Verify re-processed 0 bytes out of 2114207088640 bytes
Forced Sync Verify failure: operation aborted!

Going to delete 1970 and try a force sync.

Offline kevin.r

  • Newbie
  • *
  • Posts: 33
  • Karma: +0/-0
    • View Profile
Re: Invalid state - Unexpected EOF on 001971.flxr
« Reply #12 on: February 08, 2018, 04:53:33 pm »
Going to delete 1970 and try a force sync.

Figured it out...it's on the second parity not the first. I assumed from the wording P:1 meant the first parity, but now that I think about it P:1:0 means parity drive 2, disk 1 then the file. I feel special...

Offline kevin.r

  • Newbie
  • *
  • Posts: 33
  • Karma: +0/-0
    • View Profile
Re: Invalid state - Unexpected EOF on 001971.flxr
« Reply #13 on: February 13, 2018, 02:42:20 pm »
Quote
Verify success: all bits match!

THE END!