danioj

I can't see any obvious issues that would cause the test to fail. I have just tested both my main and redundant instances of this plugin though and both mine fail too. However, I have been using them all morning. I am even using one of them now. Have you tried to just connect anyway? The test says that: Perhaps the reason it fails has something to do with the fact it is running in a Container on a Server on a different Subnet with just ports forwarded to the connectivity ports. I don't know. I wouldn't worry - if it works - all is good! Give it a try!

Have you recently move the folder or done anything to manipulate the permissions? TBH it doesn't really matter. The last time I had this issue the ONLY way I found to restore the correct permissions was to delete the config folder. Delete the Container. Start again. I know that is probably NOT what you want to hear BUT it worked. Thankfully this Docker is REALLY easy to set up. And barring having to re-deploy my auto-login certificates again which took a little while, the actual setup only took 5 mins.

@gfjardim here is a nice thought regarding possible future features of the new BETA Plugin / Preclear Script from RobJ as a result of a support thread posted: http://lime-technology.com/forum/index.php?topic=47697.msg457468#msg457468 For your consideration.

Running at Full is raging loud, too loud for me. Is there an easy way to tweak the bios settings to different fan levels to see the speed change? Or do I need to set the level, save and reboot to see the change? Well, it depends what your board supports. For instance my IPMI interface only lets me select the following options: You should log into your IPMI interface and see what options there are to select. In this way you can "Tweak" without going into BIOS and rebooting etc. You could always NOT let the system get into unRAID (stop it at the boot screen) and just change the fan settings. Let it run for a while then look in the BIOS at temps. This is not a great suggestion BUT I am running out of them.

Saw your edit. Turn Smart Fan mode off. Set them to full. Or I guess you could play with the Smart mode temperature ranges BUT I would just get them running at full. The fans are quiet anyway.

Have to be quick as I'm on my way out (so excuse the poorly worded and brief response) but yes, get into your BIOS or IPMI interface (assuming it allows it) and set those fans to run at full speed! I know this function is coming in the IPMI Plugin BUT you don't need it. EDIT: however as I mentioned to another user earlier today, even in the 40's why worry? The new disks of today have acceptable operating temperatures up to ~70'C. Chill! (Pun intended)

Given most new drives have acceptable operating temps up to 70'c and you're getting temps of ~ 40'c under load. Well, I don't see that there is anything to be unhappy about.

Those temps under load?

All mine are 10" from an ASRock C2550D4I. Any longer and it would start to look messy! I agree, 8" would be fine for probably 3/4 of the ports (using the board I mention).

This ends up being more of a pain than its worth. Trust me, note down the servers and the important config and just start again with a new config folder for this container. It might sound and feel like a pain BUT you WILL end up spending less time in the long run!

That was quick!! ? Very easy fix. I don't have a system that I can set up two parity disks, so let me know if it worked. Like a charm. Let me know if you need anything else 6.2 related you need testing. No important data, pure test setup.

That was quick!! ?

I wanted to share that the current version of Unassigned Devices "seems" at first glance to be playing well with 6.2.0-beta18. Although interestingly at the point where the initial Parity Sync is happening the 2nd Parity drive still shows in the Unassigned Devices section even though it has been assigned to the 2nd Parity slot in the Array and the Array is started and a Parity Sync is underway: Yep, still there even when the Parity Sync has finished. Mount is greyed out though so at least you can't DO anything bad. UD probably needs to be taught to ignore that 2nd Parity I imagine. For giggles I clicked the preclear icon to see what happened: Didn't want to press Start

