Home > Error Cannot > Error Cannot Open /boot/grub/device.map

Error Cannot Open /boot/grub/device.map

Contents

Acknowledgement sent to "Felix Zielcke" : Extra info received and forwarded to list. Done > Building dependency tree > Reading state information... Thanks for the info! Using mkinitramfs-kpkg to build the ramdisk. his comment is here

The command should specify a device and when executed will install the required GRUB files to the location called for in the options. Full text and rfc822 format available. This provides a backup in case the MBR or boot record data on a particular drive becomes corrupted. I just started to help :) Good that it's now fixed for you.

Error Cannot Open /boot/grub/device.map

Code: [email protected]:~$ sudo grub-install --root-directory=/media/a6a3e0fd-ff99-4051-89f1-7cd5295b3360 /dev/sda Installation finished. If the user wants to use a specific partition for Ubuntu the user must select the Ubuntu partition and the drive on which to embed the bootloader information. Mark as duplicate Convert to a question Link a related branch Link to CVE You are not directly subscribed to this bug's notifications.

Y is the partition number: Substitute the correct partition: sda1, sdb5, etc. Disk Utility, introduced in Ubuntu 9.10, can easily assign labels to existing partitions. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the Full text and rfc822 format available.

Downgrading to grub 0.97-35 did not > help, but downgradingto grub 0.97-27 in stable did. > > Here is the output from the failed kernel postinst with grub 0.97-36 > (note Darko. ----------------------------------------------------------------------- Ubuntu 14.04 LTS 64bit & Windows 10 Pro 64bit Adv Reply July 3rd, 2010 #6 pwaugh View Profile View Forum Posts Private Message Gee! Install Setup not working Where are the oil platforms in Google Earth? It will not replace or restore grub.cfg or fix corrupted files.

Full text and rfc822 format available. Downgrading to grub 0.97-35 did not help, but downgradingto grub 0.97-27 in stable did. Acknowledgement sent to Nick Hastings : Extra info received and forwarded to list. I will explictly tell you below. > But for me it looks > like grub-legacy is able to boot fine with just > /grub/ (for it) and not > /boot/grub/ This

Message #22 received at [email protected] (full text, mbox, reply): From: "Felix Zielcke" To: "Nick Hastings" , <[email protected]> Subject: Re: Bug#477304: Grub fails to find /boot/boot/grub/device.map Date: Tue, 22 Jul 2008 https://ubuntuforums.org/showthread.php?t=1522847 Message #12 received at [email protected] (full text, mbox, reply): From: "Felix Zielcke" To: "Nick Hastings" Cc: <[email protected]> Subject: Debian bug #477304 Grub fails to find /boot/boot/grub/device.map Date: Sun, 20 Error Cannot Open /boot/grub/device.map Message #17 received at [email protected] (full text, mbox, reply): From: Nick Hastings To: Felix Zielcke Cc: [email protected] Subject: Re: Debian bug #477304 Grub fails to find /boot/boot/grub/device.map Date: Tue, Other valid candidates: mkinitramfs-kpkg mkinitrd.yaird Not updating initrd symbolic links since we are being updated/reinstalled (2.6.24-5 was configured last, according to dpkg) Not updating image symbolic links since we are being

The UUID method may actually work but throws an error message falsely. http://megavoid.net/error-cannot/error-cannot-mount-device-uloader.html Full text and rfc822 format available. Toggle useless messagesView this report as an mbox folder, status mbox, maintainer mbox Report forwarded to [email protected], Grub Maintainers : Bug#477304; Package grub. If using the LiveCD, complete the steps up to and including the sudochroot command (Step 9) in the previous section.

Full text and rfc822 format available. When I run the command: grub-install --target=i386-pc --recheck --debug /dev/sda It errors stating: Installing for i386-pc platform. That was the "specific" error message. weblink Full text and rfc822 format available.

Unix & Linux Stack Exchange works best with JavaScript enabled Thanks Reply sent to "Felix Zielcke" : You have taken responsibility. Only the MBR data is changed.

Run the grub-setup-d command as described below.

This may correct GRUB 2 failures due to corrupted files and improper configurations as well as for missing folders/files deleted by the user. Any ideas? Last edited by sugartest (2014-07-21 12:38:58) An Arch Linux enthousiast and a Linux fan in general, mostly interrested in command line use, security issues, code learning and networks. If this happens try rebooting.

My math students consider me a harsh grader. You will be warned you are removing the bootloader. Replace XXXX in the command with the UUID, or replace /media/XXXX with the correct location if the partition is not mounted in /media. http://megavoid.net/error-cannot/error-cannot-get-memory-statistics-from-device.html How to cope with too slow Wi-Fi at hotel?

The only explanation is that > I should have run "grub-install (hd0)" to *really* switch to grub2, > but why the menu.lst from grub-legacy was not removed on purge? > Please Finding valid ramdisk creators. You don't have a grub.cfg created. Windows 8 to Windows 8.1).

[email protected]:/# Adv Reply July 3rd, 2010 #10 darkod View Profile View Forum Posts Private Message Staff Emeritus Join Date Nov 2009 Location Mataro, Spain Beans 12,998 DistroUbuntu 14.04 Trusty Tahr I boot from the live CD, and do the following after mounting the Ubuntu partition from Places: Code: [email protected]:~$ mount | tail -1 /dev/sda5 on /media/a6a3e0fd-ff99-4051-89f1-7cd5295b3360 type ext4 (rw,nosuid,nodev,uhelper=udisks) and.... Full text and rfc822 format available. This will reinstall the GRUB 2 files on the mounted partition to the proper location and to the MBR of the designated device.

All rights reserved.REDDIT and the ALIEN Logo are registered trademarks of reddit inc.πRendered by PID 18678 on app-565 at 2016-10-10 15:49:56.790484+00:00 running 9927328 country code: DE. This partition can be created via GParted or other partitioning tools, or via the command line. I have recovery DVDs in case. found: /boot/boot/grub > grub-probe: error: Cannot open `/boot/grub/device.map' > User postinst hook script [update-grub] exited with value 1 > dpkg: error processing linux-image-2.6.24-1-686-bigmem (--configure): > subprocess post-installation script returned error exit

Instead it complained: > > grub-probe: error: Cannot open `/boot/grub/device.map' > > On a system with a separate /boot partition (such as this one), I > would have thought that device.map