Disk in parity slot is not biggest with 3 identical drives

[Cheesemeister]

I have an odd issue with one of my unraid servers. over the past year it has been running just fine with 2 samsung 870 QVO sata SSD's running in the array devices slot #1 and #2. recently I started getting sector errors on a drive so I wanted to throw in a parity as part of my original plan. I bought the same 870 QVO drive from amazon and I cannot set as Parity. I get " Disk in parity slot is not biggest."

 

I read on some forums about these 2 fixes, but they didn't work.

1. GPT vs. MBR. I tried this, didn't work.

2. I precleared the new drive and it finished successfully.

 

I went and checked the sector count on all 3 drives and they are the same?

 

Not sure what to do, 

 

If this matters at all here are the specs, because I did read about motherboards being weird sometimes. This system is used as a 2-in-one gaming machine.

 

Mobo: MSI Creators TRX40

CPU: Threadripper 3970x

RAM: 128gb

GPU's 2x asus strix 3090's

Cache: 3x 2tb NVMe's

ARRAY: 2x 4tb 870 evo's (trying to add 3rd)

 

Thanks alot for the help! I have attached the diagnostics

hades-diagnostics-20220326-0211.zip

[wilsonhomelab]

I remembered Spaceinvader one in his channel said SSD cannot be used for parity in array.

Sent from my VOG-L29 using Tapatalk

[JorgeB]

Possibly existing SSDs were formatted with the old partition layout, post the output of:

 

fdisk -l /dev/sdX

 

for both array devices.

[Cheesemeister]

8 hours ago, JorgeB said:

Possibly existing SSDs were formatted with the old partition layout, post the output of:

 

fdisk -l /dev/sdX

 

for both array devices.

DEV 1:

root@Hades:~# fdisk -l /dev/sdb
Disk /dev/sdb: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: Samsung SSD 860 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: B1F04D5C-FA89-449C-B031-A699222B1249

 

Dev 2: 

root@Hades:~# fdisk -l /dev/sdc
Disk /dev/sdc: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: Samsung SSD 870 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 6815C5DE-12DD-438E-B62C-AB54D1DA0C98

 

Disk attempting to add: 

root@Hades:~# fdisk -l /dev/sdd
Disk /dev/sdd: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: Samsung SSD 870 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

 

[Cheesemeister]

ohh i did just notice one drive is an 860, not an 870. this is also the drive that has received 24 Reallocated sector counts if this matters at all.

 

[JorgeB]

Sorry, I missed the part where you precleared the drives, so there are no partitions, to make sure everything is wiped run

blkdiscard /dev/sdX

on all three, then add them to the array and post new diags if it still complains.