LinuxQuestions.org
Visit Jeremy's Blog.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 01-04-2019, 09:03 PM   #1
Erdward
LQ Newbie
 
Registered: Oct 2018
Posts: 23

Rep: Reputation: Disabled
Fedora 29 dual boot with Windows 10 - Installation


I'm in the process of trying to set up a dual boot on my lenovo x1 carbon laptop. I have done this once before, many years ago.

So far I have repartitioned my drive to free up space for Fedora. I'm running the live boot off a usb, and need to setup the storage configuration. I'm tempted to just use the "Automatic" option, but I recall running into to trouble with this the last time I set things up. I don't recall why I used to the custom configuration last time... maybe because after installation, my system would just go straight into Windows with no Fedora option? Unfortunately, I do not recall exactly...

Can someone offer some advice here please? Can I just go with the Automatic option? Or should I configure some things in a certain way?
 
Old 01-04-2019, 11:41 PM   #2
Brains
Senior Member
 
Registered: Apr 2009
Distribution: All OS except Apple
Posts: 1,591

Rep: Reputation: 389Reputation: 389Reputation: 389Reputation: 389
I never go with automatic, there has been some distributions in the past where the automatic feature used the entire drive and effectively wiped out existing operating systems. Custom installations are usually not so complicated, once you agree to the use of the designated free space, it'll set up the partitions and go automatic from there.
Your laptop is likely UEFI based, which means it will still go into Windows automatically, you will likely have to hit a designated F key at the Lenovo splash at bootup to get the UEFI boot menu to select either Windows or Fedora. Which F key, Google it or go into UEFI settings (BIOS) and navigate to the boot tab, it may mention something there and may require you to set it up enabled.
 
Old 01-04-2019, 11:57 PM   #3
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 21,151

Rep: Reputation: 4125Reputation: 4125Reputation: 4125Reputation: 4125Reputation: 4125Reputation: 4125Reputation: 4125Reputation: 4125Reputation: 4125Reputation: 4125Reputation: 4125
On the contrary, I would advise to use the default, which will be to setup LVM for you. I still find the Fedora/RH partitioning less than obvious. Any issues can be cleared up later - except the loss of the system of course.
Before you start, create a system image from Win10 - I never use Lenovo, they seem to go out of their way to screw Linux users. I always create the system image when working with Win systems - works too when/if you have to re-install.
 
Old 01-05-2019, 12:06 AM   #4
Brains
Senior Member
 
Registered: Apr 2009
Distribution: All OS except Apple
Posts: 1,591

Rep: Reputation: 389Reputation: 389Reputation: 389Reputation: 389
Quote:
Originally Posted by syg00 View Post
On the contrary, I would advise to use the default, which will be to setup LVM for you. I still find the Fedora/RH partitioning less than obvious. Any issues can be cleared up later - except the loss of the system of course.
Before you start, create a system image from Win10 - I never use Lenovo, they seem to go out of their way to screw Linux users. I always create the system image when working with Win systems - works too when/if you have to re-install.
This is kind of where I'm going, just make sure it don't use the whole drive, show it where you want it to install itself and leave defaults for the rest. Highly unlikely to loose anything else on the drive.

EDIT: Keep in mind, the Windows 10 WinRE partition needs to be right after the Windows OS partition, if the free space created is in between the Windows and WinRE partitions, there's a good chance a future Windows Creator's update will shrink the Windows partition and create a new WinRE after it, rendering the existing one at the end of the drive useless.
If this is the route already taken, and new partitions are created between Windows and WinRE partitions, the Windows recovery environment becomes disabled.

Last edited by Brains; 01-05-2019 at 12:13 AM. Reason: Added.
 
1 members found this post helpful.
Old 01-05-2019, 05:09 AM   #5
colorpurple21859
LQ Veteran
 
Registered: Jan 2008
Location: florida panhandle
Distribution: Slackware Debian, Fedora, others
Posts: 7,389

Rep: Reputation: 1594Reputation: 1594Reputation: 1594Reputation: 1594Reputation: 1594Reputation: 1594Reputation: 1594Reputation: 1594Reputation: 1594Reputation: 1594Reputation: 1594
Quote:
EDIT: Keep in mind, the Windows 10 WinRE partition needs to be right after the Windows OS partition, if the free space created is in between the Windows and WinRE partitions, there's a good chance a future Windows Creator's update will shrink the Windows partition and create a new WinRE after it, rendering the existing one at the end of the drive useless.
If this is the route already taken, and new partitions are created between Windows and WinRE partitions, the Windows recovery environment becomes disabled.
That is nice to know. I have never partitioned a drive this way, so have never come across this issue.
 
Old 01-05-2019, 05:18 AM   #6
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 21,151

Rep: Reputation: 4125Reputation: 4125Reputation: 4125Reputation: 4125Reputation: 4125Reputation: 4125Reputation: 4125Reputation: 4125Reputation: 4125Reputation: 4125Reputation: 4125
I don't pretend to understand the thinking of M$oft, but when I create a system image, it offers to delete the recovery partition and states the image is all that is needed ... :shrug:

On the occasions that I have needed to restore a Win10 system (always a result of a Win10 update), no problems. Then I do a simple restore of my Linux systems and proceed. Such a contrast as how easy it is with Linux ...
 
Old 01-05-2019, 06:13 AM   #7
yancek
LQ Guru
 
Registered: Apr 2008
Distribution: Slackware, Ubuntu, PCLinux,
Posts: 10,564

Rep: Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498
If you aren't sure, verify that your windows 10 is UEFI (or not). Make sure then that Fedora is installed UEFI.
Did you shrink your windows partition to make room for Fedora, leaving unallocated space? Did you re-boot windows after the resizing to verify that it still boots? If your windows is UEFI, do you have any familiarity with it? If not, do some research so you understand what to expect. I would turn off anything related to hibernation in windows before installing Fedora.

You might take a look at the link below at the Fedora Project which has some info. I believe Fedora by default will do an LVM install which requires a separate boot partition as well as the separate EFI partition (which should already exist if windows 10 is UEFI).

https://ask.fedoraproject.org/en/que...boot-w-fedora/
 
Old 01-05-2019, 10:45 AM   #8
Erdward
LQ Newbie
 
Registered: Oct 2018
Posts: 23

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Brains View Post
EDIT: Keep in mind, the Windows 10 WinRE partition needs to be right after the Windows OS partition, if the free space created is in between the Windows and WinRE partitions, there's a good chance a future Windows Creator's update will shrink the Windows partition and create a new WinRE after it, rendering the existing one at the end of the drive useless.
If this is the route already taken, and new partitions are created between Windows and WinRE partitions, the Windows recovery environment becomes disabled.
This seems to be the case for me now:


Click image for larger version

Name:	disk.jpg
Views:	202
Size:	175.6 KB
ID:	29403

Is there a simple way to fix this to avoid future problems? Is it really worth worrying about? I'm leaving windows installed really as an emergency backup. I won't be using it much.

At this point, my drive is partitioned as above, I've created a restore point on a usb, and have Fedora 29 on a usb ready to go. I've also confirmed that Windows 10 is in UEFI. The comments lead me to believe I should just go ahead with the automatic storage configuration and deal with potential problems after that?
 
Old 01-05-2019, 05:52 PM   #9
Brains
Senior Member
 
Registered: Apr 2009
Distribution: All OS except Apple
Posts: 1,591

Rep: Reputation: 389Reputation: 389Reputation: 389Reputation: 389
Quote:
Originally Posted by Erdward View Post
This seems to be the case for me now:


Attachment 29403

Is there a simple way to fix this to avoid future problems? Is it really worth worrying about? I'm leaving windows installed really as an emergency backup. I won't be using it much.

At this point, my drive is partitioned as above, I've created a restore point on a usb, and have Fedora 29 on a usb ready to go. I've also confirmed that Windows 10 is in UEFI. The comments lead me to believe I should just go ahead with the automatic storage configuration and deal with potential problems after that?
The WinRE partition on the first drive is for push button reset, this is in case Windows fails to boot, you may be able to hit an F key to start this recovery mode that can possibly fix boot problems automatically, give you a command prompt, restore a backup image etc. If Windows fails to boot 3 times or so, some systems are set to start this recovery mode automatically.

It appears you don't have a recovery media partition where the Windows original setup DVDs are typically stored that the WinRE push button recovery would resort too in the event you want to recover from the factory image. You may want to look at your recovery media creation options to see if you can burn something to DVDs or USB that can be used in a full system recovery. In the search field, type "recovery drive" and you should have a desktop app offered to create recovery media. The WinRE partition must be enabled for creating recovery media.

The reason that WinRE push button recovery partition can eventually be recreated is because Microsoft knows a lot of us shoot first ask questions later, they make sure you can recover your OS if it all of a sudden stops working when you really need it, this helps lower the amount of people employed at help desks because less people call for help when it can fix itself automatically after a few failed boots.

In GPT drives, partitions are in order of creation, if you leave things the way they are in that pic you posted and install Fedora in between, the WinRE partition will still be partition #4. To set up the WinRE recovery in Windows, it is the number of the partition that is used. Unfortunately, it still needs to reside after the Windows partition as of last fall, last fall's Creator's update surprised a lot of folks who installed Linux between Windows and the WinRE. To see if your recovery environment is still enabled, open a command prompt as administrator and enter command: Reagentc /info. The output should show if it is enabled and also mention where it is as in the example below.

Code:
C:\WINDOWS\system32>Reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:

    Windows RE status:         Enabled
    Windows RE location:       \\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE
    Boot Configuration Data (BCD) identifier: 5daea3ea-f2ff-11e8-8624-cce1570e2807
    Recovery image location:
    Recovery image index:      0
    Custom image location:
    Custom image index:        0

REAGENTC.EXE: Operation Successful.
Your best bet at this point is to make a bit for bit image of the current WinRE partition, then delete it, then create a new partition after the Windows partition of the same size and paste the image in that new partition before installing Fedora. This way it's partition will still be the 4th partition and you may not need to reset it's configuration. BootitBM is my favorite tool for doing this as it has partition tools and Image For DOS to create the image and paste it in the new partition, but there are other software suits that can do the same. Then check again with the ReagentC /info command to ensure it's still enabled. If not you will need to run some Reagent commands to enable it, it's not that complicated and there are lots of tutorials via a Google search.

