Inconsistent grub error 17, dual booting issues

Hello,
I've recently installed Arch as a second OS on my computer, but I'm having a bit of trouble when it comes to booting it. I'm a bit new to Linux in general, but I've tried to research the problem, and seem to have run into a wall. Any comments, insight, suggestions would be greatly appreciated. Preemptive apologies for being windy, I'm trying to give as much relevant info as possible here
****************Here are the details:******************
-1st hard drive (sda): Windows 7
-2nd hard drive (sdb): Arch
Partitioning scheme:
sdb1 = boot, about 100Mb, ext2
sdb2 = swap, ~2gig
sdb3 = root, ~20gig, ext3
sdb4 = home, the rest (HD is 500gb total), ext3
-grub is installed on the MBR of sdb
-windows has no problems booting independently (when i disconnect my second hard drive), so sda hasn't been touched at all
in grub's menu.lst:
arch has root set to (hd1,0)
windows 7 has rootnoverify set to (hd0,0), with chainloader +1 after.
**************The issue:********************
when choosing to boot arch from grub, (this is booting off of the second hard drive), i get an error 17, saying the filesystem is unrecognized and the partition type is 0x7.
if i then enter into the command line mode for grub, and try
find /grub/stage1
it spits out (hd0,0), which is incorrect. it should be (hd1,0) since my boot partition is the first partition on the second hard drive, and (hd0,0) is an entirely different hard drive with nothing but windows on it.
An interesting complication:
If I boot the USB iso image of arch I used to originally install it, and I highlight the option "boot existing OS", press tab to change hd0 0 to hd1 0, it loads up Grub, and from there on Grub boots perfectly fine to Arch - implying that at the very least Arch installed on the hard drive properly. Also, Grub run in this fashion seems to realize that (hd1,0) is ext2.
After booting arch as in the previous paragraph^ (note, this is arch as installed on the hard drive, not the liveCD version), i run:
grub
grub> find /grub/stage1
and it replies that stage1 is in hd(1,0), which is where it should be.
Googling suggests my partitions are somehow messed up, but I'm not completely sure of that. Booting from the USB image and running
fdisk -l
seems to give the right partition order and sizes.
However, there could be a problem stemming from how I partitioned the second hard drive in the first place: it's an Advanced Format drive, and using Western Digital's guidelines - http://wdc.custhelp.com/app/answers/detail/a_id/5655 - i ran:
parted -a optimal /dev/sdb
and created my partitions, then used the Arch installer to establish their file systems and do the rest.
I don't have any concrete ideas about what's going on, except that Grub is somehow having trouble mounting/recognizing the file system when I try to run it from the MBR directly.
Once again, sorry for such a long post, and any help at all is greatly appreciated.

