July 28, 201114 yr Just added a new drive to the array. Clearing started and had got to 3%. However if I try to load the Main page nothing happens, if I try to connect to the shares I get connection failed. emhttp is using cpu: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1150 root 20 0 45676 1656 1148 R 10 0.0 4:40.29 emhttp 2089 root 20 0 0 0 0 S 3 0.0 1:38.19 flush-8:0 365 root 20 0 0 0 0 S 2 0.0 0:59.53 kswapd0 2156 root 20 0 2340 956 752 R 0 0.0 0:00.01 top 1 root 20 0 828 284 240 S 0 0.0 0:02.63 init 2 root 20 0 0 0 0 S 0 0.0 0:00.00 kthreadd 3 root 20 0 0 0 0 S 0 0.0 0:00.00 ksoftirqd/0 6 root RT 0 0 0 0 S 0 0.0 0:00.00 migration/0 and here's the end of my syslog: Jul 28 23:21:04 Tower emhttp: writing MBR on disk 4 (sda) with partition 1 offset 64 Jul 28 23:21:04 Tower emhttp: re-reading (sda) partition table Jul 28 23:21:04 Tower emhttp: shcmd (80): udevadm settle Jul 28 23:21:04 Tower kernel: sda: sda1 Jul 28 23:21:04 Tower emhttp: clearing disk4... Jul 28 23:28:32 Tower dhcpcd[1008]: eth0: renewing lease of 192.168.0.29 Jul 28 23:28:33 Tower dhcpcd[1008]: eth0: acknowledged 192.168.0.29 from 192.168.0.1 Jul 28 23:28:33 Tower dhcpcd[1008]: eth0: leased 192.168.0.29 for 3600 seconds Jul 28 23:58:01 Tower crond[1142]: ignoring /var/spool/cron/crontabs/root- (non-existent user) Jul 28 23:58:34 Tower dhcpcd[1008]: eth0: renewing lease of 192.168.0.29 Jul 28 23:58:35 Tower dhcpcd[1008]: eth0: acknowledged 192.168.0.29 from 192.168.0.1 Jul 28 23:58:35 Tower dhcpcd[1008]: eth0: leased 192.168.0.29 for 3600 seconds Jul 29 00:07:20 Tower in.telnetd[2141]: connect from 192.168.0.8 (192.168.0. Is this ok? Do I just let it run? How can I tell how far through the clear process is now? Cheers, Justin
July 29, 201114 yr Author Checked on the server this morning, and it's cleared the drive ok and the gui is responsive again. I guess it would be nice if it didn't lock up during this process?
July 29, 201114 yr Checked on the server this morning, and it's cleared the drive ok and the gui is responsive again. I guess it would be nice if it didn't lock up during this process? Disks can usually be written at between 75 and 100 Mb/s. At 100Mb/s it will write 1GB every 10 seconds, and you have 2000 GB to write. You need 20000 seconds, or 5.5 hours... at the very least where the array will be off-line. Now you know why the preclear_disk.sh script was developed... Yes it takes even longer since it both reads and writes, and verifies the disk, but the array is on-line while it is running.
July 29, 201114 yr Author Yeah I understand it taking quite a while, however I'm sure I saw a message saying the array would be available during the process. The gui hung and I couldn't connect to my shares. So is that normal?
July 30, 201114 yr Author Fair enough - could have sworn I saw a dialog/message saying the opposite, but I might have misread. Thanks
August 4, 201114 yr The interface should have still worked, but the shares are offline during the clearing process. Peter
February 23, 201214 yr Old topic I know, but beta 14 has same problem. I add a new disk and the GUI hangs till finished (in preclearing step). And I also think it was written, that the array is useable during preclear - I did not try that. so don't know if it is working
February 23, 201214 yr Old topic I know, but beta 14 has same problem. I add a new disk and the GUI hangs till finished (in preclearing step). And I also think it was written, that the array is useable during preclear - I did not try that. so don't know if it is working I think you are confusing "clearing" the drive AFTER assigning it to the array with "pre-clearing" the drive BEFORE assigning it to the array. If unRAID is clearing a drive, the entire array is off-line for the duration of the clearing step. This can take 6, 8, 10 hours, or more for larger disks. unRAID will never clear a newly assigned disk when initially setting up an array (or immediately after the "New Config" button pressed, or the "initconfig" command invoked) at that point, there is no established parity calculation. If no parity disk is assigned, no clearing is performed. Once parity protection is established ( a parity disk assigned and the initial parity calc completed) unRAID will usually clear a newly assigned disk added to an existing parity protected array. It will do this with the array unavailable and off-line. It will perform this clearing step UNLESS the disk has a special pre-clear signature. If the pre-clear signature exists, the array knows the drive has all zeros and the clearing step is skipped as it is not needed. Since the preclear_disk.sh script I wrote is used on a disk BEFORE it is assigned to the unRAID array, you may use the unRAID array while the preclear_disk.sh script is running. When finished, the preclear_disk.sh script writes the special pre-clear-signature to the disk it was clearing so unRAID can know it has been zeroed. Joe L.
February 23, 201214 yr I did not choose my words wisely. Your preclear script I used once and like it very much. Will use this from now on for all new disks. In this case (last post) I let unRAID clear the disk. Offtopic: What is the best way to report bugs/issues and features? webGUI not responding during the time of clearing is a bug. I want to help to improve this product (also bought two Pro licenses some days ago ).
February 23, 201214 yr I did not choose my words wisely. Your preclear script I used once and like it very much. Will use this from now on for all new disks. In this case (last post) I let unRAID clear the disk. Offtopic: What is the best way to report bugs/issues and features? webGUI not responding during the time of clearing is a bug. I want to help to improve this product (also bought two Pro licenses some days ago ). I understand... I agree, it should respond.... but since you are on beta9, odds are it will not be high priority. I do remember on early beta's the screen would not respond. I do not know if that was fixed in later betas, but I think it was. In either case, the server will be unavailable until it finishes clearing the drive. Post the "bug" in the beta-announcement thread. That is where they are likely to get the most attention.
February 23, 201214 yr I'm running beta14 :-) Where to post features? The annoucement thread has 23 pages, I would recommend something like a bugtracker. PS: Very nice support in the forum. Thanks!
Archived
This topic is now archived and is closed to further replies.