Perc 730 mini - replaced failed disk and new one won't rebuild array - just says "Ready"

Hello, could you continue with assigning as a global hot spare? As long as you succeed in rebuilding, it shouldn't be a problem I think. This may help your understanding https://dell.to/4aKuDTh Please let us know if you have any further questions.
Respectfully, 
https://dell.to/4gpIgYU

Yes I could continue as assigning as hot-spare, but it never jumped in and actually became the hot-spare for that array with the failed disk. Especially since it said in the message " This Physical disk is not suitable to protect all current or potential virtual disks on this controller." It just sat there and said "Ready" - the disk that went into rebuilding mode was the older hard drive that originally had the "failed" status and I pulled it and popped it back in. The other drive never did anything past "ready" status. 

Jsdrexel2,

The only reason you will see that error is if the drive is of a different type (HDD, SSD), is slower, or is smaller than the original drives. Now I have seen drives with the same size giving the error, and it was attributed to the fact that the manufacturers' header space at the start of the drive was bigger than the original drives, so the controller saw it as a slightly smaller drive. The easiest way around the issue is to install either larger drives altogether, or to use the same drive part number that is already installed and match the drives.

I did use the exact same drive numbers in the replacements -- I put in 2 replacements, one has a slightly different drive number, the other the exact same. The only difference I saw was the block sizes, and I haven't figured out how to change that? 

Here's the info on the one that's good:

ID 0:1:0
Status OK
Name Physical Disk 0:1:0
State Online
Power Status Spun Up
Bus Protocol SAS
Media HDD
Failure Predicted No
Revision LS21
T10 PI Capable No
Certified Yes
Capacity 9,248.50GiB
Used RAID Disk Space 9,248.50GiB
Available RAID Disk Space 0.00GiB
Hot Spare No
Vendor ID DELL(tm)
Product ID HUH721010AL4200
Serial No. 7PGLA8SG
Part Number TH0YG2KH1256768Q03SLA00
Negotiated Speed 12.00 Gbps
Capable Speed 12.00 Gbps
Logical Block size 4KB
Manufacture Day 06
Manufacture Week 35
Manufacture Year 2016
SAS Address 0x5000CCA25121551D
WWN 0x5000CCA25121551D
Non-RAID HDD Disk Cache Policy Not Applicable
Cryptographic Erase Capable Yes

Here's the one that just shows "Ready":

ID 0:1:10
Status Non-Critical
Name Physical Disk 0:1:10
State Ready
Power Status Spun Up
Bus Protocol SAS
Media HDD
Failure Predicted No
Revision A3Z4
T10 PI Capable No
Certified No
Capacity 9,313.50GiB
Used RAID Disk Space 0.00GiB
Available RAID Disk Space 9,313.50GiB
Hot Spare No
Vendor ID HGST
Product ID HUH721010AL4200
Serial No. 7PGB2RTG
Part Number Not Available
Negotiated Speed 12.00 Gbps
Capable Speed 12.00 Gbps
Logical Block size 512B
Manufacture Day Not Available
Manufacture Week Not Available
Manufacture Year Not Available
SAS Address 0x5000CCA251142965
WWN 0x5000CCA251142965
Non-RAID HDD Disk Cache Policy Not Applicable
Cryptographic Erase Capable Yes

Sizes appear to be good? Only the Logical Block Size is different and it states that in the error -- "Possible reasons include: Insufficient physical disk space, unsupported mix of SAS and SATA type physical disks, unsupported mix of SSD and HDD type physical disks, unsupported mix of 512Bytes and 4KBytes Logical Block size physical disks"

If that's the case, how would I change the block sizes? That's the only thing I saw a difference in. 

Would you clarify a couple things for me?

What is the specific server model number are you installing the drives in?

What are the specific part numbers of the drives, or can you provide detailed pictures of the drives labels. 

That will help verify compatibility. 

The Server is a PowerEdge R730xd - the part numbers are in the info I sent over. But here is a pic of one of the drive labels

Thank you, I just wanted to verify it was a compatible drive. Now as far as it being used as a hotspare, you wouldn't be able to. The reason is that while the server and controller both support using 4k and 512b drives, you can't mix them within the same virtual disk. Meaning you can have a virtual disk with a couple 4k drives, and also have another virtual disk with a couple 512b drives, but you cant have a virtual disk made up of both 4k and 512b drives, it isn't supported. Also, there isn't a way to change the block size of the drives. 

Ok - thanks for the info - but how do we know if drives we purchase will have 512B or 4K sectors? I've never had this happen before in my 35+ years of this....crazy. I don't see any designator on the drives that show this....

The drive has an Advanced 4kn Format icon on it (black square with white lettering).

So does the 4Kn mean that the drive is going to come with the 512B sector size? All of these drives I'm seeing online all have that same 4Kn designator. So would I need to find one that's not 4Kn? 

Also, is there an option to rebuild the array with the mix of drives from scratch? Meaning wipe out the existing array and re-create it?

If you were to delete and reconfigure, it would have to be with all 4k drives or all 512b drives within a single virtual disk, as you can't mix them. Also, the 4k is the standard on most current drives, while the 512b is older technology.

Ok apparently that might not be the total issue -- since the drive I pulled that was formatted with 4K sectors also has that 4Kn designator on it and it was using the 4K sector size? So how would I know if a replacement drive has 512B versus 4K sector size?

Ok - so pretty much all the 4Kn drives should be setup as 4K sector sizes? I might have just got a couple of flukes?