FedoraForum.org - Fedora Support Forums and Community
Results 1 to 9 of 9
  1. #1
    Join Date
    Jan 2011
    Posts
    23
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Grub-install "no corresponding BIOS drive" ERROR

    hello there,

    I have had Fedora 14 running well on my Dell Latitude XT

    All was good until I created an NTFS partition and attempted to install windows XP on it.

    The installation failed, then when the computer boots i get:

    "Error Loading Operating System"

    I have attempted the following:

    1) FedoraLive from USB then :
    Code:
    [root@localhost liveuser]# grub-install /dev/sda
    Probing devices to guess BIOS drives. This may take a long time.
    /dev/mapper/../dm-0 does not have any corresponding BIOS drive.
    2) I tried:

    Code:
    # grub-install --recheck /dev/sda
    Probing devices to guess BIOS drives. This may take a long time.
    /dev/mapper/../dm-0 does not have any corresponding BIOS drive.

    The boot folder on my previously installed Fedora 14 is empty

    Any Help is appreciated !

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

    Re: Grub-install "no corresponding BIOS drive" ERROR

    If you are doing this from a live system and the busted system is using LVM, then you need to mount the boot partition and the root logical volume and use the --root-directory=dir option with the grub-install command. See more here in post #4...You also can learn there how to try it with the GRUB shell instead of grub-install (at the end of post #4). To try that, you don't have to mount any partitions or logical volumes. But sometimes I find that one or the other (the GRUB shell or grub-install) will not produce the desired result, and I then have to try the other one.

  3. #3
    Join Date
    Jan 2011
    Posts
    23
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Grub-install "no corresponding BIOS drive" ERROR

    hey Thanx alot

    I think I have two separate partitions one for root and one for boot.. because the Logical volume management showed that i have two ext3 partitions under sdb (one is sdb1 0.5 GB the other is sdb3 50 GB)

    so I tried :
    Code:
    [root@localhost liveuser]# mkdir -p /mnt/temp/boot
    [root@localhost liveuser]# mount /dev/sdb1 /mnt/temp/boot
    [root@localhost liveuser]# mount /dev/sdb3 /mnt/temp
    [root@localhost liveuser]# grub-install --root-directory=/mnt/temp /dev/sda
    Probing devices to guess BIOS drives. This may take a long time.
    The file /mnt/temp/boot/grub/stage2 not read correctly.
    I also tried the Grub shell command:

    Code:
    grub> root (hd0,0)
    root (hd0,0)
     Filesystem type is fat, partition type 0xc
    grub> setup (hd0)
    setup (hd0)
     Checking if "/boot/grub/stage1" exists... no
     Checking if "/grub/stage1" exists... no
    
    Error 15t: File not found
    Im sorry I dont understand the hd0,0 structure but i followed the post



    EDIT

    In the mean time I also downloaded the Super Grub 2 Disk (thats the default one for Fedora 14 right)

    I couldnt download the 450 Mb one..I am on mobile broadband and its quite expensive

    I tried all the following options in the start up disk but each one returned No INSERT OPTION HERE :

    1) detect any OS
    2) detect any grub 2 config file
    2) detect any grub 2 installation

    etc
    Last edited by ktulu100; 18th January 2011 at 12:05 AM.

  4. #4
    Join Date
    Jun 2006
    Posts
    7,544
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Grub-install "no corresponding BIOS drive" ERROR

    For the first one you tried, if your hard drive system really does use LVM, then for the grub-install method run from a live system you need to mount the root logical volume (/dev/VolGroup_something/LogVol_something or something similar). I have no way to know at this point. If you can connect to the Internet while in the live system, then post the fdisk and lvdisplay stuff.

    For the next thing you tried (GRUB shell), it said that (hd0,0) is a FAT partition. Obviously not your Fedora boot partition. If it really is /dev/sdb1 like your post, then try (hd1,0) in the root command.

    Next, you need the ordinary legacy Super Grub Disk. Fedora does not use GRUB 2.

    Lastly, you said you created a new partition for XP. Depending on where it is located in relation to Fedora's boot partition, creating that new partition could have had the effect of misconfiguring Fedora's grub.conf file. If that happened, then you also will need to edit that file. If you can, then post the grub.conf text when you post the fdisk stuff.

  5. #5
    Join Date
    Jan 2011
    Posts
    23
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Grub-install "no corresponding BIOS drive" ERROR

    Thank you again,
    yes i do have internet access on the live system

    1) root (hd1,0) in Grub returns not found error

    2) I assumed Fedora would have let grub legacy go, thanx for updating my knowledge

    3) I can not find the grub.conf file ! ... the problem is that my "boot/grub" directory on the system I lost is completely empty except for the flash image

    4) the fidisk -l is posted below, however when mounting /dev/mapper/something did u mean /dev/dm something or is it the same as the one you mentioned ?


    Code:
    fdisk -l
    
    Disk /dev/sda: 8011 MB, 8011120640 bytes
    41 heads, 41 sectors/track, 9307 cylinders, total 15646720 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x000e3d6a
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/sda1   *        8064    15646719     7819328    c  W95 FAT32 (LBA)
    
    Disk /dev/sdb: 120.0 GB, 120034123776 bytes
    255 heads, 63 sectors/track, 14593 cylinders, total 234441648 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x0003f2f6
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/sdb1            2048     1026047      512000   83  Linux
    /dev/sdb2   *     1026048   137162751    68068352   8e  Linux LVM
    /dev/sdb3       137162970   234436544    48636787+   7  HPFS/NTFS
    
    Disk /dev/dm-0: 3221 MB, 3221225472 bytes
    255 heads, 63 sectors/track, 391 cylinders, total 6291456 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x00000000
    
    Disk /dev/dm-0 doesn't contain a valid partition table
    
    Disk /dev/dm-1: 3221 MB, 3221225472 bytes
    255 heads, 63 sectors/track, 391 cylinders, total 6291456 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x00000000
    
    Disk /dev/dm-1 doesn't contain a valid partition table
    
    Disk /dev/dm-2: 53.7 GB, 53687091200 bytes
    255 heads, 63 sectors/track, 6527 cylinders, total 104857600 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x00000000
    
    Disk /dev/dm-2 doesn't contain a valid partition table
    
    Disk /dev/dm-3: 12.3 GB, 12314476544 bytes
    255 heads, 63 sectors/track, 1497 cylinders, total 24051712 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x00000000
    
    Disk /dev/dm-3 doesn't contain a valid partition table
    
    Disk /dev/dm-4: 3690 MB, 3690987520 bytes
    255 heads, 63 sectors/track, 448 cylinders, total 7208960 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x00000000
    
    Disk /dev/dm-4 doesn't contain a valid partition table

    5) lvdisplay result:
    Code:
    lvdisplay
      --- Logical volume ---
      LV Name                /dev/vg_tammampc/lv_root
      VG Name                vg_tammampc
      LV UUID                D32XYM-1tzW-h1ry-I0Zd-jaCD-TlrX-rPGVvu
      LV Write Access        read/write
      LV Status              available
      # open                 1
      LV Size                50.00 GiB
      Current LE             1600
      Segments               1
      Allocation             inherit
      Read ahead sectors     auto
      - currently set to     256
      Block device           253:2
       
      --- Logical volume ---
      LV Name                /dev/vg_tammampc/lv_home
      VG Name                vg_tammampc
      LV UUID                mV82TT-rVwA-MK3P-isel-Gyja-03GC-fPXM48
      LV Write Access        read/write
      LV Status              available
      # open                 0
      LV Size                11.47 GiB
      Current LE             367
      Segments               1
      Allocation             inherit
      Read ahead sectors     auto
      - currently set to     256
      Block device           253:3
       
      --- Logical volume ---
      LV Name                /dev/vg_tammampc/lv_swap
      VG Name                vg_tammampc
      LV UUID                x79hXi-HopA-dSPa-4heF-zhKV-KhAx-GWp3do
      LV Write Access        read/write
      LV Status              available
      # open                 1
      LV Size                3.44 GiB
      Current LE             110
      Segments               1
      Allocation             inherit
      Read ahead sectors     auto
      - currently set to     256
      Block device           253:4
    Last edited by ktulu100; 18th January 2011 at 12:59 AM.

  6. #6
    Join Date
    Jun 2006
    Posts
    7,544
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Grub-install "no corresponding BIOS drive" ERROR

    Okay, then again from the live system, try this idea. Open a terminal and start the GRUB shell...
    Code:
    su
    grub
    Then at the grub> prompt, do this to locate the Fedora boot partition...
    Code:
    grub> find /grub/grub.conf
    Then use that result in this...
    Code:
    grub> root (hdx,y)
    Then do this to install GRUB in the master boot record of first hard drive...
    Code:
    grub> setup (hd0)
    Then reboot to see what happens....
    Code:
    grub> reboot
    P.S.: I was just thinking about your third comment above about a nearly empty /boot/grub directory. What you described is what happens you we choose not to install GRUB at all. However such a system never would have booted unless some other boot loader directly booted the kernel and initial ram filesystem. So how was this system booting before you installed XP?

  7. #7
    Join Date
    Jan 2011
    Posts
    23
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Grub-install "no corresponding BIOS drive" ERROR

    hello

    Well.. here is what happened

    1) I was using a liveUSB fedora !! so i followed your steps and everything succeeded (i found grub.conf on hd0,0) BUT little did I know that was the USBlive grub !! didnt occur to me but the hd0,0 was my USB drive.. anyway my USBlive does not boot now.. luckily I have a Live CD laying around so Im on it now (much slower boot tho)

    2) I created the NTFS partition long time ago in anticipation for iTunes (yes thats wat i use windows for) when i installed fedora so that did not screw up my grub.conf

    3) /boot/grub is empty i know.. but I used to boot with grub Im sure.. I installed the standard Fedora 14 and it used to load grub, the reason its empty is maybe because i tried to fix Grub from the shell many times and i tried alot of grub-install commands.. so I thought i might have wiped it out by mistake ??

    4) now Im on the live CD and re-tried your steps below, gonna reboot see what happens

    ---------- Post added at 02:41 AM ---------- Previous post was at 02:24 AM ----------

    Maaaaaaan if you were here I would have HUGGED YOU

    whooo da man ?? yooo daa maan !!

    Thank you very much, it worked like a charm Im on my Fedora 14 now

    If you every need any medical opinion / advice, please DO let me know.. physician here ..maybe i can repay a complete stranger for beiing so kind

  8. #8
    Join Date
    May 2012
    Location
    Kelowna
    Posts
    2
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Grub-install "no corresponding BIOS drive" ERROR

    Hi I have similar problem. Mistakenly I deleted grub2 package from my fedora 16 box. And when I reboot I get the grub prompt. I searched lot in google but nothing seems working. I followed your steps to now I think grub prompt is also not appearing.

    I am trying everything from the live CD that I could do. I am ussing Centos 6 live CD. I have LVM partitions on root and home directory and Boot partition as ext4 (sda6) and LVM on sda6. I was able to mount the LVM and the boot partition. But something is not working.


    I have duel boot system windows + Linux

  9. #9
    Join Date
    Jun 2006
    Posts
    7,544
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Grub-install "no corresponding BIOS drive" ERROR

    Quote Originally Posted by chandank

    I deleted grub2 package from my fedora 16 box. And when I reboot I get the grub prompt.
    Quote Originally Posted by chandank

    I followed your steps to now I think grub prompt is also not appearing.
    All of that old stuff above your post relates to Fedora 14 and legacy GRUB.

    Thread closed since you've already started another thread for this matter (good idea).

Similar Threads

  1. Dual Boot: GRUB boots Fedora drive for "Other"
    By Kyuzo in forum Using Fedora
    Replies: 2
    Last Post: 1st April 2008, 01:35 AM
  2. GRUB Raid0 & Install "grub hard disk error"
    By synic in forum Installation, Upgrades and Live Media
    Replies: 7
    Last Post: 24th February 2008, 11:45 AM
  3. FC5 install result in "GRUB read Error"
    By eparser in forum EOL (End Of Life) Versions
    Replies: 1
    Last Post: 21st October 2006, 09:57 PM
  4. Replies: 4
    Last Post: 12th June 2006, 12:12 AM
  5. Replies: 0
    Last Post: 23rd May 2005, 04:59 AM

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
  •