dlandon

New release of Recycle Bin. If you are using the Recycle Bin on 6.9 Beta 24, you will notice that deleted files are logged to the syslog as well as the smb log used by Recycle Bin to show deleted files. This is due to a change in the syslog settings. If you are doing a lot of deleting on a SMB share, you might want to exclude that share from the Recycle Bin so the Syslog doesn't fill with file deleted messages.

Recycle Bin plugin is broken with this version. For the moment don't depend on it for recovering deleted files. Samba has been updated and either someting has changed or they borke the vfs_recycle module. I'll spend some time trying to figure out what is happening. Got it. Also fixed the excessive logging.

I see the following in my log now: Jul 8 05:59:08 BackupServer smbd_audit[21566]: close fd 32 Jul 8 05:59:08 BackupServer smbd_audit[21566]: close fd 37 Jul 8 05:59:08 BackupServer smbd_audit[21566]: open unassigned.devices/unassigned.devices.emhttp (fd 32) Jul 8 05:59:08 BackupServer smbd_audit[21566]: close fd 32 Jul 8 05:59:08 BackupServer smbd_audit[21566]: open unassigned.devices/unassigned.devices.emhttp (fd 32) Jul 8 05:59:08 BackupServer smbd_audit[21566]: close fd 32 Jul 8 05:59:08 BackupServer smbd_audit[21566]: open unassigned.devices/unassigned.devices.emhttp (fd 32) Jul 8 05:59:08 BackupServer smbd_audit[21566]: close fd 32 Jul 8 05:59:08 BackupServer smbd_audit[21566]: open unassigned.devices/unassigned.devices.emhttp (fd 32) Jul 8 05:59:08 BackupServer smbd_audit[21566]: open unassigned.devices/unassigned.devices.emhttp (fd 37) Jul 8 05:59:08 BackupServer smbd_audit[21566]: close fd 37 Jul 8 05:59:08 BackupServer smbd_audit[21566]: open unassigned.devices/unassigned.devices.emhttp (fd 37) The recycle bin plugin is using smb audit to track deleted files and seems to be causing these log entries. They occur when browsing smb shares. I'll have to track down how to turn the log entries off.

Each disk has a unique ID. How do you have them connected? That (stupid thing) has to have a unique device ID in order to identify each disk. What do you expect UD to do if the disks don't have unique IDs? This can happen if you have the disks in an external bay. That can present both disks to UD with the same ID.

The latest changes in Samba are causing issues with looking up servers and shares. i.e. NetBios and Windows Discovery. UD does the best it can to search for servers and shares, but using the IP address of the remote server seems to be the most reliable.

No. How you are copying the files? What kind of disk? SSD or spinner?

I put it on the Intel controller, ran the fstrim command and didn't have any issues.

The best way to do this is with the Pool feature of 6.9.

I opted to go with a nvme device instead. I prefer to stay away from these kinds of issues since this SSD holds my VMs and Docker image. It's also a lot faster than a sata SSD.

It seems like it happened again this morning when the trim was scheduled. I've moved cables so the SSD is on the Intel controller. @johnnie.black So it seems this new Samsung 960 SSD has problems with trim on the ASMedia controller? Is this a common thing?

Post diagnostics. Without it we can only guess at the problem.

Is the remote share accessible, just that UD doesn't show the disk size, free, and available?

Unfortunately, yes. UD Can't mount a partition Linux can't understand.

Unraid (Linux) does not recognize a valid partition on the first partition of those disks.

I'll try that if it happens again. Just a matter of moving a few cables.

Looks like ASMedia controller same as my cache SSD: 1b21:0612] 04:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02) [10:0:0:0] disk ATA Samsung SSD 850 4B6Q /dev/sdj 1.02TB [11:0:0:0] disk ATA Samsung SSD 860 2B6Q /dev/sdk 1.02TB

