WD20EARX. openSUSE 11.4 reported 4kSector but FreeNAS8.01Beta3 shows 512Sector

Status
Not open for further replies.

super-hornet

Cadet
Joined
Jun 29, 2011
Messages
8
I have 3 pieces of new Western Digital WD20EARX.
In openSUSE 11.4, when I do a hdparm, it indicated that it is physical of 4096byte sectors size.

When I install FreeNAS 8.01 Beta 2, I choose the "Force to use 4k sector" option during creating a RAIDZ using the above 3HDD.

I just upgraded to FreeNAS 8.01 Beta 3 but when I view the "/var/run/dmesg.boot ", I notice it reported:
ada0: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
ada1 at ahcich13 bus 0 scbus15 target 0 lun 0
ada1: <WDC WD20EARX-00PASB0 51.0AB51> ATA-8 SATA 3.x device
ada1: 300.000MB/s transfersda0 at umass-sim0 bus 0 scbus21 target 0 lun 0

Does that mean, it still registered as 512Byte sector?
 

audix

Dabbler
Joined
Jun 11, 2011
Messages
36
Just checked, my Samsung F4s are also reported as 512 byte sectors in the log... hmm...
 
B

Bohs Hansen

Guest
same for my Seagate SV35.5 2GB drives

Code:
ada1 at ahcich1 bus 0 scbus1 target 0 lun 0
ada1: <ST2000VX002-1AH166 CV01> ATA-8 SATA 3.x device
ada1: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
ada1: Command Queueing enabled
ada1: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)

 

jgreco

Resident Grinch
Joined
May 29, 2011
Messages
18,680
I haven't looked through all the code in ata_da.c, but dp->secsize is set to 512 in adasetgeom, and I didn't see any other immediately apparent places it would be set.

For the sake of reporting, listing the drive as N * 512 is probably correct as long as the drive supports N * 512; it may be misleading to expect that it will report it as M * 4096 even though the drive may support that sector size.

Check out

http://ivoras.sharanet.org/blog/tree/2011-01-01.freebsd-on-4k-sector-drives.html

for some additional 4K hints.
 
Status
Not open for further replies.
Top