Can not start Array after adding new drive

[Chelun]

Hello all, I am pretty new with Unraid, the truth is that it has been running for years without issues. When I originally installed it I had it with a bunch of different dirves, (2) 8TB, (1) 5TB, (1) 4TB and (1) 2TB. Worked perfect but I have no need for that many drives so I decided to replace the 5,4 and 2 for a new 8TB drive that I removed from another host. 

I already removed the 2 and 4 TB with out issues, but the 5 has some data that I want to move to the new 8TB, So I left it in place for now.

My issue is the new 8TB is recognized but I can not add it as a Data drive, it only let me add it as Parity 2 drive. 
Can anyone help me on setting it up as a Data drive?

Here is some screenshots of my setup.

 

Thank you in advance!

[JorgeB]

Possibly the existing parity are using a smaller partition, please post the diagnostics.

[Chelun]

Here it is

nasty-diagnostics-20240219-1223.zip

[JorgeB]

Parity has the partition starting on sector 2048, this will happen if the disk already had a valid partition on that sector, e.g., it had been previously used with another OS, best way to fix this for the future, is to wipe parity, re-sync and then add the new disk, alternatively you could partition the new disk on that sector and then add it to the array to avoid a new parity sync, but can have the same issue in the future, also would need to update to v6.12.8 first.

[Chelun]

The parity drive is the same one, did not change it at all. 

the new drive (sdd) was used in a Windows VM for a while, I decomm'ed the VM and now I want to reuse the drive here in the unraid server.

sdc is the parity and sdd is the new drive, when I open fdisk on each drive I see the sdc as bigger, so I don't understand what I am doing wrong here.

Disk /dev/sdc: 7.28 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: ST8000VN0022-2EL
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: B9C9F102-FCCB-4E59-AFB6-6561A40FD7B8

Device     Start         End     Sectors  Size Type
/dev/sdc1   2048 15628053134 15628051087  7.3T Linux filesystem


Disk /dev/sdd: 7.28 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: ST8000NM0105    
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 86B8EC10-FC00-4864-B442-E5EEFA93FBA1

Device     Start         End     Sectors  Size Type
/dev/sdd1   2048 15628052479 15628050432  7.3T Linux filesystem

I will update to 6.12.8 as soon as I finish this post.

 

[JorgeB]

26 minutes ago, Chelun said:

The parity drive is the same one, did not change it at all. 

That's not what I meant, just that before it was used as parity it must have been used with a different OS, i.e., it wasn't a new blank disk.

 

28 minutes ago, Chelun said:

sdc is the parity and sdd is the new drive, when I open fdisk on each drive I see the sdc as bigger, so I don't understand what I am doing wrong here.

sdd doesn't have a valid Unraid partition, it's not using the full disk, so Unraid wants to create a new one, and the new one would start on sector 64, so it would be larger then the existing partition on parity, I can give you the command to create a new Unraid compatible partition on the new disk to avoid messing with parity, but you may have the same issue in the future.

 

[Chelun]

25 minutes ago, JorgeB said:

I can give you the command to create a new Unraid compatible partition on the new disk to avoid messing with parity

Please, I will run it and then after the drive is in, I can rebuild the parity.

[JorgeB]

Don't forget that you will need to be on v6.12.8, it won't work with previous v6.12.x releases due to a bug:

 

Unassign the disk, then type:

 

sgdisk -o -a 8 -n 1:1M:0 /dev/sdX

Replace X with correct letter, re-assign the disk, if you get the same error reboot, but it's usually not needed al long as you unassign and re-assign.

[Chelun]

Thank you so much!! That command fixed it!
Now the array started with the 8TB as data drive and parity check is in progress!!!!

Thank you again