tr0910

I have ssh_config confirmed working with 6.2.4 and have locked my server down significantly. Secondly, I wanted to bolt it down tighter with denyhosts, but cannot get it to start running. Attempts to start it result in this: Dec 16 12:51:13 Server1 sudo: root : TTY=unknown ; PWD=/usr/local/emhttp ; USER=root ; COMMAND=/usr/bin/env python /usr/bin/denyhosts.py --daemon --config=/boot/config/plugins/denyhosts/denyhosts.cfg Dec 16 12:51:33 Server1 sudo: root : TTY=unknown ; PWD=/usr/local/emhttp ; USER=root ; COMMAND=/usr/bin/env python /usr/bin/denyhosts.py --daemon --config=/boot/config/plugins/denyhosts/denyhosts.cfg Dec 16 12:51:42 Server1 emhttp: cmd: /usr/local/emhttp/plugins/denyhosts/scripts/rc.denyhosts buttonstart Dec 16 12:51:42 Server1 sudo: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/env python /usr/bin/denyhosts.py --daemon --config=/boot/config/plugins/denyhosts/denyhosts.cfg Dec 16 12:53:10 Server1 sudo: root : TTY=unknown ; PWD=/usr/local/emhttp ; USER=root ; COMMAND=/usr/bin/env python /usr/bin/denyhosts.py --daemon --config=/boot/config/plugins/denyhosts/denyhosts.cfg This is still what I get in the logs after restricting logins to keyfiles only. The nasties won't quite trying to break in. Dec 16 10:53:30 Server1 sshd[20738]: Received disconnect from 218.65.30.123 port 8927:11: [preauth] Dec 16 10:53:30 Server1 sshd[20738]: Disconnected from 218.65.30.123 port 8927 [preauth] Dec 16 11:11:20 Server1 sshd[27831]: Received disconnect from 221.194.44.231 port 44343:11: [preauth] Dec 16 11:11:20 Server1 sshd[27831]: Disconnected from 221.194.44.231 port 44343 [preauth] Dec 16 11:16:02 Server1 sshd[29642]: Received disconnect from 221.194.47.229 port 46792:11: [preauth] Dec 16 11:16:02 Server1 sshd[29642]: Disconnected from 221.194.47.229 port 46792 [preauth] Dec 16 11:20:34 Server1 sshd[31476]: Received disconnect from 121.18.238.114 port 41878:11: [preauth] Dec 16 11:20:34 Server1 sshd[31476]: Disconnected from 121.18.238.114 port 41878 [preauth] Dec 16 11:23:32 Server1 sshd[32601]: Received disconnect from 121.18.238.114 port 55780:11: [preauth] Dec 16 11:23:32 Server1 sshd[32601]: Disconnected from 121.18.238.114 port 55780 [preauth] Dec 16 11:24:13 Server1 sshd[458]: Received disconnect from 221.194.47.208 port 41636:11: [preauth] Dec 16 11:24:13 Server1 sshd[458]: Disconnected from 221.194.47.208 port 41636 [preauth] Dec 16 11:26:38 Server1 sshd[1556]: Unable to negotiate with 123.31.32.5 port 62192: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1 [preauth] Dec 16 11:35:25 Server1 sshd[5040]: Received disconnect from 121.123.153.46 port 52816:11: Bye Bye [preauth] Dec 16 11:35:25 Server1 sshd[5040]: Disconnected from 121.123.153.46 port 52816 [preauth] Dec 16 11:45:10 Server1 sshd[8839]: Received disconnect from 221.194.47.224 port 46493:11: [preauth] Dec 16 11:45:10 Server1 sshd[8839]: Disconnected from 221.194.47.224 port 46493 [preauth] Dec 16 11:45:27 Server1 sshd[9018]: Received disconnect from 121.18.238.98 port 34741:11: [preauth] Dec 16 11:45:27 Server1 sshd[9018]: Disconnected from 121.18.238.98 port 34741 [preauth] Dec 16 11:45:28 Server1 sshd[9061]: Received disconnect from 121.18.238.104 port 35216:11: [preauth] Dec 16 11:45:28 Server1 sshd[9061]: Disconnected from 121.18.238.104 port 35216 [preauth] Dec 16 11:51:29 Server1 sshd[10941]: Received disconnect from 221.194.44.224 port 36581:11: [preauth] Dec 16 11:51:29 Server1 sshd[10941]: Disconnected from 221.194.44.224 port 36581 [preauth] Dec 16 11:53:00 Server1 sshd[11382]: Received disconnect from 221.194.47.224 port 46110:11: [preauth] Dec 16 11:53:00 Server1 sshd[11382]: Disconnected from 221.194.47.224 port 46110 [preauth] Dec 16 11:54:35 Server1 sshd[11907]: Received disconnect from 221.194.47.229 port 44266:11: [preauth] Dec 16 11:54:35 Server1 sshd[11907]: Disconnected from 221.194.47.229 port 44266 [preauth] Dec 16 12:07:49 Server1 sshd[16083]: Received disconnect from 221.194.44.195 port 44063:11: [preauth] Dec 16 12:07:49 Server1 sshd[16083]: Disconnected from 221.194.44.195 port 44063 [preauth] Dec 16 12:09:45 Server1 sshd[16694]: Received disconnect from 121.18.238.114 port 36323:11: [preauth] Dec 16 12:09:45 Server1 sshd[16694]: Disconnected from 121.18.238.114 port 36323 [preauth] Dec 16 12:10:05 Server1 sshd[16847]: Received disconnect from 221.194.47.249 port 49320:11: [preauth] Dec 16 12:10:05 Server1 sshd[16847]: Disconnected from 221.194.47.249 port 49320 [preauth] Dec 16 12:10:14 Server1 sshd[16894]: Received disconnect from 221.194.44.219 port 49424:11: [preauth] Dec 16 12:10:14 Server1 sshd[16894]: Disconnected from 221.194.44.219 port 49424 [preauth] Dec 16 12:19:13 Server1 sshd[19711]: Received disconnect from 121.18.238.98 port 42423:11: [preauth] Dec 16 12:19:13 Server1 sshd[19711]: Disconnected from 121.18.238.98 port 42423 [preauth] Dec 16 12:41:06 Server1 sshd[26559]: Received disconnect from 221.194.44.219 port 34636:11: [preauth] Dec 16 12:41:06 Server1 sshd[26559]: Disconnected from 221.194.44.219 port 34636 [preauth] Dec 16 13:06:06 Server1 sshd[3875]: Invalid user admin from 185.110.132.202 port 43627 Dec 16 13:06:06 Server1 sshd[3875]: input_userauth_request: invalid user admin [preauth] Dec 16 13:06:07 Server1 sshd[3875]: Received disconnect from 185.110.132.202 port 43627:11: Bye Bye [preauth] Dec 16 13:06:07 Server1 sshd[3875]: Disconnected from 185.110.132.202 port 43627 [preauth] Dec 16 13:12:24 Server1 sshd[6388]: Received disconnect from 121.18.238.98 port 51933:11: [preauth] Dec 16 13:12:24 Server1 sshd[6388]: Disconnected from 121.18.238.98 port 51933 [preauth] Dec 16 13:38:27 Server1 sshd[16782]: Received disconnect from 221.194.44.219 port 37815:11: [preauth] Dec 16 13:38:27 Server1 sshd[16782]: Disconnected from 221.194.44.219 port 37815 [preauth] Dec 16 13:39:43 Server1 sshd[17256]: Received disconnect from 221.194.47.224 port 47834:11: [preauth] Dec 16 13:39:43 Server1 sshd[17256]: Disconnected from 221.194.47.224 port 47834 [preauth] Dec 16 13:40:39 Server1 sshd[17633]: Received disconnect from 221.194.47.229 port 42289:11: [preauth] Dec 16 13:40:39 Server1 sshd[17633]: Disconnected from 221.194.47.229 port 42289 [preauth] Dec 16 13:41:34 Server1 sshd[18010]: Invalid user support from 185.110.132.202 port 54147 Dec 16 13:41:34 Server1 sshd[18010]: input_userauth_request: invalid user support [preauth] Dec 16 13:41:35 Server1 sshd[18010]: Received disconnect from 185.110.132.202 port 54147:11: Bye Bye [preauth] Dec 16 13:41:35 Server1 sshd[18010]: Disconnected from 185.110.132.202 port 54147 [preauth] Dec 16 14:06:54 Server1 sshd[27998]: Unable to negotiate with 123.31.32.5 port 62083: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1 [preauth] Dec 16 14:16:42 Server1 sshd[31874]: Received disconnect from 185.110.132.202 port 41156:11: Bye Bye [preauth] Dec 16 14:16:42 Server1 sshd[31874]: Disconnected from 185.110.132.202 port 41156 [preauth]

