Unable to boot into Windows after running Linux System Repair

English Install/Boot/Login
#1

Hi,
I’m running Windows Vista and Suse Linux under dual boot. I used Paragon Hard Disk Manager 2010 to convert a primary Windows partition, which is to the right of Linux in the partition sequence to a logical partition. After I did this, I redid grep and then had a functioning system that was able to boot into Windows or Linux. I then took a Paragon disk backup. Next, I made further changes after which I was unable to boot into Linux even after running Repair System and redoing grub. I then restored the version of the system with the new logical partition, using Paragon. On first boot, after reinitializing grub, I got a black and white, non-gui version of the Startup Options boot menu and selected
Windows, which booted successfully. But I didn’t have Suse, so I ran Repair System again and reset grub. After this, I got the green Startup Options screen and was able to boot into Linux. But when I tried Windows, the black and white boot menu reappeared and selecting Windows brought me nowhere with no error messages. I tried editing the Windows entry in the list and got “rootnoverify (hd0,1)”, which correctly pointed to the Windows partition. I ran Windows Repair Installation, but got the same result.
I am afraid that Linux System Repair has damaged my Windows partition.
My /boot/grep/menu.lst file follows –

Modified by YaST2. Last modification on Fri Nov 2 19:01:13 EDT 2012

default 0
timeout 8
gfxmenu (hd0,7)/boot/message
##YaST - activate

title Windows Vista
rootnoverify (hd0,1)
chainloaded +1

###Don’t change this comment - YaST2 identifier: Original name: linux###
title SUSE LINUX
root (hd0,7)
kernel /boot/vmlinuz root=/dev/disk/by-id/ata-ST31000528AS_9VP771VT-part8 repair=1 resume=/dev/disk/by-id/ata-ST31000528AS_9VP771VT-part7 splash=silent showopts vga=0x31a
initrd /boot/initrd

###Don’t change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe – SUSE LINUX
root (hd0,7)
kernel /boot/vmlinuz root=/dev/disk/by-id/ata-ST31000528AS_9VP771VT-part8 showopts ide=nodma apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 x11failsafe vga=0x31a
initrd /boot/initrd

I would appreciate any help that anyone could offer.
Thanks,
s660117

#2

> Hi,
> I’m running Windows Vista and Suse Linux under dual boot. I used Paragon Hard Disk Manager 2010 to convert a primary Windows partition, which is to the right of Linux in the partition sequence to a logical partition. After I did this, I redid grep and then had a functioning
> system that was able to boot into Windows or Linux. I then took a Paragon disk backup. Next, I made further changes after which I was unable to boot into Linux even after running Repair System and redoing grub. I then restored the version of the system with the new
> logical partition, using Paragon. On first boot, after reinitializing grub, I got a black and white, non-gui version of the Startup Options boot menu and selected

> Windows, which booted successfully. But I didn’t have Suse, so I ran Repair System again and reset grub. After this, I got the green Startup Options screen and was able to boot into Linux. But when I tried Windows, the black and white boot menu reappeared and
> selecting Windows brought me nowhere with no error messages. I tried editing the Windows entry in the list and got “rootnoverify (hd0,1)”, which correctly pointed to the Windows partition. I ran Windows Repair Installation, but got the same result.
> I am afraid that Linux System Repair has damaged my Windows partition.

> My /boot/grep/menu.lst file follows –

# Modified by YaST2. Last modification on Fri Nov 2 19:01:13 EDT 2012
default 0
timeout 8
gfxmenu (hd0,7)/boot/message
##YaST - activate

title Windows Vista
rootnoverify (hd0,1)
chainloaded +1

###Don't change this comment - YaST2 identifier: Original name: linux###
title SUSE LINUX
root (hd0,7)
kernel /boot/vmlinuz root=/dev/disk/by-id/ata-ST31000528AS_9VP771VT-part8 repair=1 resume=/dev/disk/by-id/ata-ST31000528AS_9VP771VT-part7 splash=silent showopts vga=0x31a
initrd /boot/initrd

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- SUSE LINUX
root (hd0,7)
kernel /boot/vmlinuz root=/dev/disk/by-id/ata-ST31000528AS_9VP771VT-part8 showopts ide=nodma apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 x11failsafe vga=0x31a
initrd /boot/initrd

I would appreciate any help that anyone could offer.
Thanks,
s660117

It sounds like to me you have challenged fate one time too many. You have taken several actions and using non-Linux tools, its a wonder that anything is working for you. If you still have a valid copy of Windows and can get anything to work, then backup your data files if you can and consider starting over. You should install Windows Vista First and make sure to use a custom partition size not using it all at first. With a single hard drive you might do something like this:

/dev/sda Generic booting MBR (Master Boot Record)
/dev/sda1 Primary Partition, NTFS with Windows Vista Installed (First)
/dev/sda2 Primary Partition, SWAP, SWAP (2-4 GB)
/dev/sda3 Primary Partition, EXT4 openSUSE Root partition (40-60 GB) Loading Grub 2 here and marking it active to boot
/dev/sda4 Primary Partition, EXT4 openSUSE /home partition

If these partitions make no sense to you, you are not ready for such changes as you have tried to make. Please read through the following article:

http://forums.opensuse.org/content/111-partitioning-hard-disk-during-install.html

Thank You,

#3

On 11/03/2012 05:26 PM, s660117 wrote:
> title SUSE LINUX

what version of which operating system are you running?

that can be known for certain by this command in a terminal:

cat /etc/SuSE-release

it seems from your post that you are running SUSE Linux (probably either
Desktop or Server)…if so, you really need to get with the SUSE Linux
gurus at http://forums.suse.com/

these are the openSUSE forums, the ID and Password you used here is also
good there…

on the other hand, if you are using openSUSE, please post again, along
with the output from the terminal command, and what desktop environment
you are using, if any…

–
dd