alabama

Hi again Leifi, Good to know I have been using "fix -e" correctly but confused why it doesn't seem to work for me. This is not the first time I encountered this and raised on this forum before. The conclusion then was bad ram/non-ECC and I left it as that. This time I reran "check" and also used independent hash files and multipar to confirm errors were real corruptions, not on the fly memory corruptions. This is actually what happened, I use "-l" for every snapraid command so I always have a complete...

Hi again Leifi, Good to know I have been using "fix -e" correctly but confused why it doesn't seem to work for me. This is not the first time I encountered this and raised on this forum before. The conclusion then was bad ram/non-ECC and I left it as that. This time I reran "check" and also used independent hash files and multipar to confirm errors were real corruptions, not on the fly memory corruptions. This is actually what happened, I use "-l" for every snapraid command so I always have a complete...

Hi again Leifi, Good to know I have been using "fix -e" correctly but confused why it doesn't seem to work for me. This is not the first time I encountered this and raised on this forum before. The conclusion then was bad ram/non-ECC and I left it as that. This time I reran "check" and also used independent hash files and multipar to confirm errors were real corruptions, not on the fly memory corruptions. This is actually what happened, I use "-l" for every snapraid command so I always have a complete...

I have been using snapraid wrong all this while I think. This is a sample of typical file error, where the file is corrupted during a copy or bitrot. error:2365656:u2:Users/photo/Panasonic LX5/20180916/IMG_3892.JPG: Data error at position 3, diff bits 65/128 status:damaged:u2:Users/photo/Panasonic LX5/20180916/IMG_3892.JPG error:5554388:u2:Users/photo/iPhone 6s/20200226/IMG_4817.JPG: Data error at position 2, diff bits 65/128 status:damaged:u2:Users/photo/iPhone 6s/20200226/IMG_4817.JPG msg:status:...

Yes, that would seem to be right option at this point in time for the retirees! Great suggestion. And good point regarding the speed although that's not an issue at the moment.

Understood 100%, thanks Leifi. In my case, I'm migrating 2 levels of parity, one level at a time so will execute "snapraid check -d parity" after migrating the first level of parity to new drives, then "snapraid check -d 2-parity" after migrating the second level of parity to new drives.

Hi Walter, thanks for suggestion! Yes, already using 2 sets of split parity (2x5TB, 2x5TB), still have bunch of drives leftover I rather use the extra drives for data than 3rd set of parity (a bit excessive for my current setup). Sorry my scenarios were very simplified just to highlight my proposal. Maybe something like spanned volumes is the solution after all although I really prefer the simplicity & safety of JBOD and don't mind a tiny bit more complexity in snapraid setup.

Hi Walter, thanks for suggestion! Yes, already using 2 sets of split parity (2x5TB, 2x5TB), still have bunch of drives leftover I rather use the extra drives for data than 3rd set of parity (a bit excessive for my current setup). Maybe something like spanned volumes is the solution after all although I prefer the simplicity & safety of JBOD and don't mind a tiny bit more complexity in snapraid setup.