RokleM

Looking forward to the upgrade form the 5.12 to 5.13 train. Personally, I'd love to see 5.13.9 so I can test (on this controller) some of the beta hardware.

Took a risk and rebooted and it's working... something in the upgrade process made the disk not accessible but somehow is restored during reboot. Very odd.

Literally never had a problem with that disk for 5 years until I started this upgrade. The sever will no longer see it but it works fine in windows. Jan 12 11:10:40 nas emhttpd: req (8): cmd=/plugins/dynamix.plugin.manager/scripts/plugin&arg1=update&arg2=unRAIDServer.plg&csrf_token=**************** Jan 12 11:10:40 nas emhttpd: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin update unRAIDServer.plg Jan 12 11:10:40 nas root: plugin: creating: /tmp/unRAIDServer.sh - from INLINE content Jan 12 11:10:40 nas root: plugin: running: /tmp/unRAIDServer.sh Jan 12 11:10:40 nas root: plugin: creating: /tmp/unRAIDServer.zip - downloading from URL https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.8.1-x86_64.zip Jan 12 11:10:49 nas root: plugin: creating: /tmp/unRAIDServer.md5 - downloading from URL https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.8.1-x86_64.md5 Jan 12 11:10:49 nas root: plugin: creating: /tmp/unRAIDServer.sh - from INLINE content Jan 12 11:10:49 nas root: plugin: running: /tmp/unRAIDServer.sh Jan 12 11:11:00 nas kernel: usb 5-1: USB disconnect, device number 2

My Dockers are also now down after the failed upgrade: Warning: parse_ini_file(/boot/config/docker.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 43 Warning: array_replace_recursive(): Expected parameter 2 to be an array, bool given in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 43 And my VM's: Warning: parse_ini_file(/boot/config/domain.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.vm.manager/include/libvirt_helpers.php on line 460 root@nas:/boot# ls -alh total 8.0K drwx------ 10 root root 8.0K Jan 12 11:10 ./ drwxr-xr-x 20 root root 440 Jan 11 19:47 ../

First upgrade failure I think ever... my other server worked. plugin: updating: unRAIDServer.plg plugin: downloading: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.8.1-x86_64.zip ... done plugin: downloading: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.8.1-x86_64.md5 ... done writing flash device - please wait... Archive: /tmp/unRAIDServer.zip plugin: run failed: /bin/bash retval: 1

Hello all, maybe I'm missing it, but anyway to add local host entries? There are plenty of ways to add local DNS lookup (need to resolve *nix boxes and other that don't do netbios) when running on a full VM/host, but not finding a way to do this in an unraid docker.

Copied bzroot, bzimage, make_boot, and syslinux over. Then did a make bootable and it appears to have worked.

Followed step 1. Could not find kernel image: linux boot: Make Bootable v1.2 Volume in drive E is UNRAID Volume Serial Number is asdf Press any key to continue . . . E:\syslinux\syslinux.exe -maf E: The system cannot find the path specified. Completed Press any key to continue . . .

Something I should keep an eye on? Was going to make this one the parity becuase of the speed...

Any issues with these two new 4T's? ========================================================================1.13 == invoked as: ./preclear_disk.sh -c 3 -M 4 -m rxxxm /dev/sdh == ST4000DX000-1CL160 xx == Disk /dev/sdh has been successfully precleared == with a starting sector of 1 == Ran 3 cycles == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 8:51:02 (125 MB/s) == Last Cycle's Zeroing time : 8:01:22 (138 MB/s) == Last Cycle's Post Read Time : 19:29:42 (57 MB/s) == Last Cycle's Total Time : 27:32:04 == == Total Elapsed Time 91:32:21 == == Disk Start Temperature: 29C == == Current Disk Temperature: 40C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdh /tmp/smart_finish_sdh ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 117 100 6 ok 152625539 Seek_Error_Rate = 75 100 30 ok 32540935 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 99 100 0 ok 1 Airflow_Temperature_Cel = 60 71 45 near_thresh 40 Temperature_Celsius = 40 29 0 ok 40 Hardware_ECC_Recovered = 35 100 0 ok 152625539 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 3. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 3. 0 sectors were pending re-allocation after post-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 3. 0 sectors were pending re-allocation after post-read in cycle 2 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 3. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ========================================================================1.13 == invoked as: ./preclear_disk.sh -m rxxxm -c 3 -M 4 /dev/sdi == ST4000DM000-1F2168 xx == Disk /dev/sdi has been successfully precleared == with a starting sector of 1 == Ran 3 cycles == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 9:36:21 (115 MB/s) == Last Cycle's Zeroing time : 8:27:13 (131 MB/s) == Last Cycle's Post Read Time : 19:41:18 (56 MB/s) == Last Cycle's Total Time : 28:09:31 == == Total Elapsed Time 94:12:21 == == Disk Start Temperature: 28C == == Current Disk Temperature: 31C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdi /tmp/smart_finish_sdi ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 117 99 6 ok 125490320 Seek_Error_Rate = 60 100 30 ok 1130916 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 97 100 0 ok 3 Airflow_Temperature_Cel = 69 72 45 near_thresh 31 Temperature_Celsius = 31 28 0 ok 31 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 3. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 3. 0 sectors were pending re-allocation after post-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 3. 0 sectors were pending re-allocation after post-read in cycle 2 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 3. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change.

Thoughts on this one? == Last Cycle's Pre Read Time : 6:11:42 (134 MB/s) == Last Cycle's Zeroing time : 6:26:03 (129 MB/s) == Last Cycle's Post Read Time : 12:58:02 (64 MB/s) ** Changed attributes in files: /tmp/smart_start_sde /tmp/smart_finish_sde ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 118 100 6 ok 183174328 Seek_Error_Rate = 60 100 30 ok 1107922 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 99 100 0 ok 1 Airflow_Temperature_Cel = 63 71 45 near_thresh 37 Temperature_Celsius = 37 29 0 ok 37 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. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change.

Seek_Error_Rate = 44 44 30 near_thresh 790278696138 I would only be concerned with this parameter, since the normalized value seems to be getting close to its failure threshold, and odds are the starting value was 100 or 200. The number of re-allocated sectors did not change, and that is good, but the number 343 is very high, and most people would RMA the drive based only on the number of re-allocated sectors. Since the seek error rate is iffy, and the re-allocated sector count high, I'd RMA. (the other parameters that are near their thresholds just have very high thresholds... they are not an issue) Thanks. Surprisingly, it's still under warranty. I will see if seatools shows it as bad enough to warranty.

I just finished pre-clearing an old drive that use to be in a DNS-323 (converting from that unit). I have some concerns with the data in bold. Is this drive a concern? I know it's also one that people seem to be iffy about (1.5t seagate). ========================================================================1.13 == invoked as: ./preclear_disk.sh -c 1 -M 4 -m xxxxxxxxxx /dev/hda == ST31500541AS 5XW05ES1 == Disk /dev/hda has been successfully precleared == with a starting sector of 64 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 5:44:50 (72 MB/s) == Last Cycle's Zeroing time : 7:58:24 (52 MB/s) == Last Cycle's Post Read Time : 11:28:37 (36 MB/s) == Last Cycle's Total Time : 25:12:52 == == Total Elapsed Time 25:12:52 == == Disk Start Temperature: 29C == == Current Disk Temperature: 29C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_hda /tmp/smart_finish_hda ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 110 113 6 ok 26687111 Seek_Error_Rate = 44 44 30 near_thresh 790278696138 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 97 98 0 ok 3 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. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 343 sectors had been re-allocated before the start of the preclear. 343 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change.