Have you got it running on a 6.3 server too?

Both denyhosts and ssh?? I hadn't installed it yet thinking from the comments above it was no longer working. Will try it now... Thanks...

Is anyone successfully running this plugin on 6.2 or 6.3??

You are quite a fortune teller. The disks both precleared fine in another server, and when I shut this server down to run memtest, it immediately failed. This was my only server without ECC memory, and I am sure I ran memtest on it when it was set up a year ago. I hope I don't have corrupted files....

That would be scary. It would really make you question every thing the server had been doing recently. I don't need unRAID scrambling my files. Memtest time via Tapatalk

On 6.2.4 I have 2 disks that are suddenly failing to post read at all. I am guessing it is a configuration problem. I wanted to try and run it via command line. Is this likely to result in a different result? Or is something else wrong? See the log preclear_disk_sdo: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --cycles 1 --no-prompt /dev/sdo preclear_disk_sdo: Pre-Read: dd if=/dev/sdo of=/dev/null bs=2097152 iflag=direct preclear_disk_sdn: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --cycles 1 --no-prompt /dev/sdn preclear_disk_sdn: Pre-Read: dd if=/dev/sdn of=/dev/null bs=2097152 iflag=direct preclear_disk_sdo: Zeroing: dd if=/dev/zero of=/dev/sdo bs=2097152 seek=1 conv=fdatasync,noerror oflag=direct preclear_disk_sdo: Zeroing: dd pid [15956] preclear_disk_sdn: Zeroing: dd if=/dev/zero of=/dev/sdn bs=2097152 seek=1 conv=fdatasync,noerror oflag=direct preclear_disk_sdn: Zeroing: dd pid [26846] preclear_disk_sdo: Post-Read: dd if=/dev/sdo bs=512 count=4096 skip=1 iflag=direct preclear_disk_sdo: Post-Read: dd pid [3189] preclear_disk_sdo: Post-Read: dd if=/dev/sdo bs=2097152 skip=1 iflag=direct 2>/tmp/.preclear/sdo/dd_output | cmp - /dev/zero &>/tmp/.preclear/sdo/cmp_out preclear_disk_sdo: Post-Read: dd pid [3232] preclear_disk_sdo: Post-Read: fail - disk not zeroed preclear_disk_sdo: preclear_disk_sdo: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --cycles 1 --no-prompt /dev/sdo preclear_disk_sdo: Pre-Read: dd if=/dev/sdo of=/dev/null bs=2097152 iflag=direct preclear_disk_sdn: Post-Read: dd if=/dev/sdn bs=512 count=4096 skip=1 iflag=direct preclear_disk_sdn: Post-Read: dd pid [13590] preclear_disk_sdn: Post-Read: dd if=/dev/sdn bs=2097152 skip=1 iflag=direct 2>/tmp/.preclear/sdn/dd_output | cmp - /dev/zero &>/tmp/.preclear/sdn/cmp_out preclear_disk_sdn: Post-Read: dd pid [13627] preclear_disk_sdn: Post-Read: fail - disk not zeroed preclear_disk_sdn: preclear_disk_sdo: Zeroing: dd if=/dev/zero of=/dev/sdo bs=2097152 seek=1 conv=fdatasync,noerror oflag=direct preclear_disk_sdo: Zeroing: dd pid [13096] preclear_disk_sdo: Post-Read: dd if=/dev/sdo bs=512 count=4096 skip=1 iflag=direct preclear_disk_sdo: Post-Read: dd pid [29811] preclear_disk_sdo: Post-Read: dd if=/dev/sdo bs=2097152 skip=1 iflag=direct 2>/tmp/.preclear/sdo/dd_output | cmp - /dev/zero &>/tmp/.preclear/sdo/cmp_out preclear_disk_sdo: Post-Read: dd pid [29881] preclear_disk_sdo: Post-Read: fail - disk not zeroed preclear_disk_sdo: preclear_disk_sdo: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --cycles 1 --no-prompt /dev/sdo preclear_disk_sdo: Pre-Read: dd if=/dev/sdo of=/dev/null bs=2097152 iflag=direct

