I bought hardware before I ever found out about Unraid, so my set up is not recommended.

I had an issue where 2 drives in a hard drive cage, connected over usb were disabled. I removed the drives in the main page, started the array, stopped it and readded them, prompting obviously a data rebuild on the two drives. I do have 2 parity drives fortunately. The rebuild failed multiple times, no idea why, though I have been having issues with attempting to rename shares.

As my system has run flawlessly for months until I upgraded to 7.2.4 I downgraded to 7.2.3, hoping that might be the solution. But the rebuild was still failing and those drive being disabled again.

I checked the usb drive in windows - scan disk showed no issues. I changed the usb cable to a new one. Both the old and new one looked the same in a usb cable checker I have, but this checks what the cable is able to do, not that it is working properly.

I restarted the Unraid and using Dynamix Safe mode plugin, I disabled all plugins. VMS were disabled and for the most part docker were as well, but after a number of hours I did enable plugins - Emby only, due to friends and family complaints.

The data rebuild was started yesterday at about 9am and was reaching completion this evening, but the progress stalled at 95.5% It has been there for the last 3 hours. There is no disk activity anymore - emby is now not being used by anyone, so no reads or writes.

The log shows that ;

Mar 5 21:46:14 UnraidNAS kernel: md: sync done. time=132208sec

Mar 5 21:46:14 UnraidNAS kernel: md: recovery thread: exit status: 0

Which I Googled to mean that the reconstruct had completed with no errors, but the main page and dashboard still say 95.5%, meaning I am stuck - I would rather not "cancel" the rebuild, I cannot stop the array as there is a Parity Operation running, I did try to pause the rebuild, but that did nothing. The only thing I can think to do is shut the thing server down by the power button and hope that it does not demand a rebuild on restart, though it would obviously want to do a parity check.

Would anyone have any suggestions? Have I misunderstood the 2 log entires that I think indicate successful completion?

I'm running a diagnostics right now - it is taking a loooooong time on the shares, but I will post it when (if?) it completes, and also a screenshot of the log and the apparent progress of the rebuild. Sorry the screen grab is so blurred, not sure why.

Nope, diagnostics are stuck at my Paperless folder, which I recently tried to rename to paperless, but as changing the name to the same isn't allowed, even if there is a change in case, I tried to rename it to paperless1, then hoping to rename it to paperless.

I read on this forum that this would work, but apparently not for me☹️

The whole thing has gone unresponsive now. I tried to ssh restart the GUI, no success.

I guess a hard power button has become the only option - I tried to look at the Paperless/paperless/paperless1 name by trying to browse the flash drive and everything crashed. I tried a few browsers, no success.

Although all suggestions are now moot, cos I have run out of options, I am still going to post this.

Get Diagnostics after reboot, better than no diagnostics.

Setup Syslog Server.

Also see if you can get just the syslog

cp /var/log/syslog /boot/syslog.txt

Trurl and JorgeB, I do have a syslog server running, so I likely do have the info, but I would not know what logs to share?

It does seem my unraid crashes when trying to rename shares, even if (and I presume they should be?) Docker and VMs are not running.

I tried to rename shares before with no joy - getting complaints about invalid or illegal characters, and I gave up trying to fix them, but trying again breaks things a lot.

I tried renaming shares on the flash drive, that broke everything!

Renaming in the GUI /shares fails every time. Even shares I have deleted "come back", but JorgeB reckoned they were zfs datasets rather than folders.

How to tell them apart??

I can post logs if you let me know what to send - there are about 10, though obviously only a couple from the last few days. Will I post them here? Are they "anonymisied" ? Does that matter?

Post complete diagnostics zip

Zip syslog from syslog server that covers the time of the problems and post that too.

Thanks Trurl, I am attaching diagnostics. I have looked through my syslog share and I cannot find the relevant file- I rebooted not long after I started this thread- a powerbutton reboot as the UI was non responsive.

So the latest log starts on 5th March, just after or during the reboot. Nothing last modified near that time shows the relevant date.

I suspect what Stalled the rebuild was me messing with shares- I have tried to rename shares in the GUI- everyone says it can be done, but it doesn't work for me, or at least not easily. I have managed to rename 2, but their old names now show in my list of shares as well. I think they are zfs datasets, JorgeB said they were, but I have no idea how he knows that, and deleting them with an instruction he gave me didn't do anything. The reason I was trying to rename them is because of complaints about invalid characters in the name since 7.2.3 I think. I wish I had been advised about invalid names when I was naming them, but they seemed to be valid then. I think I started on 6.8 or 6.9, so I am relatively new to this.

unraidnas-diagnostics-20260307-2340.zip

Edited March 8Mar 8 by IanMcLeish
No attach option was showing until I edited

16 minutes ago, IanMcLeish said:

looked through my syslog share and I cannot find the relevant file

Post a screenshot of your Syslog Server settings.

Try removing or updating the system stats plugin to see if it stops spamming the log, and like trurl mentioned, let's see the settings for the syslog server

Spaces in the shares should not make the rebuild get stuck. How did I suggest renaming them? They are, in fact, zfs datasets, but you should still be able to rename them using the GUI