I just assumed that it, like 12.1, just need to be changed to /sda"1". Does not work when I boot.
I get the “chainloader blah blah 0,1” but grub just keeps restarting and I can’t actually boot Windows though it is listed.
thnxxx
I just assumed that it, like 12.1, just need to be changed to /sda"1". Does not work when I boot.
I get the “chainloader blah blah 0,1” but grub just keeps restarting and I can’t actually boot Windows though it is listed.
thnxxx
Show as out put of
sudo fdisk -l
not that is a lower case L not a one
Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 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: 0xd6cf2304
Device Boot Start End Blocks Id System
/dev/sda1 * 469491712 488396799 9452544 f W95 Ext’d (LBA)
/dev/sda2 3074048 469491131 233208542 7 HPFS/NTFS/exFAT
/dev/sda5 469493760 473708543 2107392 82 Linux swap / Solaris
/dev/sda6 473710592 484198399 5243904 83 Linux
/dev/sda7 484200448 488376319 2087936 83 Linux
As I see it /dev/sda1 is the Extended Partition (hd0,0) and so /dev/sda2 is your only choice to load Windows (hd0,1) like this below in the grub legacy menu.lst file:
##Don't change this comment - YaST2 identifier: Original name: windows 1###
title Windows
rootnoverify (hd0,1)
chainloader +1
If this does not work, then Windows is blown up I guess and will not load.
Thank You,
##Don't change this comment - YaST2 identifier: Original name: windows 1### title Windows rootnoverify (hd0,1) chainloader +1
If this does not work, then Windows is blown up I guess and will not load.
Thank You,
Yeah, this is accurate unfortunately. Went back to installing 12.1, but still nothing. bootmgr is (still) missing…
Tried using a Windows 7 install disc as back up recovery, but it did not even read the OS image. I noticed through navigating CMD that all of the directories for Windows 7 are still there… Also tried fixing the MBR with SuperGRUB. It said it fixed it and now I notice “MBR” initialize as text during boot, but than grub2 starts immediately. Still nothing. Ack.
, but than grub2 starts immediately.
What?
can you still boot Linux? If so run
sudo cat /boot/grub/menu.lst
and
sudo cat /boot/grub/grub.cfg
and show the output.
I get the “chainloader blah blah 0,1” but grub just keeps restarting and I can’t actually boot Windows though it is listed.
What do you get now, Please don’t tell us “blah blah” that is not informative, give the full error message accurately.
With the Ext’d partition marked bootable/active indicates that grub stabe1 was written to it, so rewriting the MBR would have no effect.
Your fdisk indicates that the first partition starts at sector 3074048, did you delete any partitions ?
With the Win 7 cd , did you try to repair the bootmgr ?
default 0
timeout 8
##YaST - generic_mbr
gfxmenu (hd0,5)/boot/message
##YaST - activate
###Don’t change this comment - YaST2 identifier: Original name: linux###
title Desktop – openSUSE 12.1 - 3.1.10-1.9
root (hd0,5)
kernel /boot/vmlinuz-3.1.10-1.9-desktop root=/dev/disk/by-id/ata-ST9250315AS_5VCDKKBZ-part6 resume=/dev/disk/by-id/ata-ST9250315AS_5VCDKKBZ-part5 splash=silent quiet showopts vga=0x317
initrd /boot/initrd-3.1.10-1.9-desktop
###Don’t change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe – openSUSE 12.1 - 3.1.10-1.9
root (hd0,5)
kernel /boot/vmlinuz-3.1.10-1.9-desktop root=/dev/disk/by-id/ata-ST9250315AS_5VCDKKBZ-part6 showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe vga=0x317
initrd /boot/initrd-3.1.10-1.9-desktop
###Don’t change this comment - YaST2 identifier: Original name: windows###
title Windows
rootnoverify (hd0,1)
chainloader +1
cat: /boot/grub/grub.cfg: No such file or directory
Windows 7 install disc in Recovery repair mode did not even detect an operating system… Could not continue past that point.
Windows 7 install disc in Recovery repair mode did not even detect an operating system… Could not continue past that point.
As indicated by @ Lost Farmer
Your fdisk indicates that the first partition starts at sector 3074048, did you delete any partitions ?
Did you?
If a partition that is needed by windows has been deleted, It is likely that there is no way to retrieve it.
You could try rebuilding BCD and reinstalling the windows generic MBR using the info available here How to use the Bootrec.exe tool in the Windows Recovery Environment to troubleshoot and repair startup issues in Windows