Page 3 of 16 FirstFirst 1234513 ... LastLast
Results 21 to 30 of 156

Thread: Two major problems with dual boot installation of openSuSE 11.1 and Windows 7

  1. #21

    Default Re: Two major problems with dual boot installation of openSuSE 11.1 and Windows 7

    Quote Originally Posted by caf4926 View Post
    Until you get suse booting again that will be difficult.

    Switching the boot flag to the extended partition is done with Parted Magic
    My guess it's on sda1 now
    But we didn't get to see your disk info. You can get that from parted magic too. Open the terminal and type: fdisk -l
    (that's a lower case L)

    You will have to toggle the flag of the current partition and set it to extended
    Then carefully follow the grub guide to install grub again, adjusting the numbering as appropriate for your settings.

    Actually - if you post the fdisk info and the part that answers (find /boot/grub/menu.lst) we can tell you exactly how to proceed if you can't figure it.
    OK, here's the output of 'fdisk -l'
    ================================================
    Disk /dev/sda: 320.0 GB, 320072933375 bytes
    255 heads, 63 sectors/track, 38913 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifiers: 0xc20dd326

    Device Boot Start End Blocks Id System
    /dev/sda1 * 1 52 409600 27 Unknown
    Partition 1 does not end on cylinder boundary.
    /dev/sda2 52 19556 156672000 7 HPFS/NTFS
    /dev/sda3 * 19557 38913 155485102+ f W95 Ext'd (LBA)
    /dev/sda5 19557 19818 2104483+ 82 Linux swap / Solaris
    /dev/sda6 19819 22429 20972826 83 Linux
    /dev/sda7 22430 38913 132407698+ 83 Linux

  2. #22
    Join Date
    Jun 2008
    Location
    The English Lake District. UK - GMT/BST
    Posts
    36,725
    Blog Entries
    20

    Default Re: Two major problems with dual boot installation of openSuSE 11.1 and Windows 7

    Quote Originally Posted by giavvns View Post
    OK, here's the output of 'fdisk -l'
    ================================================
    Disk /dev/sda: 320.0 GB, 320072933375 bytes
    255 heads, 63 sectors/track, 38913 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifiers: 0xc20dd326

    Device Boot Start End Blocks Id System
    /dev/sda1 * 1 52 409600 27 Unknown
    Partition 1 does not end on cylinder boundary.
    /dev/sda2 52 19556 156672000 7 HPFS/NTFS
    /dev/sda3 * 19557 38913 155485102+ f W95 Ext'd (LBA)
    /dev/sda5 19557 19818 2104483+ 82 Linux swap / Solaris
    /dev/sda6 19819 22429 20972826 83 Linux
    /dev/sda7 22430 38913 132407698+ 83 Linux
    Re-Install Grub Quickly with Parted Magic

    OK you have a boot flag on both. The one on sda3 is the one to keep, you can right click sda1 in parted magic's Partition manager and manage boot flags and uncheck the boot box

    Your suse root partition is sda6
    so when you follow the guide to reinstall grub and do: find /boot/grub/menu.lst
    It should report: (hd0,5)

    so next you enter: root (hd0,5)

    then: setup (hd0)

    It should then report something like: Checking if /boot/grub/stage1 exists ... yes Computer finally returns this-- Succeeded.......Done

    You can now quit and reboot
    And grub will be back

    You will then need to add or edit your entry for windows. In suse open a terminal and if you use gnome enter:
    Code:
    gnomesu gedit /boot/grub/menu.lst
    If you se KDE enter:
    Code:
    kdesu kwrite /boot/grub/menu.lst
    Enter password when asked, and we can now edit the file.

    I suspect your entry is something like:

    Code:
    ###Don't change this comment - YaST2 identifier: Original name: windows###
    title Windows
        rootnoverify (hd0,1)
        chainloader +1
    But it needs to be

    Code:
    ###Don't change this comment - YaST2 identifier: Original name: windows###
    title Windows
        rootnoverify (hd0,0)
        chainloader +1
    edit/add as required
    save and quit

    reboot and try windows
    Leap 15.1_KDE
    My Articles Was I any help? If yes: Click the star below

  3. #23
    Carlos E. R. NNTP User

    Default Re: Two major problems with dual boot installation of openSuSE 11.1and Windows 7

    On 2010-09-27 14:36, caf4926 wrote:


    > OK you have a boot flag on both. The one on sda3 is the one to keep,
    > you can right click sda1 in parted magic's Partition manager and manage
    > boot flags and uncheck the boot box


    Yes

    > Your suse root partition is sda6
    > so when you follow the guide to reinstall grub and do: find
    > /boot/grub/menu.lst
    > It should report: (hd0,5)


    No, it should be sda3. Ie, the partition marked as bootable is the one that has to contain grub
    (stage 2). Doesn't have to be the same partition that contains the menu.lst file, that's different.

    Ie: grub has to go to sda3, and menu.lst to sda6.

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 11.2 x86_64 "Emerald" at Telcontar)

  4. #24
    Join Date
    Jun 2008
    Location
    The English Lake District. UK - GMT/BST
    Posts
    36,725
    Blog Entries
    20

    Default Re: Two major problems with dual boot installation of openSuSE 11.1 and Windows 7

    The only potential issue which I'm not 100% sure about is if grub will complain because your windows partition is so big it throws grub over a limit.
    Perhaps other will know more.
    I would try it
    We can always try something else if plan A doesn't work.
    Leap 15.1_KDE
    My Articles Was I any help? If yes: Click the star below

  5. #25

    Default Re: Two major problems with dual boot installation of openSuSE 11.1and Windows 7

    Quote Originally Posted by Carlos E. R. View Post
    Leave the MBR as is, untouched (ie, generic boot code as installed by windows. Install grub in a free primary (or extended (not logical)) partition. Mark that partition as bootable. Unmark the previously marked bootable partition.
    I will never agree with that. I believe this method has more inconvenients than advantages and the way openSUSE handles this is more political than technical. But anyway ... I don't want to repeat after me over an over. And since, I have only Unixes and never Windows, I guess my opinion doesn't really count.

    I move the discussion about the script here: Looking for Grub and Windows bootloader in all partitions.

  6. #26
    Join Date
    Jun 2008
    Location
    The English Lake District. UK - GMT/BST
    Posts
    36,725
    Blog Entries
    20

    Default Re: Two major problems with dual boot installation of openSuSE 11.1and Windows 7

    No, it should be sda3. Ie, the partition marked as bootable is the one that has to contain grub
    (stage 2). Doesn't have to be the same partition that contains the menu.lst file, that's different.

    Ie: grub has to go to sda3, and menu.lst to sda6.
    What!

    There are too many darn cooks in this Kitchen. Carlos, if you know better I suggest you write a walk thru for the OP. Spell it out A-Z
    Leap 15.1_KDE
    My Articles Was I any help? If yes: Click the star below

  7. #27
    Carlos E. R. NNTP User

    Default Re: Two major problems with dual boot installation of openSuSE 11.1and Windows 7

    On 2010-09-27 16:36, caf4926 wrote:
    >
    >> No, it should be sda3. Ie, the partition marked as bootable is the one
    >> that has to contain grub
    >> (stage 2). Doesn't have to be the same partition that contains the
    >> menu.lst file, that's different.
    >>
    >> Ie: grub has to go to sda3, and menu.lst to sda6.
    >>

    > What!


    It is how I have my laptop.

    The reasoning is that the MBR generic code can only boot a primary partition marked bootable, and
    sda6 is a logical. Marking it as bootable will not work, as far as I know.

    So:

    MBR: Generical. Boots a primary's boot code

    sda3: Contains a boot sector with grub, plus the stages, placed in the next sectors (hidden and
    fixed position). It is these "stage" codes wich contains the info to read a filesystem, and knows it
    has to read data in (sda6)/boot.

    sda6: contains /boot directory.

    As sda3 is a extended, it can not contain files.


    > There are too many darn cooks in this Kitchen. Carlos, if you know
    > better I suggest you write a walk thru for the OP. Spell it out A-Z


    That's what I can not do, walk all the steps... I seldom have that kind of patience O:-)

    But yast can install that way. It did so for me. And of course, it can be done in CLI, but I'm not
    fluent with grub's CLI options.

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 11.2 x86_64 "Emerald" at Telcontar)

  8. #28

    Default Re: Two major problems with dual boot installation of openSuSE 11.1and Windows 7

    Quote Originally Posted by Carlos E. R. View Post
    The reasoning is that the MBR generic code can only boot a primary partition marked bootable, and sda6 is a logical. Marking it as bootable will not work, as far as I know.
    He! he! I'm glad to read that. But try to tell it to the YaST developpers, as they haven't understood (or accepted) this concept and still instist of activate the root partition without caring whether it is a primary or a logical one. I should add that YaST (by default, of course!) writes a generic bootcode to the MBR without checking (or double checking) if there is one (an only one) bootflag set on a primary (or the extended ) partition ... which ends up - in some cases - in an absolute no-boot situation.

    more about that (for french readers):
    Grub pour les nuls

  9. #29
    Join Date
    Mar 2010
    Location
    Austin - Texas
    Posts
    10,140
    Blog Entries
    48

    Smile Re: Two major problems with dual boot installation of openSuSE 11.1and Windows 7

    I thought that I had also mentioned that you can not boot from a logical partition before? The Master Boot Record can only contain records for four partitions, any which could be bootable, but that is only for partitions 1 - 2 - 3 - 4, not 5 - 6 - 7 or however high they go in a logical partition. If you want to load openSUSE in a Logical partition, you must load Grub into the MBR. If you want to use a generic MBR, openSUSE must be in a primary partition numbered 1 - 2 - 3 or 4. This last setup is better when using Windows on the same partition. By just changing the active partition, you can get Windows running directly if need be and no need to play with the MBR when it is generic.

    Thank You,
    My Blog: https://forums.opensuse.org/blogs/jdmcdaniel3/

    Software efficiency halves every 18 months, thus compensating for Moore's Law

    Its James again from Austin, Texas

  10. #30
    Carlos E. R. NNTP User

    Default Re: Two major problems with dual boot installation of openSuSE 11.1and Windows 7

    On 2010-09-29 03:06, jdmcdaniel3 wrote:
    >
    > I thought that I had also mentioned that you can not boot from a logical
    > partition before? The Master Boot Record can only contain records for
    > four partitions, any which could be bootable, but that is only for
    > partitions 1 - 2 - 3 - 4, not 5 - 6 - 7 or however high they go in a
    > logical partition.


    Yes.

    > If you want to load openSUSE in a Logical partition,
    > you must load Grub into the MBR. If you want to use a generic MBR,
    > openSUSE must be in a primary partition numbered 1 - 2 - 3 or 4.


    No, that is not so. :-)

    You can have generic boot code in the MBR, a partition marked bootable, and that partition holding
    grub. Then that grub can in turn boot linux in any primary or logical partition (and it doesn't need
    to be the one holding grub). I know it is true, because my laptop is setup that way.


    MBR
    P1
    P2
    P2 * + Grub --> boots any partition you like. Like number 29.
    P3


    > This
    > last setup is better when using Windows on the same partition. By just
    > changing the active partition, you can get Windows running directly if
    > need be and no need to play with the MBR when it is generic.


    Yep.

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 11.2 x86_64 "Emerald" at Telcontar)

Page 3 of 16 FirstFirst 1234513 ... LastLast

Posting Permissions

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