tr0910

Have our leading dockers experts encountered these issues? https://thehftguy.wordpress.com/2016/11/01/docker-in-production-an-history-of-failure/ Sounds depressing. via Tapatalk

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

I see the Limetech sync is updated. Has anyone updated theirs yet? How much reconfiguration did you have to do because of the Resilio naming changes?

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.

The P4000 chassis for the S2600 motherboards is fussy about UPS power. My APC Backup UPS Pro 1300 units don't seem to ouput the kind of power they like. This results in the server instantly turning into a screaming demon if the power goes out. The fans all go to high speed and the power consumption of the server jumps from 75W to 300W. Thankfully this rarely happens, but if it does, the run time on battery UPS is severely restricted. I just just installed a Cyberpower CP1500PFCLCD - PFC Sinewave UPS Systems - Pure Sine Wave | 100% Active PFC I can confirm that the P4000 chassis likes this power much better when on battery, and continues to purr like it does from line power. It continues to run quietly with low power consumption.

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

Sync is updated to v2.4 and running 6.2 with the existing ones seems to be problems. Can you update? https://forum.resilio.com/topic/42726-latest-desktop-build-240/

It actually isn't all the clients, but only the clients that had saved the credentials for the read/write user while it was being used. Now the server is completely wide open again this shouldn't be needed for any client. Only clients that had never logged in while it was private are able to get in today. Blame Windows 10, or unRaid?

I have one 6.1.9 server where I attempted to update the share permissions to private, giving read/write access to one user (not root) This worked for a bit, but suddenly I could no longer access the server. After fighting with it for hours, even setting every share back to public did not help. Finally it just worked again even though it had been set back to public hours earlier.... Today I updated to 6.2 on this server, and I can no longer access the SMB shares via W10 anymore on any client. It asks for a login, and is trying to use the user I had set up previously for read/write access. Login with that user into unRaid doesn't help. Likely a Windows issue more than unRaid, but let me ask anyways.....

During testing using MC I renamed the inaccessible share and it instantly needed a login, when trying to access it. It should have been public. Just to check, I stopped the array and restarted the array, and the renamed share showed up as expected, and it is public as expected. but Windows cannot access it at all now. It doesn't even give a login screen, just goes directly to "you do not have permission to access \\tower\renamedShare I can create a new root level folder on the server, and the creator laptop can access it fine. The other laptops get a login screen when trying to access that share. Files moved into that share are full accessible from the creator laptop, but inaccessible from the other laptop. Here is my share.cfg file and full diagnostics are attached. # Generated settings: shareDisk="yes" shareUser="e" shareUserInclude="disk2,disk3,disk4,disk5,disk6,disk7,disk8" shareUserExclude="" shareSMBEnabled="yes" shareNFSEnabled="yes" shareNFSFsid="101" shareAFPEnabled="no" shareInitialOwner="Administrator" shareInitialGroup="Domain Users" shareCacheEnabled="yes" shareCacheFloor="2000000" shareMoverSchedule="40 3 * * *" shareMoverLogging="yes" fuse_remember="330" shareAvahiEnabled="yes" shareAvahiSMBName="%h" shareAvahiSMBModel="Xserve" shareAvahiAFPName="%h-AFP" shareAvahiAFPModel="Xserve" kim-diagnostics-20160902-1631.zip

Yes, I would agree, as I have seen this too, but the same one login credentials are used for all the shares. 4 shares are working as expected, and 2 are not. Doesn't that mean that the correct credentials are being used? The credentials manager in control panel shows the correct ones being used, and there are no other credentials on the laptop. Testing further with net use.....

I had upgraded the security giving one user R/W access to some necessary shares and locking the other shares to read only. The security for these shares was changed from public to private and after fighting with Win10 for several hours, both laptops were able to access the files after saving the login information. However today three days later, 2 of these shares suddenly became inaccessable, while the other 4 continue to work as expected. The first one is still visible and all files are viewable, but accessing the jpg files results in a ("you do not have permission to access this file") error. Other text files are accessible without issue. Rebooting the workstations and the server did not change this. Setting the SMB share security back to public also did not change this error. The second share with problems is totally inaccessible. No files are viewable. Even after I change the access for the share back to public, there is no possibility of accessing this share from either laptop. The error "you might not have permission to use this network resource. The handle is invalid" Running 6.1.9 on this server....

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"

Can anyone add more to this?? Is it not reliable? Even when done by CLI??

Yeah, .118 virtio drivers made it work. It now has Windows 10 specific drivers so we no longer have to use 8.1 drivers. The stable drivers .102 are not stable.

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