deaerator

I recently added a WD Elements Shucked drive and have a temp replacement SSD for my cache drive. I noticed my log starting to show this. Jan 11 12:27:23 Tower kernel: ata3.00: exception Emask 0x0 SAct 0xffffffff SErr 0x0 action 0x6 frozen Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/30:00:d8:53:19/05:00:59:00:00/40 tag 0 ncq dma 679936 out Jan 11 12:27:23 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/48:08:08:59:19/05:00:59:00:00/40 tag 1 ncq dma 692224 out Jan 11 12:27:23 Tower kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: READ FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 60/00:10:60:b7:fa/01:00:02:00:00/40 tag 2 ncq dma 131072 in Jan 11 12:27:23 Tower kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/40:18:50:5e:19/05:00:59:00:00/40 tag 3 ncq dma 688128 out Jan 11 12:27:23 Tower kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/40:20:90:63:19/05:00:59:00:00/40 tag 4 ncq dma 688128 out Jan 11 12:27:23 Tower kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/38:28:d0:68:19/00:00:59:00:00/40 tag 5 ncq dma 28672 out Jan 11 12:27:23 Tower kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/48:30:08:69:19/05:00:59:00:00/40 tag 6 ncq dma 692224 out Jan 11 12:27:23 Tower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/40:38:50:6e:19/05:00:59:00:00/40 tag 7 ncq dma 688128 out Jan 11 12:27:23 Tower kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/40:40:90:73:19/05:00:59:00:00/40 tag 8 ncq dma 688128 out Jan 11 12:27:23 Tower kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/38:48:d0:78:19/00:00:59:00:00/40 tag 9 ncq dma 28672 out Jan 11 12:27:23 Tower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/68:50:78:7e:19/05:00:59:00:00/40 tag 10 ncq dma 708608 out Jan 11 12:27:23 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/28:58:e0:83:19/05:00:59:00:00/40 tag 11 ncq dma 675840 out Jan 11 12:27:23 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/58:60:08:89:19/05:00:59:00:00/40 tag 12 ncq dma 700416 out Jan 11 12:27:23 Tower kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/c0:68:60:8e:19/06:00:59:00:00/40 tag 13 ncq dma 884736 out Jan 11 12:27:23 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/e8:70:20:95:19/03:00:59:00:00/40 tag 14 ncq dma 512000 out Jan 11 12:27:23 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/40:78:08:99:19/05:00:59:00:00/40 tag 15 ncq dma 688128 out Jan 11 12:27:23 Tower kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/60:80:48:9e:19/05:00:59:00:00/40 tag 16 ncq dma 704512 out Jan 11 12:27:23 Tower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/58:88:a8:a3:19/05:00:59:00:00/40 tag 17 ncq dma 700416 out Jan 11 12:27:23 Tower kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: READ FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 60/00:90:60:b8:fa/01:00:02:00:00/40 tag 18 ncq dma 131072 in Jan 11 12:27:23 Tower kernel: res 40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: READ FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 60/08:98:68:60:5a/00:00:01:00:00/40 tag 19 ncq dma 4096 in Jan 11 12:27:23 Tower kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/08:a0:70:64:fd/00:00:3b:00:00/40 tag 20 ncq dma 4096 out Jan 11 12:27:23 Tower kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/40:a8:08:29:19/05:00:59:00:00/40 tag 21 ncq dma 688128 out Jan 11 12:27:23 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/40:b0:48:2e:19/05:00:59:00:00/40 tag 22 ncq dma 688128 out Jan 11 12:27:23 Tower kernel: res 40/00:b4:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/40:b8:88:33:19/05:00:59:00:00/40 tag 23 ncq dma 688128 out Jan 11 12:27:23 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/40:c0:c8:38:19/00:00:59:00:00/40 tag 24 ncq dma 32768 out Jan 11 12:27:23 Tower kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/78:c8:08:39:19/05:00:59:00:00/40 tag 25 ncq dma 716800 out Jan 11 12:27:23 Tower kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/40:d0:80:3e:19/05:00:59:00:00/40 tag 26 ncq dma 688128 out Jan 11 12:27:23 Tower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/48:d8:c0:43:19/05:00:59:00:00/40 tag 27 ncq dma 692224 out Jan 11 12:27:23 Tower kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/80:e0:08:49:19/05:00:59:00:00/40 tag 28 ncq dma 720896 out Jan 11 12:27:23 Tower kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/50:e8:88:4e:19/05:00:59:00:00/40 tag 29 ncq dma 696320 out Jan 11 12:27:23 Tower kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: READ FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 60/00:f0:88:c1:ad/03:00:1e:00:00/40 tag 30 ncq dma 393216 in Jan 11 12:27:23 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/70:f8:08:79:19/05:00:59:00:00/40 tag 31 ncq dma 712704 out Jan 11 12:27:23 Tower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3: hard resetting link Jan 11 12:27:23 Tower kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jan 11 12:27:23 Tower kernel: ata3.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Jan 11 12:27:23 Tower kernel: ata3.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jan 11 12:27:23 Tower kernel: ata3.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Jan 11 12:27:23 Tower kernel: ata3.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Jan 11 12:27:23 Tower kernel: ata3.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jan 11 12:27:23 Tower kernel: ata3.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Jan 11 12:27:23 Tower kernel: ata3.00: configured for UDMA/133 Jan 11 12:27:23 Tower kernel: ata3.00: device reported invalid CHS sector 0 Jan 11 12:27:23 Tower kernel: ata3.00: device reported invalid CHS sector 0 Jan 11 12:27:23 Tower kernel: ata3.00: device reported invalid CHS sector 0 Jan 11 12:27:23 Tower kernel: ata3.00: device reported invalid CHS sector 0 Jan 11 12:27:23 Tower kernel: ata3.00: device reported invalid CHS sector 0 Jan 11 12:27:23 Tower kernel: ata3.00: device reported invalid CHS sector 0 Jan 11 12:27:23 Tower kernel: ata3.00: device reported invalid CHS sector 0 Jan 11 12:27:23 Tower kernel: ata3.00: device reported invalid CHS sector 0 Jan 11 12:27:23 Tower kernel: ata3: EH complete Diagnostics is attached. Curious what is causing this? And is it serious? tower-diagnostics-20190111-1346.zip

