tr0910

It just finished a second pass of preclear, this time the smart uncorrectable and pending are cleared, but uncorrect has increased to 47. Preclear it a third time, but reboot first to hopefully clear up the run errors?? ================================================================== 1.15b = unRAID server Pre-Clear disk /dev/sdn = cycle 1 of 1, partition start on sector 1 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 27C, Elapsed Time: 23:34:33 ========================================================================1.15b == ST3000DM001-9YN166 W1F0N4JK == Disk /dev/sdn has been successfully precleared == with a starting sector of 1 ============================================================================ /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected ** Changed attributes in files: /tmp/smart_start_sdn /tmp/smart_finish_sdn ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 119 ok Spin_Up_Time = 92 ok Start_Stop_Count = 97 ok Reallocated_Sector_Ct = 100 ok Seek_Error_Rate = 81 ok Power_On_Hours = 76 ok Spin_Retry_Count = 100 ok Power_Cycle_Count = 100 ok Runtime_Bad_Block = 100 ok End-to-End_Error = 100 ok Reported_Uncorrect = 63 ok Command_Timeout = 100 ok High_Fly_Writes = 84 ok Airflow_Temperature_Cel = 78 ok G-Sense_Error_Rate = 100 ok Power-Off_Retract_Count = 100 ok Load_Cycle_Count = 41 ok Temperature_Celsius = 22 ok Current_Pending_Sector = 100 ok Offline_Uncorrectable = 100 ok UDMA_CRC_Error_Count = 200 ok Head_Flying_Hours = 100 ok Total_LBAs_Written = 100 ok Total_LBAs_Read = 100 ok No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. a change of 0 in the number of sectors pending re-allocation. 0 sectors had been re-allocated before the start of the preclear. a change of 0 in the number of sectors re-allocated. SMART overall-health status = /boot/config/plugins/preclear.disk/preclear_disk.sh: line 2298: echo: write error: No space left on device root@Kim:/usr/local/emhttp#

Those 3 numbers are. 21% 3% 21% Log has lots of headroom doesn't it? But the syslog has these interesting errors early this morning relating to this drive being precleared a second time. This would have been at the end of the preread, or the start of the zeroing stage. It is happily marching along zeroing at present. Jan 30 06:04:49 Kim kernel: ata4.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0 Jan 30 06:04:49 Kim kernel: ata4.00: irq_stat 0x40000008 Jan 30 06:04:49 Kim kernel: ata4.00: failed command: READ FPDMA QUEUED Jan 30 06:04:49 Kim kernel: ata4.00: cmd 60/00:00:70:38:d7/01:00:5c:01:00/40 tag 0 ncq 131072 in Jan 30 06:04:49 Kim kernel: res 41/40:00:08:39:d7/00:01:5c:01:00/00 Emask 0x409 (media error) <F> Jan 30 06:04:49 Kim kernel: ata4.00: status: { DRDY ERR } Jan 30 06:04:49 Kim kernel: ata4.00: error: { UNC } Jan 30 06:04:49 Kim kernel: ata4.00: configured for UDMA/133 Jan 30 06:04:49 Kim kernel: sd 5:0:0:0: [sdn] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Jan 30 06:04:49 Kim kernel: sd 5:0:0:0: [sdn] tag#0 Sense Key : 0x3 [current] [descriptor] Jan 30 06:04:49 Kim kernel: sd 5:0:0:0: [sdn] tag#0 ASC=0x11 ASCQ=0x4 Jan 30 06:04:49 Kim kernel: sd 5:0:0:0: [sdn] tag#0 CDB: opcode=0x88 88 00 00 00 00 01 5c d7 38 70 00 00 01 00 00 00 Jan 30 06:04:49 Kim kernel: blk_update_request: I/O error, dev sdn, sector 5852576008 Jan 30 06:04:49 Kim kernel: ata4: EH complete Jan 30 06:04:52 Kim kernel: ata4.00: exception Emask 0x0 SAct 0x8 SErr 0x0 action 0x0 Jan 30 06:04:52 Kim kernel: ata4.00: irq_stat 0x40000008 Jan 30 06:04:52 Kim kernel: ata4.00: failed command: READ FPDMA QUEUED Jan 30 06:04:52 Kim kernel: ata4.00: cmd 60/08:18:08:39:d7/00:00:5c:01:00/40 tag 3 ncq 4096 in Jan 30 06:04:52 Kim kernel: res 41/40:08:08:39:d7/00:00:5c:01:00/00 Emask 0x409 (media error) <F> Jan 30 06:04:52 Kim kernel: ata4.00: status: { DRDY ERR } Jan 30 06:04:52 Kim kernel: ata4.00: error: { UNC } Jan 30 06:04:52 Kim kernel: ata4.00: configured for UDMA/133 Jan 30 06:04:52 Kim kernel: sd 5:0:0:0: [sdn] tag#3 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Jan 30 06:04:52 Kim kernel: sd 5:0:0:0: [sdn] tag#3 Sense Key : 0x3 [current] [descriptor] Jan 30 06:04:52 Kim kernel: sd 5:0:0:0: [sdn] tag#3 ASC=0x11 ASCQ=0x4 Jan 30 06:04:52 Kim kernel: sd 5:0:0:0: [sdn] tag#3 CDB: opcode=0x88 88 00 00 00 00 01 5c d7 39 08 00 00 00 08 00 00 Jan 30 06:04:52 Kim kernel: blk_update_request: I/O error, dev sdn, sector 5852576008 Jan 30 06:04:52 Kim kernel: Buffer I/O error on dev sdn, logical block 731572001, async page read Jan 30 06:04:52 Kim kernel: ata4: EH complete Jan 30 06:04:55 Kim kernel: ata4.00: exception Emask 0x0 SAct 0x200 SErr 0x0 action 0x0 Jan 30 06:04:55 Kim kernel: ata4.00: irq_stat 0x40000008 Jan 30 06:04:55 Kim kernel: ata4.00: failed command: READ FPDMA QUEUED Jan 30 06:04:55 Kim kernel: ata4.00: cmd 60/08:48:08:39:d7/00:00:5c:01:00/40 tag 9 ncq 4096 in Jan 30 06:04:55 Kim kernel: res 41/40:08:08:39:d7/00:00:5c:01:00/00 Emask 0x409 (media error) <F> Jan 30 06:04:55 Kim kernel: ata4.00: status: { DRDY ERR } Jan 30 06:04:55 Kim kernel: ata4.00: error: { UNC } Jan 30 06:04:55 Kim kernel: ata4.00: configured for UDMA/133 Jan 30 06:04:55 Kim kernel: sd 5:0:0:0: [sdn] tag#9 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Jan 30 06:04:55 Kim kernel: sd 5:0:0:0: [sdn] tag#9 Sense Key : 0x3 [current] [descriptor] Jan 30 06:04:55 Kim kernel: sd 5:0:0:0: [sdn] tag#9 ASC=0x11 ASCQ=0x4 Jan 30 06:04:55 Kim kernel: sd 5:0:0:0: [sdn] tag#9 CDB: opcode=0x88 88 00 00 00 00 01 5c d7 39 08 00 00 00 08 00 00 Jan 30 06:04:55 Kim kernel: blk_update_request: I/O error, dev sdn, sector 5852576008 Jan 30 06:04:55 Kim kernel: Buffer I/O error on dev sdn, logical block 731572001, async page read Jan 30 06:04:55 Kim kernel: ata4: EH complete

