Skip to main content

partitioning - Trying to understand linux support for 4TB hard disk drive on legacy BIOS


I want to add a 4TB hard disk drive for data storage only. My current configuration:



Questions:



  1. Because the size is greater than 2TB am I really forced to use GPT partition?

  2. If yes, GPT partition required UEFI or legacy BIOS is supported?

  3. if legacy bios is supported, Arch Linux will see 4TB or 2TB only?


This new hard disk drive is for data only and I will not install OS on it or boot from it.



Answer



I'm the author of the GPT fdisk partitioning software, so I know this subject pretty well. Previous answers have promoted some misconceptions that I'd like to address....



If you want a partition size greater than 2TB, you must use GPT instead of MBR.



Probably. The catch is that that MBR maxes out at 2^32 sectors. This translates to 2 TiB (not 2 TB; see here for an explanation of the difference) if the logical sector size is 512 bytes. Many external disks and a few internal disks now use 4 KiB (4096-byte) logical sectors, though, which raises the MBR limit to 16 TiB.


Note that this is referring to the logical sector size. Most modern hard disks use 4096-byte physical sectors, but this detail is unimportant for determining the limits of the partition table.



MBR only supports 2TB partition sizes. If you wanted multiple partitions (less than 2TB each), you should be able to access all of your disk as different partitions.



Up to a 4 TiB limit (assuming 512-byte sectors) and if you're willing to play with fire, yes. MBR stores partition data as a start point and a size, so you can stretch the MBR limits out to 4 TiB, but not further. The trouble is that this is unreliable. I ran some tests on this several years ago (see here), and the upshot was that the OSes that could handle this stretching of the MBR limits were pretty much the same ones that could handle GPT, so there's not much benefit to it. More importantly, there's a chance that some random disk utility would flake out because it uses a 32-bit value for a sector pointer, even if the OS itself can manage it. Thus, I personally would not trust a disk with this configuration -- it might work fine for a while, but if you happen to run a 32-bit-unclean disk utility, it could cause serious data corruption.



BIOS doesn't know about GPT so it can't boot off of disks formatted GPT.



This statement is incorrect, or at best, it applies to only some OSes and BIOSes. The BIOS boot process involves the BIOS reading the first sector of the disk (aka the MBR) and executing the code there. Importantly, a traditional BIOS knows nothing about the partition table. It's the boot loader code in the MBR that (often) begins interpreting the partition table. Thus, restrictions preventing BIOS-mode booting from GPT are embedded in boot loaders and OSes, not in the BIOS. Most GPT-aware OSes (for instance, Linux, FreeBSD, and even OS X using a Hackintosh boot loader) can boot fine from GPT disks on BIOS-only computers. The major exception to this rule is Windows, which (AFAIK) cannot be booted from GPT disks in BIOS mode.


There is one major caveat to this: Some BIOSes are too smart. Some are in fact EFIs, which do understand partition tables. Such firmware may throw up obstacles that complicate or prevent booting in BIOS mode from GPT disks. I've studied this issue pretty carefully and have comments on it here. Such problems can usually be overcome, although the solutions are often non-obvious.


Despite these caveats, the vast majority of PCs with BIOS-mode boot capability (either "real" BIOSes or EFIs with CSMs) can boot in BIOS mode from GPT disks, provided the OS has a suitable boot loader. As BufferUnderRun says the OS in question is Arch Linux, there should be no problem; GRUB 2, SYSLINUX, and even old LILO can do the job. I've done it myself on several computers.


All that said, since the new disk is a non-boot disk, you needn't really be concerned with these issues. You can boot Linux in BIOS mode from an MBR-partitioned SSD and use the GPT-partitioned 4 TiB hard disk for data storage without problems. If your needs change in the future, you might need to re-evaluate the configuration, but I wouldn't worry about it now.


Comments

Popular Posts

How do I transmit a single hexadecimal value serial data in PuTTY using an Alt code?

I am trying to sent a specific hexadecimal value across a serial COM port using PuTTY. Specifically, I want to send the hex codes 9C, B6, FC, and 8B. I have looked up the Alt codes for these and they are 156, 182, 252, and 139 respectively. However, whenever I input the Alt codes, a preceding hex value of C2 is sent before 9C, B6, and 8B so the values that are sent are C2 9C, C2 B6, and C2 8B. The value for FC is changed to C3 FC. Why are these values being placed before the hex value and why is FC being changed altogether? To me, it seems like there is a problem internally converting the Alt code to hex. Is there a way to directly input hex values without using Alt codes in PuTTY? Answer What you're seeing is just ordinary text character set conversion. As far as PuTTY is concerned, you are typing (and reading) text , not raw binary data, therefore it has to convert the text to bytes in whatever configured character set before sending it over the wire. In other words, when y...

linux - Extract/save a mail attachment using bash

Using normal bash tools (ie, built-ins or commonly-available command-line tools), is it possible, and how to extract/save attachments on emails? For example, say I have a nightly report which arrives via email but is a zip archive of several log files. I want to save all those zips into a backup directory. How would I accomplish that? Answer If you're aiming for portability, beware that there are several different versions of mail(1) and mailx(1) . There's a POSIX mailx command, but with very few requirements. And none of the implementations I have seem to parse attachments anyway. You might have the mpack package . Its munpack command saves all parts of a MIME message into separate files, then all you have to do is save the interesting parts and clean up the rest. There's also metamail . An equivalent of munpack is metamail -wy .

ubuntu - Why does my USB hdd returns SG_IO: bad/missing sense data?

I am able to boot and run commands from external USB hdd; the message in question appears for about 45 seconds then booting continues. GRUB2 is installed on internal HDD. When choosing to boot directly to /dev/sdb the message doesn't appear, however boot time is about the same as booting to internal HDD. /dev/sdb: Timing cached reads: 1018 MB in 2.00 seconds = 508.97 MB/sec Timing buffered disk reads: 80 MB in 3.03 seconds = 26.37 MB/sec pfeiffep@de:~$ sudo hdparm -i /dev/sdb /dev/sdb: SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 10 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 HDIO_GET_IDENTITY failed: Invalid argument Gparted correctly identifies the drive as SAMSUNG MP0402H. Any ideas how to remedy the HDIO & SG_IO messages?

Desktop reboots itself on sleep or hibernate

I have been using an ASUS M2NPV-VM motherboard for main home desktop workstation, operating Windows Vista x64. This computer has right from day one not been able to enter hibernate or standby; after Windows performs its final actions and brings the machine down, it would automatically revive itself for a reboot. Updating to the second latest BIOS (1201)has not helped (the latest BIOS revision would induce video refresh problems rendering it unusable). I have been reading related discussions on incidents similar to mine to no avail of a true workable solution. They appear to be more speculative guesses rather than actual knowledge on the inner workings of motherboard hardware. Does anybody have any electronic engineering experience on PC energy-saving standards to provide a more informed opinion how to go about getting this to work? More stories: this motherboard could not even reboot properly the first thing i used it. It was due to refresh rate of the onboard GPU, which had no influe...