mattw

Can you give me a little more instruction... I have proven that I can really screw things up here!

So, I have what I want and need off of the emulated and real drive. At this point, I think the emulated may be a little better.

So, I am pulling some stuff off of the share for the physical disk. Seems that the recoveries were different between the 2, neither really seems better just different.

Attached completed log. disk check.txt tower-diagnostics-20221222-1023.zip

Here it is. disk check.txt

The check completed with the following at the end of the run. No modify flag set, skipping phase 5 Inode allocation btrees are too corrupted, skipping phases 6 and 7 No modify flag set, skipping filesystem flush and exiting. File system corruption detected! I now have the option to run with correction. I assume that is the next step?

Running it now... but how does one just know that from that screen? So, once I have both sources of data online, can I just copy the stuff I want to keep to one of my other shares or make a new share and recover? None of my drives have been showing errors and I am quickly filling up random storage spaces. I have been thinking about modernizing this server with a new mobo and cpu, but I may end up keeping it as is and building a second server with bigger and lower numbers of drives as an in house replication location. We have this little winter storm headed our way, I may have to give up for a day or 2 because we will have power issues in the flatlands of IL with this wind and my UPS is not big. I dragged the server down to where it was more convenient to work on.

@trurl I did find the emulated disk 3 and the contents... and yes lost and found is loaded and looks pretty good, almost all files have names and appear to be the right size'ish. I have physical disk 3 UUID changed, or at least I selected it in UD settings and clicked "Change UUID". The drive is visible, but when clicking moung the system thinks a few seconds and it does not come back mounted. tower-diagnostics-20221222-0822.zip

So, I do not see the note that I have an emulated disk after the reboot... That is why I did not see gains in the Media folder? I never physically removed disk 3 from the system, so yes it is sitting there ready to be mounted. I do not have another disk to install, well I do but it was my previous parity drive and it had begun to pop smart errors, was pretty old. The message for each share is "Some or all files unprotected" I also have no disk shares?

So, I waited over an hour for the array to be stopped and finally did a server reboot from the GUI. Upon boot up it reported unclean shutdown, checked for what was stored on emulated disk 3 and did not find any gains. This diag file is post reboot, the one in the last message is pre-reboot. tower-diagnostics-20221221-1851.zip

So upon stopping the array in maintenance mode so that I could start it in normal mode, it seems to have gotten stuck. Dashboard indicates stopped, line at the bottom of the screen indicates " Array Stopping•Retry unmounting user share(s)..." and array operations screen has the stop button greyed out and indicates "stopping". I have about a 30 minute drive home from work and I will check on it when I get home. Update, just got home and it is still stuck. I think it really is stopped. Guess I could try a reboot. tower-diagnostics-20221221-1622.zip

Ok, has been run without -n. TowerReport.txt

So, yes I did that above and posted the results. I blows my mind that you can test an emulated drive!

It was pretty long, so I zipped it up. CheckFilesystem.zip

I should add that files that were on it are not being emulated... they are just not there. Should I just add it as a blank drive at this point?

Yes, it was xfs.

So, following the above guide... If the file system is XFS or ReiserFS (but NOT BTRFS), then you must start the array in Maintenance mode, by clicking the Maintenance mode check box before clicking the Start button. This starts the unRAID driver but does not mount any of the drives. So, I am in maintenance mode as requested in the doc. You should see a page of options for that drive, beginning with various partition, file system format, and spin down settings. The section following that is the one you want, titled Check Filesystem Status. There is a box with the 2 words Not available in it. This is the command output box, where the progress and results of the command will be displayed. Below that is the Check button that starts the test or repair, followed by the options box where you can type in options for the test/repair command. The options box may already have default options in it, for a read-only check of the file system. For more help, click the Help button in the upper right. The result of clicking the disk 3 gives me none of the options I would expect to see in the doc. So, with an emulated drive how do I get to the menus I need to see? I do see the options on one of my installed and live drives.

Ok, the array is online minus disk 3. tower-diagnostics-20221220-1552.zip

I have tried with Firefox (my normal browser) and with Microsoft Edge. Both seem to yield the same results. BTW, just did a reboot as the only option in the "Array Operations" tab was to reboot or shutdown. I can't run it on my phone, S10+, does not render well enough to trust pushing buttons with my old eyes. This is so frustrating, had this server running for years on 5.0 until my key died and life was in the way and I could not take enough time to troubleshoot it. Then adding cache drive and ram and my lack of abilities got me to this point. I will quit using Firefox during this process, it must have real issues with Unraid. After the reboot from Edge, I have the option to start the array and to enable maintenance mode when I do it. The stale config message is now gone.

It was done, before the requested reboot. Now I do not have the option on screen to do anything with parity and parity indicates valid. I tried to start the array and the note at the bottom of the screen indicates " Array Stopped•stale configuration".

Ok, reboot has been done and new drive config is in place, system was set to boot into maintenance mode and parity is marked valid. Should I start the array? How do I tell if I am in maintenance mode? Sorry to be so dense. So, if I am following correctly... I should check maintenance mode and proceed as below? IMPORTANT - Check both "parity is already valid" and "maintenance mode" and start the array (note that the GUI will still show that data on parity disk(s) will be overwritten, this is normal as it doesn't account for the checkbox, but it won't be as long as it's checked) -Stop array -Unassign disk3 -Start array (in normal mode now), and post the diagnostics. tower-diagnostics-20221220-1151.zip

Ok, different browser which has never even connected to the server... New config, selected all and applied. Back to main and tried to reassign drive 5 and when I tell it "no device" it will not remove disk 5 no matter what. It still insists my array is offline, but I can still get to all of my shares. I am still getting nightly emails from it telling me it is healthy...? tower-diagnostics-20221220-0933.zip

Ok, so I did the new config and assigned all. Went back to the array screen and it will not let me unassign disk 5. When I tell it "no device" it just leaves it as is. I have attached my current diags. So, I am a network engineer for a major university and have been for 32 years, but a server guy I am not! I feel really dumb at the moment. Why does my array and shares appear to be online but the dashboard tells me that it is stopped? This is my array options screen, no option for valid parity or to start or stop the array. tower-diagnostics-20221219-2105.zip

Correct, I have not made the change yet. Do I need to move the drive configs around before or after the config new? I seem to have a fundamental misunderstanding of the config new tool.