May 12, 20179 yr IS this the correct process 1. Stop array 2. Remove disk 1 from array 3. Add new larger disk 4. Start array (rebuild) 5. once rebuilt stop array 6. remove other small disk 7. start array (rebuild)
May 12, 20179 yr Community Expert 2 minutes ago, Greygoose said: 7. start array (rebuild) Rebuild what? You'll need to copy the data from the small disk to other disk(s) before removing it from the array, then do a new config.
May 12, 20179 yr No. In step 7 you have no target to rebuild to. You must copy the data from the slot you ultimately want to remove to another array slot, once that is done you can set a new config without the disk you want to completely remove and then rebuild parity.
May 12, 20179 yr Author Just now, johnnie.black said: Rebuild what? You'll need to copy the data from the small disk to other disk(s) before removing it from the array, then do a new config. Ok, I see. So if i use krusader, go into the disk2 folder (drive i need to copy data from) and copy it to the larger disk?
May 12, 20179 yr Community Expert 2 minutes ago, Greygoose said: Ok, I see. So if i use krusader, go into the disk2 folder (drive i need to copy data from) and copy it to the larger disk? Yes, copy to another disk, not to an user share. Edited May 12, 20179 yr by johnnie.black
May 12, 20179 yr Author Thanks Johnnie, Im running pr clear test on my new 6TB so once its complete ill do as above
May 13, 20179 yr 9 hours ago, Greygoose said: Thanks Johnnie, Im running pr clear test on my new 6TB so once its complete ill do as above Your new drive has been the same size or smaller than your parity drive. If it is, just pull the old drive and swap in the new drive and rebuild (or copy the files). Rebuild what? You'll need to copy the data from the small disk to other disk(s) before removing it from the array, then do a new config. You could just rebuild the array right - because the replaced drive would be considered a failed drive? Edited May 13, 20179 yr by coolspot
May 13, 20179 yr Best way to do this is as follows: 1 - Perform a parity check if one has not been performed recently 2 - Check the SMART reports on all of the drives after the parity check. If signs of problems, post the diagnostics file. If all looks good ... 3 - Let unRAID format the new disk. A little tricky to do . Best to boot from a trial stick, add the the new precleared disk as "disk1" with no parity. Start the "array". Let unRAID format the disk. Stop the array. 4 - Boot into your normal configuration from normal stick 5 - Mount new disk outside the array (use unassigned devices plugin is probably easiest way) 6 - Copy the data from the first disk you want to remove to the new disk (this will go at full speed since dest disk is not in the array). Use a "screen" session or do from the command line on the server itself. 7 - Copy the data from the second disk you want to remove to the new disk (ditto) 8 - Stop the array. 9 - Do a "new config". Assign disks to slots as desired. Make sure you get parity in the parity slot. If you want to rearrange - this is a good time. (Might have to re-visit user share configurations later). Include the new disk. Omit the 2 disks you don't want in the array. (These will act as backups of the data copied to the new disk). 10 - Start the new configuration for the first time, parity will build. 11 - Always good to do a parity check after a parity build
May 13, 20179 yr Author 3 hours ago, bjp999 said: Best way to do this is as follows: 1 - Perform a parity check if one has not been performed recently 2 - Check the SMART reports on all of the drives after the parity check. If signs of problems, post the diagnostics file. If all looks good ... 3 - Let unRAID format the new disk. A little tricky to do . Best to boot from a trial stick, add the the new precleared disk as "disk1" with no parity. Start the "array". Let unRAID format the disk. Stop the array. 4 - Boot into your normal configuration from normal stick 5 - Mount new disk outside the array (use unassigned devices plugin is probably easiest way) 6 - Copy the data from the first disk you want to remove to the new disk (this will go at full speed since dest disk is not in the array). Use a "screen" session or do from the command line on the server itself. 7 - Copy the data from the second disk you want to remove to the new disk (ditto) 8 - Stop the array. 9 - Do a "new config". Assign disks to slots as desired. Make sure you get parity in the parity slot. If you want to rearrange - this is a good time. (Might have to re-visit user share configurations later). Include the new disk. Omit the 2 disks you don't want in the array. (These will act as backups of the data copied to the new disk). 10 - Start the new configuration for the first time, parity will build. 11 - Always good to do a parity check after a parity build 7. Can i do this in Krusader, and do i copy the Folder say,,, Disk 2 over to the larger (new disk). So the larger NEW disk will have maybe,,, Disk 2 and Disk 3 folders... Then when i assign new config it will rebuild this into the array? I have 1 disk at the moment that is causing issues, Errors... My plan was to Stop array, remove this disk and rebuild the array with the New larger disk,.,,, Then my thinking was i just need to copy over the other small disk to the new larger disk in krusader as i mentioned above (now part of the rebuilt array)... Then i'm not sure??? new config as you suggested..
May 13, 20179 yr I didn't understand you had a problem disk. If so, I would not do a parity check to start. But would follow rest of the directions, copying data front the problem disk first. You can use Krusader. Copy don't move. You can mix files from multiple disks.on the target disk. Rebuilding as the first step is also valid. I just prefer to do the file level I/O as it is typically faster in total. You can copy your most precious files first. If a disk fails in the middle, the file copy will continue as your parity disk helps to simulate the failing disk.
Archived
This topic is now archived and is closed to further replies.