Finished post read on sdq, and sdp is midway through the post read, so I declare a success. Here is the preclear log: preclear_disk_sdp: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --cycles 1 --no-prompt /dev/sdp preclear_disk_sdp: Pre-Read: dd if=/dev/sdp of=/dev/null bs=2097152 iflag=direct preclear_disk_sdq: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --cycles 1 --no-prompt /dev/sdq preclear_disk_sdq: Pre-Read: dd if=/dev/sdq of=/dev/null bs=2097152 iflag=direct preclear_disk_sdn: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --cycles 1 --no-prompt /dev/sdn preclear_disk_sdn: Pre-Read: dd if=/dev/sdn of=/dev/null bs=2097152 iflag=direct preclear_disk_sdq: Zeroing: dd if=/dev/zero of=/dev/sdq bs=2097152 seek=1 conv=fdatasync,noerror oflag=direct preclear_disk_sdq: Zeroing: dd pid [5201] preclear_disk_sdp: Zeroing: dd if=/dev/zero of=/dev/sdp bs=2097152 seek=1 conv=fdatasync,noerror oflag=direct preclear_disk_sdp: Zeroing: dd pid [25915] preclear_disk_sdq: Post-Read: dd if=/dev/sdq bs=512 count=4096 skip=1 iflag=direct preclear_disk_sdq: Post-Read: dd pid [24376] preclear_disk_sdq: Post-Read: dd if=/dev/sdq bs=2097152 skip=1 iflag=direct 2>/tmp/.preclear/sdq/dd_output | cmp - /dev/zero &>/tmp/.preclear/sdq/cmp_out preclear_disk_sdq: Post-Read: dd pid [24412] preclear_disk_sdp: Post-Read: dd if=/dev/sdp bs=512 count=4096 skip=1 iflag=direct preclear_disk_sdp: Post-Read: dd pid [11119] preclear_disk_sdp: Post-Read: dd if=/dev/sdp bs=2097152 skip=1 iflag=direct 2>/tmp/.preclear/sdp/dd_output | cmp - /dev/zero &>/tmp/.preclear/sdp/cmp_out preclear_disk_sdp: Post-Read: dd pid [11224] preclear_disk_sdq:

