Winhoes no longer likes to boot after fresh install

English Install/Boot/Login
#1

Today I did a fresh install of Opensuse11 and everything works fine but now when I get to boot screen and select Windows to boot on my other drive it does nothing and just goes to a blackscreen with a cursor…I can boot to Suse not problem but just not to windows…

Menu.lst

# Modified by YaST2. Last modification on Wed Nov  5 14:50:46 CST 2008
default 0
timeout 8
gfxmenu (hd0,1)/boot/message
##YaST - activate

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

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

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

And my grub.conf

setup --stage2=/boot/grub/stage2 (hd0,1) (hd0,1)
quit

So I think there is something up with my grub.conf file or what?

#2

Hold on let me read this post first … “Fixing vista multiboot with openSUSE” it helps to search and read first before posting…my apologies

#3

I went in and edited the menu.lst file as the other post advised to do and did not help…the following changes I made and rebooted after each attempt to test and see if it would let me boot to Winhoes Vista and nothing …

Attempt 1

title windows
rootnoverify (hd0,0)
chainloader (hd0,0)+1

Attempt 2

title windows
rootnoverify (hd0,1)
chainloader (hd0,1)+1

Attempt 3

title windows
    rootnoverify (hd1,0)
    chainloader (hd1,0)+1

Any ideas on how I can fix this … I need that windows I am very sad to say…

#4

any ideas on this on I am getting desperate

#5

Tell us what is the history of the windows installation – too many options to guess about.

For example: If you have windows xp and if it used to be the primary drive but then you swapped it to be the second drive, then you would need to use the map function.

#6

Well its Windows Vista…setup is Windows on a 1TB Seagate and Suse on a separate Hitachi hard drive … Hitachi is the slave and naturally the Seagate is on the Master …

#7

fdisk -l

would be helpful

as would
/etc/fstab

[edit]
so did you install grub to Hitachi drive?

And are the drives not both SATA

#8

Ok here is fstab info…

/dev/disk/by-id/scsi-SATA_Hitachi_HDS7216_PVE201Z8RTUNBM-part1 swap                 swap       defaults              0 0
/dev/disk/by-id/scsi-SATA_Hitachi_HDS7216_PVE201Z8RTUNBM-part2 /                    ext3       acl,user_xattr        1 1
/dev/disk/by-id/scsi-SATA_Hitachi_HDS7216_PVE201Z8RTUNBM-part3 /home                ext3       acl,user_xattr        1 2
/dev/disk/by-id/scsi-SATA_ST31000340AS_9QJ0T1JW-part1 /windows/C           ntfs-3g    users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0
proc                 /proc                proc       defaults              0 0
sysfs                /sys                 sysfs      noauto                0 0
debugfs              /sys/kernel/debug    debugfs    noauto                0 0
devpts               /dev/pts             devpts     mode=0620,gid=5       0 0

Both are SATA and I’m not sure how to do fdisk -l … I am familiar with command line in BASH but not with fdisk haven’t had to use it yet … if can tell me what I need to do to get that info in the console for you I can get it and post it back here no problem

#9

open a terminal
go su

fdisk -l

#10

I am just so sick and tired of using Vista … I have used Fedora for years but wanted to give SUSE a try because I have heard so many good thinks about it … the only reason why I want to use Vista is play Lineage 2 because it will not run in WINE just FYI

#11

FYI
if both are SATA the old master / slave thing is out the window

#12

Ahh ok was doing su -

Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xf4b41cb8

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1         262     2104483+  82  Linux swap / Solaris
/dev/sda2   *         263         915     5245222+  83  Linux
/dev/sda3             916        9729    70798455   83  Linux

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0ec084cf

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1      121602   976759808    7  HPFS/NTFS
#13

Just check out these pages
Partitioning/Install Guide - openSUSE Forums

GRUB Boot Multiboot openSUSE Windows (2000, XP, Vista) using the Grub bootloader.

#14

Well I have read through those but is there something in there you see that I am not … when I choose to boot to windows all I get is the following … on the screen and after that bit of code one line down is a blinking cursor and just hangs there …

   
 rootnoverify (hd1,0)
    chainloader (hd0,1)+1
#15

So sda is your Hitachi?
It is set as first boot device in bios? (it should be)
Grub should be to MBR of sda

sdb is Vista

if you have left Vista MBR untouched, then switching boot order in bios would get you to vista, until you get the grub working properly

#16

try this:

title WIN
map (hd0) (hd1)
map (hd1) (hd0)
rootnoverify (hd1,0)
chainloader +1

#17

OK I will change the boot order in the BIOS and cross my fingers I didn’t screw with the MBR and read up on those links you gave me … TY very much for time …

#18

OK when I changed the menu.lst file to read as … I just left the first line of the title the same as what was there or does that really matter


map (hd0) (hd1)
map (hd1) (hd0)
rootnoverify (hd1,0)
chainloader +1

I got …


map (hd0) (hd1)
map (hd1) (hd0)
rootnoverify (hd1,0)
chainloader +1 

BOOTMGR is missing
Press CTRL+ALT+DELETE to restart
#19

What happened when booting from the windows drive when it was set as first in bios?

#20

When I went in and selected the Windows Drive to boot directly before the SUSE Drive it did exactly the same thing stating BOOTMGR is missing … now when I pressed F9 to get the boot menu and selected to boot to it there I just got a blinking cursor but no errors but nothing happened after several minutes of the blinking cursor of doom however it did show in the BIOS that the Hitachi (SUSE) was SATA 1 and the Seagate (Winhoes) was SATA 4 …