Unlock your boot loader????
Hello, I would know when this mobile will unlocked boot loader because I need unlock it and root it. I need more free space
I have the version with 8GB and it is a scam mobile.
<2GB for the user with a lot of useless bloatware. The correct versions of this mobile would be 16GB/32GB. Please, know more in the final user and less in the money.Good mobile=more sales=more money.Bad mobile=less sales=less money=FAIL
You do not need to unlock your bootloader in order to root - If that is the reason for unlocking your bootloader
For a successful technology, reality must take precedence over public relations, for Nature cannot be fooled. Richard P. Feynman
Similar Messages
-
Problems unlocking the boot loader of xperia z3
Hello,
i'm trying to unlock the boot loader of my xperia z3, i'm following the instructions on sony's site but i'm stuck: i connect the phone to the pc in fastboot mode (blue light on), then i open the command prompt window in the platform-tools folder of android sdk, but when i type fastboot devices nothing happens. If i try to enter my unlock code i get "waiting for device" forever.
Any help?I recommend that you check that you have installed the fastboot driver. You can download it from here: http://developer.sonymobile.com/downloads/drivers/fastboot-driver/
And as uliwooly says, make sure that you have read the information on http://developer.sonymobile.com/unlockbootloader/ and that you are aware of the risks.
- Official Sony Xperia Support Staff
If you're new to our forums make sure that you have read our Discussion guidelines.
If you want to get in touch with the local support team for your country please visit our contact page. -
AT300 - unlock of boot loader to get root access
Unpacking my new AT300, I was surprised to fin a locked boot-loader.
I've been using computers for 30 years and have been able to customize my system and software the way I've wanted to all that time. I don't understand why manufacturers think we all of a sudden want to give up that type of control and functionality just because the size and shape of the computing device has changed.
For my opinion the blocked boot-loader is a reason to stay away from this device,Akuma, i didn't know that the Tegra 3 is software i thought it's a SoC. So how can hardware be code?
Anyway, check out Wikipedia which tablets contain the Tegra 3, there are a lot.
http://en.wikipedia.org/wiki/Tegra#Tegra_3
And i checked quickly randomly the Nexus 7 and the ASUS Transformer pad, all of them are supported by Cyanogenmod and therefore have an unlocked bootloader. So, either Toshiba signs a silly contract with nVidia or you are not right.
http://wiki.cyanogenmod.org/index.php?title=Devices#vendor=; -
[SOLVED] efibootmgr not generating boot loader (rEFInd, etc.) entry.
Hello,
The following command runs without problem or any output. It wouldn't create any entry. Also my refind.conf is not being followed. rEFInd is able to detect kernels and boot fine from /boot
efibootmgr -c -g -d /dev/sda -p 1 -w -L "rEFInd" -l '\EFI\refind\refind_x64.efi'
Information
efibootmgr 0.6.0-1
refind-efi 0.6.8-1
Linux 3.8.4-1-ARCH
sudo efibootmgr
BootCurrent: 000A
Timeout: 0 seconds
BootOrder: 0006,0007,0008,0009,000A,000B,000C,000D,000E,000F,0010,0011,0012,0013
Boot0000 Setup
Boot0001 Boot Menu
Boot0002 Diagnostic Splash Screen
Boot0003 Startup Interrupt Menu
Boot0004 ME Configuration Menu
Boot0005 Rescue and Recovery
Boot0006* USB CD
Boot0007* USB FDD
Boot0008* ATAPI CD0
Boot0009* ATA HDD2
Boot000A* ATA HDD0
Boot000B* ATA HDD1
Boot000C* USB HDD
Boot000D* PCI LAN
Boot000E* ATAPI CD1
Boot000F* ATAPI CD2
Boot0010 Other CD
Boot0011* ATA HDD3
Boot0012* ATA HDD4
Boot0013 Other HDD
Boot0014* IDER BOOT CDROM
Boot0015* IDER BOOT Floppy
Boot0016* ATA HDD
Boot0017* ATAPI CD:
Boot0018* PCI LAN
ls -R /boot
/boot:
EFI initramfs-linux-fallback.img initramfs-linux.img refind_linux.conf vmlinuz-linux
/boot/EFI:
boot refind tools
/boot/EFI/boot:
bootx64.efi icons refind.conf
/boot/EFI/boot/icons:
*** Icons
/boot/EFI/refind:
icons refind.conf refind_x64.efi
/boot/EFI/refind/icons:
*** icons
/boot/EFI/tools:
drivers shells
/boot/EFI/tools/drivers:
ext2_x64.efi ext4_x64.efi hfs_x64.efi iso9660_x64.efi reiserfs_x64.efi
/boot/EFI/tools/shells:
Shell.efi Shell_Full.efi
cat /boot/refind_linux.conf
"Boot to X" "root=PARTUUID=5416f920-35fc-42a8-8a34-564c8c332bfe ro rootfstype=ext4 add_efi_memmap systemd.unit=graphical.target"
"Boot to Console" "root=PARTUUID=5416f920-35fc-42a8-8a34-564c8c332bfe ro rootfstype=ext4 add_efi_memmap systemd.unit=multi-user.target"
# refind.conf
# Configuration file for the rEFInd boot menu
# Timeout in seconds for the main menu screen. Setting the timeout to 0
# disables automatic booting (i.e., no timeout).
timeout 5
# Hide user interface elements for personal preference or to increase
# security:
# banner - the rEFInd title banner (built-in or loaded via "banner")
# label - boot option text label in the menu
# singleuser - remove the submenu options to boot Mac OS X in single-user
# or verbose modes; affects ONLY MacOS X
# safemode - remove the submenu option to boot Mac OS X in "safe mode"
# hwtest - the submenu option to run Apple's hardware test
# arrows - scroll arrows on the OS selection tag line
# hints - brief command summary in the menu
# editor - the options editor (+, F2, or Insert on boot options menu)
# all - all of the above
# Default is none of these (all elements active)
#hideui singleuser
#hideui all
# Set the name of a subdirectory in which icons are stored. Icons must
# have the same names they have in the standard directory. The directory
# name is specified relative to the main rEFInd binary's directory. If
# an icon can't be found in the specified directory, an attempt is made
# to load it from the default directory; thus, you can replace just some
# icons in your own directory and rely on the default for others.
# Default is "icons".
#icons_dir myicons
# Use a custom title banner instead of the rEFInd icon and name. The file
# path is relative to the directory where refind.efi is located. The color
# in the top left corner of the image is used as the background color
# for the menu screens. Currently uncompressed BMP images with color
# depths of 24, 8, 4 or 1 bits are supported, as well as PNG images.
#banner hostname.bmp
#banner mybanner.png
# Custom images for the selection background. There is a big one (144 x 144)
# for the OS icons, and a small one (64 x 64) for the function icons in the
# second row. If only a small image is given, that one is also used for
# the big icons by stretching it in the middle. If only a big one is given,
# the built-in default will be used for the small icons.
# Like the banner option above, these options take a filename of an
# uncompressed BMP image file with a color depth of 24, 8, 4, or 1 bits,
# or a PNG image. The PNG format is required if you need transparency
# support (to let you "see through" to a full-screen banner).
#selection_big selection-big.bmp
#selection_small selection-small.bmp
# Set the font to be used for all textual displays in graphics mode.
# The font must be a PNG file with alpha channel transparency. It must
# contain ASCII characters 32-126 (space through tilde), inclusive, plus
# a glyph to be displayed in place of characters outside of this range,
# for a total of 96 glyphs. Only monospaced fonts are supported. Fonts
# may be of any size, although large fonts can produce display
# irregularities.
# The default is rEFInd's built-in font, Luxi Mono Regular 12 point.
#font myfont.png
# Use text mode only. When enabled, this option forces rEFInd into text mode.
# Passing this option a "0" value causes graphics mode to be used. Pasing
# it no value or any non-0 value causes text mode to be used.
# Default is to use graphics mode.
#textonly
textonly
# Set the EFI text mode to be used for textual displays. This option
# takes a single digit that refers to a mode number. Mode 0 is normally
# 80x25, 1 is sometimes 80x50, and higher numbers are system-specific
# modes. Mode 1024 is a special code that tells rEFInd to not set the
# text mode; it uses whatever was in use when the program was launched.
# If you specify an invalid mode, rEFInd pauses during boot to inform
# you of valid modes.
# CAUTION: On VirtualBox, and perhaps on some real computers, specifying
# a text mode and uncommenting the "textonly" option while NOT specifying
# a resolution can result in an unusable display in the booted OS.
# Default is 1024 (no change)
#textmode 2
textmode 1024
# Set the screen's video resolution. Pass this option either:
# * two values, corresponding to the X and Y resolutions
# * one value, corresponding to a GOP (UEFI) video mode
# Note that not all resolutions are supported. On UEFI systems, passing
# an incorrect value results in a message being shown on the screen to
# that effect, along with a list of supported modes. On EFI 1.x systems
# (e.g., Macintoshes), setting an incorrect mode silently fails. On both
# types of systems, setting an incorrect resolution results in the default
# resolution being used. A resolution of 1024x768 usually works, but higher
# values often don't.
# Default is "0 0" (use the system default resolution, usually 800x600).
#resolution 1024 768
#resolution 3
resolution 1024 768
# Launch specified OSes in graphics mode. By default, rEFInd switches
# to text mode and displays basic pre-launch information when launching
# all OSes except OS X. Using graphics mode can produce a more seamless
# transition, but displays no information, which can make matters
# difficult if you must debug a problem. Also, on at least one known
# computer, using graphics mode prevents a crash when using the Linux
# kernel's EFI stub loader. You can specify an empty list to boot all
# OSes in text mode.
# Valid options:
# osx - Mac OS X
# linux - A Linux kernel with EFI stub loader
# elilo - The ELILO boot loader
# grub - The GRUB (Legacy or 2) boot loader
# windows - Microsoft Windows
# Default value: osx
#use_graphics_for osx,linux
# Which non-bootloader tools to show on the tools line, and in what
# order to display them:
# shell - the EFI shell (requires external program; see rEFInd
# documentation for details)
# gptsync - the (dangerous) gptsync.efi utility (requires external
# program; see rEFInd documentation for details)
# apple_recovery - boots the Apple Recovery HD partition, if present
# mok_tool - makes available the Machine Owner Key (MOK) maintenance
# tool, MokManager.efi, used on Secure Boot systems
# about - an "about this program" option
# exit - a tag to exit from rEFInd
# shutdown - shuts down the computer (a bug causes this to reboot
# EFI systems)
# reboot - a tag to reboot the computer
# Default is shell,apple_recovery,mok_tool,about,shutdown,reboot
#showtools shell, mok_tool, about, reboot, exit
showtools shell, mok_tool, about, reboot, exit
# Directories in which to search for EFI drivers. These drivers can
# provide filesystem support, give access to hard disks on plug-in
# controllers, etc. In most cases none are needed, but if you add
# EFI drivers and you want rEFInd to automatically load them, you
# should specify one or more paths here. rEFInd always scans the
# "drivers" and "drivers_{arch}" subdirectories of its own installation
# directory (where "{arch}" is your architecture code); this option
# specifies ADDITIONAL directories to scan.
# Default is to scan no additional directories for EFI drivers
#scan_driver_dirs EFI/tools/drivers,drivers
scan_driver_dirs /boot/EFI/tools/drivers,drivers
# Which types of boot loaders to search, and in what order to display them:
# internal - internal EFI disk-based boot loaders
# external - external EFI disk-based boot loaders
# optical - EFI optical discs (CD, DVD, etc.)
# hdbios - BIOS disk-based boot loaders
# biosexternal - BIOS external boot loaders (USB, eSATA, etc.)
# cd - BIOS optical-disc boot loaders
# manual - use stanzas later in this configuration file
# Note that the legacy BIOS options require firmware support, which is
# not present on all computers.
# On UEFI PCs, default is internal,external,optical,manual
# On Macs, default is internal,hdbios,external,biosexternal,optical,cd,manual
#scanfor internal,external,optical,manual
scanfor internal,external,optical,manual
# Delay for the specified number of seconds before scanning disks.
# This can help some users who find that some of their disks
# (usually external or optical discs) aren't detected initially,
# but are detected after pressing Esc.
# The default is 0.
#scan_delay 5
# When scanning volumes for EFI boot loaders, rEFInd always looks for
# Mac OS X's and Microsoft Windows' boot loaders in their normal locations,
# and scans the root directory and every subdirectory of the /EFI directory
# for additional boot loaders, but it doesn't recurse into these directories.
# The also_scan_dirs token adds more directories to the scan list.
# Directories are specified relative to the volume's root directory. This
# option applies to ALL the volumes that rEFInd scans UNLESS you include
# a volume name and colon before the directory name, as in "myvol:/somedir"
# to scan the somedir directory only on the filesystem named myvol. If a
# specified directory doesn't exist, it's ignored (no error condition
# results). The default is to scan the "boot" directory in addition to
# various hard-coded directories.
#also_scan_dirs boot,ESP2:EFI/linux/kernels
# Partitions to omit from scans. You must specify a volume by its
# label, which you can obtain in an EFI shell by typing "vol", from
# Linux by typing "blkid /dev/{devicename}", or by examining the
# disk's label in various OSes' file browsers.
# The default is "Recovery HD".
#dont_scan_volumes "Recovery HD"
# Directories that should NOT be scanned for boot loaders. By default,
# rEFInd doesn't scan its own directory or the EFI/tools directory.
# You can "blacklist" additional directories with this option, which
# takes a list of directory names as options. You might do this to
# keep EFI/boot/bootx64.efi out of the menu if that's a duplicate of
# another boot loader or to exclude a directory that holds drivers
# or non-bootloader utilities provided by a hardware manufacturer. If
# a directory is listed both here and in also_scan_dirs, dont_scan_dirs
# takes precedence. Note that this blacklist applies to ALL the
# filesystems that rEFInd scans, not just the ESP, unless you precede
# the directory name by a filesystem name, as in "myvol:EFI/somedir"
# to exclude EFI/somedir from the scan on the myvol volume but not on
# other volumes.
#dont_scan_dirs ESP:/EFI/boot,EFI/Dell
# Files that should NOT be included as EFI boot loaders (on the
# first line of the display). If you're using a boot loader that
# relies on support programs or drivers that are installed alongside
# the main binary or if you want to "blacklist" certain loaders by
# name rather than location, use this option. Note that this will
# NOT prevent certain binaries from showing up in the second-row
# set of tools. Most notably, MokManager.efi is in this blacklist,
# but will show up as a tool if present in certain directories. You
# can control the tools row with the showtools token.
# The default is shim.efi,TextMode.efi,ebounce.efi,GraphicsConsole.efi,MokManager.efi,HashTool.efi,HashTool-signed.efi
#dont_scan_files shim.efi,MokManager.efi
# Scan for Linux kernels that lack a ".efi" filename extension. This is
# useful for better integration with Linux distributions that provide
# kernels with EFI stub loaders but that don't give those kernels filenames
# that end in ".efi", particularly if the kernels are stored on a
# filesystem that the EFI can read. When uncommented, this option causes
# all files in scanned directories with names that begin with "vmlinuz"
# or "bzImage" to be included as loaders, even if they lack ".efi"
# extensions. The drawback to this option is that it can pick up kernels
# that lack EFI stub loader support and other files. Passing this option
# a "0" value causes kernels without ".efi" extensions to NOT be scanned;
# passing it alone or with any other value causes all kernels to be scanned.
# Default is to NOT scan for kernels without ".efi" extensions.
scan_all_linux_kernels
# Set the maximum number of tags that can be displayed on the screen at
# any time. If more loaders are discovered than this value, rEFInd shows
# a subset in a scrolling list. If this value is set too high for the
# screen to handle, it's reduced to the value that the screen can manage.
# If this value is set to 0 (the default), it's adjusted to the number
# that the screen can handle.
#max_tags 0
# Set the default menu selection. The available arguments match the
# keyboard accelerators available within rEFInd. You may select the
# default loader using:
# - A digit between 1 and 9, in which case the Nth loader in the menu
# will be the default.
# - Any substring that corresponds to a portion of the loader's title
# (usually the OS's name or boot loader's path).
#default_selection 1
default_selection "vmlinuz-linux"
# Include a secondary configuration file within this one. This secondary
# file is loaded as if its options appeared at the point of the "include"
# token itself, so if you want to override a setting in the main file,
# the secondary file must be referenced AFTER the setting you want to
# override. Note that the secondary file may NOT load a tertiary file.
#include manual.conf
# Sample manual configuration stanzas. Each begins with the "menuentry"
# keyword followed by a name that's to appear in the menu (use quotes
# if you want the name to contain a space) and an open curly brace
# ("{"). Each entry ends with a close curly brace ("}"). Common
# keywords within each stanza include:
# volume - identifies the filesystem from which subsequent files
# are loaded. You can specify the volume by label or by
# a number followed by a colon (as in "0:" for the first
# filesystem or "1:" for the second).
# loader - identifies the boot loader file
# initrd - Specifies an initial RAM disk file
# icon - specifies a custom boot loader icon
# ostype - OS type code to determine boot options available by
# pressing Insert. Valid values are "MacOS", "Linux",
# "Windows", and "XOM". Case-sensitive.
# graphics - set to "on" to enable graphics-mode boot (useful
# mainly for MacOS) or "off" for text-mode boot.
# Default is auto-detected from loader filename.
# options - sets options to be passed to the boot loader; use
# quotes if more than one option should be passed or
# if any options use characters that might be changed
# by rEFInd parsing procedures (=, /, #, or tab).
# disabled - use alone or set to "yes" to disable this entry.
# Note that you can use either DOS/Windows/EFI-style backslashes (\)
# or Unix-style forward slashes (/) as directory separators. Either
# way, all file references are on the ESP from which rEFInd was
# launched.
# Use of quotes around parameters causes them to be interpreted as
# one keyword, and for parsing of special characters (spaces, =, /,
# and #) to be disabled. This is useful mainly with the "options"
# keyword. Use of quotes around parameters that specify filenames is
# permissible, but you must then use backslashes instead of slashes,
# except when you must pass a forward slash to the loader, as when
# passing a root= option to a Linux kernel.
# Below are several sample boot stanzas. All are disabled by default.
# Find one similar to what you need, copy it, remove the "disabled" line,
# and adjust the entries to suit your needs.
# A sample entry for a Linux 3.3 kernel with its new EFI boot stub
# support on a filesystem called "KERNELS". This entry includes
# Linux-specific boot options and specification of an initial RAM disk.
# Note uses of Linux-style forward slashes, even in the initrd
# specification. Also note that a leading slash is optional in file
# specifications.
menuentry Linux {
icon EFI/refind/icons/os_linux.icns
volume KERNELS
loader bzImage-3.3.0-rc7
initrd initrd-3.3.0.img
options "ro root=UUID=5f96cafa-e0a7-4057-b18f-fa709db5b837"
disabled
# A sample entry for loading Ubuntu using its standard name for
# its GRUB 2 boot loader. Note uses of Linux-style forward slashes
menuentry Ubuntu {
loader /EFI/ubuntu/grubx64.efi
icon /EFI/refined/icons/os_linux.icns
disabled
# A minimal ELILO entry, which probably offers nothing that
# auto-detection can't accomplish.
menuentry "ELILO" {
loader \EFI\elilo\elilo.efi
disabled
# Like the ELILO entry, this one offers nothing that auto-detection
# can't do; but you might use it if you want to disable auto-detection
# but still boot Windows....
menuentry "Windows 7" {
loader \EFI\Microsoft\Boot\bootmgfw.efi
disabled
# EFI shells are programs just like boot loaders, and can be
# launched in the same way. You can pass a shell the name of a
# script that it's to run on the "options" line. The script
# could initialize hardware and then launch an OS, or it could
# do something entirely different.
menuentry "Windows via shell script" {
icon \EFI\refind\icons\os_win.icns
loader \EFI\tools\shell.efi
options "fs0:\EFI\tools\launch_windows.nsh"
disabled
# Mac OS is normally detected and run automatically; however,
# if you want to do something unusual, a manual boot stanza may
# be the way to do it. This one does nothing very unusual, but
# it may serve as a starting point. Note that you'll almost
# certainly need to change the "volume" line for this example
# to work.
menuentry "My Mac OS X" {
icon \EFI\refind\icons\os_mac.icns
volume "OS X boot"
loader \System\Library\CoreServices\boot.efi
disabled
cat /etc/fstab
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda2
UUID=7b92a840-4747-43b7-b2cf-02cbf92afce7 / ext4 rw,relatime,data=ordered 0 1
# /dev/sda4
UUID=72f64fd4-a3f1-424c-8fe3-cdf7751a84e0 /home ext4 rw,relatime,data=ordered 0 2
# /dev/sda1
# UUID=5447-7409 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
UUID=5447-7409 /boot vfat noatime 0 2
# /dev/sda3
UUID=1e11bea5-41db-4969-a8fa-a461734b71ac none swap defaults 0 0
This is a clean install using April 01 ISO with minimal or no modifications. I have tried to follow wiki as precisely as possible. I am not sure what I am missing. Thanks.
EDIT1: Updated and cleaned the post to better reflect current structure and added /etc/fstab.
EDIT2: @swordfish Removed /boot/EFI/arch.
Last edited by donniezazen (2013-04-04 06:37:07)I used March ISO instead of April ISO and it worked flawlessly. There is some problem with April ISO where efibootmgr and UEFI Shell1/2 fail with ASSERT_EFI_ERROR (status = device error).
I have removed both /boot/EFI/boot and /boot/EFI/arch. I now have two entries one on vmlinuz-linux on 1024 Fat 32 partition which works and second one boot/vmlinuz-linux on 20G / partition which fails and takes me to rootfs. Also refind isn't showing UEFI shells that I have in /boot/EFI/tools/Shells.
ls -R /boot
/boot:
EFI initramfs-linux-fallback.img initramfs-linux.img refind_linux.conf vmlinuz-linux
/boot/EFI:
drivers refind tools
/boot/EFI/drivers:
ext2_x64.efi ext4_x64.efi hfs_x64.efi iso9660_x64.efi reiserfs_x64.efi
/boot/EFI/refind:
icons refind.conf refind_x64.efi
/boot/EFI/refind/icons:
### Icons
/boot/EFI/tools:
Shell.efi
# refind.conf
# Configuration file for the rEFInd boot menu
# Timeout in seconds for the main menu screen. Setting the timeout to 0
# disables automatic booting (i.e., no timeout).
timeout 5
# Hide user interface elements for personal preference or to increase
# security:
# banner - the rEFInd title banner (built-in or loaded via "banner")
# label - boot option text label in the menu
# singleuser - remove the submenu options to boot Mac OS X in single-user
# or verbose modes; affects ONLY MacOS X
# safemode - remove the submenu option to boot Mac OS X in "safe mode"
# hwtest - the submenu option to run Apple's hardware test
# arrows - scroll arrows on the OS selection tag line
# hints - brief command summary in the menu
# editor - the options editor (+, F2, or Insert on boot options menu)
# all - all of the above
# Default is none of these (all elements active)
#hideui singleuser
#hideui all
# Set the name of a subdirectory in which icons are stored. Icons must
# have the same names they have in the standard directory. The directory
# name is specified relative to the main rEFInd binary's directory. If
# an icon can't be found in the specified directory, an attempt is made
# to load it from the default directory; thus, you can replace just some
# icons in your own directory and rely on the default for others.
# Default is "icons".
#icons_dir myicons
# Use a custom title banner instead of the rEFInd icon and name. The file
# path is relative to the directory where refind.efi is located. The color
# in the top left corner of the image is used as the background color
# for the menu screens. Currently uncompressed BMP images with color
# depths of 24, 8, 4 or 1 bits are supported, as well as PNG images.
#banner hostname.bmp
#banner mybanner.png
# Custom images for the selection background. There is a big one (144 x 144)
# for the OS icons, and a small one (64 x 64) for the function icons in the
# second row. If only a small image is given, that one is also used for
# the big icons by stretching it in the middle. If only a big one is given,
# the built-in default will be used for the small icons.
# Like the banner option above, these options take a filename of an
# uncompressed BMP image file with a color depth of 24, 8, 4, or 1 bits,
# or a PNG image. The PNG format is required if you need transparency
# support (to let you "see through" to a full-screen banner).
#selection_big selection-big.bmp
#selection_small selection-small.bmp
# Set the font to be used for all textual displays in graphics mode.
# The font must be a PNG file with alpha channel transparency. It must
# contain ASCII characters 32-126 (space through tilde), inclusive, plus
# a glyph to be displayed in place of characters outside of this range,
# for a total of 96 glyphs. Only monospaced fonts are supported. Fonts
# may be of any size, although large fonts can produce display
# irregularities.
# The default is rEFInd's built-in font, Luxi Mono Regular 12 point.
#font myfont.png
# Use text mode only. When enabled, this option forces rEFInd into text mode.
# Passing this option a "0" value causes graphics mode to be used. Pasing
# it no value or any non-0 value causes text mode to be used.
# Default is to use graphics mode.
#textonly
textonly
# Set the EFI text mode to be used for textual displays. This option
# takes a single digit that refers to a mode number. Mode 0 is normally
# 80x25, 1 is sometimes 80x50, and higher numbers are system-specific
# modes. Mode 1024 is a special code that tells rEFInd to not set the
# text mode; it uses whatever was in use when the program was launched.
# If you specify an invalid mode, rEFInd pauses during boot to inform
# you of valid modes.
# CAUTION: On VirtualBox, and perhaps on some real computers, specifying
# a text mode and uncommenting the "textonly" option while NOT specifying
# a resolution can result in an unusable display in the booted OS.
# Default is 1024 (no change)
#textmode 2
textmode 1024
# Set the screen's video resolution. Pass this option either:
# * two values, corresponding to the X and Y resolutions
# * one value, corresponding to a GOP (UEFI) video mode
# Note that not all resolutions are supported. On UEFI systems, passing
# an incorrect value results in a message being shown on the screen to
# that effect, along with a list of supported modes. On EFI 1.x systems
# (e.g., Macintoshes), setting an incorrect mode silently fails. On both
# types of systems, setting an incorrect resolution results in the default
# resolution being used. A resolution of 1024x768 usually works, but higher
# values often don't.
# Default is "0 0" (use the system default resolution, usually 800x600).
#resolution 1024 768
#resolution 3
resolution 1024 768
# Launch specified OSes in graphics mode. By default, rEFInd switches
# to text mode and displays basic pre-launch information when launching
# all OSes except OS X. Using graphics mode can produce a more seamless
# transition, but displays no information, which can make matters
# difficult if you must debug a problem. Also, on at least one known
# computer, using graphics mode prevents a crash when using the Linux
# kernel's EFI stub loader. You can specify an empty list to boot all
# OSes in text mode.
# Valid options:
# osx - Mac OS X
# linux - A Linux kernel with EFI stub loader
# elilo - The ELILO boot loader
# grub - The GRUB (Legacy or 2) boot loader
# windows - Microsoft Windows
# Default value: osx
#use_graphics_for osx,linux
# Which non-bootloader tools to show on the tools line, and in what
# order to display them:
# shell - the EFI shell (requires external program; see rEFInd
# documentation for details)
# gptsync - the (dangerous) gptsync.efi utility (requires external
# program; see rEFInd documentation for details)
# apple_recovery - boots the Apple Recovery HD partition, if present
# mok_tool - makes available the Machine Owner Key (MOK) maintenance
# tool, MokManager.efi, used on Secure Boot systems
# about - an "about this program" option
# exit - a tag to exit from rEFInd
# shutdown - shuts down the computer (a bug causes this to reboot
# EFI systems)
# reboot - a tag to reboot the computer
# Default is shell,apple_recovery,mok_tool,about,shutdown,reboot
#showtools shell, mok_tool, about, reboot, exit
showtools shell, about, reboot, exit
# Directories in which to search for EFI drivers. These drivers can
# provide filesystem support, give access to hard disks on plug-in
# controllers, etc. In most cases none are needed, but if you add
# EFI drivers and you want rEFInd to automatically load them, you
# should specify one or more paths here. rEFInd always scans the
# "drivers" and "drivers_{arch}" subdirectories of its own installation
# directory (where "{arch}" is your architecture code); this option
# specifies ADDITIONAL directories to scan.
# Default is to scan no additional directories for EFI drivers
#scan_driver_dirs EFI/tools/drivers,drivers
scan_driver_dirs EFI/tools/drivers,drivers
# Which types of boot loaders to search, and in what order to display them:
# internal - internal EFI disk-based boot loaders
# external - external EFI disk-based boot loaders
# optical - EFI optical discs (CD, DVD, etc.)
# hdbios - BIOS disk-based boot loaders
# biosexternal - BIOS external boot loaders (USB, eSATA, etc.)
# cd - BIOS optical-disc boot loaders
# manual - use stanzas later in this configuration file
# Note that the legacy BIOS options require firmware support, which is
# not present on all computers.
# On UEFI PCs, default is internal,external,optical,manual
# On Macs, default is internal,hdbios,external,biosexternal,optical,cd,manual
#scanfor internal,external,optical,manual
scanfor internal,external,optical,manual
# Delay for the specified number of seconds before scanning disks.
# This can help some users who find that some of their disks
# (usually external or optical discs) aren't detected initially,
# but are detected after pressing Esc.
# The default is 0.
#scan_delay 5
# When scanning volumes for EFI boot loaders, rEFInd always looks for
# Mac OS X's and Microsoft Windows' boot loaders in their normal locations,
# and scans the root directory and every subdirectory of the /EFI directory
# for additional boot loaders, but it doesn't recurse into these directories.
# The also_scan_dirs token adds more directories to the scan list.
# Directories are specified relative to the volume's root directory. This
# option applies to ALL the volumes that rEFInd scans UNLESS you include
# a volume name and colon before the directory name, as in "myvol:/somedir"
# to scan the somedir directory only on the filesystem named myvol. If a
# specified directory doesn't exist, it's ignored (no error condition
# results). The default is to scan the "boot" directory in addition to
# various hard-coded directories.
#also_scan_dirs boot,ESP2:EFI/linux/kernels
# Partitions to omit from scans. You must specify a volume by its
# label, which you can obtain in an EFI shell by typing "vol", from
# Linux by typing "blkid /dev/{devicename}", or by examining the
# disk's label in various OSes' file browsers.
# The default is "Recovery HD".
#dont_scan_volumes "Recovery HD"
# Directories that should NOT be scanned for boot loaders. By default,
# rEFInd doesn't scan its own directory or the EFI/tools directory.
# You can "blacklist" additional directories with this option, which
# takes a list of directory names as options. You might do this to
# keep EFI/boot/bootx64.efi out of the menu if that's a duplicate of
# another boot loader or to exclude a directory that holds drivers
# or non-bootloader utilities provided by a hardware manufacturer. If
# a directory is listed both here and in also_scan_dirs, dont_scan_dirs
# takes precedence. Note that this blacklist applies to ALL the
# filesystems that rEFInd scans, not just the ESP, unless you precede
# the directory name by a filesystem name, as in "myvol:EFI/somedir"
# to exclude EFI/somedir from the scan on the myvol volume but not on
# other volumes.
#dont_scan_dirs ESP:/EFI/boot,EFI/Dell
# Files that should NOT be included as EFI boot loaders (on the
# first line of the display). If you're using a boot loader that
# relies on support programs or drivers that are installed alongside
# the main binary or if you want to "blacklist" certain loaders by
# name rather than location, use this option. Note that this will
# NOT prevent certain binaries from showing up in the second-row
# set of tools. Most notably, MokManager.efi is in this blacklist,
# but will show up as a tool if present in certain directories. You
# can control the tools row with the showtools token.
# The default is shim.efi,TextMode.efi,ebounce.efi,GraphicsConsole.efi,MokManager.efi,HashTool.efi,HashTool-signed.efi
#dont_scan_files shim.efi,MokManager.efi
# Scan for Linux kernels that lack a ".efi" filename extension. This is
# useful for better integration with Linux distributions that provide
# kernels with EFI stub loaders but that don't give those kernels filenames
# that end in ".efi", particularly if the kernels are stored on a
# filesystem that the EFI can read. When uncommented, this option causes
# all files in scanned directories with names that begin with "vmlinuz"
# or "bzImage" to be included as loaders, even if they lack ".efi"
# extensions. The drawback to this option is that it can pick up kernels
# that lack EFI stub loader support and other files. Passing this option
# a "0" value causes kernels without ".efi" extensions to NOT be scanned;
# passing it alone or with any other value causes all kernels to be scanned.
# Default is to NOT scan for kernels without ".efi" extensions.
scan_all_linux_kernels
# Set the maximum number of tags that can be displayed on the screen at
# any time. If more loaders are discovered than this value, rEFInd shows
# a subset in a scrolling list. If this value is set too high for the
# screen to handle, it's reduced to the value that the screen can manage.
# If this value is set to 0 (the default), it's adjusted to the number
# that the screen can handle.
#max_tags 0
# Set the default menu selection. The available arguments match the
# keyboard accelerators available within rEFInd. You may select the
# default loader using:
# - A digit between 1 and 9, in which case the Nth loader in the menu
# will be the default.
# - Any substring that corresponds to a portion of the loader's title
# (usually the OS's name or boot loader's path).
#default_selection 1
# Include a secondary configuration file within this one. This secondary
# file is loaded as if its options appeared at the point of the "include"
# token itself, so if you want to override a setting in the main file,
# the secondary file must be referenced AFTER the setting you want to
# override. Note that the secondary file may NOT load a tertiary file.
#include manual.conf
# Sample manual configuration stanzas. Each begins with the "menuentry"
# keyword followed by a name that's to appear in the menu (use quotes
# if you want the name to contain a space) and an open curly brace
# ("{"). Each entry ends with a close curly brace ("}"). Common
# keywords within each stanza include:
# volume - identifies the filesystem from which subsequent files
# are loaded. You can specify the volume by label or by
# a number followed by a colon (as in "0:" for the first
# filesystem or "1:" for the second).
# loader - identifies the boot loader file
# initrd - Specifies an initial RAM disk file
# icon - specifies a custom boot loader icon
# ostype - OS type code to determine boot options available by
# pressing Insert. Valid values are "MacOS", "Linux",
# "Windows", and "XOM". Case-sensitive.
# graphics - set to "on" to enable graphics-mode boot (useful
# mainly for MacOS) or "off" for text-mode boot.
# Default is auto-detected from loader filename.
# options - sets options to be passed to the boot loader; use
# quotes if more than one option should be passed or
# if any options use characters that might be changed
# by rEFInd parsing procedures (=, /, #, or tab).
# disabled - use alone or set to "yes" to disable this entry.
# Note that you can use either DOS/Windows/EFI-style backslashes (\)
# or Unix-style forward slashes (/) as directory separators. Either
# way, all file references are on the ESP from which rEFInd was
# launched.
# Use of quotes around parameters causes them to be interpreted as
# one keyword, and for parsing of special characters (spaces, =, /,
# and #) to be disabled. This is useful mainly with the "options"
# keyword. Use of quotes around parameters that specify filenames is
# permissible, but you must then use backslashes instead of slashes,
# except when you must pass a forward slash to the loader, as when
# passing a root= option to a Linux kernel.
# Below are several sample boot stanzas. All are disabled by default.
# Find one similar to what you need, copy it, remove the "disabled" line,
# and adjust the entries to suit your needs.
# A sample entry for a Linux 3.3 kernel with its new EFI boot stub
# support on a filesystem called "KERNELS". This entry includes
# Linux-specific boot options and specification of an initial RAM disk.
# Note uses of Linux-style forward slashes, even in the initrd
# specification. Also note that a leading slash is optional in file
# specifications.
menuentry Linux {
icon EFI/refind/icons/os_linux.icns
volume KERNELS
loader bzImage-3.3.0-rc7
initrd initrd-3.3.0.img
options "ro root=UUID=5f96cafa-e0a7-4057-b18f-fa709db5b837"
disabled
# A sample entry for loading Ubuntu using its standard name for
# its GRUB 2 boot loader. Note uses of Linux-style forward slashes
menuentry Ubuntu {
loader /EFI/ubuntu/grubx64.efi
icon /EFI/refined/icons/os_linux.icns
disabled
# A minimal ELILO entry, which probably offers nothing that
# auto-detection can't accomplish.
menuentry "ELILO" {
loader \EFI\elilo\elilo.efi
disabled
# Like the ELILO entry, this one offers nothing that auto-detection
# can't do; but you might use it if you want to disable auto-detection
# but still boot Windows....
menuentry "Windows 7" {
loader \EFI\Microsoft\Boot\bootmgfw.efi
disabled
# EFI shells are programs just like boot loaders, and can be
# launched in the same way. You can pass a shell the name of a
# script that it's to run on the "options" line. The script
# could initialize hardware and then launch an OS, or it could
# do something entirely different.
menuentry "Windows via shell script" {
icon \EFI\refind\icons\os_win.icns
loader \EFI\tools\shell.efi
options "fs0:\EFI\tools\launch_windows.nsh"
disabled
# Mac OS is normally detected and run automatically; however,
# if you want to do something unusual, a manual boot stanza may
# be the way to do it. This one does nothing very unusual, but
# it may serve as a starting point. Note that you'll almost
# certainly need to change the "volume" line for this example
# to work.
menuentry "My Mac OS X" {
icon \EFI\refind\icons\os_mac.icns
volume "OS X boot"
loader \System\Library\CoreServices\boot.efi
disabled
Thanks for suggesting to try older ISO.
UPDATE:- Most recent ls -R /boot and my refind.conf. Reading over Rod Smith's rEFInd documentation has helped me clean up a little more and set up a good boot manager with automatic kernel detection and shell. I do want to get rid of drivers list that shows itself up along with kernel. Next is to tackle menu entry. Thanks.
Last edited by donniezazen (2013-04-04 06:43:16) -
Arch & Windows 8 Dual Boot -- Windows Boot Loader loads grub-rescue
Arch works fine,but as it always happens Windows boot went down. Both OS are EFI.
Note that boot secure and fast boot were disabled for Windows 8.
I used os-prober, but did not fix anything; so, I removed it. I tried to hack things out using boot-repair from Ubuntu, but it requires a repository, grub-efi, from Ubuntu that Arch doesn't have.
I am trying to modify files in grub.d and grub.cfg and hopefully fix something.
Exact description:
- archgrub loads and shows 3 entries. Two for Arch that load the sys succesfully and one for Windows 8 that fails.
- When I try to execute Windows from grub, it brings me to a grub rescue>
and shows error /boot/grub/x86_64-efi/normal.mod not found
As far as I am concerned this .mod is from Linux, so I don't know why it is being called into Windows loading procedures.
lsblk returns:
[jav@localhost ~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 931.5G 0 disk
|-sda1 8:1 0 1000M 0 part
|-sda2 8:2 0 260M 0 part
|-sda3 8:3 0 1000M 0 part
|-sda4 8:4 0 128M 0 part
|-sda5 8:5 0 605.3G 0 part
|-sda6 8:6 0 5.4G 0 part /boot/efi
|-sda7 8:7 0 25G 0 part
|-sda8 8:8 0 20G 0 part
|-sda9 8:9 0 244.1G 0 part /
`-sda10 8:10 0 29.3G 0 part
sr0 11:0 1 1024M 0 rom
Here's the output of fdisk. Another weird thing is that sometimes ubuntu would show on my terminal. See the first line below, "jav@ubuntu"?!
[jav@ubuntu ~]$ sudo fdisk -l
[sudo] password for jav:
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: [i deleted this]
Device Start End Size Type
/dev/sda1 2048 2050047 1000M Windows recovery environment
/dev/sda2 2050048 2582527 260M EFI System
/dev/sda3 2582528 4630527 1000M unknown
/dev/sda4 4630528 4892671 128M Microsoft reserved
/dev/sda5 4892672 1274335231 605.3G Microsoft basic data
/dev/sda6 1847777280 1859151871 5.4G EFI System
/dev/sda7 1859151872 1911580671 25G Microsoft basic data
/dev/sda8 1911580672 1953523711 20G Windows recovery environment
/dev/sda9 1335775232 1847777279 244.1G Linux filesystem
/dev/sda10 1274335232 1335775231 29.3G Microsoft basic data
And, bootinfoscript output:
Boot Info Script 0.61 [1 April 2012]
============================= Boot Info Summary: ===============================
=> No boot loader is installed in the MBR of /dev/sda.
sda1: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
sda2: __________________________________________________________________________
File system: vfat
Boot sector type: Windows 7: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /efi/Boot/bkpbootx64.efi /efi/Boot/bootx64.efi
/efi/ubuntu/grubx64.efi
sda3: __________________________________________________________________________
File system: vfat
Boot sector type: Windows 7: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /efi/Boot/bkpbootx64.efi /efi/Boot/bootx64.efi
/efi/ubuntu/grubx64.efi /bootmgr /boot/bcd
sda4: __________________________________________________________________________
File system:
Boot sector type: -
Boot sector info:
Mounting failed: mount: unknown filesystem type ''
sda5: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /bootmgr /Boot/BCD /Windows/System32/winload.exe
sda6: __________________________________________________________________________
File system: vfat
Boot sector type: SYSLINUX 6.02 ... :..(:,:0:4:8:....D:H:L:[.T:[.\:`:d:[.l:p:t:x:|:.:.:.:.:.:.:.:.....................
Boot sector info: Syslinux looks at sector 99102 of /dev/sda6 for its
second stage. SYSLINUX is installed in the /syslinux
directory. No errors found in the Boot Parameter Block.
Operating System:
Boot files: /grub/grub.cfg /syslinux/syslinux.cfg
/syslinux/ldlinux.sys
sda7: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
sda8: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
sda9: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Arch Linux ()
Boot files: /etc/fstab
sda10: _________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System:
Boot files:
============================ Drive/Partition Info: =============================
Drive: sda _____________________________________________________________________
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Partition Boot Start Sector End Sector # of Sectors Id System
/dev/sda1 1 1,953,525,167 1,953,525,167 ee GPT
GUID Partition Table detected.
Partition Start Sector End Sector # of Sectors System
/dev/sda1 2,048 2,050,047 2,048,000 Windows Recovery Environment (Windows)
/dev/sda2 2,050,048 2,582,527 532,480 EFI System partition
/dev/sda3 2,582,528 4,630,527 2,048,000 -
/dev/sda4 4,630,528 4,892,671 262,144 Microsoft Reserved Partition (Windows)
/dev/sda5 4,892,672 1,274,335,231 1,269,442,560 Data partition (Windows/Linux)
/dev/sda6 1,847,777,280 1,859,151,871 11,374,592 EFI System partition
/dev/sda7 1,859,151,872 1,911,580,671 52,428,800 Data partition (Windows/Linux)
/dev/sda8 1,911,580,672 1,953,523,711 41,943,040 Windows Recovery Environment (Windows)
/dev/sda9 1,335,775,232 1,847,777,279 512,002,048 Data partition (Linux)
/dev/sda10 1,274,335,232 1,335,775,231 61,440,000 Data partition (Windows/Linux)
"blkid" output: ________________________________________________________________
Device UUID TYPE LABEL
/dev/sda1 CE62D9F062D9DCF1 ntfs WINRE_DRV
/dev/sda10 150a8788-6049-45ed-85af-ded92a2c0801 ext4
/dev/sda2 16DC-8816 vfat SYSTEM_DRV
/dev/sda3 7CDD-0403 vfat LRS_ESP
/dev/sda4
/dev/sda5 40E4E0CFE4E0C7EC ntfs Windows8_OS
/dev/sda6 9C3F-2A9E vfat
/dev/sda7 7240E43740E40427 ntfs LENOVO
/dev/sda8 422CE5EA2CE5D945 ntfs PBR_DRV
/dev/sda9 1a765403-f251-43d8-8edf-c191475d3837 ext4
================================ Mount points: =================================
Device Mount_Point Type Options
/dev/sda6 /boot vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/sda6 /boot/efi vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/sda9 / ext4 (rw,relatime,data=ordered)
============================= sda6/grub/grub.cfg: ==============================
# DO NOT EDIT THIS FILE
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_gpt
insmod ext2
set root='hd0,gpt9'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt9 --hint-efi=hd0,gpt9 --hint-baremetal=ahci0,gpt9 1a765403-f251-43d8-8edf-c191475d3837
else
search --no-floppy --fs-uuid --set=root 1a765403-f251-43d8-8edf-c191475d3837
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
fi
terminal_input console
terminal_output gfxterm
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-1a765403-f251-43d8-8edf-c191475d3837' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod fat
set root='hd0,gpt6'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt6 --hint-efi=hd0,gpt6 --hint-baremetal=ahci0,gpt6 9C3F-2A9E
else
search --no-floppy --fs-uuid --set=root 9C3F-2A9E
fi
echo 'Loading Linux core repo kernel ...'
linux /vmlinuz-linux root=UUID=1a765403-f251-43d8-8edf-c191475d3837 rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux.img
menuentry 'Arch Linux, with Linux core repo kernel (Fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-fallback-1a765403-f251-43d8-8edf-c191475d3837' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod fat
set root='hd0,gpt6'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt6 --hint-efi=hd0,gpt6 --hint-baremetal=ahci0,gpt6 9C3F-2A9E
else
search --no-floppy --fs-uuid --set=root 9C3F-2A9E
fi
echo 'Loading Linux core repo kernel ...'
linux /vmlinuz-linux root=UUID=1a765403-f251-43d8-8edf-c191475d3837 rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux-fallback.img
### END /etc/grub.d/10_linux ###
## Attempt at fixing grub
# insmod fat
# set root='hd0,gpt6'
### BEGIN /etc/grub.d/30_os-prober ###
#menuentry 'Windows Boot Manager (on /dev/sda2)' --class windows --class os $menuentry_id_option 'osprober-efi-16DC-8816' {
# insmod part_gpt
# insmod fat
# set root='hd0,gpt2'
# if [ x$feature_platform_search_hint = xy ]; then
# search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 16DC-8816
# else
# search --no-floppy --fs-uuid --set=root 16DC-8816
# fi
# chainloader /EFI/Microsoft/Boot/bootmgfw.efi
menuentry "Windows 8 UEFI" {
set root='(hd0,gpt2)'
chainloader /EFI/Microsoft/Boot/bootmgfw.efi
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
### BEGIN /etc/grub.d/60_memtest86+ ###
### END /etc/grub.d/60_memtest86+ ###
========================= sda6/syslinux/syslinux.cfg: ==========================
# Config file for Syslinux -
# /boot/syslinux/syslinux.cfg
# Comboot modules:
# * menu.c32 - provides a text menu
# * vesamenu.c32 - provides a graphical menu
# * chain.c32 - chainload MBRs, partition boot sectors, Windows bootloaders
# * hdt.c32 - hardware detection tool
# * reboot.c32 - reboots the system
# To Use: Copy the respective files from /usr/lib/syslinux to /boot/syslinux.
# If /usr and /boot are on the same file system, symlink the files instead
# of copying them.
# If you do not use a menu, a 'boot:' prompt will be shown and the system
# will boot automatically after 5 seconds.
# Please review the wiki: https://wiki.archlinux.org/index.php/Syslinux
# The wiki provides further configuration examples
DEFAULT arch
PROMPT 0 # Set to 1 if you always want to display the boot: prompt
TIMEOUT 50
# You can create syslinux keymaps with the keytab-lilo tool
#KBDMAP de.ktl
# Menu Configuration
# Either menu.c32 or vesamenu32.c32 must be copied to /boot/syslinux
UI menu.c32
#UI vesamenu.c32
# Refer to http://syslinux.zytor.com/wiki/index.php/Doc/menu
MENU TITLE Arch Linux
#MENU BACKGROUND splash.png
MENU COLOR border 30;44 #40ffffff #a0000000 std
MENU COLOR title 1;36;44 #9033ccff #a0000000 std
MENU COLOR sel 7;37;40 #e0ffffff #20ffffff all
MENU COLOR unsel 37;44 #50ffffff #a0000000 std
MENU COLOR help 37;40 #c0ffffff #a0000000 std
MENU COLOR timeout_msg 37;40 #80ffffff #00000000 std
MENU COLOR timeout 1;37;40 #c0ffffff #00000000 std
MENU COLOR msg07 37;40 #90ffffff #a0000000 std
MENU COLOR tabmsg 31;40 #30ffffff #00000000 std
# boot sections follow
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
LABEL arch
MENU LABEL Arch Linux
LINUX ../vmlinuz-linux
APPEND root=/dev/sda3 rw
INITRD ../initramfs-linux.img
LABEL archfallback
MENU LABEL Arch Linux Fallback
LINUX ../vmlinuz-linux
APPEND root=/dev/sda3 rw
INITRD ../initramfs-linux-fallback.img
#LABEL windows
# MENU LABEL Windows
# COM32 chain.c32
# APPEND hd0 1
LABEL hdt
MENU LABEL HDT (Hardware Detection Tool)
COM32 hdt.c32
LABEL reboot
MENU LABEL Reboot
COM32 reboot.c32
LABEL poweroff
MENU LABEL Poweroff
COM32 poweroff.c32
=================== sda6: Location of files loaded by Grub: ====================
GiB - GB File Fragment(s)
================= sda6: Location of files loaded by Syslinux: ==================
GiB - GB File Fragment(s)
============== sda6: Version of COM32(R) files used by Syslinux: ===============
syslinux/cat.c32 : not a COM32/COM32R module
syslinux/chain.c32 : not a COM32/COM32R module
syslinux/cmd.c32 : not a COM32/COM32R module
syslinux/config.c32 : not a COM32/COM32R module
syslinux/cptime.c32 : not a COM32/COM32R module
syslinux/cpuid.c32 : not a COM32/COM32R module
syslinux/cpuidtest.c32 : not a COM32/COM32R module
syslinux/debug.c32 : not a COM32/COM32R module
syslinux/disk.c32 : not a COM32/COM32R module
syslinux/dmitest.c32 : not a COM32/COM32R module
syslinux/elf.c32 : not a COM32/COM32R module
syslinux/ethersel.c32 : not a COM32/COM32R module
syslinux/gfxboot.c32 : not a COM32/COM32R module
syslinux/gpxecmd.c32 : not a COM32/COM32R module
syslinux/hdt.c32 : not a COM32/COM32R module
syslinux/hexdump.c32 : not a COM32/COM32R module
syslinux/host.c32 : not a COM32/COM32R module
syslinux/ifcpu.c32 : not a COM32/COM32R module
syslinux/ifcpu64.c32 : not a COM32/COM32R module
syslinux/ifmemdsk.c32 : not a COM32/COM32R module
syslinux/ifplop.c32 : not a COM32/COM32R module
syslinux/kbdmap.c32 : not a COM32/COM32R module
syslinux/kontron_wdt.c32 : not a COM32/COM32R module
syslinux/ldlinux.c32 : not a COM32/COM32R module
syslinux/libcom32.c32 : not a COM32/COM32R module
syslinux/libgpl.c32 : not a COM32/COM32R module
syslinux/liblua.c32 : not a COM32/COM32R module
syslinux/libmenu.c32 : not a COM32/COM32R module
syslinux/libutil.c32 : not a COM32/COM32R module
syslinux/linux.c32 : not a COM32/COM32R module
syslinux/ls.c32 : not a COM32/COM32R module
syslinux/lua.c32 : not a COM32/COM32R module
syslinux/mboot.c32 : not a COM32/COM32R module
syslinux/meminfo.c32 : not a COM32/COM32R module
syslinux/menu.c32 : not a COM32/COM32R module
syslinux/pcitest.c32 : not a COM32/COM32R module
syslinux/pmload.c32 : not a COM32/COM32R module
syslinux/poweroff.c32 : not a COM32/COM32R module
syslinux/prdhcp.c32 : not a COM32/COM32R module
syslinux/pwd.c32 : not a COM32/COM32R module
syslinux/pxechn.c32 : not a COM32/COM32R module
syslinux/reboot.c32 : not a COM32/COM32R module
syslinux/rosh.c32 : not a COM32/COM32R module
syslinux/sanboot.c32 : not a COM32/COM32R module
syslinux/sdi.c32 : not a COM32/COM32R module
syslinux/sysdump.c32 : not a COM32/COM32R module
syslinux/vesainfo.c32 : not a COM32/COM32R module
syslinux/vesamenu.c32 : not a COM32/COM32R module
syslinux/vpdtest.c32 : not a COM32/COM32R module
syslinux/whichsys.c32 : not a COM32/COM32R module
syslinux/zzjson.c32 : not a COM32/COM32R module
=============================== sda9/etc/fstab: ================================
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda9
UUID=1a765403-f251-43d8-8edf-c191475d3837 / ext4 rw,relatime,data=ordered 0 1
# /dev/sda6
#UUID=9C3F-2A9E /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
UUID=9C3F-2A9E /boot vfat defaults 0 2
UUID=9C3F-2A9E /boot/efi vfat defaults 0 1
============== sda9: Version of COM32(R) files used by Syslinux: ===============
boot/syslinux/cat.c32 : not a COM32/COM32R module
boot/syslinux/chain.c32 : not a COM32/COM32R module
boot/syslinux/cmd.c32 : not a COM32/COM32R module
boot/syslinux/config.c32 : not a COM32/COM32R module
boot/syslinux/cptime.c32 : not a COM32/COM32R module
boot/syslinux/cpuid.c32 : not a COM32/COM32R module
boot/syslinux/cpuidtest.c32 : not a COM32/COM32R module
boot/syslinux/debug.c32 : not a COM32/COM32R module
boot/syslinux/disk.c32 : not a COM32/COM32R module
boot/syslinux/dmitest.c32 : not a COM32/COM32R module
boot/syslinux/elf.c32 : not a COM32/COM32R module
boot/syslinux/ethersel.c32 : not a COM32/COM32R module
boot/syslinux/gfxboot.c32 : not a COM32/COM32R module
boot/syslinux/gpxecmd.c32 : not a COM32/COM32R module
boot/syslinux/hdt.c32 : not a COM32/COM32R module
boot/syslinux/hexdump.c32 : not a COM32/COM32R module
boot/syslinux/host.c32 : not a COM32/COM32R module
boot/syslinux/ifcpu.c32 : not a COM32/COM32R module
boot/syslinux/ifcpu64.c32 : not a COM32/COM32R module
boot/syslinux/ifmemdsk.c32 : not a COM32/COM32R module
boot/syslinux/ifplop.c32 : not a COM32/COM32R module
boot/syslinux/kbdmap.c32 : not a COM32/COM32R module
boot/syslinux/kontron_wdt.c32 : not a COM32/COM32R module
boot/syslinux/ldlinux.c32 : not a COM32/COM32R module
boot/syslinux/libcom32.c32 : not a COM32/COM32R module
boot/syslinux/libgpl.c32 : not a COM32/COM32R module
boot/syslinux/liblua.c32 : not a COM32/COM32R module
boot/syslinux/libmenu.c32 : not a COM32/COM32R module
boot/syslinux/libutil.c32 : not a COM32/COM32R module
boot/syslinux/linux.c32 : not a COM32/COM32R module
boot/syslinux/ls.c32 : not a COM32/COM32R module
boot/syslinux/lua.c32 : not a COM32/COM32R module
boot/syslinux/mboot.c32 : not a COM32/COM32R module
boot/syslinux/meminfo.c32 : not a COM32/COM32R module
boot/syslinux/menu.c32 : not a COM32/COM32R module
boot/syslinux/pcitest.c32 : not a COM32/COM32R module
boot/syslinux/pmload.c32 : not a COM32/COM32R module
boot/syslinux/poweroff.c32 : not a COM32/COM32R module
boot/syslinux/prdhcp.c32 : not a COM32/COM32R module
boot/syslinux/pwd.c32 : not a COM32/COM32R module
boot/syslinux/pxechn.c32 : not a COM32/COM32R module
boot/syslinux/reboot.c32 : not a COM32/COM32R module
boot/syslinux/rosh.c32 : not a COM32/COM32R module
boot/syslinux/sanboot.c32 : not a COM32/COM32R module
boot/syslinux/sdi.c32 : not a COM32/COM32R module
boot/syslinux/sysdump.c32 : not a COM32/COM32R module
boot/syslinux/vesainfo.c32 : not a COM32/COM32R module
boot/syslinux/vesamenu.c32 : not a COM32/COM32R module
boot/syslinux/vpdtest.c32 : not a COM32/COM32R module
boot/syslinux/whichsys.c32 : not a COM32/COM32R module
boot/syslinux/zzjson.c32 : not a COM32/COM32R module
======================== Unknown MBRs/Boot Sectors/etc: ========================
Unknown GPT Partiton Type
e7afbfbf4fa38a449a5b6213eb736c22
========= Devices which don't seem to have a corresponding hard drive: =========
sdb
=============================== StdErr Messages: ===============================
cat: /tmp/BootInfo-p9ML2Cte/Tmp_Log: No such file or directory
cat: /tmp/BootInfo-p9ML2Cte/Tmp_Log: No such file or directory
/dev/cdrom: open failed: No medium found
/dev/sdb: open failed: No medium found
No volume groups found
mdadm: No arrays found in config file or automatically
Any ideas?
Here's my grub.cfg:
# DO NOT EDIT THIS FILE
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_gpt
insmod ext2
set root='hd0,gpt9'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt9 --hint-efi=hd0,gpt9 --hint-baremetal=ahci0,gpt9 1a765403-f251-43d8-8edf-c191475d3837
else
search --no-floppy --fs-uuid --set=root 1a765403-f251-43d8-8edf-c191475d3837
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
fi
terminal_input console
terminal_output gfxterm
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-1a765403-f251-43d8-8edf-c191475d3837' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod fat
set root='hd0,gpt6'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt6 --hint-efi=hd0,gpt6 --hint-baremetal=ahci0,gpt6 9C3F-2A9E
else
search --no-floppy --fs-uuid --set=root 9C3F-2A9E
fi
echo 'Loading Linux core repo kernel ...'
linux /vmlinuz-linux root=UUID=1a765403-f251-43d8-8edf-c191475d3837 rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux.img
menuentry 'Arch Linux, with Linux core repo kernel (Fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-fallback-1a765403-f251-43d8-8edf-c191475d3837' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod fat
set root='hd0,gpt6'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt6 --hint-efi=hd0,gpt6 --hint-baremetal=ahci0,gpt6 9C3F-2A9E
else
search --no-floppy --fs-uuid --set=root 9C3F-2A9E
fi
echo 'Loading Linux core repo kernel ...'
linux /vmlinuz-linux root=UUID=1a765403-f251-43d8-8edf-c191475d3837 rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux-fallback.img
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows Boot Manager (on /dev/sda2)' --class windows --class os $menuentry_id_option 'osprober-efi-16DC-8816' {
insmod part_gpt
insmod fat
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 16DC-8816
else
search --no-floppy --fs-uuid --set=root 16DC-8816
fi
chainloader /EFI/Microsoft/Boot/bootmgfw.efi
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
### BEGIN /etc/grub.d/60_memtest86+ ###
### END /etc/grub.d/60_memtest86+ ###
Last edited by knowNothing23 (2013-12-30 00:17:02)Hi,
New to this forum, joined today in anticipation of trying an install of AL...For whatever this may be worth:
I have an HP Pavillion desktop that came with Windows 8 (now 8.1), & has, of course, a UEFI boot system. I tried earlier to install Ubuntu Studio (which I currently run) on the same disk as Windows (/dev/sda), I made (I believe) a huge mistake in trying to install as LVM/ext4... wiped out my Windows install & made the UEFI unavailable... I had to do a complete re-install of Windows (fortunately, I did the recommended system backup, using 4 DVD's!) so then I tried a (non LVM) install on an external usb 3.0, with the Grub 2 on the external disk (great access time, & it worked fine... IMO)...
One other item: as I have been trying to find the right flavor of Linux for my main purposes, I have been trying various distros. & having to try to learn to negotiate the UEFI, secure/legacy procedures (still learning)... As I was unsure of installing rEFind... I did down load the .iso, burn it to a CD...
http://www.rodsbooks.com/refind/getting.html
& in legacy mode, found that simply putting it (rEFind CD into the CD/DVD player, which in the UEFI it is labeled something like HP/UEFI CD/DVD), & then launching it, rEFind worked for some other distros...that is, I was able to boot into my Linux distros, even bypassing Grub), as well as having the option of booting Windows. It may seem trivial that I say this (it maybe is), but I have not seen anywhere (I have scoured the internet rather well) this mentioned as a possibility (though it, of course, would not make such a good permanent solution, especially for computers like mine that have only one CD/DVD player).
HenryP -
OracleVM and paravirtualized guest - "Boot loader didn't return any data!"
Hi folks,
we're having a problem here: We have installed the latest version of Oracle VM Server on a machine that does not provide hardware virtualization support (i.e., no Intel VT or similar). As a result, we will not be able to make use of hardware virtualized VMs, but according to the Oracle docs, we should be able to set up virtual machines of the paravirtualized domain type. So far, so good.
Also according to the docs, when setting up a PVM, one cannot use an ISO image located in a storage repository in order to start the installation, but instead one would have the mount the installation ISO somewhere, make available it's contents via NFS (or HTTP / FTP), and then set up the newly created virtual machine to attempt a PXE boot, specifying the location where the contents of the ISO have been placed (i.e.: nfs:host:/path/to/mounted/iso). All of this is decribed very well in the Oracle VM Server docs (chapter 8), but somehow it still doesn't seem to work for us.
What happens is this: When we attempt to boot our PVM via PXE, specifying the NFS location where we've made the contents of the ISO available, we always get this:
Job Construction Phase
begin()
Appended operation 'Virtual Machine Start' to object '0004fb0000060000ab1b8caa045cc7a8 (VMOEL6)'.
commit()
Completed Step: COMMIT
Objects and Operations
Object (IN_USE): [VirtualMachine] 0004fb0000060000ab1b8caa045cc7a8 (VMOEL6)
Operation: Virtual Machine Start
Object (IN_USE): [Vnic] 0004fb0000070000797b4c17ae1154dd (00:21:f6:00:00:0a)
Object (IN_USE): [StorageElement] 0004fb0000180000eb569988de92923e (SATA_WDC_WD5001ABYS-_WD-WCAS86231834)
Object (IN_USE): [VirtualDisk] 0004fb0000120000cdbce172d90322c3.img (VMOEL6Disk1)
Object (IN_USE): [VmDiskMapping] 0004fb0000130000aaa3f5eb57705a5b
Object (IN_USE): [VmDiskMapping] 0004fb0000130000f1438eedcfee01de
Job Running Phase at 18:11 on Fri, Oct 14, 2011
Job Participants: [44:45:4c:4c:37:00:10:46:80:4b:b8:c0:4f:59:31:4a (ORAVM1)]
Actioner
Starting operation 'Virtual Machine Start' on object '0004fb0000060000ab1b8caa045cc7a8 (VMOEL6)'
Job Internal Error (Operation)com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_4010E Attempt to send command: dispatch to server: ORAVM1 failed. OVMAPI_4004E Server Failed Command: dispatch https://?uname?:[email protected]:8899/api/1 start_vm 0004fb00000300001d1619c621b16838 0004fb0000060000ab1b8caa045cc7a8, Status: org.apache.xmlrpc.XmlRpcException: exceptions.RuntimeError:Command: ['xm', 'create', '/OVS/Repositories/0004fb00000300001d1619c621b16838/VirtualMachines/0004fb0000060000ab1b8caa045cc7a8/vm.cfg'] failed (1): Error: Boot loader didn't return any data!
We've used multiple different ISOs in order to test this, including Oracle Enterprise Linux (just like the example in the docs does), however, we never get any further than this error message.
Any ideas what we might be doing wrong?
Greetings,
NilsHi Avi,
thanks for your reply! Actually, I believe I checked the NFS reachability already. Here's what I can do on the VM server:
[root@ORAVM1 ~]# ls /mnt/test
[root@ORAVM1 ~]# mount.nfs 10.0.0.220:/mnt/iso /mnt/test
[root@ORAVM1 ~]# ls /mnt/test
EFI eula.py images media.repo README-en.html RELEASE-NOTES-x86_64-en RELEASE-NOTES-x86-en.html RPM-GPG-KEY Server
EULA GPL isolinux Packages RELEASE-NOTES-en RELEASE-NOTES-x86_64-en.html repodata RPM-GPG-KEY-oracle supportinfo
eula.en_US HighAvailability LoadBalancer README-en RELEASE-NOTES-en.html RELEASE-NOTES-x86-en ResilientStorage ScalableFileSystem TRANS.TBL
[root@ORAVM1 ~]#
So, I seem to be able to mount the NFS export correctly (what we're seeing are the contents of an Oracle Enterprise Linux ISO). And when setting up the VM, I specify "nfs:10.0.0.220:/mnt/iso" as the PXE boot path. Still it doesn't seem to work. :-(
ovs-agent.log doesn't seem to contain too many additinal information of value either. Here's a snippet of what seems to happen when I power up my VM, but I guess there's nothing really new in there:
[2011-10-20 12:56:37 22423] ERROR (OVSServices:61) dispatch error: start_vm: <Fault 1: "exceptions.RuntimeError:Command: ['xm', 'create', '/OVS/Repositories/0004fb00000300001d1619c621b16838/VirtualMachines/0004fb0000060000ab1b8caa045cc7a8/vm.cfg'] failed (1): Error: Boot loader didn't return any data!\n ">
[2011-10-20 12:56:37 22423] ERROR (OVSCommons:142) catch_error: <Fault 1: "exceptions.RuntimeError:Command: ['xm', 'create', '/OVS/Repositories/0004fb00000300001d1619c621b16838/VirtualMachines/0004fb0000060000ab1b8caa045cc7a8/vm.cfg'] failed (1): Error: Boot loader didn't return any data!\n ">
Traceback (most recent call last):
File "/opt/ovs-agent-3.0/OVSCommons.py", line 140, in wrapper
return func(*args)
File "/opt/ovs-agent-3.0/OVSServices.py", line 59, in dispatch
return getattr(sp, func)(*args)
File "/opt/ovs-agent-3.0/utils/xmlrpclib.py", line 1099, in __call__
return self.__send(self.__name, args)
File "/opt/ovs-agent-3.0/utils/xmlrpclib.py", line 1386, in __request
verbose=self.__verbose
File "/opt/ovs-agent-3.0/utils/xmlrpclib.py", line 1150, in request
return self._parse_response(h.getfile(), sock)
File "/opt/ovs-agent-3.0/utils/xmlrpclib.py", line 1289, in parseresponse
return u.close()
File "/opt/ovs-agent-3.0/utils/xmlrpclib.py", line 746, in close
raise Fault(**self._stack[0])
Fault: <Fault 1: "exceptions.RuntimeError:Command: ['xm', 'create', '/OVS/Repositories/0004fb00000300001d1619c621b16838/VirtualMachines/0004fb0000060000ab1b8caa045cc7a8/vm.cfg'] failed (1): Error: Boot loader didn't return any data!\n ">
So, any further ideas where to look?
Edited by: BadForGood on 21.10.2011 04:38 -
Boot Loader Problem(rEFIt & GRUB/LILO)
Hi,
I'm planning to "triple boot" my iMac with "Mac SL, Win 7, & openSUSE". But installing the "GRUB/LILO" makes my origanel boot loader rEFIt cannot work directly.
I have to select "Win 7/openSUSE" from the rEFIt, and select "WIn 7/openSUSE" again (from GRUB/LILO).
Any suggestion for fixing the problerm so I can boot straight to the OSes?
Thanks.Boot from the solaris dvd in to singe user mode, mount the system under /a and run the instalgrub command in the shell:
/sbin/installgrub -m /boot/grub/stage1 /boot/grub/stage2 /dev/rdsk/c?d?s? (whatever your drive is).
Maybe make a backup copy of /a/boot/grub/menu.lst, I cant remember if it gets over written that way you can copy it back if necessary. -
Nexus7000 Boot issue " Status 90: Loading Boot Loader "
Hi Gents,
I have currently upgraded a NX7k to NX-OS 5.0.2 .
Now I am stuck by rebooting the system (check output below)
No chang after a manual power off and on the System.
Does anybody know how to get out of this boot process ?
Thanks in advanced for your feedback
Saluti
Alibani
<< console output >>
This command will reboot the system. (y/n)? [n] y
2010 Jun 2 09:10:20 FOR110R050_Labor %$ VDC-1 %$ %PLATFORM-2-PFM_SYSTEM_RESET: Manual system restart from Command Line Interface
writing reset reason 9,
Status 90: Loading Boot Loader
Status 90: Loading Boot Loader
Status 90: Loading Boot Loader
Status 90: Loading Boot Loader
Status 90: Loading Boot Loader
Status 90: Loading Boot Loader
Status 90: Loading Boot Loader
Status 90: Loading Boot Loader
Status 90: Loading Boot Loader
Status 90: Loading Boot LoaderHi Wilhelm,
I have tried your advice and it works, my Nexus come back life again
Thanks mate.
best regards,
Yedi -
I unlocked my Xperia Mini ST15i's boot loader, but never got around to flashing any kernel or ROM. I'm having a rebooting issue with the phone now, and want to try repairing it from a PC. Is there a specific procedure for re-locking the boot loader on an ST15i? (Also: after charging the battery fully, then rebooting, sometimes the battery appears half-empty, or even completely empty. Could this indicate the battery needs replacing?)
My ST15i with 4.0.4 installed is rebooting automatically. Sometimes during boot (SONY or XPERIA logos), sometimes just after booting. Bluetooth is off. SIM and SD cards are removed. I have repaired the phone to 4.0.4 using both Bridge for Mac and PC Companion on Windows. The phone will boot successfully only when connected to power or computer via USB. If the USB cable is disconnected after booting, the phone instantly crashes. The battery charge indicator is all over the place. After charging to 100%, the next time the phone is connected the charge icon will only show half full, or after booting in Safe Mode it'll show something like 28%. I tested the phone using a brand-new battery at a phone shop and it still wouldn't boot successfully Any suggestions?
-
Hi,
I have a quick question, I hope someone can help me out with.
I am working from the link below.
http://www.oracle.com/technology/pub/articles/chan-ubl-vmware.html
I have followed the instructions, and have the VM Server loaded, and it looks exactly like the install screen shots. I have dowloaded the Linux install files (1-4)
Unzipped and burned the copy onto a CD. When I try to install the Linux from disk one, I get the error "No boot file name received". It then times out indicating "Operating system not found".
Oracle support said I am not unzipping and copying the contents to the CD correctly. I have downloaded disk 1 about 7 times, to ensure that I am not missing anything on the download. I have burned that "unzipped" file to a CD about 5 times, but I get the same error each time. Its clear that I am missing the Boot loader I think.. although.. when I unzip the file... there is only 1 file there.. not multiple files as indicated should be by the instructions. Anyone have an idea?
Thanks for your help,
ZachSergio,
Thanks for responding.
I use a program called NTI CD and DVD maker. I choose copy, and make it a Data CD.
I tried to drag it and drop it onto the mapped CD drive, but for some reason... XP tells me
to insert a burnable CD into the drive... when I had just inserted a new unused one.
So... I use the NTI program. The unzipped file appears to be an ISO file... everything
looks ok, size etc...
I know what your saying about the single file being the ISO file... I assume that to be what should be there... but when I look at the "READ ME" on the download site:
3) Write the CD images to CDs
Use your favorite cd burning software to write these images directly to CD. Do not write the image files to the CD. To test if you have burned the images correctly, insert a burned cd and ensure that multiple files and directories are visible.
when I insert the CD... I see only one ISO file.. nothing else, so I am not sure what they are referring to. Any ideas? Do you think it might be how I am burning the CD... I have never had this issue before.
Thanks Sergio,
Zach -
Hello,
I'm getting the following error when I try to provision an OS using N1:
Rebooting with command: boot /pci@780/pci@0/pci@1/network@0:dhcp - install
Boot device: /pci@780/pci@0/pci@1/network@0:dhcp File and args: - install
100 Mbps half duplex Link up
Timed out waiting for BOOTP/DHCP reply
TFTP server not specified
ERROR: boot-read fail
Evaluating:
Boot load failed
I know the image is ok, because I provision another system. They ARE however on different subnets, but I believe that was setup ok.Well,
snoop / tcpdump for DHCP/TFTP on that subnet to be quite sure DHCP packets get to target. This way you wouldn't have to say "I believe" but you will be sure, that DHCP offers reached target and all is fine from this perspective ;)
DHCP carries the info from where the image can be downloaded. Then TFTP will be involved(but you seem to be failing before that step).
The other explanations could be, that DHCP server from your N1SM server doesn't run (not probable, since you provisioned something else) or there is some networking HW error (is the correct cable in correct interface?).
hth
Lubos -
Error: Boot loader didn't return any data
Hi,
I have installed 11gR2 Grid on VM guest and tried to reboot but it gave an below error and did not come up. Any ideas. Thanks.
Start - /OVS/running_pool/204_devrac1
PowerOn Failed : Result - failed:<Exception: return=>failed:<Exception: ['xm', 'create', '/var/ovs/mount/BE09FA7986A34D6A93F6589A31AD257F/running_pool/204_devrac1/vm.cfg'] => Error: Boot loader didn't return any data!
>
StackTrace:
File "/opt/ovs-agent-2.3/OVSXXenVM.py", line 57, in xen_start_vm
run_cmd(args=cmd)
File "/opt/ovs-agent-2.3/OVSCommons.py", line 69, in run_cmd
raise Exception('%s => %s' % (cmdlist, p.childerr.read()))
>
StackTrace:
File "/opt/ovs-agent-2.3/OVSSiteVM.py", line 113, in start_vm
raise eJust a question, did you install this host by using DHCP + TFTPBOOT ? If affirmative please follow the recipe below, otherwise nevermind it :)
In your vm.cfg file, if you have configured the following variables:
bootargs = 'bridge=vlan500,mac=00:16:3E:18:F8:49,type=netfront'
bootloader = '/usr/bin/pypxeboot'
this will try pypxeboot by default. If you have this host in the DHCP server, it will receive his network information, but after it will try to jump to TFTPBOOT that will fail since machines is already installed and unlinked. There are two ways to fix it:
- Do not use pypxeboot as the bootloader and instead, use the pygrub (in this case you can comment the bootargs line)
- Patch pypxeboot to work as desired. Please check pypxeboot script do not working as desired? for more information. We did a fix in our OracleVM infrastructure to solve this issue. -
PVM - Boot loader didn't return any data!
Hi Everyone,
This is my first post in Oracle Forums, so I hope doing right questions to the experts who read my issue.
I´m working on a virtualized environment. I created and configured my "base environment" without any problem:
- Server 1: Oracle VM Server 3.2.2 (Clustered Server Pool: "POOL HA")
- Server 2: Oracle VM Server 3.2.2 (Clustered Server Pool: "POOL HA")
- Server 3: Red Hat Enterprise Linux 6 (Oracle VM Manager 3.2.2)
The next step is create several Paravirtualized Guests (Solaris 11 & RHEL 6). I'm able to create the VMs, but the problem is when I try to start them to install the OS...simply I can´t.
The error is as follows:
"Server error message: Command: ['xm', 'create', '/OVS/Repositories/0004fb000003000057155a18cb654250/VirtualMachines/0004fb0000060000fe3a960fd05eb708/vm.cfg'] failed (1): stderr: *Error: Boot loader didn't return any data!*
stdout: Using config file "/OVS/Repositories/0004fb000003000057155a18cb654250/VirtualMachines/0004fb0000060000fe3a960fd05eb708/vm.cfg"."
I´m trying to start them as shown in the Oracle's documentation (Using mounted ISO in http, ftp or NFS). I chose the http option:
In Server 3:
# cd /var/www/html
# mkdir EL5u6-x86_64
# mount -o ro,loop /path/RHEL6.iso EL5u6-x86_64
Network Boot Path = http://localhost/RHEL6.iso
- http Server is working ok
- localhost= Server3_IP
What am I doing wrong?, some kind of parameter in default vm.cfg file is missing?
Thanx in advance for your help!Hi budachst,
Thank you very much for reply, maybe I misunderstood but according to next link, RHEL6 and Solaris 11 x86_64 can be a PVM guest on OVM Serverx86 (My OVM Servers run on 64 bits):
+"By default, Solaris 10 or Solaris 11 OS already has the required paravirtualized (PV) drivers installed as part of the OS"+ -Don't know if RHEL6 too.
+" Oracle Solaris 11 supports x86 64-bit architecture only. "+
http://docs.oracle.com/cd/E35328_01/E35329/html/vmrns-guest-os.html am I right?
The thing now is, I can start and seeing in "running" state my VMs. But I want to install the OS and VNC screen appears in black, I would expect to see the SO screen instead. Any idea? -
Boot loader did not return any data.
Hi,
i have installed the Oracle VM Server and Oracle VM Manager in two different machines. I'm using the VM Manager to create the Virtual Machines(guest). I followed all the steps given in the Oracle VM Manager User guide 2.2. I'm using the RHEL5 as the OS for the guest machine. I receive an error saying 'Boot loader did not return any data.'. The vm.cfg file has got created in the path /OVS/running_pool/12_VM1. The contents of the vm.cfg file are as below
bootloader = '/usr/bin/pygrub'
disk = ['file:/var/ovs/mount/616CC4FA976D4352B1630FFCE835FEC5/running_pool/14_VM1/System.img,xvda,w']
keymap = 'en-us'
memory = '1024'
name = '14_VM1'
on_crash = 'restart'
on_reboot = 'restart'
uuid = '3a925bc9-1555-b5bb-b0f0-c5958db65468'
vcpus = 1
vfb = ['type=vnc,vncunused=1,vnclisten=0.0.0.0,vncpasswd=vm123']
vif = ['mac=00:16:3E:02:8B:64, bridge=xenbr0']
Can any one help out in this ASAP.
Thanks in Advance.re..
sorry but did you installed guest OS or not ?
Did you install from image, from dvd ...?
If yes try start youre vm from server terminal
#>xm create -c vm. cfg
*T -
What reasons are there that the boot loader might not recognize OSX?
So il try to make this brief:
1. I dragged the contents of the "Macintosh HD" partition on my internal hardrive to a partition of an external hardrive made specifically for containing the dmg "Macintosh HD" (which supposedly holds all the files pertaining to OSX?).
2. A couple weeks later (now) I erased the contents of my internal hardrives "Macintosh HD" partition and replaced it with that of the partion of my external hardrive which contains the "backup" dmg "Macintosh HD".
Theoretically, my computer should be exactly as it was a couple weeks ago right?
So going back to the heart of the matter, why doesn't the boot loader recognize OSX?
Thanks in advance for your time :)Maybe I'm going about this the wrong way.... heres what I want to do:
I want to install mac OSX 10.8.5, a couple of audio interface drivers, Pro Tools 11/ 10 and Cubase 6. Following this, I want to imediatley make a backup that will not update. My reasoning; I'm using the computer in question as a "glorified tape recorder" and as we all know, over time computers (even macs) become "cluttered" (im not talking about messy file organization). Reinstalling isn't an ideal solutaion for me as reinstalling OSX would remove all kinds of presets from my DAWS and interface controls (too many to backup individually).
Thanks, Patrick Mulholland.
Maybe you are looking for
-
Problem with WSRV4400N and L2TP
Hi I have just bought this router and i am trying to replace a good working router but with no VPN support. I upgraded this router to Firmware Version: V2.0.2.1-ETSI and problem still continue I only set the L2TP Server , user and password. I also t
-
Hi all the is code i have used DECLARE CURRENTRECORD NUMBER; BEGIN DECLARE CURRENT_DISCOUNT NUMBER; CURRENT_REASON VARCHAR2(100); BEGIN CURRENT_DISCOUNT:=:XXSY_DISCOUNT_MANAGER_V.DISCOUNT_RATE;
-
All iTunes songs gone from my iMac and no back, now syncing iPad and iPhone is an issue...help
All my iTunes songs are no longer on my iMac and l have them all on my iPad and iPhone how do l transfer them from either to my iMac and l also have a message pop up in iTunes when either are syncd that they are related to a different iTunes??? Drivi
-
Conversion of a file with 2 converters in UCM / IBR?
Hi Folks, This might be a basic question, but would be helpful in making a key decision in our use case. Can we configure 2 conversions for a single file format? As we would like to convert each incoming jpeg file into PDF as well as getting the imag
-
PROBLEM ABOUT PATCH SET 12733251
Enviroment:windows server 2008 stardard edtion 64bit,oracle 11GR2 64bit enterprise edition,golengate with path set 12733251.When I run ggsci -v,It shows: D:\ggs>ggsci -v Oracle GoldenGate Command Interpreter for Oracle Version 11.1.1.1 12733251 Windo