Updated, but didn't reboot. Running now, both on sdp and sdq. (since both gave unexpected results) Note: sdn was also running a preclear on a failing disk, so that could be causing issues. I've aborted it and restarted as well. So we should get results from it too.

Diagnostics attached. Lots of sense.key nonsense. Unsure what matters in this syslog. Perhaps some hardware errors will be noticed by someone else. (@turl or @robj) (FYI this is a Xeon 1220 Sandybridge on a Supermicro X9SCM with 20GB Ram and the affected devices are all connected to an IBM1015 via a Norco 4224 chassis.) server1-diagnostics-20161031-1101.zip

I may have already done that. Not sure if this is what you mean?? 2 days ago I set all 3 disks to do a complete preclear again. The disk that did the full preclear initially did another full preclear including a post read verify as JoeL's script would have done. Disk 2 replicated the previous preclear as follows ############################################################################################################################ # # # unRAID Server Pre-Clear of disk /dev/sdp # # Cycle 1 of 1, partition start on sector 64. # # # # # # Step 1 of 5 - Pre-read verification: [6:42:18 @ 82 MB/s] SUCCESS # # Step 2 of 5 - Zeroing the disk: [6:33:30 @ 84 MB/s] SUCCESS # # Step 3 of 5 - Writing unRAID's Preclear signature: SUCCESS # # Step 4 of 5 - Verifying unRAID's Preclear signature: SUCCESS # # Step 5 of 5 - Post-Read verification: [0:00:00 @ MB/s] SUCCESS # # # # # # # # # # # # # # # ############################################################################################################################ # Cycle elapsed time: 13:15:57 | Total elapsed time: 13:16:00 # ############################################################################################################################ ############################################################################################################################ # # # S.M.A.R.T. Status # # # # # # ATTRIBUTE INITIAL CYCLE 1 STATUS # # 5-Reallocated_Sector_Ct 0 0 - # # 9-Power_On_Hours 11432 11445 Up 13 # # 194-Temperature_Celsius 30 34 Up 4 # # 196-Reallocated_Event_Count 0 0 - # # 197-Current_Pending_Sector 0 0 - # # 198-Offline_Uncorrectable 0 0 - # # 199-UDMA_CRC_Error_Count 0 0 - # # # # # # # # # # # ############################################################################################################################ # SMART overall-health self-assessment test result: PASSED # ############################################################################################################################ --> ATTENTION: Please take a look into the SMART report above for drive health issues. --> RESULT: Preclear finished succesfully. root@Server1:/usr/local/emhttp# The 3rd disk only confirmed that the disk was already precleared as follows. ############################################################################################################################ # # # unRAID Server: verifying Preclear State of '/dev/sdq' . # # Verifying disk '/dev/sdq' for unRAID's Preclear State. # # # # # # Step 1 of 2 - Verifying unRAID's Preclear MBR: SUCCESS # # Step 2 of 2 - Verifying if disk is zeroed: 5:04:49 @ 164 MB/s SUCCESS # # # # # # # # # # # # # # # # # # ** Time elapsed: 5:04:49 | Current speed: 164 MB/s | Average speed: 164 MB/s # # # ############################################################################################################################ # Total elapsed time: 5:05:02 # ############################################################################################################################ --> RESULT: SUCCESS! Disk /dev/sdq has been verified precleared! root@Server1:/usr/local/emhttp# Is this user error or an actual bug? I would have expected 3 full preclears like this... ############################################################################################################################ # # # unRAID Server Pre-Clear of disk /dev/sdo # # Cycle 1 of 1, partition start on sector 64. # # # # # # Step 1 of 5 - Pre-read verification: [7:05:27 @ 117 MB/s] SUCCESS # # Step 2 of 5 - Zeroing the disk: [6:58:00 @ 119 MB/s] SUCCESS # # Step 3 of 5 - Writing unRAID's Preclear signature: SUCCESS # # Step 4 of 5 - Verifying unRAID's Preclear signature: SUCCESS # # Step 5 of 5 - Post-Read verification: [7:05:24 @ 117 MB/s] SUCCESS # # # # # # # # # # # # # # # ############################################################################################################################ # Cycle elapsed time: 21:08:57 | Total elapsed time: 21:08:57 # ############################################################################################################################ ############################################################################################################################ # # # S.M.A.R.T. Status # # # # # # ATTRIBUTE INITIAL CYCLE 1 STATUS # # 5-Reallocated_Sector_Ct 0 0 - # # 9-Power_On_Hours 8525 8546 Up 21 # # 183-Runtime_Bad_Block 0 0 - # # 184-End-to-End_Error 0 0 - # # 187-Reported_Uncorrect 0 0 - # # 190-Airflow_Temperature_Cel 36 38 Up 2 ->Failed in Past<- # # 197-Current_Pending_Sector 0 0 - # # 198-Offline_Uncorrectable 0 0 - # # 199-UDMA_CRC_Error_Count 0 0 - # # # # # # # ############################################################################################################################ # SMART overall-health self-assessment test result: PASSED # ############################################################################################################################ --> ATTENTION: Please take a look into the SMART report above for drive health issues. --> RESULT: Preclear finished succesfully. root@Server1:/usr/local/emhttp#

