Slackware64 Setup does not see gpt partitions created with parted on raid5
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Slackware64 Setup does not see gpt partitions created with parted on raid5
Trying to install Slackware64
I have a 3 terrabytes raid 5 (hardware raid, 4 disks + 1 spare).
2.7 of them will be used as one partition for storage (/home).
cfdisk cannot create such a large partition, so I tried parted.I created all the partitions after doing mklabel gpt. All partitions created successfull. Also checked twice with the print command inside parted.
Running then setup, I get a message that there are no partitions for the setup to proceed. But there are.
What exactly is the error message you receive in cfdisk?
Because 2.7 TB is not a "large" partition for it and there should not be any problems with that.
I have successfully created 8 TB partitions with cfdisk.
And I think the limit is only for filesystem itself (1 000 000 TB for ext4).
What does "fdisk -l" show?
EDIT: Sorry, did not see the "GPT" thing at first. Could anyone explain it also to me, what this GPT acctually is?
Once I tried to install Slackware on an Intel Macintosh and got an error message "cfdisk do not support GPT" or something like that. I used "cfdisk -z" and it worked - partitioned and installed fine.
Last edited by AigarsABCD; 10-07-2009 at 01:23 PM.
I've seen by others that cfdisk does not support partitions over 2 TB.
I first did a cfdisk /dev/sda, created my partitions write table, and then exit.
After running again cfdisk on the raid, I saw that only the first partition (which was 50Gb) was there, and there was another one of about 500 gbytes. all the rest was just unpartitioned space.
deleted all and created again. Same thing though.
Then I decided to use parted. Without doing mklabel gpt on the raid, it could not create partitions over 2TB. But with gpt did it quite well.
Anyway since I had my partitions ready, I don't get it why slackware could not see the partitions.
GPT is the GUID Partition Table. It is a more flexible partitioning scheme than the old well known MBR. You can find more information by searching the web.
As of the cfdisk -z I don't know, I try it.
But does anyone know why slack could not see gpt partitions?
As I did some search, I found that the kernel that is booting on the slackware (huge.s) dvd does not support gpt, and that I have to reconfigure it by setting the
CONFIG_EFI_PARTITION=y
which is commented on the config file on the dvd's huge.s kernel
Is it possible to recreated the kernel image that way?
I don't know because in the past I used to recompile kernels but on an installed slackware. Since I am only booting from the dvd I don't know if is possible.
What I am thinking is:
recompile the huge.s with the above option set, and burning again a dvd with that kernel only changed and booting from it.
Can I recompile that kernel by booting only from dvd?
If you are booting a GPT partition, you will need to switch to Grub. Slack's default is Lilo.
I don't think you can compile a kernel from the bootable DVD. You will need to compile the replacement kernel on a Linux system with gcc installed. Replace the kernel in slackware64-13.0/kernels/huge.s/ and burn a new DVD. I've never done this, but it doesn't look that difficult. However, I hope you have a really good reason for using GPT before doing this.
If that is your only reason for using GPT, you should consider LVM instead.
I have a CentOS box which has a 2.4TB hardware Raid-5 partition. No problems there, and I'm sure it would work just fine in Slackware.
Code:
fdisk -l /dev/VolGroup01/LogVol00
Disk /dev/VolGroup01/LogVol00: 2663.9 GB, 2663919910912 bytes
255 heads, 63 sectors/track, 323869 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk /dev/VolGroup01/LogVol00 doesn't contain a valid partition table
EDIT:
After reading more about GPT, I think Slackware should include GPT/EFI support in the huge and generic kernels. I'm not a big fan of LVM, and considering the rate at which hard drives are growing in size, Slackware needs this feature.
Another thought - Is it possible for you to install Slackware to a MBR-based partition and add a large /home partition later?
This would allow you to install with the regular DVD and easily compile a custom kernel with GPT/EFI enabled. Then you could create, format, and mount your (GPT) home partition.
I don't know if I can combine mbr+gpt in ONE device (/dev/sda).
I don't think it can be done.
Anyway, I decided to to make a smaller partition with 2tb, and the rest of it have it as backup as another partition.
After finished installation, I realized that MBR does not have limit of 2TB for a partition, but it has limit for a total of about 2.2Tb on all the partitions of one device.
So using MBR is not an option at all anymore for me.
I don't know if I can combine mbr+gpt in ONE device (/dev/sda).
I don't think it can be done.
You're probably right.
You could add two smaller disks (raid1 mirror), and use them as the root disk (MBR). Once Slackware is installed, you can rebuild your kernel, partition and format your GPT array, and then mount it. Of course, this probably isn't your ideal solution, as it would cost more money, and suck more power. However, keeping OS and DATA on different arrays isn't a bad thing to do... It may be your only option.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.