Results 1 to 5 of 5

Thread: Can't boot into windows!

  1. #1
    Join Date
    Jul 2008
    Location
    Bella Vista, AR
    Posts
    69

    Angry Can't boot into windows!

    I can't boot into windows after installing 11.0. I just get this message when I select windows 1 (same message for windows 2, with the top two lines being different):
    rootnoverify (hd1,1)
    chainloader (hd0,0)+1

    BOOTMGR is misssing
    Press CTRL+ALT+DEL to restart.
    And I KNOW I didn't somehow damage either windows drives. All I did was format sdb (the empty drive, windows drives are sda and sdc) as ext3 and installed 11.0 on it.

    My config file:
    # Modified by YaST2. Last modification on Tue Jul 8 21:42:46 EDT 2008
    default 0
    timeout 8
    gfxmenu (hd1,1)/boot/message

    ###Don't change this comment - YaST2 identifier: Original name: linux###
    title openSUSE 11.0 - 2.6.25.9-0.2
    root (hd1,1)
    kernel /boot/vmlinuz-2.6.25.9-0.2-default root=/dev/disk/by-id/scsi-SATA_ST3500630AS_9QG3F9PA-part2 resume=/dev/sdb1 splash=silent showopts vga=0x31a
    initrd /boot/initrd-2.6.25.9-0.2-default

    ###Don't change this comment - YaST2 identifier: Original name: failsafe###
    title Failsafe -- openSUSE 11.0 - 2.6.25.9-0.2
    root (hd1,1)
    kernel /boot/vmlinuz-2.6.25.9-0.2-default root=/dev/disk/by-id/scsi-SATA_ST3500630AS_9QG3F9PA-part2 showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off x11failsafe vga=0x31a
    initrd /boot/initrd-2.6.25.9-0.2-default

    ###Don't change this comment - YaST2 identifier: Original name: windows 1###
    title windows 1
    rootnoverify (hd1,1)
    chainloader (hd0,0)+1

    ###Don't change this comment - YaST2 identifier: Original name: windows 2###
    title windows 2
    rootnoverify (hd1,1)
    chainloader (hd2,0)+1
    I should also mention that I can't explore my windows drives from suse. Wth?

  2. #2
    Join Date
    Jun 2008
    Location
    The English Lake District. UK - GMT/BST
    Posts
    36,729
    Blog Entries
    20

    Default Re: Can't boot into windows!

    Try editing your first windows like this (make a backup of the original)


    title WIN
    map (hd0) (hd1)
    map (hd1) (hd0)
    rootnoverify (hd1,0)
    chainloader +1
    Leap 15.1_KDE
    My Articles Was I any help? If yes: Click the star below

  3. #3
    Join Date
    Mar 2008
    Location
    Oz
    Posts
    11,727
    Blog Entries
    2

    Default Re: Can't boot into windows!

    Quote Originally Posted by caf4926 View Post
    Try editing your first windows like this (make a backup of the original)


    title WIN
    map (hd0) (hd1)
    map (hd1) (hd0)
    rootnoverify (hd1,0)
    chainloader +1
    IMHO that's for when Windows 2000/xp is installed on a primary drive that is later switched to the second drive. the file boot.ini needs to be tricked into thinking it's still on the first drive. But vista doesn't suffer from that delusion and has s different bootloader that sorts it out correctly. IME when Suse is installed on drive number two, the yast entry in menu.lst for windows on drive 1 is wrong and needs to be edited as in this howto sticky at top of the forum install/boot:
    Fixing vista multiboot with openSUSE - openSUSE Forums

    Perhaps try caf4926's suggestion and the sticky too, one of them might work.
    Leap 42.3 & 15.1(Beta) &KDE
    FYIs from the days of yore

  4. #4
    Join Date
    Jul 2008
    Location
    Bella Vista, AR
    Posts
    69

    Default Re: Can't boot into windows!

    Thanks guys, I will try that.

    Also, I assume that some posts were lost int he move over here? Because I had a problem exactly like this when I installed Suse 10.3. I was just going to use that older thread to fix my problem but it seems to have dissapeared.

    Cheers.

  5. #5
    Join Date
    Mar 2008
    Location
    Oz
    Posts
    11,727
    Blog Entries
    2

    Default Re: Can't boot into windows!

    Quote Originally Posted by TV-VCR View Post
    Thanks guys, I will try that.

    Also, I assume that some posts were lost int he move over here? Because I had a problem exactly like this when I installed Suse 10.3. I was just going to use that older thread to fix my problem but it seems to have dissapeared.

    Cheers.
    OK then -- to be explicit -- when you get to the sticky, take the two "map" lines out if you've put them there and change the paragraph to this:
    Code:
    ###Don't change this comment - YaST2 identifier: Original name: windows 1###
    title windows 1
    rootnoverify (hd0,0)
    chainloader (hd0,0)+1
    I've assumed here that windows is on sda1 -- is that right?

    Regarding this statement:
    I should also mention that I can't explore my windows drives from suse. Wth?
    For purposes of this exercise you can mount them temporarily following this example for sda1:

    First make a mount point with this console command:
    Code:
    sudo mkdir /mnt/sda1
    Then mount with this command:
    Code:
    sudo ntfs-3g /dev/sda1 /mnt/sda1
    For permanent mounts see this tutorial:
    HowTo Mount NTFS Filesystem Partition Read Write Access in openSUSE 10.x
    Leap 42.3 & 15.1(Beta) &KDE
    FYIs from the days of yore

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •