Frank1940

As I recall, the problem resulted from your removal of the 'bad' drive from the array. If you have simply inserted the drive into the case, it would have been available for 'preclearing'. But once the bad drive goes physically missing, any drive that is installed in the case will be automatically added to the array and the rebuilt process started (if the drive is equal to or larger in size). If you think about it this is the way most of us want it to work as it makes replacing a defective drive a simple process. Remember the preclear script is NOT a part of the Limetech's unRAID distribution package but a 'user developed' utility.

With unRAID 32bit v5 it was definitely possible to run out of memory preclearing. Not sure if it still an issue with 64bit v6. I'm not aware of anyone trying as many as you are suggesting so you may just have to try it and see. Can't imagine you really need all of them at once though so you might go with fewer at one time. Unless you break it by running too many you should be able to use your server for other things while preclearing, such as loading data to the drives already precleared so maybe not that important to do it all at once anyway. Thanks for the reply, I have Unraid V6.1.3? ( I think). ....... On a side note, i do notice that my cpu usage is 24-29%, so i'm going to try to load 3 more and see what happens. I seem to recall that the issue is actually the memory required for each disk being precleared, not the CPU usage.

http://lime-technology.com/forum/index.php?topic=37541.0 See here: http://lime-technology.com/forum/index.php?topic=37541 BTW, this is included in the WIKI for upgrading from version 5 to version 6. http://lime-technology.com/wiki/index.php/Upgrading_to_UnRAID_v6#Plugins

Did you install the Preclear Plugin using the instructions in the first post of this thread? Or you you running the preclear script from the command line either on a monitor or a telnet session? This plugin is actually started from the GUI on the 'Settings' page. You will find the 'Preclear Disk' icon near the bottom of the screen.

Can you try reinstall this package and run a preclear test to see if the bug occur again? Not at the present time. I am running a preclear (three cycles) on a 3TB drive. I will do it when I get that drive done (Guessing Saturday) and installed as the new parity drive on my Test Bed server . Just to double check what you want done. I assume you want me to uninstall the plugin and then reinstall it. Or did you want me to empty the config/plugins/preclear.disk folder also? (I do have a 1TB drive that I can use for a test.) OK. Did two things: First, updated to version 6.0.2. Second, uninstall Preclear Plugin and reinstalled the package. = = = = = Disk Temperature: 24C, Elapsed Time: 0:00:27 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdf = cycle 1 of 1, partition start on sector 64 = Disk Pre-Read in progress: 0% complete = ( 1,200,537,600 bytes of 1,000,204,886,016 read ) 44.4 MB/s = = = = = = = = = = Disk Temperature: 24C, Elapsed Time: 0:00:32 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdf = cycle 1 of 1, partition start on sector 64 = Disk Pre-Read in progress: 0% complete = ( 1,400,627,200 bytes of 1,000,204,886,016 read ) 53.0 MB/s = = = = = = = = = = Disk Temperature: 24C, Elapsed Time: 0:00:37 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdf = cycle 1 of 1, partition start on sector 64 = Disk Pre-Read in progress: 0% complete = ( 1,600,716,800 bytes of 1,000,204,886,016 read ) 53.8 MB/s = = = = = = = = = = Disk Temperature: 24C, Elapsed Time: 0:00:41 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdf = cycle 1 of 1, partition start on sector 64 = Disk Pre-Read in progress: 0% complete = ( 1,800,806,400 bytes of 1,000,204,886,016 read ) 41.8 MB/s = = = = = = = = = = Disk Temperature: 24C, Elapsed Time: 0:00:46 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdf = cycle 1 of 1, partition start on sector 64 = Disk Pre-Read in progress: 0% complete = ( 2,000,896,000 bytes of 1,000,204,886,016 read ) 40.1 MB/s = = = = = = = = = = Disk Temperature: 24C, Elapsed Time: 0:00:52 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdf = cycle 1 of 1, partition start on sector 64 = Disk Pre-Read in progress: 0% complete = ( 2,200,985,600 bytes of 1,000,204,886,016 read ) 45.0 MB/s = = = = = = = = = = Disk Temperature: 24C, Elapsed Time: 0:00:57 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdf = cycle 1 of 1, partition start on sector 64 = Disk Pre-Read in progress: 0% complete = ( 2,401,075,200 bytes of 1,000,204,886,016 read ) 52.9 MB/s = = = = = = = = = = Disk Temperature: 24C, Elapsed Time: 0:01:01 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdf = cycle 1 of 1, partition start on sector 64 = Disk Pre-Read in progress: 0% complete = ( 2,601,164,800 bytes of 1,000,204,886,016 read ) 42.1 MB/s = = = = = = = = = = Disk Temperature: 24C, Elapsed Time: 0:01:06 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdf = cycle 1 of 1, partition start on sector 64 = Disk Pre-Read in progress: 0% complete = ( 2,801,254,400 bytes of 1,000,204,886,016 read ) 43.6 MB/s = = = = = = = = = = Disk Temperature: 24C, Elapsed Time: 0:01:12 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdf = cycle 1 of 1, partition start on sector 64 = Disk Pre-Read in progress: 0% complete = ( 3,001,344,000 bytes of 1,000,204,886,016 read ) 54.7 MB/s = = = = = = = = = = Disk Temperature: 25C, Elapsed Time: 0:01:16 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdf = cycle 1 of 1, partition start on sector 64 = Disk Pre-Read in progress: 0% complete = ( 3,201,433,600 bytes of 1,000,204,886,016 read ) 55.2 MB/s = = = = = = = = = = Disk Temperature: 25C, Elapsed Time: 0:01:20 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdf = cycle 1 of 1, partition start on sector 64 = Disk Pre-Read in progress: 0% complete = ( 3,401,523,200 bytes of 1,000,204,886,016 read ) 43.6 MB/s = = = = = = You can see what I am getting in the Popup window. I am running Firefox 40.0.3 on a windows 7 computer. What I observed was that the popup screen kept getting longer and longer as the first refreshes of the the displayed data occurred. Then it stopped adding more info to the displayed text and simply updated each set of information within the window as it refreshed. (Notice the change in the progress of each set.) It appears that something is wrong in screen refresh logic early in the testing sequence. EDIT: The reports were all correctly formatted so this is a cosmetic issue more than anything else but I would imagine that it makes for a somewhat ungainly display on any device with a small display resolution. (Mine is a 2560x1600) Got back from my trip yesterday. Latest update of your Preclear Plugin has resolved this issue for me. Thanks again for all your efforts. It is a another important step in making unRAID more user friendly!!!

