Menu

Several UnRecoverable files.. why!?

Help
2018-09-15
2018-09-21
  • SourceForget

    SourceForget - 2018-09-15

    So one of my drives failed, i pulled it out, added another drive, and made sure i have provided the correct drive letter as my previous drive. (I am on windows).

    After this i executed.. snapraid fix -d -d2 -l logfile.txt

    The recovery has started and as i see the logs while its being recovered, equal number of files that are being recovered there are several unrecoverable files as well.
    I have been running the sync every few days.. and for sure this disk that died on me is an old one and has been full for awhile and has been in several sync sessions.
    Inspite of that I see several about 50% recovered and 50% unrecoverable files.
    I am using about 18 disks for pool and 2 parity for these 18 disks..
    Is this the reason?
    However previously many times the disks crashed and i was able to recover 100% without any unrecoverable files.

    Or am i wrong, these unrecoverable files will eventually be recovered when the recovery is complete??? The recovery is still going on, and might take 24 hrs or so to complete.

     
  • Leifi Plomeros

    Leifi Plomeros - 2018-09-15

    You should be able to recover from two completely lost disks.

    Wait until fix is complete and run snapraid diff --test-fmt path to find out what files are missing.

    Most of them should be missing from the lost disk. If you have missing or modified files on multiple other disks then it could result in unrecoverable files.

     
    • SourceForget

      SourceForget - 2018-09-15

      I assure you, there was no new data on this disk. This 4tb disk in the array used to be a pretty much used up disk till only 40gb space left since years. And sync has been run almost every week.
      The unrecoverable movie files i see are in my array since over 4 years.
      But yes, lets wait.. its still at 45% revcovery, it might complete i guess in another 20-22 hrs.
      I'll keep ya posted.

       
    • SourceForget

      SourceForget - 2018-09-15

      Quick question.. the path you mentioned above is the drive that i restored?
      For eg:- i lost drive F:\
      So after swapping out, and restoring, i should use
      snapraid diff --test-fmt F:\ ?? (command without question mark )

       

      Last edit: SourceForget 2018-09-15
  • SourceForget

    SourceForget - 2018-09-16

    Ok the fix is complete.. and about 1tb of files are unrecovered.
    I see many unrecoverable files. This is really pathetic. I did not really expect this from SnapRAID.
    The one time my disk crashed, and i lost so many family pictures, that was stored on my disks since years.
    I have been running sync every week.

     
  • Leifi Plomeros

    Leifi Plomeros - 2018-09-16

    Run snapraid diff --test-fmt path to find out what files are missing and from which disks.
    Don't replace the word path with something else, it tells snapraid that you want the full path of any missing/modified/added files.

    Does snapraid show a lot of removed files on other disks than the lost one?

    Running snapraid status could also give some insight.

    And of course checking the logfile.txt for any specific file that failed to restore would most likely tell you exactly what went wrong. (If the logfile is too big to open in notepad you can find solutions to that problem here: https://www.andreafortuna.org/forensics/how-to-open-very-large-text-files-on-windows/ )

     

    Last edit: Leifi Plomeros 2018-09-16
  • Quaraxkad

    Quaraxkad - 2018-09-17

    and for sure this disk that died on me is an old one and has been full for awhile and has been in several sync sessions.

    This is not neeccessarily a factor. Regardless of how old the data on the failed disk was, or how many times it has been included synced, the more relevant factor is the data on all other disks.

    I have been running sync every week.

    More importantly, how often do you delete/edit/rename/move files? From any of your 18 data disks, not just the one that failed. Unsynced deletions and edits of files on the non-failed disks is the primary cause of unrecoverable files. After you run the suggested command by Leifi Plomeros, you will have a list of files that are either missing or changed since the last sync. Once you have that, you may be able to restore those files to the exact locations where SnapRAID is looking for them, re-run fix, and your previously unrecoverable files should be repaired. For even more specific information on the exact files that are required for recovery, run snapraid fix -l fix.log. This will give you a likely massive log file that tells you, for every missing file block, the filenames and paths of files SnapRAID needs to be able to repair that missing block. Restore those files by whatever means are available (perhaps they are files you can re-download?), then re-run fix.

    EDIT: It also might be worthwhile to run data recovery tools on the failed drive. It's not uncommon to be able to fully recover files off of a failing HDD.

    EDIT2: And DO NOT run sync until you have exhausted all options for recovery.

     

    Last edit: Quaraxkad 2018-09-17
  • Stefan Thüring

    Stefan Thüring - 2018-09-21

    My thinking... the bigger the array/data the higher the chance that moves/deletes reduce the ability to recover. I sync just after I do any multi GB change.

     

Log in to post a comment.

MongoDB Logo MongoDB