From BIOS + MBR to UEFI + GPT
Hello,
I am trying to convert my classic installation from MBR to GPT and at the same time switch from BIOS to UEFI.
If you must know, I am doing this to be able to try several OS without the 4 primary partitions limitations
So I did some reading on the wiki (always full of many advices and useful information) and this seems possible but there are some steps I can't figure out.
Here is my current MBR layout:
$ LANG=C sudo fdisk -l /dev/sda
Disk /dev/sda: 59.6 GiB, 64023257088 bytes, 125045424 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x74d7d416
Device Boot Start End Blocks Id System
/dev/sda1 * 63 1992059 995998+ 83 Linux
/dev/sda2 1992060 5992244 2000092+ 82 Linux swap / Solaris
/dev/sda3 5992245 125040639 59524197+ 83 Linux
sda1 is the /boot partition with grub2, sda2 swap and sda3 is /.
This would be done on a Dell Latitude E6410.
I freed some space (around 3 MB) at the end of the disk as gdisk gave me a warning when I ran it. There is no warning anymore.
I guess I will have to convert the disk from MBR to GPT using gdisk and "just" writing the new GPT layout (from gparted live CD)
But then, what's next?
Do I need a BIOS Boot Partition?
(I'd say no as I plan to use UEFI + GPT but I'm not sure)
Should I make some more room to fit a 512MB EFI System Partition somewhere? (if needed, I'm probably going to take the 512MB from the swap)
(I'd say yes )
Can I put this partition anywhere on the disk? (as long as I flag it as boot?)
Thanks in advance!
lilorox
Last edited by lilorox (2014-06-10 21:50:58)
lilorox wrote:
OK, so basically, I just need to reformat my /boot in vfat and UEFI will be able to see the .efi inside that partition and will propose it as a mean to boot, right?
But, I can't find any .efi files inside my current /boot partition.
Your BIOS can only read FAT-formatted drives. Create the EFI System Partition in the live environment, mount it to /mnt/something, mount your / directory to /mnt/something_else, copy (-r) /mnt/something_else/boot to /mnt/something then change /etc/fstab as I have demonstrated
You will need to boot in EFI-mode using the Arch live disk, then arch-chroot into your installation to put the bootloader in place; gummiboot or pure EFISTUB is the simplest & easiest to set up IMO. You need to be booted up in EFI-mode to successfully install the EFI bootloader --- check by using:
efivar -l
It will return a long list of variables if the system is booted in EFI-mode...
Similar Messages
-
[Solved] Converting from BIOS+Grub1+MBR to UEFI+Grub2+GPT
Hello community,
my motherboard has an annoying bug, the POST sometimes taking over 20 seconds. Now I noticed that my motherboard is actually in the BIOS legacy mode, while UEFI mode is available. So I'd like to switch to UEFI in the hope that the BIOS bug won't appear there. I've read through several Wiki pages and forum posts, but still don't really know how to proceed.
The current setup is: The motherboard is in BIOS legacy mode, an HDD and an SSD are connected. The HDD contains just a big data partition while the SSD contains /, /home and swap. Grub1 is installed in the MBR of the SSD.
As far as I have understood from the Wiki, I need to change the partition table to GPT before switching to UEFI. According to https://wiki.archlinux.org/index.php/GP … MBR_to_GPT it is even possible without data loss. Since I need to free 1MiB at the end of the partition table, I'd need to boot some Live-USB and perform all the operations from there. So my first question is: If I change to GPT from Live-USB, will Grub1 still be able to boot the system afterwards?
Second thing is, I've noticed that Grub1 is neither present in the repos, nor in the AUR any more. So if I uninstall it and something goes wrong, how to get Grub1 back?
Thanks for any help,
Photon
Last edited by PhotonX (2013-03-01 12:09:16)PhotonX wrote:my motherboard has an annoying bug, the POST sometimes taking over 20 seconds. Now I noticed that my motherboard is actually in the BIOS legacy mode, while UEFI mode is available. So I'd like to switch to UEFI in the hope that the BIOS bug won't appear there. I've read through several Wiki pages and forum posts, but still don't really know how to proceed.
Try a live-medium that starts in UEFI-mode. The easiest way would be using the latest Ubuntu. If you've switched your BIOS from legacy boot to UEFI first, Ubuntu should detect this and start in UEFI mode. So you could check if it solves your POST problem.
If you want to try it with the latest Arch-ISO just follow the wiki for creating a UEFI bootable usb device. After booting this device, check if it really has booted in UEFI-mode
PhotonX wrote:Second thing is, I've noticed that Grub1 is neither present in the repos, nor in the AUR any more. So if I uninstall it and something goes wrong, how to get Grub1 back?
You can't (unless you are using an old Mac) . If you want UEFI and Grub, use grub-efi-x86_64. -
Hi there,
I've recently purchased a W530 with Windows 7 pre-installed. Ultimately, I'd like to replace this with Window 8 + Secure Boot. I believe I can get Windows 8 via the Microsoft Upgrade offer for a reasonable price, since this was a recent purchase.
What's the best way to reach my goal?
The Windows 7 install uses Legacy BIOS to boot with an MBR disk.
I had a quick look at Acronis, and I can see that it's possible that the "OS will be automatically converted to support UEFI booting" (http://www.acronis.com/support/documentation/ABR11/index.html#14021.html) when using it's tool.
If I don't use this approach, what can I do? Can I:
1. Use Rescue and Recovery in Windows 7 (Legacy BIOS/MBR disk)
2. Wipe the drive and reformat it with GPT?
3. Install Windows 7 with UEFI enabled using the Rescue and Recovery made in step 1?
4. At this point, I would now have UEFI and GPT.
5. Perform an Upgrade from Windows 7 to Windows 8 and enable Secure Boot?
Any thoughts as to whether this would work?
Richard.Hi richii,
The Acronis approach ends up in failure. Didn't give it a second look at the reason, since the tool it's not necessary. I also tried several other "automatic" tools without success.
The recovery approach will fail because it's tied up to BIOS boot.
But I've performed the conversion from BIOS to UEFI two times successfully. After some digging, is not SO hard. It's just... "undocumented". Very, very undocumented, hehe. I made a step-by-step guide: http://social.technet.microsoft.com/wiki/contents/articles/14286.converting-windows-bios-installatio...
Let me know if it helps you...
Anyway, if you don't have data/software, I would go for the clean install approach.
Cheers.
If I helped you, please give me some kudos! ^^ -
How to migrate to a new 4TB disk (switching from MBR to UEFI)
I have an HP Pavilion p7-1167c running Windows 7 Home Premium Service Pack 1.
My 1TB drive ran out of space, so I want to migrate to a new 4TB drive. However, the current drive is a MBR drive and I understand that I need to use UEFI to be able to utilize the full 4TB (ie I am limited to using 2TB of the 4TB if the 4TB drive is formatted as an MBR drive).
In the past when migrating to a new drive, I just cloned the drive. Can I still do this, even though they are formatted differently? I'm not sure if a cloning process would clone data from a MBR disk to a UEFI disk while keeping the disk formatting, or if a clone requires that the source and target disks be the same formatting.
If I can clone a drive from a MBR disk to a UEFI disk, how would I get my PC to boot using the new disk? Do I maybe need to change something in the BIOS to cause the PC to support UEFI?
If I can't clone the drive due to needing to go from MBR to UEFI, what should I do? Is the only option to do a build from scratch (ie reinstall the OS from scratch with the UEFI disk installed, then re-install all the apps, and then re-load my data from a backup)? I'm hoping to avoid this, due to the obvious large amount of effort that would take.
Thanks in advance for any guidance as to how how I might migrate my system to this new drive, while being able to utilize the full 4TB of space.
Thanks!Hi Steve,
Another point of clarification. You should be able to use a 4 TB hard drive for data. To use it as a replacement boot drive would required some special efforts using retail media and provided that the boot sources will support UEFI boot devices. If you boot up W8 installation media in UEFI mode then you could try installing W8 to the GPT formatted hard drive. I haven't tried this on your particular model so I can't say for sure that it will work.
HP DV9700, t9300, Nvidia 8600, 4GB, Crucial C300 128GB SSD
HP Photosmart Premium C309G, HP Photosmart 6520
HP Touchpad, HP Chromebook 11
Custom i7-4770k,Z-87, 8GB, Vertex 3 SSD, Samsung EVO SSD, Corsair HX650,GTX 760
Custom i7-4790k,Z-97, 16GB, Vertex 3 SSD, Plextor M.2 SSD, Samsung EVO SSD, Corsair HX650, GTX 660TI
Windows 7/8 UEFI/Legacy mode, MBR/GPT -
Hi there,
just wanted to share my experience with a manual P2V Migration. The VM became to ressource hungry and it was decided to move it off an ESX 5 Cluster to a dedicated physical Machine.
V2P Virtual Machine to physical Server IBM x3650 M4 and switch from BIOS to UEFI Boot environment
Task:
V2P Migrate a VMware virtual machine to a IBM x3650 M4 with a ServeRAID 5110e RAID Controller or any other LSI RAID Controller without 3rd Party tools.
This should also work with other RAID Controllers or Servers but be sure to pick the right drivers then.
Extra Task:
The VM's boot environment/virtual BIOS is BIOS, not UEFI (as per default VMware Setting). The physical Server is running in UEFI mode.
The Challenge:
After restore the Server won't boot or get into a BSOD (7B), because the RAID drivers are missing.
After restore the VM won't boot because the boot environment has changed from BIOS to UEFI
Preparations:
An existing physical Server of the same type and with the same RAID controller and same OS would be nice for troubleshooting and checking the registry.
An existing DHCP server will make networking things easier.
Connect the new physical server x3650 M4 to power and network
create a virtual drive that has at least the size of the existing VM plus the size of the full backup (.vhd). Should be about twice the size of the original vmdk.
Get a USB Flash stick (I used a 8GB modell so no problem with larger sticks)
Download and extract LSI MegaRAID Driver on that USB media (I used 6.705.05.00-MR_Windows_Driver directly from LSI website)
Download and extract INTEL Network Adapter Driver on that USB media (I used 12.11.97.0 of e1r62x64.inf from 19.5 driver release from 2014.09.26 directly from LSI website)
Step by Step:
if you have an other physical Server of the same type and same Controller and same OS:
1. open regedit and export everything related to SCSIAdapter and megasas2 to .reg files or skip this step and use my files below
some of this (sub)keys may not be accesible - you will then first take ownership and/or modify permissions to read them
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E97B-E325-11CE-BFC1-08002BE10318}
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI\VEN_1000&DEV_005B&SUBSYS_04121014&REV_05
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\megasas2
this one is more complicated:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase (only relevant are those devices where the service name is megasas2 - export the whole subkey and get the filtering done with tools like notepad++)
Make a copy of the following files/folders:
c:\programdata\LSI\
c:\windows\inf\megasas2.INF
c:\windows\inf\megasas2.PNF
c:\windows\system32\drivers\megasas2.SYS
on the existing VM:
1. create a full backup (image) with the built-in Windows Backup Utility and save it in an accessible network location (you will need this one, if anything goes wrong or you want to come back to this point.
Alternatively you could create a VMware snapshot.
2. import the .reg files you created earlier or import my files below.
Attention: This will make the VM unbootable!
But it is required to prepare the VM for the new RAID controller when it will be restored on the physical server.
Do NOT reboot now as this will make the VM unbootable!
4. Copy the LSI folder and the megasas2.INF/PNF/SYS files to the appropriate destination folders on the VM.
3. again create a full backup (image) with the built-in Windows Backup Utility and save it in an other accessible network location but not where you safed the first backup.
This will be the "golden" backup if you want, where the RAID controller is prepares. We will rebuild the new machine with this second backup.
4. Optional: you could use the Backuputility now to restore the Systemstate of the first backup and reboot or restore the VMware snapshot.
This will undo the changes we made to the VM.
on the new physical server:
1. boot the physical server from Windows Server 2008 R2 SP1 DVD
2. when it is ready to install, press shift+F10 to get command prompt and do not click to install Server 2008
3. check driveletter of the USB stick with diskpart list vol (was C: at my Server, so don't wonder about that letter)
3. load drivers for ServeRAID SAS controller (this is mandatory to see the volume in diskpart)
drvload c:\srv_2008_x64\megasas2.inf
4. load drivers for INTEL I350 Gigabit NIC's (you will need this to access the backup that is on the network)
drvload c:\PRO1000\NDIS62\e1r62x64.inf
5. wpeinit (will start network. wait ~15 sec to let it start and get IP address)
check if you have IP connectivity an address with ipconfig, if not, use an other NIC driver and repeat steps 4+5
6. create the EFI and BCD
diskpart
list disk
select disk x (where x is the number of the disk to convert)
clean
convert gpt
create partition EFI size=128
format fs=fat32 quick label=EFI
assign letter=i or any other free drive letter
create partition MSR size=128
6.1 Copy EFI bootloader to EFI partition
i: (where i is the letter of your EFI partition)
mkdir EFI\Boot
mkdir EFI\Microsoft\Boot
copy x:\Windows\Boot\EFI\bootmgfw.efi i:\EFI\Microsoft\Boot (where x ist the default letter of the current Windows PE environment)
copy x:\Windows\Boot\EFI\bootmgfw.efi i:\EFI\Boot\bootx64.efi (note that the file will be renamed to bootx64.efi)
7. create the new partitions
diskpart
create partition primary size=100000 (edit the size to your needs. this will later become the system drive of your server)
format fs=ntfs quick label=Windows
assign letter=Y or any other free drive letter
create partition primary size=990000 (this will temporarily store your backup and we need it for the restore process)
format fs=ntfs quick label=Backup
assign letter=B or any other free drive letter
exit
8. map network drive and copy the backup .vhd to the local disk
net use L: \\networklocation\where\you\saved\the\backup (enter the credentials when asked)
copy the .vhd file that contains the OS of your VM to the local Backup Partition B. The relevant vhd file is usually the largest file in that fileset.
Note that the names are very similarly - be sure to get the correct file!
copy "L:\WindowsImageBackup\VMNAME\Backup 2015-02-03 123456\00e767c6-xxxx-xxxx-xxxxxxxxxxxx.vhd" B:\
give it time, this is slow and will take some minutes/hours and you will not see any progress! Look at the disk-LED's to see if anything is still happening
9. mount the .vhd and copy it's contents to the new system partition
Note that you can only mount a locally stored .vhd. You cannot mount a .vhd in a network location.
diskpart
select vdisk file=B:\00e767c6-xxxx-xxxx-xxxxxxxxxxxx.vhd
attach vdisk
select vol 5 (where 5 is the number of the mounted vdisk)
assign letter=Z or any other free drive letter
exit
10. Restore the files from the image
z: (where z is the letter of your mounted .vhd)
xcopy * Y:\ /e /c /h /k /o /b /q /y (where Y: is the letter of your new partition with the label "Windows")
several "Access denied" messages appear, ignore them. Those are SystemVolumeInformation folders.
11. Create Boot Configuration Data (BCD)
bootrec /RebuildBcd
this will try to repair the missing BCD on the second of the two small partitions we created earlier in and should normally work, otherwise you'll have to create BCD manually (search google for that procedure)
Note that it may find more than one Windows installation and ask which sould be added to the boot list. Be sure to select only the one that is in the correct Volume (Y:\)
that's it - exit the DOS command box and close the "Install Windows" Window, after a prompt it will reboot.
Select "Start Windows Normally", if Windows Error Recovery appears.
12. Preparing Windows
When Windows boots for the first time, DO NOT reboot if you are asked, it won't come back at this stage!
Install Intel chipset drivers for the Server (I used "intc_dd_inteldp_9.4.0.1026_windows_32-64.exe" from IBM website)
Open Device Manager, uninstall the "RAID-Controller" with the exclamation mark. You cannot install the correct driver for this Device at this point, it will bring you the error: "Cannot create a stable subkey under a volatile
parent key"
Once again, DO NOT reboot!
In Device Manager select Action>Add Legacy Hardware
click Next
select Hardware manually
select Storage Controller as Type
LSI should be listed, select "LSI MegaRAID SAS 9281-8E"
click Next, ignore the error "Code 10" Message.
Click Done.
Rightclick the LSI MegaRAID SAS 9281-8E device with the exclamation mark in Device Manager
select Update driver
select Browse my computer for driver software
select let me pick from a list of device drivers on my computer
select "Have Disk"
browse to the folder where the extracted RAID driver 6.705.05.00-MR_Windows_Driver is located (e.g. USB Flash stick E:\6.705.05.00-MR_Windows_Driver\srv_2008_x64)
then unselect "Show Compatible Hardware"
on the right side, scroll up and select "IBM ServeRAID M5110e SAS/SSATA Controller"
ignore the Update Driver Warning and click Yes
click Next, ignore the error "Code 10" Message.
ignore the exclamation mark on "IBM ServeRAID M5110e SAS/SSATA Controller" in Device Manager but be sure that there is only this controller and no other RAID-Controller or LSI SAS Controller listed under "Other Devices"
or "Storage Controllers"
NOW you are safe to reboot
After reboot you will find two "IBM ServeRAID M5110e SAS/SSATA Controller" in Device Manager
Rightclick and uninstall the one with the exclamation mark. Do not tick the checkbox to remove the driver as well!
You're done!! (hopefully)Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C31115D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C38015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C41115D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C48015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C51115D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C58015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C61115D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C68015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C71115D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C78015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C81115D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C88015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C91115D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C98015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_D20219E5]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_D20319E5]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0071&SUBSYS_00721137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00011BD4]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00721137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00731137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_008F1137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00B01137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00B11137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00B61137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00B71137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00C21137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00C31137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_03B11014]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_040015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_040D1014]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_10541000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_11771734]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_14581002]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_1F201462]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_30351054]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_350C8086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_350D8086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_822910F1]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_843B1043]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_84711043]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92211000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92401000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92408086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92411000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92418086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92421000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92431000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92441000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92A01000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92A11000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0078&SUBSYS_92501000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0078&SUBSYS_92511000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0078&SUBSYS_92701000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_00011BAA]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_00021BD4]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_00791137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_02001AE3]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_03B21014]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_03B31014]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_03C71014]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_070015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_11761734]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_11B31734]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_30361054]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_350B8086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_84731043]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_84801043]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_8985152D]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92551000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92561000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92568086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92601000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92608086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92611000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92618086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92621000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92631000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92641000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92648086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92671000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92678086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92681000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92688086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92751000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92758086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92761000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92768086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92771000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92801000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92808086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92811000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92821000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92828086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92841000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92881000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92891000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92901000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92908086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_D20819E5]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_D20919E5]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0409&SUBSYS_10091000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10011000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10018086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10021000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10031000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10038086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10041000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10081000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10088086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_100C1000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_100D1000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10811734]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10a31734]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_20041000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_20051000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_30161054]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_34908086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_35008086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_35018086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_35048086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_35078086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_82871033]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0413&SUBSYS_10051000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7" -
Is it possible to bitlocker-encypt a UEFI/GPT drive from which I boot with Windows 7 64-bit ultimate (TPM-motherboard)?
Sure. BL does support GPT.
-
Dualboot with Windows from secondary MBR drive using e.g. grub/refind
Hi!
I'm trying to get my secondary drive with Windows 8, installed in MBR-mode to boot using either grub2, refind or any other suitable bootloader. "bootinfoscript" return:
Boot Info Script 0.61 [1 April 2012]
============================= Boot Info Summary: ===============================
=> is installed in the MBR of /dev/sda.
=> Windows is installed in the MBR of /dev/sdb.
sda1: __________________________________________________________________________
File system: vfat
Boot sector type: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /grub/grub.cfg /efi/arch_grub/grubx64.efi
/efi/refind/refind_x64.efi
sda2: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Arch Linux ()
Boot files: /etc/fstab
sdb1: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /bootmgr /Boot/BCD
sdb2: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /bootmgr /Windows/System32/winload.exe
sdb3: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System:
Boot files:
============================ Drive/Partition Info: =============================
Drive: sda _____________________________________________________________________
Disk /dev/sda: 55.9 GiB, 60022480896 bytes, 117231408 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Partition Boot Start Sector End Sector # of Sectors Id System
/dev/sda1 1 117,231,407 117,231,407 ee GPT
GUID Partition Table detected.
Partition Start Sector End Sector # of Sectors System
/dev/sda1 40 409,639 409,600 EFI System partition
/dev/sda2 409,640 115,752,999 115,343,360 Data partition (Linux)
Drive: sdb _____________________________________________________________________
Disk /dev/sdb: 1.4 TiB, 1500301910016 bytes, 2930277168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Partition Boot Start Sector End Sector # of Sectors Id System
/dev/sdb1 2,048 718,847 716,800 7 NTFS / exFAT / HPFS
/dev/sdb2 718,848 882,276,351 881,557,504 7 NTFS / exFAT / HPFS
/dev/sdb3 * 882,276,352 2,930,272,255 2,047,995,904 af HFS / HFS+
"blkid" output: ________________________________________________________________
Device UUID TYPE LABEL
/dev/sda1 39D2-CCE0 vfat
/dev/sda2 0c5d5c14-1e89-44ec-af4d-7b180ed693bc ext4
/dev/sdb1 780CD4910CD44BAE ntfs System Reserved
/dev/sdb2 105CD9745CD95556 ntfs
/dev/sdb3 bb50e1d4-cc4c-43cc-8597-54815366422f ext4
================================ Mount points: =================================
Device Mount_Point Type Options
/dev/sda1 /boot vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/sda2 / ext4 (rw,noatime,discard,data=ordered)
/dev/sdb3 /home ext4 (rw,relatime,data=ordered)
============================= sda1/grub/grub.cfg: ==============================
# DO NOT EDIT THIS FILE
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 0c5d5c14-1e89-44ec-af4d-7b180ed693bc
else
search --no-floppy --fs-uuid --set=root 0c5d5c14-1e89-44ec-af4d-7b180ed693bc
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_input console
terminal_output gfxterm
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=5
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_archlinux ###
menuentry "Arch Linux pkg-linux kernel" --class arch-linux --class arch --class gnu-linux --class gnu --class os {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
fi
set gfxpayload=keep
insmod fat
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 39D2-CCE0
else
search --no-floppy --fs-uuid --set=root 39D2-CCE0
fi
echo 'Loading Arch Linux pkg-linux kernel ...'
linux /vmlinuz-linux root=UUID=0c5d5c14-1e89-44ec-af4d-7b180ed693bc rw quiet
echo 'Loading Arch Linux pkg-linux kernel initramfs ...'
initrd /initramfs-linux.img
menuentry "Arch Linux pkg-linux kernel (fallback initramfs)" --class arch-linux --class arch --class gnu-linux --class gnu --class os {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
fi
set gfxpayload=keep
insmod fat
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 39D2-CCE0
else
search --no-floppy --fs-uuid --set=root 39D2-CCE0
fi
echo 'Loading Arch Linux pkg-linux kernel ...'
linux /vmlinuz-linux root=UUID=0c5d5c14-1e89-44ec-af4d-7b180ed693bc rw quiet
echo 'Loading Arch Linux pkg-linux kernel fallback initramfs ...'
initrd /initramfs-linux-fallback.img
### END /etc/grub.d/10_archlinux ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch Linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-0c5d5c14-1e89-44ec-af4d-7b180ed693bc' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod fat
set root='hd0,gpt1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 39D2-CCE0
else
search --no-floppy --fs-uuid --set=root 39D2-CCE0
fi
echo 'Loading Linux linux ...'
linux /vmlinuz-linux root=UUID=0c5d5c14-1e89-44ec-af4d-7b180ed693bc rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux.img
submenu 'Advanced options for Arch Linux' $menuentry_id_option 'gnulinux-advanced-0c5d5c14-1e89-44ec-af4d-7b180ed693bc' {
menuentry 'Arch Linux, with Linux linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-advanced-0c5d5c14-1e89-44ec-af4d-7b180ed693bc' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod fat
set root='hd0,gpt1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 39D2-CCE0
else
search --no-floppy --fs-uuid --set=root 39D2-CCE0
fi
echo 'Loading Linux linux ...'
linux /vmlinuz-linux root=UUID=0c5d5c14-1e89-44ec-af4d-7b180ed693bc rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux.img
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry "Microsoft Windows Vista/7/8 BIOS-MBR" {
insmod part_msdos
insmod ntfs
insmod search_fs_uuid
insmod ntldr
search --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 780CD4910CD44BAE
ntldr /bootmgr
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
### BEGIN /etc/grub.d/60_memtest86+ ###
### END /etc/grub.d/60_memtest86+ ###
=================== sda1: Location of files loaded by Grub: ====================
GiB - GB File Fragment(s)
=============================== sda2/etc/fstab: ================================
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda2
UUID=0c5d5c14-1e89-44ec-af4d-7b180ed693bc / ext4 rw,defaults,noatime,discard,data=ordered 0 1
# /dev/sda1
UUID=39D2-CCE0 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
# /dev/sdb3
UUID=bb50e1d4-cc4c-43cc-8597-54815366422f /home ext4 rw,relatime,data=ordered 0 2
=============================== StdErr Messages: ===============================
cat: /tmp/BootInfo-2fUreQzU/Tmp_Log: No such file or directory
No volume groups found
mdadm: No arrays found in config file or automatically
As seen, windows is installed in the MBR of /dev/sdb and grub, using the chainloader should be able to boot it (i guess).
I have the following in my 40-custom.
menuentry "Microsoft Windows Vista/7/8 BIOS-MBR" {
insmod part_msdos
insmod ntfs
insmod search_fs_uuid
insmod ntldr
search --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 780CD4910CD44BAE
ntldr /bootmgr
where the first is "--hint-bios= ..." is given by
sudo grub-probe --target=hints_string -d /dev/sdb1
and the UUID by
sudo grub-probe --target=fs_uuid -d /dev/sdb1
When I try to boot the above configuration, I get an error saying that "ntldr cannot be found" - and indeed, while I find "ntldr.mod" in "/usr/lib/grub/i386-pc/" I cannot find it in "/usr/lib/grub/x86_64-efi/".
I've also tried getting refind to identify "bootmgr" from windows without success. I guess it does not support NTFS or something.
Anyway, do anyone have any idea of how to get this to work - without reinstalling Windows in EFI-mode?
Thanks in advance,
eltdieelt wrote:
Hi!
I'm trying to get my secondary drive with Windows 8, installed in MBR-mode to boot using either grub2, refind or any other suitable bootloader. "bootinfoscript" return:
Boot Info Script 0.61 [1 April 2012]
============================= Boot Info Summary: ===============================
=> is installed in the MBR of /dev/sda.
=> Windows is installed in the MBR of /dev/sdb.
sda1: __________________________________________________________________________
File system: vfat
Boot sector type: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /grub/grub.cfg /efi/arch_grub/grubx64.efi
/efi/refind/refind_x64.efi
sda2: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Arch Linux ()
Boot files: /etc/fstab
sdb1: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /bootmgr /Boot/BCD
sdb2: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /bootmgr /Windows/System32/winload.exe
sdb3: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System:
Boot files:
============================ Drive/Partition Info: =============================
Drive: sda _____________________________________________________________________
Disk /dev/sda: 55.9 GiB, 60022480896 bytes, 117231408 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Partition Boot Start Sector End Sector # of Sectors Id System
/dev/sda1 1 117,231,407 117,231,407 ee GPT
GUID Partition Table detected.
Partition Start Sector End Sector # of Sectors System
/dev/sda1 40 409,639 409,600 EFI System partition
/dev/sda2 409,640 115,752,999 115,343,360 Data partition (Linux)
Drive: sdb _____________________________________________________________________
Disk /dev/sdb: 1.4 TiB, 1500301910016 bytes, 2930277168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Partition Boot Start Sector End Sector # of Sectors Id System
/dev/sdb1 2,048 718,847 716,800 7 NTFS / exFAT / HPFS
/dev/sdb2 718,848 882,276,351 881,557,504 7 NTFS / exFAT / HPFS
/dev/sdb3 * 882,276,352 2,930,272,255 2,047,995,904 af HFS / HFS+
"blkid" output: ________________________________________________________________
Device UUID TYPE LABEL
/dev/sda1 39D2-CCE0 vfat
/dev/sda2 0c5d5c14-1e89-44ec-af4d-7b180ed693bc ext4
/dev/sdb1 780CD4910CD44BAE ntfs System Reserved
/dev/sdb2 105CD9745CD95556 ntfs
/dev/sdb3 bb50e1d4-cc4c-43cc-8597-54815366422f ext4
================================ Mount points: =================================
Device Mount_Point Type Options
/dev/sda1 /boot vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/sda2 / ext4 (rw,noatime,discard,data=ordered)
/dev/sdb3 /home ext4 (rw,relatime,data=ordered)
============================= sda1/grub/grub.cfg: ==============================
# DO NOT EDIT THIS FILE
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 0c5d5c14-1e89-44ec-af4d-7b180ed693bc
else
search --no-floppy --fs-uuid --set=root 0c5d5c14-1e89-44ec-af4d-7b180ed693bc
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_input console
terminal_output gfxterm
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=5
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_archlinux ###
menuentry "Arch Linux pkg-linux kernel" --class arch-linux --class arch --class gnu-linux --class gnu --class os {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
fi
set gfxpayload=keep
insmod fat
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 39D2-CCE0
else
search --no-floppy --fs-uuid --set=root 39D2-CCE0
fi
echo 'Loading Arch Linux pkg-linux kernel ...'
linux /vmlinuz-linux root=UUID=0c5d5c14-1e89-44ec-af4d-7b180ed693bc rw quiet
echo 'Loading Arch Linux pkg-linux kernel initramfs ...'
initrd /initramfs-linux.img
menuentry "Arch Linux pkg-linux kernel (fallback initramfs)" --class arch-linux --class arch --class gnu-linux --class gnu --class os {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
fi
set gfxpayload=keep
insmod fat
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 39D2-CCE0
else
search --no-floppy --fs-uuid --set=root 39D2-CCE0
fi
echo 'Loading Arch Linux pkg-linux kernel ...'
linux /vmlinuz-linux root=UUID=0c5d5c14-1e89-44ec-af4d-7b180ed693bc rw quiet
echo 'Loading Arch Linux pkg-linux kernel fallback initramfs ...'
initrd /initramfs-linux-fallback.img
### END /etc/grub.d/10_archlinux ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch Linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-0c5d5c14-1e89-44ec-af4d-7b180ed693bc' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod fat
set root='hd0,gpt1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 39D2-CCE0
else
search --no-floppy --fs-uuid --set=root 39D2-CCE0
fi
echo 'Loading Linux linux ...'
linux /vmlinuz-linux root=UUID=0c5d5c14-1e89-44ec-af4d-7b180ed693bc rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux.img
submenu 'Advanced options for Arch Linux' $menuentry_id_option 'gnulinux-advanced-0c5d5c14-1e89-44ec-af4d-7b180ed693bc' {
menuentry 'Arch Linux, with Linux linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-advanced-0c5d5c14-1e89-44ec-af4d-7b180ed693bc' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod fat
set root='hd0,gpt1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 39D2-CCE0
else
search --no-floppy --fs-uuid --set=root 39D2-CCE0
fi
echo 'Loading Linux linux ...'
linux /vmlinuz-linux root=UUID=0c5d5c14-1e89-44ec-af4d-7b180ed693bc rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux.img
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry "Microsoft Windows Vista/7/8 BIOS-MBR" {
insmod part_msdos
insmod ntfs
insmod search_fs_uuid
insmod ntldr
search --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 780CD4910CD44BAE
ntldr /bootmgr
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
### BEGIN /etc/grub.d/60_memtest86+ ###
### END /etc/grub.d/60_memtest86+ ###
=================== sda1: Location of files loaded by Grub: ====================
GiB - GB File Fragment(s)
=============================== sda2/etc/fstab: ================================
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda2
UUID=0c5d5c14-1e89-44ec-af4d-7b180ed693bc / ext4 rw,defaults,noatime,discard,data=ordered 0 1
# /dev/sda1
UUID=39D2-CCE0 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
# /dev/sdb3
UUID=bb50e1d4-cc4c-43cc-8597-54815366422f /home ext4 rw,relatime,data=ordered 0 2
=============================== StdErr Messages: ===============================
cat: /tmp/BootInfo-2fUreQzU/Tmp_Log: No such file or directory
No volume groups found
mdadm: No arrays found in config file or automatically
As seen, windows is installed in the MBR of /dev/sdb and grub, using the chainloader should be able to boot it (i guess).
I have the following in my 40-custom.
menuentry "Microsoft Windows Vista/7/8 BIOS-MBR" {
insmod part_msdos
insmod ntfs
insmod search_fs_uuid
insmod ntldr
search --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 780CD4910CD44BAE
ntldr /bootmgr
where the first is "--hint-bios= ..." is given by
sudo grub-probe --target=hints_string -d /dev/sdb1
and the UUID by
sudo grub-probe --target=fs_uuid -d /dev/sdb1
When I try to boot the above configuration, I get an error saying that "ntldr cannot be found" - and indeed, while I find "ntldr.mod" in "/usr/lib/grub/i386-pc/" I cannot find it in "/usr/lib/grub/x86_64-efi/".
I've also tried getting refind to identify "bootmgr" from windows without success. I guess it does not support NTFS or something.
Anyway, do anyone have any idea of how to get this to work - without reinstalling Windows in EFI-mode?
Thanks in advance,
elt
UEFI GRUB(2) does not support booting BIOS boot loaders in non-Apple systems. For Apple Macs that support exists in form of 'appleloader' grub command. You might have better luck with rEFInd bios boot support but as per its author Rod Smith (srs5694) even that support is severely limited http://rodsbooks.com/refind/using.html#legacy .
You 40_custom is correct but that will work only in bios grub(2), not in uefi grub(2). 'ntldr' grub module is specific to bios grub(2).
Last edited by the.ridikulus.rat (2014-04-13 20:09:25) -
Edge e520 i5 UEFI/GPT Dual boot Windows/Ubuntu
Hi!
I have an Edge e520 1143GVG. It has an UEFI-Board with Win7/64 on MBR-Harddisk.
What I want:
GPT-Partition scheme and dual boot Windows 7/64 and ubuntu 14.04/64.
I managed to backup the partitions on an external HDD, install GPT on Harddisk, recopy saved Partitions and have now a fully running Win7/64 on GPT-System (it wasn't that easy as it seems here).
Next Step is to install Ubuntu on a separate Partition. I took a standard Ubuntu boot-CD, startet the pc with that boot disk (Board-Settings: UEFI/BIOS "Both", UEFI First) and installed Ubuntu without any trouble. Unfortunately no boot entry has been generated, so I tried to add one with EasyBCD. That doesn't work, an error is shown like "Windows cannot be startet, no valid file /NST/grub.mbr" or something like that.
I think the reason is that the cd booted in BIOS Mode, not UEFI. If I set board setting to "UEFI only", the boot CD will not start. So I built a bootable Ubuntu USB-Flashdrive with GPT-Scheme, but it didn't start as well.
After that I updated BIOS hoping UEFI-Boot from external devices will be possible then. It isn't.
The e520-board seems to be outdated or faulty, it is not possible to boot from USB or CD in UEFI-Mode.
Does anyone knows a solution? Will Lenovo update the BIOS?
kr,
Bernd Hollermann, GermanyI have to update my problem:
booting in gpt/uefi-mode is impossible from usb-key, but is ok from DVD. I managed to install Ubuntu now, everything runs well, after I took a 64-bit version on a dvd. -
"Arch By Hand" UEFI GPT SSD LUKS Install Script
Arch UEFI GPT LUKS (and non LUKS version) Automated Install Example Script, SSD friendly
Please note that if you're going to use this you're going to have to a) customize it to fit your needs and b) know what system config you need to do post install (rc.* etc). It's a jumping off point.
Want to put in a lot of effort just to get Arch Linux listed in your "bios" startup options? You're in the right post! Well, it's more than just that, of course. If you have an EFI machine, increasingly common, this might be of interest.
I got this working on my x220 tablet and thought I'd post it here. I imagine that as Archboot and the official installer rev we'll see them support this kind of thing as well, so BBS seemed like a good place to post it, but if there is an appropriate wiki location I could add it there as well.
This is pretty bare bones (otherwise you'd be using AIF or Archboot, natch) and should be customized for your own install purposes. Nonetheless, I suspect others may have been banging their heads on the low overhang of UEFI/GPT install and hope this helps them get up and running.
This is pretty much all in the wiki and BBS in various places, particularly the GRUB2 wiki entry. However the GPT partitioning (and learning more of sgdisk) were challenging enough that I felt it would be useful for others to see a working script.
I used the current-as-of-this-post Archboot iso (archlinux-2011.10-1-archboot.iso).
Don't just dd the archlinux iso to a usb. Format the USB stick as an MBR FAT drive and dump the entire Archboot ISO contents to it. To be honest, I did this in an Ubuntu vmware image I had on my mac, though I'd like to include command line options for doing this. TODO!
I also stuck the script (included herein) on the drive, but you could get it on the installation image at install time as well via scp or whatever you prefer.
On my x220 I then set the UEFI "BIOS" (the UEFI setup) to boot *ONLY* from UEFI. Pretty important. You should probably also stack your USB drive to top of your startup list or manually select it at boot time.
Boot from the USB stick. For my x220 I selected the second of the four efi grub options, x86_64.
Once Archboot is up, immediately leave the installer (option 8)
You may want to mount the usb drive to /src if you stuck this script on it. Archboot in UEFI mode doesn't seem to mount the usb drive properly (and the normal Archboot efi install will fail as well due to this). I think this is getting fixed in the next Archboot release, from what I've read on BBS.
# mount /dev/sdb1 /src
Run the script. For me this is
# /src/myarch.sh
(WARNING: will nuke everything on /dev/sda unless you've changed it).
There are probably things that could be done better/cleaner, feel free to point those out. This is really just a jumping off point.
UPDATE 15 NOV 2011: This now sources most packages locally to avoid kernel mismatch between install medium and install target.
UPDATE 16 NOV 2011: Script now unified the boot and efi partitions.
UPDATE 17 NOV 2011: Migrated code to github, including two versions (non-encrypted and LUKS-encrypted)
UPDATE 18 NOV 2011: Added encrypted swap
UPDATE 18 NOV 2011: Changed /boot/efi/grub to /boot/grub; removed extraneous /boot/efi directory entirely.
UPDATE 19 NOV 2011: Added a post-install script to handle user setup, etc. No reboot required.
UPDATE 20 NOV 2011: Post install section more complete, visudo automation added.
See code at: https://github.com/altercation/arch-by-hand
Last edited by altercation (2011-11-20 21:09:33)I've come up with this script (although it's not quite right either):
#!/bin/bash
# prereqs:
# mount /dev/sdb1 /src
set -o nounset
#set -o errexit
INSTALL_TARGET="/mnt"
HR="--------------------------------------------------------------------------------"
# Initialize
# Warn
timer=9
echo -n "This procedure will completely format /dev/sda. Please cancel with ctrl-c to cancel within $timer seconds..."
while [[ $timer -gt 0 ]]
do
sleep 1
let timer-=1
echo -en "$timer seconds..."
done
echo "Starting"
# Configure_Host
echo -e "\nFormatting disk...\n$HR"
# disk prep
sgdisk -Z /dev/sda # zap all on disk
sgdisk -a 2048 -o /dev/sda # new gpt disk 2048 alignment
# create partitions
sgdisk -n 1:0:+250M /dev/sda # partition 1 (UEFI BOOT), default start block, 250MB
sgdisk -n 2:0:+2G /dev/sda # partition 2 (SWAP), default start block, 2G
sgdisk -n 3:0:+100M /dev/sda # partition3, (BOOT), boot partition
sgdisk -n 4:0:+10G /dev/sda # partition 4, (ARCH), default start, remaining space
sgdisk -n 5:0:0 /dev/sda # partition 5, (HOME)
# set partition types
sgdisk -t 1:ef00 /dev/sda
sgdisk -t 2:8200 /dev/sda
sgdisk -t 3:8300 /dev/sda
sgdisk -t 4:8300 /dev/sda
sgdisk -t 5:8300 /dev/sda
# label partitions
sgdisk -c 1:"UEFI BOOT" /dev/sda
sgdisk -c 2:"SWAP" /dev/sda
sgdisk -c 3:"BOOT" /dev/sda
sgdisk -c 4:"ARCH" /dev/sda
sgdisk -c 5:"HOME" /dev/sda
# make filesystems
echo -e "\nCreating Filesystems...\n$HR"
mkfs.vfat /dev/sda1
mkswap /dev/sda2
mkfs.ext2 /dev/sda3
mkfs.ext4 /dev/sda4
mkfs.ext4 /dev/sda5
# Run /arch/setup
echo -n "Don't select Grub as your bootloader and exit setup before the Install Bootloader step"
/arch/setup
# unmount filesytems
umount /dev/sda1
swapoff /dev/sda2
umount /dev/sda3
umount /dev/sda5
# Get Network
echo -n "Waiting for network address.."
#dhclient eth0
dhcpcd -p eth0
echo -n "Network address acquired."
# Update Pacman
echo -e "\nUpdating pacman...\n$HR"
sed -i "s/^#S/S/" /etc/pacman.d/mirrorlist
pacman --noconfirm -Sy
pacman --noconfirm --needed -S pacman
pacman --noconfirm -S gptfdisk btrfs-progs-unstable
# Prepare to chroot to target
mv ${INSTALL_TARGET}/etc/resolv.conf ${INSTALL_TARGET}/etc/resolv.conf.orig
cp /etc/resolv.conf ${INSTALL_TARGET}/etc/resolv.conf
sed -i "s/^#S/S/" ${INSTALL_TARGET}/etc/pacman.d/mirrorlist
mount -t proc proc ${INSTALL_TARGET}/proc
mount -t sysfs sys ${INSTALL_TARGET}/sys
mount -o bind /dev ${INSTALL_TARGET}/dev
echo -e "${HR}\nINSTALL BASE COMPLETE\n${HR}"
# Write Files
# install_efi (to be run *after* chroot /install)
touch ${INSTALL_TARGET}/install_efi
chmod a+x ${INSTALL_TARGET}/install_efi
cat > ${INSTALL_TARGET}/install_efi <<EFIEOF
mount /boot
mount /boot/efi
modprobe efivars
modprobe dm-mod
pacman --noconfirm -Sy
pacman --noconfirm --needed -S pacman
pacman --noconfirm -R grub
pacman --noconfirm -S grub2-efi-i386
grub_efi_i386-install --root-directory=/boot/efi --boot-directory=/boot/efi/efi --bootloader-id=grub --no-floppy --recheck
efibootmgr --create --gpt --disk /dev/sda --part 1 --write-signature --label "ARCH LINUX" --loader "\\EFI\\grub\\grub.efi"
grub-mkconfig -o /boot/efi/efi/grub/grub.cfg
exit
EFIEOF
# Install EFI
chroot /install /install_efi
rm /install/install_efi -
Windows 8 BIOS vs. UEFI Deploy
Running ConfigMgr 2012 SP1 with MDT 2012 R1.
Is it necessary to create a Build & Capture on a BIOS machine if UEFI exists in the network? Or should the Build & Capture be done on a UEFI machine?
The B&C TS makes provisions for both UEFI and BIOS when it Formats & Partitions. But if we do a B&C on a UEFI machine, will we be able to deploy that to a BIOS machine? And the reverse - if we B&C on a BIOS machine, will we be able to deploy
that to a UEFI machine?
Do we need to create 2 B&C images, with 2 TS' to deploy based on BIOS vs. UEFI?
ThanksAdditionally, if you want to use Windows 8 Recovery Options you need at least
- 3 partitions for Windows 8 on a BIOS machine
- 5 partitions for Windows 8 on a UEFI machine
See also How to Configure BIOS/MBR-Based Hard Drive Partitions and
How to Configure UEFI/GPT-Based Hard Drive Partitions
If you want to do so there is a little challenge in shrinking the last (OS) partition for using the new space as a Recovery Partition. Why?
Because SCCM can't shrink.
A way that worked great for me is to add a "Run Command Line" Step after the "Partition Disk" Step where you do the shrinking. So create a package for this without a program where you place a text file, for instance ShrinkSystemDisk.txt
with the following content for
BIOS
select volume c
shrink minimum=15360
create partition primary
format quick fs=ntfs label="Recovery image"
assign letter="R"
set id=27
list volume
exit
UEFI
select volume c
shrink minimum=15360
create partition primary
format quick fs=ntfs label="Recovery image"
assign letter="R"
set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
gpt attributes=0x8000000000000001
list volume
exit
In the Command Line Step just call "diskpart /s ShrinkSystemDisk.txt" and add the package. -
Converting my system to uefi/gpt boot running arch and win7
Hello. I've recently purchased a new hard drive, and now I need to reorganize my partition scheme. I have a UEFI motherboard, so I'm going to go full uefi/gpt for booting and partitioning. I've done my research this morning, and I believe I know what I need to do. I just want to run it by the forum to see if there's something I am overlooking.
I have one 250gb sata hdd and one 3TB sata hdd. The 250 hdd with have one fat32 UEFI partition for booting and the rest will be an ext4 partition for Arch. The 3TB hdd will have a 250gb NTFS partition for Win7, 250gb free space for experimentation, and the rest will be a large NTFS data partition.
The 250gb hdd currently has an arch and a windows install on MBR partitions and is booting legacy style. I intend to use dd to overwrite the first sector, so that no bootcode remains in the ProtectiveMBR that may confuse my firmware into trying to load. I'll then partition/format the UEFI Fat32 partition and the Arch ext4 partition.
The 3tb hdd is already GPT and has never had an MBR written on it, so I'll simply need to re partition and format it. 250gb NTFS partition for Windows, 250gb free, 2.5tb NTFS data. I'll install Windows first so that I don't have to setup GRUB twice. And this is what concerns me. When I install Windows, it's not going to have a UEFI partition available to it on the drive it's being installed to. I'm concerned it might 'go rogue' and write bootcode to the ProtectiveMBR for one of those hybird BIOS-GPT boots. Or will it see the UEFI partition on the other disc and write its thing there? That would be fine, since I'll overwrite that when I install arch.
Naturally after that I'll install Arch , setup grub on the uefi partition, and hopefully all is well. Again my only concern is what if the windows install writes bootcode to the protectivembr and then I still end up booting strait to windows. I suppose in that case I could just overwrite the first sector with 0's again.
Anyway, I just wanted to see if I'm overlooking anything or if I'm just being paranoid. I only just learned about UEFI, so my understanding of it is still a bit fuzzy.Which windows do you have?
If windows installation starts first, you'll be able to correct its doing, to suite Arch booting mode. However in the ESP you may have any kind of boot loader / manager you'll like.
Later Grub will guide to the windows boot loader and then your done.
The only problem for certain version of windows is the kind of the partition. E.g. Vista doesn't accept logical partition. AFAIK.
I have MBR and UEFI on my USB HD. I presume they can coexist, it's just a matter of bus, USB or SATA, internal or external doesn't matter. -
Z77A-GD65 Cannot boot from Bios A
Hi,
I was fine for years until about two weeks ago, when PC sometimes didn't boot up (no VGA signal, keyboard dead). I fixed the situation by trying to turn it on/off again few times and then it worked. Few days it was OK, and then it happened again. Fixed by the same way. Today, it happened again and I wasn't able to fix it.
I checked LED error code and it was cycling about 5 codes like 49,55,4F, .. (see the attachment). I tried to check/remove all components with no success. I also tried CMOS clearing (connect pins, battery out), but still nothing.
At the end, I tried to switch to Bios B and PC booted without any problem. I updated Bios B to the latest version and now I am fine. It also looks that problem is fixed.
But what is wrong with Bios A? I want to fix it and use it, but I don't know how. I tried to update the bios with Msi forum hq usb flashing tool (booted from Bios B and then switched to Bios A before flashing), but it is still dead.
Thanks a lot for your help.I also had some sort of same problem (Bios A not booting, bios B OK)
BUT remember one thing: that bios switch is not really hardware. To really switch between bioses you must unplug power cord, wait for capacitor to discharge and then flip the switch.
So the sollution for you (that worked for me twice) is: clear CMOS (search forum for detailed method). Switch to BIOS B, Make bootable USB with BIOS version 10.5 (A5) (because this version REALLY works with option to flash the other BIOS). Update (or just downgrade to BIOS 10.5) and then clear CMOS with powercord out and battery out. Boot from bios B and within bios flash BIOS A from BIOS B. You will have same version on both Bioses. After that switch to BIOS A (again after clear CMOS etc...) and now you just can upgrade to which bios version you want using the USB bootable stick.
I now have BIOS A with version 10.11 (AB) and BIOS B with 10.5 (A5) just to restore BIOS A in case of failure.
First time when I did this was because mobo failed to boot and can't save OC profiles. Second time was (probably) because of many OC testing. -
Is there a way to go from BIOS - Splash Screen - Usable Desktop?
I am using XFCE4. I have followed the instructions for silent boot as per the wiki, and am getting only two text outputs. The first is the "Booting Arch Linux" message and the second is the automatic login notification. I would like to first get rid of the login message, if possible. The second goal is to go from BIOS to a splash screen to the desktop with nothing else being displayed at any point. Is this possible to accomplish? If yes, then how?
If you start X from a bashrc/profile with autologin to the tty then I don't know if you can do this. You could, instead, set up a graphical target.
But if you want a splash screen, that would be plymouth:
https://wiki.archlinux.org/index.php/Plymouth -
Error: Read failure when running any of self diagnostisc tests from BIOS
After Screen replacement my HP625 Laptop seems to work good as ever, but if running any of diagnostic test from BIOS (Memory, Start Up, Run In or Hard Drive Test) it throws the same Error: Read failure?!?
Should I be worried?
is is something wrong with testing software?
kind regardsHi Arturb,
Your HP 625 is a commercial product and to get your issue more exposure I would suggest posting in the commercial forums. Here is a link to the Commercial Notebook forum.
Thank you,
Please click “Accept as Solution ” if you feel my post solved your issue.
Click the “Kudos Thumbs Up" on the right to say “Thanks” for helping!
Thank you,
BHK6
I work on behalf of HP -
Why do i get an error from bios for my sata dvd recorder?
Hi!
I have updated my bois to the latest 1.70 version for my K9N Neo 1.0 motherboard and get an error from bios that the S.M.A.R.T drives dont work and that i cant be read from my Sata DVD recorder?
I have a samsung lightscribe 18X dvd recorder and it was no problem until i updated the bios. I have tryed to turn off s.m.a.r.t drives checkup but i still get the error.
What can i do to stop bios from the error? now i have turn my bios to "no errors" so i dont have to clickon F1 every time i start och restart my computer.
im using:
XP PRO 32Bit
AMD AM2 4200+
2048 MB Corsair 800Mhz Ram
2 x WD 250 GB Sata II 8 MB
1 x Samsung dvd lightscribe recorder
K9N Neo motherboard with 1.70 v Bios ( updated today)
//VargTassQuote from: vargtass on 20-June-07, 22:51:54
Hard Disk : S.M.A.R.T Status BAD, Backup and Replace
//VargTass
Quote from: BOSSKILLER on 20-June-07, 19:39:17
so if you disable SMART & reported errors can your Sata DVD works normal?
Maybe you are looking for
-
Fields missing in Update rules
I am creating snap shot DSO for inventory management and after that i created the update rules for it linking it to the info source 2LIS_03_BX. When i do this i am missing the info objects that i created to include in the DSO. How do i solve this iss
-
No sound of any kind after ios8 update
Recently I updated my iPad to iOS 8 and the subsequent updates. Since then there has been no sound at all. When I start music, the playlist will skip through all the songs, eventually crashing. When I start apps they don't work or don't have any soun
-
Recovered video files that won't play!
I have recently used a thrid party software to recover deleted video files from an external hard drive. The recovered files will now no longer play in quicktime, any suggestions on how to fix this?
-
Change payment status for COD order only
Hi, I know that if I click on the edit button within any order, I can click a button to the right of the Status and a window pops up listing the status types. If I click on "Purchase - Awaiting Payment", I can make that the default status type howeve
-
Hi Experts, I want to implement CFM Module in BI 7. Can anyone tell me what standard reports are provided by SAP and i need some document where i can find what all sub modules are to be implemented under CFM. Thanks in adv. Bhavna.