Page 3 of 4 FirstFirst 1234 LastLast
Results 21 to 30 of 37

Thread: Boot failure after GRUB 2.0 installation

  1. #21
    Join Date
    Feb 2013
    Beans
    Hidden!

    Re: Boot failure after GRUB 2.0 installation

    Then try this instead:
    Code:
    grub> search --file /boot/grub/grub.cfg --set root
    The rest is the same

  2. #22
    Join Date
    Dec 2012
    Beans
    42

    Re: Boot failure after GRUB 2.0 installation

    Unknown command "search".

    As I have mentioned, Ubuntu is on dev/sda7.

  3. #23
    Join Date
    Feb 2013
    Beans
    Hidden!

    Re: Boot failure after GRUB 2.0 installation

    Quote Originally Posted by dorruk View Post
    But ubuntu is installed on dev/sda7 if that's what you're looking for
    Ah, good.Then
    Code:
    set root=(hd0, msdos7)
    set prefix=($root)/boot/grub
    insmod normal
    normal

  4. #24
    Join Date
    Dec 2012
    Beans
    42

    Re: Boot failure after GRUB 2.0 installation

    Ok this is how it went:
    Code:
    grub rescue> set root=(hd0,msdos7),
    grub rescue> set prefix=(hd0, msdos7)/boot/grub,
    grub rescue> insmod normal
    error: missing ')'
    grub rescue> insmod normal)
    error: no such partition
    grub rescue> ls
    (partitions are still there)
    grub rescue> set
    prefix=(hd0,
    root=(hd0,msdos7),
    There are no spelling errors, just wrote it down as is.

    EDIT: Sorry about that. Just figured out my mistake. In set prefix, I added an unnecessary space.

  5. #25
    Join Date
    Dec 2012
    Beans
    42

    Re: Boot failure after GRUB 2.0 installation

    Fixing the wrong prefix string, now insmod normal replies:
    error: unknown filesystem.
    It is ext4. Any ideas?
    Last edited by dorruk; February 4th, 2013 at 04:30 PM.

  6. #26
    Join Date
    Feb 2013
    Beans
    Hidden!

    Re: Boot failure after GRUB 2.0 installation

    You somehow missed the closing ')' on 'set root'. Do you entered the comma as the last character? Don't do it. After setting both 'root' and 'prefix'
    Code:
    grub> set
    should show
    Code:
    root=(hd0,msdos7),
    prefix=(hd0,msdos7)/boot/grub,

  7. #27
    Join Date
    Dec 2012
    Beans
    42

    Re: Boot failure after GRUB 2.0 installation

    That's what I exactly see at the moment. Still insmod normal won't work.

  8. #28
    Join Date
    Feb 2013
    Beans
    Hidden!

    Re: Boot failure after GRUB 2.0 installation

    Hmm,

    1. You're booting from your harddisk, right? Not from GParted? If the latter, it seems that grub in your GParted doesn't support ext4. What GParted version it is?
    2. Are you sure /dev/sda7 is the Ubuntu partition?

  9. #29
    Join Date
    Feb 2013
    Beans
    Hidden!

    Re: Boot failure after GRUB 2.0 installation

    Ah, sorry, I see. You installed GRUB into MBR with BOOTICE. The version of Grub on BOOTICE probably differs from the version of GRUB in Ubuntu. Can you find some LiveCD with the same Ubuntu version like in your Ubuntu partition and boot from it?

  10. #30
    Join Date
    Nov 2009
    Location
    Catalunya, Spain
    Beans
    14,560
    Distro
    Ubuntu 18.04 Bionic Beaver

    Re: Boot failure after GRUB 2.0 installation

    I am not sure how chroot works from Gparted Live, since you have no other linux to boot. Try this in terminal:
    (I assume you will be root, or first google how to execute root commands in Gparted Live terminal)
    Code:
    mount /dev/sda7 /mnt
    mount --bind /proc /mnt/proc
    mount --bind /dev /mnt/dev
    mount --bind /sys /mnt/sys
    chroot /mnt
    grub-install /dev/sda
    exit
    umount /mnt/sys
    umount /mnt/dev
    umount /mnt/proc
    umount /mnt
    That is a chroot procedure. Hope fully it will work.

    And get a new usb stick, it least 1GB and make it ubuntu live usb, and keep it.
    Darko.
    -----------------------------------------------------------------------
    Ubuntu 18.04 LTS 64bit

Page 3 of 4 FirstFirst 1234 LastLast

Tags for this Thread

Bookmarks

Posting Permissions

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