-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I installed centos4 on a raid system with 7 400GB Hitachi SATA disks in RAID 5 on the 3Ware card. I set up a 2.2TB EXT3 Partition /opt.
After the install I rebooted and the system went straight into maintenance mode....! The system reported a problem with /opt, but I was able to mount it manually and init 4 with no problems. However a reboot dropped me straight back into maintanence mode ???
Back in maintenance mode again I tried to used parted to create a partition, but it says it can't manage a partition greater than 1.72TB - I thought parted could do > 2TB fs's?
parted output below:
[root@localhost ~]# parted GNU Parted 1.6.19 Copyright (C) 1998 - 2004 Free Software Foundation, Inc. This program is free software, covered by the GNU General Public License.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
Using /dev/sda (parted) print Disk geometry for /dev/sda: 0.000-2288754.000 megabytes Disk label type: msdos Minor Start End Type Filesystem Flags 1 0.031 101.975 primary ext3 boot 2 101.975 5098.754 primary linux-swap 3 5098.755 7091.191 primary ext3 4 7091.191 191600.624 extended 5 7091.222 9083.627 logical ext3 6 9083.659 11076.064 logical ext3 (parted) mkpart logical ext3 11076.065 2288754 Warning: You requested to create a partition at 11076.065-2288754.000Mb. The closest Parted can manage is 11076.095-191595.520Mb. OK/Cancel?
Any one have experience/ideas?
Regards, John
****************************************************************************** The information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution, or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Please note that emails to, from and within RTÉ may be subject to the Freedom of Information Act 1997 and may be liable to disclosure. ******************************************************************************
On Mon, 25 Apr 2005 at 4:12pm, John Moylan wrote
I installed centos4 on a raid system with 7 400GB Hitachi SATA disks in RAID 5 on the 3Ware card. I set up a 2.2TB EXT3 Partition /opt.
*snip*
Using /dev/sda (parted) print Disk geometry for /dev/sda: 0.000-2288754.000 megabytes Disk label type: msdos Minor Start End Type Filesystem Flags 1 0.031 101.975 primary ext3 boot 2 101.975 5098.754 primary linux-swap 3 5098.755 7091.191 primary ext3 4 7091.191 191600.624 extended 5 7091.222 9083.627 logical ext3 6 9083.659 11076.064 logical ext3 (parted) mkpart logical ext3 11076.065 2288754 Warning: You requested to create a partition at 11076.065-2288754.000Mb. The closest Parted can manage is 11076.095-191595.520Mb. OK/Cancel?
Any one have experience/ideas?
Yes. Oh yes. And I was so annoyed by the experience that I submitted a documentation erratum to RH about it (see https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=155728). I'll detail it a bit here for the archives.
The short version is You Can't Do That. Disk devices >2TB require gpt disk labels. msdos disk labels (as you have above) can't handle devices of that size. And neither grub nor lilo know how to boot from a gpt labelled device. So, ATM, you cannot boot from a device >2TB.
Your only option at this point is to add in a new boot device and install to that. Once you've done that, go ahead and use parted on your big array, being sure to 'mklabel gpt' before you make any partitions on it.
On Mon, April 25, 2005 10:22 am, Joshua Baker-LePain said:
On Mon, 25 Apr 2005 at 4:12pm, John Moylan wrote
I installed centos4 on a raid system with 7 400GB Hitachi SATA disks in RAID 5 on the 3Ware card. I set up a 2.2TB EXT3 Partition /opt.
*snip*
Using /dev/sda (parted) print Disk geometry for /dev/sda: 0.000-2288754.000 megabytes Disk label type: msdos Minor Start End Type Filesystem Flags 1 0.031 101.975 primary ext3 boot 2 101.975 5098.754 primary linux-swap 3 5098.755 7091.191 primary ext3 4 7091.191 191600.624 extended 5 7091.222 9083.627 logical ext3 6 9083.659 11076.064 logical ext3 (parted) mkpart logical ext3 11076.065 2288754 Warning: You requested to create a partition at 11076.065-2288754.000Mb. The closest Parted can manage is 11076.095-191595.520Mb. OK/Cancel?
Any one have experience/ideas?
Yes. Oh yes. And I was so annoyed by the experience that I submitted a documentation erratum to RH about it (see https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=155728). I'll detail it a bit here for the archives.
The short version is You Can't Do That. Disk devices >2TB require gpt disk labels. msdos disk labels (as you have above) can't handle devices of that size. And neither grub nor lilo know how to boot from a gpt labelled device. So, ATM, you cannot boot from a device >2TB.
Your only option at this point is to add in a new boot device and install to that. Once you've done that, go ahead and use parted on your big array, being sure to 'mklabel gpt' before you make any partitions on it.
Thanks for submitting the bug to RedHat concerning this issue. This is an upstream issue, as is anything like this. CentOS-4 is a faithful rebuild of the RHEL SRPMS and any limitations in RHEL4 will be carried forward.
If / when these issues are released in errata from RHEL, they will be corrected in CentOS-4.
-
John Moylan -
Johnny Hughes -
Joshua Baker-LePain