cinereus

That's exactly what I'm asking. I want to know if it could cause any issues if an operation is already in progress. Sounds like it's safer to not try.

@itimpi Can you install this (and set it up to allow pauses) while a parity check or rebuild is in progress?

Anyone using henrywhitaker3/speedtest-tracker and finding it is stopping working more often now and not recovering? Five times in the last week for me. Nothing ever in the logs and every time a simple docker restart fixes it.

I already posted a few versions above.

For future reference, I had to do an unclean shutdown, cancel the parity check then use the unsafe shrink array method. It seems the Unraid docs are out of date as the dd shrink array method is not reliable enough to use in practice.

No it's not mounted since the umount command. What can I do?

Yes. Exactly that. Even after terminating the dd script I am now seeing writes on the empty drive.

I have stopped Docker services but when I go to Open Files I get this:

Stop array button doesn't work. It just says this:

So it will be safe for me to cancel the dd command, stop array and go to a new config?

Do you think I could go straight to The "Remove Drives Then Rebuild Parity" Method now the disk have been taken off the array with umount. Thereby avoiding an unclear shutdown?

Does anyone from Unraid support have a better idea than unclear shutdown at this point?

Keeping parity is always safer. But how can I fix this without risking a reboot? How do I undo the umount command? And why does dd run so slowly to be unuseable?

The whole thing I'm trying to avoid is having to rebuild parity. That's why I chose the method that takes a lot longer but is a lot safer. I'm just trying to figure out how to stop the script that doesn't work from the unraid docs so I don't lose parity.

Diagnostics attached. The HDD has been performing normally for past 6+ months.fs-diagnostics-20250405-1558.zip