Two sata hdd, have been using vista for quite a time…
today I delete the partition P:, which is the last partition, in vista, then install suse 11.0.
the installation went on smoothly. was able to to everything in suse. good.
after the 1st reboot, could see the green GRUB, then choose “windows”, says “BOOTMGR is missing”. Google.
Auto-Repair using vista dvd. Reboot.
Then GRUB refuse to show up, “error 5”. reboot always so. Of course, i’m not going to enter windows without first step GRUB.
Then repair using usue dvd. Repair installed system —> expert tool - —> There’re some choices in Reinstall Boot loader, I remember I chose “GRUB, boot from root partition”, either chose “set active flag in the boot partition…” && “write generic code in mbr…”. just follow the hints from HELP.
Then, after boot up, The grub error seems fixed, but the computer enters vista directly as if linux does not exist.
goolge…google… I’m fed up with those paradox commands…
first time been here.
Could some one help me please?
Thanks.
With repair option did you use Vista ?
Than Vista boots
With Vista did use including the new service pack ?
Or did you like to GRUB to boot both ?
dobby9
That looks like you have either
(a) the active flag on the windows partition, not the Suse root partition
or
(b) an active flag on both the windows and the Suse partiitons
I suggest you do the repair of the bootloader again, this time setting [under the Tab called Boot Loader Installation] to boot from the Master Boot Record – not the root partition. That should fix it.
You’re right. the last two partitions O:and P: (volume P:later was deleted and occupied by suse) were inactive partitions in vista, which constitute the 2nd hdd.
“to boot from the Master Boot Record” is not recommended if another OS exists----I remember the HELP said so; and I thought this is the reason for that vista error msg “BOOTMGR is missing”
if you google this msg, you would see some info suggesting ACTIVE issues. for example, one reads"This usually occur when 2 drives (not partitioned, but 2 physical HDD) are set ACTIVE",…see link: bootmgr is missing - TechNet Forums
so what’s the possible solution? since both can’t be active simutaneously; setting one inactive then the other would not work… currently the dev/sda (vista) is active and grub not even shows so no way to linux. vice versa.
Plus, all the partitions in the 1st hd where vista lives are not readable in suse, that is, only partitions on the 2nd hdd were incorporated into"windows" filegroup.
“to boot from the Master Boot Record” is not recommended if another OS exists----I remember the HELP said so; and I thought this is the reason for that vista error msg “BOOTMGR is missing”
Try it anyway – it should work – if it doesn’t you can switch it back the way it was.
then how about the other options: should I choose “set active flag in the boot partition…” && “write generic code in mbr…”, or should I say, which option should I choose?
Uncheck those two options so that non-generic code goes in the MBR. The non-generic code to go in the MBR this time will chain the booting across to the Grub config file (menu.lst) on the Suse partition.
[If this doesn’t work, there’s another way where you do manipulate the active flag/s, but maybe think about just one thing at a time for the moment.]
I’m not sure… I see in the menu.lst that suse and suse_failsafe both locate in (hd1,5). considering I installed suse in the 2nd hdd, which is of course hd1 and vista should be in hd0, the first hdd… <:)
Please post the contents of the Grub bootloader menu located at /boot/grub/menu.lst
Please post the partition table which you can make visual with this console command:
problem is, now the computer where suse is installed is not connected to internet, I’m using a laptop to use internet(wireless share)…
but I can see if I type in the fdisk:
Device Boot Start End
/dev/sda1 1 1
partition 1 does not end on cylinder boundary
/dev/sda2 * 1 3264
partition 2 does not end on cylinder boundary
/dev/sda3 3264 30402
partition 3 does not end on cylinder boundary
(these are mounted as /windows/vista/c,d,e; but strange is that partitions f,g,h,i,j cannot be seen in device list; maybe due to they’re dynamic partitions not basic partitions? never know)
Disk /dev/sdb: 250.0 GB,
255 heads, 63 sectors/track, 30401 cylinders…
Device Boot Start End
/dev/sdb1 1 27008
partition 1 does not end on cylinder boundary
/dev/sdb2 * 27009 30401
/dev/sdb5 27009 27270
/dev/sdb6 27271 28558
/dev/sdb7 28559 30401
menu.lst
default 0
timeout 8
gfxmenu (hd1,5)/boot/message
title vista
rootnoverify (hd0,0)
chainloader (hd0,0)+1
Don’t change…
title openSuse 11.0
root (hd1,5)
kernel /boot/vmlinuz root=//dev/disk/by-id/scsi-SATA_WDC_WD…
initrd /bot/initrd
It works. You’re right.
happy to see the vista progress bar.
From the initial “BOOTMGR is missing”, how long a road I’ve taken
however luckily, no data is lost finally.
Thanks for your help.
—> There’re some choices in Reinstall Boot loader, I remember I chose “GRUB, boot from root partition”, either chose “set active flag in the boot partition…” && “write generic code in mbr…”. just follow the hints from HELP.