I have some older 3tb drives that are throwing errors. I just precleared it successfully using the preclear plugin, but here is what it dumped I think I should preclear it again just in case. What do you think? (not sure what the errors are in line 842. Boot flash has 12gb free) Warning [KIM] - reported uncorrect is 44 Warning [KIM] - current pending sector is 8 Warning [KIM] - offline uncorrectable is 8 unRAID device sdn SMART health [198]: 29-01-2016 22:35 ST3000DM001-9YN166_W1F0N4JK (sdn) ================================================================== 1.15b = unRAID server Pre-Clear disk /dev/sdn = cycle 1 of 1, partition start on sector 1 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 27C, Elapsed Time: 23:34:33 ========================================================================1.15b == ST3000DM001-9YN166 W1F0N4JK == Disk /dev/sdn has been successfully precleared == with a starting sector of 1 ============================================================================ /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected ** Changed attributes in files: /tmp/smart_start_sdn /tmp/smart_finish_sdn ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 119 ok Spin_Up_Time = 92 ok Start_Stop_Count = 97 ok Reallocated_Sector_Ct = 100 ok Seek_Error_Rate = 81 ok Power_On_Hours = 76 ok Spin_Retry_Count = 100 ok Power_Cycle_Count = 100 ok Runtime_Bad_Block = 100 ok End-to-End_Error = 100 ok Reported_Uncorrect = 63 ok Command_Timeout = 100 ok High_Fly_Writes = 84 ok Airflow_Temperature_Cel = 78 ok G-Sense_Error_Rate = 100 ok Power-Off_Retract_Count = 100 ok Load_Cycle_Count = 41 ok Temperature_Celsius = 22 ok Current_Pending_Sector = 100 ok Offline_Uncorrectable = 100 ok UDMA_CRC_Error_Count = 200 ok Head_Flying_Hours = 100 ok Total_LBAs_Written = 100 ok Total_LBAs_Read = 100 ok No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. a change of 0 in the number of sectors pending re-allocation. 0 sectors had been re-allocated before the start of the preclear. a change of 0 in the number of sectors re-allocated. SMART overall-health status = /boot/config/plugins/preclear.disk/preclear_disk.sh: line 2298: echo: write error: No space left on device root@Kim:/usr/local/emhttp#