I just installed a new Samsung PRO 1TB SSD in my server as a Pool device to hold VMs and Docker image. After a day of operation I got some errors this morning: Jul 3 20:38:51 MediaServer kernel: ata10: SATA max UDMA/133 abar m512@0x61400000 port 0x61400180 irq 137 Jul 3 20:38:51 MediaServer kernel: ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jul 3 20:38:51 MediaServer kernel: ata10.00: supports DRM functions and may not be fully accessible Jul 3 20:38:51 MediaServer kernel: ata10.00: ATA-11: Samsung SSD 860 PRO 1TB, S5G8NC0N500080A, RVM02B6Q, max UDMA/133 Jul 3 20:38:51 MediaServer kernel: ata10.00: 2000409264 sectors, multi 1: LBA48 NCQ (depth 32), AA Jul 3 20:38:51 MediaServer kernel: ata10.00: supports DRM functions and may not be fully accessible Jul 3 20:38:51 MediaServer kernel: ata10.00: configured for UDMA/133 Jul 3 20:38:51 MediaServer kernel: ata10.00: Enabling discard_zeroes_data Jul 3 20:38:51 MediaServer kernel: sd 11:0:0:0: [sdk] 2000409264 512-byte logical blocks: (1.02 TB/954 GiB) Jul 3 20:38:51 MediaServer kernel: sd 11:0:0:0: [sdk] Write Protect is off Jul 3 20:38:51 MediaServer kernel: sd 11:0:0:0: [sdk] Mode Sense: 00 3a 00 00 Jul 3 20:38:51 MediaServer kernel: sd 11:0:0:0: [sdk] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jul 3 20:38:51 MediaServer kernel: ata10.00: Enabling discard_zeroes_data Jul 3 20:38:51 MediaServer kernel: sdk: sdk1 Jul 3 20:38:51 MediaServer kernel: ata10.00: Enabling discard_zeroes_data Jul 3 20:38:51 MediaServer kernel: sd 11:0:0:0: [sdk] Attached SCSI disk Jul 3 20:39:05 MediaServer emhttpd: Samsung_SSD_860_PRO_1TB_S5G8NC0N500080A (sdk) 512 2000409264 Jul 3 20:39:05 MediaServer emhttpd: import 31 cache device: (sdk) Samsung_SSD_860_PRO_1TB_S5G8NC0N500080A Jul 3 20:39:15 MediaServer emhttpd: shcmd (48): mount -t xfs -o noatime,nodiratime /dev/sdk1 /mnt/sysdata Jul 3 20:39:15 MediaServer kernel: XFS (sdk1): Mounting V5 Filesystem Jul 3 20:39:15 MediaServer kernel: XFS (sdk1): Ending clean mount Jul 4 05:30:34 MediaServer kernel: ata10.00: exception Emask 0x0 SAct 0x7ff071 SErr 0x0 action 0x6 frozen Jul 4 05:30:34 MediaServer kernel: ata10.00: failed command: WRITE FPDMA QUEUED Jul 4 05:30:34 MediaServer kernel: ata10.00: cmd 61/40:00:a0:a5:d7/00:00:1d:00:00/40 tag 0 ncq dma 32768 out Jul 4 05:30:34 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:30:34 MediaServer kernel: ata10.00: failed command: WRITE FPDMA QUEUED Jul 4 05:30:34 MediaServer kernel: ata10.00: cmd 61/40:20:a0:a5:f7/00:00:1d:00:00/40 tag 4 ncq dma 32768 out Jul 4 05:30:34 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:30:34 MediaServer kernel: ata10.00: failed command: WRITE FPDMA QUEUED Jul 4 05:30:34 MediaServer kernel: ata10.00: cmd 61/08:28:98:15:bc/00:00:1f:00:00/40 tag 5 ncq dma 4096 out Jul 4 05:30:34 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:30:34 MediaServer kernel: ata10.00: failed command: WRITE FPDMA QUEUED Jul 4 05:30:34 MediaServer kernel: ata10.00: cmd 61/08:30:98:15:3c/00:00:20:00:00/40 tag 6 ncq dma 4096 out Jul 4 05:30:34 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:30:34 MediaServer kernel: ata10.00: failed command: WRITE FPDMA QUEUED Jul 4 05:30:34 MediaServer kernel: ata10.00: cmd 61/08:60:f8:40:d9/00:00:59:00:00/40 tag 12 ncq dma 4096 out Jul 4 05:30:34 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:30:34 MediaServer kernel: ata10.00: failed command: WRITE FPDMA QUEUED Jul 4 05:30:34 MediaServer kernel: ata10.00: cmd 61/08:68:80:41:d9/00:00:59:00:00/40 tag 13 ncq dma 4096 out Jul 4 05:30:34 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:30:34 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED Jul 4 05:30:34 MediaServer kernel: ata10.00: cmd 64/01:70:00:00:00/00:00:00:00:00/a0 tag 14 ncq dma 512 out Jul 4 05:30:34 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:30:34 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED Jul 4 05:30:34 MediaServer kernel: ata10.00: cmd 64/01:78:00:00:00/00:00:00:00:00/a0 tag 15 ncq dma 512 out Jul 4 05:30:34 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:30:34 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED Jul 4 05:30:34 MediaServer kernel: ata10.00: cmd 64/01:80:00:00:00/00:00:00:00:00/a0 tag 16 ncq dma 512 out Jul 4 05:30:34 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:30:34 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED Jul 4 05:30:34 MediaServer kernel: ata10.00: cmd 64/01:88:00:00:00/00:00:00:00:00/a0 tag 17 ncq dma 512 out Jul 4 05:30:34 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:30:34 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED Jul 4 05:30:34 MediaServer kernel: ata10.00: cmd 64/01:90:00:00:00/00:00:00:00:00/a0 tag 18 ncq dma 512 out Jul 4 05:30:34 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:30:34 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED Jul 4 05:30:34 MediaServer kernel: ata10.00: cmd 64/01:98:00:00:00/00:00:00:00:00/a0 tag 19 ncq dma 512 out Jul 4 05:30:34 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:30:34 MediaServer kernel: ata10.00: failed command: WRITE FPDMA QUEUED Jul 4 05:30:34 MediaServer kernel: ata10.00: cmd 61/08:a0:20:8b:6a/00:00:00:00:00/40 tag 20 ncq dma 4096 out Jul 4 05:30:34 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:30:34 MediaServer kernel: ata10.00: failed command: WRITE FPDMA QUEUED Jul 4 05:30:34 MediaServer kernel: ata10.00: cmd 61/08:a8:a8:8b:6a/00:00:00:00:00/40 tag 21 ncq dma 4096 out Jul 4 05:30:34 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:30:34 MediaServer kernel: ata10.00: failed command: WRITE FPDMA QUEUED Jul 4 05:30:34 MediaServer kernel: ata10.00: cmd 61/00:b0:80:bb:1a/01:00:63:00:00/40 tag 22 ncq dma 131072 out Jul 4 05:30:34 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:30:34 MediaServer kernel: ata10: hard resetting link Jul 4 05:30:34 MediaServer kernel: ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jul 4 05:30:34 MediaServer kernel: ata10.00: supports DRM functions and may not be fully accessible Jul 4 05:30:34 MediaServer kernel: ata10.00: supports DRM functions and may not be fully accessible Jul 4 05:30:34 MediaServer kernel: ata10.00: configured for UDMA/133 Jul 4 05:30:34 MediaServer kernel: ata10: EH complete Jul 4 05:31:05 MediaServer kernel: ata10.00: exception Emask 0x0 SAct 0xffcd00 SErr 0x0 action 0x6 frozen Jul 4 05:31:05 MediaServer kernel: ata10.00: failed command: WRITE FPDMA QUEUED Jul 4 05:31:05 MediaServer kernel: ata10.00: cmd 61/08:40:20:8b:6a/00:00:00:00:00/40 tag 8 ncq dma 4096 out Jul 4 05:31:05 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:31:05 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED Jul 4 05:31:05 MediaServer kernel: ata10.00: cmd 64/01:50:00:00:00/00:00:00:00:00/a0 tag 10 ncq dma 512 out Jul 4 05:31:05 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:31:05 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED Jul 4 05:31:05 MediaServer kernel: ata10.00: cmd 64/01:58:00:00:00/00:00:00:00:00/a0 tag 11 ncq dma 512 out Jul 4 05:31:05 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:31:05 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED Jul 4 05:31:05 MediaServer kernel: ata10.00: cmd 64/01:70:00:00:00/00:00:00:00:00/a0 tag 14 ncq dma 512 out Jul 4 05:31:05 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:31:05 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED Jul 4 05:31:05 MediaServer kernel: ata10.00: cmd 64/01:78:00:00:00/00:00:00:00:00/a0 tag 15 ncq dma 512 out Jul 4 05:31:05 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:31:05 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED Jul 4 05:31:05 MediaServer kernel: ata10.00: cmd 64/01:80:00:00:00/00:00:00:00:00/a0 tag 16 ncq dma 512 out Jul 4 05:31:05 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:31:05 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED Jul 4 05:31:05 MediaServer kernel: ata10.00: cmd 64/01:88:00:00:00/00:00:00:00:00/a0 tag 17 ncq dma 512 out Jul 4 05:31:05 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:31:05 MediaServer kernel: ata10.00: failed command: WRITE FPDMA QUEUED Jul 4 05:31:05 MediaServer kernel: ata10.00: cmd 61/08:90:80:41:d9/00:00:59:00:00/40 tag 18 ncq dma 4096 out Jul 4 05:31:05 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:31:05 MediaServer kernel: ata10.00: failed command: WRITE FPDMA QUEUED Jul 4 05:31:05 MediaServer kernel: ata10.00: cmd 61/08:98:f8:40:d9/00:00:59:00:00/40 tag 19 ncq dma 4096 out Jul 4 05:31:05 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:31:05 MediaServer kernel: ata10.00: failed command: WRITE FPDMA QUEUED Jul 4 05:31:05 MediaServer kernel: ata10.00: cmd 61/08:a0:98:15:3c/00:00:20:00:00/40 tag 20 ncq dma 4096 out Jul 4 05:31:05 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:31:05 MediaServer kernel: ata10.00: failed command: WRITE FPDMA QUEUED Jul 4 05:31:05 MediaServer kernel: ata10.00: cmd 61/08:a8:98:15:bc/00:00:1f:00:00/40 tag 21 ncq dma 4096 out Jul 4 05:31:05 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:31:05 MediaServer kernel: ata10.00: failed command: WRITE FPDMA QUEUED Jul 4 05:31:05 MediaServer kernel: ata10.00: cmd 61/40:b0:a0:a5:f7/00:00:1d:00:00/40 tag 22 ncq dma 32768 out Jul 4 05:31:05 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:31:05 MediaServer kernel: ata10.00: failed command: WRITE FPDMA QUEUED Jul 4 05:31:05 MediaServer kernel: ata10.00: cmd 61/40:b8:a0:a5:d7/00:00:1d:00:00/40 tag 23 ncq dma 32768 out Jul 4 05:31:05 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:31:05 MediaServer kernel: ata10: hard resetting link Jul 4 05:31:05 MediaServer kernel: ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jul 4 05:31:05 MediaServer kernel: ata10.00: supports DRM functions and may not be fully accessible Jul 4 05:31:05 MediaServer kernel: ata10.00: supports DRM functions and may not be fully accessible Jul 4 05:31:05 MediaServer kernel: ata10.00: configured for UDMA/133 Jul 4 05:31:05 MediaServer kernel: ata10: EH complete Jul 4 05:31:05 MediaServer kernel: ata10.00: Enabling discard_zeroes_data Jul 4 05:31:35 MediaServer kernel: ata10.00: exception Emask 0x0 SAct 0xff0000 SErr 0x0 action 0x6 frozen Jul 4 05:31:35 MediaServer kernel: ata10.00: failed command: WRITE FPDMA QUEUED Jul 4 05:31:35 MediaServer kernel: ata10.00: cmd 61/08:80:80:41:d9/00:00:59:00:00/40 tag 16 ncq dma 4096 out Jul 4 05:31:35 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:31:35 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED Jul 4 05:31:35 MediaServer kernel: ata10.00: cmd 64/01:88:00:00:00/00:00:00:00:00/a0 tag 17 ncq dma 512 out Jul 4 05:31:35 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:31:35 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED Jul 4 05:31:35 MediaServer kernel: ata10.00: cmd 64/01:90:00:00:00/00:00:00:00:00/a0 tag 18 ncq dma 512 out Jul 4 05:31:35 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:31:35 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED Jul 4 05:31:35 MediaServer kernel: ata10.00: cmd 64/01:98:00:00:00/00:00:00:00:00/a0 tag 19 ncq dma 512 out Jul 4 05:31:35 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:31:35 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED Jul 4 05:31:35 MediaServer kernel: ata10.00: cmd 64/01:a0:00:00:00/00:00:00:00:00/a0 tag 20 ncq dma 512 out Jul 4 05:31:35 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:31:35 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED Jul 4 05:31:35 MediaServer kernel: ata10.00: cmd 64/01:a8:00:00:00/00:00:00:00:00/a0 tag 21 ncq dma 512 out Jul 4 05:31:35 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:31:35 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED Jul 4 05:31:35 MediaServer kernel: ata10.00: cmd 64/01:b0:00:00:00/00:00:00:00:00/a0 tag 22 ncq dma 512 out Jul 4 05:31:35 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:31:35 MediaServer kernel: ata10.00: failed command: WRITE FPDMA QUEUED Jul 4 05:31:35 MediaServer kernel: ata10.00: cmd 61/08:b8:20:8b:6a/00:00:00:00:00/40 tag 23 ncq dma 4096 out Jul 4 05:31:35 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:31:35 MediaServer kernel: ata10: hard resetting link Jul 4 05:31:36 MediaServer kernel: ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jul 4 05:31:36 MediaServer kernel: ata10.00: supports DRM functions and may not be fully accessible Jul 4 05:31:36 MediaServer kernel: ata10.00: supports DRM functions and may not be fully accessible Jul 4 05:31:36 MediaServer kernel: ata10.00: configured for UDMA/133 Jul 4 05:31:36 MediaServer kernel: ata10: EH complete Jul 4 05:32:06 MediaServer kernel: ata10.00: NCQ disabled due to excessive errors Jul 4 05:32:06 MediaServer kernel: ata10.00: exception Emask 0x0 SAct 0xff800 SErr 0x0 action 0x6 frozen Jul 4 05:32:06 MediaServer kernel: ata10.00: failed command: READ FPDMA QUEUED Jul 4 05:32:06 MediaServer kernel: ata10.00: cmd 60/40:58:78:78:78/00:00:5f:00:00/40 tag 11 ncq dma 32768 in Jul 4 05:32:06 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:32:06 MediaServer kernel: ata10.00: failed command: WRITE FPDMA QUEUED Jul 4 05:32:06 MediaServer kernel: ata10.00: cmd 61/08:60:20:8b:6a/00:00:00:00:00/40 tag 12 ncq dma 4096 out Jul 4 05:32:06 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:32:06 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED Jul 4 05:32:06 MediaServer kernel: ata10.00: cmd 64/01:68:00:00:00/00:00:00:00:00/a0 tag 13 ncq dma 512 out Jul 4 05:32:06 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:32:06 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED Jul 4 05:32:06 MediaServer kernel: ata10.00: cmd 64/01:70:00:00:00/00:00:00:00:00/a0 tag 14 ncq dma 512 out Jul 4 05:32:06 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:32:06 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED Jul 4 05:32:06 MediaServer kernel: ata10.00: cmd 64/01:78:00:00:00/00:00:00:00:00/a0 tag 15 ncq dma 512 out Jul 4 05:32:06 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:32:06 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED Jul 4 05:32:06 MediaServer kernel: ata10.00: cmd 64/01:80:00:00:00/00:00:00:00:00/a0 tag 16 ncq dma 512 out Jul 4 05:32:06 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:32:06 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED Jul 4 05:32:06 MediaServer kernel: ata10.00: cmd 64/01:88:00:00:00/00:00:00:00:00/a0 tag 17 ncq dma 512 out Jul 4 05:32:06 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:32:06 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED Jul 4 05:32:06 MediaServer kernel: ata10.00: cmd 64/01:90:00:00:00/00:00:00:00:00/a0 tag 18 ncq dma 512 out Jul 4 05:32:06 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:32:06 MediaServer kernel: ata10.00: failed command: WRITE FPDMA QUEUED Jul 4 05:32:06 MediaServer kernel: ata10.00: cmd 61/08:98:80:41:d9/00:00:59:00:00/40 tag 19 ncq dma 4096 out Jul 4 05:32:06 MediaServer kernel: ata10.00: status: { DRDY } Jul 4 05:32:06 MediaServer kernel: ata10: hard resetting link Jul 4 05:32:06 MediaServer kernel: ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jul 4 05:32:06 MediaServer kernel: ata10.00: supports DRM functions and may not be fully accessible Jul 4 05:32:06 MediaServer kernel: ata10.00: supports DRM functions and may not be fully accessible Jul 4 05:32:06 MediaServer kernel: ata10.00: configured for UDMA/133 Jul 4 05:32:06 MediaServer kernel: sd 11:0:0:0: [sdk] tag#11 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=30s Jul 4 05:32:06 MediaServer kernel: sd 11:0:0:0: [sdk] tag#11 Sense Key : 0x5 [current] Jul 4 05:32:06 MediaServer kernel: sd 11:0:0:0: [sdk] tag#11 ASC=0x21 ASCQ=0x4 Jul 4 05:32:06 MediaServer kernel: sd 11:0:0:0: [sdk] tag#11 CDB: opcode=0x28 28 00 5f 78 78 78 00 00 40 00 Jul 4 05:32:06 MediaServer kernel: blk_update_request: I/O error, dev sdk, sector 1601730680 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 0 Jul 4 05:32:06 MediaServer kernel: ata10: EH complete Jul 4 05:32:06 MediaServer kernel: ata10.00: Enabling discard_zeroes_data Jul 4 05:33:08 MediaServer root: /mnt/sysdata: 752.7 GiB (808155463680 bytes) trimmed on /dev/sdk1 I have the trim operation set for 5:30 AM which is about the time of these errors. Any disk expert out there have any ideas on this?

New release of UD. - SSD disks will not be issued a spin down timer. This should help those having problems with SSD disks going off-line when spun down. - Better xfs and btrfs partition alignment when formatting a disk.

That's probably from a network or remote share server issue.

There is no easy mode. The Nvidia CUDA cannnot be pre-packaged because of licensing. There is no way I can do an 'easy mode'. The compile script I've provided is the best I can do.

I expect that nothing will change except that the Nvidia plugin will not have to be installed.

It'll be in the next update.

Haven't looked at this in a long time. I'll have a look.

You need to move the data, but you can't just move Events. You need to move the complete data/ folder. The database will be out of synch if you don't. I would: - Remove the Docker. - Move the data/ folder to your UD Disk. - Reinstall the Docker and map the data to your UD disk.

That level of permission control would have to to be done with Linux permissions, or through array shares.