Ok, so I've tried to reconfigure my grub/menu.lst as described in https://wiki.archlinux.org/index.php/Pe … t_managers .
When I try to boot after that, it claims that the device /dev/disk/by-uuid/*the uuid i got for my boot partition* cannot be found.
This next paragraph might be a bit of a facepalm moment; in retrospect, it seems like it should be obvious that this would happen (like lifeafter2am is saying, my drives are getting switched at boot up):
After booting up grub in a bunch of different configurations, I've managed to determine that what my computer does is this:
- In the bios, I changed the boot order to be USB -> 2nd hard drive (the one with arch on it) -> first hard drive (since I use a USB for a liveCD, and the 2nd hard drive's MBR has grub on it, which i want to use to dual boot both arch and windows, windows being on the first hard drive).
So every time I insert the usb, it changes what grub perceives to be hd0 and hd1. When I insert the usb, the usb becomes hd0, and the other drives are renumbered. When I try to boot without the USB, having the BIOS boot from my second hard drive makes the second hard drive become hd0.
What with ^ going on, I simply went in to the grub/menu.lst and changed arch's (hd1,0) to (hd0,0), and now it recognizes that (hd0,0) is indeed an ext2 fs, partition type 0x83, etc.
The problem now is: no matter what I try to set the root in menu.lst to be, whether it's sdb1, sda1, some uuid label, grub starts booting and then says error: unable to mount the real root device, and dumps me into a shell with a good luck message.
Is there a way to figure out what i should set grub's root in menu.lst to be, from the arch iso on my USB, keeping in mind the fact that inserting the USB renumbers the hard drives?
I don't wanna make the analogy to quantum mechanics, but this almost seems like an observer disturbing the results type of thing >_<
Last edited by sergs (2012-02-12 01:18:54)

Similar Messages

  • Error with dual boot Win 8/OL6 R3

    Hello,
    I am hoping to discuss this with someone who has experience with this configuration. My goal is to get Oracle Linux dual booting on my windows 8 machine.
    I have installed OL but I am having trouble getting it to dual boot win8/OL using the windows boot menu. Whereas windows 8 boots as expected, the Oracle Linux option gives me the error:
    "+Windows failed to start. A recent hardware or software change might be the cause...contact you system administrator or computer manufacturer for assistance+
    +File:+ \NST\nst_linux.mbr
    +Status: 0xc000007b+
    +Info: The selected application or operating system couldn't be loaded because a required file is missing or contains errors.+"
    Here are some details of the scenario:
    - Documentation followed: Red_Hat_Enterprise_Linux-6-Installation_Guide-en-US.pdf
    - Hardware: Dell Precision M4700 64 bit UEFI
    - OEM installed/Default OS: Windows 8 Pro 64 bit
    - Installation source: OracleLinux-R6-U3-Server-x86_64-dvd.iso (written to DVD)
    These are the broad steps I followed:
    In windows 8
    I:
    - downloaded the Linux ISO software. The checksum on the download matched
    - wrote the ISO to a bootable installation disk
    - created a new 344gb partition for Linux using the DOS DISKPART command - partition 7
    Linux Install
    - I booted using the Linux installation DVD and started the installation
    - When Installing Linux partition 7 became a 500mb system partition and partition 8 became the 343 gb Linux partition
    - I manually created the boot partition as ext3 (because the pdf I was following said "+If your 64-bit x86 system uses UEFI instead of BIOS, you will need to manually create a /boot partition. This partition must have an ext3 file system. If you choose to partition automatically, your system will not boot.+"
    - I installed the boot loader on sda7. I selected “First sector of boot partition - /dev/sda7”. I assume this installs separate GRUB boot loader on the Linux partition (7) – which will then be 'chain loaded' from the windows boot menu. Put another way, it will boot with the windows boot manager, which will give me an option to chain load the Grub boot loader, which will then run Linux...
    - I chose the desktop installation
    - The installation reported that it completed successfully
    I successfully booted back into windows:
    - I used easybcd to edit the microsoft bcd and successfully created a boot menu for Oracle Linux. I used the legacy grub because the Linux documentation says "+Note that the version of GRUB in Red Hat Enterprise Linux 6 is an old and stable version now known as "GRUB Legacy" since upstream development moved to GRUB 2.3 Red Hat remains committed to maintaining the version of GRUB that we ship with Red Hat Enterprise Linux 6, just as we do with all packages that we ship.+".
    - After installing Linux and updating the BCD, the BCD now looks like this:
    Windows Boot Manager
    identifier {bootmgr}
    path \EFI\Microsoft\Boot\bootmgfw.efi
    description Windows Boot Manager
    locale en-US
    inherit {globalsettings}
    integrityservices Enable
    default {current}
    resumeobject {2b56acdd-8bbe-11e2-9ba6-b8ca3ad88679}
    displayorder {current}
    {524cc0d3-8bce-11e2-935f-b8ca3ad88679}
    toolsdisplayorder {memdiag}
    timeout 30
    Windows Boot Loader
    identifier {current}
    device partition=C:
    path \Windows\system32\winload.efi
    description Windows 8
    locale en-US
    inherit {bootloadersettings}
    recoverysequence {524cc0d1-8bce-11e2-935f-b8ca3ad88679}
    integrityservices Enable
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice partition=C:
    systemroot \Windows
    resumeobject {2b56acdd-8bbe-11e2-9ba6-b8ca3ad88679}
    nx OptIn
    bootmenupolicy Standard
    Real-mode Boot Sector
    identifier {524cc0d3-8bce-11e2-935f-b8ca3ad88679}
    device partition=C:
    path \NST\nst_linux.mbr
    description OracleLinux
    I'm not sure the BCD entry is correct. I assume that this entry should be pointing to the nst_linux.mbr on the Linux boot partition. However I have verified that this file exists in windows 8:
    C:\NST\nst_linux.mbr
    I haven't been able to exactly confirm how the boot process should work i.e. whether this file should actually be in the Linux boot partition (as opposed to the windows c drive) and whether the BCD should also point to the Linux boot partition when referring to this partition.
    As I mentioned above, I now have the windows boot menu with Windows 8 (which boots successfully) and Oracle Linux (which gives me the error see below for complete wording**). Is the Real-mode Boot sector wrong? Should it point to the Linux boot partition? Is it a problem with my UEFI disk? I don't think it should be because this version of Oracle Linux supports UEFI and my hardware is UEFI.
    Has anyone carried out a similar win8/OL dual boot?
    2001
    ** Complete wording of the Linux boot option in the windows boot manager:
    Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:
    1. Insert your Windows installation disk and restart the computer.
    2. Choose your language settings, and then click "next".
    3. Click "Repair your computer".
    If you do not have this disk, contact you system administrator or computer manufacturer for assistance
    File: \NST\nst_linux.mbr
    Status: 0xc000007b
    Info: The selected application or operating system couldn’t be loaded because a required file is missing or contains errors.
    Edited by: 2001 on Apr 1, 2013 4:27 PM
    Edited by: 2001 on Apr 17, 2013 5:17 PM

    Hi,
    Here are my responses:
    *[asmirnov]* Could you please confirm, I just want to see if I got it right the first time -
    *[2001]* I'm happy to share my progress
    Q1)
    *[asmirnov]* You did create a partition (where you would install Linux) from Win8, correct?
    *[2001]* Yes. I used diskmgmt.msc to create a separate partition. I didn't format the partition because the Linux install doesn't want that, it creates and formats the partitions in the unallocated partition
    Q2)
    *[asmirnov]* You use GRUB (not GRUB2)?
    *[2001]* I'm not sure where you were asking about, so I hope my answer here covers all possibilities you may have meant.
    I was using the windows 8 boot. I wanted to chain load to the boot loader in the Linux Partition. It is interesting what the Linux install did with my partition, it created 2 partitions in the unformatted partition. 1 was a bootable partition and the other was the Linux partition. The details were:
    2 sda’s (a boot / ext4 and a VolGroup (vg_linuxlocalhost)/ physical volume (LVM) ). In the VolGroup it created 3 lv’s, lv_root, lv_home and lv_swap. I understand that this is all normal.
    I followed the documentation note which said "To configure the Red Hat Enterprise Linux boot loader to chain load from a different boot loader, you must specify the boot drive manually. If you chose any of the automatic partitioning options, you must now select the Review and modify partitioning layout option before you click Next or you cannot specify the correct boot drive"
    So there was also the note in the documentation that said "Note that the version of GRUB in Red Hat Enterprise Linux 6 is an old and stable version now known as "GRUB Legacy" since upstream development moved to GRUB 2.3 Red Hat remains committed to maintaining the version of GRUB that we ship with Red Hat Enterprise Linux 6, just as we do with all packages that we ship." I didn't install any bootloaders manually (either the windows 8 OOTB default that came with my machine or the Linux one), I just took the defaults. I'm wasn't sure how to access the Linux partitions once it is installed, so I can't confirm it was the legacy GRUB in the Linux boot partition, but I believe this note is saying that it OL6 does use the legacy grub. I believe GRUB Legacy is version .97.
    Q3)
    *[asmirnov]* Which version of Linux exactly did you use, was that Oracle Linux or you used one from RedHat directly? What is the kernal version?
    *[2001]* I used "OracleLinux-R6-U3-Server-x86_64-dvd.iso.sha1sum" from the mirror site http://mirror.aarnet.edu.au/pub/oraclelinux/OL6/U3/x86_64/. According to the release notes at: https://oss.oracle.com/ol6/docs/RELEASE-NOTES-U3-en.html the kernel is
    - Unbreakable Enterprise Kernel Release 2 [kernel-uek-2.6.39-200.24.1.el6uek]. Installed and booted by default
    - Red Hat compatible Kernel [kernel-2.6.32-279.el6]. Installed by default
    Note: By default, both the Unbreakable Enterprise Kernel and the Red Hat Compatible Kernel for the specific architecture (i386 or x86_64) are installed, and the system boots the Unbreakable Enterprise Kernel by default. If needed, /etc/grub.conf and /etc/sysconfig/kernel can be modified to make the system boot with the Red Hat Compatible Kernel by default.
    Regarding your follow-up point that "Microsoft blocks 3rd party chainloaders from the BCD menu for UEFI machines. We are researching workarounds, none have presented themselves as of yet.", I'm not sure it actually blocks it, but it certainly isn't a straight forward process.
    I have actually abandoned my attempt to get the dual boot working. It is a real shame because I wanted to do it for my own satisfaction.
    I am now using Oracle Virtual Box as suggested by others, include Dude earlier in this thread. This has given me confidence that I was doing all the right things because the install worked first time without any problems. The virtualization is much simpler and I have had no problems so far.
    Fusion
    As for your point about the fusion middleware and OL5. I am looking at Oracle SOA with is part of the Fusion brand. I think that the latest SOA components will work on OL6 - but I have yet to try it. Following the certification matrix can be a little difficult. So as I indicated above, my current thoughts are to use the Oracle Virtual Box with Linux r6 u3 and to install the SOA components on that when I get chance. The alternative is using the pre-built virtual machine it has Linux and SOA (it might cover your stack too, or there may be another one that suits you better on the site) http://www.oracle.com/technetwork/middleware/soasuite/learnmore/vmsoa-172279.html. Note that this is still on OL5.
    I hope this helps.

  • 975x Platinum PowerUp Dual Boot Issue

    Hello -
    I have a 975x Plat. PowerUp and dual boot Linux and Windows XP. This process works fine on BIOS 7.1, but fails to boot the Windows disk on BIOS 7.4 and newer. The disk still works, it just can't be started by the Linux bootloader (grub).
    I spent a lot of time working on this as a grub issue, but in the end the only thing that affects the problem is revision of the BIOS I am using. (e.g., flash 7.4, Windows does not boot, reboot and flash 7.1, Windows boots).
    I also get an issue where I cannot eject the CD drive on warm boot under the same conditions (like a BIOS boot disc, or a Windows boot disc). Works fine on 7.1 not on 7.4 or newer.
    I have all 4 ports on the ICH7 controller used for hard drives, and the JMicron controller used for a SATA DVD drive. The issue occurs in IDE or AHCI mode (currently using AHCI mode).
    Are these known problems? Are there known fixes? I would like to use a newer BIOS because I have an MS USB keyboard that does not work in DOS mode with BIOS < 7.4 (need keyboard to select OS at boot time).
    Thanks,
    Chris

      Not sure if this will help: BIOS 7.61 BETA - Flash at your own risk - http://www.msi-forum.de/thread.php?threadid=32518&threadview=1&hilight=&hilightuser=0#post264463

  • [SOLVED] Grub error 18 - cannot boot to Windows

    Earlier today I tried to install Arch 64bit (I had 32bit earlier) with kdemod to test new KDE4.2. However, after installation I could not boot neither Arch nor Windows. Grub appeared, but every single option gave me an error. I can't remember anymore which error it was, but It doesn't matter anymore. I thought I had made a really stupid and basic mistake while installing, I just didn't know what.
    I wanted to test KDE4.2 so much so I installed Kubuntu (yeah, this topic is not related to Arch Linux, I hope that somebody can help me though, move this topic to somewhere else if it doesn't belong here ). Installation was fine, booting to Kubuntu was fine (and upgrading to KDE4.2 was fine), but booting to Windows was not. It gave me a following error:
    Error 18: Selected cylinder exceeds maximum supported by BIOS
    I googled a bit and found this: http://wiki.linuxquestions.org/wiki/GRUB#Error_18 I reinstalled Kubuntu using /dev/sdb1 as /boot and /dev/sdb2 as / (/dev/sdb3 is windows and /dev/sdb4 is my game partition, ntfs). Before this I had /dev/sdb1 as / and /dev/sdb2 as swap (now I have no swap at all, my 4GB RAM should be enough). The only difference was that at first grub gave me error 15 (I fixed it with Kubuntu LiveCD). After that - no difference.
    I need Windows for playing. That's why it's very important that I can use it. [SOLVED] In addition, I should say that /dev/sda is a separated hard drive which is encrypted with Truecrypt. (I said this because I think that Kubuntu tried to install grub on (hd0)...) When I tried to mount this hard drive with Kubuntu, it couldn't do it. I wanted to test mounting on Windows to check if it is just Kubuntu's problem. If not, I'm fucked because this hard drive contains VERY VERY VERY IMPORTANT files. [/SOLVED]
    I really need help, please. If somebody can help me, (s)he is my hero.
    Last edited by Exitium (2009-01-29 14:42:32)

    Oops, I forgot:
    menu.lst:
    (Yup, a lot of comments, Ubuntu style)
    # menu.lst - See: grub(8), info grub, update-grub(8)
    # grub-install(8), grub-floppy(8),
    # grub-md5-crypt, /usr/share/doc/grub
    # and /usr/share/doc/grub-doc/.
    ## default num
    # Set the default entry to the entry number NUM. Numbering starts from 0, and
    # the entry number 0 is the default if the command is not used.
    # You can specify 'saved' instead of a number. In this case, the default entry
    # is the entry saved with the command 'savedefault'.
    # WARNING: If you are using dmraid do not use 'savedefault' or your
    # array will desync and will not let you boot your system.
    default 0
    ## timeout sec
    # Set a timeout, in SEC seconds, before automatically booting the default entry
    # (normally the first entry defined).
    timeout 10
    ## hiddenmenu
    # Hides the menu by default (press ESC to see the menu)
    #hiddenmenu
    # Pretty colours
    #color cyan/blue white/blue
    ## password ['--md5'] passwd
    # If used in the first section of a menu file, disable all interactive editing
    # control (menu entry editor and command-line) and entries protected by the
    # command 'lock'
    # e.g. password topsecret
    # password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
    # password topsecret
    # examples
    # title Windows 95/98/NT/2000
    # root (hd0,0)
    # makeactive
    # chainloader +1
    # title Linux
    # root (hd0,1)
    # kernel /vmlinuz root=/dev/hda2 ro
    # Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST
    ### BEGIN AUTOMAGIC KERNELS LIST
    ## lines between the AUTOMAGIC KERNELS LIST markers will be modified
    ## by the debian update-grub script except for the default options below
    ## DO NOT UNCOMMENT THEM, Just edit them to your needs
    ## ## Start Default Options ##
    ## default kernel options
    ## default kernel options for automagic boot options
    ## If you want special options for specific kernels use kopt_x_y_z
    ## where x.y.z is kernel version. Minor versions can be omitted.
    ## e.g. kopt=root=/dev/hda1 ro
    ## kopt_2_6_8=root=/dev/hdc1 ro
    ## kopt_2_6_8_2_686=root=/dev/hdc2 ro
    # kopt=root=UUID=e85e83e5-0f7c-419e-8cad-1fe5d9128e8f ro
    ## default grub root device
    ## e.g. groot=(hd0,0)
    # groot=504fab5b-7bb6-4b20-af58-83677386de37
    ## should update-grub create alternative automagic boot options
    ## e.g. alternative=true
    ## alternative=false
    # alternative=true
    ## should update-grub lock alternative automagic boot options
    ## e.g. lockalternative=true
    ## lockalternative=false
    # lockalternative=false
    ## additional options to use with the default boot option, but not with the
    ## alternatives
    ## e.g. defoptions=vga=791 resume=/dev/hda5
    # defoptions=quiet splash
    ## should update-grub lock old automagic boot options
    ## e.g. lockold=false
    ## lockold=true
    # lockold=false
    ## Xen hypervisor options to use with the default Xen boot option
    # xenhopt=
    ## Xen Linux kernel options to use with the default Xen boot option
    # xenkopt=console=tty0
    ## altoption boot targets option
    ## multiple altoptions lines are allowed
    ## e.g. altoptions=(extra menu suffix) extra boot options
    ## altoptions=(recovery) single
    # altoptions=(recovery mode) single
    ## controls how many kernels should be put into the menu.lst
    ## only counts the first occurence of a kernel, not the
    ## alternative kernel options
    ## e.g. howmany=all
    ## howmany=7
    # howmany=all
    ## should update-grub create memtest86 boot option
    ## e.g. memtest86=true
    ## memtest86=false
    # memtest86=true
    ## should update-grub adjust the value of the default booted system
    ## can be true or false
    # updatedefaultentry=false
    ## should update-grub add savedefault to the default options
    ## can be true or false
    # savedefault=false
    ## ## End Default Options ##
    title Ubuntu 8.10, kernel 2.6.27-11-generic
    uuid 504fab5b-7bb6-4b20-af58-83677386de37
    kernel /vmlinuz-2.6.27-11-generic root=UUID=e85e83e5-0f7c-419e-8cad-1fe5d9128e8f ro quiet splash
    initrd /initrd.img-2.6.27-11-generic
    quiet
    title Ubuntu 8.10, kernel 2.6.27-11-generic (recovery mode)
    uuid 504fab5b-7bb6-4b20-af58-83677386de37
    kernel /vmlinuz-2.6.27-11-generic root=UUID=e85e83e5-0f7c-419e-8cad-1fe5d9128e8f ro single
    initrd /initrd.img-2.6.27-11-generic
    title Ubuntu 8.10, memtest86+
    uuid 504fab5b-7bb6-4b20-af58-83677386de37
    kernel /memtest86+.bin
    quiet
    title Wintoosa
    root (hd1,2)
    savedefault
    makeactive
    map (hd0) (hd1)
    map (hd1) (hd0)
    chainloader +1
    fdisk -l
    (Note: These results are mainly in Finnish. It could be hard to you to read it... But whatever... I'll translate these only if necessary)
    Levy /dev/sda: 640.1 Gt, 640135028736 tavua
    255 päätä, 63 sektoria/ura, 77825 sylinteriä
    Yksiköt = 16065 * 512 = 8225280 -tavuiset sylinterit
    Levyn tunniste: 0xcc5d88e2
    Laite Käynn Alku Loppu Lohkot Id Järjestelmä
    /dev/sda1 * 244091 485122 1936074870+ b8 BSDI sivutus
    Osion 1 loppu ei ole sylinterin rajalla.
    /dev/sda2 176430 394864 1754572509+ 43 Tuntematon
    Osion 2 loppu ei ole sylinterin rajalla.
    /dev/sda3 177329 413105 1893868925 29 Tuntematon
    Osion 3 loppu ei ole sylinterin rajalla.
    /dev/sda4 57435 309703 2026342066 5c Priam Edisk
    Osion 4 loppu ei ole sylinterin rajalla.
    Osiotaulumerkinnät eivät ole levyjärjestyksessä
    Levy /dev/sdb: 500.1 Gt, 500107862016 tavua
    255 päätä, 63 sektoria/ura, 60801 sylinteriä
    Yksiköt = 16065 * 512 = 8225280 -tavuiset sylinterit
    Levyn tunniste: 0x0007a52a
    Laite Käynn Alku Loppu Lohkot Id Järjestelmä
    /dev/sdb1 1 128 1028128+ 83 Linux
    /dev/sdb2 129 13185 104880352+ 83 Linux
    /dev/sdb3 13186 26239 104856255 7 HPFS/NTFS
    /dev/sdb4 26240 60801 277619265 7 HPFS/NTFS
    Last edited by Exitium (2009-01-28 21:05:33)

  • How to configure Grub or enable dual boot Windows7 & Oracle Enterprise Linux6

    Hi,
    I had Windows 7 installed on my PC and later on I have installed Oracle Linux6 (Server).
    While installation I didn't get any option to configure dual boot and now I am unable to boot Windows7.
    If I do fsdik -l command on Linux prompt, I get the result:
    # fdisk -l
    Disk /dev/sda: 160.0 GB, 1600041885696 bytes
    255 heads, 63 sectors/track, 19457 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum.optimal): 512 bytes / 512 bytes
    Disk identifier: 0x9143f05b
    Device           Boot     Start     End     Blocks          Id     System
    /dev/sda1       *          1          1305    10482381     83     Linux
    /dev/sda2                  1306     6405    40960000      7       HPFS/NTFS
    /dev/sda3                  6405     12779  51200000      7       HPFS/NTFS
    /dev/sda4                  12779    19458 53646336      7       HPFS/NTFS
    I check the grub config file at /boot/grub/menu.lst but I do not see any entry for windows here.
    Please advise how to configure grub or other way to make the dual boot options enable and use windows and linux.
    Thanks in Advance.
    Anand

    Could you post your menu.lst file?
    It's not clear which exact partition Windows 7 is on from fdisk -l, but you could try adding this to your menu.lst file:
    title Microsoft Windows 7
    root (hd0,1)
    savedefault
    makeactive
    chainloader +1

  • Dual boot issues with P67A-GD55 (B3)

    Set up a dual boot and from a cold start now the system boots directly into the default OS even though I have it set to display the options for 15 seconds. When this happens I do a soft reset and then the 2 OS choices are there. This is on the 1.C BIOS (latest). Would expect to always see the 2 OS choices on cold boot as well.

    yes, I have several HDDs and an SSD. The 2 OSs are on the SSD. The original OS was on the SSD then I created free space on the SSD and installed another OS. I set the original OS as the default and the newer OS as the secondary. The SSD is now and always has been the primary boot disk in BIOS. Again, it's an easily repeatable issue, upoon cold boot there is no option of OS displayed, it just boots right into the default OS. If I reboot then I see the 2 OSs.
    Quote from: Bernhard on 08-July-11, 23:12:06
    >>Posting Guide<<
    Do you have more than one hard drive ? Did your boot priority change in the BIOS after your BIOS flash ? If so, change it back to the HDD/partition where you initially created the dual boot.

  • Dual boot issues

    I've been attempting to get up to speed on labview, labview RT, the PXI (8106), and getting the PXI to dual boot labview RT and windows XP. Question here is only about dual booting. I have the PXI set up with a fat32 partition physically before (C the NTFS partition that windows XP is installed on (E. I installed windows, worked great. I then tried to boot in to labview RT/communicate with the PXI (booting into RT using the bios software switch). No dice since no RT software was installed. So I used a USB memory stick and the software from MAX to install RT on to the PXI. Worked, I can communicate with the PXI, awesome. Today I wanted to boot back in to windows. Go in to the bios, set it to boot windows/other OS . . . and it boots in to labview RT. Dammit. What did I do wrong? What can I do to correct this? Please tell me I don't have to re-do the windows install. It will be my fourth time and installing all that NI software takes a painful amount of time!
    Thanks,
    Chris

    If you attempt to fix your master boot record, here's a couple other things to keep in mind:
    1. When you used the RT USB key, did you select the Format option to only update the 1st available partition or format the entire disk?  Gerardo's suggested approach will of course only work if you did the former.
    2. If you don't have any success with FixMBR since it is a slightly more complicated disk configuration with two partitions, there is another approach you can try if you meet the following requirements:
     (a) You originally set up two partition configuration on your disk with the  NI OS Recovery media
     (b) You have another disk of the exact same type that you are willing and able to erase.
     (c) You only did the partital format of the original drive from the RT USB key (see item #1 above)
     (d) You have a bootable USB key (see note below)
    If so, you could do the following:
    1. Put the 2nd disk on your PXI-8106
    2. Run the OS installer, and configure it exactly as you did with the first disk.
    3. You should now have a disk with a master boot record that exactly matches the one you'd like on your original controller.
    4. Boot to DOS from your USB key and run MBRWizard to save a copy of the master boot record (http://mbrwizard.com)
    5. Put the original disk back on your PXI-8106, boot to DOS again, and run MBRWizard to restore that saved MBR file to update the master boot record on the original disk.
    It sounds pretty involved but really can be done in a few minutes because for step 2 -you don't need to fully install the OS.  We're only interested in getting a copy of the master boot record, which is one of the first things that the installer will configure.  Once you see the installer copying files to the disk, you can stop the system and proceed to step 3.
    Note on DOS-bootable USB key: If you don't have a DOS-bootable USB key, there is a variety of ways to set one up but a relatively easy one is to grab this disk diagnostic tool from NI: Fujitsu Disk Diagnostic.  Careful, once you run the tool, IT WILL ERASE YOUR ENTIRE USB KEY.  Technically it is for setting up a disk diagnostic, but you should be able to copy the mbr wizard tool to the key and also run that from DOS.  Delete the autoexec.bat file that gets created on the USB key to prevent the Fujitsu tool from running automatically.  You could for example re-use the RT USB key you previously configured, although it will be wiped and new files put on it.
    Last thing: If you don't have a second drive available, please post the exact details on the drive you do have and the specifics on how you originally partitioned the drive (what tools, what partition sizes).  I might be able to help you out and create the MBR file for you, so you would only need to worry about step 5 above (and setting up a DOS bootable USB key).
    Cheers,
    Josh

  • Dual boot issue on Satellite A200 - xp keeps freezing or crashing

    Well being trying to install xp along side my Win7 installation (dual boot), but xp keeps freezing or crashing.
    Ive made a few slipstream xp discs with sata drivers.
    Still wont install proper.
    So i tried install win7 on the second partition and that will install but is very slow and hangs for ages.
    Im sure i got right sata drivers.(intel matrix storage manager from toshiba).
    Can anyone shed some light?
    i have toshiba Satellite a200
    intel duo t5550
    3gb ram

    Hi
    If you use SATA drivers then the SATA mode option in BIOS should be set to AHCI.
    If you dont use SATA drivers then you have to set to compatible mode.
    Here a nice description how to add SATA drivers
    +How to integrate a SATA AHCI driver in a Windows XP Setup CD+
    http://aps2.toshiba-tro.de/kb0/TSB85017Z0000R01.htm
    Good luck

  • [SOLVED]Arch Linux, and Windows 8.1 Dual Boot issue

    Hi guys. I recently bought a new laptop, and decided to run Arch Linux and Windows 8.1. I installed Windows 8.1 first as recommended by the beginners guide, and then installed Arch Linux. I made sure UEFI was enabled in my BIOS, and made sure everything was on a GPT partition. The install itself went fine. My laptop loads grub, and Arch Linux shows up and boots, but there is no option to boot into Windows 8.1. The only way I can boot into Windows 8.1 is by accessing my motherboard, and choosing to launch the windows boot manager instead of the grub launcher. How can I get Windows 8.1 to show up in grub? Thanks in advance guys.
    Last edited by Painguy (2014-08-20 20:19:37)

    Painguy wrote:
    -----------Edit------------------
    Yeah just ran this after installing os prober
    grub-mkconfig -o /boot/grub/grub.cfg
    and it works now. Sorry for the crazy posts guys. Thanks for the suggestions and help.
    Yeah I'm sure I'm doing something wrong lol. I did not install OS-Prober. I think that's where the issue is. I'm missing the menu entry in grub.cfg right? Do I just run os prober or do I have to manually edit grub.cfg.
    If that's not the case then here is what I did up until now. What I did was start with a blank SSD drive. I used cgdisk to make the disk use a GPT partitioning scheme. I installed windows 8.1 and checked in windows to make sure it boots into UEFI-GPT mode and it does.  I then installed arch linux using the beginners guide. I made sure to use cgdisk to create any extra partitions, and installed GRUB to the efi partition that windows had created ( I did not format this partition ). I then finished the installation and rebooted, and Grub only shows arch linux. I don't think I'm dealing with anything MBR related. I made sure I used the GPT partitioning scheme....i think lol.
    All you need to do is run os-prober then run grub-mkconfig. It should pick up Windows at that point.

  • [Solved] Grub Error 15 at boot on new install.

    So I was trying to avoid asking for help, but I honestly can't see what's wrong with my new install of arch.  I followed the beginner's guide all the way up to the part where you reboot and remove the liveCD.  It all went swimmingly until I rebooted and got:
    GRUB Loading stage1.5.
    GRUB Loading, please wait...
    Error 15
    I don't know what's going on.  Error 15 is supposedly "file not found," but I don't know what file it's looking for since I have a grub.cfg that I created from the steps posted on the guide.  Any help is greatly appreciated.
    --Wes
    EDIT:
    Just to be clear I followed the BIOS motherboard steps for GRUB.
    Last edited by Wesman26 (2012-11-09 01:25:38)

    Xacky wrote:Which instructions did you follow? This would normaly do it when chrooted (during install).
    Wat your disk en partition lay-out?
    -One or more harddisks?
    -Partitions? Everything on / or separate /home /boot (/var)?
    I'm following the beginner's guide instructions for a BIOS install.  After chroot I used the following:
    # pacman -S grub-bios
    # grub-install --target=i386-pc --recheck --force --debug /dev/sdb
    # cp /usr/share/locale/en\@quot/LC_MESSAGES/grub.mo /boot/grub/locale/en.mo
    # grub-mkconfig -o /boot/grub/grub.cfg
    Aside from the warnings (that I think most people ignored) of a few files not existing during the installation of grub-bios, it all went fine.  The harddrive is definitely sdb (fdisk -l shows sda as my windows drive, not to mention I just formatted and partitioned sdb).  My partitions are laid out exactly as the guide tells me to (/ on /dev/sdb1 and /home on /dev/sdb2).  They are the only partitions on sdb.
    DSpider wrote:Lol... a full reinstall wasn't needed. This mentality is typical to a Windows user.
    I don't appreciate your condescension.  These forums have (up to this point) always been really helpful and friendly to me; just because I'm posting in the newbie corner doesn't mean I'm not familiar with linux, and even if I were unfamiliar with linux I would hope that you could show more respect and compassion for someone who needs help than to ostracize them and laugh about their problem.  I posted here because I figured I didn't need to waste the time of the mods and users who offer help in the installation subforum with something that I assumed would be a trivial fix.  I expected courteous, thoughtful responses.  I was apparently wrong to assume.
    I reinstalled because I didn't know what else to do, and figured that there might have been a chance that I made a mistake.  Since your previous advice was literally getting me nowhere I figured the 10 minutes of my time reinstalling took up would be worth the potential of fixing my problem. 
    To answer your questions that are actually helpful:
    I don't have grub installed on another drive and my drive and partition layout is detailed above.  As for boot priority, it hasn't changed since I first installed linux in 2006 and it's worked ever since; I'm performing this operation to clear what was once a drive cluttered with a few other distros that I've abandoned since 2007 when I found Arch (yes I am actually that lazy).
    Is it possible that my old installation of grub might have stayed on the drive even after I rid it of the old partitions (since it's stored in MBR)?  If so does the installation of grub2 I'm performing not get rid of it?
    Hope this helps,
    --Wes
    Last edited by Wesman26 (2012-11-08 20:53:27)

  • Z77 Mpower Error Code 62 Boot Issue

    Hey guys. I am pretty dumbfounded on this one. I will start by listing my specs:
    MSI Mpower mobo
    i5-2500k
    Corsair AX-750
    EVGA 670
    Intel 520 SSD / WD 3TB
    So this build has been running fine for absolutely months, no issues whatsoever. Today I downloaded and installed Mumble, it asked me to restart my system which I did. Now nothing out of the ordinary until nothing happens on the restart boot. PC is on, power on, fans all working, LED's on, but no screen input. Note I had changed NOTHING since it was working.
    I'm just failing to see why and what caused this and how to fix it. I've tried a few basic things, re-seating GPU/moving to diff slot, re-seating RAM, turning off for 1-2 hours, nothing is working. The error code is 62. I've looked around but as far as I can see there are no dead-set fixes, just hoping anyone here may be able to assist me.
    Regards.

    I couldn't test it in another system but I had an old GTX 260 on hand and with that the system runs fine.
    Which obviously points to the GTX 670 malfunctioning but I still don't get how it can go from fine no issues one moment to completely not working after doing a restart..
    Well I guess I'm going to have to RMA it either way. Thanks for the help.

  • Lenovo Z585 Ubuntu 13.04 / Windows 8 Dual Boot Issue - Wake from Suspend?

    As the title says. I have been having an issue with waking the screen on my laptop after going into suspend from Ubuntu 13.04. (Also, same problem on Ubuntu 12.10 and Fedora 18)
    When I close the lid, the computer will go into standby normally. Lights go out, and power light just blinks. Upon opening the lid I get the lights on the computer to come back and the fans come back on, however the screen stays black.
    I have the following:
    Processor: AMD A10-4600M APU with Radeon HD Graphics x 4
    Driver: Gallium 0.4 on AMD ARUBA
    I have tried updating drivers through Ubuntu. I have tried modifying the backlight controls through editing the grub.
    I have tried several re-installs of multiple versions of the listed Linux above.
    No matter what I do, I have the same issue(s) on all three versions.
    A seperate issue is a weak wifi signal using the installed Broadcom wifi antenna. Sitting next to the router I only get about 60% strength. If I plug in my Belkin USB wireless antenna I get 100%.
    Any help would be great!
    Thanks

    Bump

  • Grub & error trying to boot other linux partition

    My 40 gig hard drive is partitioned like this
    hda1 = Arch Linux partition (XFS file system, Grub installed to MBR)
    hda5 = swap partition for Arch
    hda6 = Vector Linux partiton (Reiser file system, LILO installed to superblock)
    hda7 = swap partition for Vector
    Here is my Grub menu.1st
    menu.lst            [B---] 51 L:[  1+40  41/ 41] *(1251/1251b)= <EOF>
    # Config file for GRUB - The GNU GRand Unified Bootloader
    # /boot/grub/menu.lst
    # DEVICE NAME CONVERSIONS
    #  Old /dev    DevFS                    Grub
    #  /dev/fd0    /dev/floppy/0            (fd0)
    #  /dev/hda    /dev/discs/disc0/disc    (hd0)
    #  /dev/hdb2   /dev/discs/disc1/part2   (hd1,1)
    #  /dev/hda3   /dev/discs/disc0/part3   (hd0,2)
    #  FRAMEBUFFER RESOLUTION SETTINGS
    #     +----------------------------------------+
    #          | 640x480 800x600 1024x768 1280x1024
    #      ----+-----------------------------------
    #      256 |   0x301   0x303    0x305     0x307
    #      32K |   0x310   0x313    0x316     0x319
    #      64K |   0x311   0x314    0x317     0x31A
    #      16M |   0x312   0x315    0x318     0x31B
    #     +----------------------------------------+
    # general configuration:
    timeout   10
    default   0
    color light-blue/black light-cyan/blue
    # boot sections follow
    # each is implicitly numbered from 0 in the order of appearance below
    # (0) Arch Linux
    title  Arch Linux  [/boot/vmlinuz26]
    root   (hd0,0)
    kernel /boot/vmlinuz26 root=/dev/discs/disc0/part1 ro
    # (1) Vector Linux
    title Vector Linux  [/boot/vmlinuz]
    root   (hd0,5)
    kernel /boot/vmlinuz root=/dev/discs/disc0/part6 ro
    The problem is I can't get Vector to boot. The "Uncompressing Linux" message is follwed by all the usual messages and then at the end thses lines pop up.
    VFS: cannot open root device "discs/disc0/part6" or 00:00
    please append a correct "root=" boot option
    Kernel panic:VFS: unable to mount fs on 00:00
    I have tried changing the grub parameters to try .../part7 and ....part5 but part7 should be the swap so that won't work naturally.
    Both had1 and hda6 are set as bootable btw.
    Can I get some insight as to what I am doing wrong???

    No problem.  I am glad I was able to help. 
    FYI,  In the grub entry for Vector you used the devfs (Arch) style (/dev/discs/disc0/partx) to define the root partition instead of the older dev system (/dev/hdax) that Vector expected.  Besides that there was nothing wrong with your grub entries.

  • Drivers for windows xp, Dual Booting issue

    I have recently purchased a mac Book pro the 13 inch model, it came with lion installed by default this means boot camp only works for 7
    So ive partioned my disk using boot camp and installed Xp onto the partioned part of the hd
    Obviously the issue with this is that boot camp wont let me burn a disk for the drivers as it only supports 7
    so really i need someway of getting the drivers, after googling for a while i couldnt find anything so if anyone has any suggestions it would be most appreciated.
    Drivers would be for such thing as the wirelsess card, sound, graphics chip etc

    XP is not supported in Lion or by the newer Apple computers. There are no XP drivers for lion or for the newer hardware. This issue has been discussed repeatedly in the Boot Camp forum: https://discussions.apple.com/community/windows_software/boot_camp

  • GRUB Error, unable to boot [SOLVED]

    Edited Away!
    Last edited by wroom (2009-06-12 20:57:32)

    No problem.  I am glad I was able to help. 
    FYI,  In the grub entry for Vector you used the devfs (Arch) style (/dev/discs/disc0/partx) to define the root partition instead of the older dev system (/dev/hdax) that Vector expected.  Besides that there was nothing wrong with your grub entries.

Maybe you are looking for

  • MS office report

    Hi, I am trying to generate a report using the MS office express vi and after follow the instructions in the manuals and check the examples I cant fill a table predefined in my own template!! and I get an error Error -41110 occurred at NI_ReportGener

  • Monitor looks red

    monitor looks all red, I tried another monitor before and that one looked yellow, do i have a problem with my videocard? I went to system preferences and tried all; also I tried the PRAM RESET but didn't work? the monitors seems to work fine in a min

  • Sending emails

    Hi. l am hoping someone can help me. In exploring the new Yahoo mail site l clicked on something which has added a thumbnail photo of myself to the top right hand side of my email. It doesn't show on Yahoo but when l send an email through my Macbook

  • Searching with large text

    Greetings, We are evaluating Oracle 10g specifically for its Oracle Text functionality and are having a difficult time trying to figure out how to use large text for searching. Specifically, we have a table containing large, full-text descriptions th

  • Preview not updating

    I'm using Premier Elements 10 and last night I encountered a strange bug causing the preview window to not update. I;m currently working on a project that's dependent on syncing this with music which is highly difficult if I can't see things in real