Or, hot plug didn't work and Linux thought there were two drives with the same UUID? Here is the current log, but I don't find the one for the time before the reboot. You can see I hot plugged another drive. An old Array xfs drive LAFX and it shows an error, but this is different. This drive was showing errors and that is why it got pulled from the array. Jan 28 9:31:30 Disk 'ST3000DM001 9YN166 W1F0N4JK' not mounted, cannot unmount... Jan 28 9:31:30 Command not available, skipping. Jan 28 9:31:30 Unmounting disk 'Samsung SSD 840 EVO 120GB S1D5NEAD803955A'... Jan 28 9:31:30 Unmounting '/dev/sdp1'... Jan 28 9:31:31 Successfully unmounted '/dev/sdp1' Jan 28 9:31:31 Disk 'Samsung SSD 840 EVO 120GB S1D5NEAD803955A' removed successfully. Jan 28 9:31:31 Disk 'Areca ARC1280V2' not mounted, cannot unmount... Jan 28 9:31:31 Disk 'Hitachi HDS5C3030ALA630' not mounted, cannot unmount... Jan 28 9:31:31 Disk 'WDC WD20EARS 00MVWB0' not mounted, cannot unmount... Jan 28 9:31:31 Disk 'WDC WD30EZRS 00J99B0' not mounted, cannot unmount... Jan 28 9:38:39 Disk with serial 'ST3000DM001-9YN166_W1F0N4JK' auto mount is disabled, not mounted. Jan 28 9:38:39 Disk with serial 'ST3000DM001-9YN166_W1F11605' auto mount is disabled, not mounted. Jan 28 9:38:39 Disk with serial 'ARC1280V1_0000003002536795' auto mount is disabled, not mounted. Jan 28 9:38:39 Disk with serial 'HDS5C3030ALA630_MJ1323YNG1UKKC' auto mount is disabled, not mounted. Jan 28 9:38:39 Disk with serial 'WD20EARS-00MVWB0_WD-WMAZA3919347' auto mount is disabled, not mounted. Jan 28 10:03:29 Adding disk '/dev/sdo1'... Jan 28 10:03:29 Mount drive command: mount -t reiserfs -o auto,async,noatime,nodiratime '/dev/sdo1' '/mnt/disks/ST1605' Jan 28 10:03:29 Successfully mounted '/dev/sdo1' on '/mnt/disks/ST1605' Jan 28 10:03:29 Defining share 'ST1605' on file '/etc/samba/unassigned-shares/ST1605.conf' Jan 28 10:03:29 Adding share 'ST1605' to '/boot/config/smb-extra.conf' Jan 28 10:03:29 Reloading Samba configuration... Jan 28 10:03:29 Directory '/mnt/disks/ST1605' shared successfully. Jan 28 10:03:29 Command not available, skipping. Jan 28 10:19:37 Disk with serial 'ST3000DM001-9YN166_W1F0LAFX' auto mount is disabled, not mounted. Jan 28 10:24:54 Adding disk '/dev/sds1'... Jan 28 10:24:54 Mount drive command: mount -t xfs -o rw,noatime,nodiratime '/dev/sds1' '/mnt/disks/STLAFX' Jan 28 10:24:54 Mount of '/dev/sds1' failed. Error message: mount: wrong fs type, bad option, bad superblock on /dev/sds1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so Jan 28 10:25:02 Adding disk '/dev/sds1'... Jan 28 10:25:02 Mount drive command: mount -t xfs -o rw,noatime,nodiratime '/dev/sds1' '/mnt/disks/STLAFX' Jan 28 10:25:02 Mount of '/dev/sds1' failed. Error message: mount: wrong fs type, bad option, bad superblock on /dev/sds1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so

Or, hot plug didn't work and Linux thought there were two drives with the same UUID? Here is the current log, but I don't find the one for the time before the reboot. You can see I hot plugged another drive. An old Array xfs drive LAFX and it shows an error, but this is different. This drive was showing errors Jan 28 9:31:30 Disk 'ST3000DM001 9YN166 W1F0N4JK' not mounted, cannot unmount... Jan 28 9:31:30 Command not available, skipping. Jan 28 9:31:30 Unmounting disk 'Samsung SSD 840 EVO 120GB S1D5NEAD803955A'... Jan 28 9:31:30 Unmounting '/dev/sdp1'... Jan 28 9:31:31 Successfully unmounted '/dev/sdp1' Jan 28 9:31:31 Disk 'Samsung SSD 840 EVO 120GB S1D5NEAD803955A' removed successfully. Jan 28 9:31:31 Disk 'Areca ARC1280V2' not mounted, cannot unmount... Jan 28 9:31:31 Disk 'Hitachi HDS5C3030ALA630' not mounted, cannot unmount... Jan 28 9:31:31 Disk 'WDC WD20EARS 00MVWB0' not mounted, cannot unmount... Jan 28 9:31:31 Disk 'WDC WD30EZRS 00J99B0' not mounted, cannot unmount... Jan 28 9:38:39 Disk with serial 'ST3000DM001-9YN166_W1F0N4JK' auto mount is disabled, not mounted. Jan 28 9:38:39 Disk with serial 'ST3000DM001-9YN166_W1F11605' auto mount is disabled, not mounted. Jan 28 9:38:39 Disk with serial 'ARC1280V1_0000003002536795' auto mount is disabled, not mounted. Jan 28 9:38:39 Disk with serial 'HDS5C3030ALA630_MJ1323YNG1UKKC' auto mount is disabled, not mounted. Jan 28 9:38:39 Disk with serial 'WD20EARS-00MVWB0_WD-WMAZA3919347' auto mount is disabled, not mounted. Jan 28 10:03:29 Adding disk '/dev/sdo1'... Jan 28 10:03:29 Mount drive command: mount -t reiserfs -o auto,async,noatime,nodiratime '/dev/sdo1' '/mnt/disks/ST1605' Jan 28 10:03:29 Successfully mounted '/dev/sdo1' on '/mnt/disks/ST1605' Jan 28 10:03:29 Defining share 'ST1605' on file '/etc/samba/unassigned-shares/ST1605.conf' Jan 28 10:03:29 Adding share 'ST1605' to '/boot/config/smb-extra.conf' Jan 28 10:03:29 Reloading Samba configuration... Jan 28 10:03:29 Directory '/mnt/disks/ST1605' shared successfully. Jan 28 10:03:29 Command not available, skipping. Jan 28 10:19:37 Disk with serial 'ST3000DM001-9YN166_W1F0LAFX' auto mount is disabled, not mounted. Jan 28 10:24:54 Adding disk '/dev/sds1'... Jan 28 10:24:54 Mount drive command: mount -t xfs -o rw,noatime,nodiratime '/dev/sds1' '/mnt/disks/STLAFX' Jan 28 10:24:54 Mount of '/dev/sds1' failed. Error message: mount: wrong fs type, bad option, bad superblock on /dev/sds1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so Jan 28 10:25:02 Adding disk '/dev/sds1'... Jan 28 10:25:02 Mount drive command: mount -t xfs -o rw,noatime,nodiratime '/dev/sds1' '/mnt/disks/STLAFX' Jan 28 10:25:02 Mount of '/dev/sds1' failed. Error message: mount: wrong fs type, bad option, bad superblock on /dev/sds1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so

