suse 10.2 not booting after network installation

[leadbala]

I have installed suse 10.2 in my machine already with win xp. Installation is through network (ie nfs ) with external usb drive.
now if i boot the machine it boot directly to winxp. I can get into linux only by attaching usb drive. pls help me to install grub loader and necessary things to do for getting working grub.

here i have attached the information of boot loader settings


FDISK -L ENTRIES


Disk /dev/hda: 82.3 GB, 82348277760 bytes
255 heads, 63 sectors/track, 10011 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 2619 21037086 7 HPFS/NTFS
/dev/hda2 2620 10011 59376240 f W95 Ext'd (LBA)
/dev/hda5 2620 5195 20691688+ 7 HPFS/NTFS
/dev/hda6 5196 5290 763056 82 Linux swap / Solaris
/dev/hda7 5291 7186 15229588+ 83 Linux
/dev/hda8 7187 10011 22691781 83 Linux

Disk /dev/sda: 507 MB, 507510784 bytes
255 heads, 63 sectors/track, 61 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 62 495584+ e W95 FAT16 (LBA)
Partition 1 has different physical/logical endings:
phys=(60, 254, 63) logical=(61, 178, 53)

Here is the menu.lst entries

Modified by YaST2. Last modification on Sat Feb 10 04:26:56 UTC 2007
default 0
timeout 8
gfxmenu (hd1,6)/boot/message

###Don't change this comment - YaST2 identifier: Original name: linux###
title openSUSE 10.2
root (hd1,6)
kernel /boot/vmlinuz-2.6.18.2-34-default root=/dev/hda7 resume=/dev/hda6 splash=silent showopts
initrd /boot/initrd-2.6.18.2-34-default

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

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

###Don't change this comment - YaST2 identifier: Original name: failsafe###
"/boot/grub/menu.lst" 26L, 964C

this one is device.map

(fd0) /dev/fd0
(hd0) /dev/sda
(hd1) /dev/hda
~

this one is /etc/fstab entries

dev/hda7 / ext3 acl,user_xattr 1 1
/dev/hda8 /home ext3 acl,user_xattr 1 2
/dev/hda1 /windows/C ntfs ro,users,gid=users,umask=0002,nls=utf8 0 0
/dev/sda1 /windows/D vfat users,gid=users,umask=0002,utf8=true 0 0
/dev/hda5 /windows/E ntfs ro,users,gid=users,umask=0002,nls=utf8 0 0
/dev/hda6 swap swap defaults 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs noauto 0 0
debugfs /sys/kernel/debug debugfs noauto 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
/dev/fd0 /media/floppy auto noauto,user,sync 0 0
~
~

[devils casper]

edit menu.lst file and re-install GRUB again.

Modified by YaST2. Last modification on Sat Feb 10 04:26:56 UTC 2007
default 0
timeout 8
gfxmenu (hd0,6)/boot/message

###Don't change this comment - YaST2 identifier: Original name: linux###
title openSUSE 10.2
root (hd0,6)
kernel /boot/vmlinuz-2.6.18.2-34-default root=/dev/hda7 resume=/dev/hda6 splash=silent showopts
initrd /boot/initrd-2.6.18.2-34-default

too re-install GRUB, execute this

grub-install /dev/hda --recheck

Casper

[leadbala]

Thank you so much for your attention towards my problem.
I have done exactly as you told.
Hurrah...! now i have got grub loader with splash screen background. I am able to boot into linux too..
But when i select windows it says selected drive not exist. I also added two lines ie map (hd0) (hd1) map (hd1) (hd0). No use.
the following is my new menu.lst

# Modified by YaST2. Last modification on Sat Feb 10 04:26:56 UTC 2007
default 0
timeout 8
gfxmenu (hd0,6)/boot/message

###Don't change this comment - YaST2 identifier: Original name: linux###
title openSUSE 10.2
root (hd0,6)
kernel /boot/vmlinuz-2.6.18.2-34-default root=/dev/hda7 resume=/dev/hda6 splash=silent showopts
initrd /boot/initrd-2.6.18.2-34-default

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

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

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 10.2
root (hd0,6)
kernel /boot/vmlinuz-2.6.18.2-34-default root=/dev/hda7 showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off 3
initrd /boot/initrd-2.6.18.2-34-default
pls kind enough to rectify this problem

Thank you once again.

[devils casper]

my mistake. i should have looked into Windows code too.
edit menu.lst again.

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

save file, reboot and select Windows Title. check if it works.





Casper

[leadbala]

[QUOTE=devils_casper]my mistake. i should have looked into Windows code too.
edit menu.lst again.

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

save file, reboot and select Windows Title. check if it works.





Casper[/QUOTE

First of all my thanks to you for your kind help towards my problem.
It is working fine without any trouble. I was struggling for more than a week to correct
this problem. BUT no success.
Could you tell me the secret behind these new entries in brief? One more question
In the documentation page they told me to put two lines for mapping ie map (hd0) (hd1)
.... without these lines only windows is booting. With them it says that
"Disk read error occured press ctrl+alt+del " to restart.
when should we use mapping?

Once my sincere thanks to linux lovers who have helped me directly or indirectly.

[devils casper]

hi leadbala !

i am glad i could help you.

GRUB checks device.map file for disk names and menu.lst file for displaying Menu at startup.
hd0 refers to Primary Harddisk and hd1 refers to Secondary. during installation, External Disk was plugged in as Secondry and installer installed GRUB in MBR of External disk and configured GRUB according to that. GRUB was looking for its configuration files in External Harddisk (hd1).
we edited menu.lst file and directed GRUB to look into Primary Harddisk (replaced hd1 with hd0) and re-installed GRUB in MBR of Primary Harddisk (hda).

we use mapping code in Two Harddisks dual boot setup. Windows needs to be installed in Primary Harddisk only. in two harddisks setup, we plug-in Windows Harddisk as Secondary and use mapping code to cheat windows. coz of mapping code, windows boot loader thinks that its harddisk is plugged in as Primary Master.






Casper

[leadbala]

Because of people like U, the linux is finding its way for spreading and replacing windows usage.
Thank you once again for the timely help.