I've had my 4x2tb data plus 2tb parity drive on unraid 4.7 running for over two years, recently upgraded to 5.0.5 for a month and all is great.  Until...

 

Invested in a set of WD red 4tb drives for a straight swap, double capacity upgrade.

 

Tonight, I stopped the array, unassigned the 2tb parity drive, powered down, took the WD red 4tb out of it's sealed bag and replaced the parity drive. Booted, chose the WD 4tb as the parity.  Drive status was blue.  Tried to start the array, but it won't, just get the 'spinning up all drives' message but the array hasn't started.

 

Stopped. New parity disk installed.

 

is the message under the disks.  I've refreshed, re-booted, started started... still no go.

 

Below is the syslog after I try to re-start again.  Any experts have any idea?

 

thanks

CTID

 

 

Feb 28 21:29:26 Tower kernel: mdcmd (25): set md_num_stripes 1280 (unRAID engine)

Feb 28 21:29:26 Tower kernel: mdcmd (26): set md_write_limit 768 (unRAID engine)

Feb 28 21:29:26 Tower kernel: mdcmd (27): set md_sync_window 384 (unRAID engine)

Feb 28 21:29:26 Tower kernel: mdcmd (28): set spinup_group 0 0 (unRAID engine)

Feb 28 21:29:26 Tower emhttp: shcmd (96): /usr/local/sbin/set_ncq sdf 1 $stuff$> /dev/null (Drive related)

Feb 28 21:29:26 Tower kernel: mdcmd (29): set spinup_group 1 0 (unRAID engine)

Feb 28 21:29:26 Tower kernel: mdcmd (30): set spinup_group 2 0 (unRAID engine)

Feb 28 21:29:26 Tower kernel: mdcmd (31): set spinup_group 3 0 (unRAID engine)

Feb 28 21:29:26 Tower kernel: mdcmd (32): set spinup_group 4 0 (unRAID engine)

Feb 28 21:29:26 Tower emhttp: shcmd (97): /usr/local/sbin/set_ncq sdc 1 $stuff$> /dev/null (Drive related)

Feb 28 21:29:26 Tower emhttp: shcmd (98): /usr/local/sbin/set_ncq sdd 1 $stuff$> /dev/null (Drive related)

Feb 28 21:29:27 Tower emhttp: shcmd (99): /usr/local/sbin/set_ncq sde 1 $stuff$> /dev/null (Drive related)

Feb 28 21:29:27 Tower emhttp: shcmd (100): /usr/local/sbin/set_ncq sdb 1 $stuff$> /dev/null (Drive related)

Feb 28 21:29:27 Tower emhttp: Spinning up all drives... (Other emhttp)

Feb 28 21:29:27 Tower emhttp: writing GPT on disk (sdf), with partition 1 offset 64, erased: 0 (Drive related)

Feb 28 21:29:27 Tower emhttp: shcmd (101): sgdisk -Z /dev/sdf $stuff$> /dev/null (Drive related)

Feb 28 21:29:27 Tower kernel: mdcmd (33): spinup 0 (Routine)

Feb 28 21:29:27 Tower kernel: mdcmd (34): spinup 1 (Routine)

Feb 28 21:29:27 Tower kernel: mdcmd (35): spinup 2 (Routine)

Feb 28 21:29:27 Tower kernel: mdcmd (36): spinup 3 (Routine)

Feb 28 21:29:27 Tower kernel: mdcmd (37): spinup 4 (Routine)

Feb 28 21:29:27 Tower emhttp: _shcmd: shcmd (101): exit status: 1 (Other emhttp)

Feb 28 21:29:27 Tower emhttp: shcmd (102): sgdisk -o -a 64 -n 1:64:0 /dev/sdf |$stuff$ logger (Drive related)

Feb 28 21:29:27 Tower logger: sgdisk: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.11' not found (required by sgdisk) (System)

Feb 28 21:29:27 Tower emhttp: shcmd (103): udevadm settle (Other emhttp)

Feb 28 21:29:27 Tower emhttp: Start array... (Other emhttp)

Feb 28 21:29:27 Tower emhttp: mdcmd: write: No such device or address (Other emhttp)

Feb 28 21:29:27 Tower emhttp: shcmd (104): rmmod md-mod |$stuff$ logger (Other emhttp)

Feb 28 21:29:27 Tower kernel: mdcmd (38): start RECON_DISK (unRAID engine)

Feb 28 21:29:27 Tower kernel: md: do_run: lock_rdev error: -6 (Errors)