I never had a problem with the drive showing on the unassigned list. Whether using the motherboard ports or the Areca ports both always showed up. After rebooting the server, I had no problems mounting with the drive connected to the Areca. So problem solved with a reboot. Confession time: The previous problems followed uninstalling the gfardjim unassigned devices plugin, and then reinstalling your newer version without doing a reboot. It sort of worked, but not with this drive. Here are the log entries from around that time that you might find interesting as I was hot plugging drives in and out. Sometimes Areca ports and sometimes motherboard ports are being used in the list below. The drive in question is a WDC WD30EZRS, and I was also working with a Hitachi and a WD 2tb EARS both RFS formatted and connected to the Areca. Jan 27 16:25:34 Kim kernel: XFS (sdp1): Unmounting Filesystem Jan 27 16:26:06 Kim emhttp: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin remove unassigned.devices.plg Jan 27 16:26:06 Kim logger: plugin: running: anonymous Jan 27 16:26:29 Kim emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/hd_parm down sdp Jan 27 16:26:34 Kim emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/hd_parm up sdp Jan 27 16:26:45 Kim emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/disk_log sdp Jan 27 16:27:55 Kim emhttp: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin install https://github.com/dlandon/unassigned.devices/raw/master/unassigned.devices.plg Jan 27 16:27:55 Kim logger: plugin: running: anonymous Jan 27 16:27:55 Kim logger: plugin: creating: /boot/config/plugins/unassigned.devices/packages/unassigned.devices-2016.01.26a.tgz - downloading from URL https://github.com/dlandon/unassigned.devices/raw/master/unassigned.devices-2016.01.26a.tgz Jan 27 16:27:56 Kim logger: plugin: checking: /boot/config/plugins/unassigned.devices/packages/unassigned.devices-2016.01.26a.tgz - MD5 Jan 27 16:27:56 Kim logger: plugin: creating: /boot/config/plugins/unassigned.devices/packages/ntfs-3g-2015.3.14-x86_64-1.txz - downloading from URL http://slackbuilds.org/mirror/slackware/slackware64-current/slackware64/a/ntfs-3g-2015.3.14-x86_64-1.txz Jan 27 16:28:02 Kim logger: plugin: checking: /boot/config/plugins/unassigned.devices/packages/ntfs-3g-2015.3.14-x86_64-1.txz - MD5 Jan 27 16:28:02 Kim logger: plugin: running: /boot/config/plugins/unassigned.devices/packages/ntfs-3g-2015.3.14-x86_64-1.txz Jan 27 16:28:02 Kim logger: plugin: creating: /boot/config/plugins/unassigned.devices/packages/exfat-utils-1.1.1-x86_64-1_SBo.txz - downloading from URL https://github.com/dlandon/unassigned.devices/raw/master/packages/exfat-utils-1.1.1-x86_64-1_SBo.txz Jan 27 16:28:03 Kim logger: plugin: checking: /boot/config/plugins/unassigned.devices/packages/exfat-utils-1.1.1-x86_64-1_SBo.txz - MD5 Jan 27 16:28:03 Kim logger: plugin: running: anonymous Jan 27 16:28:03 Kim logger: plugin: creating: /boot/config/plugins/unassigned.devices/packages/fuse-exfat-1.1.0-x86_64-1_SBo.txz - downloading from URL https://github.com/dlandon/unassigned.devices/raw/master/packages/fuse-exfat-1.1.0-x86_64-1_SBo.txz Jan 27 16:28:04 Kim logger: plugin: checking: /boot/config/plugins/unassigned.devices/packages/fuse-exfat-1.1.0-x86_64-1_SBo.txz - MD5 Jan 27 16:28:04 Kim logger: plugin: running: anonymous Jan 27 16:28:04 Kim logger: plugin: creating: /boot/config/plugins/unassigned.devices/packages/hfsprogs-332.25-x86_64-2sl.txz - downloading from URL http://slackware.org.uk/slacky/slackware64-14.1/system/hfsprogs/332.25/hfsprogs-332.25-x86_64-2sl.txz Jan 27 16:28:06 Kim logger: plugin: checking: /boot/config/plugins/unassigned.devices/packages/hfsprogs-332.25-x86_64-2sl.txz - MD5 Jan 27 16:28:06 Kim logger: plugin: running: /boot/config/plugins/unassigned.devices/packages/hfsprogs-332.25-x86_64-2sl.txz Jan 27 16:28:06 Kim logger: plugin: creating: /boot/config/plugins/unassigned.devices/packages/libbsd-0.6.0-x86_64-1sl.txz - downloading from URL http://slackware.org.uk/slacky/slackware64-14.1/libraries/libbsd/0.6.0/libbsd-0.6.0-x86_64-1sl.txz Jan 27 16:28:08 Kim logger: plugin: checking: /boot/config/plugins/unassigned.devices/packages/libbsd-0.6.0-x86_64-1sl.txz - MD5 Jan 27 16:28:08 Kim logger: plugin: running: /boot/config/plugins/unassigned.devices/packages/libbsd-0.6.0-x86_64-1sl.txz Jan 27 16:28:08 Kim logger: plugin: creating: /boot/config/plugins/unassigned.devices/packages/parted-3.1-x86_64-1.txz - downloading from URL http://slackware.osuosl.org/slackware64-14.1/slackware64/l/parted-3.1-x86_64-1.txz Jan 27 16:28:09 Kim logger: plugin: checking: /boot/config/plugins/unassigned.devices/packages/parted-3.1-x86_64-1.txz - MD5 Jan 27 16:28:09 Kim logger: plugin: running: /boot/config/plugins/unassigned.devices/packages/parted-3.1-x86_64-1.txz Jan 27 16:28:09 Kim logger: plugin: creating: /boot/config/plugins/unassigned.devices/packages/libnl-1.1.4-x86_64-1.txz - downloading from URL http://slackware.osuosl.org/slackware64-14.1/slackware64/l/libnl-1.1.4-x86_64-1.txz Jan 27 16:28:09 Kim logger: plugin: checking: /boot/config/plugins/unassigned.devices/packages/libnl-1.1.4-x86_64-1.txz - MD5 Jan 27 16:28:09 Kim logger: plugin: running: /boot/config/plugins/unassigned.devices/packages/libnl-1.1.4-x86_64-1.txz Jan 27 16:28:09 Kim logger: plugin: running: anonymous Jan 27 16:29:35 Kim kernel: XFS (sdp1): Mounting V5 Filesystem Jan 27 16:29:36 Kim kernel: XFS (sdp1): Ending clean mount Jan 27 16:42:03 Kim kernel: ata1: exception Emask 0x50 SAct 0x0 SErr 0x40d0800 action 0xe frozen Jan 27 16:42:03 Kim kernel: ata1: irq_stat 0x00400040, connection status changed Jan 27 16:42:03 Kim kernel: ata1: SError: { HostInt PHYRdyChg CommWake 10B8B DevExch } Jan 27 16:42:03 Kim kernel: ata1: hard resetting link Jan 27 16:42:04 Kim kernel: ata1: SATA link down (SStatus 0 SControl 300) Jan 27 16:42:09 Kim kernel: ata1: hard resetting link Jan 27 16:42:09 Kim kernel: ata1: SATA link down (SStatus 0 SControl 300) Jan 27 16:42:09 Kim kernel: ata1: limiting SATA link speed to 1.5 Gbps Jan 27 16:42:14 Kim kernel: ata1: hard resetting link Jan 27 16:42:15 Kim kernel: ata1: SATA link down (SStatus 0 SControl 310) Jan 27 16:42:15 Kim kernel: ata1.00: disabled Jan 27 16:42:15 Kim kernel: ata1: EH complete Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: [sdp] killing request Jan 27 16:42:15 Kim kernel: blk_update_request: I/O error, dev sdp, sector 2930276939 Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device Jan 27 16:42:15 Kim kernel: XFS (sdp1): metadata I/O error: block 0xaea87a0b ("xlog_iodone") error 5 numblks 64 Jan 27 16:42:15 Kim kernel: XFS (sdp1): xfs_do_force_shutdown(0x2) called from line 1180 of file fs/xfs/xfs_log.c. Return address = 0xffffffff81275cff Jan 27 16:42:15 Kim kernel: XFS (sdp1): Log I/O Error Detected. Shutting down filesystem Jan 27 16:42:15 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:42:15 Kim kernel: XFS (sdp1): Please umount the filesystem and rectify the problem(s) Jan 27 16:42:15 Kim kernel: ata1.00: detaching (SCSI 2:0:0:0) Jan 27 16:42:15 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:42:16 Kim kernel: sd 2:0:0:0: [sdp] Synchronizing SCSI cache Jan 27 16:42:16 Kim kernel: sd 2:0:0:0: [sdp] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=0x00 Jan 27 16:42:16 Kim kernel: sd 2:0:0:0: [sdp] Stopping disk Jan 27 16:42:16 Kim kernel: sd 2:0:0:0: [sdp] Start/Stop Unit failed: Result: hostbyte=0x04 driverbyte=0x00 Jan 27 16:42:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:43:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:43:18 Kim kernel: scsi 1:0:0:7: Direct-Access WDC WD30EZRS-00J99B0 R001 PQ: 0 ANSI: 5 Jan 27 16:43:18 Kim kernel: sd 1:0:0:7: [sds] physical block alignment offset: 3276288 Jan 27 16:43:18 Kim kernel: sd 1:0:0:7: [sds] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB) Jan 27 16:43:18 Kim kernel: sd 1:0:0:7: Attached scsi generic sg16 type 0 Jan 27 16:43:18 Kim kernel: sd 1:0:0:7: [sds] Write Protect is off Jan 27 16:43:18 Kim kernel: sd 1:0:0:7: [sds] Mode Sense: cb 00 00 08 Jan 27 16:43:18 Kim kernel: sd 1:0:0:7: [sds] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jan 27 16:43:18 Kim kernel: sds: sds1 Jan 27 16:43:18 Kim kernel: sd 1:0:0:7: [sds] Attached SCSI disk Jan 27 16:43:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:44:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:44:16 Kim kernel: XFS (sds1): Filesystem has duplicate UUID 66b1241d-8dd2-4e4b-bd71-ad687c5cf146 - can't mount Jan 27 16:44:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:44:37 Kim kernel: XFS (sds1): Filesystem has duplicate UUID 66b1241d-8dd2-4e4b-bd71-ad687c5cf146 - can't mount Jan 27 16:45:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:45:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:46:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:46:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:47:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:47:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:48:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:48:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:49:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:49:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:49:51 Kim kernel: REISERFS (device sdr1): found reiserfs format "3.6" with standard journal Jan 27 16:49:51 Kim kernel: REISERFS (device sdr1): using ordered data mode Jan 27 16:49:51 Kim kernel: reiserfs: using flush barriers Jan 27 16:49:51 Kim kernel: REISERFS (device sdr1): journal params: device sdr1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Jan 27 16:49:51 Kim kernel: REISERFS (device sdr1): checking transaction log (sdr1) Jan 27 16:49:51 Kim kernel: REISERFS (device sdr1): Using r5 hash to sort names Jan 27 16:50:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:50:14 Kim kernel: XFS (sds1): Filesystem has duplicate UUID 66b1241d-8dd2-4e4b-bd71-ad687c5cf146 - can't mount Jan 27 16:50:23 Kim kernel: XFS (sds1): Filesystem has duplicate UUID 66b1241d-8dd2-4e4b-bd71-ad687c5cf146 - can't mount Jan 27 16:50:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:51:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:51:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:51:38 Kim apcupsd[11285]: Power failure. Jan 27 16:51:40 Kim apcupsd[11285]: Power is back. UPS running on mains. Jan 27 16:52:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:52:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:53:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:53:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:54:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:54:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:55:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:55:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:56:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:56:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:56:38 Kim kernel: sd 1:0:0:7: [sds] Synchronizing SCSI cache Jan 27 16:57:01 Kim kernel: ata1: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen Jan 27 16:57:01 Kim kernel: ata1: irq_stat 0x00000040, connection status changed Jan 27 16:57:01 Kim kernel: ata1: SError: { CommWake DevExch } Jan 27 16:57:01 Kim kernel: ata1: hard resetting link Jan 27 16:57:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:57:07 Kim kernel: ata1: link is slow to respond, please be patient (ready=0) Jan 27 16:57:11 Kim kernel: ata1: COMRESET failed (errno=-16) Jan 27 16:57:11 Kim kernel: ata1: hard resetting link Jan 27 16:57:17 Kim kernel: ata1: link is slow to respond, please be patient (ready=0) Jan 27 16:57:17 Kim kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jan 27 16:57:17 Kim kernel: ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Jan 27 16:57:17 Kim kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jan 27 16:57:17 Kim kernel: ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Jan 27 16:57:17 Kim kernel: ata1.00: ATA-8: WDC WD30EZRS-00J99B0, WD-WCAWZ0361944, 80.00A80, max UDMA/133 Jan 27 16:57:17 Kim kernel: ata1.00: 5860533168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA Jan 27 16:57:17 Kim kernel: ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Jan 27 16:57:17 Kim kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jan 27 16:57:17 Kim kernel: ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Jan 27 16:57:17 Kim kernel: ata1.00: configured for UDMA/133 Jan 27 16:57:17 Kim kernel: ata1: EH complete Jan 27 16:57:17 Kim kernel: scsi 2:0:0:0: Direct-Access ATA WDC WD30EZRS-00J 0A80 PQ: 0 ANSI: 5 Jan 27 16:57:17 Kim kernel: sd 2:0:0:0: [sds] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB) Jan 27 16:57:17 Kim kernel: sd 2:0:0:0: Attached scsi generic sg16 type 0 Jan 27 16:57:17 Kim kernel: sd 2:0:0:0: [sds] 4096-byte physical blocks Jan 27 16:57:17 Kim kernel: sd 2:0:0:0: [sds] Write Protect is off Jan 27 16:57:17 Kim kernel: sd 2:0:0:0: [sds] Mode Sense: 00 3a 00 00 Jan 27 16:57:17 Kim kernel: sd 2:0:0:0: [sds] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jan 27 16:57:17 Kim kernel: sds: sds1 Jan 27 16:57:17 Kim kernel: sd 2:0:0:0: [sds] Attached SCSI disk Jan 27 16:57:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:57:51 Kim kernel: XFS (sds1): Filesystem has duplicate UUID 66b1241d-8dd2-4e4b-bd71-ad687c5cf146 - can't mount Jan 27 16:58:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:58:11 Kim kernel: XFS (sds1): Filesystem has duplicate UUID 66b1241d-8dd2-4e4b-bd71-ad687c5cf146 - can't mount Jan 27 16:58:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:59:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:59:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 17:00:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 17:00:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned.

