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

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

Sun USS 7100 foo

TIP: put ALL of your LUNs into a designated TARGET and INITIATOR group when you create them.  If you leave them in the "default" group, then everything that does an discovery against the array will find them :-( I'm struggling to recognize a reason that a default should even be present on the array. Also - who, exactly, is Sun trying to kid.  The USS is simply a box.. running Solaris .. with IPMP and ZFS.  Great.  If you have ever attempted to "break-in" or "p0wn" your IBM HMC, you know that there are people out there that can harden a box - then.. there's Sun.  After a recent meltdown at the office I had to get quite intimate with my USS 7110 and learned quite a bit.  Namely: there's a shell ;-) My current irritation is how they attempt to "warn you" away from using the shell (my coverage expired a long time ago to worry about that) and then how they try to hide things, poorly. I was curious as to what version of SunOS it ...
1 comment
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