Good to know, thanks! I'm still quite the n00b when it comes to FreeBSD (been a Windows guy for almost 15 years now... :/ ) so I'm still learning.
The reason I forced a 4096k sector size when I created the pool though was because one of the drives happened to be an older 512k drive. It's a long story, but the short of it is when I bought my drives, I had bought them through Newegg when they had a great deal on them. One of them turned out to be bad so I had to send it in for a warranty exchange. In the meantime, to get the system up and running with all the drives, I went out and bought another 2TB WD drive locally in a retail box. Turns out that drive was an older non-advanced format drive. :/
You have me wondering though. If TECK has AF drives but they're not being detected correctly, could he have the jumper on the back set for compatibility with non-AF aware OS's?
The reason I forced a 4096k sector size when I created the pool though was because one of the drives happened to be an older 512k drive. It's a long story, but the short of it is when I bought my drives, I had bought them through Newegg when they had a great deal on them. One of them turned out to be bad so I had to send it in for a warranty exchange. In the meantime, to get the system up and running with all the drives, I went out and bought another 2TB WD drive locally in a retail box. Turns out that drive was an older non-advanced format drive. :/
You have me wondering though. If TECK has AF drives but they're not being detected correctly, could he have the jumper on the back set for compatibility with non-AF aware OS's?
Your does because the FreeBSD succeeds to detect the disk as a 4096 sector size, in some cases the OS can retrieve that info correctly, in some it doesn't (depending on the disk, firmware version, achi mode, etc)
For example, in my WD15EARS it shows as 512 sector size, still it works pretty ok with the 4k sector size checked...