Grub Error Hd0 Read Error
communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Ask Ubuntu Questions Tags Users Badges Unanswered Ask Question _ Ask Ubuntu is a question and answer site for Ubuntu users and developers. 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 top error: hd0, 1 read error, VM can't boot up up vote 0 down vote favorite On Lubuntu 13.10 I had some virtual machines running in VirtualBox 4.2.26. While backing up, all I ever did was make a copy of VirtualBox VMs folder. I have now switched to OS X, and now I can easily import my VMs, by just copy them out of my backup into the new VirtualBox VMs folder and then go in and manually open the VMNAME.vbox file in each VM folder. After my BackTrack 5 disco inside VirtualBox lights up, message I get is: error: hd0, 1 read error. grub rescue> _ I have prompt ready to take some commands. grub2 virtualbox virtualization grubrescue share|improve this question asked Oct 28 '14 at 18:17 MiniBug 106 add a comment| 1 Answer 1 active oldest votes up vote 0 down vote boot a Live CD and reinstall grub2 by chroot'ing to the 'broken' system. Boot into Live CD Open Terminal (CTRL+ALT+T) Enter the following commands: sudo fdisk -l And find your Ubuntu partition (should be /dev/sda1 if it is the first partition) sudo mount /dev/sda1 /mnt sudo mount --bind /sys /mnt/sys sudo mount --bind /proc /mnt/proc sudo mount --bind /dev /mnt/dev sudo chroot /mnt Now reinstall Grub2 sudo apt-get install --reinstall grub2 share|improve this answer answered Oct 28 '14 at 18:30 vembutech 1,968149 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using G
anything about commands and am vitrually operating system illiterate.. Have a Ubuntu 11.10 CD which I initially used to install operating system as a single boot . Message sent on Net Book. Could anybody help me? Also interested in changing to a dual boot system with Windows XP. However, boot up is my urgent problem and can pose a separate question when PC up and running. Question information Language: English Edit question Status: Answered For: Boot-Repair Edit question Assignee: No assignee Edit question Last query: 2012-09-26 Last reply: 2012-09-26 Related bugs Link existing bug Related FAQ: None Link to a FAQ YannUbuntu (yannubuntu) http://askubuntu.com/questions/542843/error-hd0-1-read-error-vm-cant-boot-up said on 2012-09-16: #1 hello Chris please run Boot-Repair, click the "Recommened repair" button, and indicate the URL that will appear. Reboot the pc, and tell what you observe. Chris Hirtes (hirtes) said on 2012-09-17: #2 Hello Yan, Thanks for response. Tried to run from Terminal "Boot repair" and "Run Boot-repair" and, as expected, got error messages. Then booted up with Ubuntu 11.10 CD using "try installation" but could not https://answers.launchpad.net/boot-repair/+question/208655 find programme using dash. Goggled "Boot-repair" and choose first result "Boot-Repair- Community Ubuntu Documentation". Followed "install boot-repair in Ubuntu and ended up with update option -selected yes and received message "Updating.." which continued for over an hour before I exited. Used dash again and found "Boot repair" - "Scanning systems .." message came up. Still running after 20 minutes. I must have done something wrong - I am very much a novice. Any ideas? Chris YannUbuntu (yannubuntu) said on 2012-09-17: #3 ok, let's do it simple: 1) download the ISO of Boot-Repair-Disk : https://sourceforge.net/projects/boot-repair-cd/files/ 2) burn it onto a CD 3) boot your computer on it. 4) You see this black screen: http://ubuntuforums.org/showpost.php?p=11181195&postcount=1 5) choose "32bits session" 6) Boot-Repair will automatically start 7) It will ask you if you want to update the software --> answer "NO" 8) the main window will appear 9) click the "Recommended Repair" button 10) Write the URL (something like http://paste.ubuntu.com/ XXXXXXXX ) that will appear in the final window. 11) Reboot the PC, and check if it's better 12) if you still have problems, please tell me the URL that you wrote on your paper. Chris Hirtes (hirtes) said on 2012-09-26: #4 YannUbuntu (yannubuntu) said on 2012-09-26: #5 ? Chris Hirt
code. Start a free trial of Bitbucket Server and get your shirt. On this page How it looks? Basic commands available. The Rescue Shell. After Booting the system. As GRUB 2's ability to fix boot problems has greatly https://www.howtoforge.com/tutorial/repair-linux-boot-with-grub-rescue/ improved over the original GRUB bootloader. This article provides you with information on available options for repairing GRUB 2 boot issues and specific instructions on how to use the GRUB 2 terminal. The instructions are written for GRUB 2. How it looks? There are basically three error messages or screens when GRUB fails to boot. grub>: This is the screen mode you see when GRUB has found everything except the configurationn file. This file probably will grub error be grub.conf. grub rescue>: This is the mode when GRUB 2 is unable to find the GRUB folder or its contents are missing/corrupted. The GRUB 2 folder contains the menu, modules and stored environmental data. GRUB: Just "GRUB" nothing else indicates GRUB 2 failed to find even the most basic information needed to boot the system. These are the basic errors that may occur during booting. Although there are a few more errors that can be seen grub error hd0 on the screen like frozen splash screen, Busybox or Initramfs: GRUB 2 began.... But each of the GRUB 2 failure modes can be corrected either from GRUB 2 terminal or the Live boot CD or DVD of the distro, there are also 3rd party rescue tools available out there. Basic commands available. These are the commands that can be used when you enter the GRUB 2 terminl mode by pressing "c". boot (Initiate the boot, also F10 or CTRL-x) cat (view the contents of config or txt files; cat (hd0,1)/boot/grub/grub.cfg) configfile (Load a GRUB 2 configuration file such as grub.cfg; configfile (hd0,5)/boot/grub/grub.cfg.) initrd (Loads the initrd.img, necessary for booting; initrd (hd0,5)/initrd.img.) insmod (Loads a module; insmod (hd0,5)/boot/grub/normal.mod, or insmod normal.) linux (Loads the kernel; insmod /vmlinuz root=(hd0,5) ro.) loop (Mount a file as a device; loopback loop (hd0,2)/iso/my.iso.) ls (lists the contents of a partition/folder; ls, ls /boot/grub, ls (hd0,5)/, ls (hd0,5)/boot.) lsmod (List loaded modules.) normal (Activate the normal module, if loaded.) search (Search for a device. Type help search for the available options.) set (Review current settings, or set XXX to set a variable such as colors, prefix, root.) vbeinfo (Display GRUB 2 available resolutions.) The Rescue Shell. If you get a rescue shell, this usually means that GRUB failed to load the "normal" module for some reason. It may be possible to work around this