Besonderheiten Windows-Installationen/en

Aus EUserv Wiki

(Unterschied zwischen Versionen)
Wechseln zu: Navigation, Suche
(Standard installationns)
(Problems with GPT)
 
(Der Versionsvergleich bezieht 13 dazwischenliegende Versionen mit ein.)
Zeile 1: Zeile 1:
-
[[Kategorie:Betriebssysteme und Software]]
+
[[Kategorie:Operation Systems and Software]]
{{Languages|Besonderheiten Windows-Installationen}}
{{Languages|Besonderheiten Windows-Installationen}}
''''' Characteristics of Windows installations '''''
''''' Characteristics of Windows installations '''''
Zeile 19: Zeile 19:
<pre>With GPT a maximum of 128 primary partitions can be created for each disk. GPT can address HDDs of up to 9.4 Zettabytes.</pre>
<pre>With GPT a maximum of 128 primary partitions can be created for each disk. GPT can address HDDs of up to 9.4 Zettabytes.</pre>
 +
'''In conclusion: Booting from hard disks with a capacity greater than 4 TB makes the use of GPT mandatory.'''
-
While Linux and several Unix distributions are able to boot from GPT-formatted HDDs, Windows has some restrictions regarding this:
+
While Linux and several Unix distributions are able to boot from GPT-formatted HDDs, Windows has some restrictions regarding this. '''These restrictions only apply to the system (boot) disk''':
Zeile 26: Zeile 27:
* Using MBR-formatted hard disks Windows can only use the first 2.2 TB of the disk (this pertains to the system disk only)
* Using MBR-formatted hard disks Windows can only use the first 2.2 TB of the disk (this pertains to the system disk only)
 +
 +
* Using MBR-formatted hard disks only disks up to a maximum capacity of 4 TB may be used as the system disk.
* Free storage above the 2.2 TB limit can't be partitioned and thus cannot be used
* Free storage above the 2.2 TB limit can't be partitioned and thus cannot be used
Zeile 33: Zeile 36:
Since the majority of the deployed server hardware still operates with a conventional BIOS and in order to ensure compatibility with the other installations we provide, installing Windows via (U)EFI is not possible at the moment (Effective 08/2015).
Since the majority of the deployed server hardware still operates with a conventional BIOS and in order to ensure compatibility with the other installations we provide, installing Windows via (U)EFI is not possible at the moment (Effective 08/2015).
-
 
== Partitioning schemes ==
== Partitioning schemes ==
Zeile 48: Zeile 50:
'''b) Standard installations for hard disks > 2 TB'''
'''b) Standard installations for hard disks > 2 TB'''
-
With server hardware featuring hard disks with a capacity of 3 TB and above per disk, the operating system is installed on the first disk. Using a special workaround the hard disk is partitioned so that the whole storage can be used.
+
With server hardware featuring hard disks with a capacity of 3 TB and above per disk, the operating system is installed on the first disk. Using a special workaround the hard disk is partitioned so that the whole storage can be used. This applies to '''all hard disks up to 4 TB'''.
Example for a 3 TB hard disk:
Example for a 3 TB hard disk:
-
* Partition 1 => 40 GB
+
* Partition 1 => 100 GB
-
* Partition 2 => 1360 GB
+
* Partition 2 => 1300 GB
* Partition 3 => 1600 GB
* Partition 3 => 1600 GB
-
'''NOTE:''' Changing the partition layout (i.e. deleting partitions beyond the 2.2 TB limit) causes the restrictions mentioned above to be applied again. That means it is not possible to create further partitions beyond the 2.2 T limit.
+
Example for a 4 TB hard disk:
 +
* Partition 1 => 100 GB
 +
* Partition 2 => 2000 GB
 +
* Partition 3 => 1900 GB
 +
 +
 +
