running unRaid 5.0b12

 

Just bought a 3TB WD drive and ran through the preclear.  Everything came back fine after about 30 hours.

 

I stopped the array, assigned the 3TB drive to the next slot and hit start array. 

 

The array has been offline for 2 hours now, the default unraid webpage is unavailable.  I can load unmenu and it shows a ton of read/writes to the new drive and that it's assigned in the array.  The status under unmenu is: PROTECTED_EXPANSION, unRAID ARRAY is STOPPED 7 disks in array.    PARITY NOT VALID: DISK_NEW.

 

Is this normal?  Is it something I'm just going to have to wait out?  I figured it should be an easy add considering I just waited 30+ hours for preclear. 

 

thanks in advance.

Related syslog entries:

 

Oct  3 16:12:43 MRPOKCFS01 kernel: scsi0 : mvsas (Drive related)

Oct  3 16:12:43 MRPOKCFS01 kernel: scsi 0:0:0:0: Direct-Access    ATA      WDC WD30EZRX-00M 80.0 PQ: 0 ANSI: 5 (Drive related)

Oct  3 16:12:43 MRPOKCFS01 kernel: sd 0:0:0:0: [sdi] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB) (Drive related)

Oct  3 16:12:43 MRPOKCFS01 kernel: sd 0:0:0:0: [sdi] 4096-byte physical blocks (Drive related)

Oct  3 16:12:43 MRPOKCFS01 kernel: sd 0:0:0:0: [sdi] Write Protect is off (Drive related)

Oct  3 16:12:43 MRPOKCFS01 kernel: sd 0:0:0:0: [sdi] Mode Sense: 00 3a 00 00 (Drive related)

Oct  3 16:12:43 MRPOKCFS01 kernel: sd 0:0:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA (Drive related)

Oct  3 16:12:43 MRPOKCFS01 kernel:  sdi: unknown partition table (Drive related)

Oct  3 16:12:43 MRPOKCFS01 kernel: sd 0:0:0:0: [sdi] Attached SCSI disk (Drive related)

Oct  3 16:12:43 MRPOKCFS01 emhttp: WDC_WD30EZRX-00MMMB0_WD-WCAWZ1394854 (sdi) 2930266584 (Drive related)

Oct  3 16:18:10 MRPOKCFS01 kernel:  sdi: unknown partition table (Drive related)

Oct  4 13:48:58 MRPOKCFS01 kernel:  sdi: sdi1 (Drive related)

Oct  5 10:04:01 MRPOKCFS01 preclear_disk-diff[12656]: == invoked as: ./preclear_disk.sh -A /dev/sdi (Misc)

Oct  5 10:04:01 MRPOKCFS01 preclear_disk-diff[12656]: == Disk /dev/sdi has been successfully precleared (Misc)

Oct  5 10:04:01 MRPOKCFS01 preclear_disk-diff[12656]: ** Changed attributes in files: /tmp/smart_start_sdi  /tmp/smart_finish_sdi (Misc)

Oct  5 10:04:01 MRPOKCFS01 preclear_disk-diff[12656]: == S.M.A.R.T Initial Report for /dev/sdi  (Misc)

Oct  5 10:04:01 MRPOKCFS01 preclear_disk-diff[12656]: Disk: /dev/sdi (Misc)

Oct  5 10:04:01 MRPOKCFS01 preclear_disk-diff[12656]: == S.M.A.R.T Final Report for /dev/sdi  (Misc)

Oct  5 10:04:01 MRPOKCFS01 preclear_disk-diff[12656]: Disk: /dev/sdi (Misc)

Oct  5 11:41:37 MRPOKCFS01 emhttp: WDC_WD30EZRX-00MMMB0_WD-WCAWZ1394854 (sdi) 2930266584 (Drive related)

Oct  5 11:41:37 MRPOKCFS01 emhttp: WDC_WD30EZRX-00MMMB0_WD-WCAWZ1394854 (sdi) 2930266584 (Drive related)

Oct  5 11:41:44 MRPOKCFS01 emhttp: WDC_WD30EZRX-00MMMB0_WD-WCAWZ1394854 (sdi) 2930266584 (Drive related)

Oct  5 11:41:44 MRPOKCFS01 kernel: md: import disk6: [8,128] (sdi) WDC_WD30EZRX-00MMMB0_WD-WCAWZ1394854 size: 2930266532 (Drive related)

Oct  5 11:41:44 MRPOKCFS01 kernel: md: disk6 new disk (unRAID engine)

Oct  5 11:42:26 MRPOKCFS01 emhttp: shcmd (110): /usr/local/sbin/set_ncq sdi 1 $stuff$> /dev/null (Drive related)

Oct  5 11:42:26 MRPOKCFS01 emhttp: writing GPT on disk 6 (sdi) with partition 1 offset 64 (Drive related)

Oct  5 11:42:26 MRPOKCFS01 emhttp: shcmd (112): sgdisk -Z /dev/sdi $stuff$> /dev/null (Drive related)

Oct  5 11:42:27 MRPOKCFS01 emhttp: shcmd (113): sgdisk -o -a 64 -n 1:64:0 /dev/sdi |$stuff$ logger (Drive related)

Oct  5 11:42:27 MRPOKCFS01 kernel:  sdi: sdi1 (Drive related)

Oct  5 11:42:28 MRPOKCFS01 kernel:  sdi: sdi1 (Drive related)

Oct  5 11:42:28 MRPOKCFS01 emhttp: clearing disk6...  (Other emhttp)

After reading through the logs I'm guessing I screwed up somewhere on the preclear.  I'm also guessing that the array is offline because unRaid is doing a clear on the drive now so am I correct in assuming it's going to take 10+ hours for it to clear the drive and get the array back online now?

After reading through the logs I'm guessing I screwed up somewhere on the preclear.  I'm also guessing that the array is offline because unRaid is doing a clear on the drive now so am I correct in assuming it's going to take 10+ hours for it to clear the drive and get the array back online now?

exactly.  Possibly you did not let the preclear run to completion?  Or you used an older version of the preclear script? (only the 1.13 and 1.12beta are able to clear 3TB drives.  The 1.12 (non-beta) would clear them, but not put a valid signature.

After reading through the logs I'm guessing I screwed up somewhere on the preclear.  I'm also guessing that the array is offline because unRaid is doing a clear on the drive now so am I correct in assuming it's going to take 10+ hours for it to clear the drive and get the array back online now?

exactly.   Possibly you did not let the preclear run to completion?   Or you used an older version of the preclear script? (only the 1.13 and 1.12beta are able to clear 3TB drives.  The 1.12 (non-beta) would clear them, but not put a valid signature.

 

I looked and I used version 1.11.  I should have updated my preclear script before kicking it off.  I didn't partition the drive before I ran the script either.  The script ran to completion and returned no errors.  (in the screen session and also relayed in unmenu)

 

Thanks for the response Joe.  After about 11 hours the drive cleared through unraid and the array came online without issues.  I'll be more detail oriented when I add another drive in the future.

 

Do the drives need to be partitioned before preclearing or does the script take care of that?

Do the drives need to be partitioned before preclearing or does the script take care of that?

You do not need to partition or format the drives.  Pre-clearing sets up a signature that is used to define the initial partition.  unRAID itself does the final partitioning... especially with drives over 2.2TB, as it then also loads a protective MBR partition in place that make it look like the entire drive is allocated.