Grub Hard Disk Error Boot San
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and grub rescue commands policies of this site About Us Learn more about Stack Overflow the company
Grub Rescue Commands List
Business Learn more about hiring developers or posting ads with us Unix & Linux Questions Tags Users Badges Unanswered grub rescue boot windows Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute: Sign grub rescue unknown filesystem 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 RHEL 5 Booting from Local Hardisk & SAN Harddisk via grub up vote 1 down vote favorite I had a RHEL machine booting from local disk. Later I removed local disk & booted from a SAN disk and installed
Ubuntu Grub Repair
RHEL on it. Now I have read about a grub.conf file: root (hd0,0) kernel /boot/vmlinuz-2.6.18.2-34-default root=/dev/hda1 vga=0x317 showopts initrd /boot/initrd-2.6.18.2-34-default Grub stage1 boots from MBR and then when it goes to Stage2 it takes these entry parameters. What is the simplest way to set and choose which OS the machine will boot from? rhel multipath-storage share|improve this question edited Nov 6 '14 at 12:37 geedoubleya 2,063617 asked Nov 6 '14 at 11:14 Ashish 1457 add a comment| 1 Answer 1 active oldest votes up vote 2 down vote accepted When grub goes to stage 2, it will present the kernel selection menu. The best way to configure this is to use either the SAN disk or the local disk as your MBR (master boot record) then update the /boot/grub/grub.conf file to include both stanza entries from the local HDD and the SAN disk. Then use the default=0 entry to set the default OS kernel to load. default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz root (hd0,0) kernel /boot/vmlinuz-2.6.18.2-34-default root=/dev/hda1 vga=0x317 showopts initrd /boot/initrd-2.6.18.2-34-default ### SAN stanza entry ### root (sd0,0) kernel /boot/vmlinuz-2.6.18.2-34-default root=/dev/sda1 vga=0x317 showopts initrd /boot/initrd-2.6.18.2-34-default The second entry will be default=1. Note
Get Kubuntu Get Xubuntu Get Lubuntu Get UbuntuStudio Get Mythbuntu Get Edubuntu Get Ubuntu-GNOME Get UbuntuKylin Ubuntu Code of Conduct Ubuntu grub rescue no such partition Wiki Community Wiki Other Support Launchpad Answers Ubuntu IRC Support AskUbuntu grub command line boot Official Documentation User Documentation Social Media Facebook Twitter Useful Links Distrowatch Bugs: Ubuntu PPAs: Ubuntu Web Upd8:
Grub Commands
Ubuntu OMG! Ubuntu Ubuntu Insights Planet Ubuntu Activity Page Please read before SSO login Advanced Search Forum The Ubuntu Forum Community Ubuntu Official Flavours Support General Help [SOLVED] Grub http://unix.stackexchange.com/questions/166367/rhel-5-booting-from-local-hardisk-san-harddisk-via-grub 'Read Error' - AHCI Boot Issue Having an Issue With Posting ? Do you want to help us debug the posting issues ? < is the place to report it, thanks ! Page 1 of 2 12 Last Jump to page: Results 1 to 10 of 20 Thread: Grub 'Read Error' - AHCI Boot Issue Thread Tools Show https://ubuntuforums.org/showthread.php?t=2051302 Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode September 1st, 2012 #1 RyanSharp View Profile View Forum Posts Private Message First Cup of Ubuntu Join Date Sep 2012 Beans 11 Grub 'Read Error' - AHCI Boot Issue I've had an issue for the past few weeks, that I've been desperately trying to solve. I bought a brand new Samsung 64GB SSD, installed Windows 7. Easy peasy so far. I then installed Ubuntu to run along side it, using my 1TB secondary HDD as /Home and Swap. Installed completely fine. However, after rebooting after install, GRUB would not load, instead I receive the following error: HTML Code: Loading Operating Systems Read Error Though I have to admit, it's possible that it is in fact a Motherboard Read Error, and not from GRUB, but I can't be sure. Anyway, if I go into BIOS and change the SATA mode to 'IDE', Grub loads fine, however doing so, no OS would boot afterwards. I also
operations performed by your computer between the moment when you switch it on and the moment it's ready for you to log in. During this time, all kinds of incomprehensible messages scroll up the screen, http://www.tuxradar.com/content/how-fix-linux-boot-problems but they're not something you usually take much notice of, and most linux distros cover http://www.supergrubdisk.org/wiki/Howto_Fix_Grub them up with a pretty splash screen and a nice encouraging progress bar. This is all fine, of course, until it stops working. In this tutorial we'll examine the boot process in more detail, looking in particular at what can go wrong, and how to diagnose and fix the problem. Grokking the problem When I'm teaching Linux on grub rescue one of my courses, many attendees tell me they are interested in troubleshooting of one form or another. Some of them are looking for a cookbook approach - "If you see the error message X, run command Y", but troubleshooting rarely works that way. My initial advice to anyone who needs to troubleshoot is always the same: "The most important thing in troubleshooting is to understand how the system is supposed to grub rescue commands work in the first place. The second most important thing is figuring out exactly what the system was trying to do when it went wrong." Figure 1: the normal sequence of events when booting Linux. With this in mind, let's take a look at how Linux boots. Knowing the normal sequence of events, and determining how far it got before it ran into trouble, are key to diagnosing and fixing boot-time problems. Figure 1 above, right shows the normal sequence of events (green arrows) and indicates some of the possible failure paths (red arrows). Picking yourself up by your bootstraps Booting is a multi-stage affair. When a PC is powered up, control initially passes to a program (called the BIOS) stored in read-only memory on the motherboard. The BIOS performs a self-test of the hardware and scouts around looking for a device to boot from. The BIOS provides configuration screens that allow you to assign the order in which it searches for a bootable device, and modern BIOSes support a wide range of boot devices, including PXE booting from a network server. The only case we consider here is booting from the hard drive. The BIOS loads the Master Boot Record (MBR) of the selected boot device and executes it. (If this fails, the BIOS w
no longer boots! Contents 1 Other titles for this same problem. 2 Rescatux 3 Windows Solution 4 Quick solution 5 Not So Quick solution 6 Classical solution 7 Advanced solution 8 Problematic solution 9 GRUB solution (on its own) 10 GRUB solution (Linux shell) 11 GRUB2 solution (on its own) 12 GRUB2 solution (Linux shell) (Recommended) 13 GRUB2 solution (Linux shell) (Maybe deprecated) 14 Tecnical explanation 15 One thing you should know 16 TIP 17 Problems? 18 External resources Other titles for this same problem. How do I restore GRUB? I have lost my GRUB, how do I find it again? I have reinstalled Windows and the Ubuntu selection menu is not there. Rescatux Please check the complete Wizard at: Wizard – Restore Grub with Rescatux Select Restore grub / Fix Linux Boot option and click on OK button Select the partition where your main Linux is and click on OK button Select the hard disk where you want Grub to be installed (usually the first one) Grub was installed OK confirmation / Grub was not installed error will appear Windows Solution This is the less complicated and most easy solution for a Windows user. Please check: Auto Super Grub Disk. Quick solution GRUB => MBR & !LINUX! (1) AUTO ;-))) SGD fixes GRUB automagically for you and presents your grub boot menu again. Not So Quick solution GRUB => MBR & !LINUX! (>2) MANUAL |8-) Choose the partition where the Linux GRUB you want to recover is located. Choose the partition where the Linux GRUB you want to boot is located. Classical solution Choose Language & HELP :-))) English Super Grub Disk Gnu/Linux Fix Boot of Gnu/Linux (GRUB) Choose the partition where the Linux GRUB you want to recover is located and SGD prompts you: SGD HAS SUCCEEDED. Advanced solution Sometimes the hard disk where you want to GRUB to be installed might not be the first one. If you want to install GRUB into a non-standard MBR you can choose: Super Grub Disk (WITH HELP) :-))) English Super Grub Disk Advanced Grub Restore Grub to MBR Restore Grub to MBR manually Select the partition where GRUB it is found (i.e. stage1 is found). Select the hard disk where you want GRUB installed to its MBR. Problema