Graphics
Intel® graphics drivers and software, compatibility, troubleshooting, performance, and optimization
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
22744 Discussions

Setting sector size on ICH10DO

idata
Employee
‎01-23-2011 02:27 PM
1,752 Views

I recently purchased 4 2TB Seagate drives for use in a 6TB RAID-5 array. I am running Windows XP 32-bit, which can only recognise drives up to 2TB in size using the default sector size of 512 bytes, so I intended to create the array and specify its logical sector size as 4KB which would allow expansion to 16TB in theory.

Unfortunately I can't find an option to specify this in the Intel RAID BIOS or the RST management console. After I create the array I can expand the "Advanced" option and see that the settings "Physical sector size" and "Logical sector size" are both set to 512 bytes, but I need a way to set "Logical sector size" to 4KB during array creation. Is there a way to do this?

Link Copied

1 Reply
idata
Employee
‎01-23-2011 05:39 PM
921 Views

XP 32 bit dose not support GPT it only supports MBR.

http://www.microsoft.com/whdc/device/storage/gpt_faq.mspx http://www.microsoft.com/whdc/device/storage/gpt_faq.mspx

The "Physical sector size" and "Logical sector size" have nothing to do with limiting the array size to 2TB.

Note: Intel only supports an a array size past 2TB if it is a data only array which is to say you can't have a OS on it.

0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.