var/log doesn't have a preclear.disk.log file to send you... after checking with MC on 6.3rc3

Doesn't want to download via Firefox or Chrome... (6.3rc3) warning:%20copy(/var/log/preclear.disk.log):%20failed%20to%20open%20stream:%20No%20such%20file%20or%20directory%20in%20/usr/local/emhttp/plugins/dynamix/include/Download.php%20on%20line%2023/log/SERVER1-preclear.disk-20161030-1316.zip

Could you please update and test if this error has been corrected? Yes, this have fixed the array drives from showing up, thanks.... I am still getting an intermittent failure to do the post read as follows: ############################################################################################ unRAID Server Pre-Clear of disk /dev/sdp # # Cycle 1 of 1, partition start on sector 64. # # # # # # Step 1 of 5 - Pre-read verification: [6:42:18 @ 82 MB/s] SUCCESS # # Step 2 of 5 - Zeroing the disk: [6:33:30 @ 84 MB/s] SUCCESS # # Step 3 of 5 - Writing unRAID's Preclear signature: SUCCESS # # Step 4 of 5 - Verifying unRAID's Preclear signature: SUCCESS # # Step 5 of 5 - Post-Read verification: [0:00:00 @ MB/s] SUCCESS # # # How can it do a post read in 0 seconds??

