Skip to main content

Dual Boot Lenovo X1 Carbon - Windows 7 Fedora 18

Lenovo sent me a Recovery Media Kit - so, I decided to reinnstall Windows 7 Pro to see if their installation would resolve an issue I have been having with the SD card reader.

Boot the system and press Enter to Interrupt Normal Boot.
Press F1 to enter the BIOS, configure the Boot Options (under Startup) to boot Legacy first (this is only for the Windows Installation - as I could not get the Recovery Media to boot with UEFI)
Boot from the Disc 1 of 1 from Set 1 and follow the prompts.  If/when it asks, select GPT for your disk.
Remove the last 2 partitions on your disk (right-click My Computer, select Manage | Disk Manager)
Once the Windows Installation has completed, shut the machine down.

Boot the system and press Enter to Interrupt Normal Boot
Press F1 to enter the BIOS, configure the Boot Options (under Startup) to boot UEFI only, then change the Boot Order to boot the USB CD first
Reboot the system

The Fedora 18 installer can be a bit tricky (I'm not exactly a fan, personally)
You have to follow the disk partitioning in a particular order.

Click on Installation Destination
  Let me customize the partitioning of the disks instead

/boot/efi - sda1
/boot      - sda4
/             - lvm
/home     - lvm
<swap>  - lvm

Click on sda1 (EFI system partition)
  on the right, update the mountpoint to be /boot/efi
  click Apply Changes

Click the + symbol and add /boot (200MB)
-- this should create a sda4


Click the + symbol and add / (15000MB)
-- This should default to use LVM.  I click on the new mount point and update the VG name (simply a preference)

Click the + symbol and add swap (8000MB)
Click the + symbol and add /home (leave the size blank - it will auto-populate the remainder of the disk)

Add the refind rpm and update the BIOS to boot to refind.





Comments

Post a Comment

Popular posts from this blog

PXE boot a LiveCD image

Summary: I have wanted to build a kickstart environment which hosted a "rescue CD" or LiveCD to allow you to boot over the network after you blew your stuff up and needed to repair a few things.  Today I have worked through a method of doing so, with the help of the people who published a succinct script with the Red Hat Enterprise Virtualization Hypervisor.  (the script will be at the bottom of this post - if I have somehow not followed the GPL, please let me know and I will correct whatever is necessary) NOTE/Warning: The boot will fail due the initrd being too large (645mb).  I'm not sure how to proceed.  This procedure worked for RHEVh, because it is quite a bit smaller.  Hopefully I can report back with progress on this? :-$ Procedure: download your LiveCD image to /export/isos/RESCUE/Fedora-16-i686-Live-Desktop.iso # cd /var/tmp # vi livecd-iso-to-pxeboot (populate the file with the script shown below) # chmod 754 ./livecd-iso-to-pxeb...
2 comments
Read more

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)"

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)" One issue that may cause this to arise is if you managed to break your /etc/fstab We had an engineer add a line with the intended options of "nfsvers=3" but instead added "-onfsvers=3" and it broke the system fairly catastrophically.
Post a Comment
Read more

P2V using dd for KVM-QEMU guest

Preface: I have certainly not exhaustively tested this process.  I had a specific need and found a specific solution that worked. Situation:  I was issued a shiny new laptop running Red Hat Enterprise Linux 7 (with Corp VPN, certs, Authentication configuration, etc...)  The image was great, but I needed more flexibility on my bare metal.  So, my goal was to P2V the corporate image so I could just run it as a VM. * Remove corporate drive and install new SSD * install corp drive in external USB-3 case * Install RHEL 7 on new SSD * dd old drive to a disk-image file in a temp location which will be an image which is the same size as your actual drive (unless you have enough space in your destination to contain a temp and converted image) * convert the raw disk-image to a qcow file while pushing it to the final location - this step should reduce the disk size - however, I believe it will only reduce/collapse zero-byte blocks (not just free space - i.e. if you de...
1 comment
Read more