repair snapraid array with error after syncing

  • Hi.


    First sorry for my english :S and thanks for the help.



    After syncing a snapraid array it gives me the follwing error.




    after that I have executed "snapraid status" and the reading has been


    I have looked for information in the forum and I thought that the solution was to apply "snapraid --filter-error fix" whit the following result




    Now i'm stuck and i dare not do anything else, i appreciate any help. :thumbup::thumbup:


    Before all this i have changed a 2TB disk for a 4TB one (D3) and added another 4TB (D4). After these operations the sync command was correct. Later ihave copied files from one disk to another to empty the full ones and sync again gave me the error. I don't know if this is relevant.

    Core I3 3225, RAM 4GB, SnapRaid and UnionFS, 1 parity disk (5TB), 3 data disks (5TB+4TB+4TB), 1 x 32GB USB disk for startup, 1 x 60GB SSD disk for docker

    I DO NOT SPEAK ENGLISH. I translate with google, sorry if sometimes I am not well understood :)

  • It would also be helpful to know if this query is not appropriate in this forum and in that case to know where I can go.

    Thanks again and sorry for the inconvenience.

    Core I3 3225, RAM 4GB, SnapRaid and UnionFS, 1 parity disk (5TB), 3 data disks (5TB+4TB+4TB), 1 x 32GB USB disk for startup, 1 x 60GB SSD disk for docker

    I DO NOT SPEAK ENGLISH. I translate with google, sorry if sometimes I am not well understood :)

  • I'm surprised no one's answered, but I don't use this any more, I just went with the suggestion and run snapraid -e fix whenever I had an error warning, one time it came back with 66 :) but I never had any unrecoverable errors

  • Thank you very much for answering, I am also surprised that they did not answer me, I thought they had ostracized me for asking such basic questions. I'm new to OMV and I still don't dare to touch things without understanding them well.


    I obviously already used that command, although I hadn't said it, I'll give you the result, I still have the error.



    I want to give OMV a chance, I really like it but I find it difficult to understand the information available to handle it. I have managed to install OMV and get it working without bothering anyone but I don't know how to solve this I get the impression that this forum is for users much more advanced than me, if so tell me and I will look for help elsewhere although it is difficult to find. Thanks also.

    Core I3 3225, RAM 4GB, SnapRaid and UnionFS, 1 parity disk (5TB), 3 data disks (5TB+4TB+4TB), 1 x 32GB USB disk for startup, 1 x 60GB SSD disk for docker

    I DO NOT SPEAK ENGLISH. I translate with google, sorry if sometimes I am not well understood :)

  • The first question then is why have you chosen to use Snapraid? for me the choice was because 95% of my files are media which is the idea of Snapraid.

    There are a few on here that use it but not many and most would refer to the Snapraid manual, I can't remember if the reported errors came after a scrub or sync, whatever it was after running fix I would then run the scrub or sync.

    If the manual doesn't help then try a search there are a few hits in relation to unrecoverable errors and seem to point to the content file.

  • Quote

    The first question then is why have you chosen to use Snapraid? for me the choice was because 95% of my files are media which is the idea of Snapraid.

    Indeed I use snapraid because on this server I only have multimedia files, with little or no movement.


    Quote

    There are a few on here that use it but not many and most would refer to the Snapraid manual, I can't remember if the reported errors came after a scrub or sync, whatever it was after running fix I would then run the scrub or sync.

    If the manual doesn't help then try a search there are a few hits in relation to unrecoverable errors and seem to point to the content file.

    Reported errors are after a sync.


    The system has entered a loop from which I don't know how to get out. After running "snapraid -e fix" it tells me that there is an unrecoverable error. I run "snapraid scrub", the error follows, and it says to run "snapraid status" and then "snapraid -e fix" and then "snapraid -p bad scrub". After the process the error follows and takes me back to the beginning.

    Core I3 3225, RAM 4GB, SnapRaid and UnionFS, 1 parity disk (5TB), 3 data disks (5TB+4TB+4TB), 1 x 32GB USB disk for startup, 1 x 60GB SSD disk for docker

    I DO NOT SPEAK ENGLISH. I translate with google, sorry if sometimes I am not well understood :)

  • Well you're using Snapraid for what it was meant to be used, as to the error you've done exactly as instructed in the manual, it's not in a loop as such it's just reporting it has found an error that's unrecoverable How do you stop it or remove it I don't know, from recollection there is tab in the plugin to exclude, perhaps adding uncoverable in the correct format will prevent it from reporting.

  • I assume you mean a tab that says "fix silent". My version of OMV is installed in Spanish. I cannot locate that command in the Snapraid Manual and I ignore the result. Do I apply it? Will it solve the problem or hide it? Is the problem in the snapraid sync or is it my data and my hard drives?

    Core I3 3225, RAM 4GB, SnapRaid and UnionFS, 1 parity disk (5TB), 3 data disks (5TB+4TB+4TB), 1 x 32GB USB disk for startup, 1 x 60GB SSD disk for docker

    I DO NOT SPEAK ENGLISH. I translate with google, sorry if sometimes I am not well understood :)

  • Will it solve the problem or hide it

    I think it will hide it, but I used this for about 12 months primarily because I had mismatched drive sizes, I've since replaced two of my drives, finally completed a clean install of V5 but I've deployed zfs, only because I have used it before in another OS.

    Is the problem in the snapraid sync or is it my data and my hard drives?

    That's what I've been trying to find out, but without success, I'm thinking/wondering if the parity drive was removed, wiped, formatted then added back would it resolve the error.

    The next question is do you have a backup of the data, as this is something that should not be overlooked, with me everything got backed up once every two weeks, except for any docker containers and configs which are on a separate drive.

  • I'm thinking/wondering if the parity drive was removed, wiped, formatted then added back would it resolve the error.

    no, would it help?

    The next question is do you have a backup of the data

    Unfortunately not now, use the backup disks you used to mount this server. I am waiting for a 12TB disk that I will use for backup. I should have bought that record before, I know, don't remind me ... X/ Personal photos are endorsed, the rest are not.


    "fix silent" applied, keeps giving error...

    and after "status"


    We are like at the beginning...

    Core I3 3225, RAM 4GB, SnapRaid and UnionFS, 1 parity disk (5TB), 3 data disks (5TB+4TB+4TB), 1 x 32GB USB disk for startup, 1 x 60GB SSD disk for docker

    I DO NOT SPEAK ENGLISH. I translate with google, sorry if sometimes I am not well understood :)

    Edited once, last by chente ().

  • Thanks for your time : pulgar arriba:: pulgar arriba:

    Core I3 3225, RAM 4GB, SnapRaid and UnionFS, 1 parity disk (5TB), 3 data disks (5TB+4TB+4TB), 1 x 32GB USB disk for startup, 1 x 60GB SSD disk for docker

    I DO NOT SPEAK ENGLISH. I translate with google, sorry if sometimes I am not well understood :)

  • Have you checked the smart stat's on your drives? If there are hardware errors involved, generally speaking, that might be why you can't run a sync. Under Storage, SMART, enable SMART. Then run some device tests. In your case, off-line LONG tests might be in order.


    Some details on SMART are in the current User Guide, under Hard Drive Health and SMART.

  • Have you checked the smart stat's on your drives? If there are hardware errors involved, generally speaking, that might be why you can't run a sync. Under Storage, SMART, enable SMART. Then run some device tests. In your case, off-line LONG tests might be in order.


    Some details on SMART are in the current User Guide, under Hard Drive Health and SMART.

    I have the short test scheduled weekly. I do not see errors in the results. I think that now it would not be wise to do a long test because I have no backup, I will wait for the hard disk that I bought to arrive.


    I already downloaded that guide a month ago and it was very good for me to configure OMV and try to understand how it works.


    Thanks for your interest.

    Core I3 3225, RAM 4GB, SnapRaid and UnionFS, 1 parity disk (5TB), 3 data disks (5TB+4TB+4TB), 1 x 32GB USB disk for startup, 1 x 60GB SSD disk for docker

    I DO NOT SPEAK ENGLISH. I translate with google, sorry if sometimes I am not well understood :)

  • The latest Guide, in the last week, has some very minor updates and was reorganized a bit. (I've been going through it.)


    I think that now it would not be wise to do a long test because I have no backup, I will wait for the hard disk that I bought to arrive.

    That makes sense to me. A long test does a surface scan which might detect a bad sector, if there some present, but are as yet undetected. But a long test in an exercise for a drive.


    Have you looked at these SMART stat's? Any counts?


    SMART 5 – Reallocated_Sector_Count

    SMART 187 – Reported_Uncorrectable_Errors

    SMART 188 – Command_Timeout

    SMART 197 – Current_Pending_Sector_Count

    SMART 198 – Offline_Uncorrectable


    Are you using the UnionFS plugin?

  • The latest Guide, in the last week, has some very minor updates and was reorganized a bit. (I've been going through it.)

    Ok, I'll check the new version in case it helps, thanks.



    All disks report zero but there are 3 disks that do not report values 187 188

    Are you using the UnionFS plugin?

    Yes, my disk configuration is:


    1 parity - 5TB

    1 data - 5TB

    2 data - 2TB

    3 data - 4TB

    4 data - 4TB


    Data disks 1 to 4 joined with unionFS

    Core I3 3225, RAM 4GB, SnapRaid and UnionFS, 1 parity disk (5TB), 3 data disks (5TB+4TB+4TB), 1 x 32GB USB disk for startup, 1 x 60GB SSD disk for docker

    I DO NOT SPEAK ENGLISH. I translate with google, sorry if sometimes I am not well understood :)

    Edited once, last by chente ().

  • Ok, I'll check the new version in case it helps, thanks.

    Not to worry about that. There are no functional differences - just a bit more readable. Just get a new copy for ref.


    All disks report zero but there are 3 disks that do not report values 187 188

    That's good news but the stat's many change with Long tests.

    There's nothing to worry about with stat's that are not available. Stat 5 and 197 are a couple of the most worrisome.

    _________________________________________________________________________

    I chatted with geaves about your situation. There's no obvious reason for this fault and I've never seen exactly what you're dealing with.
    (I finally have a marginal 2TB hard drive to throw in SNAPRAID array, for some testing, but results may take months.)

    While waiting on your backup drive, you might consider copying and pasting some of your posts, above, into the SNAPRAID forum. They, on the SNAPRAID forum, have a lot of cumulative experience with odd errors in a SNAPRAID array.

  • There's no obvious reason for this fault and I've never seen exactly what you're dealing with.

    It's the unrecoverable error, I can't work out if this is related to a physical drive or it's an error in relation to the parity, if you do a search there is very little out there.


    That's why an option I suggested was to remove the parity drive, wipe it, format it and add it back, but that approach may be prudent after a backup of the data

  • chente , I forgot to ask, what disk format are you using? EXT4?

    ____________________________________________________________________________________


    I can't work out if this is related to a physical drive or it's an error in relation to the parity

    I agree that there's no way, that I know of, to make that determination. But we both know that SMART stat's can lag, somewhat, behind the actual physical condition of the disk. A Long test (after backup) would be the best way to dig out a potential drive problem.

    That's why an option I suggested was to remove the parity drive, wipe it, format it and add it back, but that approach may be prudent after a backup of the data

    I agree that wiping the parity drive is an action that could be tried, after he backs up.
    __________________________________________________________________________

    While others may see it differently, I see the health and age of the Parity drive as being the most important to a SNAPRAID array. A Parity drive with an odd issue has the potential create a lot of issues and problems in recovery. For those reasons, the Parity drive should be the newest in the array with zero health issues.

    On the other hand, with a good backup in hand, a parity drive problem is one of the easier issues to look at. Wipe it, format it (EXT4), run a long test to be sure of health, and run a sync.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!