I asked this question over in the DNS-323 forum because there was a topic over there specifically about 4k sector drives. So if you saw this questions over there, it's a duplicate...

Anyway, I have just installed 2 Samsung HD204UI (2TB drives with 4k sectors) in my DNS-321 with RAID1. I went ahead and used the web formatting to install the drives, and it didn't seem to have a problem. However, I knew there were some issues with 4k sectors, so I did a little more research, and came across the post in the DNS-323 forum, so I thought I'd ask. So far, I'm getting 133Mbps writes and 75Mbps reads, and I'm wondering if this will degrade due to the 4k sectors. It's a new install, so I'm not worried about the data at this point.
This is what my drives look like as they are currently installed. Can anyone interpret this and see if I should try to do a special, manual format to get the drives to work properly? Or does this look good? Does the start sector need to be 64 instead of 63?
Thanks for any pointers!
root@dcNAS:/etc# fdisk -ul /dev/sda
Disk /dev/sda: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/sda1 63 1060289 530113+ 82 Linux swap
/dev/sda2 2088450 3904903484 1951407517+ 83 Linux
/dev/sda4 1060290 2088449 514080 83 Linux
Partition table entries are not in disk order
root@dcNAS:/etc# fdisk -ul /dev/sdb
Disk /dev/sdb: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 63 1060289 530113+ 82 Linux swap
/dev/sdb2 2088450 3904903484 1951407517+ 83 Linux
/dev/sdb4 1060290 2088449 514080 83 Linux
Partition table entries are not in disk order
root@dcNAS:/etc# tune2fs -l /dev/sda2
tune2fs 1.41.0 (10-Jul-2008)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: 0da8ca80-4a21-4c6c-81f9-593b080774d6
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: ext_attr resize_inode dir_index filetype sparse_super large_file
Filesystem flags: unsigned_directory_hash
Default mount options: (none)
Filesystem state: not clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 121970688
Block count: 487851856
Reserved block count: 0
Free blocks: 458479878
Free inodes: 121925477
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 907
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
Filesystem created: Wed Nov 3 14:02:59 2010
Last mount time: Wed Nov 3 22:53:54 2010
Last write time: Thu Nov 4 16:45:24 2010
Mount count: 6
Maximum mount count: 33
Last checked: Wed Nov 3 14:02:59 2010
Check interval: 15552000 (6 months)
Next check after: Mon May 2 14:02:59 2011
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Default directory hash: half_md4
Directory Hash Seed: 46a82cf3-6f9a-469c-b801-2655fa861d5e