After update, get “error: file not found.” followed by “grub rescue>

After update, get “error: file not found.” followed by “grub rescue> _”

I just installed quite a lot of 12.10 updates, was prompted to reboot, and then found that I couldn't boot.

edited Nov 26 '13 at 14:09

Braiam

51.3k20136219

asked Sep 14 '12 at 20:20

8128

24.8k21100137

Since I'm not yet allowed to add comments since my low reputation I add the comment this way... I used 8128s Answer wit Boot-repair but I had to add this line before the apt-get update sudo sed 's/trusty/saucy/g' -i /etc/apt/sources.list.d/yannubuntu-boot-repair-trusty.list like you see in the link he added to the answer
– Dominik
Jul 15 '14 at 17:53

add a comment |

I just installed quite a lot of 12.10 updates, was prompted to reboot, and then found that I couldn't boot.

edited Nov 26 '13 at 14:09

Braiam

51.3k20136219

asked Sep 14 '12 at 20:20

8128

24.8k21100137

Since I'm not yet allowed to add comments since my low reputation I add the comment this way... I used 8128s Answer wit Boot-repair but I had to add this line before the apt-get update sudo sed 's/trusty/saucy/g' -i /etc/apt/sources.list.d/yannubuntu-boot-repair-trusty.list like you see in the link he added to the answer
– Dominik
Jul 15 '14 at 17:53

add a comment |

I just installed quite a lot of 12.10 updates, was prompted to reboot, and then found that I couldn't boot.

edited Nov 26 '13 at 14:09

Braiam

51.3k20136219

asked Sep 14 '12 at 20:20

8128

24.8k21100137

I just installed quite a lot of 12.10 updates, was prompted to reboot, and then found that I couldn't boot.

grub2 grubrescue

edited Nov 26 '13 at 14:09

Braiam

51.3k20136219

asked Sep 14 '12 at 20:20

8128

24.8k21100137

edited Nov 26 '13 at 14:09

Braiam

51.3k20136219

asked Sep 14 '12 at 20:20

8128

24.8k21100137

edited Nov 26 '13 at 14:09

Braiam

51.3k20136219

edited Nov 26 '13 at 14:09

Braiam

51.3k20136219

edited Nov 26 '13 at 14:09

Braiam

51.3k20136219

asked Sep 14 '12 at 20:20

8128

24.8k21100137

asked Sep 14 '12 at 20:20

8128

24.8k21100137

asked Sep 14 '12 at 20:20

8128

24.8k21100137

Since I'm not yet allowed to add comments since my low reputation I add the comment this way... I used 8128s Answer wit Boot-repair but I had to add this line before the apt-get update sudo sed 's/trusty/saucy/g' -i /etc/apt/sources.list.d/yannubuntu-boot-repair-trusty.list like you see in the link he added to the answer
– Dominik
Jul 15 '14 at 17:53

add a comment |

Since I'm not yet allowed to add comments since my low reputation I add the comment this way... I used 8128s Answer wit Boot-repair but I had to add this line before the apt-get update sudo sed 's/trusty/saucy/g' -i /etc/apt/sources.list.d/yannubuntu-boot-repair-trusty.list like you see in the link he added to the answer
– Dominik
Jul 15 '14 at 17:53

Since I'm not yet allowed to add comments since my low reputation I add the comment this way... I used 8128s Answer wit Boot-repair but I had to add this line before the apt-get update sudo sed 's/trusty/saucy/g' -i /etc/apt/sources.list.d/yannubuntu-boot-repair-trusty.list like you see in the link he added to the answer
– Dominik
Jul 15 '14 at 17:53

add a comment |

6 Answers
6

active

oldest

votes

Use Boot Repair to fix your bootloader.

Boot Ubuntu from a LiveCD or Live USB

Connect to the internet

Open a terminal, and add the Boot Repair PPA

sudo add-apt-repository ppa:yannubuntu/boot-repair && sudo apt-get update

Install Boot Repair

sudo apt-get install -y boot-repair && boot-repair

Launch and use, see https://help.ubuntu.com/community/Boot-Repair#Using_Boot-Repair for more details

answered Oct 19 '12 at 22:09

8128

24.8k21100137

I had to run 3. as root (sudo su) instead of just sudoing
– David Brossard
Mar 10 '13 at 20:03

1

THANK YOU!! Saved my server after a power outage. Time to buy a UPS!
– Domenic D.
Jun 29 '13 at 16:20