'''NOTE:''' Changing the partition layout (i.e. deleting partitions beyond the 2.2 TB limit) causes the restrictions mentioned above to be applied again. That means it is not possible to create further partitions beyond the 2.2 T limit.
-
'''c) Standardinstallation mit Hardware-RAID-Controller'''
 
-
Bei Serverhardware, in welcher ein Hardware-RAID-Controller verbaut ist, werden 2 "logische" bzw. virtuelle Laufwerke erstellt. Diese werden vom Betriebssystem wie 2 separate Festplatten behandelt.
+
'''c) Standard installations with Hardware RAID Controller'''
-
Die erste Festplatte besitzt eine Kapazität von 100 GB und enthält das Betriebssystem. Die zweite Festplatte wird auf die Kapazität des verfügbaren (Netto)-Speicherplatzes erweitert. Die Größe der 2. Festplatte variiert daher in Abhängigkeit vom gewählten RAID-Level.
+
-
Beispiel:
+
With server hardware featuring a hardware RAID controller, 2 "logical" hard disks are being created. Those are treated like 2 separate disks by the operating system. The first hard disk has a capacity of 100 GB and contains the operating system. The 2nd disk is expanded to the remaining size of the available storage space. The size of the 2nd disk varies depending on the selected RAID level.
-
Am RAID-Controller sind 4 Festplatten zu je 4 TB angeschlossen. Das definierte RAID-Level ist RAID1. Daraus ergibt sich:
+
Example:
-
* 1. Festplatte: 100 GB
+
4 hard disks with 4 TB each are connected to the RAID controller. The selected RAID level is RAID1. The resulting sizes are:
-
* 2. Festplatte: 3.9 TB
+
-
Damit die größere 2. Festplatte voll nutzbar ist, wird diese mit GPT formatiert.
+
* 1. hard disk: 100 GB
 +
* 2. hard disk: 3.9 TB
-
=== Software-RAID-Installationen ===
+
For the 2nd disk to be fully usable, it will be formated with GPT.
-
'''a) Software-RAID-Installation bei Festplatten bis 2 TB'''
+
=== Software RAID installations ===
-
Bei Serverhardware mit verbauten Festplatten mit bis zu 2 TB Kapazität / Festplatte erfolgt die Installation des Betriebssystems auf der ersten Festplatte. Die gesamte Speicherkapazität steht zur Verfügung. Die 2. Festplatte bildet zusammen mit der ersten Festplatte eine Spiegelung (entspricht RAID1). Alle Daten sind redundant vorhanden.
+
'''a) Software RAID installations with hard disks up to 2 TB'''
-
Alle weiteren angeschlossenen Festplatten werden mittels GPT formatiert und können einzeln angesprochen werden.
+
With server hardware featuring hard disks with a capacity of up to 2 TB capacity / per disk, the operating system is installed on the first disk. The whole storage capacity is available. Together with the 1st hard disk the 2nd one constitutes a mirror (this equals RAID1). All data is redundant.  
 +
All other hard disks are formatted with GPT and can be addressed as single disks.
-
'''b) Software-RAID-Installation bei Festplatten > 2 TB'''
+
'''b) Software RAID installation with hard disks > 2 TB'''
-
RAID-Installationen sind bei Festplatten mit einer Kapazität über 2 TB nicht möglich. Hintergrund ist, dass die Spiegelung der Datenträger nicht eingerichtet werden kann, da die erforderliche Umwandlung in einen dynamischen Datenträger aufgrund des Überschreitens der 2.2 TB Grenze nicht vorgenommen werden kann.
+
RAID installations are not possible with hard disks featuring a capacity of more than 2 TB. This is due to the restriction that such hard disks can't be converted to dynamic disks (which is necessary for RAID setups under Windows).

Aktuelle Version vom 15:59, 17. Sep. 2015

Characteristics of Windows installations

Inhaltsverzeichnis

Characteristics of Windows installations

General

We offer the unattended installation of Windows Server for all dedicated servers. In the following article we will show you what to consider with the Windows installations provided by us.


