Does this operation lose data?

[grays]

hi all:

  i have two unraid server ,today , i get one HDD from unraid A and put it into unraid B. this HDD contain a docker data with gitlab-ce ,unraid B also has a gitlab-ce data in appdata .when i start unraid B, i found The gitlab-ce data on unraid B losted and became gitlab-ce data on unraid A ,and i cant found the lost data.. dose it unsafe move A HDD from a unraid to another one ?

 

Edited November 28, 2020 by grays

[itimpi]

How did you add the drive after moving it?  It should have showed up just fine in Unassigned Devices with its data intact.   If you tried to add it to the array or to an existing cache pool then the data could well be lost  as those actions expect the disk to not contain any data you want to keep.

[grays]

9 hours ago, itimpi said:

How did you add the drive after moving it?  It should have showed up just fine in Unassigned Devices with its data intact.   If you tried to add it to the array or to an existing cache pool then the data could well be lost  as those actions expect the disk to not contain any data you want to keep.

tks for reply ,my unraid A is 6.8.2 ，and when i put the HDD Into unraid b( 6.9.0 beta35), HDD Is unassigned ,and i assign it to a disk3,  the HDD fs show "auto", and i also have a 4T parity hdd on unraid b, when a start array , unraid seem to move data. after that , unraid b tell me format HDD ,i do that。 HDD fs became “xfs”.and ，i lost my  gitlab-ce data on unrad B disk1...😂

Edited November 29, 2020 by grays

[itimpi]

3 hours ago, grays said:

tks for reply ,my unraid A is 6.8.2 ，and when i put the HDD Into unraid b( 6.9.0 beta35), HDD Is unassigned ,and i assign it to a disk3,  the HDD fs show "auto", and i also have a 4T parity hdd on unraid b, when a start array , unraid seem to move data. after that , unraid b tell me format HDD ,i do that。 HDD fs became “xfs”.and ，i lost my  gitlab-ce data on unrad B disk1...😂

If you assign a drive to a parity protected array then the first action that Unraid will take is to ‘clear’ the drive (by writing zeroes to every sector of the drive) to keep parity valid.  This will erase any existing content and leave the drive ready to be formatted to the file system you choose (auto means use the default setting).  From your description this is what has happened.   

[grays]

8 hours ago, itimpi said:

If you assign a drive to a parity protected array then the first action that Unraid will take is to ‘clear’ the drive (by writing zeroes to every sector of the drive) to keep parity valid.  This will erase any existing content and leave the drive ready to be formatted to the file system you choose (auto means use the default setting).  From your description this is what has happened.   

 

If you assign a drive to a parity-protected array, the first action Unraid will take is to “clean” the drive (by writing Zeros on each sector of the drive) to keep the parity valid. This deletes any existing content and prepares the drive for formatting to the file system of your choice (which automatically means using the default settings) . According to your description, that’s what happened.

new HDD is disk3 had gitlab-ce docker data

old HDD is disk2 also had gitlab-ce docker data.

when i put new HDD into array，and start ,parity found new HDD has gitlab-ce data and move it into disk2..

i think that cost my data lost...

 

Edited November 29, 2020 by grays