joemama

Yep, just in case someone else stumbles across this post with a similar issue...I believe the xfs_repair did the trick, but even after it ran, the disk still showed unmountable. And I was timid to act on a reboot or change because in the world of data recovery(or support in general), your best bet is dont touch anything until you know lest you cross a line of no return that no one can help you out of. But after the reboot, the unmountable flag was cleared and I could start it up like normal. Thanks again for all the help!

I appreciate both of these points and didn't think about the points of failure by coasting lackluster disks. I'll keep that in mind going forward and bump up my time table to phase out the little disks with better larger disks

Going back to your comment, would it be best practice to arrange my disks better? Or will it not matter that much? I'll attach a mockup of how its currently laid out and if you have any tips or insight I'd love to hear it. This is my first run with the platform, and so far I'm loving it, but there may be room for improvement

Good news! So I was reading more articles on the xfs_repair command and somewhere said to do a reboot afterwards because the corrections might not actually take in unraid until you do(or something to that effect). So with the array still in maintenance mode I rebooted the server. When it came back up I logged in and it said array stopped - autostart disabled(or something like that) but it didn't show the disk as unmountable this time. So I went ahead and started the array normally and it came up fine. I can browse the contents and the status appears to be good! I'll attach a final diagnostic I just ran with everything actually stood up and mounted, for posterity. And I read somewhere that if the xfs_repair command found corrupt data it would move it to a directory called Lost and Found, but I don't even see that directory so I believe it recovered everything without corruption! Its recalculating parity now Thanks for the help! I definitely appreciate it since this was a pretty tense start to the day

I wanted the unraid disk layout to match the physical layout. So since my first disk is actually my parity disk, I started at disk 2 for the array. So its just cosmetic So it doesn't sound like the parity disk will help me with the issue on Disk4 at all. And I'm fine with parity overwriting once the array is intact. I just need a recommendation on what to try to get Disk4 back into the array

I'm trying to hang tight for someone more knowledgeable than me to offer some insight so I don't screw something up by going too far. But as I'm poking around with the array still in maintenance mode, I see an option called Sync that looks like it would fire a rebuild. I'm curious if that would help or hurt my situation. My Parity also shows INVALID now, but idk if that means invalid against the newly assigned array data and that it still has the old data in tact. I can confirm that before this the Parity was valid with zero errors. I'll attach an image of the button I'm referencing...

I assigned the existing parity disk with parity data on it to the parity slot. I just meant I *may* have screwed up because it said it was going to overwrite that disk after I made all of my assignments and started the array. If its positive in anyway that the parity disk still has valuable data, as soon as I started the array and saw the disk was unmountable I immediately stopped it and have only had it in maintenance mode since. So maybe it didnt get overwritten yet? I am attaching a previous diagnostic from Dec 2020 as well for reference

Hi all, I had a failing disk(Disk 20) that I migrated the data off of and spun down with the goal of removing it from the array before it tanked. So I did all that, physically removed it, hit New Config(w/ Preserve Assignments). I also rebooted after that succeeded to update my Nvidia Driver. After it came back up it didn't have any of the disk assignments(all showed unassigned), so I re-added them all in the correct order manually. *This may be an area I made a mistake? I added all the disks in the correct order, but when I added my parity drive I got a warning saying the disk would be overwritten when I started the array. In my head I was fine with that because I had no parity errors before this so I assumed my array was intact even after spinning that drive down and removing it. So I was fine with it doing a fresh parity check and overwriting Enter the problem. One disk in my array(Disk4) shows unmountable. When I clicked the disk the File System Type showed Any so I set that to XFS like the rest, but no good. Then while looking through the forums I saw a XFS repair command that I tried, but still no luck. I'm hoping someone can help me get it re-added to the array. I have attached diagnostics as I noticed in previous posts that helps you to see where things are at. The disk in question is Disk 4 - ST12000VN0008-2PH103_ZLW03STN (sdi) Thanks xfs_repair_log.txt