You have not said you rebooted or just plugged the drive in. If you didn't reboot, it may be a hot plug problem. The best way to see if a drive is recognized by unraid and subsequently by unassigned devices is to go to the 'Dashboard' and look at the row labeled 'Unassigned". You will see the disks that unraid sees as unassigned. If it does not show there, unassigned devices will not recognize it. Drive was always showing in the list of drives recognized by unassigned devices, you could change the mount name without problems, but pressing mount just brought it back to the same screen without any results. I did reboot the server and it (newly formatted XFS drive) is now mounted on a motherboard port without issue as un unassigned device. Perhaps mounting and unmounting multiple times from multiple ports gets things in a mishmash that only a reboot can cure??? What can we do to test the Areca mount issue?

Now after moving the drive back and forth between an Areca port and a motherboard port it won't mount in either place ?? The RFS drives are still happily mounted on the Areca.

I updated to the latest version (thanks dlandon for updating this) I am converting drives from RFS to XFS, and I added a drive to the array, formatted it XFS and then pulled it out of the array and connected it via this plugin. This newly formatted XFS drive will not mount at all when connected to my Areca card, but when moved back to the motherboard port, it will mount fine. I have an Areca 1280 with a bunch of 3tb drives on it and it works fine with unRaid. Other Areca connected RFS drives mount fine with this unassigned devices plugin too. But this newly formatted 3TB WD EZRS drive would not.

