Xorius

For some reason, the exact same command I used earlier works fine now. The only difference I noticed is that the previous time the disk was asleep and had to be waken up. Maybe that caused som kind of confusion.

I did try it with 4k earlier, but parity was still being written from the previous operation, got tired of waiting. it went quite quickly up to 1GB, then basically stopped.

Yeah. The question is why it is so slow though. I ran these commands, I suppose they are correct: umount /mnt/disk26 truncate -s 400M /tmp/26mini.img mkfs.xfs -f /tmp/26mini.img > /dev/null mount /tmp/26mini.img /mnt/disk26 dd if=/dev/zero of=/dev/md26p1 bs=1M status=progress I was thinking of just saying "screw you" to my server and stop the array, remove the disks I was gonna remove and let parity recalc, but I am afraid it may do that in this speed as well.

Thanks I will try that, but my array is still doing parity calculations from my previous try and it's been over an hour now since I cancelled it.

I have sent the diagnostics to you, @JorgeB .

I am generating the diagnostics right now. Takes a while with many disks, Nothing was accessing the array. No disk errors. Nothing unusual in syslog...

I am trying to downsize my array and remove some disks. I am following the guide from https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/array-configuration/#removing-disks for removal without losing parity. I have done the umount, truncate, mkfs, and mount commands and the gui now shows a 400MB empty disk like it should. When i started the dd command it was super slow. when I cancelled the command in the console it had done 1GB in 10 minutes and in the web gui it shows (with reconstruct write turned on) about 550-600 KB/s writes on the parity drives and the one I am removing and about 60-70 KB/s reads on all disks, including the one I am removing. It has now been quite a while since I cancelled the dd command and I am waiting to try again with oflag=direct, as per suggestions i found, but the array is still doing its extremely slow operations. Any suggestions?

I will verify it before I start but it has never been anything but correct up until now so I am feeling confident it won't fail now. Thank you!

Of course. My mistake. But just to make sure, I will during this whole process have at least one valid parity drive at all times?

I want to reorder my disks to move the smallest to the end to so I can in the future move towards bigger and fewer disks and not have any gaps in the numbering (yes, OCD...). I have dual parity at the moment and I know that the second parity drive will be invalid if I reorder the disks, but the first one should still be fine. If I want to have the security of the first parity drive present while rebuilding the second parity drive, can I do it like this: Stop the array New config, put the disks in the order I want but leave the second parity blank Start the array and tick that parity is valid (only one parity drive at the moment) Stop the array Add the second parity drive back Start the array and DON'T tick that parity is valid Will this only recalculate parity for P2 when I start the array at #6, or will it recalculate for both disks and leave me without parity at all for quite a lot of hours?