Hi all,
I'm trying to get F18 installed on a server (x86_64). The setup is quiet easy and typical for a server:
Partitions: sda1: primary partition, 512M sda2: primary partition, rest of the disk sdb1: primary partition, 512M sdb2: primary partition, rest of the disk
SOFT RAID: /dev/md0: raid1, consists of sda1 and sdb1 /dev/md1: raid1, consists of sda2 and sdb2
md0: formatted with ext2, mounted as /boot md1: LVM physical device.
LVM: LVM VG: "vg" using md1 LVM LV: "root", formatted as ext4, mounted as / LVM LV: "var", formatted as ext4, mounted as /var (this is for libvirt disk images) LVM LV: "swap", swap partition
Grub installed in both MBRs of sda and sdb, to allow booting from both disks.
Unfortunately the installer does not allow to create this kind of partition layout. With F17 this was possible.
What I've already tried:
1.) creating the layout manually using fdisk, mdadm and lvm tools. Selecting only the mountpoint in installer: This does not work. The installer does not correctly recognize the layout. I was not able to select the mountpoints.
2.) Installing F17 and upgrade using fedup. This fails. Seems like fedup is not able to handle this layout.
3.) Kickstart: It looks like this is most likely the way to get it working. But I was not able to write a working kickstart script. The online doc is not enough for that. I found same kickstart examples using Google, but these didn't work either.
Maybe somebody can assists me with that or has a better idea how to install that system.
regards, Gerhard.
On 06.06.2013 10:30, Gerhard Gappmeier wrote:
Unfortunately the installer does not allow to create this kind of partition layout. With F17 this was possible.
Yes, it was possible in F17. Now it isn't :) It's kind of improvement in installer.
2.) Installing F17 and upgrade using fedup. This fails. Seems like fedup is not able to handle this layout.
fedup is not touching anything in partition layout. (someone on devel@ group stated this recently) fedup downloads packages, new kernel and "installation" initrd. Then it uses yum/rpm do upgrade OS. So it should be possible to upgrade your machine.
3.) Kickstart: It looks like this is most likely the way to get it working. But I was not able to write a working kickstart script. The online doc is not enough for that. I found same kickstart examples using Google, but these didn't work either.
This is the only chance to do what you want. I also wait with upgrade/reinstall on some of my boxes because I can't play with kickstart to learn how it works. I have no spare box to destroy for one day. You can see content of kickstart-ks.cfg in /root directory of your Fedora 17 install and use it for new installation.
Maybe somebody can assists me with that or has a better idea how to install that system.
I'm waiting for this feature to be available back in Fedora. For now I don't have any good news for you. This kind of installation might be only possible using kickstart. Please try Fedora 19, maybe it's available again.
Mateusz Marzantowicz
On 06/06/2013 05:34 PM, Mateusz Marzantowicz wrote:
On 06.06.2013 10:30, Gerhard Gappmeier wrote:
Unfortunately the installer does not allow to create this kind of partition layout. With F17 this was possible.
Yes, it was possible in F17. Now it isn't :) It's kind of improvement in installer.
2.) Installing F17 and upgrade using fedup. This fails. Seems like fedup is not able to handle this layout.
fedup is not touching anything in partition layout. (someone on devel@ group stated this recently) fedup downloads packages, new kernel and "installation" initrd. Then it uses yum/rpm do upgrade OS. So it should be possible to upgrade your machine.
3.) Kickstart: It looks like this is most likely the way to get it working. But I was not able to write a working kickstart script. The online doc is not enough for that. I found same kickstart examples using Google, but these didn't work either.
This is the only chance to do what you want. I also wait with upgrade/reinstall on some of my boxes because I can't play with kickstart to learn how it works. I have no spare box to destroy for one day. You can see content of kickstart-ks.cfg in /root directory of your Fedora 17 install and use it for new installation.
It should be called as 'anaconda-ks.cfg' in your '/root/' directory.
Maybe somebody can assists me with that or has a better idea how to install that system.
I'm waiting for this feature to be available back in Fedora. For now I don't have any good news for you. This kind of installation might be only possible using kickstart. Please try Fedora 19, maybe it's available again.
Mateusz Marzantowicz
On 06.06.2013 14:35, Rejy M Cyriac wrote:
On 06/06/2013 05:34 PM, Mateusz Marzantowicz wrote:
On 06.06.2013 10:30, Gerhard Gappmeier wrote:
Unfortunately the installer does not allow to create this kind of partition layout. With F17 this was possible.
Yes, it was possible in F17. Now it isn't :) It's kind of improvement in installer.
2.) Installing F17 and upgrade using fedup. This fails. Seems like fedup is not able to handle this layout.
fedup is not touching anything in partition layout. (someone on devel@ group stated this recently) fedup downloads packages, new kernel and "installation" initrd. Then it uses yum/rpm do upgrade OS. So it should be possible to upgrade your machine.
3.) Kickstart: It looks like this is most likely the way to get it working. But I was not able to write a working kickstart script. The online doc is not enough for that. I found same kickstart examples using Google, but these didn't work either.
This is the only chance to do what you want. I also wait with upgrade/reinstall on some of my boxes because I can't play with kickstart to learn how it works. I have no spare box to destroy for one day. You can see content of kickstart-ks.cfg in /root directory of your Fedora 17 install and use it for new installation.
It should be called as 'anaconda-ks.cfg' in your '/root/' directory.
Sorry, my fault.
Mateusz Marzantowicz
Hi thx for your answer.
On Thursday, June 06, 2013 02:04:24 PM Mateusz Marzantowicz wrote:
On 06.06.2013 10:30, Gerhard Gappmeier wrote:
Unfortunately the installer does not allow to create this kind of partition layout. With F17 this was possible.
Yes, it was possible in F17. Now it isn't :) It's kind of improvement in installer.
2.) Installing F17 and upgrade using fedup. This fails. Seems like fedup is not able to handle this layout.
fedup is not touching anything in partition layout. (someone on devel@ group stated this recently) fedup downloads packages, new kernel and "installation" initrd. Then it uses yum/rpm do upgrade OS. So it should be possible to upgrade your machine.
fedup works without error, but after reboot the system cannot mount the root partition. I guess the newly created initrd does not work anymore.
3.) Kickstart: It looks like this is most likely the way to get it working. But I was not able to write a working kickstart script. The online doc is not enough for that. I found same kickstart examples using Google, but these didn't work either.
This is the only chance to do what you want. I also wait with upgrade/reinstall on some of my boxes because I can't play with kickstart to learn how it works. I have no spare box to destroy for one day. You can see content of kickstart-ks.cfg in /root directory of your Fedora 17 install and use it for new installation.
I tried this also. I used the F17 generated anaconda-ks.cfg and only removed the F17 repos. Then I booted the F18 network install CD, pressed Esc, entered the "linux ks=...." command and the installation starts. But here I get the error "Installation Destination: Error checking storage configuration."
I looks like there is no way to install F18 on this setup.
BTW, I also tried the "hardcore" way. Installed F18 using only LVM. Then booted SystemResue CD. Archived the system using tar. Reformated the system using fdisk, setup everything using mdadm and lvm tools. Restored the system to the new partitions. Changed /etc/fstab and grub configuration, reinstalled grub and rebootet. But the old initrd was not able to detect the raid stuff.
So I rebooted SystemRescue, chrooted again to F18, tried to generate a new initrd using dracut. I explicitly added devicemapper, md and lvm support to dracut modules. But this didn't work either.
At the moment I've no clue howto solve that problem. Maybe I should use also Gentoo for the server. This works without problems. But I wanted to avoid that, because keeping the system up2date is more work with Gentoo.
regards, Gerhard
On Thu, 06 Jun 2013 16:42:34 +0200 Gerhard Gappmeier gerhard.gappmeier@ascolab.com wrote:
I looks like there is no way to install F18 on this setup.
Have you tried yum? officially unsupported, but works for some. https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum#Fedora_17_-.3E_Fed...
Just have backups done first I went from F16.raid1 to > F17 > F18, following the relevant details from above (links)
I don't use lvm though.
On 06.06.2013 10:30, Gerhard Gappmeier wrote:
Hi all,
I'm trying to get F18 installed on a server (x86_64). The setup is quiet easy and typical for a server:
Partitions: sda1: primary partition, 512M sda2: primary partition, rest of the disk sdb1: primary partition, 512M sdb2: primary partition, rest of the disk
SOFT RAID: /dev/md0: raid1, consists of sda1 and sdb1 /dev/md1: raid1, consists of sda2 and sdb2
md0: formatted with ext2, mounted as /boot md1: LVM physical device.
LVM: LVM VG: "vg" using md1 LVM LV: "root", formatted as ext4, mounted as / LVM LV: "var", formatted as ext4, mounted as /var (this is for libvirt disk images) LVM LV: "swap", swap partition
Grub installed in both MBRs of sda and sdb, to allow booting from both disks.
Unfortunately the installer does not allow to create this kind of partition layout. With F17 this was possible.
What I've already tried:
1.) creating the layout manually using fdisk, mdadm and lvm tools. Selecting only the mountpoint in installer: This does not work. The installer does not correctly recognize the layout. I was not able to select the mountpoints.
2.) Installing F17 and upgrade using fedup. This fails. Seems like fedup is not able to handle this layout.
3.) Kickstart: It looks like this is most likely the way to get it working. But I was not able to write a working kickstart script. The online doc is not enough for that. I found same kickstart examples using Google, but these didn't work either.
Maybe somebody can assists me with that or has a better idea how to install that system.
19-TC2 driven by anaconda-19.30.3 is capable for a mentioned layout. http://alt.fedoraproject.org/pub/alt/stage/19-TC2/Fedora/%5Bi386%7Cx86_64%5D... or http://dl.fedoraproject.org/pub/alt/bfo/bfo.iso i.e. Pre-release > Fedora-19-Branched-[i386|x86_64]
poma
On 10.06.2013 03:39, poma wrote:
On 06.06.2013 10:30, Gerhard Gappmeier wrote:
Hi all,
I'm trying to get F18 installed on a server (x86_64). The setup is quiet easy and typical for a server:
Partitions: sda1: primary partition, 512M sda2: primary partition, rest of the disk sdb1: primary partition, 512M sdb2: primary partition, rest of the disk
SOFT RAID: /dev/md0: raid1, consists of sda1 and sdb1 /dev/md1: raid1, consists of sda2 and sdb2
md0: formatted with ext2, mounted as /boot md1: LVM physical device.
LVM: LVM VG: "vg" using md1 LVM LV: "root", formatted as ext4, mounted as / LVM LV: "var", formatted as ext4, mounted as /var (this is for libvirt disk images) LVM LV: "swap", swap partition
Grub installed in both MBRs of sda and sdb, to allow booting from both disks.
Unfortunately the installer does not allow to create this kind of partition layout. With F17 this was possible.
What I've already tried:
1.) creating the layout manually using fdisk, mdadm and lvm tools. Selecting only the mountpoint in installer: This does not work. The installer does not correctly recognize the layout. I was not able to select the mountpoints.
2.) Installing F17 and upgrade using fedup. This fails. Seems like fedup is not able to handle this layout.
3.) Kickstart: It looks like this is most likely the way to get it working. But I was not able to write a working kickstart script. The online doc is not enough for that. I found same kickstart examples using Google, but these didn't work either.
Maybe somebody can assists me with that or has a better idea how to install that system.
19-TC2 driven by anaconda-19.30.3 is capable for a mentioned layout. http://alt.fedoraproject.org/pub/alt/stage/19-TC2/Fedora/%5Bi386%7Cx86_64%5D... or http://dl.fedoraproject.org/pub/alt/bfo/bfo.iso i.e. Pre-release > Fedora-19-Branched-[i386|x86_64]
Could you give here a hint about how to create such layout? I was trying to do LVM on RAID1 but I was only able to create file systems on RAID devices or on LVM volumes but not to combine them together. I must be missing something in GUI.
Mateusz Marzantowicz
On 10.06.2013 09:35, Mateusz Marzantowicz wrote:
Could you give here a hint about how to create such layout? I was trying to do LVM on RAID1 but I was only able to create file systems on RAID devices or on LVM volumes but not to combine them together. I must be missing something in GUI.
STORAGE
INSTALL. DEST. <Custom part. sel.>
INSTALL. OPT. Partition scheme: Standard Partition -> "Custom partitioning"
MANUAL PARTITIONING
"+" Add a new mountpoint.
<RAID> Mount Point: "swap" & "/boot" Desired Capacity: "4G" & "500M" Device Type: "RAID" & "RAID" File System: "swap" & "ext4" RAID Level: "RAID1" & "RAID1" <\RAID>
<LVM> Mount Point: "/" & "/var" Desired Capacity: "20G" & "100G" Device Type: "LVM" & "LVM" File System: "ext4" & "ext4" <x2> Volume Group "<VGNAME>" -> "Modify…"(CONF. VG) RAID Level: "RAID1" -> "Save" <\x2> <\LVM>
"Update Settings" x4
"Done"
poma
-
Frank Murphy -
Gerhard Gappmeier -
Mateusz Marzantowicz -
poma -
Rejy M Cyriac