Re: Upgrading the computer issues (dual boot windows 7 with grub)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 2010-12-13 at 01:48 +0200, Doron Bar Zeev wrote:
> 
> 
> On Sun, Dec 12, 2010 at 21:55, Les <hlhowell@xxxxxxxxxxx> wrote:
>         
>         
>         I do not see the menu presented.  I don't seem to be able to
>         get into
>         windows 7 at all.  So the question becomes, how to access the
>         menu and
>         get windows 7 to boot.  I have included the information on
>         grub.conf and
>         menu.lst to show what I have done.  I am sure it is wrong, but
>         I am not
>         seeing it.
>         
>         =========================================================================
>         # 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_school3-lv_root
>         #          initrd /initrd-[generic-]version.img
>         #boot=/dev/pdc_dcedfhhihd
>         default=0
>         timeout=0
>         splashimage=(hd0,0)/grub/splash.xpm.gz
>         #hiddenmenu
>         title Fedora (2.6.35.9-64.fc14.x86_64)
>                root (hd0,0)
>                kernel /vmlinuz-2.6.35.9-64.fc14.x86_64 ro
>         root=/dev/mapper/vg_school3-lv_root rd_DM_UUID=pdc_dcedfhhihd
>         rd_LVM_LV=vg_school3/lv_root rd_LVM_LV=vg_school3/lv_swap
>         rd_NO_LUKS
>         rd_NO_MD LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16
>         KEYBOARDTYPE=pc
>         KEYTABLE=us rhgb quiet
>                initrd /initramfs-2.6.35.9-64.fc14.x86_64.img
>         title Fedora (2.6.35.6-45.fc14.x86_64)
>                root (hd0,0)
>                kernel /vmlinuz-2.6.35.6-45.fc14.x86_64 ro
>         root=/dev/mapper/vg_school3-lv_root rd_DM_UUID=pdc_dcedfhhihd
>         rd_LVM_LV=vg_school3/lv_root rd_LVM_LV=vg_school3/lv_swap
>         rd_NO_LUKS
>         rd_NO_MD LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16
>         KEYBOARDTYPE=pc
>         KEYTABLE=us rhgb quiet
>                initrd /initramfs-2.6.35.6-45.fc14.x86_64.img
>         title Windows
>         title Windows
>         map (hd0) (hd1)
>         map (hd1) (hd0)
>         rootnoverify (hd1,1)
>         # makeactive #if you use Windows7 this line should be
>         commented out
>         chainloader +1
>         
>         =========================================================
>         
>         fdisk -l shows the following:
>         
>         Disk /dev/sda: 500.1 GB, 500107862016 bytes
>         255 heads, 63 sectors/track, 60801 cylinders, total 976773168
>         sectors
>         Units = sectors of 1 * 512 = 512 bytes
>         Sector size (logical/physical): 512 bytes / 512 bytes
>         I/O size (minimum/optimal): 512 bytes / 512 bytes
>         Disk identifier: 0x00088ae8
>         
>           Device Boot      Start         End      Blocks   Id  System
>         /dev/sda1   *        2048     1026047      512000   83  Linux
>         /dev/sda2         1026048   976642047   487808000   8e  Linux
>         LVM
>         
>         Disk /dev/sdb: 1500.3 GB, 1500301910016 bytes
>         255 heads, 63 sectors/track, 182401 cylinders, total
>         2930277168 sectors
>         Units = sectors of 1 * 512 = 512 bytes
>         Sector size (logical/physical): 512 bytes / 512 bytes
>         I/O size (minimum/optimal): 512 bytes / 512 bytes
>         Disk identifier: 0xa2771934
>         
>           Device Boot      Start         End      Blocks   Id  System
>         /dev/sdb1            2048    37750783    18874368   27
>          Unknown
>         /dev/sdb2   *    37750784    37955583      102400    7
>          HPFS/NTFS
>         /dev/sdb3        37955584  2930143231  1446093824    7
>          HPFS/NTFS
>         
>         
>  
> I understand you are able to load fedora, and you want to see the grub
> menu.
> In that case you can press shift during the first stage of loading the
> computer or
> change the line in grub.cfg  to: 
> timeout=10 
> 
> 
> 
> however I think you have to change the  windows part of grub.cfg to:
>  
> title Windows
> roonoverify (hd1,0)
> chainloader +1
> 
> 
> tell us what happenened



Changing the timeout fixed the issue with not seeing the menu, and
changing the rootnoverify (hd1,0) brought me to a windows reload screen
(earlier reply), then changiing the rootnoverify line back to
rootnoverify(hd1,1) got me into windows proper.  I suspect that a
problem with booting in windows due to a root kit or messed up boot
selector would cause the disk to default to partition 0, so microsoft
put the reloader there so the system could be restored in the event of a
catastrophic failure.

All is well again in Les Land now.
Thanks, Doron, your help is greatly appreciated.

Regards,
Les H

-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux