Home > Error Cannot > Error Cannot Stat /boot/grub/boot.img

Error Cannot Stat /boot/grub/boot.img

Setting up linux-base (4.0ubuntu1) ... indomU=detect ## indomU=true ## indomU=false # indomU=detect ## should update-grub create memtest86 boot option ## e.g. On my desktop system the same combination runs as expected. Best regards Miche Information forwarded to [email protected], GRUB Maintainers : Bug#586815; Package grub-pc. (Tue, 13 Jul 2010 02:09:05 GMT) Full text and rfc822 format available. this contact form

Good grief! Send a report that this bug log contains spam. share|improve this answer answered Jun 14 '11 at 4:03 RolandiXor♦ 41.4k20118216 add a comment| up vote 0 down vote You can try this to: Just download and install "Boot repair" http://mygeekopinions.blogspot.com/2011/06/install-boot-repair-in-ubuntu-1104.html And now (with the new version i just updated to) the grub number reported by vbeinfo (0x105 for 1024x768x8) works fine.

Anyway, I tried it: #grub-setup '(hd0)' --root-device '(hd0,5)' and then it gives the error: grub-setup: error: cannot stat /boot/grub/boot.img indeed, there is no boot.img. Debian bug tracking system administrator . Because it worked a few weeks ago.

  • No apport report written because the error message indicates its a followup error from a previous failure.
  • What i tried but didnt help is: 1 # echo change > /sys/block/dm-X/uevent (with all dm-[0-3]) 2 I manually edited /boot/grub/device.map to contain sda instead of hda and did # grub-setup
  • There seems to be no possibility to successfully run the ubuntu installer.
  • It seems to happen in the grub-mkconfig script as mentioned in #32, at the line: GRUB_DEVICE="`${grub_probe} --target=device /`" Any ideas?

title Other operating systems: root # This entry automatically added by the Debian installer for a non-linux OS # on /dev/sda1 title Microsoft Windows XP Professional rootnoverify (hd0,0) savedefault makeactive chainloader Mark as duplicate Convert to a question Link a related branch Link to CVE Duplicates of this bug Bug #1547177 You are not directly subscribed to this bug's notifications. Grub2 wiki and the grub functional system is horrid compared to original legacy grub.KISS is no longer applicable to Arch it seems. lockold=false ## lockold=true # lockold=false ## Xen hypervisor options to use with the default Xen boot option # xenhopt= ## Xen Linux kernel options to use with the default Xen boot

Maybe the other reason was fixed, I don't know. if you want graphics support for grub just search for splash support for grub on this forum and you should come upon the splash image howto forum. Archlinux (less = more) + wmfs2-githttps://github.com/xorg62/wmfs/wiki Offline #6 2012-01-15 18:54:16 lilsirecho Veteran Registered: 2003-10-24 Posts: 5,000 Re: Force grub2 install to partition Related question:Researching the grub system, I find a update-initramfs: deferring update (hook will be called later) /bin/cp: cannot stat '/boot/initrd.img-4.3.0-7-generic': No such file or directory Failed to copy /boot/initrd.img-4.3.0-7-generic to /boot/initrd.img at /var/lib/dpkg/info/linux-image-4.3.0-7-generic.postinst line 745.

Grub2 is horrid!!!! Message #10 received at [email protected] (full text, mbox, reply): From: Colin Watson To: Michael Ostermeier , [email protected] Subject: Re: Bug#586815: grub-probe: error: cannot find a device for / is still I believe that amd64 works fine, so to see failure you have to either use qemu-user-static or actually run on the correct arch. # if running non-native arch, use qemu-user-static sudo groot=(hd0,0) # groot=daa5b96a-c32c-4091-b385-f7a1cfc1ba39 ## should update-grub create alternative automagic boot options ## e.g.

How to decline a postdoc interview if there is some possible future collaboration? Setting up flash-kernel (3.0~rc.4ubuntu57) ... Simply type the # menu entries you want to add after this comment. Serhiy Zahoriya (xintx-ua) wrote on 2011-11-21: #42 Wolfgang, I had this on a netbook which never had Windows.

