jrhamilt

Sorry, this seems stupid... How do I "run a check"? No button or other mechanism here or in the settings (as far as I can see). Do I need to run an export first? The exports are ancient... (It probably has not been running...)

Disk issues resolved. I hope. Disk 7 rebuilt on new drive. Disk 7 going back with RMA, failed in under 3 years. Disk 7 doesn't appear to have been selected in the plugin settings somehow? Dont know. Isn't clear that it has been running recently... What do those steps look like to ID the corrupt files? Any help I can get finding them here is awesome. Will get a other drive running as second parity after the data restore...

I can't get logged in... Has worked for yyears, and the data is there, but after a double disk failure, I have some restores to do. Says that it's "being updated", but has said that now for weeks. All apps and plugins updated, including this one. Help? Image cropped to not share user name, etc, but this happens after I try to login. I did change password in CrashPlan recently... Could that be it?

Turns out, I have the "Dynamic File Integrity" plugin... Should this be able to find any of the file corruption?

Huh. Drive 7 now throwing a few more errors and has something in the SMART file. Next steps? (Haven't finished building second parity because of the errors... Disk 7 had 128 errors during that rebuild. WDC_WD40EFAX-68JH4N0_WD-WX42D308JR81-20230422-1004.txt

Understand that another file system type would be better... And longer term I can head that way. In the mean time, is there anything that you know of that will help identify and replace corrupt files? As for parity, my intent is to add a second parity disk. Does it need pre-cleared? Can I just add it to the array? I feel like I should do that before changing file system types.

Finished, no errors, awaiting next steps, but going to go with this... Another question (3rd one)... I plan to use one of the blank 4tb drives as a parity drive. What order of operations should I follow? Get the parity drive cleared and added then recover stuff? Or other way around... Thank you so much!!!

The re-wrotento disk 2 is nearly complete. Couple next step questions: Will I need to redo the check disk activities for the now new disk 2 given this update? Any recommended tools for recovering potentially lost files? (Thinking checksum evaluators, etc that can work from Windows to see if downloaded backups match files in Unraid...) Backup solution is CrashPlan running on the Unraid box itself. Once array is running can do a restore there, but seems wasteful. Should only restore damage / corrupted files if possible...

They happened close in time. I'll try to rebuild overwriting the "new disk 7" and see if they pop up again.

I have the "new disk 7" that I could overwrite... It was built with the 18k or so of read errors, and the "better" parity state... Do you think that at this point, we are better off on this route with "old disk 7"? I kinda think we are, but I also acknowledge that I'm not sure we will get another chance at reading from "old disk 2" again...

During the Disk 2 rebuild, there were 1151 read errors on Disk 7. I did not cancel. Subsequent to that rebuild (with the read errors), we ran the check disk actions per your notes above. Per your most recent instructions, I have now rebooted, and attached the Diags. Next steps? I don't know what caused the read errors. If we need to rebuild again, I have no problem with doing that... Just being "slow and steady" through this part. whitenas-diagnostics-20230417-2247.zip

Seems like, even with the read errors from "original disk 7", and the potential for bad sectors in 2 from the rebuild, this is the best path forward, right? Now, what's to be done with Disk 7? When I bring the disk online I plan to have the backup service try and restore all the files it backed up in place overwriting things as it goes... Then will do some other checks on the data that wasn't backed up. I also plan to add a second parity. Thoughts on when I should do that?

Done. Didn't ask for L, I don't think.

Here are the results.

Here are some screenshots of the disk 2 details and the array status overall. Default for the system for filesystem is XFS.

Hmmm. The File System type for Disk 2 is "auto", so there is no check disk section. I think all the drives were xfs. Should I "set" disk 2 to XFS first? Is that a doable thing?

Can't do that from maintenance mode, right? Need to actually mount the drives with a normal startup, right? I did finish the rebuild of Disk 2, (with the 1151 read errors from Disk7 per above). Does that change anything? Do I just run it on the file system itself since it's not emulated?

So, thinking that not much could be lost by trying a sync, I assigned a new drive to the disk2 slot, and started a rebuild. All of that looked pretty normal, but I did wind up getting some read errors from the "good disk 7". I didn't write from Disk 2 to Disk 7, this one should be unmolested, but I guess I'm realizing at this point, that both drives really are most likely bad... I don't have a good feel for why the reads failed... Can't get a diagnostic right now, but this is where it's at...

That doesn't look right... That's starting the array as "unassigned". I stopped the array as soon as diags and screen shot were complete... What now? whitenas-diagnostics-20230416-0851.zip

Hmmm - if I unassign and then start the array, we're not done, right? That's just going to emulate Disk 2 for now. Correct? Then I have to rebuild on Disk 2? Is the point to check the diags before we commit to rebuilding on 2? Here's the screen after the start in maintenance...

I would like to try it, and would appreciate your instructions. At the end of my previous build, it noted that disk 7 is invalid. I believe that with it being marked as invalid, that there is no way that I can successfully turn the array on, and I don't think that a "check disk" on disk 2 is going to do anything good. I think the steps are something like, put the other disk back in (the old, probably good disk 7), force it to think the previous configuration (current bad disk 2, old probably good disk 7) is good, (new config? parity correct check mark? start in maintenance? something like that)... then shutdown, pull Disk 2 out, start array. Assign new (blank) 4 TB drive as Disk 2. Start in Maintenance. Sync. I think that series of steps will be as good as I can get it... But again, would like instructions from the professional. I don't need to use the array while we do any of this. It's probably better that it's not used. (I've downloaded the super critical data from my backups, so having this down for a week isn't horrible.) Here is the final result from the main page.

I'm thinking since this is getting so many errors (up to 18,000), that I will let this finish. Then, is there a way for me to put the old "probably good" drive back in the array, force Unraid to consider that drive and parity to be correct, and rebuild on top of Disk 2? Then I'll have a "Disk 2 rebuild" and a "Disk 7 rebuild" and the old Disk 2 (if it still runs) and the old Disk 7, and my online backup - and from there it just is what it is... And when I find failed files, I've got options on trying to find them...

I've removed the "potentially good" disk 7, and have a new disk in it's place. I'm starting the array in maintenance mode and trying to rebuild to Disk 7... Disk 2 is starting to throw read errors... Not sure what to do, going to let it rebuild? (I still have the old disk 7, which I think / hope is good...) Need help!

The disk wasn't disabled for too long - and I was watching everything. A couple "quiescent" hours. But, it's a lot of data and there are other users - though typically they wouldn't be writing anything there. And all of the dockers were disabled. And the mover was disabled. I suppose I did turn the array back on and it took me a little while (again, couple hours) to realize that Disk 7 was offline... Thinking it through, if there were any changes to the emulated disk 7, and we wind up rebuilding Disk 2, then I've effectively corrupted Disk 2 if it rebuilds in those areas (because disk 7 isn't what we said it was). I could remove disk 7 and check file modification times? But that doesn't help by itself... - I need to check the modification times on the "emulated" disk 7 and compare to the real disk 7. That would require me to start the array and "read" the contents of the emulated disk 7 (enough to get the file properties). Can I start the array "read only" in order to check that out? If the file mod times on Disk 7 "emulated" and Disk 7 "actual" match, is that sufficient?

Maybe it would be better to put a new "cleared" drive in place of Disk 7 and "try" the rebuild first? I don't know. I'm going to be out of town for the week, so I'm not going to be able to physically touch things for a bit... And, here's the setting that I changed before Disk 7 went weird - I assume that this would prevent writes to the disk. (Don't have any dockers that would write to it either - they were all disabled).