used with Kubuntu 13.10 and worked. Thanks.
– David
Oct 22 '13 at 13:37

add a comment |

Type ls to get a list of partitions

Enter set prefix=(hd0,msdos6)/boot/grub [you will almost certainly have to enter a different drive/partition in the brackets, you may just have to try all of those listed by ls until you find the one that works.

Type insmod normal

Type normal and you will get your boot prompt back!

See also: The helpful place where I found this. I doubt this will work for everyone encountering this error, but I've put it here in the hope it helps someone.

Once you've loaded Ubuntu, run sudo grub-install /dev/sda and sudo update-grub as soon as possible. This means you won't have to do that tedious process above every time you boot your machine.

answered Sep 14 '12 at 20:20

8128

24.8k21100137

9

when I run insmod normal it again says file not found
– tovmeod
Oct 19 '12 at 14:18

1

You can also use the command ls (hd0,msdos1)/ to check the contents of the partition, which would be faster if you have many partitions.
– Jonathan
Oct 23 '14 at 15:07

This worked for me, except I have a separate boot partition, so the format was set prefix=(hd0)/grub, since you need to reference the grub directory relative to the partition on the drive, not relative to its mount point during normal operation.
– Nick Coons
Dec 18 '15 at 5:27

add a comment |

I had the exact same issue - normal.mod not found, ls of the boot partition would produce a blank line. After a week of troubleshooting to get the system to boot properly here are the steps I went through.

Got a copy of SuperGrub and created a boot cd. I could now get logged back on to my system. Got a copy of BootRepair and had not luck getting the system to boot directly from the hard disk and had to keep using the CD. BootRepair did act a little strange since the Grub location and Grub options were grayed out. It did report a successful install.

Hard drive was originally set up:
sda1 ext4 root with boot
sda2 linux swap
sda3 ext4 used as a spare drive (holds VMs for Virtual box).

Used a copy of Ubuntu 10.10 live cd. Ran gparted to shrink the sda1 partition and created sda4 ext4 boot partition at the front of the drive and set mount point to /boot after deleting the boot directory from /. BootRepair now has options available. Installed on boot partition and can now boot from hard drive.

Being curious I decided to investigate further. The boot repair log had a peculiar entry for my sda1 ext4 partition, it was reported as DOS and had a short 8 character UUID instead of the UUID reported by blkid. grub-probe reported the file system as vfat.

After many other trials I cleared the first 440 bytes of sda1 partition record. Grub-probe now reports file system as ext2. Ran update-grub and the correct UUID for the sda1 partition appears.

The issue seems to be two-fold:

1. It seem to affect installations where the partition record has references to msdos.

2. grub-probe does not try to resolve mismatch issues between fs type and contents in the partition record.

edited Mar 11 '17 at 19:03

Community♦

answered Nov 13 '12 at 15:33

Mark Milakovic

411

add a comment |

Another thing to check is the boot order in your BIOS. I apparently had installed grub installed on all my disks (perhaps after following 8128's answer), but this broke when updating my Linux distro (Debian). Changing the first boot disk as my Linux OS fixed it.

answered Oct 23 '14 at 15:05

Jonathan

1216

add a comment |

I ran across this error upgrading to Kubuntu 13.10. I had a memory stick plugged into the USB port during the dist-upgrade. After rebooting I went straight to Grub Rescue. Unplugging the USB drive and rebooting fixed the problem.

answered Oct 19 '13 at 5:38

David Walker

add a comment |

-1

In my case, I had downgraded to GRUBv1 and after the upgrade to 12.10 grub2 couldn't find his files (*.mod, etc...), although the grub.cfg was there.

I found a more comprehensive manual on grub rescue:
https://help.ubuntu.com/community/Grub2/Troubleshooting#grub_rescue.3E-1

See also the command list at the begining of the page.
Thx flute flute.

answered Nov 17 '12 at 14:16

iceburn_pt

add a comment |

protected by Community♦ Dec 18 at 8:32

Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

6 Answers
6

active

oldest

votes

6 Answers
6

active

oldest

votes

Use Boot Repair to fix your bootloader.

Boot Ubuntu from a LiveCD or Live USB

Connect to the internet

Open a terminal, and add the Boot Repair PPA

sudo add-apt-repository ppa:yannubuntu/boot-repair && sudo apt-get update

Install Boot Repair

sudo apt-get install -y boot-repair && boot-repair

Launch and use, see https://help.ubuntu.com/community/Boot-Repair#Using_Boot-Repair for more details

answered Oct 19 '12 at 22:09

8128

24.8k21100137

I had to run 3. as root (sudo su) instead of just sudoing
– David Brossard
Mar 10 '13 at 20:03

1

THANK YOU!! Saved my server after a power outage. Time to buy a UPS!
– Domenic D.
Jun 29 '13 at 16:20

used with Kubuntu 13.10 and worked. Thanks.
– David
Oct 22 '13 at 13:37

add a comment |

Use Boot Repair to fix your bootloader.

Boot Ubuntu from a LiveCD or Live USB

Connect to the internet

Open a terminal, and add the Boot Repair PPA

sudo add-apt-repository ppa:yannubuntu/boot-repair && sudo apt-get update

Install Boot Repair

sudo apt-get install -y boot-repair && boot-repair

Launch and use, see https://help.ubuntu.com/community/Boot-Repair#Using_Boot-Repair for more details

answered Oct 19 '12 at 22:09

8128

24.8k21100137

I had to run 3. as root (sudo su) instead of just sudoing
– David Brossard
Mar 10 '13 at 20:03

1

THANK YOU!! Saved my server after a power outage. Time to buy a UPS!
– Domenic D.
Jun 29 '13 at 16:20

used with Kubuntu 13.10 and worked. Thanks.
– David
Oct 22 '13 at 13:37

add a comment |

Use Boot Repair to fix your bootloader.

Boot Ubuntu from a LiveCD or Live USB

Connect to the internet

Open a terminal, and add the Boot Repair PPA

sudo add-apt-repository ppa:yannubuntu/boot-repair && sudo apt-get update

Install Boot Repair

sudo apt-get install -y boot-repair && boot-repair

Launch and use, see https://help.ubuntu.com/community/Boot-Repair#Using_Boot-Repair for more details

answered Oct 19 '12 at 22:09

8128

24.8k21100137

Use Boot Repair to fix your bootloader.

Boot Ubuntu from a LiveCD or Live USB

Connect to the internet

Open a terminal, and add the Boot Repair PPA

sudo add-apt-repository ppa:yannubuntu/boot-repair && sudo apt-get update

Install Boot Repair

sudo apt-get install -y boot-repair && boot-repair

Launch and use, see https://help.ubuntu.com/community/Boot-Repair#Using_Boot-Repair for more details

answered Oct 19 '12 at 22:09

8128

24.8k21100137

answered Oct 19 '12 at 22:09

8128

24.8k21100137

answered Oct 19 '12 at 22:09

8128

24.8k21100137

answered Oct 19 '12 at 22:09

8128

24.8k21100137

I had to run 3. as root (sudo su) instead of just sudoing
– David Brossard
Mar 10 '13 at 20:03

1

THANK YOU!! Saved my server after a power outage. Time to buy a UPS!
– Domenic D.
Jun 29 '13 at 16:20

used with Kubuntu 13.10 and worked. Thanks.
– David
Oct 22 '13 at 13:37

add a comment |

I had to run 3. as root (sudo su) instead of just sudoing
– David Brossard
Mar 10 '13 at 20:03

1

THANK YOU!! Saved my server after a power outage. Time to buy a UPS!
– Domenic D.
Jun 29 '13 at 16:20

used with Kubuntu 13.10 and worked. Thanks.
– David
Oct 22 '13 at 13:37

I had to run 3. as root (sudo su) instead of just sudoing
– David Brossard
Mar 10 '13 at 20:03

THANK YOU!! Saved my server after a power outage. Time to buy a UPS!
– Domenic D.
Jun 29 '13 at 16:20

used with Kubuntu 13.10 and worked. Thanks.
– David
Oct 22 '13 at 13:37

add a comment |

Type ls to get a list of partitions

Enter set prefix=(hd0,msdos6)/boot/grub [you will almost certainly have to enter a different drive/partition in the brackets, you may just have to try all of those listed by ls until you find the one that works.

Type insmod normal

Type normal and you will get your boot prompt back!

See also: The helpful place where I found this. I doubt this will work for everyone encountering this error, but I've put it here in the hope it helps someone.

Once you've loaded Ubuntu, run sudo grub-install /dev/sda and sudo update-grub as soon as possible. This means you won't have to do that tedious process above every time you boot your machine.

answered Sep 14 '12 at 20:20

8128

24.8k21100137

9

when I run insmod normal it again says file not found
– tovmeod
Oct 19 '12 at 14:18

1

You can also use the command ls (hd0,msdos1)/ to check the contents of the partition, which would be faster if you have many partitions.
– Jonathan
Oct 23 '14 at 15:07

This worked for me, except I have a separate boot partition, so the format was set prefix=(hd0)/grub, since you need to reference the grub directory relative to the partition on the drive, not relative to its mount point during normal operation.
– Nick Coons
Dec 18 '15 at 5:27

add a comment |

Type ls to get a list of partitions

Enter set prefix=(hd0,msdos6)/boot/grub [you will almost certainly have to enter a different drive/partition in the brackets, you may just have to try all of those listed by ls until you find the one that works.

Type insmod normal

Type normal and you will get your boot prompt back!

See also: The helpful place where I found this. I doubt this will work for everyone encountering this error, but I've put it here in the hope it helps someone.

Once you've loaded Ubuntu, run sudo grub-install /dev/sda and sudo update-grub as soon as possible. This means you won't have to do that tedious process above every time you boot your machine.

answered Sep 14 '12 at 20:20

8128

24.8k21100137

9

when I run insmod normal it again says file not found
– tovmeod
Oct 19 '12 at 14:18

1

You can also use the command ls (hd0,msdos1)/ to check the contents of the partition, which would be faster if you have many partitions.
– Jonathan
Oct 23 '14 at 15:07

This worked for me, except I have a separate boot partition, so the format was set prefix=(hd0)/grub, since you need to reference the grub directory relative to the partition on the drive, not relative to its mount point during normal operation.
– Nick Coons
Dec 18 '15 at 5:27

add a comment |

Type ls to get a list of partitions

Enter set prefix=(hd0,msdos6)/boot/grub [you will almost certainly have to enter a different drive/partition in the brackets, you may just have to try all of those listed by ls until you find the one that works.

Type insmod normal

Type normal and you will get your boot prompt back!

See also: The helpful place where I found this. I doubt this will work for everyone encountering this error, but I've put it here in the hope it helps someone.

Once you've loaded Ubuntu, run sudo grub-install /dev/sda and sudo update-grub as soon as possible. This means you won't have to do that tedious process above every time you boot your machine.

answered Sep 14 '12 at 20:20

8128

24.8k21100137

Type ls to get a list of partitions

Enter set prefix=(hd0,msdos6)/boot/grub [you will almost certainly have to enter a different drive/partition in the brackets, you may just have to try all of those listed by ls until you find the one that works.

Type insmod normal

Type normal and you will get your boot prompt back!

See also: The helpful place where I found this. I doubt this will work for everyone encountering this error, but I've put it here in the hope it helps someone.

Once you've loaded Ubuntu, run sudo grub-install /dev/sda and sudo update-grub as soon as possible. This means you won't have to do that tedious process above every time you boot your machine.

answered Sep 14 '12 at 20:20

8128

24.8k21100137

answered Sep 14 '12 at 20:20

8128

24.8k21100137

answered Sep 14 '12 at 20:20

8128

24.8k21100137

answered Sep 14 '12 at 20:20

8128

24.8k21100137

9

when I run insmod normal it again says file not found
– tovmeod
Oct 19 '12 at 14:18

1

You can also use the command ls (hd0,msdos1)/ to check the contents of the partition, which would be faster if you have many partitions.
– Jonathan
Oct 23 '14 at 15:07

This worked for me, except I have a separate boot partition, so the format was set prefix=(hd0)/grub, since you need to reference the grub directory relative to the partition on the drive, not relative to its mount point during normal operation.
– Nick Coons
Dec 18 '15 at 5:27

add a comment |

9

when I run insmod normal it again says file not found
– tovmeod
Oct 19 '12 at 14:18

1

You can also use the command ls (hd0,msdos1)/ to check the contents of the partition, which would be faster if you have many partitions.
– Jonathan
Oct 23 '14 at 15:07

This worked for me, except I have a separate boot partition, so the format was set prefix=(hd0)/grub, since you need to reference the grub directory relative to the partition on the drive, not relative to its mount point during normal operation.
– Nick Coons
Dec 18 '15 at 5:27

when I run insmod normal it again says file not found
– tovmeod
Oct 19 '12 at 14:18

You can also use the command ls (hd0,msdos1)/ to check the contents of the partition, which would be faster if you have many partitions.
– Jonathan
Oct 23 '14 at 15:07

This worked for me, except I have a separate boot partition, so the format was set prefix=(hd0)/grub, since you need to reference the grub directory relative to the partition on the drive, not relative to its mount point during normal operation.
– Nick Coons
Dec 18 '15 at 5:27

add a comment |

Got a copy of SuperGrub and created a boot cd. I could now get logged back on to my system. Got a copy of BootRepair and had not luck getting the system to boot directly from the hard disk and had to keep using the CD. BootRepair did act a little strange since the Grub location and Grub options were grayed out. It did report a successful install.

Hard drive was originally set up:
sda1 ext4 root with boot
sda2 linux swap
sda3 ext4 used as a spare drive (holds VMs for Virtual box).

Used a copy of Ubuntu 10.10 live cd. Ran gparted to shrink the sda1 partition and created sda4 ext4 boot partition at the front of the drive and set mount point to /boot after deleting the boot directory from /. BootRepair now has options available. Installed on boot partition and can now boot from hard drive.

Being curious I decided to investigate further. The boot repair log had a peculiar entry for my sda1 ext4 partition, it was reported as DOS and had a short 8 character UUID instead of the UUID reported by blkid. grub-probe reported the file system as vfat.

After many other trials I cleared the first 440 bytes of sda1 partition record. Grub-probe now reports file system as ext2. Ran update-grub and the correct UUID for the sda1 partition appears.

edited Mar 11 '17 at 19:03

Community♦

answered Nov 13 '12 at 15:33

Mark Milakovic

411

add a comment |

Got a copy of SuperGrub and created a boot cd. I could now get logged back on to my system. Got a copy of BootRepair and had not luck getting the system to boot directly from the hard disk and had to keep using the CD. BootRepair did act a little strange since the Grub location and Grub options were grayed out. It did report a successful install.

Hard drive was originally set up:
sda1 ext4 root with boot
sda2 linux swap
sda3 ext4 used as a spare drive (holds VMs for Virtual box).

Used a copy of Ubuntu 10.10 live cd. Ran gparted to shrink the sda1 partition and created sda4 ext4 boot partition at the front of the drive and set mount point to /boot after deleting the boot directory from /. BootRepair now has options available. Installed on boot partition and can now boot from hard drive.

Being curious I decided to investigate further. The boot repair log had a peculiar entry for my sda1 ext4 partition, it was reported as DOS and had a short 8 character UUID instead of the UUID reported by blkid. grub-probe reported the file system as vfat.

After many other trials I cleared the first 440 bytes of sda1 partition record. Grub-probe now reports file system as ext2. Ran update-grub and the correct UUID for the sda1 partition appears.

edited Mar 11 '17 at 19:03

Community♦

answered Nov 13 '12 at 15:33

Mark Milakovic

411

add a comment |

Got a copy of SuperGrub and created a boot cd. I could now get logged back on to my system. Got a copy of BootRepair and had not luck getting the system to boot directly from the hard disk and had to keep using the CD. BootRepair did act a little strange since the Grub location and Grub options were grayed out. It did report a successful install.

Hard drive was originally set up:
sda1 ext4 root with boot
sda2 linux swap
sda3 ext4 used as a spare drive (holds VMs for Virtual box).

Used a copy of Ubuntu 10.10 live cd. Ran gparted to shrink the sda1 partition and created sda4 ext4 boot partition at the front of the drive and set mount point to /boot after deleting the boot directory from /. BootRepair now has options available. Installed on boot partition and can now boot from hard drive.

Being curious I decided to investigate further. The boot repair log had a peculiar entry for my sda1 ext4 partition, it was reported as DOS and had a short 8 character UUID instead of the UUID reported by blkid. grub-probe reported the file system as vfat.

After many other trials I cleared the first 440 bytes of sda1 partition record. Grub-probe now reports file system as ext2. Ran update-grub and the correct UUID for the sda1 partition appears.

edited Mar 11 '17 at 19:03

Community♦

answered Nov 13 '12 at 15:33

Mark Milakovic

411

Got a copy of SuperGrub and created a boot cd. I could now get logged back on to my system. Got a copy of BootRepair and had not luck getting the system to boot directly from the hard disk and had to keep using the CD. BootRepair did act a little strange since the Grub location and Grub options were grayed out. It did report a successful install.

Hard drive was originally set up:
sda1 ext4 root with boot
sda2 linux swap
sda3 ext4 used as a spare drive (holds VMs for Virtual box).

Used a copy of Ubuntu 10.10 live cd. Ran gparted to shrink the sda1 partition and created sda4 ext4 boot partition at the front of the drive and set mount point to /boot after deleting the boot directory from /. BootRepair now has options available. Installed on boot partition and can now boot from hard drive.

Being curious I decided to investigate further. The boot repair log had a peculiar entry for my sda1 ext4 partition, it was reported as DOS and had a short 8 character UUID instead of the UUID reported by blkid. grub-probe reported the file system as vfat.

After many other trials I cleared the first 440 bytes of sda1 partition record. Grub-probe now reports file system as ext2. Ran update-grub and the correct UUID for the sda1 partition appears.

edited Mar 11 '17 at 19:03

Community♦

answered Nov 13 '12 at 15:33

Mark Milakovic

411

edited Mar 11 '17 at 19:03

Community♦

edited Mar 11 '17 at 19:03

Community♦

edited Mar 11 '17 at 19:03

Community♦

answered Nov 13 '12 at 15:33

Mark Milakovic

411

answered Nov 13 '12 at 15:33

Mark Milakovic

411

answered Nov 13 '12 at 15:33

Mark Milakovic

411

add a comment |

answered Oct 23 '14 at 15:05

Jonathan

1216

add a comment |

answered Oct 23 '14 at 15:05

Jonathan

1216

add a comment |

answered Oct 23 '14 at 15:05

Jonathan

1216

answered Oct 23 '14 at 15:05

Jonathan

1216

answered Oct 23 '14 at 15:05

Jonathan

1216

answered Oct 23 '14 at 15:05

Jonathan

1216

answered Oct 23 '14 at 15:05

Jonathan

1216

add a comment |

answered Oct 19 '13 at 5:38

David Walker

add a comment |

answered Oct 19 '13 at 5:38

David Walker

add a comment |

answered Oct 19 '13 at 5:38

David Walker

answered Oct 19 '13 at 5:38

David Walker

answered Oct 19 '13 at 5:38

David Walker

answered Oct 19 '13 at 5:38

David Walker

answered Oct 19 '13 at 5:38

David Walker

add a comment |

-1

In my case, I had downgraded to GRUBv1 and after the upgrade to 12.10 grub2 couldn't find his files (*.mod, etc...), although the grub.cfg was there.

I found a more comprehensive manual on grub rescue:
https://help.ubuntu.com/community/Grub2/Troubleshooting#grub_rescue.3E-1

See also the command list at the begining of the page.
Thx flute flute.

answered Nov 17 '12 at 14:16

iceburn_pt

add a comment |

-1

In my case, I had downgraded to GRUBv1 and after the upgrade to 12.10 grub2 couldn't find his files (*.mod, etc...), although the grub.cfg was there.

I found a more comprehensive manual on grub rescue:
https://help.ubuntu.com/community/Grub2/Troubleshooting#grub_rescue.3E-1

See also the command list at the begining of the page.
Thx flute flute.

answered Nov 17 '12 at 14:16

iceburn_pt

add a comment |

-1

In my case, I had downgraded to GRUBv1 and after the upgrade to 12.10 grub2 couldn't find his files (*.mod, etc...), although the grub.cfg was there.

I found a more comprehensive manual on grub rescue:
https://help.ubuntu.com/community/Grub2/Troubleshooting#grub_rescue.3E-1

See also the command list at the begining of the page.
Thx flute flute.

answered Nov 17 '12 at 14:16

iceburn_pt

In my case, I had downgraded to GRUBv1 and after the upgrade to 12.10 grub2 couldn't find his files (*.mod, etc...), although the grub.cfg was there.

I found a more comprehensive manual on grub rescue:
https://help.ubuntu.com/community/Grub2/Troubleshooting#grub_rescue.3E-1

See also the command list at the begining of the page.
Thx flute flute.

answered Nov 17 '12 at 14:16

iceburn_pt

answered Nov 17 '12 at 14:16

iceburn_pt

answered Nov 17 '12 at 14:16

iceburn_pt

answered Nov 17 '12 at 14:16

iceburn_pt

add a comment |

protected by Community♦ Dec 18 at 8:32

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Cfxtrjtrk