Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

I've been searching as best I can for this precise problem, but the only place I found it exactly was here, and I don't think that the OP ever got an adequate answer. Most of the issues I've seen with regards to 3TB hard drives stem from outdated hardware, dual-booting issues, etc.

My server is brand-new, using an ASRock H67M-ITX with onboard Intel RAID. I have two Seagate 3TB set up in a RAID 1 array. Everything I can see in the raid controller indicates that the motherboard is having no problems with this arrangement: both disks show up as 3TB devices, and the RAID array does as well. The only point at which anything goes amiss is upon loading 12.04-desktop-amd64 from a flash drive, and attempting to partition. At this stage, I create a new partition table on the disk, and the resulting size is 801567 MB.

I was under the impression that the motherboard had no problems with RAID arrays this large, and also that the latest long-term stable release of 64-bit Ubuntu shipped with in-kernel GPT support and would have no difficulties as well. Any ideas on what I'm doing wrong?

share|improve this question
    
I have a quick question. How are you looking at the RAID? For just about any type of RAID on linux, you should be using mdadm. If you see something showing up as a /dev/sda or something along those lines then it probably isn't your raid. Run mdadm -ay then cat /proc/mdstat to see what the name of your RAID device should be. I think you can take it from there. Good Luck! –  darkdragn Apr 28 '12 at 23:52

1 Answer 1

up vote 3 down vote accepted

I have no simple and sure-fire answer, but for a first diagnostic step, I recommend you check your boot mode and disk information using lower-level tools than the installer provides:

  1. Boot into the "try before installing" mode.
  2. Open a terminal window.
  3. Type ls /sys/firmware/efi. If you see any files (normally one file and one directory), you've booted in EFI mode. If you get a "no such file or directory" error, you've probably booted in BIOS mode. This may have implications for the partition table type used and perhaps for the way the motherboard's RAID features get detected by Linux. (This last is very speculative on my part, though.)
  4. Type sudo apt-get install gdisk to install the gdisk package. (If this doesn't work, you may need to enable networking and futz around with package options.)
  5. Type gdisk -l /dev/sda (change the device identifier, if necessary, to see your disk or RAID array). Pay attention to the disk's reported size (in sectors and GiB or TiB) and to the table type ("MBR: protective and GPT: present" for GPT; or "MBR: MBR only and GPT: not present" for MBR). If your disk is set up with MBR, that could be throwing things off. I'd expect it to let you use up to 2 TiB in this case, but there could be a bug in libparted that's cutting you off too early. If the disk uses MBR, switching to GPT with the help of gdisk, GParted, or some other tool is in order.

One more comment: If this is to be a Linux-only installation, the motherboard-based RAID is probably not the best way to go. Linux supports it, but my impression is that it's flakier than is Linux's own software-based RAID. (Both are actually software-based; it's just that the motherboard variety includes "hooks" in the firmware, can be used across OSes, and is tied to a particular type of disk controller, whereas the Linux variety has no hooks, is Linux-only, and can be used on any disk controller.) Thus, if this is a Linux-only system, I recommend you disable the RAID option in the firmware and then use Linux's software RAID. Not all Ubuntu installers support software RAID, though. The desktop installers definitely don't, but I think the server and alternate installers both do.

share|improve this answer
    
Sorry for the delay - real life kicked in and hobbies had to fall by the wayside. I'll try this out this weekend and let you know what I find. –  Brian Bauman May 5 '12 at 7:05
    
I run into an error telling me to run apt-get update. When I attempt to do so, it tells me to...run apt-get update. I'm going to try the Linux software RAID, I'll post what I find. –  Brian Bauman May 6 '12 at 19:51
    
Software RAID has no problems detecting the disks properly. It seems to be an incompatibility with the onboard FakeRAID and Ubuntu. Now I just need to figure out how to boot from a RAID 1, but that's a different question. –  Brian Bauman May 7 '12 at 0:32
1  
It's unclear if you need the motherboard-based software raid ("Fake RAID") or not. I'll re-emphasize that this method is less reliable than Linux's own software RAID. If you don't need cross-OS compatibility, you should disable it in the firmware and uninstall the dmraid package. –  Rod Smith May 8 '12 at 16:38
    
If apt-get is flaking out, you can download GPT fdisk manually from OBS, using links here: rodsbooks.com/gdisk/download.html#obs . –  Rod Smith May 8 '12 at 16:39

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.