How long should it take? I'm trying to add a 3TB drive to an unRAID 5.11 server which was working with no known issues or parity problems, but adding a drive is taking longer than I expected. I ran three pre clears (around 30 hours each), stopped the array,  formatted using the unMenu tool.

 

All that went as expected, but since adding the drive to the array and clicking the start button it's been over 36 hours but the array is still stopped. Did I do something wrong or do I need to be more patient?

 

The log keeps repeating similar info such as below, any suggestions?

 

/usr/bin/tail -n 40 -f /var/log/syslog

Jul 5 06:14:54 192 emhttp: VB0250EAVER_Z3T26XCQ (sdc) 244198584

Jul 5 06:14:54 192 emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0705384 (sdd) 2930266584

Jul 5 06:14:54 192 kernel: md: unRAID driver 2.1.5 installed

Jul 5 06:14:54 192 kernel: mdcmd (1): import 0 8,0 2930266532 WDC_WD30EFRX-68AX9N0_WD-WMC1T2135866

Jul 5 06:14:54 192 kernel: md: import disk0: [8,0] (sda) WDC_WD30EFRX-68AX9N0_WD-WMC1T2135866 size: 2930266532

Jul 5 06:14:54 192 kernel: mdcmd (2): import 1 8,16 488386552 WDC_WD5000AAKS-00YGA0_WD-WCAS81272501

Jul 5 06:14:54 192 kernel: md: import disk1: [8,16] (sdb) WDC_WD5000AAKS-00YGA0_WD-WCAS81272501 size: 488386552

Jul 5 06:14:54 192 kernel: mdcmd (3): import 2 8,32 244198552 VB0250EAVER_Z3T26XCQ

Jul 5 06:14:54 192 kernel: md: import disk2: [8,32] (sdc) VB0250EAVER_Z3T26XCQ size: 244198552

Jul 5 06:14:54 192 emhttp: shcmd (3372): /usr/local/sbin/emhttp_event driver_loaded

Jul 5 06:14:54 192 kernel: mdcmd (4): import 3 8,48 2930266532 WDC_WD30EFRX-68AX9N0_WD-WCC1T0705384

Jul 5 06:14:54 192 kernel: md: import disk3: [8,48] (sdd) WDC_WD30EFRX-68AX9N0_WD-WCC1T0705384 size: 2930266532

Jul 5 06:14:54 192 kernel: md: disk3 new disk

Jul 5 06:14:54 192 kernel: mdcmd (5): import 4 0,0

Jul 5 06:14:54 192 kernel: mdcmd (6): import 5 0,0

Jul 5 06:14:54 192 emhttp_event: driver_loaded

Jul 5 06:14:54 192 emhttp: shcmd (3373): rmmod md-mod |& logger

Jul 5 06:14:54 192 kernel: md: unRAID driver removed

Jul 5 06:14:54 192 emhttp: shcmd (3374): modprobe md-mod super=/boot/config/super.dat slots=6 |& logger

Jul 5 06:14:54 192 emhttp: shcmd (3375): udevadm settle

Jul 5 06:14:54 192 kernel: md: unRAID driver 2.1.5 installed

Jul 5 06:14:54 192 emhttp: Device inventory:

Jul 5 06:14:54 192 emhttp: WDC_WD30EFRX-68AX9N0_WD-WMC1T2135866 (sda) 2930266584

Jul 5 06:14:54 192 emhttp: SanDisk_SDSSDP064G_122358400638 (hdb) 62522712

Jul 5 06:14:54 192 emhttp: WDC_WD5000AAKS-00YGA0_WD-WCAS81272501 (sdb) 488386584

Jul 5 06:14:54 192 emhttp: VB0250EAVER_Z3T26XCQ (sdc) 244198584

Jul 5 06:14:54 192 emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0705384 (sdd) 2930266584

Jul 5 06:14:54 192 emhttp: shcmd (3376): /usr/local/sbin/emhttp_event driver_loaded

Jul 5 06:14:54 192 kernel: mdcmd (1): import 0 8,0 2930266532 WDC_WD30EFRX-68AX9N0_WD-WMC1T2135866

Jul 5 06:14:54 192 kernel: md: import disk0: [8,0] (sda) WDC_WD30EFRX-68AX9N0_WD-WMC1T2135866 size: 2930266532

Jul 5 06:14:54 192 kernel: mdcmd (2): import 1 8,16 488386552 WDC_WD5000AAKS-00YGA0_WD-WCAS81272501