Having trouble with this Plex Docker staying alive. I find myself restarting this every few hours. I see this populating in the log all the time. I attached diagnostics. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. tower-diagnostics-20181221-2041.zip

How do I testdisk?

I reverted to another HBA card to see if I can get my original array. How do I troubleshoot to get it back. tower-diagnostics-20181120-0945.zip

I thought there was a IT Mode but I was wrong. Thanks for the insight. There is an HBA mode but it still didn't pass the drives to the host OS.

Curious if anyone has experience with this card and what do you have for settings. I can't seem to get the drives to passthrough the controller. The controller itself seems to have renamed my drives and it can no longer start. How do I find the proper drive order.

I'm seeing this in my log. Nov 16 00:37:35 Tower nginx: 2018/11/16 00:37:35 [crit] 8608#8608: *1 connect() to unix:/var/tmp/plex.sock failed (2: No such file or directory) while connecting to upstream, client: 192.168.1.100, server: , request: "GET /dockerterminal/plex/ws HTTP/1.1", upstream: "http://unix:/var/tmp/plex.sock:/ws", host: "f.unraid.net" tower-diagnostics-20181116-0041.zip

Server is starting to get unstable and keeps on crashing. Diagnostics attached tower-diagnostics-20181113-2358.zip

Thank you for the help. I had to move the keyfile temparory to that location until it was formatted and mounted. Then I deleted and did a re-boot and everything is working correctly.

I attempted to format and it still says unmountable missing encryption key.

I'm trying to add a new drive to my encrypted array, and after the pre-clear it keeps telling me it's unmountable due to missing encryption key. How do I find this setting or how to mount it with encryption? Diagnostics attached. tower-diagnostics-20181026-1215.zip

I have two HP220 and I am trying to flash this into IT mode using this thread: https://forums.servethehome.com/index.php?threads/flashing-hp-h220-sas-card-to-latest-fw.13057/ I am flashing this on another machine and it seems to be working but when I goto my main unraid server it seems to be non functional or not detectiing the drives. how do I correct this?

I acquired an HP220 and want to flash it to this card so it matches the one I purchased How do I flash this guy to this. https://www.ebay.com/itm/HP-H220-6Gbps-SAS-PCI-E-3-0-HBA-LSI-9207-8i-P20-IT-Mode-for-ZFS-FreeNAS-unRAID/162862201664?rmvSB=true LSI Avago IT mode firmware version P20 (20.00.07.00) MPTSAS2 BIOS ROM flashed version 07.39.02.00 MPTSAS2 UEFI ROM flashed version 07.27.01.01 Original SAS address preserved

I ssh into unraid and made my way to /mnt/cache/appdata/downloads directory and ls -l