Feb 28 21:29:27 Tower emhttp: shcmd (105): modprobe md-mod super=/boot/config/super.dat slots=24 |$stuff$ logger (unRAID engine)

Feb 28 21:29:27 Tower kernel: md: unRAID driver removed (System)

Feb 28 21:29:27 Tower emhttp: shcmd (106): udevadm settle (Other emhttp)

Feb 28 21:29:27 Tower emhttp: Device inventory: (Drive related)

Feb 28 21:29:27 Tower emhttp: SAMSUNG_HD204UI_S2H7JD2B108427 (sdb) 1953513527 (Drive related)

Feb 28 21:29:27 Tower emhttp: SAMSUNG_HD204UI_S2H7J9CB105081 (sdc) 1953514584 (Drive related)

Feb 28 21:29:27 Tower kernel: md: unRAID driver 2.2.0 installed (System)

Feb 28 21:29:27 Tower emhttp: SAMSUNG_HD204UI_S2H7J9CB105079 (sdd) 1953514584 (Drive related)

Feb 28 21:29:27 Tower emhttp: SAMSUNG_HD204UI_S2H7J9CB105083 (sde) 1953514584 (Drive related)

Feb 28 21:29:27 Tower emhttp: WDC_WD40EFRX-68WT0N0_WD-WCC4E0969816 (sdf) 3907018584 (Drive related)

Feb 28 21:29:27 Tower emhttp: shcmd (107): /usr/local/sbin/emhttp_event driver_loaded (System)

Feb 28 21:29:27 Tower kernel: mdcmd (1): import 0 8,80 3907018532 WDC_WD40EFRX-68WT0N0_WD-WCC4E0969816 (unRAID engine)

Feb 28 21:29:27 Tower kernel: md: import disk0: [8,80] (sdf) WDC_WD40EFRX-68WT0N0_WD-WCC4E0969816 size: 3907018532 (Drive related)

Feb 28 21:29:27 Tower kernel: md: disk0 replaced (unRAID engine)

Feb 28 21:29:27 Tower kernel: mdcmd (2): import 1 8,32 1953514552 SAMSUNG_HD204UI_S2H7J9CB105081 (unRAID engine)

Feb 28 21:29:27 Tower kernel: md: import disk1: [8,32] (sdc) SAMSUNG_HD204UI_S2H7J9CB105081 size: 1953514552 (Drive related)

Feb 28 21:29:27 Tower kernel: mdcmd (3): import 2 8,48 1953514552 SAMSUNG_HD204UI_S2H7J9CB105079 (unRAID engine)

Feb 28 21:29:27 Tower kernel: md: import disk2: [8,48] (sdd) SAMSUNG_HD204UI_S2H7J9CB105079 size: 1953514552 (Drive related)

Feb 28 21:29:27 Tower kernel: mdcmd (4): import 3 8,64 1953514552 SAMSUNG_HD204UI_S2H7J9CB105083 (unRAID engine)

Feb 28 21:29:27 Tower kernel: md: import disk3: [8,64] (sde) SAMSUNG_HD204UI_S2H7J9CB105083 size: 1953514552 (Drive related)

Feb 28 21:29:27 Tower kernel: mdcmd (5): import 4 8,16 1953513496 SAMSUNG_HD204UI_S2H7JD2B108427 (unRAID engine)

Feb 28 21:29:27 Tower kernel: md: import disk4: [8,16] (sdb) SAMSUNG_HD204UI_S2H7JD2B108427 size: 1953513496 (Drive related)

Feb 28 21:29:27 Tower kernel: mdcmd (6): import 5 0,0 (unRAID engine)

Feb 28 21:29:27 Tower kernel: mdcmd (7): import 6 0,0 (unRAID engine)