EDIT: If anyone decides to use BootitBM for the tasks listed above, during BootitBM media creation steps, leave all default settings except choose 64k for Vesa video and choose "Partition work" instead of "Normal" when this option presents itself. Normal will start the application in such a way that you can accidentally hit OK which will install the Boot manager, you don't want to do this, you want to work on partitions. When it boots to the partition work screen, hit exit to get to other options menu, then click on Image to create partition image. It creates compressed images of data only, it won't include free space in the image making it smaller in size than the actual partition size.

Last edited by Brains; 01-05-2019 at 06:29 PM.
 
Old 01-05-2019, 07:59 PM   #10
Erdward
LQ Newbie
 
Registered: Oct 2018
Posts: 23

Original Poster
Rep: Reputation: Disabled
OK, trying to wrap my head around all this...

Brains, can I use the TBWinPE/RE Builder? I'm not sure how this is different from the BM tool. I just the Builder to copy the winRE partition to a usb key (I think!), but I'm not sure what to do next in order to delete and then recreate a moved version of this partition.
 
Old 01-05-2019, 10:25 PM   #11
Brains
Senior Member
 
Registered: Apr 2009
Distribution: All OS except Apple
Posts: 1,591

Rep: Reputation: 389Reputation: 389Reputation: 389Reputation: 389
Quote:
Originally Posted by Erdward View Post
OK, trying to wrap my head around all this...

Brains, can I use the TBWinPE/RE Builder? I'm not sure how this is different from the BM tool. I just the Builder to copy the winRE partition to a usb key (I think!), but I'm not sure what to do next in order to delete and then recreate a moved version of this partition.
I've never used this tool, and you will need to download and install Windows 10 ADK which is just over 4GB in size, and it appears Image for Windows would need to be installed. BootitBM is only a couple megabytes and you don't install anything. You simply download and extract it, click on MakeDisk.exe to create an ISO to burn to disk or have a USB key plugged in and install to the key. Then you boot whichever one you created and work on the partition and image creation in DOS mode independent of any OS. And you don't need to rebuild anything, just relocate the partition.

After downloading and extracting BootitBM, click on Makedisk to create either an ISO to burn to CD or a bootable USB key, have the key plugged in and follow instructions in my last post edit. Then you will need to reboot and go into computer settings (BIOS) and change booting to legacy instead of UEFI, save the setting and exit and hit the appropriate key if necessary to get a boot menu where you can select to boot the media you created.

If you selected partition work instead of normal during creation as I mentioned in my edit, it will start at partition work window. You should'nt need to make an image, I remembered BootitBM has a slide function. Highlight the WinRE_DRV partition and click the "Slide" button on the right. In the window that appears, there should be a large number of megabytes in the "Space before" box, change that number to a 0, leave the Data only check in the check box and click OK. It will give a warning but I've yet to see this software suite fail and I've used it for 17 years, click OK and it will take a while and recreate the same partition with same name, same UUID, same data just after the Windows OS partition and delete the old one. When it completes, find your way to the main menu by clicking OK and exit, at the main menu, click "reboot" at bottom right of screen and go back to Computer settings to enable UEFI boot instead of Legacy so you can boot back into Windows.

Now open Command promp as adminstrator to check if Recovery environment still OK. The command: ReagentC /info may still show it enabled, but that might not necessarily be the case, to ensure it is good, disable it, then enable it with following commands below, if after that it still shows it is enabled you should be good to go.

Code:
ReagentC /disable
ReagentC /enable
ReagentC /info
You can also run a test with command: ReagentC /boottore, then close all windows and reboot, it should reboot directly into recovery environment. This is a one time thing, hitting quit or exit will get you out of there and back to Windows.
 
Old 01-06-2019, 09:32 AM   #12
Erdward
LQ Newbie
 
Registered: Oct 2018
Posts: 23

Original Poster
Rep: Reputation: Disabled
Thanks for the detailed response. Just to confirm, when I run MakeDisk, I should use the PC Platofrm (BIOS) option, not the PC Platform (UEFI) option?
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Dual boot without windows - Windows 10 UEFI dual boot with Metamorphose Panther(Debian/KDE) mithidieri Linux - Newbie 7 11-03-2017 12:10 AM
Windows 7 Fedora 20 Dual Boot - Fedora Installation Failing to Boot BlooMeth Fedora 4 08-15-2015 01:17 PM
LXer: My first-ever Windows installation experience, a Fedora 13-Windows 7 dual-boot LXer Syndicated Linux News 0 08-09-2010 07:50 AM
grub boot loader installation in dual boot machine after windows 7 installation sourabh.sinha Linux - Newbie 4 03-23-2010 09:22 AM
System boot failure after installation of fedora fc11 in dual boot with windows xp npsdevan Fedora - Installation 1 08-10-2009 04:45 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 12:22 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration