GNU GRUB short for GNU GRand Unified Bootloader is a boot loader package from the GNU Project. GRUB is the reference implementation of the Free Software Foundation. How to Install Ubuntu 1. Alongside With Windows 1.
Dual Boot. Ubuntu 1. July 2. 01. 7 and Ubuntu 1. Canonical with a life circle of 5 years support. This tutorial will guide you on how you can perform the installation of Ubuntu 1. Ubuntu 1. 6. 0. 4 in dual boot with a Microsoft Operating System on machines that come pre installed with Windows 1. For fresh Ubuntu 1. Secure Boot has arrived A few weeks ago one of my computers, a desktop machine, called it quits after many productive years of service. Following a respectful period. 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 CTRLx. Ubuntu 1. 6. 0. 4 Desktop Installation Guide and Ubuntu 1. Installation Guide. This guide assumes that your machine comes pre installed with Windows 1. OS or an older version of Microsoft Windows, such as Windows 8. In case your hardware uses UEFI then you should modify the EFI settings and disable Secure Boot feature. If your computer has no other Operating System already installed and you plan to use a Windows variant alongside Ubuntu 1. Microsoft Windows and then proceed with Ubuntu 1. In this particular case, on Windows installation steps, when formatting the hard disk, you should allocate a free space on the disk with at least 2. GB in size in order use it later as a partition for Ubuntu installation. Requirements. Download Ubuntu 1. Ubuntu 1. 6. 1. 0 ISO Image as per your system architecture using following link Ubuntu 1. Desktop. Ubuntu 1. Desktop. Step 1 Prepare Windows Machine for Dual Boot. The first thing you need to take care is to create a free space on the computer hard disk in case the system is installed on a single partition. Login to your Windows machine with an administrative account and right click on the Start Menu Command Prompt Admin in order to enter Windows Command Line. Preparing Windows for Dual Boot with Ubuntu 1. Once in CLI, type diskmgmt. Disk Management utility should open. From here, right click on C partition and select Shrink Volume in order to resize the partition. C Windowssystem. Shrink Volume to Resize Partition. On Shrink C enter a value on space to shrink in MB use at least 2. MB depending on the C partition size and hit Shrink to start partition resize as illustrated below the value of space shrink from below image is lower and only used for demonstration purposes. Once the space has been resized you will see a new unallocated space on the hard drive. Leave it as default and reboot the computer in order to proceed with Ubuntu 1. Create Windows Partition for Ubuntu 1. Installation. Windows Partition for Dual Boot Ubuntu 1. Step 2 Install Ubuntu 1. Windows Dual Boot. Now its time to install Ubuntu 1. Go the download link from the topic description and grab Ubuntu Desktop 1. ISO image. Burn the image to a DVD or create a bootable USB stick using a utility such as Universal USB Installer BIOS compatible or Rufus UEFI compatible. Place the USB stick or DVD in the appropriate drive, reboot the machine and instruct the BIOSUEFI to boot up from the DVDUSB by pressing a special function key usually F1. F1. 0 or F2 depending on the vendor specifications. Once the media boot up a new grub screen should appear on your monitor. From the menu select Install Ubuntu and hit Enter to continue. Ubuntu 1. 6. 0. 4 Install Boot Screen. After the boot media finishes loading into RAM you will end up with a completely functional Ubuntu system running in live mode. On the Launcher hit on the second icon from top, Install Ubuntu 1. LTS, and the installer utility will start. Choose the language you wish to perform the installation and click on Continue button to proceed further. Select Ubuntu 1. 6. Installation Language. Next, leave both options from Preparing to Install Ubuntu unchecked and hit on Continue button again. Preparing Ubuntu 1. Installation. 7. Now its time to select an Installation Type. You can choose to Install Ubuntu alongside Windows Boot Manager, option that will automatically take care of all the partition steps. Use this option if you dont require personalized partition scheme. In case you want a custom partition layout, check the Something else option and hit on Continue button to proceed further. The option Erase disk and install Ubuntu should be avoided on dual boot because is potentially dangerous and will wipe out your disk. Select Ubuntu 1. 6. Installation Type. On this step well create our custom partition layout for Ubuntu 1. On this guide will recommend that you create two partitions, one for root and the other for home accounts data and no partition for swap use a swap partition only if you have limited RAM resources or you use a fast SSD. To create the first partition, the root partition, select the free space the shrink space from Windows created earlier and hit on the icon below. On partition settings use the following configurations and hit OK to apply changes Size at least 2. MBType for the new partition Primary. Location for the new partition Beginning. Use as EXT4 journaling file system. Mount point Create Ubuntu 1. Partitions. Create Root Partition for Ubuntu 1. Create the home partition using the same steps as above. Use all the available free space left for home partition size. The partition settings should look like this Size all remaining free space. Type for the new partition Primary. Location for the new partition Beginning. Use as EXT4 journaling file system. Mount point home. Create Home Partition for Ubuntu 1. When finished, hit the Install Now button in order to apply changes to disk and start the installation process. A pop up window should appear to inform you about swap space. Ignore the alert by pressing on Continue button. Next a new pop up window will ask you if you agree with committing changes to disk. Hit Continue to write changes to disk and the installation process will now start. Confirm Partition Changes. Confirm Write Changes to Disk. On the next screen adjust your machine physical location by selecting a city nearby from the map. When done hit Continue to move ahead. Select Your City Location. Next, select your keyboard layout and click on Continue button. Select Keyboard Layout. Pick up a username and password for your administrative sudo account, enter a descriptive name for your computer and hit Continue to finalize the installation. This are all the settings required for customizing Ubuntu 1. From here on the installation process will run automatically until it reaches the end. Create User Account for Ubuntu 1. Ubuntu 1. 6. 0. 4 Installation Process. After the installation process reaches its end hit on Restart Now button in order to complete the installation. The machine will reboot into the Grub menu, where for ten seconds, you will be presented to choose what OS you wish to use further Ubuntu 1. Microsoft Windows. Ubuntu is designated as default OS to boot from. Thus, just press Enter key or wait for those 1. Ubuntu 1. 6. 0. 4 Installation Completed. Grub Menu Select Ubuntu or Windows to Boot. After Ubuntu finishes loading, login with the credentials created during the installation process and enjoy it. Ubuntu 1. 6. 0. 4 provides NTFS file system support automatically so you can access the files from Windows partitions just by clicking on the Windows volume. Ubuntu 1. 6. 0. 4 Login. Access Windows Partitions from Ubuntu 1. Thats it In case you need to switch back to Windows, just reboot the computer and select Windows from the Grub menu. If you want to install some additional software packages and customize Ubuntu 1. Top 7 Things to Do After Ubuntu 1. How to fix Linux boot problems. Booting, or bootstrapping for us older folk, is that deeply mysterious sequence of operations performed by your computer between the moment when you switch it on and the moment its ready for you to log in. During this time, all kinds of incomprehensible messages scroll up the screen, but theyre not something you usually take much notice of, and most linux distros cover 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 well 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 Im teaching Linux on 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 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, lets 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 will report something like Missing Operating System, and come to a screaming halt. The MBR occupies the very first sector of the drive. It holds the drives partition table 6. This stage 1 loader is pretty dumb all it does is to display the word GRUB on the screen then load a second stage boot loader using a block map that is embedded into the MBR. The block map specifies the disk block numbers where the second stage loader resides. Im assuming here that were using the Grub boot loader. Theres an earlier boot loader called Lilo, but Grub is more recent, smarter, and used in most modern Linux distros. The second stage of the Grub boot loader is actually called stage one and a half, and if you list the directory bootgrub you can see the files that contain the various versions of this they have names like e. Each of these programs is able to access files by name using one particular filesystem format. Grubs ability to access files by name at boot time before linux is running is the thing that really sets it apart from Lilo. The stage one and a half program loads Grub stage 2 which is considerably larger. This stage reads the Grub configuration file usually bootgrubmenu. If Grub cant find its config file it will drop down to an interactive command line prompt to allow you to enter Grub commands manually. A typical entry in menu. SUSE 1. 0. 2. root hd. The title line simply specifies the text that will appear in Grubs boot time menu. The lines that follow specify the commands that Grub will execute if you select that item from the menu. The root line sets Grubs idea of where the root filesystem resides. Grub has its own way of naming disk partitions which is confusingly different from the naming scheme used by Linux. In Grub speak, hd. PC with IDE drives this corresponds to the Linux device name devhda, or, in some of the more recent distros, devsda. In Grub speak, hd. Linux would call this devhda. The kernel line specifies the file that Grub will load as the Linux kernel at the end of this line you may see some additional boot parameters that are passed to the kernel. More about these later. The initrd line specifies the file that contains the initial RAM Disk a file system image that will be used by the kernel as it boots. Grub is also responsible for loading this file into memory. If Grub fails to find the kernel or the ramdisk images it will report Error 1. File not found, and halt. Once the kernel starts running, it mounts the root file system from the hard drive. The name of the partition that holds this file system is passed as a parameter to the kernel, as you can see from the menu. Mounting the root file system is a key point in the boot process and if youre trying to pin down a boot time problem its vital to figure out if the kernel was able to get this far. Failure to mount the root file system will generally result in a kernel panic, though some systems just appear to halt. If the kernel succeeds in mounting the root file system, it creates a single process with process ID 1 which runs the program sbininit. If the kernel cant find init, it will either panic and halt or depending on the distro drop you into a root shell. Oh, by the way, just to add a little confusion, Ubuntu doesnt use init any more, it uses a replacement called upstart. The program init is responsible for running the scripts that will start all the other services in the system. There is one important and rather low level script run by init early in the process. On Red Hat style systems its etcrc. SUSE its etcinit. Among other things, these early scripts consistency check and mount any other disk partitions, as specified in etcfstab. Although there is certainly plenty of scope for things going wrong at this stage, we need to leave the story at that point, at least for this month. Getting to grips with Grub. A key skill in fixing boot time problems is knowing how to manually intervene in the Grub boot sequence. Most distros configure Grub to boot a default choice from the menu, but allow a short time window a few seconds in which you can press Esc to interrupt this and gain direct control of Grub. Typically this will exit from the Grub splash screen and drop to a character based menu. From here, follow the on screen instructions to select an item from the menu, and edit the commands associated with that menu selection before booting. Its even possible to drop down to a Grub command prompt where you can enter Grub commands directly for example at this point you could, in theory, manually enter the root, kernel and initrd lines from the menu. Figure 2 below shows the result of typing help at the Grub command prompt. Figure 2 the result that is output when help is typed at the Grub command prompt. Rescue Booting. If no amount of tweaking with the Grub boot commands will allow your system to boot, it may be time to perform a rescue boot, which means that youll boot Linux from an installation CD or other rescue media. The kernel and its modules are loaded off the CD, along with a small file system that is built in memory. This results in a small but working Linux system that isnt dependent on any file systems on the hard drive. You can then mount the hard drives partitions into the file system and access them to repair the damage. The installation DVD or CD of almost any modern Linux distribution can be used for this purpose there is no requirement that the rescue media is from the same distribution as the one youre trying to rescue. Its important to keep a clear head when using a rescue system because the files on your hard drive wont be in the same place when they are mounted into the rescue system as when theyre viewed by the real installation. For example, if in the rescue system I were to mount my systems root partition onto mnt, then the file I would normally see as etcfstab will be seen as mntetcfstab. Case Study 1. Our first case study concerns a RHEL5 system on which the usr directory had been placed on a separate partition.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
November 2017
Categories |