Jul 5 06:14:54 192 kernel: md: import disk1: [8,16] (sdb) WDC_WD5000AAKS-00YGA0_WD-WCAS81272501 size: 488386552

Jul 5 06:14:54 192 kernel: mdcmd (3): import 2 8,32 244198552 VB0250EAVER_Z3T26XCQ

Jul 5 06:14:54 192 kernel: md: import disk2: [8,32] (sdc) VB0250EAVER_Z3T26XCQ size: 244198552

Jul 5 06:14:54 192 kernel: mdcmd (4): import 3 8,48 2930266532 WDC_WD30EFRX-68AX9N0_WD-WCC1T0705384

Jul 5 06:14:54 192 kernel: md: import disk3: [8,48] (sdd) WDC_WD30EFRX-68AX9N0_WD-WCC1T0705384 size: 2930266532

Jul 5 06:14:54 192 kernel: md: disk3 new disk

Jul 5 06:14:54 192 kernel: mdcmd (5): import 4 0,0

Jul 5 06:14:54 192 kernel: mdcmd (6): import 5 0,0

Jul 5 06:14:54 192 emhttp_event: driver_loaded

Jul 5 06:14:59 192 emhttp: shcmd (3377): rmmod md-mod |& logger

Jul 5 06:14:59 192 emhttp: shcmd (3378): modprobe md-mod super=/boot/config/super.dat slots=6 |& logger

Jul 5 06:14:59 192 kernel: md: unRAID driver removed

Jul 5 06:14:59 192 emhttp: shcmd (3379): udevadm settle

Jul 5 06:14:59 192 kernel: md: unRAID driver 2.1.5 installed

Jul 5 06:14:59 192 emhttp: Device inventory:

Jul 5 06:14:59 192 emhttp: WDC_WD30EFRX-68AX9N0_WD-WMC1T2135866 (sda) 2930266584

Jul 5 06:14:59 192 emhttp: SanDisk_SDSSDP064G_122358400638 (hdb) 62522712

Jul 5 06:14:59 192 emhttp: WDC_WD5000AAKS-00YGA0_WD-WCAS81272501 (sdb) 488386584

Jul 5 06:14:59 192 emhttp: VB0250EAVER_Z3T26XCQ (sdc) 244198584

Jul 5 06:14:59 192 emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0705384 (sdd) 2930266584

Jul 5 06:14:59 192 emhttp: shcmd (3380): /usr/local/sbin/emhttp_event driver_loaded

Jul 5 06:14:59 192 kernel: mdcmd (1): import 0 8,0 2930266532 WDC_WD30EFRX-68AX9N0_WD-WMC1T2135866

Jul 5 06:14:59 192 kernel: md: import disk0: [8,0] (sda) WDC_WD30EFRX-68AX9N0_WD-WMC1T2135866 size: 2930266532

Jul 5 06:14:59 192 kernel: mdcmd (2): import 1 8,16 488386552 WDC_WD5000AAKS-00YGA0_WD-WCAS81272501

Jul 5 06:14:59 192 kernel: md: import disk1: [8,16] (sdb) WDC_WD5000AAKS-00YGA0_WD-WCAS81272501 size: 488386552

Jul 5 06:14:59 192 kernel: mdcmd (3): import 2 8,32 244198552 VB0250EAVER_Z3T26XCQ

Jul 5 06:14:59 192 kernel: md: import disk2: [8,32] (sdc) VB0250EAVER_Z3T26XCQ size: 244198552

Jul 5 06:14:59 192 kernel: mdcmd (4): import 3 8,48 2930266532 WDC_WD30EFRX-68AX9N0_WD-WCC1T0705384

Jul 5 06:14:59 192 kernel: md: import disk3: [8,48] (sdd) WDC_WD30EFRX-68AX9N0_WD-WCC1T0705384 size: 2930266532

Jul 5 06:14:59 192 kernel: md: disk3 new disk

Jul 5 06:14:59 192 kernel: mdcmd (5): import 4 0,0

Jul 5 06:14:59 192 kernel: mdcmd (6): import 5 0,0

Jul 5 06:14:59 192 emhttp_event: driver_loaded

Jul 5 06:15:04 192 emhttp: shcmd (3381): rmmod md-mod |& logger

Jul 5 06:15:04 192 emhttp: shcmd (3382): modprobe md-mod super=/boot/config/super.dat slots=6 |& logger

Jul 5 06:15:04 192 kernel: md: unRAID driver removed

Jul 5 06:15:04 192 kernel: md: unRAID driver 2.1.5 installed

