chesh

See attached. Doing this all from mobile, so excuse any misspellings. tower-diagnostics-20170325-1131.zip

I upgraded my unRAID from 6.3.0 to 6.3.1 a couple of weeks ago, but never rebooted. Fast forward to me going on vacation this week and then having a power outage back home while I'm away. Anyway, the person watching my house turned back on my server after getting home from work last night. Server boots and I can ssh into it, but the web UI, dockers, and no VMs are starting up. Anything I can do remotely, and if not, what should my next steps be when I get home? Thanks to anyone that can provide some help.

I'm now having issues connecting to rTorrent after an update today. I'm an UnRaid user that switched to this until SickRage figures out the issue w/ Deluge. Here is my log output after I deleted the image and rebuilt from template. ErrorWarningSystemArrayLogin 2017-03-10 10:28:07.479694 [info] Starting Supervisor... 2017-03-10 10:28:07,915 CRIT Set uid to user 0 2017-03-10 10:28:07,915 INFO Included extra file "/etc/supervisor/conf.d/rtorrent.conf" during parsing 2017-03-10 10:28:07,924 INFO supervisord started with pid 7 2017-03-10 10:28:08,927 INFO spawned: 'flood-script' with pid 119 2017-03-10 10:28:08,929 INFO spawned: 'start-script' with pid 120 2017-03-10 10:28:08,931 INFO spawned: 'rtorrent-script' with pid 121 2017-03-10 10:28:08,933 INFO spawned: 'rutorrent-script' with pid 122 2017-03-10 10:28:08,936 INFO spawned: 'privoxy-script' with pid 123 2017-03-10 10:28:08,938 DEBG 'flood-script' stdout output: [info] Flood not enabled, skipping starting Flood Web UI 2017-03-10 10:28:08,938 INFO success: flood-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2017-03-10 10:28:08,939 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2017-03-10 10:28:08,939 INFO success: rtorrent-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2017-03-10 10:28:08,940 INFO success: rutorrent-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2017-03-10 10:28:08,940 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2017-03-10 10:28:08,940 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 46963474132792 for <Subprocess at 46963474323576 with name flood-script in state RUNNING> (stdout)> 2017-03-10 10:28:08,940 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 46963474132648 for <Subprocess at 46963474323576 with name flood-script in state RUNNING> (stderr)> 2017-03-10 10:28:08,941 INFO exited: flood-script (exit status 0; expected) 2017-03-10 10:28:08,941 DEBG received SIGCLD indicating a child quit 2017-03-10 10:28:08,941 DEBG 'start-script' stdout output: [info] VPN is enabled, beginning configuration of VPN 2017-03-10 10:28:08,943 DEBG 'rtorrent-script' stdout output: [info] rTorrent config file already exists, skipping copy 2017-03-10 10:28:08,945 DEBG 'rtorrent-script' stdout output: [info] VPN is enabled, checking VPN tunnel local ip is valid 2017-03-10 10:28:08,957 DEBG 'start-script' stdout output: [info] VPN default certs defined, copying to /config/openvpn/... 2017-03-10 10:28:08,964 DEBG 'start-script' stdout output: [info] VPN config file (ovpn extension) is located at /config/openvpn/openvpn.ovpn 2017-03-10 10:28:08,967 DEBG 'start-script' stderr output: dos2unix: converting file /config/openvpn/openvpn.ovpn to Unix format... 2017-03-10 10:28:09,039 DEBG 'start-script' stdout output: [info] Default route for container is 172.17.0.1 2017-03-10 10:28:09,045 DEBG 'start-script' stdout output: [info] Adding 8.8.8.8 to /etc/resolv.conf 2017-03-10 10:28:09,051 DEBG 'start-script' stdout output: [info] Adding 37.235.1.174 to /etc/resolv.conf 2017-03-10 10:28:09,056 DEBG 'start-script' stdout output: [info] Adding 8.8.4.4 to /etc/resolv.conf 2017-03-10 10:28:09,062 DEBG 'start-script' stdout output: [info] Adding 37.235.1.177 to /etc/resolv.conf 2017-03-10 10:28:09,073 DEBG 'start-script' stdout output: [info] Adding 192.168.1.0/24 as route via docker eth0 2017-03-10 10:28:09,074 DEBG 'start-script' stdout output: [info] ip route defined as follows... -------------------- 2017-03-10 10:28:09,075 DEBG 'start-script' stdout output: default via 172.17.0.1 dev eth0 172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.7 192.168.1.0/24 via 172.17.0.1 dev eth0 2017-03-10 10:28:09,075 DEBG 'start-script' stdout output: -------------------- 2017-03-10 10:28:09,083 DEBG 'start-script' stdout output: [info] iptable_mangle support detected, adding fwmark for tables 2017-03-10 10:28:09,108 DEBG 'start-script' stdout output: [info] Docker network defined as 172.17.0.0/16 2017-03-10 10:28:09,165 DEBG 'start-script' stdout output: [info] iptables defined as follows... -------------------- 2017-03-10 10:28:09,166 DEBG 'start-script' stdout output: -P INPUT DROP -P FORWARD ACCEPT -P OUTPUT DROP -A INPUT -i tun0 -j ACCEPT -A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT -A INPUT -i eth0 -p udp -m udp --sport 1198 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --dport 9080 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --sport 9080 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --dport 9443 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --sport 9443 -j ACCEPT -A INPUT -s 192.168.1.0/24 -i eth0 -p tcp -m tcp --dport 5000 -j ACCEPT -A INPUT -s 192.168.1.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -j ACCEPT -A INPUT -p udp -m udp --sport 53 -j ACCEPT -A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT -A INPUT -i lo -j ACCEPT -A OUTPUT -o tun0 -j ACCEPT -A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT -A OUTPUT -o eth0 -p udp -m udp --dport 1198 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --dport 9080 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 9080 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --dport 9443 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 9443 -j ACCEPT -A OUTPUT -d 192.168.1.0/24 -o eth0 -p tcp -m tcp --sport 5000 -j ACCEPT -A OUTPUT -s 172.17.0.0/16 -d 192.168.1.0/24 -o eth0 -p tcp -j ACCEPT -A OUTPUT -p udp -m udp --dport 53 -j ACCEPT -A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT -A OUTPUT -o lo -j ACCEPT 2017-03-10 10:28:09,166 DEBG 'start-script' stdout output: -------------------- 2017-03-10 10:28:09,167 DEBG 'start-script' stdout output: [info] Starting OpenVPN... 2017-03-10 10:28:09,185 DEBG 'start-script' stdout output: [info] OpenVPN started 2017-03-10 10:28:11,175 DEBG 'rtorrent-script' stdout output: [info] rTorrent not running [info] rTorrent listening interface IP 0.0.0.0 and VPN provider IP 10.16.10.6 different, marking for reconfigure 2017-03-10 10:28:11,176 DEBG 'privoxy-script' stdout output: [info] Configuring Privoxy... 2017-03-10 10:28:11,450 DEBG 'privoxy-script' stdout output: [info] All checks complete, starting Privoxy... 2017-03-10 10:28:11,451 DEBG 'privoxy-script' stderr output: 2017-03-10 10:28:11.451 2abda0ef0e00 Info: Privoxy version 3.0.26 2017-03-10 10:28:11.451 2abda0ef0e00 Info: Program name: /usr/bin/privoxy 2017-03-10 10:28:17,888 DEBG 'rtorrent-script' stdout output: [info] Removing any rtorrent session lock files left over from the previous run... 2017-03-10 10:28:17,892 DEBG 'rtorrent-script' stdout output: [info] Attempting to start rTorrent... 2017-03-10 10:28:17,895 DEBG 'rtorrent-script' stdout output: Script started, file is /home/nobody/typescript 2017-03-10 10:28:17,921 DEBG 'rtorrent-script' stdout output: Script done, file is /home/nobody/typescript

