Per Jessen wrote:

Per Jessen wrote:

...

Yesterday I received two new laptops, both Toshiba L675 with Windows 7. This morning I tried to install openSUSE 11.4 without touching any of the default settings. The installation went fine, but the system was not able to boot up afterwards (after stage1 had finished). I suspect graphics is the problem as a saw a weird dotted line being written across the splash-screen before the system halted. Does this sound familiar to anyone?

Sorry, not graphics, just a boot-partition that wasn't made bootable.

https://bugzilla.novell.com/show_bug.cgi?id=691927

Well, a little more than that - I can boot my newopenSUSE 11.4, but Windows can't be booted anymore. (BOOTMGR is missing). I haven't done one of these installations (Linux onto an system with an working Windows installation including shrinking of NTFS partition) in years, any chance I'm doing something wrong? -- Per Jessen, Zürich (16.5°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 5/5/2011 10:07 AM, Per Jessen wrote:

I'm now trying to get this BOOTMGR back using a Windows Repair Disc that I created earlier, but something must have gotten screwed up royally here. It can't be right that one does a new installation of openSUSE only to end up with a non-bootable Windows system? Seems like it would make any newbie run away screaming.

Well it's always a risk when dual booting that the MBR would be overwritten. Go grab a multi boot program or a partitioning tool that can fdisk the mbr. once you force a new mbr it should boot back into windows for you. in fact if you can use the rescue cd to drop to a c:\ prompt you may be able to do it. Been a while since I had to rescue a Windows install. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 2011/05/05 11:38 (GMT-0400) Carl Hartung composed:

boot dvd into rescue mode # grub # find /boot/grub/menu.lst [say it returns '(HD0,4)'] # root (HD0,4) # setup (HD0] # quit # reboot

That's probably what you want to do if you wish Windows to boot no longer, as it replaces Windows' standard MBR code with Grub code. It may work, depending on Windows version and whether there's a functional chainloader entry for booting Windows. If however you do 'setup (hd0,rootpart#)'[1], then you won't destroy the MBR code Windows depends on. Additionally, not replacing standard MBR code with non-standard MBR code, and not depending on non-standard MBR code, means Windows virtually inevitable repairs won't be destroying the ability to boot Linux. [1] works only if rootpart# is 1-4, or if you provide an intermediary step for reaching higher numbered / Linux partitions, or alternate bootloader reachable via standard MBR code. cf. http://fm.no-ip.com/PC/install-doz-after.html -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Carl Hartung wrote:

On Thu, 05 May 2011 12:08:26 -0400 Felix Miata wrote:

...

On 2011/05/05 11:38 (GMT-0400) Carl Hartung composed:

...

boot dvd into rescue mode # grub # find /boot/grub/menu.lst [say it returns '(HD0,4)'] # root (HD0,4) # setup (HD0] # quit # reboot

That's probably what you want to do if you wish Windows to boot no longer,

"no longer"? That's a bit overstated, Felix. The OP's complaint was long on hyperbole and short on details. I read "non-bootable" and responded accordingly. What I left out was the obvious need, once booted into Linux, to reinstall the bootloader so it picks up and write a proper entry for the Windows installation.

"Long on hyperbole"?? :-) Why should there be a need to reinstall any bootloader when grub was installed during the openSUSE installation? The config was prepared by yast and looks fine (after I've removed the superflous entries for the hidden winRE and the data partition). -- Per Jessen, Zürich (18.8°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Carl Hartung wrote:

On Thu, 05 May 2011 19:38:37 +0200 Per Jessen wrote:

<snipped>

...

"Long on hyperbole"?? :-)

Sorry, Per, but IMHO "it would make any newbie run away screaming." qualifies as hyperbole. Not that I don't empathize! ;-)

I think you'll need to use Windows' "recovery console" to repair the boot system on that side. Then, after using the install DVD to boot into the installed 11.4 system, use the full YaST2 bootloader installer to reinstall grub.

Let me describe the situation (which hasn't changed much since my first posting): openSUSE 11.4 installed fine apart from one minor bug, and it is also perfectly fine now. Windows 7 does no longer boot (when selected from grub), but complains that "BOOTMGR is missing". I have tried using the windows repair disc (created when Windows7 was still running), but that stops after not recognising any Windows partitions and the suggesting I "load drivers". Grub is working fine, except for not being to chainload Windows7. I don't think I'm overstating anything when I say that an openSUSE newbie would run away screaming (and swearing) after having openSUSE quite literally screw up his or her system like this. I'm pulling out what is left of my hair, and I don't even NEED Windows7 (this is purely an exercise with fresh hardware). If nothing else, 11.4 has here clearly and grossly violated the "it just works" idea. Anyway, I've recorded the situation in bug#692047, maybe a kind soul will pick it up - I can't guarantee this system will be around for late follow-ups, but then I guess we'll just have to close it as POORQUALITY (apologies for frustrations showing). -- Per Jessen, Zürich (14.3°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 2011/05/05 18:34 (GMT+0200) Per Jessen composed:

Michael S. Dunsavage wrote:

...

Well it's always a risk when dual booting that the MBR would be overwritten.

I'm guessing it must have been, but grub is wokring fine - it's only when I tell grub to chainload from the Windows partition that I get the BOOTMGR is missing message. I guess whatever is in the first block of the Windows partition is this bootmgr, but I don't understand how it got screwed up just by me resizing the partition (as per yast's suggestion).

