NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Fallon
Oct 15, 2010Aspirant
Spinpoint F4 HD204UI 2TB 5400 RPM working good so far
There was a recent deal at NewEgg on the SAMSUNG Spinpoint F4 HD204UI 2TB 5400 RPM 32MB drives, so I decided to risk it as opposed to the other WD & Seagate 2tb drives. I installed them, upgraded the ...
Wracky
Nov 03, 2010Aspirant
Hey everyone,
I just installed 2 of these drives in my ReadyNAS duo myself.
I updated the firmware to 4.1.7-T60 and started a Factory Default from FrontView, after which I used RAIDar to set the device to Raid 1 mode.
Everything seems to work fine, it's syncing now at 90 to 100MB/sec ... however Hingy here said the partition logs for him now show "disks are aligned for the 4K sectors"
I've looked in partition.log and can't find anything that would suggest 4K sectors :-/
The Log looks like this now:
Disk /dev/md0 doesn't contain a valid partition table
Disk /dev/md1 doesn't contain a valid partition table
Disk /dev/md2 doesn't contain a valid partition table
Disk /dev/hdc: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/hdc1 32 4096031 2048000 fd Linux raid autodetect
Partition 1 does not end on cylinder boundary.
/dev/hdc2 4096032 5144607 524288 fd Linux raid autodetect
Partition 2 does not end on cylinder boundary.
/dev/hdc3 5144608 3907012815 1950934104 fd Linux raid autodetect
Disk /dev/hde: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/hde1 32 4096031 2048000 fd Linux raid autodetect
Partition 1 does not end on cylinder boundary.
/dev/hde2 4096032 5144607 524288 fd Linux raid autodetect
Partition 2 does not end on cylinder boundary.
/dev/hde3 5144608 3907012815 1950934104 fd Linux raid autodetect
Note: sector size is 1024 (not 512)
Disk /dev/md0: 2097 MB, 2097086464 bytes
2 heads, 4 sectors/track, 255992 cylinders, total 2047936 sectors
Units = sectors of 1 * 1024 = 1024 bytes
Disk identifier: 0x00000000
Note: sector size is 1024 (not 512)
Disk /dev/md1: 536 MB, 536805376 bytes
2 heads, 4 sectors/track, 65528 cylinders, total 524224 sectors
Units = sectors of 1 * 1024 = 1024 bytes
Disk identifier: 0x00000000
Note: sector size is 1024 (not 512)
Disk /dev/md2: 1997.7 GB, 1997756432384 bytes
2 heads, 4 sectors/track, 243866752 cylinders, total 1950934016 sectors
Units = sectors of 1 * 1024 = 1024 bytes
Disk identifier: 0x00000000
Raidiator_version.log says. RAIDiator!!version=4.1.7-T60,time=1287008617
Is this OK ?
Thanks!
I just installed 2 of these drives in my ReadyNAS duo myself.
I updated the firmware to 4.1.7-T60 and started a Factory Default from FrontView, after which I used RAIDar to set the device to Raid 1 mode.
Everything seems to work fine, it's syncing now at 90 to 100MB/sec ... however Hingy here said the partition logs for him now show "disks are aligned for the 4K sectors"
I've looked in partition.log and can't find anything that would suggest 4K sectors :-/
The Log looks like this now:
Disk /dev/md0 doesn't contain a valid partition table
Disk /dev/md1 doesn't contain a valid partition table
Disk /dev/md2 doesn't contain a valid partition table
Disk /dev/hdc: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/hdc1 32 4096031 2048000 fd Linux raid autodetect
Partition 1 does not end on cylinder boundary.
/dev/hdc2 4096032 5144607 524288 fd Linux raid autodetect
Partition 2 does not end on cylinder boundary.
/dev/hdc3 5144608 3907012815 1950934104 fd Linux raid autodetect
Disk /dev/hde: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/hde1 32 4096031 2048000 fd Linux raid autodetect
Partition 1 does not end on cylinder boundary.
/dev/hde2 4096032 5144607 524288 fd Linux raid autodetect
Partition 2 does not end on cylinder boundary.
/dev/hde3 5144608 3907012815 1950934104 fd Linux raid autodetect
Note: sector size is 1024 (not 512)
Disk /dev/md0: 2097 MB, 2097086464 bytes
2 heads, 4 sectors/track, 255992 cylinders, total 2047936 sectors
Units = sectors of 1 * 1024 = 1024 bytes
Disk identifier: 0x00000000
Note: sector size is 1024 (not 512)
Disk /dev/md1: 536 MB, 536805376 bytes
2 heads, 4 sectors/track, 65528 cylinders, total 524224 sectors
Units = sectors of 1 * 1024 = 1024 bytes
Disk identifier: 0x00000000
Note: sector size is 1024 (not 512)
Disk /dev/md2: 1997.7 GB, 1997756432384 bytes
2 heads, 4 sectors/track, 243866752 cylinders, total 1950934016 sectors
Units = sectors of 1 * 1024 = 1024 bytes
Disk identifier: 0x00000000
Raidiator_version.log says. RAIDiator!!version=4.1.7-T60,time=1287008617
Is this OK ?
Thanks!
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!