Running 7.2.3

I'm chasing a problem that I think is unrelated to what I was actually doing. I was trying to get a movie on jellyfin to play on my tv and while just playing around in the settings, I turned on trickplay. Server went to an absolute snail pace and I eventually got it all turned off.

However, even with all dockers turned off it remains slow. I pulled a syslog and it says this. quick google says this is a drive failure but all the drives according to the gui are good. I'm not sure how to proceed.

screenshot as well so easily pick out the errors. Thanks in advance for any help.

Feb 17 14:37:34 ZefyServer kernel: sd 7:0:2:0: [sdh] tag#1839 CDB: opcode=0x28 28 00 05 4b 6a 00 00 04 00 00

Feb 17 14:37:34 ZefyServer kernel: I/O error, dev sdh, sector 88828416 op 0x0:(READ) flags 0x80700 phys_seg 128 prio class 2

Feb 17 14:37:34 ZefyServer kernel: sd 7:0:2:0: attempting task abort!scmd(0x00000000d02f8b4d), outstanding for 30095 ms & timeout 30000 ms

Feb 17 14:37:34 ZefyServer kernel: sd 7:0:2:0: [sdh] tag#1838 CDB: opcode=0x28 28 00 05 4b 66 00 00 04 00 00

Feb 17 14:37:34 ZefyServer kernel: scsi target7:0:2: handle(0x000a), sas_address(0x4433221106000000), phy(6)

Feb 17 14:37:34 ZefyServer kernel: scsi target7:0:2: enclosure logical id(0x500605b004eb3320), slot(5)

Feb 17 14:37:34 ZefyServer kernel: sd 7:0:2:0: No reference found at driver, assuming scmd(0x00000000d02f8b4d) might have completed

Feb 17 14:37:34 ZefyServer kernel: sd 7:0:2:0: task abort: SUCCESS scmd(0x00000000d02f8b4d)

Feb 17 14:37:34 ZefyServer kernel: sd 7:0:2:0: [sdh] tag#1838 UNKNOWN(0x2003) Result: hostbyte=0x03 driverbyte=DRIVER_OK cmd_age=30s

Feb 17 14:37:34 ZefyServer kernel: sd 7:0:2:0: [sdh] tag#1838 CDB: opcode=0x28 28 00 05 4b 66 00 00 04 00 00

Feb 17 14:37:34 ZefyServer kernel: I/O error, dev sdh, sector 88827392 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 2

Feb 17 14:37:34 ZefyServer kernel: sd 7:0:2:0: Power-on or device reset occurred

Feb 17 14:38:04 ZefyServer kernel: sd 7:0:2:0: attempting task abort!scmd(0x00000000be35322f), outstanding for 30443 ms & timeout 30000 ms

Feb 17 14:38:04 ZefyServer kernel: sd 7:0:2:0: [sdh] tag#1849 CDB: opcode=0x28 28 00 05 4b 4e 00 00 00 08 00

Feb 17 14:38:04 ZefyServer kernel: scsi target7:0:2: handle(0x000a), sas_address(0x4433221106000000), phy(6)

Feb 17 14:38:04 ZefyServer kernel: scsi target7:0:2: enclosure logical id(0x500605b004eb3320), slot(5)

Feb 17 14:38:04 ZefyServer kernel: sd 7:0:2:0: task abort: SUCCESS scmd(0x00000000be35322f)

Feb 17 14:38:04 ZefyServer kernel: sd 7:0:2:0: attempting task abort!scmd(0x0000000009909f79), outstanding for 30470 ms & timeout 30000 ms

Feb 17 14:38:04 ZefyServer kernel: sd 7:0:2:0: [sdh] tag#1848 CDB: opcode=0x28 28 00 05 4b 8a 48 00 03 b8 00

Feb 17 14:38:04 ZefyServer kernel: scsi target7:0:2: handle(0x000a), sas_address(0x4433221106000000), phy(6)

Feb 17 14:38:04 ZefyServer kernel: scsi target7:0:2: enclosure logical id(0x500605b004eb3320), slot(5)

Feb 17 14:38:04 ZefyServer kernel: sd 7:0:2:0: No reference found at driver, assuming scmd(0x0000000009909f79) might have completed

Feb 17 14:38:04 ZefyServer kernel: sd 7:0:2:0: task abort: SUCCESS scmd(0x0000000009909f79)

Feb 17 14:38:04 ZefyServer kernel: sd 7:0:2:0: [sdh] tag#1848 UNKNOWN(0x2003) Result: hostbyte=0x03 driverbyte=DRIVER_OK cmd_age=30s

Feb 17 14:38:04 ZefyServer kernel: sd 7:0:2:0: [sdh] tag#1848 CDB: opcode=0x28 28 00 05 4b 8a 48 00 03 b8 00

Feb 17 14:38:04 ZefyServer kernel: I/O error, dev sdh, sector 88836680 op 0x0:(READ) flags 0x80700 phys_seg 119 prio class 2

Feb 17 14:38:04 ZefyServer kernel: sd 7:0:2:0: attempting task abort!scmd(0x00000000c0d2b334), outstanding for 30470 ms & timeout 30000 ms

Feb 17 14:38:04 ZefyServer kernel: sd 7:0:2:0: [sdh] tag#1847 CDB: opcode=0x28 28 00 05 4b 86 48 00 04 00 00

Feb 17 14:38:04 ZefyServer kernel: scsi target7:0:2: handle(0x000a), sas_address(0x4433221106000000), phy(6)

Feb 17 14:38:04 ZefyServer kernel: scsi target7:0:2: enclosure logical id(0x500605b004eb3320), slot(5)

Feb 17 14:38:04 ZefyServer kernel: sd 7:0:2:0: No reference found at driver, assuming scmd(0x00000000c0d2b334) might have completed

Feb 17 14:38:04 ZefyServer kernel: sd 7:0:2:0: task abort: SUCCESS scmd(0x00000000c0d2b334)

Feb 17 14:38:04 ZefyServer kernel: sd 7:0:2:0: [sdh] tag#1847 UNKNOWN(0x2003) Result: hostbyte=0x03 driverbyte=DRIVER_OK cmd_age=30s

Feb 17 14:38:04 ZefyServer kernel: sd 7:0:2:0: [sdh] tag#1847 CDB: opcode=0x28 28 00 05 4b 86 48 00 04 00 00

Feb 17 14:38:04 ZefyServer kernel: I/O error, dev sdh, sector 88835656 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 2

Feb 17 14:38:04 ZefyServer kernel: sd 7:0:2:0: attempting task abort!scmd(0x0000000067ee0bee), outstanding for 30470 ms & timeout 30000 ms

Feb 17 14:38:04 ZefyServer kernel: sd 7:0:2:0: [sdh] tag#1846 CDB: opcode=0x28 28 00 05 4b 82 48 00 04 00 00

Feb 17 14:38:04 ZefyServer kernel: scsi target7:0:2: handle(0x000a), sas_address(0x4433221106000000), phy(6)

Feb 17 14:38:04 ZefyServer kernel: scsi target7:0:2: enclosure logical id(0x500605b004eb3320), slot(5)

Feb 17 14:38:04 ZefyServer kernel: sd 7:0:2:0: No reference found at driver, assuming scmd(0x0000000067ee0bee) might have completed

Feb 17 14:38:04 ZefyServer kernel: sd 7:0:2:0: task abort: SUCCESS scmd(0x0000000067ee0bee)

Feb 17 14:38:04 ZefyServer kernel: sd 7:0:2:0: [sdh] tag#1846 UNKNOWN(0x2003) Result: hostbyte=0x03 driverbyte=DRIVER_OK cmd_age=30s

Feb 17 14:38:04 ZefyServer kernel: sd 7:0:2:0: [sdh] tag#1846 CDB: opcode=0x28 28 00 05 4b 82 48 00 04 00 00

Feb 17 14:38:04 ZefyServer kernel: I/O error, dev sdh, sector 88834632 op 0x0:(READ) flags 0x80700 phys_seg 128 prio class 2

Feb 17 14:38:04 ZefyServer kernel: sd 7:0:2:0: attempting task abort!scmd(0x00000000cc169dfc), outstanding for 30470 ms & timeout 30000 ms

Feb 17 14:38:04 ZefyServer kernel: sd 7:0:2:0: [sdh] tag#1845 CDB: opcode=0x28 28 00 05 4b 7e 48 00 04 00 00

Feb 17 14:38:04 ZefyServer kernel: scsi target7:0:2: handle(0x000a), sas_address(0x4433221106000000), phy(6)