I think I was a little hasty in my apprehension about this work, so for that I am Sorry. After taking in all the facts (and also TBH some surprising behaviour by some of the longer serving members of the community) I would like to do my bit to support. I will use your BETA preclear version throughout my testing of unRAID 6.2 soon™ Edition through BETA -> RC -> FINAL: http://lime-technology.com/forum/index.php?topic=47427.0 I will work into what I am doing the ability to test as much as I can (e.g. between testing rebuilds etc) the following disks. And I have started them ALL off on a preclear run right now .... Parity 1: Western Digital Blue WD800AAJS (00PSA0) 80GB 7200 RPM 8MB Cache SATA 3.0Gb/s Parity 2: Western Digital Blue WD800AAJS (00PSA0) 80GB 7200 RPM 8MB Cache SATA 3.0Gb/s Data 1: Seagate Barracuda 7200.10 ST380815AS (9CY131-020) 80GB 7200 RPM 8MB Cache SATA 3.0Gb/s Data 2: Western Digital WD Blue WD800JD (60LSA5) 80GB 8MB Cache SATA 3.0Gb/s Data 3: Western Digital WD Blue WD800JD (60LSA5) 80GB 8MB Cache SATA 3.0Gb/s 6.2.0-beta18: *For those who notice, don't worry about the temperatures. As it is my test server with test disks I didn't double check the fans. They had failed. Replaced them as of the verify so temperatures are in order. Links below are screenshots from the Plugins' setup page and from Unassigned Devices on the Main Tab (if you're checking compatibility). UPDATE 1: Preclear on ALL drives was successful. Links below indicating status are once again from Unassigned Devices and Main Tab for results (including eye popup at finished) indication and indicating Start of an ALL disk Verify (including eye popup during). UPDATE 2: ALL Disk Verify on ALL drives was successful. Message reports back that the drive is now precleared. UPDATE 3: Then I tried to follow the instructions to use the exisiting preclear plugin to run the Test and Postread Verify from the older plugin. Unfortunately I could not. After placing the Joe.L version (original) version of the script on the flash, here is what happened: Firstly I note that once I pressed the X it cleared the status BUT now no-where does it indicate that the drive is preceared. We should probably preserve that pre cleared flag and indicate it somewhere on the GUI. Then I tried to run the Test and I got a blank status field in the GUI (which was not helpful). I had to click the eye to see what had happened. Of course, the stupid disk.cfg issue. Can we resolve this? After adding a disk to a slot, starting the Array, stopping the Array and then removing the disk (which meant I now have a disk.cfg) I tried to run a Test again. I was once again I got a blank status field in the GUI (which was not helpful). I had to click the eye to see what had happened. This was the -R issue reported by johnnies.black and BRiT indicating that the version of "sfdisk" included in unraid 6.2.0 beta 18 is different, and doesn't seem to support the uppercase R option. Not knowing where to go from here I decided to try the next step, which was the Run Post Read Verify. Unfortunately I was not able to complete this either. The popup window opened, it allowed me to select "Run post read verify" but when I clicked Start nothing happened. It just sat there. At which point the GUI also hung for a while. At this point. Mainly due to the HANG I went to the CLI and looked at the syslog. It appeared unRAID was spamming my Syslog with messages about the disks. I wasn't sure if what was happening was due to the preclear or something going on in unRAID. I made an educated (although it might have been a poor one) decision to decide it was something happening in unRAID (don't yet know if it is harmless) so I grabbed the diagnostics file and posted about it here: https://lime-technology.com/forum/index.php?topic=47408.msg453990#msg453990 With only assigning the disks to the Array left and doing a Check Parity I decided to take stock at what the failed attempts at the above operations had done to the status in the Preclear GUI and the Unassigned Devices GUI and this was the result. Messages and Status' were confused. It also didn't seem to grasp that the Seagate had been precleared either. UPDATE 4: I started the Array fine. Formatted the disks (nice to see the default is XFS now as I didn't check this) and started a Parity Sync. UPDATE 5: Finished (without step 4 as indicated above). Parity Sync Complete. unRAID 6.2-beta18 seems to have been fine with the work that the Plugin has done. Dual Parity Protected Array** **Note: For those that are 6.2 conscious, I have noted how the 2nd Parity Disk appears in the Unassigned Devices area and have posted this in the Unassigned Devices support thread here: https://lime-technology.com/forum/index.php?topic=45807.msg453974#msg453974 gfjardim: Please let me know if you would like anything else tested / done. Hope this helps.

