10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi everyone!
A very frustrating night!!! I installed a new linux server on my system that has IDE drives and SATA drives. At the time of installation I only had IDE drive plugged in and that is where I install the linux. Everything works fine until I shut the system down and plug in my SATA... (3 Replies)
Discussion started by: hytron
3 Replies
2. Ubuntu
Hey i am running both ubuntu 10.10 and windows 7, trying to make the default boot be windows 7 instead of ubuntu but it doesn't want to work. Ive tried changing default in the grub file it didnt work, then i installed startup-manager and set windows 7 as the OS and it still boots into ubuntu. Thx... (3 Replies)
Discussion started by: Era555
3 Replies
3. Hardware
Hey All,
Im using Fedora 2.6 (which is cannot be changed for compatibility reasons).
I cloned a drive from a different server and when i added this drive to a new box, during startup it hangs on "Configuring Kernel Parameters:"
Is there any way to bypass this process and still boot... (0 Replies)
Discussion started by: robfwauk
0 Replies
4. Solaris
How do I mirror the boot drive, which I believe is /dev/dsk/c1t0d0s0.
Filesystem size used avail capacity Mounted on
/dev/dsk/c1t0d0s0 16G 457M 15G 3% /
/devices 0K 0K 0K 0% /devices
ctfs 0K 0K 0K ... (7 Replies)
Discussion started by: Kjons76
7 Replies
5. Solaris
Hi Folks,
First a little background, I am working on a ship that operates in the Indian Ocean and Persian/Arabian gulf area. We had a Sunblade 2000 that finally died. The Video board burned up and I guess damaged the mother board. So we ordered 2 rebuilt 2000s one as a spare. Due to mounting... (1 Reply)
Discussion started by: Sean.kelly
1 Replies
6. Solaris
I have Solaris 10 Express that I installed on a PC with two drives. It was on drive 1 (with the boot drive being drive 0). Linux was in a different parition and my boot options where managed by grub.
The Solaris parition's /etc/vfstab referenced the root, user, etc.. disks as c0d1sX. But... (6 Replies)
Discussion started by: lyonsd
6 Replies
7. Solaris
Has anyone installed Solaris 10 10/08 and enabled zfs on the boot drive? We're considering enabling zfs boot on some upcoming production machines and I was curious if anyone here has experiences they wish to share. (1 Reply)
Discussion started by: dangral
1 Replies
8. Ubuntu
there is probably another post about this, i just can't find it on unix.com or google. basically, i am trying to make a boot floppy via CLI/terminal. the problem is that i use an external drive. when i do the first couple of steps, i get rejected. when i do the mounting and unmounting, all the... (4 Replies)
Discussion started by: Texasone
4 Replies
9. Solaris
Solaris system
version 6
I cloned the drive using the DD command.
Using the format command and examining the partitions, all looks the same as the original drive.
Problem:
When I attach the cloned drive as the master, and only drive in system, it will not boot.
Error messages:
... (9 Replies)
Discussion started by: HikerLT
9 Replies
10. UNIX for Dummies Questions & Answers
I need to change the boot slice on a Sun box, more specifically the alias of "disk". When I do a printenv from the ok prompt, it lists "boot-device disk net", but when it boots, it is looking at the wrong slice on "disk" (3 Replies)
Discussion started by: 98_1LE
3 Replies
EFIBOOTMGR(8) EFIBOOTMGR(8)
NAME
efibootmgr - manipulate the EFI Boot Manager
SYNOPSIS
efibootmgr [ -a ] [ -A ] [ -b XXXX ] [ -B XXXX ] [ -c ] [ -d DISK ] [ -e 1|3|-1 ] [ -E NUM ] [ -g ] [ -H XXXX ] [ -i NAME ] [ -l NAME ] [
-L LABEL ] [ -n XXXX ] [ -N ] [ -o XXXX,YYYY,ZZZZ ... ] [ -O ] [ -p PART ] [ -q ] [ -t seconds ] [ -T ] [ -u ] [ -U XXXX ] [ -v ] [ -V ] [
-w ] [ -@ file ]
DESCRIPTION
efibootmgr is a userspace application used to modify the Intel Extensible Firmware Interface (EFI) Boot Manager. This application can cre-
ate and destroy boot entries, change the boot order, change the next running boot option, and more.
Details on the EFI Boot Manager are available from the EFI Specification, v1.02 or later, available from:
<URL:http://developer.intel.com>
Note: efibootmgr requires that the kernel support access to EFI non-volatile variables (through /proc/efi/vars on 2.4 kernels,
/sys/firmware/efi/vars on 2.6 kernels). modprobe efivars should do the trick.
OPTIONS
The following is a list of options accepted by efibootmgr:
-a | --active
Sets bootnum active
-A | --inactive
Sets bootnum inactive
-b | --bootnum XXXX
Modify BootXXXX (hex)
-B | --delete-bootnum
Delete bootnum (hex)
-c | --create
Create new variable bootnum and add to bootorder
-d | --disk DISK
The disk containing the loader (defaults to /dev/sda)
-e | --edd 1|3|-1
Force EDD 1.0 or 3.0 creation variables, or guess.
-E | --device NUM
EDD 1.0 device number (defaults to 0x80)
-g | --gpt
Force disk with invalid PMBR to be treated as GPT
-H | --acpi_hid XXXX
set the ACPI HID (used with -i)
-i | --iface NAME
create a netboot entry for the named interface
-l | --loader NAME
Specify a loader (defaults to \elilo.efi)
-L | --label LABEL
Boot manager display label (defaults to "Linux")
-n | --bootnext XXXX
Set BootNext to XXXX (hex)
-N | --delete-bootnext
Delete BootNext
-o | --bootorder XXXX,YYYY,ZZZZ
Explicitly set BootOrder (hex)
-O | --delete-bootorder
Delete BootOrder
-p | --part PART
Partition number containing the bootloader (defaults to 1)
-q | --quiet
Quiet mode - supresses output.
--test filename
Don't write to NVRAM, write to filename.
-t | --timeout seconds
Boot Manager timeout, in seconds.
-T | --delete-timeout
Delete Timeout variable.
-u | --unicode | --UCS-2
pass extra command line arguments as UCS-2 (default is ASCII)
-U | --acpi_uid XXXX
set the ACPI UID (used with -i)
-v | --verbose
Verbose mode - prints additional information
-V | --version
Just print version string and exit.
-w | --write-signature
write unique signature to the MBR if needed
-@ | --append-binary-args
append extra variable args from file (use - to read from stdin). Data in file is appended as command line arguments to the boot
loader command, with no modification to the data, so you can pass any binary or text data necessary.
EXAMPLES
1.
DISPLAYING THE CURRENT SETTINGS (MUST BE ROOT).
[root@localhost ~]# efibootmgr BootCurrent: 0004 BootNext: 0003 BootOrder: 0004,0000,0001,0002,0003 Timeout: 30 seconds Boot0000* Diskette
Drive(device:0) Boot0001* CD-ROM Drive(device:FF) Boot0002* Hard Drive(Device:80)/HD(Part1,Sig00112233) Boot0003* PXE Boot:
MAC(00D0B7C15D91) Boot0004* Linux
This shows:
o BootCurrent - the boot entry used to start the currently running system
o BootOrder - the boot order as would appear in the boot manager. The boot manager tries to boot the first active entry in this
list. If unsuccessful, it tries the next entry, and so on.
o BootNext - the boot entry which is scheduled to be run on next boot. This supercedes BootOrder for one boot only, and is deleted
by the boot manager after first use. This allows you to change the next boot behavior without changing BootOrder.
o Timeout - the time in seconds between when the boot manager appears on the screen until when it automatically chooses the startup
value from BootNext or BootOrder.
o Five boot entries (0000 - 0004), along with the active/inactive flag (* means active) and the name displayed on the screen.
2.
CREATING A NEW BOOT OPTION
An OS installer would call efibootmgr -c. This assumes that /boot/efi is your EFI System Partition, and is mounted at /dev/sda1. This
creates a new boot option, called "Linux", and puts it at the top of the boot order list. Options may be passed to modify the default
behavior. The default OS Loader is elilo.efi.
3.
CHANGING THE BOOT ORDER
Assuming the configuration in Example #1, efibootmgr -o 3,4 could be called to specify PXE boot first, then Linux boot.
4.
CHANGING THE BOOT ORDER FOR THE NEXT BOOT ONLY
Assuming the configuration in Example #1, efibootmgr -n 4 could be called to specify that the Linux entry be taken on next boot.
5.
DELETING A BOOT OPTION
Assuming the configuration in Example #1, efibootmgr -b 4 -B could be called to delete entry 4 and remove it from the BootOrder.
6.
CREATING NETWORK BOOT ENTRIES
A system administrator wants to create a boot option to network boot (PXE). Unfortunately, this requires knowing a little more information
about your system than can be easily found by efibootmgr, so you've got to pass additional information - the ACPI HID and UID values.
These can generally be found by using the EFI Boot Manager (in the EFI environment) to create a network boot entry, then using efibootmgr
to print it verbosely. Here's one example: Boot003* Acpi(PNP0A03,0)/PCI(5|0)/Mac(00D0B7F9F510)
ACPI(a0341d0,0)PCI(0,5)MAC(00d0b7f9f510,0) In this case, the ACPI HID is "0A0341d0" and the UID is "0". For the zx2000 gigE, the HID is
"222F" and the UID is "500". For the rx2000 gigE, the HID is "0002" and the UID is "100". You create the boot entry with: efibootmgr -c
-i eth0 -H 222F -U 500 -L netboot
BUGS
Please direct any bugs, features, patches, etc. to Matt Domsch <Matt_Domsch@dell.com>.
AUTHOR
This man page was generated by dann frazier <dannf@debian.org> for the Debian GNU/Linux operating system, but may be used by others.
SEE ALSO
elilo(1)
11 August 2005 EFIBOOTMGR(8)
