You are not logged in.
I am converting an MBR installation to GPT, so I can dual-boot Win+Arch with Gummiboot.
After successfully changing the partitioning, I (1) set the BIOS to boot in EFI only; (2) booted from an arch EFI installation disk; (3) arch-chrooted in, mounted /boot to the Windows EFI partition, and installed Gummiboot. Gummiboot found the Windows EFI partition and installed correctly, I believe. I next followed the Beginners Guide and created the arch.conf and loader.conf files in the EFI partition.
When I try to boot into Arch, the bootloader reports
/vmlinuz-linux not found
or something similar.
I've clearly overlooked something along the way, but I'm not sure what. Thanks in advance for any suggestions!!
Last edited by hcra (2014-11-14 22:23:07)
Offline
Please post your arch.conf & loader.conf and the output of:
lsblk -f
EDIT: Also, how did you go about converting your MBR disk to a GPT format?
Last edited by Head_on_a_Stick (2014-11-14 17:09:52)
godisnowhere
Online
Please post your arch.conf & loader.conf
#cat arch.conf
title Arch Linux
linux /vmlinuz-linux
initrd /initramfs-linux.img
options root=/dev/sdc1 rw
# cat loader.conf
default arch
timeout 5
and the output of:
lsblk -f
sda
sda1 ntfs Recovery UUID#
sda2 vfat UUID#
sda3
sda4 ntfs UUID#
sda5 ntfs UUID#
sdc
sdc1 ext4 UUID#
sdc2 ext 4 UUID#
How did you go about converting your MBR disk to a GPT format?
I first used the Gparted (live CD) to shrink the initial and ending partitions of sdc slightly. (This may have been unnecessary.) Then, I used Rod Smith's gdisk, following the Wiki.
Offline
Why have you not posted the full output of lsblk?
I wanted to see your mountpoints (fnar!)...
Is sda also a GPT disk?
Have you tried using UUIDs (or PARTUUIDs) to identify your root filesystem in arch.conf?
godisnowhere
Online
Why have you not posted the full output of lsblk?
I'm sorry, but I'm not sure how to post the full output other than type it by hand.
Is sda also a GPT disk?
Yes, I believe so, since Windows is booting UEFI with Gummiboot.
Have you tried using UUIDs (or PARTUUIDs) to identify your root filesystem in arch.conf?
I just tried, doubling checking the UUIDs, and it also failed. Same error output.
Offline
Did you copy (recursively) the contents of /boot to the partition on sda2?
Gummiboot can only boot kernels in the same partition.
What is the output of:
ls /boot
godisnowhere
Online
Did you copy (recursively) the contents of /boot to the partition on sda2?
No.
So, I did just that, and now the boot fails reporting:
Triggering uevents...
Waiting 10 second for device /dev/disk/by-partuuid/c25...cd46c ...
ERROR: device 'PARTUUID=c25b...cd46c' not found. Skipping fsck.
ERROR: Unable to find root device 'PARTUUID=c25... cd46c
Stumbling along ... thanks so much for your willingness to help!
Offline
Sounds like whatever PARTUUID you entered in arch.conf was the wrong one.
godisnowhere
Online
Please see this image at imgur. Looks okay, as far as I can tell. Thanks again!!
Offline
That image shows UUIDs -- these are different to PARTUUIDs (PARTition Universally Unique IDentifiers).
Change "root=PARTUUID" to "root=UUID" in arch.conf
Last edited by Head_on_a_Stick (2014-11-14 22:16:06)
godisnowhere
Online
Genius! Thanks so much Head_on_a_Stick. Solved, straightaway.
Offline
Ha!
Glad you got it sorted!
godisnowhere
Online
I suggest to label the partitions, which are much more easy to handle and remember.
That's why phones got letter on their keys
do it good first, it will be faster than do it twice the saint
Offline