Can you try reinstall this package and run a preclear test to see if the bug occur again? Not at the present time. I am running a preclear (three cycles) on a 3TB drive. I will do it when I get that drive done (Guessing Saturday) and installed as the new parity drive on my Test Bed server . Just to double check what you want done. I assume you want me to uninstall the plugin and then reinstall it. Or did you want me to empty the config/plugins/preclear.disk folder also? (I do have a 1TB drive that I can use for a test.) OK. Did two things: First, updated to version 6.0.2. Second, uninstall Preclear Plugin and reinstalled the package. = = = = = Disk Temperature: 24C, Elapsed Time: 0:00:27 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdf = cycle 1 of 1, partition start on sector 64 = Disk Pre-Read in progress: 0% complete = ( 1,200,537,600 bytes of 1,000,204,886,016 read ) 44.4 MB/s = = = = = = = = = = Disk Temperature: 24C, Elapsed Time: 0:00:32 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdf = cycle 1 of 1, partition start on sector 64 = Disk Pre-Read in progress: 0% complete = ( 1,400,627,200 bytes of 1,000,204,886,016 read ) 53.0 MB/s = = = = = = = = = = Disk Temperature: 24C, Elapsed Time: 0:00:37 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdf = cycle 1 of 1, partition start on sector 64 = Disk Pre-Read in progress: 0% complete = ( 1,600,716,800 bytes of 1,000,204,886,016 read ) 53.8 MB/s = = = = = = = = = = Disk Temperature: 24C, Elapsed Time: 0:00:41 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdf = cycle 1 of 1, partition start on sector 64 = Disk Pre-Read in progress: 0% complete = ( 1,800,806,400 bytes of 1,000,204,886,016 read ) 41.8 MB/s = = = = = = = = = = Disk Temperature: 24C, Elapsed Time: 0:00:46 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdf = cycle 1 of 1, partition start on sector 64 = Disk Pre-Read in progress: 0% complete = ( 2,000,896,000 bytes of 1,000,204,886,016 read ) 40.1 MB/s = = = = = = = = = = Disk Temperature: 24C, Elapsed Time: 0:00:52 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdf = cycle 1 of 1, partition start on sector 64 = Disk Pre-Read in progress: 0% complete = ( 2,200,985,600 bytes of 1,000,204,886,016 read ) 45.0 MB/s = = = = = = = = = = Disk Temperature: 24C, Elapsed Time: 0:00:57 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdf = cycle 1 of 1, partition start on sector 64 = Disk Pre-Read in progress: 0% complete = ( 2,401,075,200 bytes of 1,000,204,886,016 read ) 52.9 MB/s = = = = = = = = = = Disk Temperature: 24C, Elapsed Time: 0:01:01 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdf = cycle 1 of 1, partition start on sector 64 = Disk Pre-Read in progress: 0% complete = ( 2,601,164,800 bytes of 1,000,204,886,016 read ) 42.1 MB/s = = = = = = = = = = Disk Temperature: 24C, Elapsed Time: 0:01:06 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdf = cycle 1 of 1, partition start on sector 64 = Disk Pre-Read in progress: 0% complete = ( 2,801,254,400 bytes of 1,000,204,886,016 read ) 43.6 MB/s = = = = = = = = = = Disk Temperature: 24C, Elapsed Time: 0:01:12 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdf = cycle 1 of 1, partition start on sector 64 = Disk Pre-Read in progress: 0% complete = ( 3,001,344,000 bytes of 1,000,204,886,016 read ) 54.7 MB/s = = = = = = = = = = Disk Temperature: 25C, Elapsed Time: 0:01:16 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdf = cycle 1 of 1, partition start on sector 64 = Disk Pre-Read in progress: 0% complete = ( 3,201,433,600 bytes of 1,000,204,886,016 read ) 55.2 MB/s = = = = = = = = = = Disk Temperature: 25C, Elapsed Time: 0:01:20 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdf = cycle 1 of 1, partition start on sector 64 = Disk Pre-Read in progress: 0% complete = ( 3,401,523,200 bytes of 1,000,204,886,016 read ) 43.6 MB/s = = = = = = You can see what I am getting in the Popup window. I am running Firefox 40.0.3 on a windows 7 computer. What I observed was that the popup screen kept getting longer and longer as the first refreshes of the the displayed data occurred. Then it stopped adding more info to the displayed text and simply updated each set of information within the window as it refreshed. (Notice the change in the progress of each set.) It appears that something is wrong in screen refresh logic early in the testing sequence. EDIT: The reports were all correctly formatted so this is a cosmetic issue more than anything else but I would imagine that it makes for a somewhat ungainly display on any device with a small display resolution. (Mine is a 2560x1600)