Know where to find SickRage's in-depth changelog? All I could seem to find was last updated in February.

So, after yesterdays update to both SickRage and Deluge, SickRage is no longer able to connect to Deluge. Both are using binhex's version of the containers. Anyone else seeing "2017-03-08 15:53:18 Thread-26 :: [41d7d9d] Request failed: No JSON object could be decoded" when SickRage tries to send a torrent over to Deluge since the update? Was hoping the Deluge container update today would have fixed the issue, but no luck. I've already tried destroying the dockers and then rebuilding them from template. Haven't gone the full nuclear option yet and blown away all dockers, docker.img file, and rebuild, but I think this is more of an API issue between programs and not the dockers themselves. Let me know if it's the software or the dockers, or my stuff is just borked. Thanks!

New update out 3 days ago. Your docker repository auto update script not working? Sickrage has had some updates out for a couple of days too. Just a head up.

You do realize you need 2 video cards if you want to pass through to a VM? unRAID needs a video input and the VM needs one. Doesn't matter if unRAID is using onboard or a installed card.

Do you have onboard video? Do you see the unRAID console on its display? What's the error code on the card in device manager?

Can you try installing the VNC driver as your first graphics card and the Nvidia as your second and see if your device manager is detecting the card? That's the first step I did in troubleshooting my issue. The final settings that worked for me were i440f-2.3 and OVMF. Word of warning to you, Win10 will eventually install an update that will bork your whole VM. I'm not sure which one it is, but last weekend I set up my first VM and ended up installing Win10 at least 13 times before I gave up and went back to 7. Haven't had an issue since.

