diagnosing a slow controller?

[cdoublejj]

is it possible to diagnose in such a way to find out if a controller(s) is causing a bottle neck?

 

 

 

 

 

EDIT maybe pre clear is hard on drives or certain types of SSDs??? you'd think all of the 2TB SSDs would be way faster than the 6TB HDDs?

Edited October 26, 2020 by cdoublejj

[JorgeB]

You can use the diskspeed docker.

[JorgeB]

Also, you shouldn't preclear SSDs.

[cdoublejj]

1 hour ago, JorgeB said:

Also, you shouldn't preclear SSDs.

oh? aside from taking off life span might that be why i saw an error and ran again the drive was fine? is there some info/reasoning behind this? like defragging SSDs back in the day would scramble stuff or cause excessive wear?

[JorgeB]

9 minutes ago, cdoublejj said:

aside from taking off life span

Because of this, also very usual for SSDs to have pending sectors or "surface" errors, they usually work or don't work.

[cdoublejj]

27 minutes ago, JorgeB said:

Because of this, also very usual for SSDs to have pending sectors or "surface" errors, they usually work or don't work.

good to know!

 

is the docker the only way to test drives? i've disabled docker to improve reliability and drop resource usage.

[JorgeB]

3 minutes ago, cdoublejj said:

is the docker the only way to test drives?

It's the esiest way, you can also assign them to the array, without parity and do a read check.

[cdoublejj]

42 minutes ago, JorgeB said:

It's the esiest way, you can also assign them to the array, without parity and do a read check.

also does 1118 relocated sectors sound right for an SSD or a bad SSD needing replaced? (or would that have to do with having ran a pre clear on it?)

[JorgeB]

Never a good sign, but might be OK for now, assuming it's not new.

[cdoublejj]

is the raw value the same as the actual amount of re allocated sectors?

[JorgeB]

Usually yes.