remove grub from extended partition

English Install/Boot/Login
1

I noticed an odd occurance when hibrinating my Laptop after a clean Suse 11.1 install. After openSuse attempts a hibernate (guessing with swsusp?) when I recover from hibernation I see grub load…my kernel commands then a clean recovery from my hibernation state.

Below are my errors that I think caused this? Thinking this may make the fix easier to diagnosis.

I mistakenly installed grub on an extended partition (/dev/sda7) instead of the MBR. I wanted grub in the MBR so I can still boot an Windows OS. I did get a Bootloader error during the Suse install but after a reboot(no options like Failsafe or Windows) Suse came up and I installed grub to MBR from Yast.
Now when I boot I can select Suse, Failsafe or Windows.

How do I safely remove grub from my /dev/sda7 partition without losing data/corrupting my drive?

Also I have an IBM Thinkpad A22m and don’t care about the Thinkpad button so I thought it was safe to install grub in my MBR… SuSE release notes mentioned writing grub to the MBR on Lenovo laptaps will inactivate the Thinkpad button.

Sorry for typing so much but there were a lot of details.

2

You don’t need to remove grub from the sda7 boot sector. Actually, there is no way to remove boot code from an MBR or a boot sector except for over-writing it with something else (e.g., zeroes). But unless that boot sector is called (“chainloaded”) from other boot code, it will just be there harmlessly doing nothing.

3

Thanks for the reply.

So is the following below normal for swsusp? I have been using apm (acpi=off) which worked just fine for many years.

After openSuse attempts a hibernate (guessing with swsusp?) when I recover from hibernation I see grub load…my kernel commands then a clean recovery from my hibernation state.