hypergolic

Here is the syslog. syslog

I enabled syslog and it locked up again today, thanks! tower-diagnostics-20230920-1705.zip

I upgraded the OS the other day and now I am having problems. The server has been unresponsive a couple of times and this morning docker was disabled. Should I roll back? tower-diagnostics-20230919-0831.zip

I am getting warnings about my docker disk utilization and I am trying to figure out what is causing it. I currently have the disk set to 50GB and it's saying 77% is being used and it's climbing. Here is the output of docker system df -v. I am not seeing it, am I missing something? https://pastebin.com/DD4kcTkM

Any idea why pihole is trying to bind to 0.0.0.0 when I am specifying a ServerIP?

Can anyone tell me why my plex server has become unreachable? Thanks! tower-diagnostics-20191117-0017.zip Plex Media Server.zip

Thanks again! I replaced the cable and no more errors.

That worked, thanks!

I see errors from ata7 in the syslog, how do I determine which disk it is? tower-diagnostics-20190217-1408.zip

Thanks for the help!

Here ya go! tower-diagnostics-20190101-0656.zip

I noticed the parity check that started this morning was running very slow, less than 1MB/s. Looking in syslog I assume this is the cause. How do I identify which disk this is? Thanks! Jan 1 05:59:43 Tower kernel: ata1.00: cmd 25/00:f8:38:99:7c/00:02:03:00:00/e0 tag 3 dma 389120 in Jan 1 05:59:43 Tower kernel: res 50/00:00:37:99:7c/00:00:03:00:00/40 Emask 0x10 (ATA bus error) Jan 1 05:59:43 Tower kernel: ata1.00: status: { DRDY } Jan 1 05:59:43 Tower kernel: ata1: hard resetting link Jan 1 05:59:48 Tower kernel: ata1: link is slow to respond, please be patient (ready=0) Jan 1 05:59:53 Tower kernel: ata1: COMRESET failed (errno=-16) Jan 1 05:59:53 Tower kernel: ata1: hard resetting link Jan 1 05:59:53 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jan 1 05:59:55 Tower kernel: ata1.00: configured for UDMA/33 Jan 1 05:59:55 Tower kernel: ata1: EH complete Jan 1 05:59:55 Tower kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x4890000 action 0xe frozen Jan 1 05:59:55 Tower kernel: ata1.00: irq_stat 0x0c400040, interface fatal error, connection status changed Jan 1 05:59:55 Tower kernel: ata1: SError: { PHYRdyChg 10B8B LinkSeq DevExch } Jan 1 05:59:55 Tower kernel: ata1.00: failed command: READ DMA EXT Jan 1 05:59:55 Tower kernel: ata1.00: cmd 25/00:d8:c8:e2:7c/00:02:03:00:00/e0 tag 6 dma 372736 in Jan 1 05:59:55 Tower kernel: res 50/00:00:c7:e2:7c/00:00:03:00:00/40 Emask 0x10 (ATA bus error) Jan 1 05:59:55 Tower kernel: ata1.00: status: { DRDY } Jan 1 05:59:55 Tower kernel: ata1: hard resetting link Jan 1 06:00:01 Tower kernel: ata1: link is slow to respond, please be patient (ready=0) Jan 1 06:00:05 Tower kernel: ata1: COMRESET failed (errno=-16) Jan 1 06:00:05 Tower kernel: ata1: hard resetting link Jan 1 06:00:05 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jan 1 06:00:07 Tower kernel: ata1.00: configured for UDMA/33 Jan 1 06:00:07 Tower kernel: ata1: EH complete Jan 1 06:00:07 Tower kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x4890000 action 0xe frozen Jan 1 06:00:07 Tower kernel: ata1.00: irq_stat 0x0c400040, interface fatal error, connection status changed Jan 1 06:00:07 Tower kernel: ata1: SError: { PHYRdyChg 10B8B LinkSeq DevExch } Jan 1 06:00:07 Tower kernel: ata1.00: failed command: READ DMA EXT Jan 1 06:00:07 Tower kernel: ata1.00: cmd 25/00:40:b0:14:7d/00:05:03:00:00/e0 tag 12 dma 688128 in Jan 1 06:00:07 Tower kernel: res 50/00:00:af:14:7d/00:00:03:00:00/40 Emask 0x10 (ATA bus error) Jan 1 06:00:07 Tower kernel: ata1.00: status: { DRDY } Jan 1 06:00:07 Tower kernel: ata1: hard resetting link Jan 1 06:00:13 Tower kernel: ata1: link is slow to respond, please be patient (ready=0) Jan 1 06:00:17 Tower kernel: ata1: COMRESET failed (errno=-16) Jan 1 06:00:17 Tower kernel: ata1: hard resetting link Jan 1 06:00:18 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jan 1 06:00:19 Tower kernel: ata1.00: configured for UDMA/33 Jan 1 06:00:19 Tower kernel: ata1: EH complete Jan 1 06:00:19 Tower kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x4890000 action 0xe frozen Jan 1 06:00:19 Tower kernel: ata1.00: irq_stat 0x0c400040, interface fatal error, connection status changed Jan 1 06:00:19 Tower kernel: ata1: SError: { PHYRdyChg 10B8B LinkSeq DevExch } Jan 1 06:00:19 Tower kernel: ata1.00: failed command: READ DMA EXT Jan 1 06:00:19 Tower kernel: ata1.00: cmd 25/00:40:20:58:7d/00:05:03:00:00/e0 tag 13 dma 688128 in Jan 1 06:00:19 Tower kernel: res 50/00:00:1f:58:7d/00:00:03:00:00/40 Emask 0x10 (ATA bus error)

I am using the sample files from the tutorial and I am getting a 401 error in the chrome console with a blank page, any suggestions? "GET https://mydomain.duckdns.org/sonarr 401 (Unauthorized)" Here is the part of my config: location /sonarr { include /config/nginx/proxy.conf; proxy_pass http://192.168.1.10:8989/sonarr; }

Yep dumb mistake, thanks for the help!

I followed the procedure below to replace some 2TB drives with an 8TB. https://wiki.lime-technology.com/Replacing_Multiple_Data_Drives_with_a_Single_Larger_Drive I now have the following errors: Share disk1 is identically named to a disk share Share disk2 is identically named to a disk share Edit: So I think my problem was using tab complete and I actually ran the command rsync -avX /mnt/disk1/ /mnt/disk4/ instead of rsync -avX /mnt/disk1/ /mnt/disk4, note the trailing slash. Any suggestions on how to correct this? Thanks!