Verarbeite Trigger für man-db ... > Richte grub-pc ein (1.98+20100617-1) ... > /usr/sbin/grub-probe: error: cannot stat `/dev/hda'. > Generating grub.cfg ... > Found background: /boot/grub/gnu.png > Found background image: moreblue-orbit-grub.png > http://optimisersonpc.com/error-cannot/error-cannot-load-file-code-5555h-boot-auto-ini.html How can I ask about the "winner" of an ongoing match? Mark as duplicate Convert to a question Link a related branch Link to CVE Duplicates of this bug Bug #832406 You are not directly subscribed to this bug's notifications. Reported by: Michael Ostermeier Date: Tue, 22 Jun 2010 19:42:02 UTC Severity: normal Found in version grub2/1.98-1 Done: Vladimir 'φ-coder/phcoder' Serbinenko Bug is archived.

Calendros (calendros) wrote on 2011-10-08: Re: [Bug 703009] Re: grub-probe: error: cannot stat `aufs'. #35 I think it may be caused by the fact that grub-install does not know where is I have nothing special: A Vostro 1500 with a new harddrive (no RAID or something). So i tested: > edit /etc/grub.d/10_linux and change places where it emits 'linux' > and 'initrd' commands to 'linux16' and 'initrd16' respectively. navigate here tekstr1der (tekstr1der) wrote on 2011-11-21: #43 @Wolfgang: That may be _one_ reason for this bug, but certainly not the only reason.

Adv Reply July 29th, 2010 #3 sukumarreddy View Profile View Forum Posts Private Message 5 Cups of Ubuntu Join Date Sep 2009 Beans 23 Re: grub-setup: error: Cannot read `/grub/core.img' Could you please send me the output of: sh -x /usr/sbin/grub-mkconfig -o /boot/grub/grub.cfg > * the background-picture is still not displayed > * the resolution of the screen is still bad Subscribing...

Richte grub-pc ein (1.98+20100617-1) ... /usr/sbin/grub-probe: error: cannot stat `/dev/hda'.

Now I have Kubuntu 11.10 beta2 installed with lvm and cryptsetup. Having a problem logging in? You > can use GRUB_GFXPAYLOAD_LINUX (see 'info grub' in unstable; there are > caveats) Ok, thank you. When the computer starts, the BIOS will determine which device to boot from (based on your boot order settings).

Adv Reply July 8th, 2010 #2 oldfred View Profile View Forum Posts Private Message Super Master Roaster Join Date Jun 2009 Location SW Forida BeansHidden! TL;DR change /dev/sda2 to /dev/sda share|improve this answer edited Oct 6 '15 at 6:39 community wiki 2 revs, 2 users 95%ladaghini add a comment| up vote 1 down vote Two things. Search this Thread 10-24-2004, 11:10 PM #1 brokenflea Member Registered: Nov 2003 Distribution: Slackware 11.0, FreeBSD Posts: 284 Rep: GRUB Upgrade to 2.0? his comment is here X-ray confirms Iam spineless!

Really disappointing what a crap Ubuntu has become. Report a bug This report contains Public information Edit Everyone can see this information. Registration is quick, simple and absolutely free. The simple workaround (and, in my view, the correct way to perform a recovery install!) is to chroot into the system you're trying to recover before reinstalling GRUB: https://help.ubuntu.com/community/Grub2#METHOD%203%20-%20CHROOT That's not

Upon reboot I would get the recovery screen which is absolutely useless. create the initramfs. groot=(hd0,0) # groot=0c33c34c-25ac-444b-8356-69d85a3f6ba5 ## should update-grub create alternative automagic boot options ## e.g. timeout 10 ## hiddenmenu # Hides the menu by default (press ESC to see the menu) #hiddenmenu # Pretty colours #color cyan/blue white/blue ## password ['--md5'] passwd # If used in

Try `/usr/sbin/grub-setup --help' for more information. /usr/sbin/grub-probe: error: cannot find a device for / (is /dev mounted?). Processing triggers for man-db (2.7.5-1) ...

Back to Top