He won't give you the authorisation or you can't get hold of him!? Haven't you incorporated both scripts (Original and Faster) into the Plugin already? Have you been asked to remove them? If it is a matter of contact I am SURE someone can help facilitate that. If it is the latter then I would be SHOCKED. Your Plugin has added much needed front end to an almost ESSENTIAL task. I won't speculate further until you confirm. Is there perhaps another reason WHY you are re-writing it too? Are you looking to add further functionality? If so what is this functionality? If at all possible (if you really don't have to) I think given the exposure your plugin gets via Community Applications - not to mention how well you have done at making a CLI exercise task so easy and user friendly via the GUI - I think it should only use one of the two very well tested scripts. Although it is officially unsupported by LT, a preclear is a task that almost every user of unRAID does. All new users of unRAID are advised to do it by Staff, Mod's and Experienced Users alike. At the moment the ability to do it is STABLE. Your Plugin is great as all it does is add a front end to those stable scripts whose (once executed) outcomes are very assured. My issue is that by introducing an untested scripts into the mix does a few things: - Removes confidence in the preclear script; - Introduces possibilities for error / bugs etc; - Add's confusion etc Now, like I said above, IF you are being told you can't use the scripts then I guess you have no choice BUT I think that would be a big step back from where we are today. If it isn't broken don't fix it. Can you add some more context to your decision?

So, do we have any reason to suggest that these issue have anything to do with the Seagate 8TB drive or is this issue a candidate for a separate support thread?

Does anyone know where "fuse.conf" is placed AND if it is persistent? I am trying to edit it to enable edit fuse.conf to include user_allow_other so I can pass the option allow_other shfs option but AFAIK it will be ignored until you also edit /etc/fuse.conf to include user_allow_other.

Perhaps. I haven't used screen since the earlier version of the Plugin. I updated the plugin without taking head of release notes clearly AND didn't know I had to go in and switch them on. All good now though. Thanks for the explanation.

Have you actually gone to Settings->Nerd Pack and checked that screen has been selected for install? Earlier versions of the plugin installed all the options, but a while ago it was upgraded to only install the selected options. Very strange. When I went to Settings > Nerd Pack, all the tools were Off. I turned them on... and hit Apply. Not all turned on. At least screen which is the one I most need is On. Thank you guys for pointing me in the right direction. H. I just had this issue too. Exactly the same. I went to run a script in a screen session and the command wasn't found. Checked the Plugin Status, Installed. Checked my Backup Server and the same thing happened. I start to think it must be the Plugin given screen wasn't available on 2 different servers. Only when I saw your post did I think to check on the settings page... Same as you ALL of the packages were set to OFF on both the Main and Backup Systems. I have enabled them now and, like you, I now have screen running. Not sure how long my server has been running with these off or what caused the issue. However given it happened on 2 seperate servers I can only guess the issue is systemic. Interestingly there are also 2 packages which won't enable: - cksfv-1.3.14-x86_64-1_slack.txz - fdupes-1.51-x86_64-3_slack.txz

I haven't done one, but about 10 posts up (ish) another user posted their results: I did one recently, not because of a failure but for upgrading a 3tb drive, duration was similar to a parity check/sync. Event: unRAID Data rebuild: Subject: Notice [TOWER7] - Data rebuild: finished (0 errors) Description: Duration: 14 hours, 55 minutes, 14 seconds. Average speed: 149.0 MB/sec Importance: normal I'd be interested to see what the math behind the "estimated time" is. Parity rebuilt requires the reading all of the data disks and writing to the Parity disk. What average speed is being reported? Also, are you doing anything with the Array at the same time? Reading / Writing?

None at all or just reporting that no bytes trimmed?

IMHO the Noctua NF-F12 PWM fans are Perfect. I have them in my Setup and they are awesome. http://noctua.at/en/nf-f12-pwm http://www.newegg.com/Product/Product.aspx?Item=N82E16835608026

I don't think it's a good idea for a plugin to access the Internet to connect to an SFTP server. I'm also not comfortable that I know enough to do it securely. For the time being, I feel that UD is accomplishing its intended goals and won't be adding any new features. Fair enough, I can understand those arguments.

Dan, do you think there is any chance of adding support for being able to mount an SFTP location?

Yeah, sorry, just updated my last post. I've been able to work around this by forwarding the same port through both my router and the new modem. Thanks! I am glad that you have seemingly solved your issue - BUT - is there any issue why you are running NAT (Network Address Translation) on two connected devices? Typically with NAT only the router needs to have a public IP address (also called Gateway, usually a DSL or Cable Modem). All devices behind the NAT router have private IP addresses - usually starting with 192.168 or 10 etc. These addresses are of course only valid within the router network. The most common setup is simple and is a network with one gateway (say DSL or Cable modem). The gateway has a public (WAN) IP address and does NAT. All computers connected to this gateway get assigned a private IP address (as described above). The gateway takes care routing the data from / to computers connected to it. To make a computer connected to gateway accessible from Internet a port forwarding setting is required. This scenario of course represents a single level of NAT (just one router on network that does network address translation) and that in most cases is what you want. As johnathanm indicates you have Double NAT. Double NAT is a scenario where multiple routers on network are doing network address translation. Common example is the one you have which is a Cable or DSL modem, to which a Wi-Fi router is connected. Both modem and router have NAT enabled. Computers on the network are typically only connected to the Wi-Fi router. As you have found, even if port forwarding is setup on Wi-Fi router, the computer is not accessible from the Internet, because the WiFi router itself doesn't have public IP address. It has a private IP address within the network of DSL/Cable modem. Assuming this is not by design, there are multiple ways to resolve this. So with regards to your setup I will make the assumptions that: - You have the typical problematic setup in a modem (DSL, Cable, Fiber, etc) and a Wireless router connected to the modem; - Both the wireless router and the modem have web administration interface, each can be configured with a web browser and you have the connection details. As for solutions (and you have already come across the first one): 1 - Port forward between the devices - NOT RECOMMENDED Note that all this does is route the traffic and get a specific application (for the ports being forwarded) to work. Note that this does NOT eliminate Double-NAT. Unless you have a specific need for Double-NAT this is not recommended. There are network related reasons BUT the practical one is that you will have to do this for EVERY port you want to forward making what should be a simple and manageable thing - much harder. 2- Put the wireless router in the modem's DMZ (if supported) - NOT RECOMMENDED A DMZ (demilitarized zone) is a common feature of a router that allows you to chose one client to which all traffic is forwarded. If your modem supports DMZ you could do this: - Find out the WAN address of the wireless router. For this you might need to log in to the WiFi router admin interface and look at the Status page (most router's have status pages which show relevant information about the WAN connection). - Log in to the modem web administration interface, find the DMZ settings and put the WiFi router's IP WAN address there. Note that (Like option 1) this does NOT eliminate Double-NAT. Unless you have a specific need for Double-NAT this is not recommended. 3 - Put the Modem in "bridged mode" - RECOMMENDED Bridged mode means that NAT and DHCP functions on it will be disabled. Some routers call it "bridged mode", some simply allow you to disable NAT and DHCP. Unfortunately some devices simply don't support bridged mode at all. If the modem doesn't support this - you "could" disable it on the router and run NAT on the modem. I will leave you to your manufacturers instructions for doing this - but the principals are the same (in that it requires logging on to the management interface of the device and enabling (or disabling) the appropriate option) as option 2. This is the BEST option IMHO. If you manage to switch the modem to bridged mode, all port forwarding (along with all your other network config) needs to be configured in one place, on the router. You might not have needed all that but I still enjoyed sourcing / writing it! 8