Grub Error 5 Suse
Contents |
Favorite Rating: Error with grub while updating SLES 10 FCS how to solve grub error in redhat linux to SLES 10 SP 1This document (3656781) is provided subject
How To Fix Grub Error In Linux
to the disclaimer at the end of this document. Environment Novell SUSE Linux Enterprise Server 10
Redhat Boots To Grub Prompt
Service Pack (SP) 1 grub Situation ERROR: grub> install --stage2=/boot/grub/stage2 (hd0,0)/grub/stage1 ERROR: Error 5: Partition table invalid or corrupt ERROR: An error occurred during boot
System Boots To Grub> Prompt After A Reboot
loader installation. While the server would still boot fine, grub's graphical splash screen was missing. A text-based grub menu was presented instead. Resolution Edit the /boot/grub/menu.lst file. Make sure that the"gfxmenu" line is pointed to the correct device. In this case, the failure was occuring because it looked as follows: how to recover grub in redhat linux gfxmenu (/dev/md1, 0) /messageIn this situation the menu.lst is pointed to a software mirrored device, which the BIOS cannot recognize during bootup. It needs to be changed to the physical device to be recognized properly during bootup.The following changed fixed the issue (which was only cosmetic in nature): gfxmenu (hd0,0) /messageNOTE: This location/device may vary from server to server. DisclaimerThis Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND. Document ID:3656781Creation Date:10-JUL-07Modified Date:27-APR-12SUSESUSE Linux Enterprise Server Did this document solve your problem? Provide Feedback © Micro Focus Careers Legal close Feedback Print Full Simple Request a Call Follow Us Facebook YouTube Twitter LinkedIn Newsletter Subscription RSS
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project grub problem in linux Hire for a Full Time Job Ways to Get Help Expand Search Submit how to troubleshoot grub error in linux Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts troubleshooting linux boot problems Exchange > Questions > GRUB error 5; Ubunutu replacing Suse with Win dual boot Want to Advertise Here? Solved GRUB error 5; Ubunutu replacing Suse with Win dual boot Posted on http://www.novell.com/support/kb/doc.php?id=3656781 2007-09-23 Linux Linux Distributions 1 Verified Solution 5 Comments 728 Views Last Modified: 2013-12-15 I've spent 2 solid days on this now, searching, scouring, ect. I can't quite find exactly what I need . Bear with me....it's kind of long. I had WinXP and Suse 10.2 as a successful dual boot setup. Windows on drive 1, and Suse on drive 2. For various https://www.experts-exchange.com/questions/22847164/GRUB-error-5-Ubunutu-replacing-Suse-with-Win-dual-boot.html reasons, I decided to replace Suse with Ubuntu Feisty Fawn. Ubuntu FF (Alternate CD) seemed to install fine, but upon reboot I got the GRUB error 5 and system halt. After searching, I found the recommendations for SGD. I tried every appropriate option in SGD, including advanced options, and the only repair I was able to make was to restore the Windows MBR. Even trying to direct boot Linux with SGD fails. There were 3 main errors that I got depending on which option I chose: 1) Error 15: /grub/stage1 and /boot/stage1 -- file does not exist (But they do, because I've checked them with Explore2fs from Windows 2) Error 17: file system not recoginized (IIRC, I got this when trying to boot the hda MBR at some point.......probably before I restored it) 3) Another error was that it couldn't find the 'conf' and 'menu.lst' files. SGD offered 4 default locations to check, and none of the worked, but yet Explore2fs clearly shows that they are there. When I installed Fawn, I started with the guided installer, but then switched to manual because I want
Cannot mount selected partition × × Sorry for the inconvenience Our new site design is only available in English right now. Go to the previous site to https://www.suse.com/support/kb/doc?id=7010670 read in my language Stay here and read in English × Give https://www.suse.com/support/kb/doc?id=7014290 Us Feedback Got some feedback about the website? Let us know so we can fix it. For support information, please visit Support. Sales:1-800-796-3700 Support:1-800-858-4000 Connect with us Feedback Form We adapt, you succeed. Read Privacy Policy Required Fields* X SUSE Support My Favorites Close Please login to see your grub error favorites. Bookmark Email Document Printer Friendly Favorite Rating: Grub fails with Error 17: Cannot mount selected partitionThis document (7010670) is provided subject to the disclaimer at the end of this document. Environment SUSE Linux Enterprise Server 11 Service Pack 1SUSE Linux Enterprise Server 11 Service Pack 2 Situation After an online update grub fails with:Error 17: Cannot mount selected partition Resolution grub error in Solution: For systems running SLES11SP1 or immediate action to get the system back online please see the workaround below. On systems running SLES11SP2 update perl-Bootloader to version 0.4.89.44-0.4.2.1 or later. Workaround:Press enter to get back into the grub menu, press "e" on the default boot entry (usually the first in the list), select the line root (hd0) and press "e" again. Change root (hd0) to the desired value (e.g. if the root device is /dev/sda1, the location would be hd0,0) and press enter. Check the changes on the screen for correctness and press "b" to boot.Once the system is online, please adjust /boot/grub/menu.lst and change all root (hd0) entries to their correct values. Cause After the update /boot/grub/menu.lst contains root (hd0)for the default boot entry but should contain root (hdx,y)instead. DisclaimerThis Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND. Document ID:7010670Creation Date:23-AUG-12M
the upgrade to newer SLES 11 (SPx) × × Sorry for the inconvenience Our new site design is only available in English right now. Go to the previous site to read in my language Stay here and read in English × Give Us Feedback Got some feedback about the website? Let us know so we can fix it. For support information, please visit Support. Sales:1-800-796-3700 Support:1-800-858-4000 Connect with us Feedback Form We adapt, you succeed. Read Privacy Policy Required Fields* X SUSE Support My Favorites Close Please login to see your favorites. Bookmark Email Document Printer Friendly Favorite Rating: Error 21 in grub during the upgrade to newer SLES 11 (SPx)This document (7014290) is provided subject to the disclaimer at the end of this document. Environment SUSE Linux Enterprise Server 11 Service Pack 3SUSE Linux Enterprise Server 11 Service Pack 2SUSE Linux Enterprise Server 11 Service Pack 1SUSE Linux Enterprise Server 11 Situation Server was converted from running as a "physical server" to running as a "virtual machine" running on VMware infrastructure. The conversion was made by using VMware vCenter Converter.SymptomsDuring the upgrade process from a previous OS version (i.e. SLES 10 SP4, or older SLES 11 SP) to a newer version of SLES 11, an error is encountered when the grub bootloader is installed. The relevant text of the error is similar to:grub> install --stage2=/boot/grub/stage2 (hd0,0)/boot/grub/stage1 d (hd0) (hd0,0)/boot/grub/stage2 0x8000 (hd0,0)/boot/grub/menu.lstError 21: Selected disk does not existgrub> quitIf using a graphical install, you may see the following: Resolution Revert the VM back to the snapshot before applying the update/installation.Modify the /boot/grub/device.map to point to the proper disk/partition. Ideally, you will want to use either:/dev/disk/by-idor/dev/disk/by-uuidReboot and run the upgrade again. Cause After conversion to a virtual machine, the /boot/grub/device.map file no longer points to a proper device. Additional Information When the server is on physical hardware, the /boot/grub/device.map file may incorporate the driver name in the device. In our example it read like:(hd0) /dev/disk/by-id/cciss-xxxxxxxxxxxxxxxxxxxx(hd1) /dev/disk/by-id/cciss-xxxxxxxxxxxxxxxxxxxxAfter