Find the answer to your Linux question:
Results 1 to 4 of 4
hello all, i'm new to this forum (and linux) but haven't found any info about my specific problem anywhere i've searched on the net. if you take pity on a ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Sep 2004
    Posts
    2

    hard drive unreadable after grub install...help please


    hello all, i'm new to this forum (and linux) but haven't found any info about my specific problem anywhere i've searched on the net. if you take pity on a distressed newb, feel free to im/pm/e-mail in addition to/instead of replying here. ok, here it is:

    when my system was fully operational, the configuration was
    160GB S-ATA HDD with windows xp home installed
    60GB IDE HDD used as storage
    (system is a P4 ht processor in an asus MB, 512MB DDR PC3300 RAM)

    While installing debian linux on the 60GB drive (with the sarge
    installer) after reformatting/partitioning, I pointed the GRUB bootloader installation prompt to my 160GB drive. When I went to restart, however, I found that I was unable to boot windows; only linux worked.

    I have since tried using a win98 boot disk and running fdisk fixmbr,
    as well as using the windows XP cd to try and accomplish the same
    thing, but xp still will not boot when I select it from GRUB's menu. in
    linux, when i try to mount the 160GB hard drive, it gives the error:
    "wrong fs type, bad option, bad superblock", i have been completely
    unable to see the contents of this drive.

    when i unplug the 60GB drive and try to boot just from the
    S-ATA 160GB one, all I see is the word "GRUB" in plain text with a
    blinking cursor after it. This makes me think that
    somehow the mbr used by the computer is located on the IDE drive,
    although that's supposed to be my secondary HDD, seeing as how it
    never had windows on it. Also, the S-ATA drive is listed in BIOS as
    "third IDE master", i have no idea what to make of this.

    if there are details i've left out, please let me know what they are so i can make this entry more complete. thanks for taking the time to read this and in advance for any help you may choose to offer
    chris

  2. #2
    Just Joined!
    Join Date
    Sep 2004
    Location
    /home/mike
    Posts
    15
    Can you post your grub.conf file? We can start there, as likely it is just not properly configured to boot windows.

  3. #3
    Just Joined!
    Join Date
    Sep 2004
    Posts
    2
    hello, i don't actually have a grub.conf file but a menu.lst, so here are the contents of that. thanks for your consideration of my problem
    -chris


    # menu.lst - See: grub(, info grub, update-grub(
    # grub-install(, grub-floppy(,
    # grub-md5-crypt, /usr/share/doc/grub
    # and /usr/share/doc/grub-doc/.

    ## default num
    # Set the default entry to the entry number NUM. Numbering starts from 0, and
    # the entry number 0 is the default if the command is not used.
    #
    # You can specify 'saved' instead of a number. In this case, the default entry
    # is the entry saved with the command 'savedefault'.
    default 0

    ## timeout sec
    # Set a timeout, in SEC seconds, before automatically booting the default entry
    # (normally the first entry defined).
    timeout 45

    # Pretty colours
    color cyan/blue white/blue

    ## password ['--md5'] passwd
    # If used in the first section of a menu file, disable all interactive editing
    # control (menu entry editor and command-line) and entries protected by the
    # command 'lock'
    # e.g. password topsecret
    # password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
    # password topsecret

    #
    # examples
    #
    # title Windows 95/98/NT/2000
    # root (hd0,0)
    # makeactive
    # chainloader +1
    #
    # title Linux
    # root (hd0,1)
    # kernel /vmlinuz root=/dev/hda2 ro
    #

    #
    # Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

    ### BEGIN AUTOMAGIC KERNELS LIST
    ## lines between the AUTOMAGIC KERNELS LIST markers will be modified
    ## by the debian update-grub script except for the default optons below

    ## DO NOT UNCOMMENT THEM, Just edit them to your needs

    ## ## Start Default Options ##
    ## default kernel options
    ## default kernel options for automagic boot options
    ## If you want special options for specifiv kernels use kopt_x_y_z
    ## where x.y.z is kernel version. Minor versions can be omitted.
    ## e.g. kopt=root=/dev/hda1 ro
    # kopt=root=/dev/hda1 ro

    ## default grub root device
    ## e.g. groot=(hd0,0)
    # groot=(hd0,0)

    ## should update-grub create alternative automagic boot options
    ## e.g. alternative=true
    ## alternative=false
    # alternative=true

    ## should update-grub lock alternative automagic boot options
    ## e.g. lockalternative=true
    ## lockalternative=false
    # lockalternative=false

    ## altoption boot targets option
    ## multiple altoptions lines are allowed
    ## e.g. altoptions=(extra menu suffix) extra boot options
    ## altoptions=(recovery mode) single
    # altoptions=(recovery mode) single

    ## controls how many kernels should be put into the menu.lst
    ## only counts the first occurence of a kernel, not the
    ## alternative kernel options
    ## e.g. howmany=all
    ## howmany=7
    # howmany=all

    ## ## End Default Options ##

    title Debian GNU/Linux, kernel 2.6.8-1-686
    root (hd0,0)
    kernel /boot/vmlinuz-2.6.8-1-686 root=/dev/hda1 ro
    initrd /boot/initrd.img-2.6.8-1-686
    savedefault
    boot

    title Debian GNU/Linux, kernel 2.6.8-1-686 (recovery mode)
    root (hd0,0)
    kernel /boot/vmlinuz-2.6.8-1-686 root=/dev/hda1 ro single
    initrd /boot/initrd.img-2.6.8-1-686
    savedefault
    boot

    title Debian GNU/Linux, kernel 2.4.27-1-686
    root (hd0,0)
    kernel /boot/vmlinuz-2.4.27-1-686 root=/dev/hda1 ro
    initrd /boot/initrd.img-2.4.27-1-686
    savedefault
    boot

    title Debian GNU/Linux, kernel 2.4.27-1-686 (recovery mode)
    root (hd0,0)
    kernel /boot/vmlinuz-2.4.27-1-686 root=/dev/hda1 ro single
    initrd /boot/initrd.img-2.4.27-1-686
    savedefault
    boot

    title Debian GNU/Linux, kernel 2.4.26-1-386
    root (hd0,0)
    kernel /boot/vmlinuz-2.4.26-1-386 root=/dev/hda1 ro
    initrd /boot/initrd.img-2.4.26-1-386
    savedefault
    boot

    title Debian GNU/Linux, kernel 2.4.26-1-386 (recovery mode)
    root (hd0,0)
    kernel /boot/vmlinuz-2.4.26-1-386 root=/dev/hda1 ro single
    initrd /boot/initrd.img-2.4.26-1-386
    savedefault
    boot

    ### END DEBIAN AUTOMAGIC KERNELS LIST

    # This is a divider, added to separate the menu items below from the Debian
    # ones.
    title Other operating systems:
    root


    # This entry automatically added by the Debian installer for a non-linux OS
    # on /dev/hde1
    title Windows NT/2000/XP
    rootnoverify (hd1,0)
    map (hd1) (hd0)
    map (hd0) (hd1)
    makeactive
    savedefault
    chainloader +1
    boot

  4. #4
    Just Joined!
    Join Date
    Oct 2004
    Posts
    1
    Hello,

    Try the GAG boadloader. It installs on a floppy and you can boot from the floppy. It finds all your OS's on all HD's.
    Just Google --> download --> install on flop --> boot.
    Better not install to HD untill you are sure you want this.

Posting Permissions

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