Feb 28 21:29:27 Tower kernel: mdcmd (: import 7 0,0 (unRAID engine)

Feb 28 21:29:27 Tower kernel: mdcmd (9): import 8 0,0 (unRAID engine)

Feb 28 21:29:27 Tower kernel: mdcmd (10): import 9 0,0 (unRAID engine)

Feb 28 21:29:27 Tower kernel: mdcmd (11): import 10 0,0 (unRAID engine)

Feb 28 21:29:27 Tower kernel: mdcmd (12): import 11 0,0 (unRAID engine)

Feb 28 21:29:27 Tower kernel: mdcmd (13): import 12 0,0 (unRAID engine)

Feb 28 21:29:27 Tower kernel: mdcmd (14): import 13 0,0 (unRAID engine)

Feb 28 21:29:27 Tower kernel: mdcmd (15): import 14 0,0 (unRAID engine)

Feb 28 21:29:27 Tower kernel: mdcmd (16): import 15 0,0 (unRAID engine)

Feb 28 21:29:27 Tower kernel: mdcmd (17): import 16 0,0 (unRAID engine)

Feb 28 21:29:27 Tower kernel: mdcmd (18): import 17 0,0 (unRAID engine)

Feb 28 21:29:27 Tower kernel: mdcmd (19): import 18 0,0 (unRAID engine)

Feb 28 21:29:27 Tower kernel: mdcmd (20): import 19 0,0 (unRAID engine)

Feb 28 21:29:27 Tower kernel: mdcmd (21): import 20 0,0 (unRAID engine)

Feb 28 21:29:27 Tower kernel: mdcmd (22): import 21 0,0 (unRAID engine)

Feb 28 21:29:27 Tower kernel: mdcmd (23): import 22 0,0 (unRAID engine)

Feb 28 21:29:27 Tower kernel: mdcmd (24): import 23 0,0 (unRAID engine)

Feb 28 21:29:27 Tower emhttp_event: driver_loaded (System)

Feb 28 21:29:27 Tower emhttp: shcmd (108): :>/etc/samba/smb-shares.conf (Other emhttp)

Feb 28 21:29:27 Tower avahi-daemon[1597]: Files changed, reloading.

Feb 28 21:29:27 Tower emhttp: Restart SMB... (Other emhttp)

Feb 28 21:29:27 Tower emhttp: shcmd (109): killall -HUP smbd (Minor Issues)

Feb 28 21:29:28 Tower emhttp: shcmd (110): cp /etc/avahi/services/smb.service- /etc/avahi/services/smb.service (Other emhttp)

Feb 28 21:29:28 Tower avahi-daemon[1597]: Files changed, reloading.

Feb 28 21:29:28 Tower avahi-daemon[1597]: Service group file /services/smb.service changed, reloading.

Feb 28 21:29:28 Tower emhttp: shcmd (111): ps axc | grep -q rpc.mountd (Other emhttp)

Feb 28 21:29:28 Tower emhttp: _shcmd: shcmd (111): exit status: 1 (Other emhttp)

Feb 28 21:29:28 Tower emhttp: shcmd (112): /usr/local/sbin/emhttp_event started (Other emhttp)

Feb 28 21:29:28 Tower emhttp_event: started (Other emhttp)

Feb 28 21:29:28 Tower emhttp: shcmd (113): rmmod md-mod |$stuff$ logger (Other emhttp)

Feb 28 21:29:28 Tower emhttp: shcmd (114): modprobe md-mod super=/boot/config/super.dat slots=24 |$stuff$ logger (unRAID engine)

Feb 28 21:29:28 Tower kernel: md: unRAID driver removed (System)

Feb 28 21:29:28 Tower kernel: md: unRAID driver 2.2.0 installed (System)

Feb 28 21:29:28 Tower emhttp: shcmd (115): udevadm settle (Other emhttp)

Feb 28 21:29:28 Tower emhttp: Device inventory: (Drive related)

Feb 28 21:29:28 Tower emhttp: SAMSUNG_HD204UI_S2H7JD2B108427 (sdb) 1953513527 (Drive related)

Feb 28 21:29:28 Tower emhttp: SAMSUNG_HD204UI_S2H7J9CB105081 (sdc) 1953514584 (Drive related)

Feb 28 21:29:28 Tower emhttp: SAMSUNG_HD204UI_S2H7J9CB105079 (sdd) 1953514584 (Drive related)

Feb 28 21:29:28 Tower emhttp: SAMSUNG_HD204UI_S2H7J9CB105083 (sde) 1953514584 (Drive related)

Feb 28 21:29:28 Tower emhttp: WDC_WD40EFRX-68WT0N0_WD-WCC4E0969816 (sdf) 3907018584 (Drive related)

Feb 28 21:29:28 Tower kernel: mdcmd (1): import 0 8,80 3907018532 WDC_WD40EFRX-68WT0N0_WD-WCC4E0969816 (unRAID engine)

Feb 28 21:29:28 Tower kernel: md: import disk0: [8,80] (sdf) WDC_WD40EFRX-68WT0N0_WD-WCC4E0969816 size: 3907018532 (Drive related)

Feb 28 21:29:28 Tower kernel: md: disk0 replaced (unRAID engine)

Feb 28 21:29:28 Tower kernel: mdcmd (2): import 1 8,32 1953514552 SAMSUNG_HD204UI_S2H7J9CB105081 (unRAID engine)

Feb 28 21:29:28 Tower kernel: md: import disk1: [8,32] (sdc) SAMSUNG_HD204UI_S2H7J9CB105081 size: 1953514552 (Drive related)

Feb 28 21:29:28 Tower emhttp: shcmd (116): /usr/local/sbin/emhttp_event driver_loaded (System)

Feb 28 21:29:28 Tower kernel: mdcmd (3): import 2 8,48 1953514552 SAMSUNG_HD204UI_S2H7J9CB105079 (unRAID engine)

Feb 28 21:29:28 Tower kernel: md: import disk2: [8,48] (sdd) SAMSUNG_HD204UI_S2H7J9CB105079 size: 1953514552 (Drive related)

Feb 28 21:29:28 Tower kernel: mdcmd (4): import 3 8,64 1953514552 SAMSUNG_HD204UI_S2H7J9CB105083 (unRAID engine)

Feb 28 21:29:28 Tower kernel: md: import disk3: [8,64] (sde) SAMSUNG_HD204UI_S2H7J9CB105083 size: 1953514552 (Drive related)

Feb 28 21:29:28 Tower kernel: mdcmd (5): import 4 8,16 1953513496 SAMSUNG_HD204UI_S2H7JD2B108427 (unRAID engine)

Feb 28 21:29:28 Tower kernel: md: import disk4: [8,16] (sdb) SAMSUNG_HD204UI_S2H7JD2B108427 size: 1953513496 (Drive related)

Feb 28 21:29:28 Tower kernel: mdcmd (6): import 5 0,0 (unRAID engine)

Feb 28 21:29:28 Tower kernel: mdcmd (7): import 6 0,0 (unRAID engine)

Feb 28 21:29:28 Tower kernel: mdcmd (: import 7 0,0 (unRAID engine)

Feb 28 21:29:28 Tower kernel: mdcmd (9): import 8 0,0 (unRAID engine)

Feb 28 21:29:28 Tower kernel: mdcmd (10): import 9 0,0 (unRAID engine)

Feb 28 21:29:28 Tower kernel: mdcmd (11): import 10 0,0 (unRAID engine)

Feb 28 21:29:28 Tower kernel: mdcmd (12): import 11 0,0 (unRAID engine)

Feb 28 21:29:28 Tower kernel: mdcmd (13): import 12 0,0 (unRAID engine)

Feb 28 21:29:28 Tower kernel: mdcmd (14): import 13 0,0 (unRAID engine)

Feb 28 21:29:28 Tower kernel: mdcmd (15): import 14 0,0 (unRAID engine)

Feb 28 21:29:28 Tower kernel: mdcmd (16): import 15 0,0 (unRAID engine)

Feb 28 21:29:28 Tower kernel: mdcmd (17): import 16 0,0 (unRAID engine)

Feb 28 21:29:28 Tower kernel: mdcmd (18): import 17 0,0 (unRAID engine)

Feb 28 21:29:28 Tower kernel: mdcmd (19): import 18 0,0 (unRAID engine)

Feb 28 21:29:28 Tower kernel: mdcmd (20): import 19 0,0 (unRAID engine)

Feb 28 21:29:28 Tower kernel: mdcmd (21): import 20 0,0 (unRAID engine)

Feb 28 21:29:28 Tower kernel: mdcmd (22): import 21 0,0 (unRAID engine)

Feb 28 21:29:28 Tower kernel: mdcmd (23): import 22 0,0 (unRAID engine)

Feb 28 21:29:28 Tower kernel: mdcmd (24): import 23 0,0 (unRAID engine)

Feb 28 21:29:28 Tower emhttp_event: driver_loaded (System)

Feb 28 21:29:28 Tower avahi-daemon[1597]: Service "Tower" (/services/smb.service) successfully established.

 

Is there an option to rebuild parity? That's what you'll need to do if your starting the array with the new parity drive.

no, can't find that anywhere.  No format either.  Only have th eoption to start array, start it in maintenance mode (which doesn't work either), identify (not sure what this does as nothing happens), reboot or power down.

Also, if I unassign the new HDD so I have no parity drive, the array starts.

The array will start without a partiy (I suppose, never had a reason to try it) but, I believe it is simply unprotected.

 

1. Did you run a parity check before bringing down the server to ensure no errors?

 

2. Did you preclear the new drive(s) - your post reads as though you took the drive out of the packaging and slapped it in place of where the old parity drive was and were going to rely on it just like that 

 

 

Oh and

 

3.  STOP doing -anything- on your unRAID until someone here can help you out (oddly, that has to be said)

 

Yes, had a parity check yesterday.  Everything was tip top.

 

I have literally opened the bag and put the new drive in.  I have read many messages before posting my plea for help.  The majority didn't see the need for a preclear for a parity drive.  I have the script ready and loaded on my thumb drive to run a preclear but I didn't want my system tied up in a 30+hour preclear if it wasn't absolutely necessary.

 

I am perplexed as to why the array does not start or throw up any errors in the syslog.  Admittedly, I am a relative novice, but nothing jumps out in the syslog.

Oh and

 

3.  STOP doing -anything- on your unRAID until someone here can help you out (oddly, that has to be said)

 

Wise advice!

 

I would NOT be starting your array without parity in any circumstance because any writes to existing discs beyond that stage will invalidate your EXISTING parity which means you have no fallback option at all in the event that a disc should go on you before the new parity is established, touch wood eh!. When replacing a parity disc your array should be offline until such time that parity has been re-established AND a parity check of that new parity has been completed. Then and only then shoud the array be restarted. As for why it's failing to start ... are you sure it's not formatting (there's no disc activity at all?) behinbd the scenes? A blue dot normally indicates a disc which is NOT part of the array yet. You have definitely assigned it as parity? Is it spinning up?

 

As for preclear ... i too am an UNRAID novice but would definitely NOT want to trust a brand new drive anywhere near my data!! Indeed I have a 4TB pre-clear going right now on a Seagate NAS 4TB drive, it's just touched 32hrs on its first of three cycles, gulp! You must be a brave man.

 

See last post here http://lime-technology.com/forum/index.php?topic=15757.0

I put the array on line without parity just to make sure that the new HDD was the cause.  Once it was on line, I took it down again.

 

Yes, definitely set as parity.

 

superloopy, did you try to start the array with your new drive or immediately go for a preclear?  Was it a data or parity drive?

As i say i'm no expert so best get confirmation here but if I were in your shoes i'd be dropping that parity out of the array, unassign it, then run preclear.sh against it to prove that it isn't RMA material. Can be done out of the array. Your existing parity can serve the array in the meantime but make sure that you do a aparity check against EXISTING parity disk again before restarting the array because it has been started without parity disc being in situ since your last check.

superloopy, did you try to start the array with your new drive or immediately go for a preclear?  Was it a data or parity drive?

 

Parity drive preclearing outside of the array. Once finished (Sunday eve) i'll swap with existing smaller parity drive safe in the knowledge (although nothing is ever guaranteed) that i've given it a good thrashing and it's safe to be unleashed on my system.

read the link, thanks superloopy.  But the implication there is that it is for future security of your data that a preclear is good practice and not that it is needed to make the HDD work in the array from the off. 

 

Once I know this HDD is compatible I'm happy to set it going on a preclear, I just don't want to find out in three days time, that I still have a non compatible disk!

I do have another WD red 4tb here that I am going to replace one of my data drives with.  Another 3 are coming on Monday.  I could try this other drive too as the parity drive.  Not now though, it's bedtime in NL! I will try tomorrow, thanks everyone for the help thus far.

There have been several examples here of failure to add large drives caused by conflicting add on software. Find a post by dgaschk and follow his signature to revert to totally stock, then try to add the drive again.

 

Also, as others in this thread have said, I would NEVER allow a drive into any position in my array without passing at least 1 preclear cycle, I typically do 3 cycles. If you want to use your array while this is going on, my advice would be to put the original parity drive back, and run a correcting parity check to get back protected while you are preclearing your new drives. If you have enough drive slots, you could preclear multiples at the same time, just be aware of memory limitations.

 

Also, as others in this thread have said, I would NEVER allow a drive into any position in my array without passing at least 1 preclear cycle, I typically do 3 cycles. If you want to use your array while this is going on, my advice would be to put the original parity drive back, and run a correcting parity check to get back protected while you are preclearing your new drives.

 

Agreed.

no, can't find that anywhere.  No format either.  Only have th eoption to start array, start it in maintenance mode (which doesn't work either), identify (not sure what this does as nothing happens), reboot or power down.

Just to clarify the "normal" operation when a new parity disk is assigned. You will be allowed to start the array and rebuild parity on the new parity disk. unRAID will not offer to format a parity disk as the parity disk has no file system.

 

Not sure what your current problem is. Maybe a screenshot would help.

 

Don't know which forum you were reading that didn't warn you against putting a new disk in without testing it first. While it is true that unRAID does not need the parity disk to be cleared everyone around here with any experience always recommends preclearing just to give it a good test before trusting it. If you add a bad disk to the array all of the other disks are unprotected.

Attach a syslog.

I put the array on line without parity just to make sure that the new HDD was the cause.  Once it was on line, I took it down again.

 

Yes, definitely set as parity.

 

Dumb question, but did you first click the checkbox for "Yes I want to do this" so that the "Start" button will change from Grayed-out to Normal?

After clicking the box, you can then press the Start button to "bring the array on-line and begin Parity-Sync".

 

 

I put the array on line without parity just to make sure that the new HDD was the cause.  Once it was on line, I took it down again.

 

Yes, definitely set as parity.

 

Dumb question, but did you first click the checkbox for "Yes I want to do this" so that the "Start" button will change from Grayed-out to Normal?

After clicking the box, you can then press the Start button to "bring the array on-line and begin Parity-Sync".

 

That's a good spot from the screenshot .... it may well be all that is needed here!

 

I would still recommend a preclear outside of the array though as this disc is brand spanking new out of the bag, hardly trustworthy material to throw at your array from the off. It is good practice to stress test the disc unless you KNOW its history ie moving it from one server to another.

 

... just checked my preclear - 44hrs in and only 24% through cycle 2 of 3. Takes a long time but it's definitely worth stressing your new disc to that extent before adding to your array.

I put the array on line without parity just to make sure that the new HDD was the cause.  Once it was on line, I took it down again.

 

Yes, definitely set as parity.

 

Dumb question, but did you first click the checkbox for "Yes I want to do this" so that the "Start" button will change from Grayed-out to Normal?

After clicking the box, you can then press the Start button to "bring the array on-line and begin Parity-Sync".

 

Ha!  I said I was a novice not a dim wit!!!  Yes, I know how to start the array.

 

Update time.  I took the drive out and connected to my laptop with the esata connector.  Set it up as an MBR partition, so only 2TB was seen, I didn't want to complicate things with GPT.  Gave it a quick format and plugged it back into my server.

 

Fired it up and lo and behold the array starts.  It is also seen as 4TB too.  Currently it is rebuilding the parity.

 

I had to do it this way as I couldn't just add one of my 4TB's in a spare slot and preclear as they would be bigger than the parity and would have messed things up.  So once I have the parity re-built I will then start pre-clearing my drives and adding them one by one. 

Good to hear youre up and running but i still dont understand what you mean by 'couldn't just add ..... as they would be bigger than the parity and would have messed things up'? That is exactly how you add a bigger drive. It matters not that it is larger to your existing array as at that time you havent included it in the array. And ...you can be preclearing at the same time as your parity is rebuilding. The two activities are not connected. Can i suggest a quick FAQ refresher while you're waiting on those preclears ... they'll take a good few days!

 

Dont forget to 'check' your newly written parity once it completes.

 

superloopy,  I don't think you are quite understanding, but never mind.  I'm up and running though.

 

I wonder why unraind cannot deal with a fresh, out of the packet drive.  Yes, I know there is preclear but this is not a prerequisite but good practice.  Maybe there needs to be a way to create the partition so unraid can use a disk from the webgui.

I don't think you are quite understanding. unRAID can deal with a fresh out of the packet drive as long as it is a good drive. If the drive turns out to be bad how is it supposed to deal with it? Keep your original parity drive handy and don't do anything to it until the parity finishes rebuilding on the new drive since it is the only protection you have.

 

Maybe you will be lucky. There was no point in partitioning and formatting the new parity drive since unRAID wipes that completely out. Formatting is also not a good test of the disk so you don't know whether you are building parity on a good disk or not.

 

You can plug in any drives you want and preclear them whether they are larger than parity or not. Only when you try to add them to the array does it matter whether the parity drive is as large.

 

For future reference, the correct way to do this would have been to leave your array with its original parity drive intact. Preclear one or more of your new larger disks. Take a drive that passed the preclear and use it to replace your original parity drive and let it rebuild parity.

 

Also, don't write to the array while parity is rebuilding since that would invalidate the parity on the original parity drive.

 

And, after (if) parity finishes rebuilding, you should immediately start a parity check to make sure the parity that was written can be read.

 

I know this sounds like a lot of worry but unRAIDs ability to rebuild a data drive depends on the integrity of all of the other disks in the array including parity. If you are not worried about this at least a little then there is no point in even bothering with a parity drive.