General :: Getting Output From GRUB During Boot From USB Key?
Oct 5, 2010
I have a home-brewed Linux system that I've installed on a USB key. I'm plugging this into a laptop. I can tell from what is going on that it has successfully loaded the kernel and is running the shell script that is specified on the "kernel"he GRUB configuration.But... although I can get output from printk() calls in the kernel just fine, I get nothing from "echo" commands (or any other commands) in the initialization shell script. I can see that the commands are being run,t the output is just disappearing into the void.This is problematic because there are other problems, but I can't get debug output to track those down...Given that printk() output goes to the laptop screen as expected, it seems that GRUB must be sending other output to something other than the console, yet the grub.conf configuration is quite simple:
This is what I get when following the instructions to fix grub. I type in "grub-install /dev/sda" and that's the error I get.I'm trying to put Ubuntu or Mint on a Dell Mini 9 with 16gb ssd, but no matter what I do I cannot achieve this goal
I am learning Linux administration and I am new in this area. Currently I am trying to find out which drive has grub.conf file. Following commands giving me correct output (hd0,0):
when I was updating my Ubuntu, the Linux kernel images were also updated (to 2.6.35-x), and the one I was using was removed (2.6.32-x). Since then, none of the 2.6.35-x kernels boot at all. I have upgraded several times, and now have installed 2.6.35-23-generic and 2.6.35-24-generic. Neither boots. I am running 2.6.32-24-generic, but there are no sources or headers for that. I even compiled 2.6.35-7 and 2.6.36, but neither worked either.
After I select the kernel in Grub, the screen goes blank, my hard drive spins a few times, and the screen stays blank, until finally the computer just shuts off. I tried running one of those kernels, and then booting normally after that failed, and looked at /var/log/kern.log. I saw messages from the last time I booted using 2.6.32-24-generic, and messages from when I booted just now (identified by the timestamps), but I could see no messages that took place in between, when the nonfunctional kernel should have been loading.
I really don't know what other information to add. I am running Ubuntu 10.10 on a Toshiba Satellite A215-S7411. The hard drive is an external hard drive connected with a USB Y cable. like VirtualBox, do not run without having the drivers compiled, and to compile them, I need the kernel headers, which I don't have and are not available in the repositories.
Problem: I have installed two Ubuntu servers, 10.04 32-bit and 10.10 64-bit, in a multi-boot environment (also have FDOS and WinXPsp3). The 64-bit will not boot because grub can't find the UUID for the disk with the 64-bit system.
Brief Background: Installed 10.04 LTS two months ago with no problems. 10.04 is in a primary partition on hda with FDOS.
Installed 10.10 (64-bit) in a new primary partition on the same hd. The install seemed to go ok, but the MBR and the fs on the 10.04 were corrupted; could not boot. Restored drive, and rebuilt grub.
Installed 10.10 on separate hd (hdb). In grub step all OS's were recognized so I pointed the grub to hda. Grub failed to boot.
Rebuilt grub from 10.04 on hda. All systems recognized but 10.10 will not boot because it says it cannot locate the UUID specified.
Compared the grub.cfg for both systems, the UUID specified for hdb is the same. Also, when I mount the drive for 10.10 on the 10.04 system the drive UUID is consistent.
I know I must be missing some thing, but I know not what. Have searched and can't find any clues. All other OS's boot ok.
Hardware: AMD64 4GB, 2 internal IDE drives (hda and hdb), 1 internal SATA (hdc WinXP), various USB and Firewire Drives (no bootable systems).
i installed slackware then i unistalled it and installed debian then i decided to go back to slackware but it wont boot because i have the grub boot loder how do i fix this
i am trying to change the boot order on the GRUB menu so that the countdown automatically starts on an older kernel. From what i can see all the solutions on the web want me to edit the /boot/grub/menu.lst file. The problem is that i don't have one. Someone also mentioned that if i don't have a menu.lst file then i should look for the grub.conf file. I don't have on of those either. The closest thing in /boot/grub is grub.cfg but that looks nothing like the descriptions i have heard of /boot/grub/menu.lst file
I just recently installed a kernel, everything works fine after reboot except. When I use nano -w /boot/grub/grub.conf I get /boot/grub/grub.conf: No such file or directoryIs there something i have to do after installing a new kernel in Gentoo Linux.I can't access my /boot all that appears there is a symlink to /boot How can i see my kernels located in /boot.
I had a dual boot machine with fedora 12 and windows vista and I could use grub boot-loader to switch between two. Few days ago windows got corrupt and I have to reinstall it. I put windows 7 now and as usual it erased grub. So to reinstall I put the fedora 12 installation CD on and followed some usual setup steps. When I got the command line I issued the command "grub-install /dev/sda" (sda not hda because It showed bunch of sda, sda1..) but surprisingly it said grub command not found. I remember doing it before while it worked fine.
I'm trying to install Xubuntu, but I don't have an empty CD and my computer boots only from HDD and CD. I've extracted ISO's contents into my HDD root and have installed a (non-working) Linux and GRUB. So I've tried this boot entry:
root (hd1,msdos1) linux /casper/vmlinuz initrd /casper/initrd.lz boot
But it boots same as the non-working Linux install
What is the generic way to create a boot CD for any given Linux distro using grub ? Can anyone give me the exact commands for creating the proper ISO image. From there I know how to burn the ISO image to CD.
I am inexperienced in using Linux, and just installed Ubuntu 10.10 on an external hard drive. I didn't want to mess around with re-partitioning my hard drive, which has Windows 7. I figured that I could just run Ubuntu from the external, and if it gave me any problems with Windows, which I unfortunately need for work, I could just unplug it and boot normally. However, GRUB appears to have installed some component to the local hard drive. Whenever I try to boot from the local hard drive, I get this error message: "error: no such device: 8b84f351-7770-4908-b12f-0cbd31bc3662 grub rescue> " Another thing is that in the boot menu, only the CD/DVD drive and local hard drive are options, it won't even register the external. Any suggestions on what may have caused this error? I saw from other posts that GRUB doesn't like multi-drive systems. Also, would it be possible to delete GRUB from my system, then allowing Window's MBR to take over?
I have yet to find any coherent instructions anywhere on earth on this and I am wondering if its ever actually been done before. Assuming I have root partitions on /dev/hda1, /dev/hda2, /dev/hda7. How would I do it? What would I type in the terminal?
I regularly update my ubuntu (10.04), and new minor versions keep accumulating on the GRUB screen. Right now I have 5 different versions listed on the GRUB, even though I always select the latest version to work with.
Am I supposed to do anything to get rid of the old version references? Do these old versions affect disk space/performance?
I used Windows to reformat my Ubuntu partition and now I can't boot anything. What's the best way to recover my netbook? I'm only able to use a 256 MB flash drive.
I just installed Ubuntu 10.04 onto my toshiba C655 iCeleron 900 2.20ghz 1GB RAM. I have win7 and I have a 4GB swap partition. How Do I change the Boot order in Grub? I saw instructions somewhere else to type sudo, etc in the command line and was getting access denies...
Slackware is my main desktop, however, I decided to give Fedora 15 a try and overwrote the MBR installing it with grub. Now I want to keep fedora and its grub, just I can't get slackware to boot.Fdisk:
Code: Disk /dev/sda: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
I'm trying to install MS Windows from my Linux box. Because I have no CD drives nor USB ports, I can't use any live media to boot the computer and install Windows from the installation disk. So I've created a FAT partition and copy DOS files on that, so that I can boot this partition and install Windows from there. But the problem is I still haven't able to get it to boot.
Here's the output of fdisk -l code...
I created the partition by using cfdisk to format it as type 0B: WIN95 FAT32, and made dos filesystem on it using:
Code: mkfs.msdos /dev/hda1 But when I reboot and select the DOS entry in GRUB, it tells me that: "This is not a bootable disk. Please insert a bootable floppy and press any key to try again."
what I'm missing or doing wrong here? Do I need to change something on the MBR of hda1 etc...
Today I was forced to reformat windoze and of course lost grub so I can't boot ubuntu 9.10. I found two suggestions in previous posts which didn't work. One suggested using the install disk as a rescue disk and as root run grub. I entered sudo grub and the cmd was accepted but the cmnd grub was not found.
The second was to sudo grub -install and again grub was not found. Both these suggestions were for a win 98/mandrake installation.
Do I have to reinstall ubuntu? If so there is a problem in partitioning. Setup sees there is already an ubuntu os on the disk. In fact two of them. I forget why, but I reinstalled ubuntu and ended up with two in the grub menu. I was advised not to try to repair grub and didn't. Now I have two and it thinks I want to put the third one side by side, or erase and use the entire disk. There was a third choice but I forgot already exactly what it was and didn't like it anyway. If I erase and use the entire disk, won't I lose windoze? If I put them side by side I will then have three which which will waste disc space. The discs aren't that big being only about 10gb. I don't think I want to waste the space with a third ubuntu.
I had debian squeeze already installed, then installed win 7. Windows overwrote by MBR, as I expected it to, so I used an ubuntu live cd to reinstall grub2 to debian root.
I rebooted, and sure enough I had grub back. The boot menu has debian on it. Just debian (crunchbang actually, but its the same thing).
So I added a script in /etc/grub.d (called Windows_11) to create a windows chainloader entry in grub.cfg, and ran update-grub.
Update-grub picks up my /etc/grub.d/Windows_11 script, and adds an appropriate chainloader entry to /boot/grub/grub.cfg.
So I would expect this new chainloader entry to show up in my boot menu when I boot up. But it doesn't; on booting I only have the option to select debian.
Here is my /boot/grub/grub.cfg -
Code: ### BEGIN /etc/grub.d/10_linux ### menuentry 'CrunchBang Linux, with Linux 2.6.32-5-686' --class crunchbang --class gnu-linux --class gnu --class os { insmod part_msdos
I'm working my way through my Linux self-education and I'm hitting a slight road block. After consulting forum posts here and elsewhere, I have tried to alter my grub boot order by editing my menu.lst file found in /boot/grub. I don't seem to be having any luck. Changing the default [value] doesn't seem to work, nor does the savedefault. Below is a copy of my file.
Code: # menu.lst - See: grub(8), info grub, update-grub(8) # grub-install(8), grub-floppy(8), # grub-md5-crypt, /usr/share/doc/grub # and /usr/share/doc/grub-doc/.
default 4 # Set the default entry to the entry number NUM. Numbering starts from 0, and # the entry number 0 is the default if the command is not used. # You can specify 'saved' instead of a number. In this case, the default entry # is the entry saved with the command 'savedefault'. # WARNING: If you are using dmraid do not use 'savedefault' or your # array will desync and will not let you boot your system. default0
## timeout sec # Set a timeout, in SEC seconds, before automatically booting the default entry # (normally the first entry defined). timeout10 ## hiddenmenu # Hides the menu by default (press ESC to see the menu) #hiddenmenu
# Pretty colours #color cyan/blue white/blue ## password ['--md5'] passwd # If used in the first section of a menu file, disable all interactive editing # control (menu entry editor and command-line) and entries protected by the # command 'lock' # e.g. password topsecret # password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/ # password topsecret # examples
# titleWindows 95/98/NT/2000 # root(hd0,0) # makeactive # chainloader+1 # titleLinux # root(hd0,1) # kernel/vmlinuz root=/dev/hda2 ro # Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST ### BEGIN AUTOMAGIC KERNELS LIST ## lines between the AUTOMAGIC KERNELS LIST markers will be modified ## by the debian update-grub script except for the default options below ## DO NOT UNCOMMENT THEM, Just edit them to your needs
## ## Start Default Options ## ## default kernel options ## default kernel options for automagic boot options ## If you want special options for specific kernels use kopt_x_y_z ## where x.y.z is kernel version. Minor versions can be omitted. ## e.g. kopt=root=/dev/hda1 ro ## kopt_2_6_8=root=/dev/hdc1 ro ## kopt_2_6_8_2_686=root=/dev/hdc2 ro # kopt=root=UUID=18250e14-e47e-4bf9-a927-6456120575f8 ro ## default grub root device ## e.g. groot=(hd0,0) # groot=18250e14-e47e-4bf9-a927-6456120575f8
## should update-grub create alternative automagic boot options ## e.g. alternative=true ## alternative=false # alternative=true ## should update-grub lock alternative automagic boot options ## e.g. lockalternative=true ## lockalternative=false # lockalternative=false
## additional options to use with the default boot option, but not with the ## alternatives ## e.g. defoptions=vga=0x317 resume=/dev/hda5 # defoptions=vga=0x317 ## should update-grub lock old automagic boot options ## e.g. lockold=false ## lockold=true # lockold=false ## Xen hypervisor options to use with the default Xen boot option # xenhopt=
## Xen Linux kernel options to use with the default Xen boot option # xenkopt=console=tty0 ## altoption boot targets option ## multiple altoptions lines are allowed ## e.g. altoptions=(extra menu suffix) extra boot options ## altoptions=(recovery) single # altoptions=(recovery mode) single
## controls how many kernels should be put into the menu.lst ## only counts the first occurence of a kernel, not the ## alternative kernel options ## e.g. howmany=all ## howmany=7 # howmany=all ## should update-grub create memtest86 boot option ## e.g. memtest86=true ## memtest86=false # memtest86=true
## should update-grub adjust the value of the default booted system ## can be true or false # updatedefaultentry=false ## should update-grub add savedefault to the default options ## can be true or false # savedefault=false ## ## End Default Options ## splashimage=18250e14-e47e-4bf9-a927-6456120575f8/boot/grub/splash.xpm.gz
titleBackTrack 4 R2, memtest86+ uuid18250e14-e47e-4bf9-a927-6456120575f8 kernel/boot/memtest86+.bin quiet ### END DEBIAN AUTOMAGIC KERNELS LIST # This is a divider, added to separate the menu items below from the Debian # ones. titleOther operating systems: root
# This entry automatically added by the Debian installer for a non-linux OS # on /dev/sda1 titleWindows Vista/Longhorn (loader) root(hd0,0) savedefault makeactive chainloader+1
Can't get into GRUB to reset root password. Hitting ESC only toggles between verbose boot information and progress screen. Holding SHIFT does not bring up the GRUB screen for Runlevel editing. Only found correct key strokes once and forgot what they are. While I'm here, does anyone know how to choose and permamently select a kernel version for bootup?
I am trying to boot up linux on a SATA drive. The SATA drive already had some other linux. I 'fdisk' the SATA drive and cleared all partitions. Now tried to CD boot with linux, it copied over to the SATA drive, however, when i tried to boot from harddrive, it gave me a GRUB Error 22. Why does this happen ? Shouldnt the linux have created its own partition ?
I have an unbranded netbook (N270, 1GB RAM, 160GB HDD, no disk drive). This netbook had a strange, unusable Linux installation, which did not allow any possibility to modify anything on the machine. I could not even use F2 to get into the BIOS. F2 was the only key I could use to get a boot device option. I wanted to wipe off that Linux installation and install Windows 7 (reading some instruction from the net, using USB drive or SD card). I have done a similar installation on another netbook and it worked OK. On this machine though, I could only see "GRUB" when I tried to boot using USB or SD card. Later, I used UNetBootIn on SD card to load Ubuntu LiveCD.
This time it worked and I though of installing Ubuntu on this machine instead of Windows7. I chose to use the entire HDD, thereby, wiping the old original Linux installation. The installation went well and I wanted to start Ubuntu from the HDD. But it only ended up in a "C" with a blinking cursor. Laterwhen I tried to boot from the same UNetBootIn SD card, all I get is a "GRUB" with nothing else. The same happens when I try to boot from the USB drive with the Windows 7. I am left with no bootable OS on the netbook, no way to get into the BIOS, no possibility to boot from USB or SD card.