K, already did that. Generally speaking with WOL in Windows, you have to set the NIC to be allowed to be woken up in the power management tab. Thought I might be missing something since the tab doesn't exist with the virtio drivers.

How does one turn on wake on lan for a network adapter in a VM? I'm currently using the NetKVM drivers for my Win10 VM and don't have a Power Management tab because of which (Win10 Pro x64). Should I change the adapter to a E1000 for the option to appear?

Ok, finally got it working. Here's what I did: Turned back on PCIe ACS override (not sure if needed, but my Plex users are getting sick of me rebooting constantly), moved the GTX 970 to PCIe slot 3 (2 would probably work also, but in my testing I had put in another video card to see if the IOMMU groups were an issue. Have since removed that card), and I installed Win10 as a OVMF/1440fx-2.3 VM. This finally detected the EVGA GTX 970 card correctly and let me install/initialize the drivers for it. Win10 is now at full resolution and working as it should. Next is to stress test w/ 3DMark and see what type of performance I'm getting.

Well, just rebuilt the VM w/ PCIe ACS override turned off (had it on during the first go round) and I'm still getting the Code 10 error on the video card. Just reviewed my mobo's manual, though, and it states that a graphics card should be installed in PCIe slot 2-4 and of course I have mine in PCIe slot 1. So, I'll be changing that as soon as my monthly parity check finishes sometime tonight. I'll report back if that fixed the issue or not. Thanks for the suggestion, gridrunner, but the power is connected and hooked up to my PS. So, unless I have a bad rail, I'm hoping that's not my issue.

Hi all, Just got my GTX 970 and setup a Win10 gaming VM. For some reason, my USB keyboard wouldn't work in console, so I initially had the VNC driver attached to the system to install Win10. Got Win10 all installed, installed my GTX 970, and then set it to passthrough w/ the Nvidia audio device. Well, I installed the drivers and now the GTX 970 won't start. It's still using the MS Display Driver, but when I check the properties of the GTX 970 or the HD Audio controller, I've got a code 10. I went to try to pass through the vbios, but after going through all EVGA Nvidia GTX 970's, it doesn't seem that there is one for my card (VEN_10DE&DEV_13C2&SUBSYS_39753842). It's weird that I'm getting output on my display, but for some reason the Nvidia drivers just don't want to load. I currently have append pcie_acs_override=downstream libata.force=noncq iommu=pt vfio_iommu_type1.allow_unsafe_interrupts=1 initrd=/bzroot in my syslinux.cfg, but only previously had append pcie_acs_override=downstream iommu=pt initrd=bzroot in there before, but still not working. My BIOS is OVMF and machine type of Q35-2.3. Here is my XML <domain type='kvm'> <name>Win10 Gaming</name> <uuid>392ae47d-5ac1-14d6-4c3a-454945b9df4a</uuid> <metadata> <vmtemplate name="Custom" icon="windows.png" os="windows"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>10</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='2'/> <vcpupin vcpu='2' cpuset='3'/> <vcpupin vcpu='3' cpuset='4'/> <vcpupin vcpu='4' cpuset='5'/> <vcpupin vcpu='5' cpuset='6'/> <vcpupin vcpu='6' cpuset='7'/> <vcpupin vcpu='7' cpuset='8'/> <vcpupin vcpu='8' cpuset='9'/> <vcpupin vcpu='9' cpuset='10'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-2.3'>hvm</type> <loader type='pflash'>/usr/share/qemu/ovmf-x64/OVMF-pure-efi.fd</loader> </os> <features> <acpi/> <apic/> <kvm> <hidden state='on'/> </kvm> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='10' threads='1'/> </cpu> <clock offset='localtime'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/disks/VM_SSD/Win10 Gaming/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='dmi-to-pci-bridge'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:d7:28:95'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/Win10 Gaming.org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x81' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x02' slot='0x05' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x81' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x02' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x046d'/> <product id='0xc52b'/> </source> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x02' slot='0x07' function='0x0'/> </memballoon> </devices> </domain> Attached is my diagnostics. In my signature is my current setup. Any help would be greatly appreciated!!! PS: I just ran DDU to try to uninstall/reinstall the drivers and I noticed that the MS Display Adapter was in a code 10 too (not sure if that was just reading that the Nvidia GTX 970 was in code 10 or what) tower-diagnostics-20160630-1903.zip

