I'm using the script but it's been running at 4-5 MB/s overnight (and this is a 20 TB drive!)

 

Is there any way to abort the script as it will take far too long like this (almost 2 months).

On 10/7/2022 at 12:56 AM, stereopine said:

clear a 1TB SSD

SSDs in the parity array cannot be trimmed, and can only be written at parity speed. Usually you would put SSDs in a pool.

 

I always recommend to just remove the disk with New Config and rebuild parity.

11 hours ago, cinereus said:

I'm using the script but it's been running at 4-5 MB/s overnight (and this is a 20 TB drive!)

 

Is there any way to abort the script as it will take far too long like this (almost 2 months).

Now down to 1.0 MB/s. Any ideas?

That script is known to not work correctly with current releases, you can still do it manually:

 

https://forums.lime-technology.com/topic/61614-shrink-array-question/?tab=comments#comment-606335

55 minutes ago, JorgeB said:

That script is known to not work correctly with current releases, you can still do it manually:

 

https://forums.lime-technology.com/topic/61614-shrink-array-question/?tab=comments#comment-606335

I'm on 6.9.2 which is the same version I used it successfully with last time. It's just a dd command, I don't get why it is running at 1 MB/s.

 

How do I cancel it now it is running? 

Edited April 4, 20251 yr by cinereus

Not sure, never used, it, if nothing else, a reboot shoudl do it.

The script is running at 1 MB/s on a 20 TB drive. Does anyone know how to cancel it as it's clearly not working correctly?

5 minutes ago, JorgeB said:

Not sure, never used, it, if nothing else, a reboot shoudl do it.

Would really rather avoid a reboot. All it's done is:

 

umount /mnt/disk7 
dd bs=1M if=/dev/zero of=/dev/md7  status=progress

 

Can I format and remount in some way?

I'm shrinking an array on 6.9.2. Have done this with the clear array drive script before on this version so I don't need to rebuild parity.

 

However, this time the script isn't working. It has unmounted the drive with umount but dd is not working.

 

dd started at 4-5 MB/s but two days layers is now less than 1 MB/s (and this is a 20 TB drive!)

 

How can I safely abort the script?

The speed being that slow suggests a problem.

 

You are likely to get better informed feedback if you attach your system’s diagnostics (with everything in the one zip file) to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.

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

I have split your posts in various threads about this into this thread.

 

I recommend rebooting, then New Config without that disk and rebuild parity.

6 hours ago, trurl said:

I recommend rebooting, then New Config without that disk and rebuild parity.

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.

Edited April 5, 20251 yr by cinereus

18 minutes ago, cinereus said:

a lot safer.

debatable

24 minutes ago, trurl said:

debatable

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?

32 minutes ago, cinereus said:

Keeping parity is always safer.

What is debatable is whether or not the complications of this particular method is always safer. Remains to be seen whether unclean shutdown can be avoided.

12 hours ago, trurl said:

What is debatable is whether or not the complications of this particular method is always safer. Remains to be seen whether unclean shutdown can be avoided.

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

On 4/5/2025 at 12:09 PM, itimpi said:

The speed being that slow suggests a problem.

 

You are likely to get better informed feedback if you attach your system’s diagnostics (with everything in the one zip file) to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.

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?

1 minute ago, cinereus said:

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?

You can do that regardless of having an Unclean shutdown.   If you do get an Unclean Shutdown just cancel the resulting parity check on booting as you are about to rebuild parity anyway from the remaining drives.

54 minutes ago, itimpi said:

You can do that regardless of having an Unclean shutdown.   If you do get an Unclean Shutdown just cancel the resulting parity check on booting as you are about to rebuild parity anyway from the remaining drives.

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

yes

6 hours ago, trurl said:

yes

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

 

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

 

1 minute ago, cinereus said:

I have stopped Docker services

Just to clarify. Do you mean you went to Settings - Docker and set Enable Docker to No then hit the Apply button?