Jul 5 06:15:04 192 emhttp: shcmd (3383): udevadm settle

Jul 5 06:15:04 192 emhttp: Device inventory:

Jul 5 06:15:04 192 emhttp: WDC_WD30EFRX-68AX9N0_WD-WMC1T2135866 (sda) 2930266584

Jul 5 06:15:04 192 emhttp: SanDisk_SDSSDP064G_122358400638 (hdb) 62522712

Jul 5 06:15:04 192 emhttp: WDC_WD5000AAKS-00YGA0_WD-WCAS81272501 (sdb) 488386584

Jul 5 06:15:04 192 emhttp: VB0250EAVER_Z3T26XCQ (sdc) 244198584

Jul 5 06:15:04 192 emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0705384 (sdd) 2930266584

Jul 5 06:15:04 192 kernel: mdcmd (1): import 0 8,0 2930266532 WDC_WD30EFRX-68AX9N0_WD-WMC1T2135866

Jul 5 06:15:04 192 kernel: md: import disk0: [8,0] (sda) WDC_WD30EFRX-68AX9N0_WD-WMC1T2135866 size: 2930266532

Jul 5 06:15:04 192 kernel: mdcmd (2): import 1 8,16 488386552 WDC_WD5000AAKS-00YGA0_WD-WCAS81272501

Jul 5 06:15:04 192 kernel: md: import disk1: [8,16] (sdb) WDC_WD5000AAKS-00YGA0_WD-WCAS81272501 size: 488386552

Jul 5 06:15:04 192 kernel: mdcmd (3): import 2 8,32 244198552 VB0250EAVER_Z3T26XCQ

Jul 5 06:15:04 192 kernel: md: import disk2: [8,32] (sdc) VB0250EAVER_Z3T26XCQ size: 244198552

Jul 5 06:15:04 192 kernel: mdcmd (4): import 3 8,48 2930266532 WDC_WD30EFRX-68AX9N0_WD-WCC1T0705384

Jul 5 06:15:04 192 kernel: md: import disk3: [8,48] (sdd) WDC_WD30EFRX-68AX9N0_WD-WCC1T0705384 size: 2930266532

Jul 5 06:15:04 192 kernel: md: disk3 new disk

Jul 5 06:15:04 192 kernel: mdcmd (5): import 4 0,0

Jul 5 06:15:04 192 kernel: mdcmd (6): import 5 0,0

Jul 5 06:15:04 192 emhttp: shcmd (3384): /usr/local/sbin/emhttp_event driver_loaded

Jul 5 06:15:04 192 emhttp_event: driver_loaded

formatted using the unMenu tool.

There's your problem.

 

If you read the preclear post, it says this...

 

Do NOT use anything other than the Format button on the main unRAID management console page to format a pre-cleared disk. The "Format" button will appear after you start the array after assigning a pre-cleared drive.  Do NOT format the drive on your own using a reiserfs linux command, or using a button in unMENU, if you do, the pre-clear will be invalid, and you may even fool unRAID into thinking it is cleared when it is not.  This would let you think you have parity protection when you do not.

 

Basically you killed your preclear by formatting the drive, so unraid is clearing it again. I don't think it should take 36 hours, so you should probably zip and post your entire syslog.

As Jonathan noted, you invalidated the pre-clear.

 

At this point, I'd Stop the array;  then re-start it and see if it indicates it's going to clear the drive.  If not, something's wrong ... either with the drive or the status info.    If that's the case, then Stop the array (if it started);  do a New Config; and assign all of your original drives, but NOT the new one.

 

Then Start the array and let it rebuild parity (it will do this automatically).  Be CERTAIN that you assigned the correct drive as parity !!    Meanwhile, start another pre-Clear on your new drive (one cycle is fine).    When it finishes, add it the correct way (following the instructions on the pre-clear post); and all will be well.

 

Note:  You COULD simply include the new drive in your new configuration IF you do NOT assign a parity drive.    Then Start the array and confirm it's okay (It MAY offer to format the new drive ... that's okay -- but any other drive is NOT).  Then Stop it; assign your parity drive; and Start it again and let it do the parity sync.    The new drive won't be all zeroes in that case, but that doesn't matter as long as it's got a proper Reiser file structure.  The "all zeroes" is only necessary to preserve parity when adding  a new drive to a parity protected array.

 

Thank you both for the quick replies. I've misinterpreted the instructions as Jonathan stated by not seeing the format tool in the unRAID console and mixed it up with the unMenu option. Just to be sure it's OK I'll do another pre-clear and try and follow the instructions correctly this time.