LinuxQuestions.org
Register a domain and help support LQ
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
 
Search this Thread
Old 12-06-2013, 11:28 PM   #1
tb75252
Member
 
Registered: Oct 2010
Distribution: Slackware 14.1 (64-bit)
Posts: 112

Rep: Reputation: 2
Hard Drives and UEFI


This is a question from somebody who is not much of a computer expert...

It is my understanding that UEFI stores all information about initialization and startup in an .efi file located on the HD, inside a special partition.

So, if I were to install a brand-new HD and get rid of the old one, I first would have to find a way to backup this special partition, correct?

Is this a job that Clonezilla can handle, or do I need some other utility?
 
Old 12-07-2013, 12:53 AM   #2
wildwizard
Member
 
Registered: Apr 2009
Location: Oz
Distribution: slackware64-14.0
Posts: 785

Rep: Reputation: 234Reputation: 234Reputation: 234
Those efi files are the boot loaders for whatever operating systems are installed.

If you only copy them over then what will they boot?

If your intention is to install a OS on the new disk them don't worry about copying that partition over as your OS installer should create it and install a loader to it.
 
1 members found this post helpful.
Old 12-07-2013, 05:58 AM   #3
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 11,738
Blog Entries: 10

Rep: Reputation: 1604Reputation: 1604Reputation: 1604Reputation: 1604Reputation: 1604Reputation: 1604Reputation: 1604Reputation: 1604Reputation: 1604Reputation: 1604Reputation: 1604
Member Response

Hi,

Quote:
Originally Posted by tb75252 View Post
This is a question from somebody who is not much of a computer expert...

It is my understanding that UEFI stores all information about initialization and startup in an .efi file located on the HD, inside a special partition.

So, if I were to install a brand-new HD and get rid of the old one, I first would have to find a way to backup this special partition, correct?

Is this a job that Clonezilla can handle, or do I need some other utility?
Your understanding is correct. '.efi' information is the 'UEFI' firmware that is then provided to allow the boot process from a bootloader;
Quote:
Excrpt from 'UEFI';
UEFI has support for reading both the partition table as well as understanding filesystems. Hence it is not limited by 440 byte code limitation (MBR boot code) as in BIOS systems. It does not use the MBR boot code at all.
The commonly used UEFI firmwares support both MBR and GPT partition table. EFI in Apple-Intel Macs are known to also support Apple Partition Map besides MBR and GPT. Most UEFI firmwares have support for accessing FAT12 (floppy disks), FAT16 and FAT32 filesystems in HDDs and ISO9660 (and UDF) in CD/DVDs. EFI in Intel Macs can also access HFS/HFS+ filesystems, in addition to the mentioned ones.
UEFI does not launch any boot code in the MBR whether it exists or not. Instead it uses a special partition in the partition table called EFI System Partition in which files required to be launched by the firmware are stored. Each vendor can store its files under <EFI SYSTEM PARTITION>/EFI/<VENDOR NAME>/ folder and can use the firmware or its shell (UEFI shell) to launch the boot program. An EFI System Partition is usually formatted as FAT32 or (less commonly) FAT16.
Under UEFI, every program whether it is an OS loader or a utility (e.g. a memory testing app or recovery tool), should be a UEFI Application corresponding to the EFI firmware bitness/architecture. The vast majority of UEFI firmwares, including recent Apple Macs, use x86_64 EFI firmware. The only known devices that use IA32 (32-bit) EFI are older (pre 2008) Apple Macs, some Intel Cloverfield ultrabooks and some older Intel Server boards are known to operate on Intel EFI 1.10 firmware.
An x86_64 EFI firmware does not include support for launching 32-bit EFI apps (unlike x86_64 Linux and Windows versions which include such support). Therefore the UEFI application must be compiled for that specific firmware processor bitness/architecture.
Simplified boot process;
Quote:
Excerpt from 'UEFI';
Boot Process under UEFI

  1. System switched on - Power On Self Test, or POST process.
  2. UEFI firmware is loaded. Firmware initializes the hardware required for booting.
  3. Firmware then reads its Boot Manager data to determine which UEFI application to be launched and from where (i.e. from which disk and partition).
  4. Firmware then launches the UEFI application as defined in the boot entry in the firmware's boot manager.
  5. The launched UEFI application may launch another application (in case of UEFI Shell or a boot manager like rEFInd) or the kernel and initramfs (in case of a boot loader like GRUB) depending on how the UEFI application was configured.
  6. Note: On some UEFI systems the only possible way to launch UEFI application on boot (if it does not have custom entry in UEFI boot menu) is to put it in this fixed location: <EFI SYSTEM PARTITION>/EFI/boot/bootx64.efi (for 64-bit x86 system)
Hope this helps.
 
Old 12-07-2013, 09:04 AM   #4
tb75252
Member
 
Registered: Oct 2010
Distribution: Slackware 14.1 (64-bit)
Posts: 112

Original Poster
Rep: Reputation: 2
Thanks, Gary. With my limited computer experience, I am not sure that I understand everything in the UEFI excerpt that you posted...

Say that I have an UEFI-capable motherboard and a brand-new, blank hard drive. Say that I want to install Ubuntu, Linux Mint, Fedora, openSUSE, Debian, Slackware Linux, or any other major Linux distribution.

Will any of the above-mentioned distributions then create their own .efi file on a special partition of the hard drive? I think this is what wildwizard is stating.
 
Old 12-07-2013, 12:48 PM   #5
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 11,738
Blog Entries: 10

Rep: Reputation: 1604Reputation: 1604Reputation: 1604Reputation: 1604Reputation: 1604Reputation: 1604Reputation: 1604Reputation: 1604Reputation: 1604Reputation: 1604Reputation: 1604
Member Response

Hi,

Each will handle UEFI in a similar manner to provide usable firmware files for 'EFI' boot process.

I use Slackware and there have been no major issues to date for Slackware 14.1.

I presented the information for understanding, '.efi' files are the firmware information files to allow process of the hardware to boot the system via a bootloader.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Full-drive encryption for UEFI drives Ulysses_ Linux - Security 4 11-02-2013 08:30 PM
Help Creating UEFI A MENU For My Bootable (BIOS/UEFI) CDROM ssenuta Linux - Hardware 0 08-27-2012 09:11 PM
2 hard drives, XP on my main sata drives, 10.2 on my IDE LILO doesnt show on boot up Dachy Slackware 14 01-03-2008 07:01 AM
External Hard Drives/Hard Drives ddrfreak Mandriva 1 12-16-2004 06:12 PM
Upgrading hard drives on Software raid 1 boot drives. linuxboy123 Linux - General 0 12-11-2003 03:28 PM


All times are GMT -5. The time now is 03:12 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration