Can't add second parity drive that is the same size as the largest data drive

attach diagnostics NEXT post

unraid-diagnostics-20210919-1731.zip

01:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9215 PCIe 2.0 x1 4-port SATA 6 Gb/s Controller [1b4b:9215] (rev 11)

Marvell controllers NOT recommended, though probably not the cause of this issue.

 

What do you get from the command line with this?

hdparm -N /dev/sdc

 

Understand about the Marvell; I will look for a different option (I need a half-height PCIe expansion board with at least 4 ports).

 

root@unraid:~# hdparm -N /dev/sdc

/dev/sdc:
 max sectors   = 19532873728/19532873728, HPA is disabled
root@unraid:~# hdparm -N /dev/sdf

/dev/sdf:
 max sectors   = 19532873728/19532873728, HPA is disabled

 

 

Thanks; I will buy the FebSmart ASM1064 PCIe 1x controller.

Disks have the same number of sectors, but the size being detected by Unraid is different:

 

Quote

 

Sep 19 04:32:23 unraid kernel: md: import disk3: (sdf) WDC_WD100PURZ-85W86Y0_7JKSZ7MC size: 9766436812

Sep 19 04:32:23 unraid kernel: md: import disk29: (sdc) WDC_WD100PURZ-85W86Y0_7JKX88SC size: 9766435820

 

 

Likely partition on parity2 starts on sector 2048 instead of the standard Unraid sector 64, can you please post the output of:

 

fdisk -l /dev/sdX

 

replace X with the correct letter for both disks.

Does it have something to do with one being on the motherboard controller and one on the Marvell controller? I have a new controller I can try.

 

root@unraid:~# fdisk -l /dev/sdc
Disk /dev/sdc: 9.1 TiB, 10000831348736 bytes, 19532873728 sectors
Disk model: WDC WD100PURZ-85
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: 55200E74-35FD-2444-A1C3-F74DDF3DDD61

Device     Start         End     Sectors  Size Type
/dev/sdc1   2048 19532873694 19532871647  9.1T Linux filesystem

 

root@unraid:~# fdisk -l /dev/sdf
Disk /dev/sdf: 9.1 TiB, 10000831348736 bytes, 19532873728 sectors
Disk model: WDC WD100PURZ-85
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: B566F1E4-F89E-4197-B61E-58ADA7569255

Device     Start         End     Sectors  Size Type
/dev/sdf1     64 19532873694 19532873631  9.1T Linux filesystem

 

7 minutes ago, zbot said:

Device     Start         End     Sectors  Size Type
/dev/sdc1   2048 19532873694 19532871647  9.1T Linux filesystem

 

Like suspected this is the problem, Unraid standard partition start is sector 64, except for non rotational devices, this partition starts on sector 2048, so it's smaller than it should be, you need to erase the current partition with fdisk then let Unraid repartition the disk, though it should detect the non standard partition and do it automatically.

9 minutes ago, JorgeB said:

Though it should detect the non standard partition and do it automatically.

 

Ok, so there is a bug then. 

 

What's the fdisk command to erase it?

fdisk /dev/sdX

 

Double check it's the correct device then type

d

 

then

w

to writes changes

After this command it now gives me the option to start the array with the disk in Parity 2 slot. 

 

All existing data on this device will be OVERWRITTEN when array is Started

 

Not sure how that partition got there or why it caused this issue but thanks very much for the fix.