This article offers a step-by-step guide on how to dual-boot Windows 7 and Fedora 17 on a computer with two hard drives, with Fedora 17 installed on an LVM partitioning scheme. LVM, the Linux Logical Volume Manager, is the default disk partitioning scheme in Fedora 17, but disk space allocation to the logical volumes could be better.

Take the image below, for example, which was taken from a test installation of Fedora 17 KDE. It shows the default disk space allocation to the logical volumes. You can see that there are two primary partitions, one of which is a boot partition (/dev/sdb1) and the other (/dev/sdb2), the LVM Physical Volume. In addition, there are three logical volumes (see the top of section of the image). They are: lv_root, lv_home and lv_swap. Notice that there are no free space available.

That is because Anaconda allocates all available disk space to the logical volumes, when it is supposed to allocate just enough to install the system, especially to the root logical volume. For a desktop system, allocating 51 GB to the root logical volume is a waste of disk space.
Default Fedora 17 Partitions

The point of this tutorial, then, is to show how to dual-boot Fedora 17 and Windows 7 on a computer with two hard drives, with proper disk allocation to the logical volumes. Because the installation process is the same across all the Fedora 17 editions, this tutorial can be used to set up a dual-boot system between Windows 7 and Fedora 17 (main edition), which uses the GNOME 3 desktop environment, or any of the Fedora 17 Spins.

If you are not familiar with LVM and with disk partitioning in Linux, it is highly recommended that you read guide to disks and disks partitions in Linux and introductory articles to LVM here.

As on a default installation, two primary partitions and three logical volumes will be created. The first primary partition, which is a Standard partition, will be mounted at /boot, that is, it is the boot partition, where all boot-related programs will be located. The second primary partition will be the LVM Physical Volume, under which the three logical volumes will be created.

Related Post:  How to dual-boot Fedora 18 and Windows 8 on 1 HDD, with GRUB in a PBR

After the installation has completed, the computer will always boot into Windows, since it is installed on the first hard drive. At that stage, you have two options, if you want to be able to boot into Fedora: Change the default boot disk to /dev/sdb in the BIOS, or add an entry for Fedora in Windows 7’s boot menu. Because Fedora’s installer automatically adds an entry for Windows 7 in GRUB’s boot menu, using the first method requires very little effort; no additional software installation is required. The second method involves installing a special program on Windows 7. From experience, the second method is not necessary, so the recommendation is to use the first method.

If you have not done so already, download an installation image of Fedora 17 from here. Transfer it to a suitable media and boot the computer from it. Start the installer and click through the first steps until you get to the one shown in the image below. Select Basic Storage Devices, the click Next.
Fedora 17 Storage Devices

Because the hard drive that will be used for Fedora will be partitioned manually, select Create Custom Layout. Next.
Fedora 17 Partition Methods

Selecting Create Custom Layout and clicking Next in the previous step should land you in the window shown in the image below, where the disks and partitions connected to the computer are listed. At the top of the list is sda, where Windows 7 is installed. You do not want to mess with that one. Any action you take here MUST be on sdb, the target disk for Fedora 17. If there are existing partitions on it, as in this example, delete them. You do that by selecting each partition and clicking Delete. Again, be sure that you are not messing with any partition under sda.
Existing Partitions

Related Post:  4 security features in Fedora 16

After deleting the partitions under sdb, select the free space and click Create to start creating partitions. You will be presented with the window shown here. The default option on this window is Standard, which is what we want. Click Create.
Storage Types

On the next window, shown here, there are three options that we have to modify. They are: Mount Point, File System Type, and Size (in megabytes). For the boot partition, the mount point will, of course, be /boot. While the default file system type on Fedora and virtually all Linux distributions is Ext4, there are other options. However, you do not have to bother about them. Aside from physical volume (lvm) and swap, which we will be using further later, you do not need to bother about the rest, at least for this tutorial.
Anaconda Filesystem Options

When the right options for the boot partition have been selected, the window should look just like the one shown here. Notice that for the size, 500 MB was allocated. That is the default size allocation for a boot partition on most Linux distributions. If you do not have a lot of disk space to spare, you can go lower than that. As low as, say, 100 MB. OK.
Create /boot

With the boot partition out of the way, select the free space on the main window, and click Create. That should bring up the same window you saw earlier. Since the next partition is a primary partition for LVM, select LVM Physical Volume. Create.


Share on facebook
Share on twitter
Share on pinterest
Share on linkedin

