Descargar Controladores Sata Para Windows 7 32 Bits
Latrisha Adan
In order for an operating system to fully support storage devices that have capacities that exceed 2 terabytes (2 TB, or 2 trillion bytes), the device must be initialized by using the GUID Partition Table (GPT) partitioning scheme. This scheme supports addressing of the full range of storage capacity. If the user intends to start the computer from one of these large disks, the system's base firmware interface must use the Unified Extensible Firmware Interface (UEFI) and not BIOS.
The management of modern storage devices is addressed by using a scheme called Logical Block Addressing (LBA). It's the arrangement of the logical sectors that constitute the media. LBA0 represents the first logical sector of the device, and the last LBA designation represents the last logical sector of the device, one label per sector. To determine the capacity of the storage device, you multiply the number of logical sectors within the device by the size of each logical sector. The current size standard is 512 bytes. For example, to achieve a device that has a capacity of 2 TB, you must have 3,906,250,000 512-byte sectors. However, a computer system requires 32 bits (1 s and 0 s) of information to represent this large number. Therefore, any storage capacity that is greater than what can be represented by using 32 bits would require an additional bit. That is, 33 bits.
The problem in this computation is that the partitioning scheme that is used by most modern Windows-based computers is MBR (master boot record). This scheme sets a limit of 32 for the number of bits that are available to represent the number of logical sectors.
To make more bits available for addressing, the storage device must be initialized by using GPT. This partitioning scheme lets up to 64 bits of information be used within logical sectors. It translates to a theoretical limitation of 9.4 ZB (9.4 zettabytes, or 9.4 billion terabytes). However, the issue that affects GPT is that most currently available systems are based on the aging BIOS platform. BIOS supports only MBR-initialized disks to start the computer. To restart from a device that is initialized by using GPT, your system must be UEFI-capable. By default, many current systems can support UEFI. Microsoft expects that most future systems will have this support. Customers should consult with their system vendor to determine the ability of their systems to support UEFI and disks that have storage capacities that are greater than 2 TB.
The latest storage drivers from your storage controller manufacturer must be installed. For example, if your system uses an Intel storage controller that is set to "RAID" mode, make sure that you have the latest applicable drivers from the Intel support site.
The latest storage drivers from your storage controller manufacturer must be installed. For example, if your system uses an Intel storage controller set to RAID mode, make sure that you have the latest applicable drivers from the Intel support site.
Windows does not support starting GPT-initialized volumes by using UEFI systems on 32-bit versions of Windows. Also, legacy BIOS systems do not support starting GPT-partitioned volumes. Consult your system vendor to determine whether the system supports both UEFI and the startup of devices that have storage capacities of greater than 2 TB.
The following tables list Microsoft support for the various concepts that are discussed in this article. This information provides an overall support statement about disks that have a storage capacity of greater than 2 TB.
Capacity beyond 2 TB cannot be addressed by Windows if the disk is initialized by using the MBR partitioning scheme. For example, for a 3-TB single disk that is initialized by using MBR, Windows can create partitions up to the first 2 TB. However, the remaining capacity cannot be addressed and, therefore, cannot be used.
The following steps show how to initialize a fresh disk by using the GPT partitioning scheme to help ensure that Windows can address the maximum available storage capacity. Make sure that you back up any important data before you try these steps.
Click Start, type diskmgmt.msc in the Start search box, right-click diskmgmt.msc, and then click Run as Administrator. If it's necessary, enter the credentials for a user account that has Administrator privileges.
After the disk is initialized, you must create a partition, and then format that partition by using a file system. It's to be able to store data in that partition, and assign a name and a drive letter to that partition. To do it, right-click the unallocated space on the right side of the status row for that disk, and then click New Simple Volume. Follow the steps in the partition wizard to complete this process.
If you have previously initialized the disk by using the MBR partitioning scheme, follow these steps to initialize the disk by using the GPT scheme. Make sure that you back up any important data before you try these steps.
In the Disk Management window, examine the disk status rows at the bottom. In the following example, the user has a 3-TB disk that was previously initialized by using the MBR partitioning scheme. That device is labeled here as Disk 1.
Disk 1 contains two separate unallocated sections. This separation indicates that the first 2 TB of the disk space can be used. However, the remaining space is non-addressable because of the 32-bit addressing space limitation of the MBR partitioning scheme. To enable the system to fully address the total capacity of the storage device, you must convert the disk to use the GPT partitioning scheme.
Now that the disk is initialized to access the full storage capacity, you must create a partition, and then format that partition by using a file system. It's to be able to store data in that partition, and assign a name and a drive letter to that partition. To do it, right-click the unallocated space on the right side of the status row for that disk, and then click New Simple Volume. Follow the steps in the partition wizard to complete this process.
Because the transition to a single-disk capacity of greater than 2 TB has occurred fairly recently, Microsoft has investigated how Windows supports these large disks. The results reveal several issues that apply to all versions of Windows earlier than and including Windows 7 with Service Pack 1 and Windows Server 2008 R2 with Service Pack 1.
The storage device isn't detected correctly. In this case, it isn't displayed in either the Device Manager or Disk Management windows. Many storage controller manufacturers offer updated drivers that provide support for storage capacities of more than 2 TB. Contact your storage controller manufacturer or OEM to determine what downloadable support is available for single-disk capacities that are greater than 2 TB.
When a disk encounters errors that are related to unreadable or unwritable sectors, it reports those errors and the relevant SCSI sense data to the operating system. SCSI sense data may contain information about LBA for sectors that were found to be unreadable or unwritable.
For LBA address space that is greater than 2 TB, the disk requires SCSI sense data in Descriptor format. This format isn't supported by Windows 7 or Windows Server 2008 R2, which retrieves SCSI sense data in Fixed format. Therefore, the retrieved SCSI sense data either does not contain information about bad sectors or it contains incorrect information about bad sectors. Administrators should note this limitation when they look for bad sector LBA information that's recorded in the Windows event log.
d3342ee215