The SCSI devices plugin allows disks connected to a controller to be known by their proper name/model, but it doesn't automatically add temperature reading to the Main page. To read SMART information from these disks, it may be required to configure the controller settings. See Main -> diskname -> SMART settings. Ah, yes bubbaq was able to get some things working, but I don't recall he ever got temperatures from the Areca's. Perhaps my memory was faulty with it "just working" automatically on 6.1.9 via your plugin. You are such a magic worker.... and us Areca users are a small group. Thanks for what you have done in bringing the Areca controller more mainstream in UnRaid. I'm not seeing any documentation for this part of your plugin other than the help text that says. By default automatic controller selection is done by smartctl to read the SMART information. Certain controllers however need specific settings for smartctl to work. Use this setting to select your controller type and fill-in the specific disk index and device name for your situation. Use the manufacturer's documentation to find the relevant information. Each disk may have its own specific setting overruling the 'default' setting (see global SMART settings under Disk Settings). I can see the smart controller type of Areca, but setting to this from default doesn't change anything. For the Areca smart controller setup, I see 4 additional config spots filled in with "1.4", "1.28", "1.4", "/dev/sdh". The drive is attached via Areca IDE channel 8 as follows to /dev/sdh on the Areca 1231 IDE Channel 8 Model Name ST3000DM001-9YN166 Serial Number W1F0ZTJA Firmware Rev. CC9F Disk Capacity 3000.6GB Current SATA Mode SATA300+NCQ(Depth32) Supported SATA Mode SATA300+NCQ(Depth32) Error Recovery Control (Read/Write) N.A. Disk APM Support Yes Device State Normal Timeout Count 0 Media Error Count 0 SMART Read Error Rate 118(6) SMART Spinup Time 92(0) SMART Reallocation Count 100(36) SMART Seek Error Rate 87(30) SMART Spinup Retries 100(97) SMART Calibration Retries N.A.(N.A.) The Areca hardware monitor shows this drive temperature at 31 deg C even though the drive is spun down There is also the other Smart Settings. I am guessing they are not so important to getting the temps working?? Smart Notification Value "Use Default" Smart Notification Tolerance Value "Use Default" Smart Attribute Notifications "Use Default"

Same here. I had 3 drivers showing up via unassigned devices as expected. But 3 more array devices show up in the preclear plugin screen, one of which was parity 2. Areca is involved in this server as well using the dynamix SCSI plugin. via Tapatalk Unassigned Devices is working ok for you, guys? Yes it is for me. via Tapatalk

Same here. I had 3 drivers showing up via unassigned devices as expected. But 3 more array devices show up in the preclear plugin screen, one of which was parity 2. Areca is involved in this server as well using the dynamix SCSI plugin. via Tapatalk

