Tracking down IOwait cause

[DanielPT]

13 minutes ago, JorgeB said:

And the torrents/downloads are also going to exclusive shares?

Nope becurse downloads are also on the array

[JorgeB]

That can be the reason.

[habron]

I've been dealing with the same problem for several years now. In the past, it wasn't a big deal for me because I didn't need the parity, but now, more and more data are on the array that I don't want to lose.

 

I'm not able to create a parity disk, even when I shut down Docker, remove the VM Manager, delete all plugins, and so on. First, I assumed there was a problem with the motherboard (ASUS ROG STRIX B550-F GAMING), so I updated the motherboard and checked all settings twice. Second, I assumed it was the Adaptec HBA because it was mentioned somewhere that an old firmware on the controller (Adaptec ASR-71605) itself has a problem, so I updated the controller.

 

When I just copy files between the disks, I get 10 to 20% iowait.

 

Maybe the controller will not work with Unraid or needs another driver.

 

I assume none of you have solved the issue, right?

 

 

 

[itimpi]

11 minutes ago, habron said:

I'm not able to create a parity disk,

 

What happens when you try and do this?  This seems to be nothing to do with IOwait which is the subject of this thread.  Perhaps posting your diagnostics after an attempt will help us spot something?

[habron]

i assume, it's because of the iowait situation. because If I add a parity device and start syncing, the iowait increases just as when I copy files. When the iowait lasts too long, it causes read errors on a disk in the array (not always the same one not alwas at the same Time), and if there are too many errors, they occur on the parity disk, and Unraid disables it.

currently i switch from btrfs and xfs to zfs. if this is done by the next Days i will go deeper in to the issue. 

 

im tring now several things so if there strange things in the config dont wonder

inge-diagnostics-20240213-1639.zip

[JorgeB]

1 hour ago, habron said:

it causes read errors on a disk in the array (not always the same one not alwas at the same Time),

There's a know issue with that Adaptec controller, try the recently released v6.12.7-rc2, it should fix that issue, if it still fails post new diags after that.

[habron]

Quote

no its because because of the IOwait situation, if i put a Parity device in and Start Syncing the IOwait raises same as when i copy files. when the IOwait situation causes TO long 

 

Great support!!! Thanks, that helps. I was able to create the parity!❤️

IO wait is still a topic, but it's possible that the HDDs are the bottleneck.🤷‍♂️

Edited February 15 by habron

[JorgeB]

Some i/o wait can be normal, you can also take a look at turbo write for better write performance at the expense of all disks spinning up for writes.

[robo22]

Nice to know I'm not alone in this issue with the IOwait time going up super high and slowing down the server.
I can attach my diagnostic log here if it might help, or post it in a new thread if that's preferred.