Ahh, I get it now. Didn't compare the 2. Huh, oh well, I'm sure it'll be committed to the master branch soon. Just annoying as since it's a DB update, it won't auto-update itself

In that link it's showing that there was an update on 6/14.

FYI: There's been an update out for SickRage for a couple of days and requires a new docker build due to it being a database change.

Version 0.9.17.2.2159 is now available

Ok, got this set up. I was overthinking the whole thing. If anyone else is looking for a decent guide to follow, see this: https://linuxpluse.wordpress.com/2013/12/21/sickbeard-couchpotato-deluge-plex/. It's for SickBeard and CouchPotato, but it's virtually the same setup. Leaving this post here instead of deleting it so if someone else is looking for a starts guide, they might find this post

Hey all, I'm starting to get my automation side of my media setup, and I'm wondering how everyone else does their workflow for auto torrent downloads. I've got DelugeVPN setup, I'm working on importing all of my media into SickRage, and I have installed the docker for CouchPotato. Now, I'm just trying to figure out how they all work together. I want to use a mixture of public and private trackers (TorrentLeech) and have stuff that is compressed, automatically uncompressed and put where it needs to go. Once I have this portion of my dockers figured out, I can finally turn off my old files erver that I'm using for manually downloading torrents with. Can anyone layout their configuration and how they manage these applications?

So, I had about 10 Plex users on last night and a couple on today and that error has disappeared from my logs and no complaints from the users. Seems that was the fix.

Been Googling around and I think I found the answer. Seems this is a pretty common problem on Linux w/ SSDs. So, I'm posting here in case someone else goes searching the forums for the answer. Change this setting: Settings -> Disk Settings -> Force NCQ Disabled to yes or alternatively, nano /boot/syslinux/syslinux.cfg and add libata.force=noncq to your append line. Set the setting either way and reboot. Will post back in a day or so if this permanently fixed my problem w/ my cache SSDs

Bump

Diagnostic logs attached tower-diagnostics-20160531-1810.zip