Latest version of SCSI devices 9/15 on both 6.22 and 6.3rc3 show flat unchanging temperatures of 30 degrees C for Areca attached drives. I seem to recall you were showing correct temperatures on Areca on 6.1.9?? Before your plugin, I used bubbaq solution and it never showed anything for temperature on the tower/main screen for Areca attached drives. Areca models 1280, 1231 and 1260 with bios 1.49 are all showing the same temp issue on the tower/main screen.

I too have been enjoying this tool, has helped with some testing I've been doing. Thanks! We're getting off-topic though, perhaps it deserves its own thread? Running the latest version - the Total column looks more like an average to me. I would have expected a sum? Is this plugin still around? The link doesn't work... Squid updated it to 6.2 here http://lime-technology.com/forum/index.php?topic=29009.msg492140#msg492140

The following worked Have an array disk or user share mapped into the container config area. I have container /data mapped to unRaid array /disk2. Then it is simply docker ps docker exec -t -i 37fcc75e886d /bin/bash cp /data/btsync ./btsyncnew rename 's/btsync/oldsync/' * rename 's/btsyncoldnew/btsync/' * chmod 777 btsync The rename was required as I couldn't copy over top of the same file. "cp: cannot create regular file ‘/opt/btsync/btsync’: Text file busy"

I'm not in China now but could test via team viewer

Yes that works fine. But is 6.1.9 missing the "docker cp" into container option??

Here is the difference in the help files. On 6.1.9 the docker copy command is only one way?? Copy out only?? root@Tower619:~# docker cp --help Usage: docker cp [OPTIONS] CONTAINER:PATH HOSTDIR|- Copy files/folders from a PATH on the container to a HOSTDIR on the host running the command. Use '-' to write the data as a tar file to STDOUT. root@Tower62rc2:/boot# docker cp --help Usage: docker cp [OPTIONS] CONTAINER:SRC_PATH DEST_PATH|- docker cp [OPTIONS] SRC_PATH|- CONTAINER:DEST_PATH Copy files/folders between a container and the local filesystem Use '-' as the source to read a tar archive from stdin and extract it to a directory destination in a container. Use '-' as the destination to stream a tar archive of a container source to stdout.

On ver 6.2 rc2 the following works to copy a file from the flash drive into a running container. But on 6.1.9 it doesn't. On 6.1.9 it complains about the path. Also the help for "docker cp" on 6.1.9 doesn't show an option to copy in, only to copy out of the docker container to the host. docker cp /boot/btsync be45c973020a:/opt/btsync/btsync Is there a way to copy a file into a docker container running on 6.1.9?

I have a reiser disk that I plugged into the 6.1.9 server via unassigned devices and see the following errors in the u/d log. And even though the disk mounts, is shared and shows up in Windows Explorer, navigating to it brings me to the password required page, and no way can I browse the disk from Windows. From telnet the following errors spit out when I try to do a "ls" /bin/ls: cannot access Pictures: Permission denied /bin/ls: cannot access Music: Permission denied Jul 14 17:54:46 Adding disk '/dev/sdg1'... Jul 14 17:54:46 Mount drive command: /sbin/mount -t reiserfs -o auto,async,noatime,nodiratime '/dev/sdg1' '/mnt/disks/ST_NC4Q' Jul 14 17:54:57 Successfully mounted '/dev/sdg1' on '/mnt/disks/ST_NC4Q'. Jul 14 17:54:57 Error: No valid smb users defined. Share '/mnt/disks/ST_NC4Q' cannot be accessed. Jul 14 17:54:57 Defining share 'ST_NC4Q' on file '/etc/samba/unassigned-shares/ST_NC4Q.conf' Jul 14 17:54:57 Adding share 'ST_NC4Q' to '/boot/config/smb-extra.conf' Jul 14 17:54:57 Reloading Samba configuration... Jul 14 17:54:57 Directory '/mnt/disks/ST_NC4Q' shared successfully. Jul 14 17:55:57 Device '/dev/sdg1' script file not found. 'ADD' script not executed.