Slow seek times lots of startup errors

[ali_v001]

Hey guys,
I'm seeing very large seek times when connecting to my smb share via windows and my system generally behaving really slow and I'm not sure why.
I have one pool with one dataset which I am sharing via smb.
For the hardware spec I'd expect this machine to be very stable / responsive.
I am receiving a lot of error messages on startup. The system does take a long while to start up also, I imagine due to all the error's I am getting. Also I am just noticing in the console these errors keep periodically happening.
I get no errors on hardware when looking at the hp ilo interface, but this doesnt check the disks attatched to the h220
Any help would be great. See console output and machine spec below.
Thanks

System info - FreeNAS-11.3-U4.1
Hardware - HP ml350p 6 x 1.2tb sas drives connected to a h220 host bus adapter - OS running on an ssd - 32gb ram - Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz

Code:

Aug 10 13:22:33 sr101 (da4:mps0:0:4:0): SCSI sense: RECOVERED ERROR asc:17,1 (Recovered data with retries)
Aug 10 13:22:33 sr101 (da4:mps0:0:4:0): Info: 0x86a90cf
Aug 10 13:22:33 sr101 (da4:mps0:0:4:0): Actual Retry Count: 24
Aug 10 13:22:38 sr101 (da4:mps0:0:4:0): READ(10). CDB: 28 00 0c 46 2b b0 00 00 08 00
Aug 10 13:22:38 sr101 (da4:mps0:0:4:0): CAM status: SCSI Status Error
Aug 10 13:22:38 sr101 (da4:mps0:0:4:0): SCSI status: Check Condition
Aug 10 13:22:38 sr101 (da4:mps0:0:4:0): SCSI sense: MEDIUM ERROR asc:11,0 (Unrecovered read error)
Aug 10 13:22:38 sr101 (da4:mps0:0:4:0): Info: 0xc462bb1
Aug 10 13:22:38 sr101 (da4:mps0:0:4:0): Actual Retry Count: 138
Aug 10 13:22:38 sr101 (da4:mps0:0:4:0): Error 5, Unretryable error
Aug 10 13:22:41 sr101 (da4:mps0:0:4:0): READ(10). CDB: 28 00 0c 48 02 20 00 00 20 00
Aug 10 13:22:41 sr101 (da4:mps0:0:4:0): CAM status: SCSI Status Error
Aug 10 13:22:41 sr101 (da4:mps0:0:4:0): SCSI status: Check Condition
Aug 10 13:22:41 sr101 (da4:mps0:0:4:0): SCSI sense: MEDIUM ERROR asc:11,0 (Unrecovered read error)
Aug 10 13:22:41 sr101 (da4:mps0:0:4:0): Info: 0xc480223

 

[Samuel Tai]

You've got a failing drive (da4) in your pool.

 

[ali_v001]

Thanks, do you think this is what's causing the slow seek times also? When browsing in windows i get a huge lag opening folders... more lag depending on the amount of data within. Also with the failing drive should I just pull and replace?

 

[Samuel Tai]

It's the likeliest explanation, that drive retries are the cause of your excessive latency.

 

[ali_v001]

It seems to have fixed all issues... I messed up the pool trying to find out what disk it was.. pulling drives etc.. stupidity on my part but it wasn't important data. Is there a more professional way in the future of identifying which drive to pull? Maybe this isn't a FreeNAS question but more the specific server?
All my caddys have diagnostic lights etc but the server didn't identify it as a failing disk. Any way to get FreeNAS to flag it with the diagnostic lights?

Is it usual behaviour for a failing disk to cause so much havoc... server was set up in raidz, so I would have thought having a redundant disk would allow the server to function as normal as far as speed/latency goes

I created a new pool set up a new share and am now saturating my 100mb/s connection which is great.

 

[Samuel Tai]

Storage->Disks will show the serial number of the drive. This is the fastest way to confirm you've pulled the correct drive.

 

[Yorick]

When in doubt, take the downtime and check the serial number of the drive to pull while the server is down. In future, label caddies with SNs so you can easily identify the right one.