Hi all! Just got my unRaid server setup and I'm having some hiccups when browsing the webGui and my Plex library. They tend to become unresponsive for a couple of moments (sometimes 30secs, sometimes 2mins). Upon checking my system log and my hard drive logs, I found this on my cache drives. May 31 12:44:12 Tower kernel: ata8: SATA max UDMA/133 abar m2048@0xdf910000 port 0xdf910180 irq 46 May 31 12:44:12 Tower kernel: ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 300) May 31 12:44:12 Tower kernel: ata8.00: supports DRM functions and may not be fully accessible May 31 12:44:12 Tower kernel: ata8.00: READ LOG DMA EXT failed, trying unqueued May 31 12:44:12 Tower kernel: ata8.00: failed to get NCQ Send/Recv Log Emask 0x1 May 31 12:44:12 Tower kernel: ata8.00: ATA-9: Samsung SSD 850 EVO 500GB, S21HNXAG303357A, EMT01B6Q, max UDMA/133 May 31 12:44:12 Tower kernel: ata8.00: 976773168 sectors, multi 1: LBA48 NCQ (depth 31/32), AA May 31 12:44:12 Tower kernel: ata8.00: supports DRM functions and may not be fully accessible May 31 12:44:12 Tower kernel: ata8.00: failed to get NCQ Send/Recv Log Emask 0x1 May 31 12:44:12 Tower kernel: ata8.00: configured for UDMA/133 May 31 12:44:12 Tower kernel: sd 9:0:0:0: [sdh] 976773168 512-byte logical blocks: (500 GB/466 GiB) May 31 12:44:12 Tower kernel: sd 9:0:0:0: [sdh] 4096-byte physical blocks May 31 12:44:12 Tower kernel: sd 9:0:0:0: [sdh] Write Protect is off May 31 12:44:12 Tower kernel: sd 9:0:0:0: [sdh] Mode Sense: 00 3a 00 00 May 31 12:44:12 Tower kernel: sd 9:0:0:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA May 31 12:44:12 Tower kernel: sdh: sdh1 May 31 12:44:12 Tower kernel: sd 9:0:0:0: [sdh] Attached SCSI disk May 31 12:44:49 Tower emhttp: Samsung_SSD_850_EVO_500GB_S21HNXAG303357A (sdh) 488386584 May 31 12:44:49 Tower emhttp: import 24 cache device: sdh May 31 12:44:49 Tower emhttp: shcmd (7): /usr/sbin/hdparm -S0 /dev/sdh &> /dev/null May 31 12:44:49 Tower emhttp: Samsung_SSD_850_EVO_500GB_S21HNXAG303357A (sdh) 488386584 May 31 12:44:49 Tower emhttp: import 24 cache device: sdh May 31 12:45:17 Tower emhttp: Samsung_SSD_850_EVO_500GB_S21HNXAG303357A (sdh) 488386584 May 31 12:45:17 Tower emhttp: import 24 cache device: sdh May 31 12:45:20 Tower emhttp: Samsung_SSD_850_EVO_500GB_S21HNXAG303357A (sdh) 488386584 May 31 12:45:20 Tower emhttp: import 24 cache device: sdh May 31 12:45:22 Tower emhttp: Samsung_SSD_850_EVO_500GB_S21HNXAG303357A (sdh) 488386584 May 31 12:45:22 Tower emhttp: import 24 cache device: sdh May 31 12:45:49 Tower emhttp: Samsung_SSD_850_EVO_500GB_S21HNXAG303357A (sdh) 488386584 May 31 12:45:49 Tower emhttp: import 24 cache device: sdh May 31 12:46:19 Tower emhttp: Samsung_SSD_850_EVO_500GB_S21HNXAG303357A (sdh) 488386584 May 31 12:46:19 Tower emhttp: import 24 cache device: sdh May 31 12:46:19 Tower emhttp: Samsung_SSD_850_EVO_500GB_S21HNXAG303357A (sdh) 488386584 May 31 12:46:19 Tower emhttp: import 24 cache device: sdh May 31 12:46:35 Tower emhttp: Samsung_SSD_850_EVO_500GB_S21HNXAG303357A (sdh) 488386584 May 31 12:46:35 Tower emhttp: import 24 cache device: sdh May 31 12:47:22 Tower emhttp: Samsung_SSD_850_EVO_500GB_S21HNXAG303357A (sdh) 488386584 May 31 12:47:22 Tower emhttp: import 24 cache device: sdh May 31 12:47:35 Tower emhttp: Samsung_SSD_850_EVO_500GB_S21HNXAG303357A (sdh) 488386584 May 31 12:47:35 Tower emhttp: import 24 cache device: sdh May 31 12:47:35 Tower emhttp: shcmd (61): /usr/sbin/hdparm -S0 /dev/sdh &> /dev/null May 31 12:47:35 Tower kernel: BTRFS: device fsid a64386f3-4ec6-4195-8fb8-30a743718631 devid 2 transid 6837 /dev/sdh1 May 31 13:06:06 Tower kernel: ata8.00: exception Emask 0x0 SAct 0x1000 SErr 0x0 action 0x6 frozen May 31 13:06:06 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED May 31 13:06:06 Tower kernel: ata8.00: cmd 61/10:60:78:69:f2/00:00:10:00:00/40 tag 12 ncq 8192 out May 31 13:06:06 Tower kernel: ata8.00: status: { DRDY } May 31 13:06:06 Tower kernel: ata8: hard resetting link May 31 13:06:06 Tower kernel: ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 300) May 31 13:06:06 Tower kernel: ata8.00: supports DRM functions and may not be fully accessible May 31 13:06:06 Tower kernel: ata8.00: failed to get NCQ Send/Recv Log Emask 0x1 May 31 13:06:06 Tower kernel: ata8.00: supports DRM functions and may not be fully accessible May 31 13:06:06 Tower kernel: ata8.00: failed to get NCQ Send/Recv Log Emask 0x1 May 31 13:06:06 Tower kernel: ata8.00: configured for UDMA/133 May 31 13:06:06 Tower kernel: ata8.00: device reported invalid CHS sector 0 May 31 13:06:06 Tower kernel: ata8: EH complete May 31 13:06:38 Tower kernel: ata8.00: exception Emask 0x0 SAct 0x20000 SErr 0x0 action 0x6 frozen May 31 13:06:38 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED May 31 13:06:38 Tower kernel: ata8.00: cmd 61/10:88:08:55:f5/00:00:10:00:00/40 tag 17 ncq 8192 out May 31 13:06:38 Tower kernel: ata8.00: status: { DRDY } May 31 13:06:38 Tower kernel: ata8: hard resetting link May 31 13:06:38 Tower kernel: ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 300) May 31 13:06:38 Tower kernel: ata8.00: supports DRM functions and may not be fully accessible May 31 13:06:38 Tower kernel: ata8.00: failed to get NCQ Send/Recv Log Emask 0x1 May 31 13:06:38 Tower kernel: ata8.00: supports DRM functions and may not be fully accessible May 31 13:06:38 Tower kernel: ata8.00: failed to get NCQ Send/Recv Log Emask 0x1 May 31 13:06:38 Tower kernel: ata8.00: configured for UDMA/133 May 31 13:06:38 Tower kernel: ata8.00: device reported invalid CHS sector 0 May 31 13:06:38 Tower kernel: ata8: EH complete May 31 13:33:36 Tower kernel: ata8.00: exception Emask 0x0 SAct 0xc800000 SErr 0x0 action 0x6 frozen May 31 13:33:36 Tower kernel: ata8.00: failed command: READ FPDMA QUEUED May 31 13:33:36 Tower kernel: ata8.00: cmd 60/08:b8:a0:bb:a4/00:00:08:00:00/40 tag 23 ncq 4096 in May 31 13:33:36 Tower kernel: ata8.00: status: { DRDY } May 31 13:33:36 Tower kernel: ata8.00: failed command: READ FPDMA QUEUED May 31 13:33:36 Tower kernel: ata8.00: cmd 60/08:d0:70:cc:d4/00:00:08:00:00/40 tag 26 ncq 4096 in May 31 13:33:36 Tower kernel: ata8.00: status: { DRDY } May 31 13:33:36 Tower kernel: ata8.00: failed command: READ FPDMA QUEUED May 31 13:33:36 Tower kernel: ata8.00: cmd 60/08:d8:20:ce:09/00:00:09:00:00/40 tag 27 ncq 4096 in May 31 13:33:36 Tower kernel: ata8.00: status: { DRDY } May 31 13:33:36 Tower kernel: ata8: hard resetting link May 31 13:33:36 Tower kernel: ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 300) May 31 13:33:36 Tower kernel: ata8.00: supports DRM functions and may not be fully accessible May 31 13:33:36 Tower kernel: ata8.00: failed to get NCQ Send/Recv Log Emask 0x1 May 31 13:33:36 Tower kernel: ata8.00: supports DRM functions and may not be fully accessible May 31 13:33:36 Tower kernel: ata8.00: failed to get NCQ Send/Recv Log Emask 0x1 May 31 13:33:36 Tower kernel: ata8.00: configured for UDMA/133 May 31 13:33:36 Tower kernel: ata8.00: device reported invalid CHS sector 0 May 31 13:33:36 Tower kernel: ata8.00: device reported invalid CHS sector 0 May 31 13:33:36 Tower kernel: ata8.00: device reported invalid CHS sector 0 May 31 13:33:36 Tower kernel: ata8: EH complete May 31 17:41:57 Tower kernel: ata8.00: exception Emask 0x0 SAct 0x4000000 SErr 0x0 action 0x6 frozen May 31 17:41:57 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED May 31 17:41:57 Tower kernel: ata8.00: cmd 61/10:d0:78:90:65/00:00:0b:00:00/40 tag 26 ncq 8192 out May 31 17:41:57 Tower kernel: ata8.00: status: { DRDY } May 31 17:41:57 Tower kernel: ata8: hard resetting link May 31 17:41:57 Tower kernel: ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 300) May 31 17:41:57 Tower kernel: ata8.00: supports DRM functions and may not be fully accessible May 31 17:41:57 Tower kernel: ata8.00: failed to get NCQ Send/Recv Log Emask 0x1 May 31 17:41:57 Tower kernel: ata8.00: supports DRM functions and may not be fully accessible May 31 17:41:57 Tower kernel: ata8.00: failed to get NCQ Send/Recv Log Emask 0x1 May 31 17:41:57 Tower kernel: ata8.00: configured for UDMA/133 May 31 17:41:57 Tower kernel: ata8.00: device reported invalid CHS sector 0 May 31 17:41:57 Tower kernel: ata8: EH complete Upon some Googling around, I found that this error could be caused by a bad drive or bad cables. Can anyone tell me by the logs at which one I should be going after first? Or am I barking up the wrong tree? The drives in question are Samsung EVO 850 500gb SSDs. Thanks for any light you can share on this issue!