[(6.8.1) Replacing existing disks with larger ones]

Thanks for clearing that up : )

[(6.8.1) Replacing existing disks with larger ones]

OK,  the word "copy" is not correct in relation to rebuild from parity. I can see it is not a strict "copy" but it would recreate the data that was on 1TB(a) from the parity disk onto the new disk. I'll get the hang of the terminology at some point, Thanks for pointing it out.

 

I understand your advice to be take out 1TB(a), put in 3TB(a), rebuild, take out 1TB(b), put in 3TB(b), rebuild. 

Ending up with 2 larger instead of 2 smaller.

 

And then I am done. No need to make new config?

 

I was thinking it would be best to have the date on one single disk, so that only that disk would have to spin up. Leaving the other disks in the array "unused" ( for lack of better word) until needed. But not important, if you say it isn't.

 

Thanks for taking the time tot answer my questions, really appreciate it.

6 hours ago, trurl said:

And no parity rebuild is needed. Why would it? Parity was used to rebuild the data disks, so the data disks match parity.

Yes I understand now. I was not sure if the parity would update itself in this process, but it only does that if I tell it to, or have it scheduled.

[(6.8.1) Replacing existing disks with larger ones]

Ok : ) like I said I am a noob, thank you for the rescue. And sorry for the confusing explanations that follow underneath

 

Also I messed up my question. I intend to first put in one 3TB and collect all shares on that one new disk. Then put in extra 3TB disks to get more space.

 

I added the disks to the enclosure and hooked them up to SATA to the motherboard. I formatted as XFS and mounted them via Unassigned Devices.

 

I then used Terminal on my Mac to SSH in and copied:

 

/mnt/Disk1/myfiles

/mnt/Disk1/Media

/mnt/Disk1/appdata

/mnt/Disk1/domains

/mnt/Disk1/isos

/mnt/Disk1/system

 

To .../disks/WDC_WD30EFRX

 

then I copied

 

/mnt/Disk2/myfiles

/mnt/Disk2/Media

/mnt/Disk2/appdata

/mnt/Disk2/domains

/mnt/Disk2/isos

/mnt/Disk2/system

 

To .../disks/WDC_WD30EFRX

 

I accidentally copied "/appdata /domains /isos /system" from /mnt/user/ instead of /mnt to the new 3TB drive but I deleted each share and re copied from mnt/Disk1

 

I was going to do the new config thing without the old drives. My understanding was that I would still have the option of recreating the array with old drives. I am trying to learn this and not just following steps and not fully understanding what I did. So I don't mind a little extra work. I already learned to SSH and a little about how the file structure on Unraid is laid out

 

Are you saying I could have just taken out 1TB(a) and replaced it with 3TB(new), let it rebuild, then taken out 1TB(b), let it rebuild and I would have been done? Then I will do that : )

 

I did read about that method, but what I couldn't understand about the method you prescribed is that I have my shares on 2 separate disks.

And I think it would be best to have my data on one single new larger disk. If I removed disk 1TB(a), put in 3TB(new), it would take the part of the shares on 1TB(a) and put that onto 3TB(new). Could I then remove the last small disk 1TB(b) and it would now copy the rest of the data from the shares to the correct directories on the one new larger disk, 3TB(new)?

 

1TB(a)  /Share1   /Share 2   /Appdata

1TB(b)  /Share1   /Share2.   /Appdata

3TB Parity

 

3TB(new)  Rebuilds the data from 1TB(a)

1TB  /Share1   /Share2.   /Appdata

3TB Parity

 

Now my confusion starts

 

3TB  /Share1   /Share 2   /Appdata (Adds the data to the share from 1TB(b)

1TB(b) Removed

3TB Parity

 

or 

 

3TB  /Share1   /Share 2   /Appdata

3TB(new)  Rebuilds the data from 1TB(b)

3TB Parity

 

Is there a rebuild of parity in between somewhere?

 

I am trying to learn and I assume I can just recreate the whole array with the original drives, if I mess up the process on the new ones.

 

Sorry for the massive post, I tried to make it easier to read what I did by formatting it this way, hope it worked

The MC image is to show my method of copying

tower-diagnostics-20200125-0616.zip

[(6.8.1) Replacing existing disks with larger ones]

First of all, sorry for posting about a question that has been asked many times before. I searched a lot, but could not find a solution that mirrored my situation. I am a total noob and I don't really know what I am doing, so thought it best to ask before I wreck my array.

 

I have (Disk1 = 1 TB) + (Disk2 = 1 TB) + (ParityDisk = 3 TB), both 1TB drives have the same 8 shares and are High Water.

 

My 2 new 3TB drives are installed and pre cleared.

I am thinking I will use the MC function and move the data from the old drives to the new ones.

I want to move everything from Disk1 and Disk2 to one  3TB disk.

Now my problem is that both 1TB disks have the same Shares but they contain different files.

Do I first copy the whole Share from Disk1 to the 3TB disk and afterwards navigate into the Share on Disk2 and move the rest of the files into the Share that now exist on the 3TB disk. And repeat for all Shares?

Is there a way to just copy a Share and have all data from both Disk1 and Disk2 get all data copied at once?

 

Alternatively I am considering just copying all the data to a USB disk and building a new Array from scratch