Hola! Did you notice that no longer runs network ads?  Yep, no more ads from the usual suspects that track you across the Internet.  But since  I still need to pay to keep the site running, feel free to make a small donation by PayPal.

Subscribe for updates. Trust me, no spam!

Mailchimp Signup Form

Sponsored links

1. Attend Algorithm Conference, a top AI and ML event for 2020.
2. Reasons to use control panel for your server.
3. DHgate Computers Electronics, Cell Phones & more.

10 Responses

  1. “1. Change the Hostname: In the process of installing your brand new Fedora 19 desktop, I’m sure you noticed that Anaconda, the Fedora system installer, did not give you the option of setting a hostname (if it did, then I need more than a new pair of specs).”

    It’s in the Network panel. I’ve booked you an appointment with the optometrist 🙂

    1. That’s funny. But why did you have to “hide” it in the network spoke? This becomes a design issue. Remember that in the hub, the network spoke is not marked as an item that needs to be configured, in the same manner than the installation destination spoke is.

      You know, just before I published that article, I installed a system just to look for that feature. Your design guys should be working for Booz Allen Hamilton 🙂

      Where did they hide the option to install the bootloader in a custom location? 😉 I looked for that, too.

      1. “But why did you have to “hide” it in the network spoke?”

        What spoke would you *expect* it to be in? Software Selection? Installation Source? Installation Destination? Keyboard? None of those appears to make a whole deal of sense. “Network” seems the perfectly logical place for it, to me. A system’s host name is only of any interest in the context of a network, after all.

        “Where did they hide the option to install the bootloader in a custom location?”

        That depends on what you mean by ‘custom location’. You can pick which disk it will be installed to from the “Full disk summary and bootloader…” link on the Installation Destination page. (I’d figure the word ‘bootloader’ should be adequate indication of that.) You cannot choose to install the bootloader to a partition header when doing a BIOS install. See for that bikeshed.

        1. Not sure where to begin with something this wrong. A machine without a hostname is WRONG, WRONG, WRONG. Network or no network.

          Or do you call your pet, “dog” instead of giving it a name, because you probably only have one, right?

          1. Arguments welcome, bare assertions tend to be ignored.

            The machine is not ‘without a hostname’ if you don’t set one explicitly. It gets the hostname localhost.localdomain.

      2. “Remember that in the hub, the network spoke is not marked as an item that needs to be configured, in the same manner than the installation destination spoke is.”

        Indeed. It does not *need* to be configured. You can *choose* to configure it if you so desire. One of the main points of a hub/spoke design is that you are not forced through steps you don’t need to modify, but choose which you do and don’t want to use.

        1. But considering that the hostname is something that most users like to personalize, shouldn’t there be an indication that there’s something in that spoke that needs to be modified?

          1. “But considering that the hostname is something that most users like to personalize”

            I don’t agree with that assertion.

            “shouldn’t there be an indication that there’s something in that spoke that needs to be modified?”

            No. It doesn’t need to be modified. The indicators indicate that you *have* to change something on that spoke in order to proceed. The lack of an indicator isn’t meant to indicate ‘there’s no reason to come in here’. If there was no reason the spoke wouldn’t _be_ there at all.

  2. You can set the hostname during the install by clicking the network icon. I change my hostname and also add nameservers.

Leave a Reply

Your email address will not be published. Required fields are marked *

Get the latest

On social media
Via my newsletter
Mailchimp Signup Form

Partner links

1. Attend Algorithm Conference, a top AI and ML event for 2021.
2. Reasons to use control panel for your server.
3. DHgate Computers Electronics, Cell Phones & more.
Hacking, pentesting distributions

Linux Distributions for Hacking

Experts use these Linux distributions for hacking, digital forensics, and pentesting.


The authors of these books are confirmed to speak during

Algorithm Conference

T-minus AI

Author was the first chairperson of AI for the U.S. Air Force.

The case for killer robots

Author is the Director of the Center for Natural and Artificial Intelligence.

Why greatness cannot be planned

Author works on AI safety as a Senior Research Scientist at Uber AI Labs.

Anastasia Marchenkova

An invitation from Anastasia Marchenkova

Hya, after stints as a quantum researcher at Georgia Tech Quantum Optics & Quantum Telecom Lab, and the University of Maryland Joint Quantum Institute, I’m now working on superconducting qubit quantum processors at Bleximo. I’ll be speaking during Algorithm Conference in Austin, Texas, July 16 – 18, 2020. Meet me there and let’s chat about progress and hype in quantum computing.