Find the answer to your Linux question:
Page 2 of 3 FirstFirst 1 2 3 LastLast
Results 11 to 20 of 25
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #11

    This is a multi-problem!

    If you have windows2000 installed, add an sata drive and install xp, windows gets confused.
    Because xp sees the partitions in a different way and calls them otherwise.
    I do not know if it has anything to do with sata drives.
    If you are booting in windows, you are already past the linux boot manager.
    And windows looks for the files boot.ini and ntldr.
    If boot.ini points at the wrong partition he cannot find ntldr en you get the message.

    You can try to remove the sata drive and look what happens.
    Or do an xp install, but without installing and see what partitions xp finds and how he calls them.
    And maybe you should edit your boot.ini.

    Basically it is not a linux problem but a windows problem.
    But with such a multiboot system maybe linux gets also a bit off-track!

  2. #12
    Yancek,
    here is the device.map from Suse 11.2:

    nova-bane:/boot/grub # cat device.map
    (fd0) /dev/fd0
    (hd2) /dev/disk/by-id/ata-SAMSUNG_HD502HI_S1VZJ90S225155
    (hd1) /dev/disk/by-id/ata-SAMSUNG_HD501LJ_S0MUJDSP900048
    (hd0) /dev/disk/by-id/ata-Hitachi_HDS721616PLAT80_PV6904ZF072UZN
    nova-bane:/boot/grub #

    And here are Windows partitions that I mounted manualy:

    nova-bane:/boot/grub # mount
    /dev/sdb2 on / type ext4 (rw,acl,user_xattr)
    proc on /proc type proc (rw)
    sysfs on /sys type sysfs (rw)
    debugfs on /sys/kernel/debug type debugfs (rw)
    udev on /dev type tmpfs (rw)
    devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
    /dev/sda7 on /tmp type ext4 (rw)
    fusectl on /sys/fs/fuse/connections type fusectl (rw)
    securityfs on /sys/kernel/security type securityfs (rw)
    gvfs-fuse-daemon on /home/branislav/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=branislav)
    /dev/sda1 on /windows/D type fuseblk (rw,allow_other,default_permissions,blksize=4096)
    /dev/sda6 on /windows/G type vfat (rw,uid=1000,gid=100)
    /dev/sdc2 on /windows/F type vfat (rw,uid=1000,gid=100)
    nova-bane:/boot/grub #

    This shows that there is no problem with mapping of devices.
    Also - as somebody here suggested, I made a Super GRUB CD, and booted Suse 10.3 from /dev/sda2.
    So it is clear - no problem with device map, no problem with Suse 10.3 partition. This shows that problem is somewhere else...
    Thanks for help everyone!

  3. #13

    This one may really sound silly.

    I haven't succeeded yet to teach myself this a first line defence. Thunderbird reported your post of 10:05 AM today.

    The mapping says the houses are built where they are meant to be. So the postman will get the right one if the address is right on the letter. I think this was the issue from the start, but yancek was correct in asking you to check this.

    You are also correct in that the problem lies elsewhere. Now, here's the silly one.

    Make a list like naughts an crosses, draw the raster. Start with the lowest/first disc in numbering for say GRUB. Make a column of these. The next column does it for SUSE and another one. The fourth column holds the contents of each. This is important since you have different discs. You have three calling systems; the sdc type, the (hd0) type and the (hd1,0) type. Where does your MBR call boot loaders or pointers to boot loaders?

    Here's the kicker. You will need two (2) of these rasters. Set up one for what the situation should be. The other one reports to you what you do actually have. This can be very confusing at times. Be careful. Lay it out exactly. Nitpick it to death. Compare the two rasters. Like math, you can't talk it, you have to write it.

    There's nothing to beat an eyeball. You will find it.

    Good luck!

  4. $spacer_open
    $spacer_close
  5. #14
    Sorry, but your device.map is not correct!
    Because I read: /dev/sda1 on /windows/D

    The first partition on the first disk where windows is installed, windows calls C.
    If a second disk is installed and he is bootable, windows calls the first partition D.
    After that windows calls the further partitions on the first disk E F etc.
    And after that comes the partitions of the second disk.
    It depends on if the disk is (flagged) bootable or how he is formatted.
    So windows always calls the first (windows) partition C.
    And I think the problem is indeed windows related.

    On the other hand linux calls the first disk hda en de second hdb etc, as correctly is stated here.
    And the first partition hda1 hdb1 etc.
    Ofcourse GRUB calls them hd0 hd1 hd2 etc, also correctly stated earlier.

    You can also booting manually with a GRUB boot-disk.
    Or maybe with the Super GRUB CD, I do not know that.
    The way to do that is to get in de GRUB command mode with the c key.
    Then you must first load the kernel and initrd from command line.

    root (hd0,7)
    kernel (hd0,7)/boot/vmlinuz
    initrd (hd0,7)/boot/initrd

    And you boot in linux with:

    boot /dev/sda8

    This if your linux installation is on sda8.
    Boot in other linux installations with the correct syntax for that drive
    This way you could check if your menu.lst entries are correct.

  6. #15
    But no wonder that you are getting confused!

    You say you are booting from a pata drive because BIOS doesn't allow sata.
    And that is /dev/hdc.
    But normally the first (boot) drive is called /dev/hda etc.
    (how did you jumper the drive?).
    If you also have a sata drive this would be called /dev/sda.
    And a second sata drive sdb.
    This was the situation with suse10.3.

    But with suse11.x this has changed.
    Here pata and sata drives a both called /dev/sdx.
    So a pata drive is called /dev/sda, and a second sata /dev/sdb.
    I know this because I have also one machine with both xp and suse11.1
    I asume that here the confusing begins.

    You say you have added a sata drive called /dev/sdb and xp and suse11.2 on it.
    But I don't see anything of xp in your device.map.
    Your pata drive is however correctly called hd0.
    But this doesn't correspond with /dev/hdc (drive three).
    It should be either /dev/hda or /dev/sda (but /dev/sda is already the sata drive).
    So the correct configuration should be pata /dev/hda with windows2000 and suse on it as boot drive.
    But suse11.x or xp could be on another drive.

  7. #16
    Quote Originally Posted by linuxforever View Post
    Sorry, but your device.map is not correct!
    Because I read: /dev/sda1 on /windows/D

    The first partition on the first disk where windows is installed, windows calls C.
    If a second disk is installed and he is bootable, windows calls the first partition D.
    After that windows calls the further partitions on the first disk E F etc.
    And after that comes the partitions of the second disk.
    It depends on if the disk is (flagged) bootable or how he is formatted.
    So windows always calls the first (windows) partition C.
    And I think the problem is indeed windows related.

    On the other hand linux calls the first disk hda en de second hdb etc, as correctly is stated here.
    And the first partition hda1 hdb1 etc.
    Ofcourse GRUB calls them hd0 hd1 hd2 etc, also correctly stated earlier.

    You can also booting manually with a GRUB boot-disk.
    Or maybe with the Super GRUB CD, I do not know that.
    The way to do that is to get in de GRUB command mode with the c key.
    Then you must first load the kernel and initrd from command line.

    root (hd0,7)
    kernel (hd0,7)/boot/vmlinuz
    initrd (hd0,7)/boot/initrd

    And you boot in linux with:

    boot /dev/sda8

    This if your linux installation is on sda8.
    Boot in other linux installations with the correct syntax for that drive
    This way you could check if your menu.lst entries are correct.
    Thanks for reply Linuxforever.
    This /dev/sda1 on /windows/D is my manual install - I chose to mount it on D because it was D disk in Widows 2000 so it is easy to remember for me. Nothing to do with device map. I chose the letter "D" in mkdir - it could be letter W or any other letter, because that was my choice to label it. So this is not proof of error.

    It is the Suse 11.2 install program who gave this order /dev/sdc, /dev/sda, /dev/sdb, and it seems logical to me( I know only little bit about GRUB etc.) as it in fact it boots from Hitachi /dev/sdc (pata) and /dev/sda is first on sata controller and /dev/sdb is second disk on the same controller.
    Why it chose to label first (bootable ) disk with /dev/sdc and not /dev/sda I don't know - but does the mere letter make a difference if the sequence is all right ( to my understanding).
    I manage to boot quite easily from Super GRUB. I will still have to try what you suggest.
    Thanks for all your replies!

  8. #17
    Sure, fine, that you achieved this by installing suse11.2.
    But the result is that you cannot boot properly.

    Concerning your device.map that says hd0 is the pata drive and that is correct.
    And hd0 means the FIRST drive and thats for GRUB.
    But for linux hdc or sdc means THIRD drive.
    And that's a contradiction.
    In linux hda is always the first drive and hdb the second, etc.
    It isn't just a letter with no meaning.
    So the sequence isn't wright.

    And then your windows D.
    Windows doesn't call your disk D, but only the windows partition on wich it is.
    Additional windows partitions on that disk get additional letters.
    So in linux you have also to give letters to the partitions if you want to see them in linux.
    And too for windows partitions on other drives.
    Also I don't see the windows xp partition on sdb in your device.map.

    Further I find it very unwise to install windows2000 two times!
    Thats asking for problems.
    The proper solution should have been windows2000 and a linux installation on the first pata drive, and partition.
    Further windows and linux installations on other partitions or drives.

    The fact that you can boot with super GRUB proves that your menu.lst isn't correct.
    You can always boot a linux partition.
    You have first to point at the wright partition, load the kernel and initrd and boot then.
    Just as I have already described.
    At last, normally when you install a multi-boot system with windows and linux you get only one windows choice.
    If you select this you go to the windows dual-boot menu.
    From this you select 2000 or xp.
    That's the way it should go.

  9. #18
    Linux User
    Join Date
    Dec 2007
    Location
    Idaho USA
    Posts
    366
    Some times with a mix of PATA and SATA, grub sees hdd's totally different then we would think. Need to see just how hdds are seen by grub.
    (note: I'm running XP so must try to remember commands)

    When you get to the grub menu
    1) Press 'ESC'
    2) press 'C' for command prompt
    3) type in 'root (hd ' press the tab key and take note of hdd's listed.
    4)type in 'root (hdx, ' x=hdds from step 3 above, one hdd at a time. It will have listed each partition on selected hdd. Looking at the partition types displayed and compare them to the fdisk output. post what hdx =/dev/sdx.

    If you can download and run 'boot_info_script' might help you figure it out. Boot Info Script | Get Boot Info Script at SourceForge.net

  10. #19
    Hey, that's fine chap, I didn't remember that one!
    Because I always make a GRUB boot CD with menu for win/linux machines.
    So that I always can boot from this and have the GRUB command mode.

    The tab key ouput gives the partitions types by number ie 7 for NTFS and 83 for linux.
    So indeed you can see what sdx it is.

    But asuming that hd0 is sda what normally should be the case then his menu.lst is wrong.
    And that has already been stated several times here.
    Also that he has windows2000 on both sda and sdc is not nice.
    This should always be on de first drive.

  11. #20
    I ran bootinfo_script041.sh as suggested by Lostfarmer. As I need to keep what is on /dev/sda1(Windows2000) and /dev/sda2 (Suse 10.2) because there are to many applications there configured and to much work - I can't reshuffle disks as linuxforever suggests.
    Here is the output of that script:
    ================================
    ============================= Boot Info Summary: ==============================

    => No boot loader is installed in the MBR of /dev/sda
    => Windows is installed in the MBR of /dev/sdb
    => Grub 0.97 is installed in the MBR of /dev/sdc and looks on boot drive #3
    in partition #2 for /boot/grub/stage2 and /boot/grub/menu.lst.

    sda1: __________________________________________________ _______________________

    File system: ntfs
    Boot sector type: Windows XP
    Boot sector info: No errors found in the Boot Parameter Block.
    Operating System:
    Boot files/dirs:
    sda2: __________________________________________________ _______________________

    File system: ext3
    Boot sector type: -
    Boot sector info: Operating System: Welcome to openSUSE 10.3
    (i586) - Kernel ().
    Boot files/dirs: /boot/grub/menu.lst /etc/fstab

    sda3: __________________________________________________ _______________________

    File system: ext3
    Boot sector type: -
    Boot sector info: Operating System:
    Boot files/dirs:
    sda4: __________________________________________________ _______________________

    File system: Extended Partition
    Boot sector type: -
    Boot sector info:
    sda5: __________________________________________________ _______________________

    File system: swap
    Boot sector type: -
    Boot sector info:
    sda6: __________________________________________________ _______________________

    File system: vfat
    Boot sector type: -
    Boot sector info: No errors found in the Boot Parameter Block.
    Operating System:
    Boot files/dirs:
    sda7: __________________________________________________ _______________________

    File system: ext4
    Boot sector type: -
    Boot sector info: Operating System:
    Boot files/dirs: /menu.lst

    sdb1: __________________________________________________ _______________________

    File system: ntfs
    Boot sector type: Windows XP
    Boot sector info: No errors found in the Boot Parameter Block.
    Operating System: Windows XP
    Boot files/dirs:
    sdb2: __________________________________________________ _______________________

    File system: ext4
    Boot sector type: -
    Boot sector info: Operating System: Welcome to openSUSE 11.2
    "Emerald" - Kernel ().
    Boot files/dirs: /boot/grub/menu.lst /etc/fstab

    sdb4: __________________________________________________ _______________________

    File system: Extended Partition
    Boot sector type: -
    Boot sector info:
    sdb5: __________________________________________________ _______________________

    File system: vfat
    Boot sector type: -
    Boot sector info: No errors found in the Boot Parameter Block.
    Operating System:
    Boot files/dirs:
    sdb6: __________________________________________________ _______________________

    File system: swap
    Boot sector type: -
    Boot sector info:
    sdb7: __________________________________________________ _______________________

    File system: swap
    Boot sector type: -
    Boot sector info:
    sdc1: __________________________________________________ _______________________

    File system: ntfs
    Boot sector type: Windows XP
    Boot sector info: No errors found in the Boot Parameter Block.
    Operating System:
    Boot files/dirs: /boot.ini /ntldr /NTDETECT.COM

    sdc2: __________________________________________________ _______________________

    File system: vfat
    Boot sector type: -
    Boot sector info: No errors found in the Boot Parameter Block.
    Operating System:
    Boot files/dirs:
    =========================== Drive/Partition Info: =============================

    Drive: sda ___________________ __________________________________________________ ___

    Disk /dev/sda: 500.1 GB, 500107862016 bytes
    255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Disk identifier: 0x808f72ac

    Partition Boot Start End Size Id System

    /dev/sda1 * 63 274,727,564 274,727,502 7 HPFS/NTFS
    /dev/sda2 274,727,565 358,618,994 83,891,430 83 Linux
    /dev/sda3 358,618,995 633,346,559 274,727,565 83 Linux
    /dev/sda4 633,346,560 976,768,064 343,421,505 f W95 Ext d (LBA)
    /dev/sda5 633,346,623 648,029,969 14,683,347 82 Linux swap / Solaris
    /dev/sda6 648,030,033 710,940,509 62,910,477 c W95 FAT32 (LBA)
    /dev/sda7 710,940,573 976,768,064 265,827,492 83 Linux


    Drive: sdb ___________________ __________________________________________________ ___

    Disk /dev/sdb: 500.1 GB, 500107862016 bytes
    255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Disk identifier: 0xcd2e0164

    Partition Boot Start End Size Id System

    /dev/sdb1 * 63 285,218,009 285,217,947 7 HPFS/NTFS
    /dev/sdb2 285,218,010 570,436,019 285,218,010 83 Linux
    /dev/sdb4 855,654,030 976,768,064 121,114,035 f W95 Ext d (LBA)
    /dev/sdb5 855,654,093 922,757,534 67,103,442 c W95 FAT32 (LBA)
    /dev/sdb6 922,757,598 939,529,394 16,771,797 82 Linux swap / Solaris
    /dev/sdb7 939,529,458 956,301,254 16,771,797 82 Linux swap / Solaris


    Drive: sdc ___________________ __________________________________________________ ___

    Disk /dev/sdc: 160.0 GB, 160041885696 bytes
    255 heads, 63 sectors/track, 19457 cylinders, total 312581808 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Disk identifier: 0x1b601b5f

    Partition Boot Start End Size Id System

    /dev/sdc1 * 63 249,553,709 249,553,647 7 HPFS/NTFS
    /dev/sdc2 249,553,710 312,576,704 63,022,995 c W95 FAT32 (LBA)


    blkid -c /dev/null: __________________________________________________ __________

    /dev/sda1: UUID="241C9F531C9F1EBC" LABEL="Local Disk" TYPE="ntfs"
    /dev/sda2: LABEL="Samsung_2" UUID="f6e8ed98-5b2d-4136-9eaf-462444077193" SEC_TYPE="ext2" TYPE="ext3"
    /dev/sda3: LABEL="Samsung_3" UUID="6a3a9deb-526e-412d-ae2f-086939e3cb74" SEC_TYPE="ext2" TYPE="ext3"
    /dev/sda5: UUID="f461a39c-9921-4518-a87a-78c90c6001fb" TYPE="swap"
    /dev/sda6: LABEL="LOCAL DISK" UUID="B0F5-FD37" TYPE="vfat"
    /dev/sda7: LABEL="Nova" UUID="b7f522b3-27a1-4692-a8de-26d0695d4eb2" TYPE="ext4"
    /dev/sdb1: UUID="96142BE4142BC659" TYPE="ntfs"
    /dev/sdb2: LABEL="SUSE" UUID="c9fa4de2-aabe-4a92-82f2-381ab5a18f59" TYPE="ext4"
    /dev/sdb5: UUID="5A20-FD97" TYPE="vfat"
    /dev/sdb6: TYPE="swap"
    /dev/sdb7: TYPE="swap"
    /dev/sdc1: UUID="9CACB0BCACB0926E" LABEL="Local Disk" TYPE="ntfs"
    /dev/sdc2: UUID="83D1-C8D1" TYPE="vfat"

    =============================== "mount" output: ===============================

    /dev/sdb2 on / type ext4 (rw,acl,user_xattr)
    proc on /proc type proc (rw)
    sysfs on /sys type sysfs (rw)
    debugfs on /sys/kernel/debug type debugfs (rw)
    udev on /dev type tmpfs (rw)
    devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
    /dev/sda7 on /tmp type ext4 (rw)
    fusectl on /sys/fs/fuse/connections type fusectl (rw)
    securityfs on /sys/kernel/security type securityfs (rw)
    gvfs-fuse-daemon on /home/branislav/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=branislav)


    =========================== sda2/boot/grub/menu.lst: ===========================

    # Modified by YaST2. Last modification on Thu Jan 22 23:16:23 EST 2009
    default 0
    timeout 8
    gfxmenu (hd1,1)/boot/message

    ###Don't change this comment - YaST2 identifier: Original name: linux###
    title openSUSE 10.3 - 2.6.22.19-0.2 (default)
    root (hd1,1)
    kernel /boot/vmlinuz-2.6.22.19-0.2-default root=/dev/disk/by-id/scsi-SATA_SAMSUNG_HD501LJS0MUJDSP900048-part2 vga=0x31a resume=/dev/sdb5 splash=silent showopts
    initrd /boot/initrd-2.6.22.19-0.2-default

    ###Don't change this comment - YaST2 identifier: Original name: failsafe###
    title Failsafe -- openSUSE 10.3 - 2.6.22.19-0.2
    root (hd1,1)
    kernel /boot/vmlinuz-2.6.22.19-0.2-default root=/dev/disk/by-id/scsi-SATA_SAMSUNG_HD501LJS0MUJDSP900048-part2 vga=normal showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off 3
    initrd /boot/initrd-2.6.22.19-0.2-default

    ###Don't change this comment - YaST2 identifier: Original name: xen###
    title Xen -- openSUSE 10.3 - 2.6.22.19-0.2
    root (hd1,1)
    kernel /boot/xen.gz
    module /boot/vmlinuz-2.6.22.19-0.2-xen root=/dev/disk/by-id/scsi-SATA_SAMSUNG_HD501LJS0MUJDSP900048-part2 vga=0x31a resume=/dev/sdb5 splash=silent showopts
    module /boot/initrd-2.6.22.19-0.2-xen

    ###Don't change this comment - YaST2 identifier: Original name: openSUSE 10.3 (/dev/sdc2)###
    title openSUSE 10.3 (/dev/sdc2)
    root (hd2,1)
    configfile /boot/grub/menu.lst

    ###Don't change this comment - YaST2 identifier: Original name: windows 1###
    title windows 1
    rootnoverify (hd1,1)
    chainloader (hd0,0)+1

    ###Don't change this comment - YaST2 identifier: Original name: windows 2###
    title windows 2
    rootnoverify (hd1,1)
    chainloader (hd1,0)+1

    ###Don't change this comment - YaST2 identifier: Original name: floppy###
    title Floppy
    rootnoverify (hd1,1)
    chainloader (fd0)+1

    =============================== sda2/etc/fstab: ===============================

    /dev/disk/by-id/scsi-SATA_SAMSUNG_HD501LJS0MUJDSP900048-part2 / ext3 acl,user_xattr 1 1
    /dev/disk/by-id/scsi-SATA_SAMSUNG_HD501LJS0MUJDSP900048-part3 /home ext3 acl,user_xattr 1 2
    /dev/disk/by-id/scsi-SATA_SAMSUNG_HD501LJS0MUJDSP900048-part5 swap swap defaults 0 0
    proc /proc proc defaults 0 0
    sysfs /sys sysfs noauto 0 0
    debugfs /sys/kernel/debug debugfs noauto 0 0
    usbfs /proc/bus/usb usbfs noauto 0 0
    devpts /dev/pts devpts mode=0620,gid=5 0 0
    /dev/fd0 /media/floppy auto noauto,user,sync 0 0

    =================== sda2: Location of files loaded by Grub: ===================


    140.6GB: boot/grub/menu.lst
    140.6GB: boot/grub/stage2
    140.6GB: boot/initrd
    140.6GB: boot/initrd-2.6.22.19-0.2-default
    140.6GB: boot/initrd-2.6.22.19-0.2-xen
    140.6GB: boot/initrd-xen
    140.6GB: boot/vmlinuz
    140.6GB: boot/vmlinuz-2.6.22.19-0.2-default
    140.6GB: boot/vmlinuz-2.6.22.19-0.2-xen
    140.6GB: boot/vmlinuz-xen

    ================================ sda7/menu.lst: ================================

    # Modified by YaST2. Last modification on Fri Dec 4 20:30:57 EST 2009
    # THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader
    # Configure custom boot parameters for updated kernels in /etc/sysconfig/bootloader

    default 0
    timeout 8
    gfxmenu (hd2,1)/boot/message

    ###Don't change this comment - YaST2 identifier: Original name: linux###
    title openSUSE 11.2 - 2.6.31.5-0.1
    root (hd2,1)
    kernel /boot/vmlinuz-2.6.31.5-0.1-default root=/dev/disk/by-id/ata-SAMSUNG_HD502HI_S1VZJ90S225155-part2 resume=/dev/disk/by-id/ata-SAMSUNG_HD502HI_S1VZJ90S225155-part6 splash=silent quiet showopts vga=0x31a
    initrd /boot/initrd-2.6.31.5-0.1-default

    ###Don't change this comment - YaST2 identifier: Original name: failsafe###
    title Failsafe -- openSUSE 11.2 - 2.6.31.5-0.1
    root (hd2,1)
    kernel /boot/vmlinuz-2.6.31.5-0.1-default root=/dev/disk/by-id/ata-SAMSUNG_HD502HI_S1VZJ90S225155-part2 showopts apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 x11failsafe vga=0x31a
    initrd /boot/initrd-2.6.31.5-0.1-default

    ###Don't change this comment - YaST2 identifier: Original name: openSUSE 10.3 - 2.6.22.19-0.2 (default) (/dev/sda2)###
    title openSUSE 10.3 - 2.6.22.19-0.2 (default) (/dev/sda2)
    root (hd1,1)
    configfile /boot/grub/menu.lst

    ###Don't change this comment - YaST2 identifier: Original name: windows 1###
    title windows 1
    map (hd1) (hd0)
    map (hd0) (hd1)
    rootnoverify (hd1,0)
    makeactive
    chainloader +1

    ###Don't change this comment - YaST2 identifier: Original name: windows 2###
    title windows 2
    map (hd2) (hd0)
    map (hd0) (hd2)
    rootnoverify (hd2,0)
    makeactive
    chainloader +1

    ###Don't change this comment - YaST2 identifier: Original name: windows 3###
    title windows 3
    rootnoverify (hd0,0)
    chainloader +1

    ###Don't change this comment - YaST2 identifier: Original name: floppy###
    title Floppy
    rootnoverify (fd0)
    chainloader +1

    =================== sda7: Location of files loaded by Grub: ===================


    364.0GB: menu.lst

    =========================== sdb2/boot/grub/menu.lst: ===========================

    # Modified by YaST2. Last modification on Sun Dec 6 18:27:32 EST 2009
    # THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader
    # Configure custom boot parameters for updated kernels in /etc/sysconfig/bootloader

    default 0
    timeout 8
    gfxmenu (hd2,1)/boot/message

    ###Don't change this comment - YaST2 identifier: Original name: linux###
    title openSUSE 11.2 - 2.6.31.5-0.1
    root (hd2,1)
    kernel /boot/vmlinuz-2.6.31.5-0.1-default root=/dev/disk/by-id/ata-SAMSUNG_HD502HI_S1VZJ90S225155-part2 resume=/dev/disk/by-id/ata-SAMSUNG_HD502HI_S1VZJ90S225155-part6 splash=silent quiet showopts vga=0x31a
    initrd /boot/initrd-2.6.31.5-0.1-default

    ###Don't change this comment - YaST2 identifier: Original name: failsafe###
    title Failsafe -- openSUSE 11.2 - 2.6.31.5-0.1
    root (hd2,1)
    kernel /boot/vmlinuz-2.6.31.5-0.1-default root=/dev/disk/by-id/ata-SAMSUNG_HD502HI_S1VZJ90S225155-part2 showopts apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 x11failsafe vga=0x31a
    initrd /boot/initrd-2.6.31.5-0.1-default

    ###Don't change this comment - YaST2 identifier: Original name: openSUSE 10.3 - 2.6.22.19-0.2 (default) (/dev/sda2)###
    title openSUSE 10.3 - 2.6.22.19-0.2 (default) (/dev/sda2)
    root (hd1,1)
    configfile /boot/grub/menu.lst

    ###Don't change this comment - YaST2 identifier: Original name: windows 1###
    title windows 1
    map (hd1) (hd0)
    map (hd0) (hd1)
    rootnoverify (hd1,0)
    makeactive
    chainloader +1

    ###Don't change this comment - YaST2 identifier: Original name: windows 2###
    title windows 2
    map (hd2) (hd0)
    map (hd0) (hd2)
    rootnoverify (hd2,0)
    makeactive
    chainloader +1

    ###Don't change this comment - YaST2 identifier: Original name: windows 3###
    title windows 3
    rootnoverify (hd0,0)
    chainloader +1

    ###Don't change this comment - YaST2 identifier: Original name: floppy###
    title Floppy
    rootnoverify (fd0)
    chainloader +1

    =============================== sdb2/etc/fstab: ===============================

    /dev/disk/by-id/ata-SAMSUNG_HD502HI_S1VZJ90S225155-part2 / ext4 acl,user_xattr 1 1
    /dev/disk/by-id/ata-SAMSUNG_HD501LJ_S0MUJDSP900048-part5 swap swap defaults 0 0
    /dev/disk/by-id/ata-SAMSUNG_HD502HI_S1VZJ90S225155-part6 swap swap defaults 0 0
    /dev/disk/by-id/ata-SAMSUNG_HD502HI_S1VZJ90S225155-part7 swap swap defaults 0 0
    /dev/disk/by-id/ata-SAMSUNG_HD501LJ_S0MUJDSP900048-part7 /tmp ext4 defaults 1 2
    proc /proc proc defaults 0 0
    sysfs /sys sysfs noauto 0 0
    debugfs /sys/kernel/debug debugfs noauto 0 0
    usbfs /proc/bus/usb usbfs noauto 0 0
    devpts /dev/pts devpts mode=0620,gid=5 0 0

    =================== sdb2: Location of files loaded by Grub: ===================


    146.0GB: boot/grub/menu.lst
    146.0GB: boot/grub/stage2
    146.0GB: boot/initrd
    146.0GB: boot/initrd-2.6.31.5-0.1-default
    146.0GB: boot/vmlinuz
    146.0GB: boot/vmlinuz-2.6.31.5-0.1-default

    ================================ sdc1/boot.ini: ================================

    [boot loader]
    timeout=30
    default=multi(0)disk(0)rdisk(2)partition(1)\WINDOW S
    [operating systems]
    multi(0)disk(0)rdisk(2)partition(1)\WINDOWS="Micro soft Windows XP Professional" /noexecute=optin /fastdetect
    multi(0)disk(0)rdisk(1)partition(1)\WINNT="Microso ft Windows 2000 Professional" /fastdetect
    multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microso ft Windows 2000 Professional" /fastdetect
    branislav@branisla-vv99hk:~/Download>

Posting Permissions

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