Device /dev/disk/by-partuuid/XXX is causing slow I/O on pool

lenard2000

Cadet
Joined
Oct 18, 2023
Messages
8
Hi All,

Recently I have been getting an error claiming that my APPs pool is experiencing Slow IO due to some issue. However, I am not sure what the issue is, and based on my research, it is usually related to SMR drives. However, my drive is not an HDD but an SSD, so I should not be having this problem.

I also saw that a couple of guys on reddit claimed that they had the same issue with SSD but no one replied.

Does anyone know what could be the issue?

Hardware:
QuestionHardware
Motherboard make and modelAsustek P7P55D-E LX
CPU make and modelIntel(R) Core(TM) i5 CPU 760 @ 2.80GHz
RAM quantity32GB DDR3
Hard drives, quantity, model numbers, and RAID configuration, including boot drivesSee the below.
Hard disk controllersNo External Hard Disk Controllers
Network CardsNo External Network Card.

Hard Disk Configuration:
BrandModelTypeSizeSpeedPoolDeploy Date
SeagateExos X18 Enterprise ClassHDD (CMR)16TB7200 RPMStorage 106/09/23
SeagateExos X18 Enterprise ClassHDD (CMR)16TB7200 RPMStorage 1
CrucialBX500SSD1TB6GB/sApps04/09/23
CrucialBX500SSD1TB6GB/sNot Assigned Yet
GoodRamSSD120GBBoot
CrucialBX500SSD240GB6GB/sBoot11/11/2023
CrucialBX500SSD2TB6GB/sTemp11/11/2023

I look forward to any feedback that anyone can give me :)
 

lenard2000

Cadet
Joined
Oct 18, 2023
Messages
8
Code:
WARNING
Device /dev/disk/by-partuuid/69040800-2564-4c22-b837-79db52ad3c18 is causing slow I/O on pool Apps.
2023-11-13 14:54:18 (Europe/Malta)
 

Attachments

  • Screenshot 2023-11-13 145134.png
    Screenshot 2023-11-13 145134.png
    18.4 KB · Views: 132

lenard2000

Cadet
Joined
Oct 18, 2023
Messages
8
Following up on here. Any ideas of what the issue could be? Any feedback will go a long way in troubleshooting the issue.
Weirdly enough, the error went away on its own but it comes back from time to time.
 

NugentS

MVP
Joined
Apr 16, 2020
Messages
2,947
[Guess] I wonder if you have written a lot of data to the disks, exhausted any cache so the SSD performance has hit its brick wall. You would then have to wait for the SSD to sort itself out and restore performance, until you exhaust it again.

This would be an issue with consumer SSD's, of all sorts. As they lie about their performance. Enterprise SSD's are more honest.

I had the same issue on a pool of cheapish NVMe drives (since removed) yet my pool of Intel DC SSD's (SATA) have no issue.
 
Top