February 11, 201313 yr I have an array of 3 3Tb drives right now (one is parity) and I have a forth and fifth to put in. I checked the forth disk for errors and then added it to my server case and it showed up in the drop down menu for data drive 3 which is where it is going. So where it says this: "Start will record the new disk information and bring the expanded array on-line. All new disks which have not been factory-erased will be cleared first; and, the array will be available after the clear completes. This process takes time, but the array remains protected at all times. Caution: any data on the new disk(s) will be erased! If you want to preserve the data on the new disk(s), reset the array configuration and rebuild parity instead." I checked yes I want to do this and clicked start. all that happens is the page reloads, the array doesn't start or add the disk it just looks exactly the way it did before I clicked start. So I don't know what is happening so can someone please help??
February 11, 201313 yr If you have not used the 'pre-clear' script when checking your disk for errors, then unRAID starts by writing zeroes to every sector on the disk. This can take many hours for a 3TB disk, and during that period the array is not usable, and the GUI is unresponsive. Is the disk activity light for the new disk showing it is active - it should if the clear process is running as I suspect? A big advantage of using the pre_clear script in advance of trying to add the disk to the array is that it reduces the time the array is not accessible to seconds rather than hours. it also allows you to do a more thorough check of the disk.
February 11, 201313 yr If you have not used the 'pre-clear' script when checking your disk for errors, then unRAID starts by writing zeroes to every sector on the disk. This can take many hours for a 3TB disk, and during that period the array is not usable, and the GUI is unresponsive. Is the disk activity light for the new disk showing it is active - it should if the clear process is running as I suspect? A big advantage of using the pre_clear script in advance of trying to add the disk to the array is that it reduces the time the array is not accessible to seconds rather than hours. it also allows you to do a more thorough check of the disk. Writing the initial set of zeros to a 3TB drive will take about 8 hours or more. If able to write at 100MB/s, then it will take 10 seconds per GB, or 6 GB per minute. You have 3000 GB to write. 3000GB / 6 per minute = 500 Minutes = 8.33 hours. During that time the array is not available and the GUI is un-responsive. (Hint: it is one of the reasons the pre-clear script was created to take advantage ot unRAID's ability to recognize a pre-cleared drive.) Other than that, log onto the server via telnet or the system console and capture a system log for analysis for anything more specific to your server, since so far, it seems it is acting normal. (Unless you do not see the new disk activity light blinking) Joe L.
February 11, 201313 yr Author I already use the pre_clear script on the drive so that I can use the array while it is doing that and then add it very quickly. Are you talking about a physical activity light like an led, or the light (dot) in the web gui of unraid? I don't have any led activity lights on my server but in the web gui it shows a blu dot which means "New disk, not in array". Here is a picture of what it looks like after I press start. Here is a link to my syslog.txt file so you all can look at it and tell me something. https://dl.dropbox.com/u/1548652/Downloads/syslog.txt
February 12, 201313 yr I see this line in the syslog. Feb 11 16:35:55 Tower emhttp: new disk(s) are not cleared
February 12, 201313 yr Author well even if it is not cleared, which I don't know why it isn't, shouldn't it start the clearing process when I click start? Maybe ill start the pre_clear again tonight and see if it works after that.
Archived
This topic is now archived and is closed to further replies.