A few months ago I tried to use this plugin to move from rfs to xfs disk format. I formatted the xfs drive in the plugin but after copying the files from the rfs drive, unRaid did not like the new xfs disk. I couldn't mount it in the array. At that time someone said that the xfs format laid down by this plugin was not unRaid array compatible. Is this still true?

+1 for the filtering request.

When in China and accessing my USA unRaid box running openvpn, I typically get a delay before I can access local or any internet through the vpn from my Win10 laptop. Then next time it is instant, and then it won't connect at all. I can only describe it as sort of works .... (used to access local files, and get to gmail now that even my phone can't get my gmail in China) c:\>ping google.com Pinging google.com [216.58..221.78] with 32 bytes of data Request timed out Request timed out Request timed out Request timed out

OK, that is the way mine is too. If you changed your server IP from .190 to something else like .231 would your OpenVPN installation need to be deleted and reinstalled with new certs and new clients? When I changed the IP of my unRaid server (not my VPN server) everything stopped working.

No my original server ip was 192.168.3.142. I needed to change it to 196.168.3.82 and the VPN server IP was left at the default of 10.8.0.0 Because of the openvpn would not work after I changed the IP, I have moved back to .142 I can change the address of the VPN Server easily, but is it safe to make it 192.168.3.0?? Won't I get a conflict with my router gateway at 192.168.3.1? How do you run yours??

Is the only way to fix, to uninstall OpenVPN and reinstall everything regenerating the certs on the server and all the clients?

Because of IP conflicts I had to change the IP address of my server. Now OpenVPN won't start and the logs show Thu Nov 12 21:38:25 2015 OpenVPN 2.3.6 x86_64-slackware-linux-gnu [sSL (OpenSSL)] [LZO] [EPOLL] [MH] [iPv6] built on Dec 10 2014 Thu Nov 12 21:38:25 2015 library versions: OpenSSL 1.0.1p 9 Jul 2015, LZO 2.03 Thu Nov 12 21:38:25 2015 MANAGEMENT: Socket bind failed on local address [AF_INET]192.168.3.142:10000: Cannot assign requested address Thu Nov 12 21:38:25 2015 Exiting due to fatal error Thu Nov 12 21:38:45 2015 OpenVPN 2.3.6 x86_64-slackware-linux-gnu [sSL (OpenSSL)] [LZO] [EPOLL] [MH] [iPv6] built on Dec 10 2014 Thu Nov 12 21:38:45 2015 library versions: OpenSSL 1.0.1p 9 Jul 2015, LZO 2.03 Thu Nov 12 21:38:45 2015 MANAGEMENT: Socket bind failed on local address [AF_INET]192.168.3.142:10000: Cannot assign requested address Thu Nov 12 21:38:45 2015 Exiting due to fatal error Sat Nov 14 09:03:05 2015 OpenVPN 2.3.6 x86_64-slackware-linux-gnu [sSL (OpenSSL)] [LZO] [EPOLL] [MH] [iPv6] built on Dec 10 2014 Sat Nov 14 09:03:05 2015 library versions: OpenSSL 1.0.1p 9 Jul 2015, LZO 2.03 Sat Nov 14 09:03:05 2015 MANAGEMENT: Socket bind failed on local address [AF_INET]192.168.3.142:10000: Cannot assign requested address Sat Nov 14 09:03:05 2015 Exiting due to fatal error and default via 192.168.3.1 dev br0 metric 1 127.0.0.0/8 dev lo scope link 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.42.1 192.168.3.0/24 dev br0 proto kernel scope link src 192.168.3.82 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1

+1 I vote for it too.

After using this for a few days, I would say that the upload and download speeds are in the ballpark compared with speedtest.net running on a wired computer and running Chrome browser. However the ping times are way longer. I am on Comcast here and my pings are in the 30's This utility reports pings over 90 ms and some over 100. Other than this, looks like it works ok.

I guess I need to try to connect remotely from another Google fiber location and run the speed test from there. I did try and copy large files across the vpn and per the Windows 8 and Windows 10 file explorer was getting 1.5 - 2.2 mb/sec over the 100mbs Comcast line.

What is the expected slowdown to expect from running open vpn server? Got it running. Intel i7 Unraid server on gigabit Google Fiber, and connecting remotely with an i5 W10 laptop via 100/10 Comcast and ran a speedtest, I get 30/10 max through the vpn. I lose 70%of my download speed but nothing on my upload. Is this typical overhead for openvpn? GF isn't the limiting factor. What overhead are others finding?

Presently I have my VPN set up in my Router. With Google Fiber coming, I will have to give up my DD-WRT router unless I want to hack my own bypass to Google fiber network box. I prefer to run with supported, known working stuff, so am not eager to hack the Google Fiber Network Box. However, I need to create a secure VPN entry to my entire lan which the GFNB is not able to do. Will OpenVPN on unRaid do that? Is the plugin more or less suited to this than the Docker? My main use case is to access my entire network remotely, not just my unRaid box. (I am not wanting to hide my internet downloading.)

6.2 will have a 4.2 kernel.