Problems with GPT

GPT ("GUID Partition Table") ist the successor of MBR ("Master Boot Record"). Both terms represent a certain way of how to partition disk drives (number of usable partitions, partition size etc.). While MBR used to be the standard for quite a long time, GPT is now becoming more and more popular with the uprising usage of (U)EFI.

With MBR a maximum of 4 primary partitions can be created for each disk. MBR can address HDDs of up to 4 TB. A single partition may be up to 2.2 TB large.
With GPT a maximum of 128 primary partitions can be created for each disk. GPT can address HDDs of up to 9.4 Zettabytes.

In conclusion: Booting from hard disks with a capacity greater than 4 TB makes the use of GPT mandatory.

While Linux and several Unix distributions are able to boot from GPT-formatted HDDs, Windows has some restrictions regarding this. These restrictions only apply to the system (boot) disk:


  • Using servers without (U)EFI Windows can only boot from MBR-formatted hard disks
  • Using MBR-formatted hard disks Windows can only use the first 2.2 TB of the disk (this pertains to the system disk only)
  • Using MBR-formatted hard disks only disks up to a maximum capacity of 4 TB may be used as the system disk.
  • Free storage above the 2.2 TB limit can't be partitioned and thus cannot be used
  • Windows can only boot from GPT-formatted hard disks when installed with (U)EFI


Since the majority of the deployed server hardware still operates with a conventional BIOS and in order to ensure compatibility with the other installations we provide, installing Windows via (U)EFI is not possible at the moment (Effective 08/2015).

Partitioning schemes

Standard installations

a) Standard installations for hard disks up to 2 TB

With server hardware featuring hard disks with a capacity of up to 2 TB per disk, the operating system is installed on the first disk. The whole storage capacity is available. All other disks are formatted and provided respectively.


b) Standard installations for hard disks > 2 TB

With server hardware featuring hard disks with a capacity of 3 TB and above per disk, the operating system is installed on the first disk. Using a special workaround the hard disk is partitioned so that the whole storage can be used. This applies to all hard disks up to 4 TB.

Example for a 3 TB hard disk:

  • Partition 1 => 100 GB
  • Partition 2 => 1300 GB
  • Partition 3 => 1600 GB


Example for a 4 TB hard disk:

  • Partition 1 => 100 GB
  • Partition 2 => 2000 GB
  • Partition 3 => 1900 GB


NOTE: Changing the partition layout (i.e. deleting partitions beyond the 2.2 TB limit) causes the restrictions mentioned above to be applied again. That means it is not possible to create further partitions beyond the 2.2 T limit.


c) Standard installations with Hardware RAID Controller

With server hardware featuring a hardware RAID controller, 2 "logical" hard disks are being created. Those are treated like 2 separate disks by the operating system. The first hard disk has a capacity of 100 GB and contains the operating system. The 2nd disk is expanded to the remaining size of the available storage space. The size of the 2nd disk varies depending on the selected RAID level.

Example:

4 hard disks with 4 TB each are connected to the RAID controller. The selected RAID level is RAID1. The resulting sizes are:

  • 1. hard disk: 100 GB
  • 2. hard disk: 3.9 TB

For the 2nd disk to be fully usable, it will be formated with GPT.

Software RAID installations

a) Software RAID installations with hard disks up to 2 TB

With server hardware featuring hard disks with a capacity of up to 2 TB capacity / per disk, the operating system is installed on the first disk. The whole storage capacity is available. Together with the 1st hard disk the 2nd one constitutes a mirror (this equals RAID1). All data is redundant.

All other hard disks are formatted with GPT and can be addressed as single disks.

b) Software RAID installation with hard disks > 2 TB


RAID installations are not possible with hard disks featuring a capacity of more than 2 TB. This is due to the restriction that such hard disks can't be converted to dynamic disks (which is necessary for RAID setups under Windows).