Feb 17 14:38:04 ZefyServer kernel: scsi target7:0:2: enclosure logical id(0x500605b004eb3320), slot(5)

Feb 17 14:38:04 ZefyServer kernel: sd 7:0:2:0: No reference found at driver, assuming scmd(0x00000000cc169dfc) might have completed

Feb 17 14:38:04 ZefyServer kernel: sd 7:0:2:0: task abort: SUCCESS scmd(0x00000000cc169dfc)

Feb 17 14:38:04 ZefyServer kernel: sd 7:0:2:0: [sdh] tag#1845 UNKNOWN(0x2003) Result: hostbyte=0x03 driverbyte=DRIVER_OK cmd_age=30s

Feb 17 14:38:04 ZefyServer kernel: sd 7:0:2:0: [sdh] tag#1845 CDB: opcode=0x28 28 00 05 4b 7e 48 00 04 00 00

Feb 17 14:38:04 ZefyServer kernel: I/O error, dev sdh, sector 88833608 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 2

Feb 17 14:38:04 ZefyServer kernel: sd 7:0:2:0: attempting task abort!scmd(0x00000000817aae0b), outstanding for 30470 ms & timeout 30000 ms

i started looking at my drives and it seems like maybe it's the cache drive. It wouldn't finish a smart test. it's a intel 512gb ssd. has this reallocated sector count error but it says old age under type? I'm not sure what this means but i'm working under the assumption that the drive needs attention.

Attach Diagnostics ZIP to your NEXT post in this thread.

1 minute ago, trurl said:

Attach Diagnostics ZIP to your NEXT post in this thread.

zefyserver-diagnostics-20260217-1726.zip

Thanks for the help

You rebooted before taking the diagnostics so can't see what happened before.

Your appdata, domains, and system shares are configured to be moved to the array. And system has some files already on the array.

Ideally, these shares would have all files on cache or other pool, with nothing on the array, so Docker/VM will perform better, and so array disks can spin down since these files are always open. These shares should have Mover action:array->cache, you have them cache->array.

Nothing can move open files so you have to disabled Docker and VM Manager in Settings to get those system files off the array.

When you took those diagnostics, it was running a parity check, which will affect performance of array access.

Feb 17 16:56:19 ZefyServer emhttpd: unclean shutdown detected
...
Feb 17 16:56:34 ZefyServer kernel: mdcmd (36): check correct
Feb 17 16:56:34 ZefyServer kernel: md: recovery thread: check P ...

SMART test for cache didn't fail, it was interrupted. Check connections and try again.

10 minutes ago, trurl said:

You rebooted before taking the diagnostics so can't see what happened before.

Your appdata, domains, and system shares are configured to be moved to the array. And system has some files already on the array.

Ideally, these shares would have all files on cache or other pool, with nothing on the array, so Docker/VM will perform better, and so array disks can spin down since these files are always open. These shares should have Mover action:array->cache, you have them cache->array.

Nothing can move open files so you have to disabled Docker and VM Manager in Settings to get those system files off the array.

When you took those diagnostics, it was running a parity check, which will affect performance of array access.

Feb 17 16:56:19 ZefyServer emhttpd: unclean shutdown detected
...
Feb 17 16:56:34 ZefyServer kernel: mdcmd (36): check correct
Feb 17 16:56:34 ZefyServer kernel: md: recovery thread: check P ...

SMART test for cache didn't fail, it was interrupted. Check connections and try again.

Thanks. Yes I rebooted to check my connections before you posted. Unfortunately I didn't have any diagnostic logs from before restarting, only those screenshots. I was working under the assumption that the cache was bad so i was setting everything to move to the array such that I can replace the cache and move it all back to the new cache drive. I was following this guys instructions.

https://youtu.be/1orfWpekkqw?si=VSRzoi98Gmxrhemf&t=621

It is normally setup exactly how you describe it should be. I have since changed it back after checking my connections. I just disconnected and reconnected the sata cable on the drive. However I would like to make sure that nothing is wrong otherwise. After the reboot, it automatically started running a parity check. Even with that going it is considerably faster than it was idling when i made this thread. Something was definitely wrong before this, just want to cover my bases. I setup appdata backup directly to the array in case my cache does fail.

This is how it is normally setup and the way it is currently

Edited February 18Feb 18 by Zefy