Hi, On Friday, May 27, 2011 15:45:36 Zack Yovel wrote: > Currently I have windows 2K8 R2 on first HD and SL6 on the second. Super > Grub doesn't get the job done so I guess I need to add an entry to > /boot/grub/grub.conf. > > Before all, if there is a tool that can automatically fix this, I'd be > happy to know about it. > > Here are the contents of my /boot/grub/grub.conf: > . > . > # grub.conf generated by anaconda > # > # Note that you do not have to rerun grub after making changes to this file > # NOTICE: You have a /boot partition. This means that > # all kernel and initrd paths are relative to /boot/, eg. > # root (hd0,0) > # kernel /vmlinuz-version ro root=/dev/mapper/vg_c3po-lv_root > # initrd /initrd-[generic-]version.img > #boot=/dev/sdb > default=0 > timeout=5 > splashimage=(hd0,0)/grub/splash.xpm.gz > hiddenmenu > title Scientific Linux (2.6.32-71.29.1.el6.x86_64) > root (hd0,0) > kernel /vmlinuz-2.6.32-71.29.1.el6.x86_64 ro > root=/dev/mapper/vg_c3po-lv_root rd_LVM_LV=vg_c3po/lv_root > rd_LVM_LV=vg_c3po/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 > SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us crashkernel=128M > rhgb quiet initrd /initramfs-2.6.32-71.29.1.el6.x86_64.img > . > . > I simply don't know exactly how to write the entry, I'll be happy If > someone can point me in the right direction. something like this should work as boot entry for M$ in grub.conf title Win rootnoverify (hd1,0) chainloader +1 Since grub thinks your SL install resides on hd0, I guess your M$ install is on hd1 (or some other hd<number>). Cheers, Andreas