Perfect time for a SMART long test! Since the long test examines every sector, it should (if the code is done right) reinitialize the overall counters, as to how many are really remapped. It's probably a coincidence, but can't help noticing that both VALUE and WORST for Reallocated_Sector_Ct is 57, same as the leading integers of the RAW 57240. Could be a bug there. Unfortunately, that doesn't make sense from a programmatic view, as it's 57 and 57000, VERY different numbers. The one way you can estimate the number of spares a given drive model has is to find one with a number of reallocated sectors and see how far it dropped the VALUE for Reallocated_Sector_Ct. It dropped it 43% for your drive with a count of 57240, so if you extrapolate that, you get an estimate of about 130,000 spare sectors, an obviously crazy number! What we need is a SMART report for another ST3000DM001-9YN166 with reallocated sectors, to see what the real spare count should be. You are at 6300 operational hours now. Back at 2860 hours, something went wrong, ostensibly with uncorrectable sectors. The reported LBA numbers are meaningless though, so it's hard to tell what actually was wrong. Certainly not confidence building in this drive. All other numbers look fine, with a very few runtime bad blocks and uncorrectable sectors, nothing that correlates with 57000 of them though, or even 240 of them. Kinda funny but the Raw_Read_Error_Rate has improved with every single SMART report, has never been worse than 99 (almost perfect). Ok here is the long smart test report and the preclear report for another ST3000DM001-9YN166. Sorry it doesn't have issues though.... Found another one with errors. ED2 smartctl -a -A /dev/sdn smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.0.4-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.14 (AF) Device Model: ST3000DM001-9YN166 Serial Number: W1F0LAFX LU WWN Device Id: 5 000c50 05246d833 Firmware Version: CC9E User Capacity: 3,000,592,982,016 bytes [3.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Mon Aug 24 20:25:32 2015 CDT SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 584) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 338) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x3081) SCT Status supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 116 099 006 Pre-fail Always - 104284160 3 Spin_Up_Time 0x0003 093 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 099 099 020 Old_age Always - 1186 5 Reallocated_Sector_Ct 0x0033 057 057 036 Pre-fail Always - 57240 7 Seek_Error_Rate 0x000f 075 060 030 Pre-fail Always - 36360856 9 Power_On_Hours 0x0032 093 093 000 Old_age Always - 6378 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 848 183 Runtime_Bad_Block 0x0032 097 097 000 Old_age Always - 3 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 068 068 000 Old_age Always - 32 188 Command_Timeout 0x0032 100 097 000 Old_age Always - 11 18 18 189 High_Fly_Writes 0x003a 098 098 000 Old_age Always - 2 190 Airflow_Temperature_Cel 0x0022 057 046 045 Old_age Always - 43 (Min/Max 35/50) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 99 193 Load_Cycle_Count 0x0032 094 094 000 Old_age Always - 12620 194 Temperature_Celsius 0x0022 043 054 000 Old_age Always - 43 (0 7 0 0 0) 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 1148h+05m+44.061s 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 20989294796726 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 178319632353629 SMART Error Log Version: 1 ATA Error Count: 28 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 28 occurred at disk power-on lifetime: 2860 hours (119 days + 4 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 ff ff ff ef 00 01:35:54.630 READ DMA EXT 25 00 00 ff ff ff ef 00 01:35:54.625 READ DMA EXT 25 00 90 ff ff ff ef 00 01:35:49.050 READ DMA EXT 25 00 d8 ff ff ff ef 00 01:35:49.042 READ DMA EXT 25 00 68 ff ff ff ef 00 01:35:49.041 READ DMA EXT Error 27 occurred at disk power-on lifetime: 2860 hours (119 days + 4 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 ff ff ff ef 00 01:34:21.313 READ DMA EXT ea 00 00 ff ff ff af 00 01:34:21.039 FLUSH CACHE EXT 25 00 00 ff ff ff ef 00 01:34:21.019 READ DMA EXT 35 00 08 ff ff ff ef 00 01:34:21.019 WRITE DMA EXT 35 00 08 ff ff ff ef 00 01:34:21.019 WRITE DMA EXT Error 26 occurred at disk power-on lifetime: 2860 hours (119 days + 4 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 ff ff ff ef 00 01:34:17.122 READ DMA EXT 25 00 00 ff ff ff ef 00 01:34:16.265 READ DMA EXT 25 00 10 ff ff ff ef 00 01:34:16.188 READ DMA EXT 25 00 00 ff ff ff ef 00 01:34:14.071 READ DMA EXT 25 00 00 ff ff ff ef 00 01:34:13.801 READ DMA EXT Error 25 occurred at disk power-on lifetime: 2860 hours (119 days + 4 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 ff ff ff ef 00 01:34:09.809 READ DMA EXT ea 00 00 ff ff ff af 00 01:34:09.558 FLUSH CACHE EXT 25 00 00 ff ff ff ef 00 01:34:09.539 READ DMA EXT 35 00 08 ff ff ff ef 00 01:34:09.538 WRITE DMA EXT 35 00 08 ff ff ff ef 00 01:34:09.538 WRITE DMA EXT Error 24 occurred at disk power-on lifetime: 2860 hours (119 days + 4 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 ff ff ff ef 00 01:34:06.061 READ DMA EXT 25 00 00 ff ff ff ef 00 01:34:06.058 READ DMA EXT ea 00 00 ff ff ff af 00 01:34:05.782 FLUSH CACHE EXT 25 00 00 ff ff ff ef 00 01:34:05.757 READ DMA EXT 35 00 08 ff ff ff ef 00 01:34:05.757 WRITE DMA EXT SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 6377 - # 2 Short offline Completed without error 00% 6372 - # 3 Short offline Completed without error 00% 6372 - # 4 Short offline Completed without error 00% 2164 - # 5 Extended offline Aborted by host 90% 1721 - # 6 Short offline Completed without error 00% 1720 - # 7 Short offline Completed without error 00% 1417 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. preclear_rpt_W1F0N4JK_2015-07-19.zip preclear_start_W1F0MED2_2015-08-17.zip

Final results a second time are fully the same as the first time. No change. I've posted all the reports as an attachment to see if we can figure out this one... Love these 3tb Seagate drives faster than a speeding bullet. Others have had lots of issues with them, but I've been lucky with only one in about 20 drives. preclear_reports.zip