I don't know if Vista & 7 are different, I suspect not, but XP writes several bytes just in front of the MBR table beginning at 0x01B7. It can get very bent out of shape when it's changed or missing. Since I never allow Grub to write to any MBR I don't have any direct experience with what Grub may or may not write in that location. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Thu, 05 May 2011 14:33:33 +0200 Per Jessen wrote:

Per Jessen wrote:

Well, a little more than that - I can boot my newopenSUSE 11.4, but Windows can't be booted anymore. (BOOTMGR is missing). I haven't done one of these installations (Linux onto an system with an working Windows installation including shrinking of NTFS partition) in years, any chance I'm doing something wrong?

I've had this problem some time ago when I tried to install OpenSuse 11.2 on a Windows 7 laptop. I can't remember exacty how I solved he problem but I think I solved it by copying bootmgr which was located on the D drive (Windows) to the C drive. Somehow the bootmgr on the C drive was missing. I used Knoppix for this purpose. HTH , Martin -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 2011/05/06 12:12 (GMT+0200) Per Jessen composed:

The Windows Repair Disc enabled me to get the windows boot manager back. The question still remains though: how did the installation of openSUSE screw up the windows boot manager? Any chance that it resides at the end of a partition and therefore got removed when the partition was resized?

See https://bugzilla.novell.com/show_bug.cgi?id=692047

I didn't see you respond to http://lists.opensuse.org/opensuse/2011-05/msg00127.html Alternatively, the bootmgr file may need to be in a certain location in the partition that got changed to an invalid location or had a checksum change caused by the resize process. Did you think to try resizing using the built-in Windows resizer? I would expect a native tool like that to be more reliable than a foreign one from a competitive product. You did back up first as recommended, right? ;-) -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Per Jessen wrote:

Per Jessen wrote:

...

Yesterday I received two new laptops, both Toshiba L675 with Windows 7. This morning I tried to install openSUSE 11.4 without touching any of the default settings. The installation went fine, but the system was not able to boot up afterwards (after stage1 had finished). I suspect graphics is the problem as a saw a weird dotted line being written across the splash-screen before the system halted. Does this sound familiar to anyone?

The Windows Repair Disc enabled me to get the windows boot manager back. The question still remains though: how did the installation of openSUSE screw up the windows boot manager? Any chance that it resides at the end of a partition and therefore got removed when the partition was resized?

Explanation (courtesy of Stefan Quandt, thank you): Apparently one no longer boots a Windows partition directly, one is now supposed to boot from the boot manager partition, which appears to be called WinRE. YaST doesn't quite understand this (just like me), so instead of configuring the boot loader to boot from the WinRE partition, YaST configured it to boot from the Windows partition. Clearly something we need to fix so people (who need Windows) don't stumble over this again. -- Per Jessen, Zürich (17.1°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Roger Oberholtzer wrote:

On Sat, 2011-05-07 at 11:05 +0200, Per Jessen wrote:

...

Explanation (courtesy of Stefan Quandt, thank you):

Apparently one no longer boots a Windows partition directly, one is now supposed to boot from the boot manager partition, which appears to be called WinRE. YaST doesn't quite understand this (just like me), so instead of configuring the boot loader to boot from the WinRE partition, YaST configured it to boot from the Windows partition.

Clearly something we need to fix so people (who need Windows) don't stumble over this again.

I installed 11.4 on laptop with 64-bit windows 7 already installed. It installed properly, and GRUB has entries for the Windows boot, which works fine. In fact, GRUB has two windows boot entries - one for each windows partition. This is on a new Sony laptop. So maybe Toshiba are up to something with how they set up the disk.

The grub entries look like this:

title windows 1 rootnoverify (hd0,1) chainloader +1

title windows 2 rootnoverify (hd0,2) chainloader +1

That is how mine was setup too, but the entry for the boot manager was missing: title windows 7 rootnoverify (hd0,0) chainloader +1

As you had made backup Windows disks, you obviously had set up Windows. So I cannot offer any suggestions.

How did you shrink the Windows partition?

It was a vanilla installation, all default options except I unticked "Automatic configuration".

IIRC, I was suspicious of letting Linux do it. So I did this in Windows before the install. I had to disable a disk swap file so the shrinking would free up enough of the disk. This is a known Windows 7 partition resizing issue.

What issue is that - that the boot manager isn't configured in grub instead of the "actual" partitions? AFAICT, I had no problem with the resizing, YaST carved out about 80Gb from the first Windows partition. -- Per Jessen, Zürich (25.2°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org