Jump to content

Adding NTFS drives to existing ZFS Array (with no parity at the moment), need help on format/assign steps...


RichB
Go to solution Solved by RichB,

Recommended Posts

I'm in the process of first steps to building my unRAID server. So far I had created an array of 3 4tb nas drives into an array with no parity drive (yet). I had a few other drives from a Win/NTFS das setup that I migrated content over using Krusader. Then I wanted to take to older drives and add them to the array.  What I did next stopped existing array. I then enabled destructive mode on unassigned disks. I then cleared the partitions on the old disks. I went to tools, new config and applied. Went back to main and was going to format the new, old drives I want to add to the array.

 

Now they each have a format option nex to them and the prior drives in array have a grayed out 'mount' button. When I go to format the drives to be added as ZFS, it is asking me for a Pool Name. Should I have this value already or is this brand new pool name? This confused me and I don't want to destroy the existing array drives content in anything I do. Should I just make up a pool name and start formatting the new drives? How will this affect the drives that were in the old array config? I'm scared to break something that causes data loss on the 3 original drives in array.

 

Finally, in the original array the first 3 drives in array were 4TB in order: sdb, sdc, sdd below with the grey mount buttons. When I assign drives to slots above at the end, does the old to new slot order matter? I may have only selected to keep the cache array assignments preserved in new config screen : (  If I can get past the format/ZFS pool name step, should I add just all drives above in any order to the array itself first as step 1, than after confirming added, stop array again then add the largest 14Tb as the parity drive or just do all at once?

 

Sorry for the long post, just nervous being my first time through adding new disks and don't want to lose anything. Thanks in advance!!!

image.thumb.png.973d0ec9dd734b924b05732e71dee451.png

FYI: The UI seems to not allow me to put the 4Tb disks back in their original slots in array, which were Disk 1-3 corresponding to sdb-sdd drives. Seems to force the unformatted 8Tb below into disk 1 slot. Maybe I have to format the new ones first?

image.thumb.png.926431129235061b8578be5e5da735fa.png

Link to comment
9 minutes ago, RichB said:

Went back to main and was going to format the new, old drives I want to add to the array.

Add to array first, set FS you want then format.

 

Slot order doesn't matter.

 

What's your reason for using ZFS? Cause it might not apply in the array. Array drives are always single, independent filesystems.

 

Edited by Kilrah
Link to comment

I had the original 3 - 4tb drives in a zfs array with a 4tb parity drive, so they are presently ZFS with data on them I don't want to lose. Then I decided I wanted to expand the array and used more drives I had in a windows DAS setup. I then did new config, removed the parity drive to speed the migration. Migrated the files, now want to build a new array with all the drives listed and make the 14Tb my parity drive.  

 

So you're saying add all of the drives I desire into array first (including the parity drive at same time?), then format the ones needed. Or should add all but the 14tb parity, format them, then when done, stap array and add in the parity drive which will build from scratch?

 

Will this have any destructive effect on the existing 3 qty 4Tb drives with data presently formatted as ZFS? Does the disk #/order of new array matter relative to the original slots held by the 3 - 4tb drives?

 

Thank you very much for your reply and help!

Edited by RichB
Link to comment

FYI, I'm trying to add back the original and 'new' drives in the array devices section and the UI is not letting me add some or forcing the 8Tb's into slots. Really weird behavior. Did I break the array? Do I have to create a new 1 drive array and then do another new config not saving any drive assignments or cache only? This feels really weird behavior and confusing

Link to comment
4 minutes ago, itimpi said:

ZFS drives in the main array are all single drive file systems.  You can only have multi-drive ZFS arrays in a pool.

I'm new to ZFS and unraid so don't know the nuances. I just want to add the 3 Tb drives that were in the functioning array back in with the new drives. They were each formatted individually as ZFS. The drive array UI slots will not let me select the drives I want into each slot. It's forcing a new 8Tb in Disk 1 slot and for some of the existing drives from former array it won't let me add in any slot. Sorry, I'm confused

Edited by RichB
clarity
Link to comment

Follow up weirdness and don't poke at me for my homelab build...TLDR : I think the USB3 DAS enclosures are confusing the ids/drives unraid sees across two enslosures. 1 DAS works fine and UI acts normal with array disk assignments.

 

I have a mini PC with two 4 bay USB3 DAS enclosures to leverage existing stuff and try this out. So I build with the first 4 bay and the 4 qty 4tb drives. Goes nicely. I decide to grab the 2nd DAS enclosure and drives. Drop one 4Tb parity drive in first DAS/Array. Plug in the 2nd DAS and migrate all the data to the shares on the 3 drive/no parity array. I also backup key files onto another external WD 4Tb usb drive just in case. Now I'm ready to format the old drives which were NTFS and add them to the array. Here's where the weirdness begins. If I try to add drives from the original array to the new array setup, the UI gets wonky. Won't let me add some of the original 4Tb's into the array. When I unplug the 2nd DAS, all of the larger drives I migrated from drop of course and magically all 4 of the 4Tb drives in the 1st DAS get recognized without an issue. The moment the 2nd DAS gets plugged in the UI doesn't allow me to add some of the 4Tb's to the array. I think this is getting into USB weirdness zone. 

 

Any ideas on how to make this work? Since both DAS are identical, could some id's be identical causing unraid to get confused on drive ID's? Would a usb hub in front of one help make unique? Please don't make fun of this goofiness. I'm trying to save some money versus buying a whole new build for $$$. Thx for any advice and sorry for the long story.

Link to comment
  • Solution

Well, I've found out that there are a multitude of potential issues in using unraid with multiple USB DAS ensclosures, so my little homelab has to do some growing up it seems. I have one more trick up my sleeve and that's an 8 bay Syba USB3 DAS enclosure before I rule it out altogether. Nice thing about this one is it is physically switched so no soft sync on power through USB to PC.

 

I'll set this as solution out to let others see what a mess multiple USB enclosures can be. Will post follow ups if my 8 bay enclosure does what I want. Thx to those who replied

Edited by RichB
clarity
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...