<---- template headericclude ----->
set up windows on a seperate hdd help how to
FedoraForum.org - Fedora Support Forums and Community
Results 1 to 8 of 8
  1. #1
    F.User_4_Life Guest

    set up windows on a seperate hdd help how to

    plain and simple i have installed on a 40 gig hdd windows xp and need to know how to make the grub from linux the master mbr. theres 2 mbr one on the linux drive and one on the windows and i need to know how to remove or dissable the windows one and add the other drive to the start up list in grub so i may select the windows. im trying to set up my pc for school use and need help on fixing this problem.

    im a bit confused because i read how to's on seting up the grub and when i do the fdisk commands fdisk does not exhist on my pc dont ask i dont know where to find it. i dont care to use fdisk but what ever i just need to edit the grub to be root mbr and add the windows to the boot order.

  2. #2
    Join Date
    Jun 2006
    Posts
    7,544
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Hello F.User_4_Life,

    That's a very common predicament. It usually can be made to work. But the answer is hard to say without some more information from your computer. It's also not clear (to me, anyway) what is booting right now (XP?, Fedora?, neither?). So I recommend that you make it clearer to your readers exactly what happens when you boot your computer now. Then, if Fedora is booting, post some information from it.

    I know you have had some trouble getting the partition list with fdisk. But I assure you that fdisk exists in Fedora. If this is Fedora 9 that you're talking about (your signature is the only clue), then it matters to fdisk how you are logged in to the terminal or how you type the command.

    The results of these terminal commands will be helpful to anyone who wants to help you. In Fedora 9, open a terminal and...
    Code:
    su
    /sbin/fdisk -l
    cat /boot/grub/grub.conf
    It's hard to tell in some fonts, but that fdisk option is a lower-case letter L and not a number one.

  3. #3
    F.User_4_Life Guest
    [root@Hydroponikz KDE]# /sbin/fdisk -l

    Disk /dev/sda: 320.0 GB, 320072933376 bytes
    255 heads, 63 sectors/track, 38913 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x2850284f

    Device Boot Start End Blocks Id System
    /dev/sda1 * 1 25 200781 83 Linux
    /dev/sda2 26 38913 312367860 8e Linux LVM

    Disk /dev/dm-0: 317.7 GB, 317726916608 bytes
    255 heads, 63 sectors/track, 38628 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x00000000

    Disk /dev/dm-0 doesn't contain a valid partition table

    Disk /dev/dm-1: 2080 MB, 2080374784 bytes
    255 heads, 63 sectors/track, 252 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x30307800

    Disk /dev/dm-1 doesn't contain a valid partition table

    Disk /dev/sdg: 250.0 GB, 250059350016 bytes
    255 heads, 63 sectors/track, 30401 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0xfc9a426e

    Device Boot Start End Blocks Id System
    /dev/sdg1 * 1 30401 244196001 7 HPFS/NTFS
    [root@Hydroponikz KDE]# cat /boot/grub/grub.conf
    # grub.conf generated by anaconda
    #
    # Note that you do not have to rerun grub after making changes to this file
    # NOTICE: You have a /boot partition. This means that
    # all kernel and initrd paths are relative to /boot/, eg.
    # root (hd0,0)
    # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
    # initrd /initrd-version.img
    #boot=/dev/sda
    default=0
    timeout=1
    splashimage=(hd0,0)/grub/splash.xpm.gz
    hiddenmenu
    title Fedora (2.6.27.21-78.2.41.fc9.x86_64)
    root (hd0,0)
    kernel /vmlinuz-2.6.27.21-78.2.41.fc9.x86_64 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
    initrd /initrd-2.6.27.21-78.2.41.fc9.x86_64.img
    title Fedora (2.6.27.19-78.2.30.fc9.x86_64)
    root (hd0,0)
    kernel /vmlinuz-2.6.27.19-78.2.30.fc9.x86_64 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
    initrd /initrd-2.6.27.19-78.2.30.fc9.x86_64.img
    title Fedora (2.6.25-14.fc9.x86_64)
    root (hd0,0)
    kernel /vmlinuz-2.6.25-14.fc9.x86_64 ro root=UUID=6ea483cf-b6b2-4c19-8206-b6aa9f5533fb rhgb quiet
    initrd /initrd-2.6.25-


    ok now what happens when i have the drive with the xp on it plugged in is that xp boots up the mbr for that drive is dominant over the other. i dont have hot swap support i disabled it.

    hope this helps

  4. #4
    Join Date
    Jun 2006
    Posts
    7,544
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Quote Originally Posted by F.User_4_Life

    ok now what happens when i have the drive with the xp on it plugged in is that xp boots up the mbr for that drive is dominant over the other.
    To me, there are two issues here. One is to make the Fedora drive boot when the XP drive is plugged in (I guess that means its an external USB drive). And the other unrelated issue is to make GRUB boot XP.

    First I don't think you are describing the sequence of events during booting accurately. It may help you to understand that better. See, XP does not "boot up the mbr" for its drive. What actually happens is that one of your drives is set to be first in the boot order in your computer's BIOS setup. At boot time, the BIOS finds that drive and loads the boot code of its master boot record into memory to be executed. After that happens, the booting sequence continues on. If the BIOS does not find that drive, it generally moves on to the next drive in the boot order. That may explain why XP boots when the XP drive is plugged in, and Fedora boots when the XP drive is not plugged in. Maybe you should get into your computer's BIOS setup and study the drive boot order. You might find that changing the Fedora drive to first will consistently boot Fedora regardless of the state of the XP drive.

    Next, if what I just said was correct, then adding a section to the grub.conf should allow GRUB to boot XP. Check the fdisk again after any BIOS changes. If, for example, the XP partition remains /dev/sdg1, then try this for XP in the grub.conf. Add it at the end.
    Code:
    title Windows XP
    rootnoverify (hd6,0)
    map (hd0) (hd6)
    map (hd6) (hd0)
    chainloader +1
    If after changes to the BIOS, the XP drive is no longer /dev/sdg, then change my example appropriately. If, just for example, the XP drive where to be /dev/sdb making the XP partition /dev/sdb1, then the grub.conf section for XP might be like this...
    Code:
    title Windows XP
    rootnoverify (hd1,0)
    map (hd0) (hd1)
    map (hd1) (hd0)
    chainloader +1
    See what I mean? You change it to whatever it needs to be. It's even okay to guess at the XP partition in the grub.conf. It does no harm to guess wrongly. But when you change it for the drive, change the drive number in all three places in the example like I did. Don't change the partition because according to the fdisk, the XP partition will be the first (and only) partition on the drive.

  5. #5
    F.User_4_Life Guest
    ok i checked my bios its not the problem it now boots for no reason into the linux

    [root@Hydroponikz KDE]# cat /boot/grub/grub.conf
    # grub.conf generated by anaconda
    #
    # Note that you do not have to rerun grub after making changes to this file
    # NOTICE: You have a /boot partition. This means that
    # all kernel and initrd paths are relative to /boot/, eg.
    # root (hd0,0)
    # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
    # initrd /initrd-version.img
    #boot=/dev/sda
    default=0
    timeout=1
    splashimage=(hd0,0)/grub/splash.xpm.gz
    hiddenmenu
    title Fedora (2.6.27.21-78.2.41.fc9.x86_64)
    root (hd0,0)
    kernel /vmlinuz-2.6.27.21-78.2.41.fc9.x86_64 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
    initrd /initrd-2.6.27.21-78.2.41.fc9.x86_64.img
    title Fedora (2.6.27.19-78.2.30.fc9.x86_64)
    root (hd0,0)
    kernel /vmlinuz-2.6.27.19-78.2.30.fc9.x86_64 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
    initrd /initrd-2.6.27.19-78.2.30.fc9.x86_64.img
    title Fedora (2.6.25-14.fc9.x86_64)
    root (hd0,0)
    kernel /vmlinuz-2.6.25-14.fc9.x86_64 ro root=UUID=6ea483cf-b6b2-4c19-8206-b6aa9f5533fb rhgb quiet
    initrd /initrd-2.6.25-14.fc9.x86_64.img
    [root@Hydroponikz KDE]# /sbin/fdisk -l

    Disk /dev/sda: 320.0 GB, 320072933376 bytes
    255 heads, 63 sectors/track, 38913 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x2850284f

    Device Boot Start End Blocks Id System
    /dev/sda1 * 1 25 200781 83 Linux
    /dev/sda2 26 38913 312367860 8e Linux LVM

    Disk /dev/dm-0: 317.7 GB, 317726916608 bytes
    255 heads, 63 sectors/track, 38628 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x00000000

    Disk /dev/dm-0 doesn't contain a valid partition table

    Disk /dev/dm-1: 2080 MB, 2080374784 bytes
    255 heads, 63 sectors/track, 252 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x30307800

    Disk /dev/dm-1 doesn't contain a valid partition table

    Disk /dev/sdb: 40.0 GB, 40020664320 bytes
    255 heads, 63 sectors/track, 4865 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0xf84ef84e

    Device Boot Start End Blocks Id System
    /dev/sdb1 * 1 4865 39078081 7 HPFS/NTFS

    Disk /dev/sdh: 250.0 GB, 250059350016 bytes
    255 heads, 63 sectors/track, 30401 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0xfc9a426e

    Device Boot Start End Blocks Id System
    /dev/sdh1 * 1 30401 244196001 7 HPFS/NTFS
    Note: sector size is 2048 (not 512)

    Disk /dev/sdi: 30.0 GB, 30005821440 bytes
    255 heads, 62 sectors/track, 926 cylinders
    Units = cylinders of 15810 * 2048 = 32378880 bytes
    Disk identifier: 0x20202020

    Device Boot Start End Blocks Id System
    /dev/sdi1 1 4 96264 0 Empty
    Partition 1 has different physical/logical beginnings (non-Linux?):
    phys=(0, 1, 1) logical=(0, 1, 2)
    Partition 1 has different physical/logical endings:
    phys=(2, 254, 63) logical=(3, 12, 21)
    Partition 1 does not end on cylinder boundary.
    /dev/sdi2 4 927 29206168 b W95 FAT32
    Partition 2 has different physical/logical beginnings (non-Linux?):
    phys=(3, 0, 1) logical=(3, 12, 22)
    Partition 2 has different physical/logical endings:
    phys=(911, 254, 62) logical=(926, 180, 59)
    [root@Hydroponikz KDE]#


    so i did the commands again and i dont know if theres a difference but it booted up in the linux no problem and both the drives were installed.

    my guess is that i just need to edit the grub.

  6. #6
    Join Date
    Jun 2006
    Posts
    7,544
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Quote Originally Posted by F.User_4_Life

    my guess is that i just need to edit the grub.
    I guess so, too. Figure out which partition in the fdisk partition list has the Windows boot loader files. Edit the grub.conf file and type in the lines for Windows at the end. Remember to include the appropriate map command lines since the partition with the Windows boot loader files will now be on a non-first drive.

  7. #7
    F.User_4_Life Guest
    sorry for not posting but i just installed vista extreame ed r2 on a 80 gig and there is the info i can boot into fedora no problem but here is the info i just want to know what u think i should do and exactly what do i type in the grub edit according to the info here below


    [KDE@Hydroponikz ~]$ su
    Password:
    [root@Hydroponikz KDE]# cat /boot/grub/grub.conf
    # grub.conf generated by anaconda
    #
    # Note that you do not have to rerun grub after making changes to this file
    # NOTICE: You have a /boot partition. This means that
    # all kernel and initrd paths are relative to /boot/, eg.
    # root (hd0,0)
    # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
    # initrd /initrd-version.img
    #boot=/dev/sda
    default=0
    timeout=1
    splashimage=(hd0,0)/grub/splash.xpm.gz
    hiddenmenu
    title Fedora (2.6.27.21-78.2.41.fc9.x86_64)
    root (hd0,0)
    kernel /vmlinuz-2.6.27.21-78.2.41.fc9.x86_64 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
    initrd /initrd-2.6.27.21-78.2.41.fc9.x86_64.img
    title Fedora (2.6.27.19-78.2.30.fc9.x86_64)
    root (hd0,0)
    kernel /vmlinuz-2.6.27.19-78.2.30.fc9.x86_64 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
    initrd /initrd-2.6.27.19-78.2.30.fc9.x86_64.img
    title Fedora (2.6.25-14.fc9.x86_64)
    root (hd0,0)
    kernel /vmlinuz-2.6.25-14.fc9.x86_64 ro root=UUID=6ea483cf-b6b2-4c19-8206-b6aa9f5533fb rhgb quiet
    initrd /initrd-2.6.25-14.fc9.x86_64.img
    [root@Hydroponikz KDE]# /sbin/fdisk -l

    Disk /dev/sda: 320.0 GB, 320072933376 bytes
    255 heads, 63 sectors/track, 38913 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x2850284f

    Device Boot Start End Blocks Id System
    /dev/sda1 * 1 25 200781 83 Linux
    /dev/sda2 26 38913 312367860 8e Linux LVM

    Disk /dev/dm-0: 317.7 GB, 317726916608 bytes
    255 heads, 63 sectors/track, 38628 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x00000000

    Disk /dev/dm-0 doesn't contain a valid partition table

    Disk /dev/dm-1: 2080 MB, 2080374784 bytes
    255 heads, 63 sectors/track, 252 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x30307800

    Disk /dev/dm-1 doesn't contain a valid partition table

    Disk /dev/sdb: 80.0 GB, 80026361856 bytes
    255 heads, 63 sectors/track, 9729 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x00005437

    Device Boot Start End Blocks Id System
    /dev/sdb1 * 1 9730 78148608 7 HPFS/NTFS
    [root@Hydroponikz KDE]#

  8. #8
    F.User_4_Life Guest
    thanks for the help i got it to work

Similar Threads

  1. etc on seperate partition?
    By ACiD GRiM in forum Using Fedora
    Replies: 3
    Last Post: 4th April 2009, 08:28 PM
  2. SAMBA - When to set up a seperate Server
    By sesproul in forum Servers & Networking
    Replies: 1
    Last Post: 13th May 2008, 04:53 AM
  3. ATI troubles + seperate monitor
    By Kyran in forum Hardware
    Replies: 2
    Last Post: 27th December 2006, 11:38 AM
  4. How to seperate the unseperable?
    By lower_wolf in forum Installation, Upgrades and Live Media
    Replies: 2
    Last Post: 28th August 2006, 03:01 AM
  5. Seperate partitions
    By edkilp in forum Installation, Upgrades and Live Media
    Replies: 5
    Last Post: 17th July 2004, 07:12 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
[[template footer(Guest)]]