nzbget locks up and pauses alot

[cutch3233]

So i have a Dell T620 with 12 total physical coes and when i use nzbget my system comes to a crawl and pauses the download and takes a few min to catch up.  I see in htop cpu spike but the gui % is way higher.  Here is my logs i am lost on what else it could be.

 

tower-diagnostics-20230623-1844.zip

[michaelmurfy]

This sounds like drive thrashing. I also note your SSD may be on its way out:
 

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     PO-R--   100   100   050    -    0
  9 Power_On_Hours          -O--C-   100   100   000    -    39149
 12 Power_Cycle_Count       -O--C-   100   100   000    -    188
168 SATA_Phy_Error_Count    -O--C-   100   100   000    -    0
170 Bad_Blk_Ct_Lat/Erl      PO----   086   086   010    -    21/269
173 MaxAvgErase_Ct          -O--C-   100   100   000    -    374 (Average 347)
192 Unsafe_Shutdown_Count   -O--C-   100   100   000    -    145
194 Temperature_Celsius     PO---K   067   067   000    -    33 (Min/Max 33/33)
218 CRC_Error_Count         PO-R--   100   100   050    -    11
231 SSD_Life_Left           PO--C-   100   100   000    -    65
241 Lifetime_Writes_GiB     -O--C-   100   100   000    -    58316
                            ||||||_ K auto-keep
                            |||||__ C event count
                            ||||___ R error rate
                            |||____ S speed/performance
                            ||_____ O updated online
                            |______ P prefailure warning

 

With my configuration I personally use SABnzbd as it is maintained (NZBGet has been abandoned by its developer) and find it runs quite a bit better + also have 2x cache drives in a pool and download to that initially. This helps prevent slowdowns during NZB processing.

But totally get your data off that SSD and replace it ASAP. It may not fail just yet, but when they do they'll fail hard and fast. That drive has done pretty well.

[cutch3233]

On 6/23/2023 at 9:44 PM, michaelmurfy said:

This sounds like drive thrashing. I also note your SSD may be on its way out:
 

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     PO-R--   100   100   050    -    0
  9 Power_On_Hours          -O--C-   100   100   000    -    39149
 12 Power_Cycle_Count       -O--C-   100   100   000    -    188
168 SATA_Phy_Error_Count    -O--C-   100   100   000    -    0
170 Bad_Blk_Ct_Lat/Erl      PO----   086   086   010    -    21/269
173 MaxAvgErase_Ct          -O--C-   100   100   000    -    374 (Average 347)
192 Unsafe_Shutdown_Count   -O--C-   100   100   000    -    145
194 Temperature_Celsius     PO---K   067   067   000    -    33 (Min/Max 33/33)
218 CRC_Error_Count         PO-R--   100   100   050    -    11
231 SSD_Life_Left           PO--C-   100   100   000    -    65
241 Lifetime_Writes_GiB     -O--C-   100   100   000    -    58316
                            ||||||_ K auto-keep
                            |||||__ C event count
                            ||||___ R error rate
                            |||____ S speed/performance
                            ||_____ O updated online
                            |______ P prefailure warning

 

With my configuration I personally use SABnzbd as it is maintained (NZBGet has been abandoned by its developer) and find it runs quite a bit better + also have 2x cache drives in a pool and download to that initially. This helps prevent slowdowns during NZB processing.

But totally get your data off that SSD and replace it ASAP. It may not fail just yet, but when they do they'll fail hard and fast. That drive has done pretty well.

replaced the drive and things are away better