JorgeB

Yes it did! With a preclear going it just took 1 or 2 seconds more than usual to start the array after a new config. Thanks! Great work!

For me only while writing, no issues when it’s reading. Pretty sure is the sync command hanging the webui. When it hangs stoping the array, status line on the WebGUI displays "syncing..."

For me only while writing, no issues when it’s reading.

That sounds like a good idea, because normally stopping the array during a preclear sometimes also takes a long time.

Do what gfjardim asked a few posts above and upload your log.

I didn’t want to stop the 3 disks that are preclearing on that server so I was trying it on my test server, and I see now that it only hanged because I assigned the disk to array and started it after starting the preclear. As long as I’m not starting a new array for the first time I can start the array with a preclear going, so this is a very specific use case, still attached log in case you want to have a look. BTW, is there a command I can use to see the progress of the 3 preclears that I have going on the hanged server? preclear.disk.beta.txt

You can only preclear unassigned disks, I'm preclearing 3 disks and trying to start the array with another disk.

ok

This server is preclearing 3 disks, I tried starting the array with a single disk to copy some data in the meantime and it's been like this for 2 hours.

Don't have UD installed.

Because of dual parity I’ve been reorganizing my servers and doing a lot of preclearing, the plugin has been working great, used on disks of various sizes, 3, 4 and 8TB. One thing I noticed, starting an array after starting a preclear makes the WebGUI non responsive, I bet it will respond when the preclears finish, but until then I can’t do anything, is this a known limitation?

Changing the number of slots did it, and that’s a good enough fix for me, I was thinking the plugin was getting info from the previous array config.

And how do I do that? This is the settings page from my test server, at the moment it only has 4 data disks. Pressing default doesn't remove unused disks.

Not a very big deal but if a disk is removed from the array (disk10 in this example) it still appears on the plugin selection.

You can use the new beta plugin, works with v6.2-beta http://lime-technology.com/forum/index.php?topic=39985.msg453938#msg453938

Just finished preclearing a 3TB WD Green, this disk was previously used on another server so skipped pre and post reads, but failed verifying signature: ########################################################################################### # # # unRAID Server Pre-Clear of disk /dev/sdn # # Cycle 1 of 1, partition start on sector 64. # # # # # # # # Step 1 of 3 - Zeroing the disk: SUCCESS # # Step 2 of 3 - Writing unRAID's Preclear signature: SUCCESS # # Step 3 of 3 - Verifying unRAID's Preclear signature: FAIL # # # # # # # # # # # # # # # # # ########################################################################################### # Cycle elapsed time: 7:10:21 | Total elapsed time: 7:10:21 # ########################################################################################### --> FAIL: unRAID's Preclear signature not valid. root@Tower2:/usr/local/emhttp# This server is still on V6.1 so I can also test with the old plugin: root@Tower2:/boot# preclear_disk.sh -t /dev/sdn Pre-Clear unRAID Disk /dev/sdn ################################################################## 1.15 Model Family: Western Digital Caviar Green (AF, SATA 6Gb/s) Device Model: WDC WD30EZRX-00D8PB0 Serial Number: WD-WCC4N5DDZX6V LU WWN Device Id: 5 0014ee 20bdc27d7 Firmware Version: 80.00A80 User Capacity: 3,000,592,982,016 bytes [3.00 TB] Disk /dev/sdn: 3000.6 GB, 3000592982016 bytes 255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdn1 64 732566645 366283291 0 Empty ######################################################################## failed test 2 00000 00000 00000 00000 failed test 3 00000 00000 00000 00000 failed test 6 ========================================================================1.15 == == Disk /dev/sdn is NOT precleared == 64 732566582 5860533104 ============================================================================

Since last post precleared 4 or 5 more disks, all were added to the array with no issues, parity sync always completed with 0 errors, although for now only tested on small SSDs. Having an issue with not finding all available disks, /dev/sdo appears as unassigned on main page but it’s not available for preclear, preclear_beta.txt attached. preclear_beta.txt

3) Once it's over, please run a Verify All the Disk operation; verify successful 4) If successful, please run both Test and Run the post-read verify operations from the older plugin; can't at the moment because old plugin does not work on 6.2 5) If possible, assign the precleared disk to the array and start a Check Parity operation. successfully assigned and parity check finished with 0 sync errors

Working now Will report if all went well. P.S. - looks like there's some wrong info on the status display: Time elapsed: 0:02:42 | Write speed: 159.62s, | Average speed: 83MB/s Plugin page: Zeroing: 78% @ 296.065s, MB/s (0:04:58)

Here you go. preclear_beta.txt

Updated to 2016.03.12 and still get same error, let me know of need any more info.

No problem. preclear_beta.txt

Attached. preclear_beta.txt

Trying to start a preclear but getting assigned disk error.

This shortcut stopped working on v6.2beta, people using this method to convert to XFS better finish before upgrading.