Can you try reinstall this package and run a preclear test to see if the bug occur again? Not at the present time. I am running a preclear (three cycles) on a 3TB drive. I will do it when I get that drive done (Guessing Saturday) and installed as the new parity drive on my Test Bed server . Just to double check what you want done. I assume you want me to uninstall the plugin and then reinstall it. Or did you want me to empty the config/plugins/preclear.disk folder also? (I do have a 1TB drive that I can use for a test.)

I just checked in the config/plugins/preclear.disk folder, there is a ncurses-5.9-x86_64-2.txz file with a date of 5/7/2013.

It's a bug i'm chasing. unRAID 6.1.1 don't have the correct terminal descriptor in place, so I had to include ncurses on the package. Or you started your preclear session before I update the package to 2015.09.08 or it's still broken. As a point of information, I started this preclear session yesterday and the update to the 2015.09.08 version was done on 2015.09.09 prior to this session. I wanted to make sure that you were aware of the issue. I hope you find the source of the problem so it can be corrected. Thanks again for all your work in getting this GUI interface for the preclear script. PS--- I can recall that there was some type of message generated during the install that the ncurses package all ready existed and the installation was being skipped.

I am posting about an issue that I am having using the Preclear plugin (2015.09.08) and unRAID (Ver 6.1.1). Unfortunately, I am unable to attached a screen capture to clearly illustrate what is going on. So I going to do a copy-and-paste to illustrate the problem. (Even this is difficult as the screen keeping updating every few seconds.) This short copy is a portion of the entire display that shows about bit more than one of the typical screen (that JoeL's preclear script generates) that is normally displayed. The entire display contains about eight to ten of these screens of information separated by the update time (and information) being a few seconds apart. = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Post-Read in progress: 25% complete. ( 756,138,598,400 of 3,000,592,982,016 bytes read ) 131 MB/s Disk Temperature: 33C, Elapsed Time: 18:55:23 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdf = cycle 1 of 3, partition start on sector 1 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Post-Read in progress: 25% complete. ( 756,338,688,000 of 3,000,592,982,016 bytes read ) 115 MB/s Disk Temperature: 33C, Elapsed Time: 18:55:27 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdf = Any comment you might have on this issue and its solution would be appreciated. Frank

I had a thought. The IP address is a bit of unneeded information as the name of the Local Master is also displayed. That name *should* be unique on the Samba network. The name is the really important item. You might want to consider one of the two approaches: 1-- Don't display the IP address in all cases, just display the server name. 2-- If you can easily detect that that Network adapter is being virtualized, don't display the IP address. For the other cases, display the IP address. Be aware that I would really like to have that IP address just as a bit of information but not at the cost of not having some indication of which computer is currently serving as the Local Master! I really don't know what percentage of users are actually using a VM but I do know that they will be always be pointing out the issue.

I don't think this is a problem with the Plugin. What you are seeing is why I asked to have this plugin developed. You have a problem and you are going to have troubleshoot (Google is your friend) your network and figure out why the Domain Controller is not ending up as the Local Master. (As I understand it, it SHOULD be!)

Here is what I think is going on. When a virtual Network device is being emulated, The emulation software is essentially acting as a NAT (or a router). The address which appears to the outside of the box is within the range of the your LAN. The emulation software, however, is assigning addresses for use inside the box. It then does address translation just like your network router does as it interfaces between your LAN and the WAN. EDIT: BTW, it seems to be working perfect on both of my machines!

It is compliant. It doesn't use exec.php or any executables outside /plugins/<plugin>/scripts . Thank you! I have a new 3TB WD Red on order and will be using it to preclear that drive. (Otherwise, I was planning to roll back to 6.0.1) EDIT: You should see about getting this thread moved from the 'Unverified' to 'Verified' section of Plugins (V6)!

Now that 6.1 has been released, are there any plans to bring this plugin into compliance?

I DON'T have the sleep plugin installed but have you looked at the Help for it? You should be able to access it by clicking on the 'Help' button on the right side of the tool bar (Just under the banner image).

I think that is should be noted as 'Advisory-- This drive is currently stable and could be used.' I think this condition should be noted as 'Warning-- This drive is not currently stable and additional testing is warranted before using in an array!.'

My personal recommendation is to use 6.01. It is stable and should be used for any production server. 6.1 is currently beta software and, from what I am reading, it has far more serious issues than any of the beta issues for 6.0! It is best used for test bed servers by people who enjoy helping to ring the bugs out of software. You also have be be willing to install each new beta release. Stopping the update process in the middle of the a beta program will leave you in no man's land if you have an issue a couple of months down the road.

A few page ago, you were asked to run ping google.com at a command prompt. You never answer that you actually did this. Now it could be that you didn't understand exactly what was being requested. What is needed is for you to log into the server using either a monitor and keyboard on the server or Telnet session. If you have a working DNS setup up on your server, you will get a series of times to that it takes for google.com to response to the pinging. (You use a CTRL-C to stop the process.) This will tell us whether the problem is with the DNS setup or something in the GUI.

If you are using those IP addresses which are in my file, that might be the issue. They are the DNS servers for my local ISP provider (Time-Warner), You might try using the Google DNS service which provides world wide service. They are 8.8.8.8 and 8.8.4.4 BTW, most people have good luck with using getting the DNS servers automatically setting. Perhaps, you should try that first.

PK, I may have found your problem. In your network.cfg file, is the following information. # Generated settings: USE_DHCP="no" IPADDR="10.0.0.72" NETMASK="255.255.255.0" GATEWAY="10.0.0.24" DHCP_KEEPRESOLV="no" DNS_SERVER1="" DNS_SERVER2="" DNS_SERVER3="" BONDING="no" BONDING_MODE="1" This is my network.cfg file: # Generated settings: USE_DHCP="no" IPADDR="192.168.1.242" NETMASK="255.255.255.0" GATEWAY="192.168.1.1" DHCP_KEEPRESOLV="no" DNS_SERVER1="208.67.222.222" DNS_SERVER2="208.67.220.220" DNS_SERVER3="" Notice that I have setup the IP addresses for DNS servers. I did this because I have set the "Obtain DNS Server Address Automatically:" to 'No' on the 'NetworkSettings' tab on the 'Settings' Page. You have to set the "Obtain DNS Server Address Automatically:" to 'Yes' OR you have to supply IP addresses for a DNS server in the appropriate places. Some people have found that their router will handle the DNS service correctly. (To use this feature, you do have to turn on "Obtain DNS Server Address Automatically:" setting!) However, I had some issues with my setup not doing it correctly so I elected to use the manual method. The 'Help' system for the NetworkSettings tab will give you the assistance that you need.

My DNS is definitely configured and working. You might want to go to the Tools page and run the 'Diagnostics' package and attach the resulting file to your next post.

What version are you running? Check on the plugin page to find out. The reason is that this was an issue for several of us (Look back a couple of pages in the thread) but it was fixed for us with an update.

Typedf and see what you have for available space in tmpfs. Well on my Media server, the available space in tmpfs is 128,476. On the Test Bed Server, the available space is 129297. However, both servers have been rebooted to get rid of the extra two buttons so the present available space number (on the Media server) is not really a good indicator of what it was when the plugin installation was being run. See here for some discussion and a fix for tmpfs allocation. Interesting reading. I had a look at the syslog file which was saved (Thanks, dlanson, for including this in the Powerdown plugin) when I did the last reboot. I found hundreds of lines of error similar to these: Jul 22 08:33:22 Elsie1 logger: plugin: creating: /boot/config/plugins/dynamix.schedules/dynamix.schedules-2015.07.20.txz - downloading from URL https://raw.github.com/bergware/dynamix/master/archive/dynamix.schedules-2015.07.20.txz Jul 22 08:33:23 Elsie1 logger: plugin: running: /boot/config/plugins/dynamix.schedules/dynamix.schedules-2015.07.20.txz Jul 22 08:33:23 Elsie1 logger: plugin: running: anonymous Jul 22 08:35:01 Elsie1 crond[1340]: failed parsing crontab for user root: /usr/bin/run-parts /etc/cron.hourly 1> /dev/null Jul 22 08:35:01 Elsie1 crond[1340]: failed parsing crontab for user root: /usr/bin/run-parts /etc/cron.daily 1> /dev/null Jul 22 08:35:01 Elsie1 crond[1340]: failed parsing crontab for user root: /usr/bin/run-parts /etc/cron.weekly 1> /dev/null Jul 22 08:35:01 Elsie1 crond[1340]: failed parsing crontab for user root: /usr/bin/run-parts /etc/cron.monthly 1> /dev/null Jul 22 08:41:17 Elsie1 kernel: mdcmd (145): spindown 0 Jul 22 08:41:17 Elsie1 kernel: mdcmd (146): spindown 5 Jul 22 08:45:01 Elsie1 crond[1340]: failed parsing crontab for user root: /usr/bin/run-parts /etc/cron.hourly 1> /dev/null Jul 22 08:45:01 Elsie1 crond[1340]: failed parsing crontab for user root: /usr/bin/run-parts /etc/cron.daily 1> /dev/null Jul 22 08:45:01 Elsie1 crond[1340]: failed parsing crontab for user root: /usr/bin/run-parts /etc/cron.weekly 1> /dev/null Jul 22 08:45:01 Elsie1 crond[1340]: failed parsing crontab for user root: /usr/bin/run-parts /etc/cron.monthly 1> /dev/null Jul 22 09:05:01 Elsie1 crond[1340]: failed parsing crontab for user root: /usr/bin/run-parts /etc/cron.hourly 1> /dev/null Jul 22 09:05:01 Elsie1 crond[1340]: failed parsing crontab for user root: /usr/bin/run-parts /etc/cron.daily 1> /dev/null Jul 22 09:05:01 Elsie1 crond[1340]: failed parsing crontab for user root: /usr/bin/run-parts /etc/cron.weekly 1> /dev/null Jul 22 09:05:01 Elsie1 crond[1340]: failed parsing crontab for user root: /usr/bin/run-parts /etc/cron.monthly 1> /dev/null Jul 22 09:25:11 Elsie1 crond[1340]: failed parsing crontab for user root: /usr/bin/run-parts /etc/cron.hourly 1> /dev/null I attached the syslog for your information. syslog.zip

Typedf and see what you have for available space in tmpfs. Well on my Media server, the available space in tmpfs is 128,476. On the Test Bed Server, the available space is 129297. However, both servers have been rebooted to get rid of the extra two buttons so the present available space number (on the Media server) is not really a good indicator of what it was when the plugin installation was being run.