What could be going on?

I'm kind of flying blind here. I have also had several instances where I get disconnected and when I reconnect, the dockers are no longer enabled?

Do I need to wipe my installation and reinstall? or is there a more nuanced approach?

Thanks-

Attach Diagnostics ZIP to your NEXT post in this thread.

Sorry -

and my parity drive just failed.

I've attached 2, one very recent and one from a failure ago.

I'm on unraid 6.12.6

with

MSI B4590 Tomahawk motherboard

American Megatrends ver. 1.20

and an AMD Ryzen 7 1700X 8core 3400MHz

tower-diagnostics-20260328-1543.zip tower-diagnostics-20260327-1145.zip

Start the array and post new diagnostics

here - I hope you see something in here.

At this point I have replaced the CPU cooler, the power supply, all the old 10TB drives, and added a network card.

Now, with the parity 12TB drive failure, I am at the end of the road.

tower-diagnostics-20260328-1657.zip

Setup Syslog Server and post a screenshot of those settings.

Start the array in normal (not maintenance mode) and post new diagnostics.

Hopefully this is what you want

syslog syslog-previous

A lot more would have to be done to actually get it to save syslogs to another computer, including setting up a syslog server on the other computer.

Just set Remote syslog server to localhost then the syslogs will be saved to the isos share on your Unraid server, then when we ask for them, you can get the sylogs from there, zip and post them.

1 minute ago, lockrob2000 said:

Here I think that this is the most recent.

Not sure where you got those, did you have it mirrored to flash?

What I really am asking for now is

16 minutes ago, trurl said:

Start the array in normal (not maintenance mode) and post new diagnostics.

syslog-127.0.0.1.log

I did have it mirrored to flash.

I just pulled the diagnostics and attached.

Those are not the diagnostics

You posted diagnostics earlier in the thread, but the array was not started in normal mode.

23 minutes ago, trurl said:

Start the array in normal (not maintenance mode) and post new diagnostics.

I went to Tools and Diagnostics and downloaded from there.

Where are the ones you want?

I have not started in Maintenance mode, however since I no longer have a Parity drive, could that be the issue?

Edited March 28Mar 28 by lockrob2000
vanity

You are posting syslog. You posted diagnostics earlier in the thread. I want diagnostics.

Start the array in normal (not maintenance) mode, go to Tools - Diagnostics, download, and attach the complete zip to your next post.

6 minutes ago, lockrob2000 said:

I went to Tools and Diagnostics and downloaded from there

That may be, but you didn't post that download, you posted something different.

trying again

tower-diagnostics-20260328-1751.zip

Try again. You didn't get those diagnostics with the array started in normal mode.

Go to MAIN - Array Operation, START the array without checking the Maintenance mode box.

Then go to Tools - Diagnostics, download, and post that complete downloaded zip file.

crap

tower-diagnostics-20260328-1757.zip

All your data drives are mounting and show plenty of data. Parity has none of your data.

SMART for parity looks fine. You can rebuild parity to that same disk.

Stop the array, unassign parity, start the array with parity unassigned, stop the array, reassign parity, start the array to begin parity rebuild.

While parity is rebuilding, you should see lots of writes to parity, lots of reads from all other disks, zero errors in the ERRORS column for all disks.

If there are any problems, get diagnostics while it is still happening and post them.

wow, OK

will try that.

it is now rebuilding.

Thanks, you saved me a TON of $.

Now, if the server disconnects when rebuilding, will a restart pick up where it was interrupted?

On the disconnect side...Do you think that disabling the C-states in BIOS will help? (I read about that in the "FAQ for unRaid v.6".

What do you think happened to the data? and why on some restarts was the Docker tab no longer enabled?

Sorry for so many questions.

Edited March 28Mar 28 by lockrob2000
more questions

Do you have an attached keyboard and monitor? You can also get diagnostics from the command line if the webUI isn't working. You should definitely take care of those Ryzen things in that FAQ.

4 hours ago, lockrob2000 said:

if the server disconnects when rebuilding, will a restart pick up where it was interrupted?

If you have to reboot, rebuild will have to start over.

4 hours ago, lockrob2000 said:

What do you think happened to the data?

What data? All your data disks seem to have their data. Do you know of anything you are missing?

4 hours ago, lockrob2000 said:

why on some restarts was the Docker tab no longer enabled?

Not enough information to know. That's why we need diagnostics taken when the problem occurs.

10 hours ago, lockrob2000 said:

Now, if the server disconnects when rebuilding, will a restart pick up where it was interrupted?

The default Unraid behaviour is to restart any array operation if the system is rebooted before it finishes.

The Parity Check Tuning plugin does have an option to restart array operations from the point reached, but it will only do so if you manage a clean shutdown and this is unlikely to be achieved if you are getting a disconnecct.