drive in parity is not the biggest

[sluggathor]

hi

i shucked a wd elements 8tb into my array and now i am getting the error that the parity drive hast to be the biggest.

my current setup is:

 

data: 6 disk (4-8tb wd reds)

parity: 1 disk (8tb wd red)

 

i want to add the shucked drive as a data disk but get the error about parity not being the biggest disk.

sector counts on the disks are identical

 

what gives?

 

EDIT: nvm the partition on the shucked drive is slightly smaller than the parity ( 7.814.025.540 vs 7.814.026.532)

 

jarvis-diagnostics-20220331-1144.zip

Edited March 31, 2022 by sluggathor
added diagnostics and findings

[JorgeB]

Likely the remaining disks are partitioned on sector 2048, instead of Unraid default sector 64.

 

You can check with

fdisk -l /dev/sdX

 

[sluggathor]

yes you are correct, which is still a strange thing because i've created and formatted the drives using unraid. why would it put the partitions down inconsistently?

Edited April 1, 2022 by sluggathor
typo

[JorgeB]

9 hours ago, sluggathor said:

which is still a strange thing because i've created and formatted the drives using unraid.

This usually happens when the drives already have a partition starting on sector 2048, Unraid will format the drive but use the existing partition, since that starting sector is now valid for SSDs, it should never happen with a new or completely wiped disk.

[sluggathor]

i see. the drives were carried over from another nas setup - i had unraid format them. should i use pre-clear next time or does deleting the old partition before formatting them next time?

[JorgeB]

Deleting the old partition(s) is enough.