Everything posted by loady
-
ProFTPD Plugin for unRAID v6.8.x
Hmmm..i understand what your saying..and i hear it everytime i look to doing this and every time it scares me off. I wouldnt say the shares are critical data..but i would hate it if some little git deleted my entire movie folder for fun !!...pity theres not more development on this side of things..i just want to be able to be anywhere and grab whatever files i want out of any share without the worrying, i wouldnt be giving anyone else access to it personally. Also...i tried to install the plugin but it came back with... installing plugin: proftpd file /tmp/plugin-prepare: successfully wrote INLINE file contents /bin/bash /tmp/plugin-prepare ... ************************************************************* * ProFTPD plugin installation started... ************************************************************* success file /tmp/plugin-cleanup: successfully wrote INLINE file contents /bin/bash /tmp/plugin-cleanup ... success file /boot/config/plugins/proftpd/README: already exists file /boot/config/plugins/proftpd/device_status.png: downloading from -q --no-check-certificate https://github.com/SlrG/unRAIDplugins/raw/master/proftpd/device_status.png ... bad download, deleting root@warptower:/boot/config/plugins#
-
ProFTPD Plugin for unRAID v6.8.x
+1 for that, i have a router running dd-wrt with dyn dns setup, can you just set yourself up to see all your shares and have access and use a c0MpL3x pa55word to avoid getting it hacked ??
-
Preclear.sh results - Questions about your results? Post them here.
i never checked the memory as my 8GB kit arrived so i just put that in, i still dont think memory was an issue..just a glitch maybe ??..heres the result of second preclear..looks good this time.. == invoked as: ./preclear_disk.sh -M 4 /dev/sdb == SAMSUNG HD204UI S2H7J1BZ912023 == Disk /dev/sdb has been successfully precleared == with a starting sector of 63 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 6:26:36 (86 MB/s) == Last Cycle's Zeroing time : 5:42:57 (97 MB/s) == Last Cycle's Post Read Time : 14:19:40 (38 MB/s) == Last Cycle's Total Time : 26:30:23 == == Total Elapsed Time 26:30:23 == == Disk Start Temperature: 25C == == Current Disk Temperature: 27C, == ============================================================================ 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.
-
Preclear.sh results - Questions about your results? Post them here.
Hmmm.. i dont suspect the memory, i have done no less than 5 preclears straight on different drives and all have passed, i am going to stick in 8gb shortly anyway, whats the best way to test the memory, do i need to add a monitor and boot server and wait for option to run mem test or can i invoke it via telnet session ?
-
Preclear.sh results - Questions about your results? Post them here.
not sure if this is a bad sign...in short.. ========================================================================1.13 == invoked as: ./preclear_disk.sh -M 4 /dev/sdb == == Disk /dev/sdb has NOT been successfully precleared == Postread detected un-expected non-zero bytes on disk== == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 6:32:11 (85 MB/s) == Last Cycle's Zeroing time : 5:43:22 (97 MB/s) == Last Cycle's Post Read Time : 14:02:46 (39 MB/s) == Last Cycle's Total Time : 26:19:30 == == Total Elapsed Time 26:19:31 == == Disk Start Temperature: 26C == == Current Disk Temperature: 25C, == ============================================================================ No SMART attributes are FAILING_NOW