Slow performance, bad hardware or config?


Recommended Posts

 

I don't know what's going on but I recently doubled my RAM but also switched to Radarr and updated a large chunk of my library.

 

However iv noticed sabnzbd is much slower to extract. All containers hang, cpu going Crazy.

 

I haven't seen any disk errors I know my cache disk has been getting full due to small size it surely that shouldnt stop plex etc from working.

 

Would someone mind having a look at my diagnostics and see if anything stands out please.

 

Thanks

 

Sent from my SM-G973F using Tapatalk

 

 

 

http://cloud.tapatalk.com/s/5cf0374445f87/server-diagnostics-20190530-1952.zip

Link to comment

Just a quick overview do you use tmux regularly? Also the mover is erroring many times on idiots abroad s2e5 file does not exist on cache, that could explain CPU freak out

Also you may be feeling the effects of the Spectre patch.

Something also seems off on your spindown rules

Just a brief pass will dive in more

 

Edited by Fiservedpi
New info has come to light
  • Like 1
Link to comment
Just a quick overview do you use tmux regularly? Also the mover is erroring many times on idiots abroad s2e5 file does not exist on cache, that could explain CPU freak out
Also you may be feeling the effects of the Spectre patch.
Something also seems off on your spindown rules
Just a brief pass will dive in more
 
Thanks for that! Not sure what tmux is if I'm honest... Also idiot abroad makes sense it's a show on plex and my transcode folder used to be set to my SSD cache drive but I have now changed it to Transcode to RAM.

Just checked the firmware on bios and it looks like its outdated so likely not even got the spectre patch. I have downloaded the latest bios from Supermicro and will install that this week.



Sent from my SM-G973F using Tapatalk

Link to comment

Ok sounds good ill keep thumbing through, whats the logic behind a spin down of -1? i ask because your shares are spread across many drives except for one so that could cause slowness in sab n plex when it has to wake up the disk to get the media. Take a look at your drives and the "use cache" section some do some don't its my understanding "Cache Preferred" is the way to go, they all should use the cache and the mover moves from cache nightly to the array.

 

Edited by Fiservedpi
Link to comment
ok sounds good ill keep thumbing through, whats the logic behind a spin down of -1? i ask because your shares are spread across many drives except for one so that could cause slowness in sab n plex when it has to wake up the disk to get the media 
 
Spin down time should be set to unraid default. Iv never changed it

Sent from my SM-G973F using Tapatalk

Link to comment
34 minutes ago, bally12345 said:

Spin down time should be set to unraid default. Iv never changed it emoji848.png

Sent from my SM-G973F using Tapatalk
 

you have a plugin handling that lol, dynamix.s3.sleep, and your drives are sleeping as fast as every 1.5hr

Edited by Fiservedpi
Link to comment
2 minutes ago, bally12345 said:

I have removed that plugin, quickly started looking at the share settings, appdata on SSD cache is set to "Preferred" I am assuming this should be set to "Only"

 

I have attached Diagnostics from today

server-diagnostics-20190604-1338.zip 116.53 kB · 0 downloads

no preferred this way your media will download and unpack on cache "quickly" then at night moved to the less volatile array  

Link to comment
1 hour ago, bally12345 said:

I have removed that plugin, quickly started looking at the share settings, appdata on SSD cache is set to "Preferred" I am assuming this should be set to "Only"

 

I have attached Diagnostics from today

server-diagnostics-20190604-1338.zip 116.53 kB · 0 downloads

This is new and was not present in your previous logs and MAY be concerning or maybe not, your smart report is clear, but this in the logs is something you may want to research, and run an extended test, its saying there is a bad sector across multiple drives,  MAKE A BACKUP NOW!! OF IMPORTANT INFO, CA AUTO BACKUP

after a little research this may have something to do with spindown dont panic

How is sab and docker working?

also check the cables on crucial ssd ```174 Unexpect_Power_Loss_Ct  -O--CK   100   100   000    -    42```

 

Jun  4 14:30:20 Server kernel: sd 5:0:1:0: [sdc] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00
Jun  4 14:30:20 Server kernel: sd 5:0:1:0: [sdc] tag#1 CDB: opcode=0x88 88 00 00 00 00 01 d1 c0 be 00 00 00 00 08 00 00
Jun  4 14:30:20 Server kernel: print_req_error: I/O error, dev sdc, sector 7814036992
Jun  4 14:30:27 Server kernel: sd 5:0:3:0: [sde] tag#3 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00
Jun  4 14:30:27 Server kernel: sd 5:0:3:0: [sde] tag#3 CDB: opcode=0x88 88 00 00 00 00 01 d1 c0 be 00 00 00 00 08 00 00
Jun  4 14:30:27 Server kernel: print_req_error: I/O error, dev sde, sector 7814036992
Jun  4 14:30:35 Server kernel: sd 5:0:2:0: [sdd] tag#2 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00
Jun  4 14:30:35 Server kernel: sd 5:0:2:0: [sdd] tag#2 CDB: opcode=0x88 88 00 00 00 00 01 d1 c0 be 00 00 00 00 08 00 00
Jun  4 14:30:35 Server kernel: print_req_error: I/O error, dev sdd, sector 7814036992
Jun  4 14:30:43 Server kernel: sd 5:0:4:0: [sdf] tag#3 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00
Jun  4 14:30:43 Server kernel: sd 5:0:4:0: [sdf] tag#3 CDB: opcode=0x88 88 00 00 00 00 01 d1 c0 be 00 00 00 00 08 00 00
Jun  4 14:30:43 Server kernel: print_req_error: I/O error, dev sdf, sector 7814036992
Jun  4 14:31:01 Server kernel: sd 5:0:5:0: [sdg] tag#21 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00
Jun  4 14:31:01 Server kernel: sd 5:0:5:0: [sdg] tag#21 CDB: opcode=0x88 88 00 00 00 00 01 d1 c0 be 00 00 00 00 08 00 00
Jun  4 14:31:01 Server kernel: print_req_error: I/O error, dev sdg, sector 7814036992
Jun  4 14:31:01 Server kernel: sd 5:0:6:0: [sdh] tag#34 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00
Jun  4 14:31:01 Server kernel: sd 5:0:6:0: [sdh] tag#34 CDB: opcode=0x88 88 00 00 00 00 01 d1 c0 be 00 00 00 00 08 00 00
Jun  4 14:31:01 Server kernel: print_req_error: I/O error, dev sdh, sector 7814036992

 

Edited by Fiservedpi
Link to comment
19 minutes ago, bally12345 said:

Sab may have been the culprit extracting was super slow. But iv not checked back since defaulting the settings.

I will keep on eye on things and run extended test just in case.

Sent from my SM-G973F using Tapatalk
 

are you using a SATA AHCI controller?

Edited by Fiservedpi
Link to comment
FANTASTIC now we're gettin somewhere
 
Seems to be working better now, films were added to Plex and nothing seemed to hang. I don't know if it was removing that plugin or defaulting the settings in sabnzbd or a combo of both but definitely better.

Will keep checking and update bios on weekend with a bit of luck.

Sent from my SM-G973F using Tapatalk

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.