You are not logged in.
I spent about 13 hours yesterday trying to convert from a dual-boot Win7 64-bit and Arch 64-bit on an MBR to running on UEFI. My machine is an HP ProBook 4530s that is UEFI capable. After failing a direct conversion, I decided to wipe the whole drive and start from scratch with Arch being the primary installation. I started with the normal installation process, and when I got to partitioning and formatting, that's where the trouble started. Looking here I saw that I needed a 1007KB partition for GRUB to embed the core.img into. It was at this point that I realized, while I was setting up a GPT, that was specific only to the BIOS boot option. I believe this may have something to do with the error I'm having, because during the grub-mkconfig step, it generates successfully, but it also generates an error stating that there's no SQUASHFS on the superblock of partition 1, and an EXT4 filesystem cannot be found on that partition either
I continued here instead, and setup a new EFI partition of 512MB, and an LVM partition after that, result in the following partition table:
Type device filename, or press <Enter> to exit: /dev/sda
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Command (? for help): p
Disk /dev/sda: 1953525168 sectors, 931.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): E6937116-60A6-486B-BF5E-1A79B1801064
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1953525134
Partitions will be aligned on 2048-sector boundaries
Total free space is 1415603599 sectors (675.0 GiB)
Number Start (sector) End (sector) Size Code Name
1 2048 4061 1007.0 KiB EF02 BIOS boot partition
2 4096 1052671 512.0 MiB EF00 EFI System
3 1052672 537923583 256.0 GiB 8E00 Linux LVMLooking at the guide (of which, I followed a step incorrectly) I did not format the BIOS boot partition.
I have 4 volumes inside of the LVM {root,var,boot,home} mounted at their respective locations
lvm> lvdisplay
--- Logical volume ---
LV Path /dev/localhost/boot
LV Name boot
VG Name localhost
LV UUID 6xd7W0-sgxI-zEzk-091N-DWje-4j5q-nLH8cE
LV Write Access read/write
LV Creation host, time archiso, 2013-08-16 18:38:49 -0700
LV Status available
# open 1
LV Size 128.00 MiB
Current LE 32
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:0
--- Logical volume ---
LV Path /dev/localhost/var
LV Name var
VG Name localhost
LV UUID t6Tu4r-23pa-ReQa-jMcB-djlF-OHrr-oD1qi2
LV Write Access read/write
LV Creation host, time archiso, 2013-08-16 18:39:03 -0700
LV Status available
# open 1
LV Size 16.00 GiB
Current LE 4096
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:1
--- Logical volume ---
LV Path /dev/localhost/root
LV Name root
VG Name localhost
LV UUID t6dXUW-mndC-7fd4-l8XT-XtJR-F9Vi-tVM7g5
LV Write Access read/write
LV Creation host, time archiso, 2013-08-16 18:39:16 -0700
LV Status available
# open 1
LV Size 64.00 GiB
Current LE 16384
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:2
--- Logical volume ---
LV Path /dev/localhost/home
LV Name home
VG Name localhost
LV UUID UgnIFa-ISKc-0BiX-2drZ-u0ES-Qkny-Iiq004
LV Write Access read/write
LV Creation host, time archiso, 2013-08-16 18:39:25 -0700
LV Status available
# open 1
LV Size 128.00 GiB
Current LE 32768
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:3The problem that I'm having is that when I boot up, the machine does not recognize that there is any sort of boot device on the hard drive. It just cycles repeatedly stating that there are no operating systems on the disk. I was however able to access the hard drive by going to the boot menu -> EFI File -> (hard drive UUID) -> EFI -> shellx64.efi
I believe the error may be due to the BIOS boot partition on the hard drive, but I was hoping for some more feedback before I started over and wiped the system again.
Offline
The BIOS Boot Partition is useless when booting in EFI mode, but it should also be inert and cause no problems. It's not clear from your description what, if anything, you've installed in the way of a boot loader for your system. You'll definitely need a boot loader (GRUB, ELILO, SYSLINUX, or the EFI stub loader in the kernel), and possibly a boot manager (rEFInd or gummiboot). Some combinations will require you to put your kernel on the EFI System Partition (ESP; your /dev/sda2).
Offline
My apologies, I did not explicitly state my bootloader. I'm using GRUB 2 with efibootmgr
Last edited by ZMoore (2013-08-17 17:26:51)
Offline
Please run the Boot Info Script from a live CD and post the RESULTS.txt file that it generates, either as a link or between code tags.
Offline