Native boot windows 7 ultimate on VHDX

Hi
I have been searching around for this but there's seems to be no answer and so I hope Microsoft tech support can help me answer this.
I have a PC which I want to dual boot windows 7 Ultimate and windows 8.1 Professional, both on vhdx.
First I installed windows 7 ultimate onto a VHD and it is able to boot natively.
I then install windows 8.1 professional onto a VHDX and now it can dual boot both win7 and win8.1 natively (vhd and vhdx respectively) with win8 boot menu.
Then I boot into win7 and installed kb980218 (to support 4096 disk), and converted the image from vhd to vhdx and set the physicalsize to 4096.
Next the boot entry has been amended and point to this new win7 vhdx.
However when I try to boot into this new win7 vhdx, it doesn't boot up and instead goes into recovery mode, the error is "boot configuration is corrupt" when trying to repair it. FYI, booting into win8 vhdx still works fine.
My question is given the system partition boot environment is windows 8.1 as in this case (requirement of native boot), can you natively boot windows 7 in vhdx????? If so how to make this work? (there should be no difference to the guest OS whether
its' a vhd or vhdx and so given the boot environment is windows 8, my guess is it should work)
And if not, can windows 7 install in vhdx and run inside a virtual machine (e.g., with Host OS as windows 8)
Thank you.
John

>If so how to make this work? (there should be no difference to the guest OS whether its' a vhd or vhdx and so given the boot environment is windows 8, my guess is it should work)
I've never tried this and not likely to, but the base OS definitely needs
to know how to access a VHDX and since Windows 7 predates VHDX, I suspect
it can't be done. 
Once the Windows 8 boot loader passes the running off to Windows 7, it's
got to have a driver to access the disk, and it doesn't.
It's basically the same problem as trying to dual boot Windows XP in a
VHD...
Bob Comer Microsoft MVP -- Hyper-V

Similar Messages

  • SCCM's OSD (not MDT): Task sequence can be tweaked into imaging Windows+VHD Native Boot, but can it go all the way and deploy?

    Hello All,
    What I am trying to do is use SCCM's own OSD Task Sequence / Windows PE to deploy an operating system that boots using VHD Native Boot. (C:\ = VHD File  with Windows, D:\ Data drive with BCDBoot).
    MDT 2013 Can do it I've been told, but I am putting off MDT until Windows 10 if I can get away with it.
    TechNet VHD Native Boot on Windows 8.1:
    http://technet.microsoft.com/en-us/library/hh825689.aspx
    http://technet.microsoft.com/en-us/library/hh825691.aspx
    The good news is it is working up to the "Apply Operating System" phase, but that apply operating system phase is reported as an error even though it completes successfully. It can't clean up the SMSTS folder it's looking for on the C:\ because
    it's been moved over to the D:\ by a diskpart script. We are left with the deployment working but requiring IT staff to deal with the OOBE Personalization wizard and adding each PC to the domain manually. From that point on the SCCM client can do the rest,
    which works for US before we upgrade to Windows 10 with utilizing MDT.
    I am not talking about deploying an OS to a VHD file and putting that file on a network share i.e.
    http://blogs.technet.com/b/configurationmgr/archive/2013/10/31/new-in-system-center-2012-r2-configuration-manager-deploying-an-operating-system-to-a-virtual-hard-drive-vhd.aspx
    I reported getting the diskpart script working first here:
    https://social.technet.microsoft.com/Forums/en-US/ff124f09-1d2e-4fc4-a5b6-63b683f3d208/native-vhd-boot-deployments-from-sccm-2012-r2?forum=configmanagerosd
    Here it is:
    rem work around any USB disk left in or any CDROM detected by PE as drive D
    select volume D
    assign letter=F noerr
    rem select the formatted volume and reassign it's drive letter
    select volume C
    assign letter=D
    rem create and setup VHD file
    create vdisk file=D:\DEV_WIN81.VHD maximum=250000 type=expandable
    select vdisk file=D:\DEV_WIN81.VHD
    attach vdisk
    create partition primary
    active
    format FS=NTFS quick label="Developer Win81 VHD"
    assign letter=C
    rescan
    exit
    (type=fixed is better for performance - we'll surely activate when we have dual boot 8.1 / Windows 10 later for the Win10 VHD's)
    The Task Sequence looks like this:
    I'd like to add a few more steps after apply operating system if I can, but I have to resolve this error with "Apply Operating system before I can go further."
    Question:
    Can an OSD guru tell me if there are any Task Sequence Variables we could throw at this to make the Apply Operating System sequence complete without error so we can do all SCCM OSD Deployment steps?
    If we can, then someone (not me) gets to add a new TechNet blog post about this being possible. It's my understanding presently that only MDT can support deploying WIM files into VHDs on Workstations, that boot them.
    The install image was created using dism to convert a VHD from a Hyper-V host into a wim. I know I'm meant to use SCCM to capture it, but I don't think that's causing this problem because when we are deploying from that image to a HDD without VHD we don't
    get any issues.
    I'm only allowed enough characters to paste the tail end of the apply operating system phase only:
    <![LOG[Execution engine result code: Success (0)]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:929">
    <![LOG[Cleaning Up.]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:675">
    <![LOG[Removing Authenticator]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:686">
    <![LOG[shKey.DeleteValue( c_szRegValue_SecurityToken ), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\ccmutillib\ccmutillib.cpp,1660)]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="ccmutillib.cpp:1660">
    <![LOG[Cleaning up task sequence folder]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:2329">
    <![LOG[Unable to delete file C:\_SMSTaskSequence\TSEnv.dat (0x80070005). Continuing.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="ccmfile.cpp:1056">
    <![LOG[hr, HRESULT=80070091 (e:\nts_sccm_release\sms\framework\core\ccmcore\ccmfile.cpp,1218)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="ccmfile.cpp:1218">
    <![LOG[Failed to delete directory 'C:\_SMSTaskSequence']LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="ccmfile.cpp:1218">
    <![LOG[(dwRet = ::SetNamedSecurityInfoW ((WCHAR*) pszObjectName, objectType, OWNER_SECURITY_INFORMATION, pOwnerSID, NULL, NULL, NULL)) == ERROR_SUCCESS, HRESULT=80070005 (e:\qfe\nts\sms\framework\tscore\utils.cpp,6675)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="utils.cpp:6675">
    <![LOG[SetNamedSecurityInfo() failed.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="3" thread="960" file="utils.cpp:6675">
    <![LOG[SetObjectOwner() failed. 0x80070005.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="3" thread="960" file="utils.cpp:6687">
    <![LOG[SetObjectOwner (szFName, SE_FILE_OBJECT, c_szAdministrators), HRESULT=80070005 (e:\qfe\nts\sms\framework\tscore\utils.cpp,6772)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="utils.cpp:6772">
    <![LOG[RemoveFile() failed for C:\_SMSTaskSequence\TSEnv.dat. 0x80070005.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="3" thread="960" file="utils.cpp:6816">
    <![LOG[RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequence]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="utils.cpp:6900">
    <![LOG[Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ...]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="resolvesource.cpp:506">
    <![LOG[DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\resolvesource.cpp,508)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="resolvesource.cpp:508">
    <![LOG[Deleting volume ID file D:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ...]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="resolvesource.cpp:506">
    <![LOG[DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\resolvesource.cpp,508)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="resolvesource.cpp:508">
    <![LOG[Successfully unregistered Task Sequencing Environment COM Interface.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="environmentlib.cpp:910">
    <![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="commandline.cpp:228">
    <![LOG[Set command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="commandline.cpp:731">
    <![LOG[Executing command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="commandline.cpp:827">
    <![LOG[==========[ TsProgressUI started in process 8012 ]==========]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:330">
    <![LOG[Command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="0" thread="8040" file="winmain.cpp:332">
    <![LOG[Unregistering COM classes]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:204">
    <![LOG[Unregistering class objects]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:495">
    <![LOG[Shutdown complete.]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:512">
    <![LOG[Process completed with exit code 0]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="commandline.cpp:1123">
    <![LOG[Successfully unregistered TS Progress UI.]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:2903">
    <![LOG[Sending success status message]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:784">
    <![LOG[MP server http://OUR-SCCM.ourcompany.com. Ports 80,443. CRL=false.]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:5881">
    <![LOG[Setting authenticator]LOG]!><time="18:29:37.785-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:5903">
    <![LOG[Set authenticator in transport]LOG]!><time="18:29:37.785-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:7734">
    <![LOG[Sending StatusMessage]LOG]!><time="18:29:37.785-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="libsmsmessaging.cpp:4023">
    <![LOG[Setting message signatures.]LOG]!><time="18:29:37.801-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:1295">
    <![LOG[Setting the authenticator.]LOG]!><time="18:29:37.801-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:1325">
    <![LOG[CLibSMSMessageWinHttpTransport::Send: URL: OUR-SCCM.ourcompany.com:80 CCM_POST /ccm_system/request]LOG]!><time="18:29:37.801-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="libsmsmessaging.cpp:8604">
    <![LOG[Request was successful.]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:8939">
    <![LOG[::RegQueryValueExW(hSubKey, szReg, NULL, NULL, NULL, &dwSize), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\utils.cpp,811)]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="utils.cpp:811">
    <![LOG[RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="utils.cpp:811">
    <![LOG[GetTsRegValue() is unsuccessful. 0x80070002.]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="utils.cpp:842">
    <![LOG[End program: ]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:805">
    <![LOG[Finalize logging request ignored from process 856]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tslogging.cpp:1737">
    <![LOG[Process completed with exit code 0]LOG]!><time="18:29:37.863-420" date="12-26-2014" component="TSPxe" context="" type="1" thread="592" file="commandline.cpp:1123">
    <![LOG[Task Sequence Manager returned code 0x00000000]LOG]!><time="18:29:37.863-420" date="12-26-2014" component="TSPxe" context="" type="1" thread="592" file="tsmediawizardcontrol.cpp:2180">
    <![LOG[Exiting with return code 0x00000000]LOG]!><time="18:29:37.863-420" date="12-26-2014" component="TSPxe" context="" type="1" thread="592" file="tsmbootstrap.cpp:1238">
    <![LOG[Execution complete.]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="bootshell.cpp:693">
    <![LOG[hMap != 0, HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentscope.cpp,493)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="environmentscope.cpp:493">
    <![LOG[m_pGlobalScope->open(), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentlib.cpp,335)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="environmentlib.cpp:335">
    <![LOG[this->open(), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentlib.cpp,553)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="environmentlib.cpp:553">
    <![LOG[::RegQueryValueExW(hSubKey, szReg, NULL, NULL, NULL, &dwSize), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\utils.cpp,811)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="utils.cpp:811">
    <![LOG[RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="2" thread="760" file="utils.cpp:811">
    <![LOG[GetTsRegValue() is unsuccessful. 0x80070002.]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="2" thread="760" file="utils.cpp:842">
    <![LOG[End program: ]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="bootshell.cpp:725">
    <![LOG[Finalizing logging from process 752]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="tslogging.cpp:1741">
    <![LOG[Finalizing logs to root of first available drive]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="tslogging.cpp:1583">
    <![LOG[Successfully finalized logs to D:\SMSTSLog]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="tslogging.cpp:1640">
    <![LOG[Cleaning up task sequencing logging configuration.]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="tslogging.cpp:584">
    MCSE,MCNE,SCO,Sair Linux/GNU, Open source-enthusiast.

    I have already set it to FALSE. The solution to this will be some different OSD Task Sequence variables or a statement that it can't be made to work.
    I believe that setting defines what volume will be the BOOT / OS Drive Letter. Some people were getting D:\WINDOWS as their boot volume drive letter. Setting to true means whatever was the System Drive letter (usually C) in the image will remain as such
    after it was was applied, setting it to false will make the system have the same drive letter arrangement as what Windows PE detects. In my case I set it to false so that no matter what the new VHD file setup as drive C will be the system drive. I'll set it
    to true on the next deployment but I expect there to be no difference, because in both PE and the WIM the installation volume is the C:.
    We are talking about the DRIVE LETTERS Windows PE SCCM OSD is using for it's temporary files - and how we can manipulate these locations using OSD Task Sequence Variables, so the Apply OS doesn't try and clean up files that are not there
    - and fail with an error if you have added a VHD Native Boot volume.
    This OSDPreserveDriveLetter setting isn't having any effect on the problem here.
    I believe that Format step is setting some task variables used by the OSD Deployment process - telling it where to store it's temporary files. However between the Format Disks and Apply operating system steps the OSD Task Sequence isn't picking up on the
    fact what was the C:\ after Format HDD step is now the D:\ .
    A developer who has an understanding of how the OSD boot process executes in order would be able to see what's going on here.
    MCSE,MCNE,SCO,Sair Linux/GNU, Open source-enthusiast.

  • Installing the Windows IoT insider preview on SD card when booting Windows 10 from VHD Native Boot

    The setup instructions for the raspberry pi 2 mention that "you
    will need to follow these instructions on a physical Windows machine (and not a VM) because you need access to the SD card reader."
    Will this work if you boot Windows 10 natively from a VHD (like
    this) or does the virtualization still get in the way?

    If you insert the SD card and can see it in explorer or when you perform the diskpart command to list drives, then it should work, since in effect the VHD is the native OS at that point.  If you don't see the card, then you'll have to perform a local
    install.
    Jonathan Tanner | Microsoft | Windows 10 IoT Core Insider Preview Support | This posting is provided 'as is' with no warranties and confers no rights.

  • Viewsonic VX900 DVI boots Windows XP (via bootcamp) but not native OS X

    I'm trying to get the DVI bootup to work correctly with my Mac Mini Core Duo. I'm using a VX900 LCD. When I reboot it goes to XP (bootcamp) and runs perfectly. But when I hold down the option key (to select OS X) I get a black screen and the 'no sync' message on the LCD.
    It seems that the bootup is happening since after a while the boot times out and I wind up booting Windows XP again. I just can't see the bootcamp selection screen.

    I would try getting another monitor and configuring the mini to boot into OS X as the default. Then get a VNC client/server connection going with another computer on the network. Finally, reconnect to the Viewsonic and let the mini boot into OS X making sure you have set the VNC server as a startup item on the mini. That's the only way you will have any visibility into what resolution the mini is starting up in when connected to the Viewsonic.
    Have you tried connecting to the Viewsonic over VGA? Does that make any difference? That might be an alternative. If it works over VGA, you could just stick with VGA.

  • Advice on dual-booting Windows 7 with UEFI motherboard

    I'm going to build a desktop PC tomorrow, having finally purchased all the parts for it. I'll be installing Arch as my main OS, and Windows for gaming. However I'm not really versed in UEFI and its uses, advantages/disadvantages; since my laptop just uses BIOS.
    My plan is to have 3 drives: 32GB SSD for the / partition, 1TB HDD for /home, and 500GB for Windows 7 x64 Ultimate.
    Being unused to UEFI I was thinking about trying to just run everything in BIOS/Legacy mode, but that doesn't seem very sensible to me, especially since I have the hardware so I might as well use it.
    So, reading the wiki and forums have led me to conclude that having a 1GB EFI System Partition on the SSD should be sufficient, and use gummiboot for my bootloader.
    Other reading about setting up dual boots suggests to me that installing Windows 7 on its own HDD with MBR partitioning and Arch on a separate (set of) drive(s) with GPT partitioning will be sufficient. The reason being that if the BIOS is set up to boot sda, which has GRUB as its bootloader, using GRUB I can choose to boot into Windows despite it being on a separate hard drive.
    My questions are (and it occurs to me that I am in the most part just looking to have my ideas confirmed):
    1. Have I gotten this all completely wrong?
    2. If I'm correct, can the above system of using GRUB on one drive to boot up an OS on another drive be applied to UEFI?
    3. Has anybody tried/succeeded/failed to dual-boot in this fashion before me, and if so what did they do?
    Thanks one and all! Hopefully I've made myself clear enough here

    billodwyer wrote:Being unused to UEFI I was thinking about trying to just run everything in BIOS/Legacy mode, but that doesn't seem very sensible to me, especially since I have the hardware so I might as well use it.
    Using BIOS/CSM/legacy mode can work fine; however, it will probably slow down the boot process by a few seconds, and it will close off some possible future (and even current) advantages, as EFI support in Linux is improved.
    So, reading the wiki and forums have led me to conclude that having a 1GB EFI System Partition on the SSD should be sufficient, and use gummiboot for my bootloader.
    A 1GB ESP is more than sufficient. In terms of space requirements, 100-500MB is enough, depending on how you use the ESP; but various bugs and default settings make me recommend 550MiB as a good size. Bigger is OK, but wastes some disk space.
    A bigger issue is that the ESP won't really benefit much from being on your SSD, since it's read once at boot time. The biggest advantage to putting the ESP on the SSD in your setup is that if you use gummiboot, you'll also have to put the Linux kernel and initrd file on the ESP, so having them on an SSD will speed up the boot process by about 1-5 seconds. Overall, I'd probably put the ESP on one of the spinning disks.
    One more comment: gummiboot can launch boot loaders from its own partition but not from other partitions. This can work fine if you plan things carefully, but with three disks and two OSes, you must be absolutely positive that Windows uses the ESP on which gummiboot is installed. I'm not an expert on Windows installation, so I can't offer any specific pointers or caveats on this. If you need something with more flexibility, both rEFInd and GRUB can redirect the boot process to other partitions or physical disks. rEFInd can also redirect from an EFI-mode boot to a BIOS/CSM/legacy-mode boot. (See below.) Overall, rEFInd's flexibility on this score is a plus compared to gummiboot; but gummiboot is covered in the Arch wiki's beginner's guide, which is a plus. You'll have to pick which advantage you prefer. (Note that I'm rEFInd's maintainer, so I'm not unbiased.)
    Other reading about setting up dual boots suggests to me that installing Windows 7 on its own HDD with MBR partitioning and Arch on a separate (set of) drive(s) with GPT partitioning will be sufficient. The reason being that if the BIOS is set up to boot sda, which has GRUB as its bootloader, using GRUB I can choose to boot into Windows despite it being on a separate hard drive.
    This is an unworkable idea, at least as stated and if you want to do an EFI-mode boot. Windows ties the partition table type to the boot mode: Windows boots from MBR disks only in BIOS mode, and from GPT disks only in EFI mode. Thus, using MBR for the Windows disk will require a BIOS/CSM/legacy-mode installation of Windows. Furthermore, neither gummiboot nor GRUB can redirect from EFI mode to BIOS mode (or vice-versa), so if you do it this way, you'll be forcing yourself to boot Linux in BIOS mode, to switch between BIOS-mode and EFI-mode boots at the firmware level (which isn't always easily controlled), or to use rEFInd to redirect from an EFI-mode boot to a BIOS-mode Windows boot.
    Overall, you're best off either using GPT for all your disks and booting all your OSes in EFI mode or using MBR for Windows (and perhaps all your disks) and using BIOS-mode booting for all your OSes.
    Under EFI, the boot process is controlled by settings in the NVRAM, which you can adjust with "efibootmgr" in Linux, "bcfg" in an EFI shell, or "bcdedit" in Windows. (The Arch wiki covers the basics at least efibootmgr and bcfg.) In a typical dual-boot setup, you tell the computer to launch your preferred boot manager (EFI-mode GRUB, rEFInd, or gummiboot, most commonly), which then controls the boot process. You set up boot loaders for all your OSes on one or more ESPs. (Note: A boot manager lets you choose which boot loader to run, and a boot loader loads the kernel into memory. GRUB is both a boot manager and a boot loader. rEFInd and gummiboot are both boot managers. The EFI stub loader, ELILO, and the EFI version of SYSLINUX are all boot loaders but not boot managers. Most EFIs include their own boot manager, but it's usually primitive and awkward to use. It's also not standardized, so my computer's built-in boot manager is likely to be different from yours. Thus, I recommend against relying on the built-in boot manager for anything but launching your preferred boot manager.) Thus, the lowest-common-denominator type of setup is to put your preferred boot manager, the Windows boot loader, and a Linux boot loader (which could mean your Linux kernel) on a single ESP. If you want to use multiple ESPs or otherwise split things up, you cannot use gummiboot as the boot manager, since it can't redirect the boot process from one partition to another. (Many EFIs can do this with their own built-in boot managers, but this isn't guaranteed, and it's usually more awkward than using rEFInd or GRUB.)
    I know this can be a lot to absorb. The official rules aren't really all that complex, but different EFIs interpret the rules differently, and the different capabilities of the various boot managers and boot loaders creates a lot of subtle implications for how you set everything up.
    1. Have I gotten this all completely wrong?
    Significant parts of it, I'm afraid; see above. You're working under BIOS assumptions, which don't apply to EFI.
    2. If I'm correct, can the above system of using GRUB on one drive to boot up an OS on another drive be applied to UEFI?
    GRUB can do this, but gummiboot can't. You set one of those (or something else, like rEFInd) as your primary boot manager. Using both GRUB and gummiboot adds unnecessary complexity, IMHO. OTOH, setting up multiple boot managers or boot loaders is possible, and can give you a fallback in case one fails. For instance, there's a known bug that affects 3.7 and later kernels, mostly on Lenovo computers, that causes the EFI stub loader to fail sometimes. Thus, if you use rEFInd, gummiboot, or the EFI's own boot manager to launch the kernel via the EFI stub loader, having GRUB, ELILO, or SYSLINUX set up as a fallback can provide helpful insurance in case a kernel upgrade causes your normal boot process to fail.
    3. Has anybody tried/succeeded/failed to dual-boot in this fashion before me, and if so what did they do?
    Many people dual-boot Windows and Linux under EFI. There are a huge number of possible solutions. My own Windows/Linux dual-boot system uses:
    rEFInd
    rEFInd's EFI filesystem drivers
    Linux kernels on Linux-native /boot partitions (two partitions, one for each of the two distributions installed on that computer)
    The Windows boot loader on the ESP
    This works well for me, but it wouldn't work with gummiboot instead of rEFInd, since gummiboot can't redirect the boot process to another partition. (gummiboot also can't automatically load filesystem drivers.) Arch Linux users who use gummiboot often mount the ESP at /boot, which enables gummiboot to easily launch the Linux kernel. Doing this with multiple Linux distributions would be awkward, though, since you'd end up with two distributions' kernels in the same directory.

  • [VHD][BOOT][UEFI] Boot Windows 8 From a VHD Drive On a GPT Disk Using UEFI BIOS

    I had been dual booting two copies of Windows 8 prior to getting a new rig without any issues. Once I installed Windows 8.1 I can no longer boot a VHD from the GPT partitioned drive. 
    My PC specifications 
    Intel i7-4770k
    ASUS SABERTOOTH Z87
    16GB KINGSTON HYPERX BEAST DUAL-DDR3 2400MHz
    2GB NVIDIA GEFORCE GTX 660 Ti 
    120GB INTEL 520 SSD 
    4TB WD CAVIAR BLACK WD2002FAEX
    4TB WD CAVIAR BLACK WD2002FAEX (two way mirror = storage spaces)
    15x BLU-RAY Writer Drive
    CORSAIR 750W PRO HX750-80
    Corsair H60 Hydro Series High Performance CPU Cooler
    10/100/1000 GIGABIT LAN PORT 
    Windows 8.1 Pro x64 
    So I basically copied my existing VHD to the new data drive and created the relevant BCD entry, when I chose to boot from the VHD I am presented with an error saying Windows cannot boot and to choose another OS or the troubleshooting options (I’ll post the
    exact error later as I am at work at the moment). 
    I can boot the VHD inside Hyper-V without any issues, it just wont boot natively. I also created a brand new Windows 8.1 VHD and still the same thing happens. Once I created a new VHD I used “bcdboot j:\windows /s j:” to insert the attached VHD into the BCD
    store. 
    So existing or brand new VHD’s don’t seem to work for me, any advice would be appreciated.   
    Mike Park

    I posted this issue on Neowin and someone kindly pointed out the answer, it's to do with storage spaces: 
    http://www.neowin.net/forum/topic/1191873-native-boot-vhdx-from-second-drive/#entry596152197
    Quote
    What types of drives can I use with Storage Spaces?
    You can use commodity drives attached via Serial-Attached SCSI (SAS), Serial ATA (SATA), or USB. Storage layers that abstract the physical disks are not compatible with Storage Spaces. This includes VHDs and pass-through disks in a virtual machine, and storage
    subsystems that layer a RAID implementation on top of the physical disks. iSCSI and Fibre Channel controllers are not supported by Storage Spaces.
    From: http://social.techne...stions-faq.aspx 
    Mike Park

  • Adding Raid drivers to Windows 8.1 VHDX

    I have a Windows 8.1 VHDX which I used to boot into prior to updating to 8.1. 
    The vhdx file sits on an SSD which is in a raid. 
    After the 8.1 update, I cannot boot into the VHDX. 
    If I move the VHDX to my non-raid drive, it boots fine.
    Looks like the vhdx cannot find the raid drivers while booting, which is suprising cause it booted fine before 8.1
    How do I add RAID drivers to my VHDX, so that I can boot to it.

    If you can boot to it when it is hosted on Hyper-V or the non-RAID drive and the RAID is attached at that point, you can simply install the RAID driver package at that point to provide support for
    the array. If you are booting to VHD natively you can just install the package but if you are doing so through Hyper-V, you will
    have to offline the RAID array in the host OS and attach it directly to the virtual machine. Either way the VHD will need to be located on the non-RAID drive for the operation.
    You can also use the registry setting to enable the RAID driver if it was previously installed and somehow switched back to AHCI, you will need to set the Start key under the driver service (probably iaStorV, but this may vary depending on storage chipset),
    located at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services, to 0 for on (from 3 for off). Check with support for the storage chipset manufacturer if you are unsure about this
    setting.
    Brandon
    Windows Outreach Team- IT Pro
    The Springboard Series on TechNet

  • [SOLVED] Can't boot Windows 8 using grub2. invalid EFI file path

    English is not my native language. Please excuse typing errors.
    I have just successfully installed Arch linux with grub2 as its boot manager. I
    followed the arch beginner guide. I've used grub before and I'm familiar with
    it, so chose to use grub instead for efistub. I installed os-prober and
    ran grub-mkconfig to create the grub.cfg file. The problem now is that I recieve
    an error when I try to boot windows 8. I have two drives (/dev/sda and /dev/sdb)
    and I believe both are EFI-systems.
    However, it's not very important for me to use grub, so if booting into windows
    8 is easier using efistub, I will try that.
    The computer is ASUS ux32vd with a hybrid disk with 25GB on the SSD and 500GB on
    the hard drive. I believe the SSD part is used by Windows.
    This is the first error I recieved when I tried to boot windows.
    error: can't find command `drivemap'.
    error: invalid EFI file path.
    Press any key to continue...
    Then I tried to follow this post
    https://bbs.archlinux.org/viewtopic.php?id=150183 and made a new boot
    entry "Windows 82". And I got a new error:
    error: unspecified search type.
    error: file '/EFI/Microsoft/Boot/bootmgfw.efi' not found
    Press any key to continue...
    Here are some command line outputs.
    ~ ᐅ sudo blkid
    /dev/sdb1: PARTLABEL="HFS" PARTUUID="4613ee39-4727-4347-8134-173f590f716f"
    /dev/sdb2: LABEL="INTELRST" UUID="BA5E-7431" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="304f2630-89b2-4632-a566-e8c6db9df3a9"
    /dev/sda1: LABEL="SYSTEM" UUID="90FA-5332" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="5a60fff2-384a-4168-ad7b-7ba25c03c910"
    /dev/sda2: LABEL="Recovery" UUID="ECE43E9AE43E674C" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="5da02b32-607a-4c63-88ef-00499bd6e05c"
    /dev/sda3: PARTLABEL="Microsoft reserved partition" PARTUUID="6c501a91-71a5-45d8-a9ee-2e2a1c427258"
    /dev/sda4: LABEL="OS" UUID="DE4241E84241C5CD" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="6e182189-b0e3-479a-ac74-8e69452d7c66"
    /dev/sda5: LABEL="DATA" UUID="B05448EC5448B6BE" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="be7e04ac-fb01-44fd-9571-e0b001652322"
    /dev/sda6: LABEL="Restore" UUID="B8D84520D844DDEE" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="4d42c26d-2c85-4ebf-88ec-7a83a4814a61"
    /dev/sda7: LABEL="ROOT" UUID="0d63036d-b624-4596-a296-1db457c068d5" TYPE="ext4" PARTUUID="707f4bca-18b4-4340-838f-ec3a39e9338a"
    /dev/sda8: UUID="bcaa2c5f-150d-47c9-9a58-9a7b7ec7bed2" TYPE="swap" PARTUUID="1da43668-418c-4883-810b-e1c3dee75e61"
    ~ ᐅ sudo lsblk
    NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
    sda 8:0 0 465.8G 0 disk
    ├─sda1 8:1 0 300M 0 part /boot/efi
    ├─sda2 8:2 0 600M 0 part
    ├─sda3 8:3 0 128M 0 part
    ├─sda4 8:4 0 186.3G 0 part /mnt/windows
    ├─sda5 8:5 0 190.1G 0 part /mnt/data
    ├─sda6 8:6 0 20G 0 part
    ├─sda7 8:7 0 66.5G 0 part /
    └─sda8 8:8 0 1.9G 0 part
    sdb 8:16 0 22.4G 0 disk
    ├─sdb1 8:17 0 18.4G 0 part
    └─sdb2 8:18 0 4G 0 part
    ~ ᐅ sudo cat /boot/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
    set default="0"
    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,gpt7'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt7 --hint-efi=hd0,gpt7 --hint-baremetal=ahci0,gpt7 0d63036d-b624-4596-a296-1db457c068d5
    else
    search --no-floppy --fs-uuid --set=root 0d63036d-b624-4596-a296-1db457c068d5
    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
    set timeout=5
    ### END /etc/grub.d/00_header ###
    ### BEGIN /etc/grub.d/10_linux ###
    menuentry 'Arch Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-0d63036d-b624-4596-a296-1db457c068d5' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_gpt
    insmod ext2
    set root='hd0,gpt7'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt7 --hint-efi=hd0,gpt7 --hint-baremetal=ahci0,gpt7 0d63036d-b624-4596-a296-1db457c068d5
    else
    search --no-floppy --fs-uuid --set=root 0d63036d-b624-4596-a296-1db457c068d5
    fi
    echo 'Loading Linux core repo kernel ...'
    linux /boot/vmlinuz-linux root=UUID=0d63036d-b624-4596-a296-1db457c068d5 ro quiet
    echo 'Loading initial ramdisk ...'
    initrd /boot/initramfs-linux.img
    menuentry 'Arch Linux, with Linux core repo kernel (Fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-fallback-0d63036d-b624-4596-a296-1db457c068d5' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_gpt
    insmod ext2
    set root='hd0,gpt7'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt7 --hint-efi=hd0,gpt7 --hint-baremetal=ahci0,gpt7 0d63036d-b624-4596-a296-1db457c068d5
    else
    search --no-floppy --fs-uuid --set=root 0d63036d-b624-4596-a296-1db457c068d5
    fi
    echo 'Loading Linux core repo kernel ...'
    linux /boot/vmlinuz-linux root=UUID=0d63036d-b624-4596-a296-1db457c068d5 ro quiet
    echo 'Loading initial ramdisk ...'
    initrd /boot/initramfs-linux-fallback.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/20_memtest86+ ###
    ### END /etc/grub.d/20_memtest86+ ###
    ### BEGIN /etc/grub.d/30_os-prober ###
    menuentry 'Windows Recovery Environment (loader) (on /dev/sda2)' --class windows --class os $menuentry_id_option 'osprober-chain-ECE43E9AE43E674C' {
    insmod part_gpt
    insmod ntfs
    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 ECE43E9AE43E674C
    else
    search --no-floppy --fs-uuid --set=root ECE43E9AE43E674C
    fi
    drivemap -s (hd0) ${root}
    chainloader +1
    menuentry 'Windows 8 (loader) (on /dev/sda4)' --class windows --class os $menuentry_id_option 'osprober-chain-DE4241E84241C5CD' {
    insmod part_gpt
    insmod ntfs
    set root='hd0,gpt4'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt4 --hint-efi=hd0,gpt4 --hint-baremetal=ahci0,gpt4 DE4241E84241C5CD
    else
    search --no-floppy --fs-uuid --set=root DE4241E84241C5CD
    fi
    drivemap -s (hd0) ${root}
    chainloader +1
    ### 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 8 x86_64 UEFI-GPT NTFS" {
    #insmod part_gpt
    #insmod ntfs
    #insmod search_fs_uuid
    #insmod chain
    #search --fs-uuid --set=root --hint-bios=hd0,gpt4 --hint-efi=hd0,gpt4 --hint-baremetal=ahci0,gpt4 DE4241E84241C5CD
    #chainloader /EFI/Microsoft/Boot/bootmgfw.efi
    menuentry "Windows 8" {
    insmod part_gpt
    insmod fat
    insmod search_fs_uuid
    insmod chain
    search --no-floppy --fs--uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 90FA-5332
    chainloader /EFI/Microsoft/Boot/bootmgfw.efi
    menuentry "Windows 8-2" --class windows --class os $menuentry_id_option 'osprober-chain-ECE43E9AE43E674C' {
    insmod part_gpt
    insmod fat
    insmod search_fs_uuid
    insmod chain
    search --no-floppy --fs--uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 90FA-5332
    chainloader /EFI/Microsoft/Boot/bootmgfw.efi
    ### 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 ###
    ~ ᐅ sudo grub-probe --target=fs_uuid /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi
    90FA-5332
    ~ ᐅ sudo grub-probe --target=hints_string /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi
    --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1
    bootinitscript
    Boot Info Script 0.61 [1 April 2012]
    ============================= Boot Info Summary: ===============================
    => No boot loader is installed in the MBR of /dev/sda.
    => No boot loader is installed in the MBR of /dev/sdb.
    sda1: __________________________________________________________________________
    File system: vfat
    Boot sector type: Unknown
    Boot sector info: No errors found in the Boot Parameter Block.
    Operating System:
    Boot files: /efi/arch-grub/grubx64.efi /efi/Boot/bkpbootx64.efi
    /efi/Boot/bootx64.efi /efi/ubuntu/grubx64.efi
    sda2: __________________________________________________________________________
    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
    sda3: __________________________________________________________________________
    File system:
    Boot sector type: -
    Boot sector info:
    Mounting failed: mount: unknown filesystem type ''
    sda4: __________________________________________________________________________
    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 /Windows/System32/winload.exe
    sda5: __________________________________________________________________________
    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:
    sda6: __________________________________________________________________________
    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:
    sda7: __________________________________________________________________________
    File system: ext4
    Boot sector type: -
    Boot sector info:
    Operating System: Arch Linux ()
    Boot files: /boot/grub/grub.cfg /etc/fstab
    sda8: __________________________________________________________________________
    File system: swap
    Boot sector type: -
    Boot sector info:
    sdb1: __________________________________________________________________________
    File system:
    Boot sector type: -
    Boot sector info:
    Mounting failed: mount: unknown filesystem type ''
    mount: unknown filesystem type ''
    sdb2: __________________________________________________________________________
    File system: vfat
    Boot sector type: Unknown
    Boot sector info: No errors found in the Boot Parameter Block.
    Operating System:
    Boot files:
    ============================ Drive/Partition Info: =============================
    Drive: sda _____________________________________________________________________
    Disk /dev/sda: 500.1 GB, 500107862016 bytes, 976773168 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/sda1 1 976,773,167 976,773,167 ee GPT
    GUID Partition Table detected.
    Partition Start Sector End Sector # of Sectors System
    /dev/sda1 2,048 616,447 614,400 EFI System partition
    /dev/sda2 616,448 1,845,247 1,228,800 Windows Recovery Environment (Windows)
    /dev/sda3 1,845,248 2,107,391 262,144 Microsoft Reserved Partition (Windows)
    /dev/sda4 2,107,392 392,816,639 390,709,248 Data partition (Windows/Linux)
    /dev/sda5 392,816,640 791,449,599 398,632,960 Data partition (Windows/Linux)
    /dev/sda6 934,809,600 976,773,119 41,963,520 Windows Recovery Environment (Windows)
    /dev/sda7 791,449,600 930,902,015 139,452,416 Data partition (Windows/Linux)
    /dev/sda8 930,902,016 934,809,599 3,907,584 Swap partition (Linux)
    Drive: sdb _____________________________________________________________________
    Disk /dev/sdb: 24.0 GB, 24015495168 bytes, 46905264 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/sdb1 1 4,294,967,295 4,294,967,295 ee GPT
    /dev/sdb1 ends after the last sector of /dev/sdb
    GUID Partition Table detected.
    Partition Start Sector End Sector # of Sectors System
    /dev/sdb1 8,392,704 46,903,295 38,510,592 -
    /dev/sdb2 2,048 8,390,655 8,388,608 -
    "blkid" output: ________________________________________________________________
    Device UUID TYPE LABEL
    /dev/sda1 90FA-5332 vfat SYSTEM
    /dev/sda2 ECE43E9AE43E674C ntfs Recovery
    /dev/sda3
    /dev/sda4 DE4241E84241C5CD ntfs OS
    /dev/sda5 B05448EC5448B6BE ntfs DATA
    /dev/sda6 B8D84520D844DDEE ntfs Restore
    /dev/sda7 0d63036d-b624-4596-a296-1db457c068d5 ext4 ROOT
    /dev/sda8 bcaa2c5f-150d-47c9-9a58-9a7b7ec7bed2 swap
    /dev/sdb1
    /dev/sdb2 BA5E-7431 vfat INTELRST
    ================================ Mount points: =================================
    Device Mount_Point Type Options
    /dev/sda1 /boot/efi vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
    /dev/sda4 /mnt/windows fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
    /dev/sda5 /mnt/data fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
    /dev/sda7 / ext4 (rw,relatime,commit=600,data=ordered)
    =========================== sda7/boot/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
    set default="0"
    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,gpt7'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt7 --hint-efi=hd0,gpt7 --hint-baremetal=ahci0,gpt7 0d63036d-b624-4596-a296-1db457c068d5
    else
    search --no-floppy --fs-uuid --set=root 0d63036d-b624-4596-a296-1db457c068d5
    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
    set timeout=5
    ### END /etc/grub.d/00_header ###
    ### BEGIN /etc/grub.d/10_linux ###
    menuentry 'Arch Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-0d63036d-b624-4596-a296-1db457c068d5' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_gpt
    insmod ext2
    set root='hd0,gpt7'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt7 --hint-efi=hd0,gpt7 --hint-baremetal=ahci0,gpt7 0d63036d-b624-4596-a296-1db457c068d5
    else
    search --no-floppy --fs-uuid --set=root 0d63036d-b624-4596-a296-1db457c068d5
    fi
    echo 'Loading Linux core repo kernel ...'
    linux /boot/vmlinuz-linux root=UUID=0d63036d-b624-4596-a296-1db457c068d5 ro quiet
    echo 'Loading initial ramdisk ...'
    initrd /boot/initramfs-linux.img
    menuentry 'Arch Linux, with Linux core repo kernel (Fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-fallback-0d63036d-b624-4596-a296-1db457c068d5' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_gpt
    insmod ext2
    set root='hd0,gpt7'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt7 --hint-efi=hd0,gpt7 --hint-baremetal=ahci0,gpt7 0d63036d-b624-4596-a296-1db457c068d5
    else
    search --no-floppy --fs-uuid --set=root 0d63036d-b624-4596-a296-1db457c068d5
    fi
    echo 'Loading Linux core repo kernel ...'
    linux /boot/vmlinuz-linux root=UUID=0d63036d-b624-4596-a296-1db457c068d5 ro quiet
    echo 'Loading initial ramdisk ...'
    initrd /boot/initramfs-linux-fallback.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/20_memtest86+ ###
    ### END /etc/grub.d/20_memtest86+ ###
    ### BEGIN /etc/grub.d/30_os-prober ###
    menuentry 'Windows Recovery Environment (loader) (on /dev/sda2)' --class windows --class os $menuentry_id_option 'osprober-chain-ECE43E9AE43E674C' {
    insmod part_gpt
    insmod ntfs
    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 ECE43E9AE43E674C
    else
    search --no-floppy --fs-uuid --set=root ECE43E9AE43E674C
    fi
    drivemap -s (hd0) ${root}
    chainloader +1
    menuentry 'Windows 8 (loader) (on /dev/sda4)' --class windows --class os $menuentry_id_option 'osprober-chain-DE4241E84241C5CD' {
    insmod part_gpt
    insmod ntfs
    set root='hd0,gpt4'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt4 --hint-efi=hd0,gpt4 --hint-baremetal=ahci0,gpt4 DE4241E84241C5CD
    else
    search --no-floppy --fs-uuid --set=root DE4241E84241C5CD
    fi
    drivemap -s (hd0) ${root}
    chainloader +1
    ### 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 "Windows 8" {
    insmod part_gpt
    insmod fat
    insmod search_fs_uuid
    insmod chain
    search --no-floppy --fs--uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 90FA-5332
    chainloader /EFI/Microsoft/Boot/bootmgfw.efi
    menuentry 'Windows 82' --class windows --class os $menuentry_id_option 'osprober-chain-ECE43E9AE43E674C' {
    insmod part_gpt
    insmod fat
    insmod search_fs_uuid
    insmod chain
    search --no-floppy --fs--uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 90FA-5332
    chainloader /EFI/Microsoft/Boot/bootmgfw.efi
    ### 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 ###
    =============================== sda7/etc/fstab: ================================
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    # /dev/sda7 LABEL=ROOT
    UUID=0d63036d-b624-4596-a296-1db457c068d5 / ext4 rw,relatime,data=ordered 0 1
    # /dev/sda1 LABEL=SYSTEM
    UUID=90FA-5332 /boot/efi vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
    LABEL=DATA /mnt/data ntfs-3g uid=sighol,gid=users,dmask=022,fmask=133 0 0
    LABEL=OS /mnt/windows ntfs-3g uid=sighol,gid=users,dmask=022,fmask=133 0 0
    =================== sda7: Location of files loaded by Grub: ====================
    GiB - GB File Fragment(s)
    ======================== Unknown MBRs/Boot Sectors/etc: ========================
    Unknown GPT Partiton Type
    5850cbb887c11947baf0379ca2d4c97e
    Unknown GPT Partiton Type
    dee2bfd3af3ddf11ba40e3a556d89593
    Unknown BootLoader on sda1
    00000000 eb 58 90 4d 53 44 4f 53 35 2e 30 00 02 08 5e 1b |.X.MSDOS5.0...^.|
    00000010 02 00 00 00 00 f8 00 00 3f 00 ff 00 00 08 00 00 |........?.......|
    00000020 00 60 09 00 51 02 00 00 00 00 00 00 02 00 00 00 |.`..Q...........|
    00000030 01 00 06 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
    00000040 80 01 29 32 53 fa 90 4e 4f 20 4e 41 4d 45 20 20 |..)2S..NO NAME |
    00000050 20 20 46 41 54 33 32 20 20 20 33 c9 8e d1 bc f4 | FAT32 3.....|
    00000060 7b 8e c1 8e d9 bd 00 7c 88 56 40 88 4e 02 8a 56 |{......|[email protected]|
    00000070 40 b4 41 bb aa 55 cd 13 72 10 81 fb 55 aa 75 0a |@.A..U..r...U.u.|
    00000080 f6 c1 01 74 05 fe 46 02 eb 2d 8a 56 40 b4 08 cd |...t..F..-.V@...|
    00000090 13 73 05 b9 ff ff 8a f1 66 0f b6 c6 40 66 0f b6 |.s......f...@f..|
    000000a0 d1 80 e2 3f f7 e2 86 cd c0 ed 06 41 66 0f b7 c9 |...?.......Af...|
    000000b0 66 f7 e1 66 89 46 f8 83 7e 16 00 75 39 83 7e 2a |f..f.F..~..u9.~*|
    000000c0 00 77 33 66 8b 46 1c 66 83 c0 0c bb 00 80 b9 01 |.w3f.F.f........|
    000000d0 00 e8 2c 00 e9 a8 03 a1 f8 7d 80 c4 7c 8b f0 ac |..,......}..|...|
    000000e0 84 c0 74 17 3c ff 74 09 b4 0e bb 07 00 cd 10 eb |..t.<.t.........|
    000000f0 ee a1 fa 7d eb e4 a1 7d 80 eb df 98 cd 16 cd 19 |...}...}........|
    00000100 66 60 80 7e 02 00 0f 84 20 00 66 6a 00 66 50 06 |f`.~.... .fj.fP.|
    00000110 53 66 68 10 00 01 00 b4 42 8a 56 40 8b f4 cd 13 |Sfh.....B.V@....|
    00000120 66 58 66 58 66 58 66 58 eb 33 66 3b 46 f8 72 03 |fXfXfXfX.3f;F.r.|
    00000130 f9 eb 2a 66 33 d2 66 0f b7 4e 18 66 f7 f1 fe c2 |..*f3.f..N.f....|
    00000140 8a ca 66 8b d0 66 c1 ea 10 f7 76 1a 86 d6 8a 56 |..f..f....v....V|
    00000150 40 8a e8 c0 e4 06 0a cc b8 01 02 cd 13 66 61 0f |@............fa.|
    00000160 82 74 ff 81 c3 00 02 66 40 49 75 94 c3 42 4f 4f |[email protected]|
    00000170 54 4d 47 52 20 20 20 20 00 00 00 00 00 00 00 00 |TMGR ........|
    00000180 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
    000001a0 00 00 00 00 00 00 00 00 00 00 00 00 0d 0a 44 69 |..............Di|
    000001b0 73 6b 20 65 72 72 6f 72 ff 0d 0a 50 72 65 73 73 |sk error...Press|
    000001c0 20 61 6e 79 20 6b 65 79 20 74 6f 20 72 65 73 74 | any key to rest|
    000001d0 61 72 74 0d 0a 00 00 00 00 00 00 00 00 00 00 00 |art.............|
    000001e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
    000001f0 00 00 00 00 00 00 00 00 ac 01 b9 01 00 00 55 aa |..............U.|
    00000200
    Unknown BootLoader on sdb2
    00000000 eb 58 90 4d 53 44 4f 53 35 2e 30 00 02 08 2e 20 |.X.MSDOS5.0.... |
    00000010 02 00 00 00 00 f8 00 00 3f 00 ff 00 00 08 00 00 |........?.......|
    00000020 00 00 80 00 e9 1f 00 00 00 00 00 00 02 00 00 00 |................|
    00000030 01 00 06 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
    00000040 80 00 29 31 74 5e ba 4e 4f 20 4e 41 4d 45 20 20 |..)1t^.NO NAME |
    00000050 20 20 46 41 54 33 32 20 20 20 33 c9 8e d1 bc f4 | FAT32 3.....|
    00000060 7b 8e c1 8e d9 bd 00 7c 88 56 40 88 4e 02 8a 56 |{......|[email protected]|
    00000070 40 b4 41 bb aa 55 cd 13 72 10 81 fb 55 aa 75 0a |@.A..U..r...U.u.|
    00000080 f6 c1 01 74 05 fe 46 02 eb 2d 8a 56 40 b4 08 cd |...t..F..-.V@...|
    00000090 13 73 05 b9 ff ff 8a f1 66 0f b6 c6 40 66 0f b6 |.s......f...@f..|
    000000a0 d1 80 e2 3f f7 e2 86 cd c0 ed 06 41 66 0f b7 c9 |...?.......Af...|
    000000b0 66 f7 e1 66 89 46 f8 83 7e 16 00 75 39 83 7e 2a |f..f.F..~..u9.~*|
    000000c0 00 77 33 66 8b 46 1c 66 83 c0 0c bb 00 80 b9 01 |.w3f.F.f........|
    000000d0 00 e8 2c 00 e9 a8 03 a1 f8 7d 80 c4 7c 8b f0 ac |..,......}..|...|
    000000e0 84 c0 74 17 3c ff 74 09 b4 0e bb 07 00 cd 10 eb |..t.<.t.........|
    000000f0 ee a1 fa 7d eb e4 a1 7d 80 eb df 98 cd 16 cd 19 |...}...}........|
    00000100 66 60 80 7e 02 00 0f 84 20 00 66 6a 00 66 50 06 |f`.~.... .fj.fP.|
    00000110 53 66 68 10 00 01 00 b4 42 8a 56 40 8b f4 cd 13 |Sfh.....B.V@....|
    00000120 66 58 66 58 66 58 66 58 eb 33 66 3b 46 f8 72 03 |fXfXfXfX.3f;F.r.|
    00000130 f9 eb 2a 66 33 d2 66 0f b7 4e 18 66 f7 f1 fe c2 |..*f3.f..N.f....|
    00000140 8a ca 66 8b d0 66 c1 ea 10 f7 76 1a 86 d6 8a 56 |..f..f....v....V|
    00000150 40 8a e8 c0 e4 06 0a cc b8 01 02 cd 13 66 61 0f |@............fa.|
    00000160 82 74 ff 81 c3 00 02 66 40 49 75 94 c3 42 4f 4f |[email protected]|
    00000170 54 4d 47 52 20 20 20 20 00 00 00 00 00 00 00 00 |TMGR ........|
    00000180 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
    000001a0 00 00 00 00 00 00 00 00 00 00 00 00 0d 0a 44 69 |..............Di|
    000001b0 73 6b 20 65 72 72 6f 72 ff 0d 0a 50 72 65 73 73 |sk error...Press|
    000001c0 20 61 6e 79 20 6b 65 79 20 74 6f 20 72 65 73 74 | any key to rest|
    000001d0 61 72 74 0d 0a 00 00 00 00 00 00 00 00 00 00 00 |art.............|
    000001e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
    000001f0 00 00 00 00 00 00 00 00 ac 01 b9 01 00 00 55 aa |..............U.|
    00000200
    ========= Devices which don't seem to have a corresponding hard drive: =========
    sdc {
    =============================== StdErr Messages: ===============================
    cat: /tmp/BootInfo-wSbit3X4/Tmp_Log: No such file or directory
    /dev/sdc: open failed: No medium found
    No volume groups found
    mdadm: No arrays found in config file or automatically
    EDIT:
    I gave up trying to make grub work, so I uninstalled grub and deleted all the grub files I could find.
    # pacrem grub-efi-x86_64
    # rm -fr /boot/grub
    That last one I came to regret later on. So I installed rEFInd using the archlinux beginners guide. When I then tried to boot into windows It told me that /boot/grub/x86_64-efi/normal.mod was not found. I then reinstalled grub-efi-x86_64 and copied /usr/lib/grub/x86_64 to /boot/grub. Now everything works fine.
    Last edited by sighol (2013-06-08 21:47:49)

    sighol wrote:However, it's not very important for me to use grub, so if booting into windows
    8 is easier using efistub, I will try that.
    The EFI stub loader is a Linux-only boot loader; however, it is possible to use the EFI stub loader in conjunction with a separate boot manager, such as rEFInd or gummiboot. In such a configuration, you'd use the boot manager to select the OS to boot (Windows or Linux, and possibly the specific Linux kernel), and the boot loader (the Windows loader or the EFI stub loader built into a specific kernel) will then take over booting the OS. In Arch, this is often easier to configure than is GRUB, since GRUB is very complex and its automated tools to help with setting things up often get it wrong.
    This is the first error I recieved when I tried to boot windows.
    error: can't find command `drivemap'.
    error: invalid EFI file path.
    Press any key to continue...
    The "drivemap" command in GRUB is generally used when booting a BIOS-mode boot loader, and in fact your "Windows Recovery Environment (loader) (on /dev/sda2)" and "Windows 8 (loader) (on /dev/sda4)" GRUB entries are both built as for BIOS-mode Windows installations -- but the fact that your disks both use GPT means that Windows won't boot in BIOS mode on your computer. (This is one of the many things that the GRUB setup scripts can get wrong.)
    Then I tried to follow this post
    https://bbs.archlinux.org/viewtopic.php?id=150183 and made a new boot
    entry "Windows 82". And I got a new error:
    error: unspecified search type.
    error: file '/EFI/Microsoft/Boot/bootmgfw.efi' not found
    Press any key to continue...
    Both your "Windows 8" and "Windows 82" entries refer to an EFI boot loader file called EFI/Microsoft/Boot/bootmgfw.efi on your EFI System Partition (ESP). This should be correct, but your Boot Info Script output doesn't show any evidence of such a file. Sometimes Boot Info Script misses such things, so you may want to check it just to be sure. Your ESP is /dev/sda1, and it looks like it's being mounted at /boot/efi by default, so check for the /boot/efi/EFI/Microsoft directory tree, and for /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi in particular. If that file isn't present, then something is wrong -- perhaps you mistakenly erased the ESP when you installed Linux, thus wiping out the Windows boot loader; or perhaps the file was accidentally deleted somewhere along the way. (Note that on FAT, which the ESP uses, case is irrelevant, and in fact case varies between the filenames reported by Boot Info Script and what's recorded in your configuration files.)
    You do have another boot loader file that may be a duplicate of the Windows boot loader: EFI/BOOT/bkpbootx64.efi. This filename is generally created by Ubuntu's "Boot Repair" tool, which IMHO can do as much harm as good, especially on a system that's not booting Ubuntu. If you ran this tool, though, it's conceivable that bkpbootx64.efi is a copy of the Windows boot loader, so copying it to EFI/Microsoft/Boot/bootmgfw.efi might get things working. OTOH, the Windows boot loader relies on other files to do its job, so if they're not present, copying the Windows boot loader to its original location won't be sufficient.
    If you can't get things working based on the preceding suggestions, I recommend you run a Windows repair tool. These are accessible from a Windows recovery disc. Such disc images are readily available on the Internet, but I don't happen to have any links handy. Try Microsoft's own site; images obtained from random third-party sites might contain malware. Once you've done this, chances are the computer will boot directly into Windows. You'll then need to either restore GRUB as the default boot loader or install another boot loader or boot manager.  You can use the Windows "bcdedit" command to do the former, as in:
    bcdedit /set {bootmgr} path \EFI\arch-grub\grubx64.efi
    You'll need to type this from an Administrator Command Prompt window.

  • Dual boot Windows and Linux?

    I recently bought a T61, and will be taking a programming course.  One prof I spoke with said they ask us to use Unix tools, so one option is to dual boot linux and Windows.  I haven't decided yet whether I will keep Windows Ultimate, or go to XP for this.  But I was wondering how easy/hard is it to make this work, and what kind of steps need to be taken?   If you could point me towards any good tutorials/guides that would be appreciated too.
    Also, I have never really used linux, so which version is best?  I will be needing it for programming, but also still want to do the basics like web surfing, music, dvd's, burning discs, etc.  I have an old copy of Ubuntu that I never used, but its probably about 4 years old.  Is this still acceptable or will I need something newer?
    Message Edited by amace on 05-29-2008 01:28 PM
    T61 15.4" T9300 (2.5GHz 6MB L2) Windows 7 Professional x64 4GB Memory, NVidia Quadro NVS 140M

    Hi,
    If it's just a couple of programming courses that you are going to take I suggest you'd try out VMware player:
    http://www.vmware.com/products/player/
    You can get this software for free and since your system packs a lot of punch it will be able to run it smoothly without any hassle. I'm an engineering grad student and I have to do alot of programming. I've used VMware player before to do some software developement in Ubuntu when I didn't have enough HD to install dual boot but still couldn't do all my other stuff without XP.
    VMware Ubuntu will need a bit of fiddling to get it work just right (USB devices, etc) but it shouldn't be harder than installing a dual boot (actually it is alot easier for my opinion). The only down side is that file sharing between VMware and Windows can be somewhat difficult. I used an external USB drive to share my files but you could always set up Samba to handle file sharing.
    I hope this helps out with your decision.

  • Dual boot windows server 2008 R2 with windows 8.1 UEFI

    Dear all,
    i was trying to dual boot in UEFI windows 8.1 and windows server 2008 R2 but every time windows server 2008 R2 separately before installing windows 8.1 was working after this windows 2008 R2 gives me blue screen immediately even if i installed windows 8
    first then windows server 2008 but for all case windows server 2008 R2 works with debug mode .
    i could not understand the reason

    Hi,
    What is the STOP error while BSOD occurred? You could try to troubleshoot BSOD with the following method.
    How To Fix a Blue Screen of Death
    http://pcsupport.about.com/od/fixtheproblem/ht/stoperrors.htm
    In addition, have you tried to use Native Boot to make a dual boot? For details, please refer to the following articles.
    Understanding Virtual Hard Disks with Native Boot
    http://technet.microsoft.com/en-us/library/dd799282(WS.10).aspx
    Add a Native-Boot Virtual Hard Disk to the Boot Menu
    http://technet.microsoft.com/en-us/library/dd799299(WS.10).aspx
    Native Boot To VHD Part I of IV - Overview
    http://blogs.technet.com/danstolts/archive/2010/03/29/native-boot-to-vhd-part-i-of-iv-overview.aspx
    Hope this helps.
    Best Regards,
    Andy Qi
    Andy Qi
    TechNet Community Support

  • Dual Boot windows 32bit and 64bit overclocking problems

    Im pretty new to overclocking and this is my first try I manage to get my AMD Venice 3200 to hit 2500 with 250fsb X 10, HTT 4, vcore 1.44. I used memory divider 166/200 so the memory is running at 208MHz not alot of overclocking on the memory since it is some cheap brand.
    My problem is that I have dual boot and with windows xp everything is fine CPU-z reports the right speed for the cpu and memory when I overclock, and there is an increse in preformance with overclocking, But when I boot windows XP 64bit CPU-z reports the FSB as 200 so it is not showing any change, it does report the change in the memory divider 166/200 and the cpu voltage increased that I applied to overclock. The thing is that when I open systerm properties it shows the CPU speed as 2500MHz but when I test the preformance there isnt any increase. I used Superpi to test preformance and in windows XP 32bit it finishes the 1M test in 36seconds while in Windows XP 64bit it takes 42seconds.
    My system specs are
    AMD Venice 3200
    MSI K8N Platium bios 1.8
    1024MB Wintec Memory 3200
    Geforce 6800 GTO 400/1100
    OCZ ModStream OCZ52012U 520W Power Supply

      Im runing the final release of Windows xp 64 and cpu-z 1.30, I also have Everest Ultimate Edition and it only shows 3% overclock 205 FSB.  Im thinking of formating the HD with windows 64 and installing it again with the systerm already overclock.

  • HT4818 I have installed bootcamp that worked properly.  Then I have partitioned the OS X 10.8.2 and installed another OS X 10.8.2 and I have got two MAC boot options and Bootcamp disappeared from the Option menu. How can I boot Windows again and keep both

    I have installed bootcamp by the bootcamp assistant and worked properly.
     Then I have partitioned the OS X 10.8.2 and installed another Mountain Lion System and I have got two MAC boot options and Bootcamp disappeared from the Option menu. However, Bootcamp still remained in the Startup Disk in the System Preferences. When I tried to boot Bootcamp using the Startup Disk it did not boot and received a message that there is no bootable device. I have not lost any data and can read Bootcamp partition from both OS X systems. Please advise how can I boot Windows / Bootcamp again? Thank you. 

    Recommendation 1: Use a VM for this. It's essentially a giant C.F. to do this with native booting, and is potentially fragile.
    But if you're going to ignore that and do this anyway, realizing that it can break anytime in particular with OS upgrades, and that it's very difficult to impossible to resize the three volumes once you've installed the systems:
    1. create three partitions, setting each to be the size for OS X copy 1, copy 2, and Windows respectively. The Windows partition needs to be set to MS-DOS format (actually FAT32) which later in the Windows installer you'll reformat as NTFS. Do not use Boot Camp Assistant to resize/partition the disk, it simply won't work for this use case.
    2. install OS X copy 1
    3. install OS X copy 3
    4. Use gdisk (available at sourceforge) which is a command line only application, to create a new hybrid MBR adding only the last partition (Windows) to the hybrid MBR and setting it to be bootable. As a concequence you will not be able to see/share either OS X volume from within Windows. The Windows NTFS volume will be visible from within OS X.
    5. Install Windows to the only partition its installer should see (confirm size), you'll need to format it NTFS first, and I suggest using the fast format option if available.

  • 2010 Mac Pro Boot Camp - Refuses to boot Windows after installing Boot Camp drivers

    Hey all,
    I have a quad 3.2Ghz 2010 Mac Pro with a Radeon 5870 and 8 GB RAM.
    I have 2 10000RPM WD Raptor drives, the first drive is my Lion boot drive. The 4th bay contains the second Raptor which has Windows 7 Ultimate 64 bit installed. Bay 2 has Time Machine, bay 3 has a Windows backup drive.
    I had first installed Windows and the Boot Camp drivers a few months ago and everything was humming along smoothly. Monday I tried to boot into Windows and it crashed immediately after the black Booting Windows screen started to change to the login window. This happened repeatedly. Nothing changed on the system that I am aware of. Whenever I tried to boot windows again, it booted into the repair mode. That did not seem to work because after running the repair it would still not boot.
    So I did what is usually required of Windows, and that was to reinstall. I reformatted the hard drive, ran Boot Camp assistant, and started the install.
    Everything was peachy so far, so I tried to reinstall the Boot Camp drivers (4.0). Did a reboot. Same problem. Doh!
    So I did ANOTHER reinstall, and everything was fine. But this time I tried to install the Boot Camp drivers off the os install disc that came with my Mac (3.1). Still no go!
    So finally I did my third reinstall and after that I did not install Boot Camp drivers. However, I did load up the CD and individually installed drivers for the Apple Mouse, Apple Keyboard, Cinema Display, etc. No problems whatsoever. Everything is actually still humming along fine.
    So it looks like running the full Boot Camp install for some reason no longer works. Which means I am missing the Apple Boot Camp control panel, but that's not really a big deal. Althought it's quite annoying to not have the functionality of the special Mac keyboard keys like volume control, etc.
    Has anyone run into this? I thought it might be a hardware problem but my Mac OS X OS exhibits no problems whatsoever.
    Thanks!

    Thank you to The hatter.
    I have a Mac Pro mid 2010 with a SSD and several internal hard disks. For some time I was trying to install Windows 7 on a fresh boot camp volume on a new WD 7200rpm 1TB hard disk. It was taking hours to install, and then I had a series of failures to reboot that proved permanent. The Window Repair utility would come up and took forever to repair the volume - but failed to actually do so, requiring completion reinstallation of the bootcamp volume. This occurred three times, between 1 day and 2 months after installation. I had already moved the Windows drive in to drive slot 1 of the Mac Pro.
    Eventually I gave up and installed boot camp on a secondary partition of the SSD. This worked fine, however is limited in capacity. So yesterday I thought I would try to install Windows on the hard disk again. The Windows installer took many hours to do its thing, and eventually a message came up that the installation had failed.
    I took your tip about possible hard disk failure, and ran Techtool Pro surface scan. It turns out that there are lots of bad blocks being reported. According to Micromat's documentation, the bad blocks being reported are those that may be in critical areas of the disk that cannot be mapped out. They recommend low level reinitialisation (with zeros) to map out the bad blocks, if possible. I am now running Apple's Disk Utility to do this, and fingers crossed that this reinitialisation succeeds, or I will have to replace the drive.

  • Not Again! Window Ultimate Parallels and Bootcamp

    I have read hundreds of threads and I don’t want this to be another but I have question that were not specifically answered on not answered at all. I am a life long Windows user and finally made the jump a few months ago. I am a photographer and I have many thousands of dollars in (Windows) software. I considered repurchasing some of them, just keeping an old PC, buying new MAC license for the software that offered it but I have decided to run a dual OS MAC.
    Specs:
    Model Name: MacBook Pro
    Model Identifier: MacBookPro5,5
    Processor Name: Intel Core 2 Duo
    Processor Speed: 2.26 GHz
    Number Of Processors: 1
    Total Number Of Cores: 2
    L2 Cache: 3 MB
    Memory: 2 GB
    Bus Speed: 1.07 GHz
    Boot ROM Version: MBP55.00AC.B03
    SMC Version (system): 1.47f2
    System Version: Mac OS X 10.6.1 (10B504)
    The big question, Bootcamp or Parallels?
    I will use Windows (Vista Ultimate 32bit) for Adobe Master Collection (mainly PS, DW and Flash). I have a few other pieces like Light Room, Aperture and one or two PC only apps. My main uses are minor/moderate .jpg photo retouches/edits in Photoshop and maintain my websites with Dreamweaver.
    Questions:
    1. With my needs, does it sound like BC or Parallels might be a good fit? (File sharing in mind)
    2. What will I see when I fire up the MAC? Will Windows and MAC OS boot at the same time? Is there a choice of what to boot?
    3. File Sharing; Can I take an image that I have brought in via iPhoto, edit it in Photoshop and send it back to the iPhoto library?
    4. I understand that PS and DW are CPU hogs and not really memory. Is this true and should I take my 2gb of memory up to 4gb?
    5..I have seen several comments about a Bootcamp portioned drive being better but no one has explained what that is. Can some one elaborate what that is and is that something done via the Parallels app and if not what is the difference between the Bootcamp partition and what Parallels does?
    6.I will keep my online activities on the MAC side except for my ftp transfers for my sites. With this limitation and limited exposure do you think I need to install a virus protection on the windows side? Does loading Windows increase my exposure to viruses?
    7.With Parallels, Can I shut down the Windows portion and have it apply all the resources back to the MAC os?
    8.I have purchased but not opened Parallels 4.0. I see that 5.0 is out at the same price. Should I go with the new or stick with 4.0 which has been out for a while?
    9.For those that say no to Parallels, should I just work with Bootcamp and a jump drive to move files back and forth?
    10.Finally, with the specs below, how much space should I partition to carry the load?
    *Specs for Parallel:*
    Memory Requirements 1 GB of RAM (2 GB recommended to run Windows Vista). Support for any memory configuration (up to 16 GB), without modifying your host system.
    Disk Space
    Software Installation — 450 MB of available hard drive space for Parallels Desktop 5 for Mac installation (plus space to allocate to your virtual machine).
    *Windows Ultimate Specs:* Not sure exactly how much space it eats up.
    Min Processor Type: Intel x86 - 1 GHz
    Min RAM Size: 1 GB
    Min Hard Drive Space: 40 GB
    *Adobe Master Collection Specs:*
    2GB of RAM (more RAM recommended when running multiple components)
    24.3GB of available hard-disk space for installation; additional free space required during installation (cannot install on flash-based storage devices)

    Questions:
    1. Boot Camp. Graphic/processor intensive apps should generally not be run in a virtual environment
    2. It will startup in whatever OS you have chosen the computer to boot from
    3. Yes
    4. Yes..upgrade to 4GB
    5. Running Windows through Boot Camp is no different than running it on any other PC...that's why it's better.
    6. Of course. Windows is Windows no matter how or what it's installed on. It's still vulnerable to the same viruses.
    7. Yes
    8. See if you're entitled to free upgrade to Parallels 5
    9. That's your call. Nobody can make that decision for you.
    10. Depends on how big the hard drive is.

  • IMac won't boot windows 7 after ram increase to 12gb

    Hi all, just wondering if anyone has has a problem trying to load up windows 7 in boot camp after installing 2 4gb sticks of ram in their iMac. I have a iMac intel core 2duo and the ram is working fine in OSX. When I try to boot up in windows it just sits on the black screen with the flashing icon. I took the extra ram out and it booted up just fine. The version of windows 7 is the ultimate edition 64bit.
    Any help would be great
    Thanks
    Mike

    Fixed the problem with this setup
    Of course this means i just lost 4GB.
    Let me tell the full story.
    In the beginning, long ago, once upon a time. My iMac had 2x2GB ram sticks which were in the two DIMM1 Banks. I then told myself "I WANT MORE RAM BECAUSE LOLZ". So i bought 2x4GB ram sticks. The two empty slots were Bank 0/DIMM0 and Bank 1/DIMM 0. and I added them in there. having done that, I booted OS X up, worked great, had 12GB, everything was shiny and beautiful. Soon after I wanted to try it out on windows. I restarted my computer and BAM the blinking cursor just sits there, being stubborn and all. I then told myself "holy balls, this new ram i got is bonkers" (them words, I blame the language filter). Then after giving it a little thought, i just asked myself if it was because I had ram from two different manufacturers. I removed my old ram, which has nice Samsung stickers on them, and booted it up on windows. Still had the same problem, I then decided that maybe this is all really mentally challenged so to win I had to think like a retard. I took my new ram and inserted it in the same slots where my old ram sticks were (DIMM1 Banks), booted windows up and IT WORKED.
    I still hold all of my WHYs on this subject but I will keep messing around to see if I find a better solution than just leaving both DIMM0 banks empty

Maybe you are looking for

  • MethodNotFound JDev 2.0

    Hi, I am using JDeveloper 2.0. When I try to run my 1.1 JApplet from within the IDE, I get the following error. java.lang.NoSuchMethodError: java.lang.SecurityManager: method classLoaderDepth()I not found at sun.applet.AppletSecurity.checkPropertyAcc

  • Can I Split Coax for TV and Add a Second Modem for Internet?

    Wireless does not work throught the house and I need a wired connection in room upstairs.  There is no way to get another coax up to that room from basement so I guess I need a second modem.  Is there a way to use the TV coax that is already wired in

  • Netbeans 6.0 - code completion of method parameters

    I just updated to NetBeans 6.0 and I find the code completion of method parameters very annoying and counter productive. It inserts the parameters as keywords when choosing a method from the list after pressing CTRL+SPACE. How can I switch this off?

  • Needed disk space, bought an external harddrive and

    Just dragged the icon for my hard drive to the icon for the back up. It is a packard bell and I used the disk utility to erase and set it up for mac. It shows both the Macintosh HD and an alias for the hard drive. Is it that easy? Can I start clearin

  • DW8 & unwanted virtual(paths)

    I tried searching for an answer, but the search returned far too many unrelated results. So, I'm just going to ask everyone. Hopefully someone can lead me in the right direction. I had a problem with PHP, MySQL, & Apache on Monday. I had to unistall,