Hi All,

From what I've read, a clean reboot should not result in restarting data rebuild yet it did for me. I'm limping through diagnosing hardware issue while trying to get my raid parity back. To do this, my best bet is for me to pause every few percent of rebuild and do a clean reboot (if it were to not start over).

Steps:

Start data rebuild

Let it go a few percent

Pause data rebuild

Clean reboot

Result: on reboot, I had to manually start the array, rebuild started automatically, but, at 0%.

Diagnostics to follow.

Rebuild starting from 0 is expected if you reboot.

Interesting. Multiple sources say otherwise. Including some first hand accounts on Reddit saying they were surprised (and happy) that it didn't.

16 minutes ago, JRubenol said:

Interesting. Multiple sources say otherwise. Including some first hand accounts on Reddit saying they were surprised (and happy) that it didn't.

Restarting from the beginning is Unraid default behaviour for all array level operations.

If you have the Parity Check Tuning plugin installed then it has an option to try and restart array operations from point previously reached (as long as the shutdown was a clean one).

12 hours ago, itimpi said:

Restarting from the beginning is Unraid default behaviour for all array level operations.

If you have the Parity Check Tuning plugin installed then it has an option to try and restart array operations from point previously reached (as long as the shutdown was a clean one).

Unfortunately, it didn't work. My system locked up again during rebuild, on forced power off and power on, it started over again.

So it wasn't a clean reboot.

Attach Diagnostics ZIP to your NEXT post in this thread.

Setup syslog server

Got those logs....crashed again. Hopefully this helps in some way.

syslog-previous tower-diagnostics-20260405-2034.zip

I see that it looks like my parity drive is having some issues.....going to try to reseat it.....I only have single disk failure available now, and obviously with disk4 rebuilding, I could be in trouble. But, happy to take any suggestions as I limp through trying to recover from this.

I think you somehow got diagnostics before it had finished booting.

Post new diagnostics.

Here it is.

tower-diagnostics-20260406-0739.zip

Parity looks OK now, but it looks like there may be some corruption on emulated disk4 even though it is mounted. And maybe a connection problem with disk2, which might be the cause.

Check connection on disk2 then post new diagnostics before restarting the rebuild.

I just took out each drive, used compressed air to clean it all out (there was a wire that was pinched a bit....) and put the drives back in. I'm booting up right now. Question is, as soon as I start the array, the drive rebuild will start. You're asking bfor a diagnostics before that. So, just to clarify, you want one before I start the array?

Set the emulated disk4 to not assigned, start the array, post new diagnostics. Then we can see if emulated disk4 is still logging any corruption before proceeding with rebuild.

Working on this now, possibly side issue happening in that it's showing an unclean shutdown despite the fact that I did a clean shutdown through the GUI....separate post? I'm getting nervous I'm on the brink of losing data.

Here's that diagnostics with disk4 removed from the array. Also - do you have a "buy me a coffee" link or anything? You're spending a lot of time with me and I appreciate it.

tower-diagnostics-20260406-0911.zip

Edited April 6Apr 6 by JRubenol

That looks good so far. Reassign disk4 and start to rebuild

1 hour ago, trurl said:

That looks good so far. Reassign disk4 and start to rebuild

Going to run a long smart test first. It's running now. Going to take until 2am. Figured, might as well know where things stand completely. Will report back. Also, I'm still interested if you have a donation/buy me a coffee link.

If you click on your avatar/username at the upper right of the forum and select Account Settings, you can enable viewing signatures (sigs) in the forum, and also edit your own sig. Signatures are a common feature of forums. It is a small bit of text appended to the bottom of each of your posts.

Here is one thing from my sig:

Donations

Good news is I got a very clean smartctrl test on it. Rebuilding now....if this fails, I'm starting to run out of ideas of what it could be. I have syslog server up and running so we'll see.

hard_drive.txt

And, another crash (not during rebuild, but, during moving files). Common theme seems to be SMB stuff mixed with other things. Lots attached. Diagnostics to follow.

syslog syslog-previous

Diagnostics attached.

tower-diagnostics-20260407-1516.zip

Those logs and SMART report are already included in Diagnostics.

Setup Syslog Server

2 hours ago, JRubenol said:

another crash (not during rebuild, but, during moving files)

Doesn't look like rebuild completed. Are you trying to write a lot to the server while it is rebuilding?

Just now, trurl said:

Those logs and SMART report are already included in Diagnostics.

Setup Syslog Server

Doesn't look like rebuild completed. Are you trying to write a lot to the server while it is rebuilding?

I thought the post (two ago) that has syslog and syslog-previous is a syslog server....I have that enabled and writing to my boot drive (USB). Those are the logs. I'm not writing that much, a bit but yes, the rebuild hasn't finished. I currently have it paused and the server is still crashing. My syslog screen is attached.

Yes, syslog-previous (included in diagnostics) are from syslog server writing to flash. If you want it to write to your Media share instead put localhost in Remote syslog server field.

8 minutes ago, JRubenol said:

not writing that much

You might try rebuild in Maintenance mode just to make sure nothing is accessing the server while rebuilding.

22 minutes ago, trurl said:

Yes, syslog-previous (included in diagnostics) are from syslog server writing to flash. If you want it to write to your Media share instead put localhost in Remote syslog server field.

You might try rebuild in Maintenance mode just to make sure nothing is accessing the server while rebuilding.

Sorry I'm not entirely tracking this. You said setup a syslog server (which I have done and it's writing to boot USB which I'm fine with). Did you get all of the logs you needed? I can try in Maintenance mode, that's something I haven't tried. I just had another freeze (not rebuilding, that was paused, I was moving some stuff via ssh and nextcloud was syncing some stuff over samba).

EDIT: I'd imagine you mean safe mode nor maintenance mode. Doesn't look like a rebuild will work in maintenance mode from what I'm reading.

Edited April 8Apr 8 by JRubenol