[ale] Recovering dual boot on installed systems

John Mills johnmills at speakeasy.net
Tue Jan 25 16:44:52 EST 2011


Cornelius -

Thanks for the pointers. I only see a console login with the 'Recovery' 
package I started. SLES does have a "Yast" module: that's where I did the 
damage! I'll make some notes about the "sleeping" boot configuration then 
step back into SLES and see if I can undo the curse.

  - Mills

On Tue, 25 Jan 2011, Cornelis van Dijk wrote:

> I thought the "Rescue" system has a bootloader section. You probably
> need to know the devices and partitions you want to repair, such as
> /dev/sda1 etc, and where to find vmlinuz and initrd (probably in
> /boot).

> I am not familiar with SLES, does that not have a "Yast" module? If so
> you could start the dual boot from SLES. You probably still would have
> to know the items mentioned above.

> Hope this helps, Cor

> On 1/25/11, John Mills <johnmills at speakeasy.net> wrote:

>> I was rearranging the boot setup but <OOPS/> ran my changes when booted
>> into SLES. &8-( Now I can't figure out how to re-activate the dual boot.

>> I can start the system from the openSuSE installation DVD in 'Rescue' mode
>> and mount and chroot to its partitions, but I don't know how to re-write
>> the boot block from that viewpoint. I expect I could also mount the SLES
>> partition and edit the 'grub' files but I'm not sure what I need to do
>> there.


More information about the Ale mailing list