Page 1 of 2 12 LastLast
Results 1 to 10 of 23

Thread: booting up with Wingrub without success after version 10 SP4

Hybrid View

  1. booting up with Wingrub without success after version 10 SP4

    Hello,

    I am asking help for Suse Linux Entreprise Destop or Server, version 11.

    Working with old generation Thinkpad T40 from IBM x85 infrastructure, I need to set up SLED version 11, booting with WinGrub without success. It seems that Wingrub can't recognize file system from version 11 and above.

    The latest version with success is version 10 SP4. Wingrub can access booting files in linux partition so that it boots.

    Any ideas to solve the issue?

    Background: for Thinkpad laptop, there is hidden partition to restore windows system installation when needed, which is only accessible by original MBR written by IBM. Thus any third party system, such as Suse, it should not overwrite MBR by Grub, otherwise no chance to recover such hidden partition function to restore windows installation.

  2. Re: booting up with Wingrub without success after version 10

    Hi
    In the final summary screen you can select where to install, I'm guessing your disk layout uses an extended partition, perhaps a /boot for SLE. I would suggest setting to either use /boot or the extended partition.

    Perhaps if you provide the output from the following command can give some more guidence;
    Code:
    fdisk -l
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  3. Re: booting up with Wingrub without success after version 10

    Quote Originally Posted by malcolmlewis View Post
    Hi
    In the final summary screen you can select where to install, I'm guessing your disk layout uses an extended partition, perhaps a /boot for SLE. I would suggest setting to either use /boot or the extended partition.

    Perhaps if you provide the output from the following command can give some more guidence;
    Code:
    fdisk -l
    Here below is the output:
    Disk /dev/hda: 157.4 GB, 157456221184 bytes
    240 heads, 63 sectors/track, 20339 cylinders
    Units = cylinders of 15120 * 512 = 7741440 bytes

    Device Boot Start End Blocks Id System
    /dev/hda1 * 1 1490 11264368+ 7 HPFS/NTFS
    /dev/hda2 1491 20339 142498440 f W95 Ext'd (LBA)
    /dev/hda5 1491 6976 41474128+ 7 HPFS/NTFS
    /dev/hda6 6977 7085 824008+ 82 Linux swap / Solaris
    /dev/hda7 7086 7695 4611568+ 83 Linux
    /dev/hda8 7696 8914 9215608+ 83 Linux
    /dev/hda9 8915 19620 80937328+ 7 HPFS/NTFS
    /dev/hda10 19621 20339 5435608+ b W95 FAT32

    Furthermore, to be precise, with SLE 10, I installed Wingrub to Windows XP boot.ini so that the booting from windows will break and load grub menu to boot SLE 10. But this can't work when I upgrade to SLE 11.

    So how about the reason?

  4. Re: booting up with Wingrub without success after version 10

    Quote Originally Posted by pi_david View Post
    Here below is the output:
    Disk /dev/hda: 157.4 GB, 157456221184 bytes
    240 heads, 63 sectors/track, 20339 cylinders
    Units = cylinders of 15120 * 512 = 7741440 bytes

    Device Boot Start End Blocks Id System
    /dev/hda1 * 1 1490 11264368+ 7 HPFS/NTFS
    /dev/hda2 1491 20339 142498440 f W95 Ext'd (LBA)
    /dev/hda5 1491 6976 41474128+ 7 HPFS/NTFS
    /dev/hda6 6977 7085 824008+ 82 Linux swap / Solaris
    /dev/hda7 7086 7695 4611568+ 83 Linux
    /dev/hda8 7696 8914 9215608+ 83 Linux
    /dev/hda9 8915 19620 80937328+ 7 HPFS/NTFS
    /dev/hda10 19621 20339 5435608+ b W95 FAT32

    Furthermore, to be precise, with SLE 10, I installed Wingrub to Windows XP boot.ini so that the booting from windows will break and load grub menu to boot SLE 10. But this can't work when I upgrade to SLE 11.

    So how about the reason?
    Hi
    So if you install the bootloader into hda2 at the summary (it should set the bootflag[*]) and then add a custom chainloader entry for windows and just use grub, if you need to do a recover then reset the bootflag to hda1? Have no experience with wingrub (or much with XP either)... I've always used grub to control booting...
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  5. Re: booting up with Wingrub without success after version 10

    Quote Originally Posted by malcolmlewis View Post
    Hi
    So if you install the bootloader into hda2 at the summary (it should set the bootflag[*]) and then add a custom chainloader entry for windows and just use grub, if you need to do a recover then reset the bootflag to hda1? Have no experience with wingrub (or much with XP either)... I've always used grub to control booting...
    Hello,

    thank you for your analyse to help.

    I have little knowledge about grub, neither booting. so i try to understand and explain my concerns.

    My core question is to protect original MBR by IBM which was damaged one time, that's why I am doing all best not to touch MBR again.

    In case of only windows, booting sequence will be: Power->BIOS->MBR(IBM)->windows (boot.ini)
    In case of multi system, booting sequence should be: Power->BIOS->MBR(IBM?)->Grub or Wingrub(windows boot.ini with integrated grub to break)

    So my question is: by installing bootloader into hda2, does it change anything in MBR? if not, i don't understand how MBR(IBM) can find grub booting files...

    What would it mean to reset bootflag hda2 or hda1? something is changing?

  6. Re: booting up with Wingrub without success after version 10 SP4

    On Thu 26 Apr 2018 06:14:02 AM CDT, pi david wrote:

    malcolmlewis;52344 Wrote:
    > Hi
    > So if you install the bootloader into hda2 at the summary (it should
    > set the bootflag ) and then add a custom chainloader entry for
    > windows and just use grub, if you need to do a recover then reset the
    > bootflag to hda1? Have no experience with wingrub (or much with XP
    > either)... I've always used grub to control booting...


    Hello,

    thank you for your analyse to help.

    I have little knowledge about grub, neither booting. so i try to
    understand and explain my concerns.

    My core question is to protect original MBR by IBM which was damaged one
    time, that's why I am doing all best not to touch MBR again.

    In case of only windows, booting sequence will be:
    Power->BIOS->MBR(IBM)->windows (boot.ini)
    In case of multi system, booting sequence should be:
    Power->BIOS->MBR(IBM?)->Grub or Wingrub(windows boot.ini with integrated
    grub to break)

    So my question is: by installing bootloader into hda2, does it change
    anything in MBR? if not, i don't understand how MBR(IBM) can find grub
    booting files...

    What would it mean to reset bootflag hda2 or hda1? something is
    changing?


    Hi
    In your case/description it would be;

    Power->BIOS->Extended Partition (with bootcode)->Grub (with chainloader
    entry for windows)

    So it just implements in your words the MBR in a different location,
    you would see the boot flag (The asterisk *) move to hda2 all done by
    the installer. You just have to look at the summary screen and change
    as required to where the bootloader goes, if not sure take a picture
    and post back here.

    If you needed to boot into windows repair, you can boot into linux or a
    live system and via fdisk change the boot flag back to hda1.

    --
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    openSUSE Leap 42.3|GNOME 3.20.2|4.4.126-48-default
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!


  7. Re: booting up with Wingrub without success after version 10

    Quote Originally Posted by malcolmlewis View Post
    Hi
    In your case/description it would be;

    Power->BIOS->Extended Partition (with bootcode)->Grub (with chainloader
    entry for windows)

    So it just implements in your words the MBR in a different location,
    you would see the boot flag (The asterisk *) move to hda2 all done by
    the installer. You just have to look at the summary screen and change
    as required to where the bootloader goes, if not sure take a picture
    and post back here.

    If you needed to boot into windows repair, you can boot into linux or a
    live system and via fdisk change the boot flag back to hda1.

    --
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    openSUSE Leap 42.3|GNOME 3.20.2|4.4.126-48-default
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!
    if i understand well the sequence, you are saying, the machine can jump from BIOS directly to extended partition without reading MBR, am I right?

    I was told that BIOS reads always MBR then MBR reads bootflag...that's why mostly i see linux grub will be installed to MBR, but i don't understand how it would be even though i do see another option to install to extened partition.

  8. Re: booting up with Wingrub without success after version 10 SP4

    On Fri 27 Apr 2018 01:44:02 AM CDT, pi david wrote:

    malcolmlewis;52375 Wrote:
    > Hi
    > In your case/description it would be;
    >
    > Power->BIOS->Extended Partition (with bootcode)->Grub (with
    > chainloader entry for windows)
    >
    > So it just implements in your words the MBR in a different location,
    > you would see the boot flag (The asterisk *) move to hda2 all done by
    > the installer. You just have to look at the summary screen and change
    > as required to where the bootloader goes, if not sure take a picture
    > and post back here.
    >
    > If you needed to boot into windows repair, you can boot into linux or
    > a live system and via fdisk change the boot flag back to hda1.
    >


    if i understand well the sequence, you are saying, the machine can jump
    from BIOS directly to extended partition without reading MBR, am I
    right?

    I was told that BIOS reads always MBR then MBR reads bootflag...that's
    why mostly i see linux grub will be installed to MBR, but i don't
    understand how it would be even though i do see another option to
    install to extened partition.
    Hi
    No, the BIOS reads/looks for the bootflag (asterisk) and reads that
    partition for the boot code on where to boot from.

    --
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SLED 15 RC3 | GNOME 3.26.2 | 4.12.14-16-default
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!


  9. Re: booting up with Wingrub without success after version 10

    Quote Originally Posted by malcolmlewis View Post
    Hi
    No, the BIOS reads/looks for the bootflag (asterisk) and reads that
    partition for the boot code on where to boot from.

    --
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SLED 15 RC3 | GNOME 3.26.2 | 4.12.14-16-default
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!
    According to this wiki, it looks that bootflag is inside MBR. if so, changing bootflag, it means changing MBR, maybe not overwrite.
    https://en.wikipedia.org/wiki/Boot_flag

  10. Re: booting up with Wingrub without success after version 10 SP4

    On Fri 27 Apr 2018 07:04:01 AM CDT, pi david wrote:

    malcolmlewis;52379 Wrote:
    > Hi
    > No, the BIOS reads/looks for the bootflag (asterisk) and reads that
    > partition for the boot code on where to boot from.
    >


    According to this wiki, it looks that bootflag is inside MBR. if so,
    changing bootflag, it means changing MBR, maybe not overwrite.
    https://en.wikipedia.org/wiki/Boot_flag


    Hi
    Yes, so your original bootcode on hda1 will be untouched.

    Again, just make sure you review the summary screen on what is being
    installed where.....

    --
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SLES 15 RC3 | GNOME 3.26.2 | 4.12.14-16-default
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!


Page 1 of 2 12 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •