You are not logged in.
Hi.
Recently I've performed arch installation in UEFI mode onto Lenovo x220 laptop.
Right after the installation I've failed to boot, refind just stucked on "loading bla-bla" message. However, it worked sometimes!
After some time, I've figured out, that system will boot only if USB stick with ARCH installation image is present.
I'm a bit new to all this UEFI stuff. And I can't resolve the issue by myself. So I'm asking for your help.
Here what I have
/etc/fstab
#
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda2
UUID=2ef1194a-3584-4e40-b406-ac1bd4255acf / ext4 rw,relatime,data=ordered,noatime,discard 0 1
# /dev/sda3
UUID=5b862aa8-a395-439a-9961-04112fc2fb7b /home ext4 rw,relatime,data=ordered,noatime,discard 0 2
# /dev/sda1
UUID=0F1B-67DE /boot/efi vfat noatime 0 2
tmpfs /tmp tmpfs nodev,nosuid 0 0
# /usr/sbin/efibootmgr -v
BootCurrent: 0019
Timeout: 0 seconds
BootOrder: 0019,000A,0009,0006,000C,0007,0008,000B,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 030a2400d23878bc820f604d8316c068ee79d25b86701296aa5a7848b66cd49dd3ba6a55
Boot0007* USB FDD 030a2400d23878bc820f604d8316c068ee79d25b6ff015a28830b543a8b8641009461e49
Boot0008* ATAPI CD0 030a2500d23878bc820f604d8316c068ee79d25baea2090adfde214e8b3a5e471856a35401
Boot0009* ATA HDD2 030a2500d23878bc820f604d8316c068ee79d25b91af625956449f41a7b91f4f892ab0f602
Boot000A* ATA HDD0 030a2500d23878bc820f604d8316c068ee79d25b91af625956449f41a7b91f4f892ab0f600
Boot000B* ATA HDD1 030a2500d23878bc820f604d8316c068ee79d25b91af625956449f41a7b91f4f892ab0f601
Boot000C* USB HDD 030a2400d23878bc820f604d8316c068ee79d25b33e821aaaf33bc4789bd419f88c50803
Boot000D* PCI LAN 030a2400d23878bc820f604d8316c068ee79d25b78a84aaf2b2afc4ea79cf5cc8f3d3803
Boot000E* ATAPI CD1 030a2500d23878bc820f604d8316c068ee79d25baea2090adfde214e8b3a5e471856a35403
Boot000F* ATAPI CD2 030a2500d23878bc820f604d8316c068ee79d25baea2090adfde214e8b3a5e471856a35404
Boot0010 Other CD 030a2500d23878bc820f604d8316c068ee79d25baea2090adfde214e8b3a5e471856a35406
Boot0011* ATA HDD3 030a2500d23878bc820f604d8316c068ee79d25b91af625956449f41a7b91f4f892ab0f603
Boot0012* ATA HDD4 030a2500d23878bc820f604d8316c068ee79d25b91af625956449f41a7b91f4f892ab0f604
Boot0013 Other HDD 030a2500d23878bc820f604d8316c068ee79d25b91af625956449f41a7b91f4f892ab0f606
Boot0014* IDER BOOT CDROM ACPI(a0341d0,0)PCI(16,2)ATAPI(0,1,0)
Boot0015* IDER BOOT Floppy ACPI(a0341d0,0)PCI(16,2)ATAPI(0,0,0)
Boot0016* ATA HDD 030a2400d23878bc820f604d8316c068ee79d25b91af625956449f41a7b91f4f892ab0f6
Boot0017* ATAPI CD: 030a2400d23878bc820f604d8316c068ee79d25baea2090adfde214e8b3a5e471856a354
Boot0018* PCI LAN 030a2400d23878bc820f604d8316c068ee79d25b78a84aaf2b2afc4ea79cf5cc8f3d3803
Boot0019* rEFInd HD(1,800,100000,2b53f746-3b6b-4a45-83c9-aa15b92b1b50)File(\EFI\refind\refind_x64.efi)
# ls -R /boot/efi/
/boot/efi/:
EFI
/boot/efi/EFI:
arch refind
/boot/efi/EFI/arch:
initramfs-arch-fallback.img initramfs-arch.img refind_linux.conf vmlinuz-arch.efi
/boot/efi/EFI/refind:
icons refind.conf refind_x64.efi
/boot/efi/EFI/refind/icons:
<omited>
refind_linux.conf
"Boot to X" "root=/dev/sda2 ro rootfstype=ext4 systemd.unit=graphical.target"
"Boot to console" "root=/dev/sda2 ro rootfstype=ext4 systemd.unit=multi-user.target"
Thanks in advance.
Last edited by eDio (2013-02-26 07:45:22)
Offline
Hi.
Recently I've performed arch installation in UEFI mode onto Lenovo x220 laptop.Right after the installation I've failed to boot, refind just stucked on "loading bla-bla" message.
Please post exactly what this message is when it fails.
"Boot to X" "root=/dev/sda2 ro rootfstype=ext4 systemd.unit=graphical.target" "Boot to console" "root=/dev/sda2 ro rootfstype=ext4 systemd.unit=multi-user.target"
You might try changing "root=/dev/sda2" to "root=UUID=2ef1194a-3584-4e40-b406-ac1bd4255acf". I don't expect that will work, since if the issue were a changing device identification because of the presence or absence of the USB disk, it should have failed well after the initial "loading" message from rEFInd; but it's worth a try....
Offline
That was a standard message like "using settings" and then came settings as in refind_linux.conf.
Anyway, I've solved this particurlar issue by upgrading kernel to 3.8-2 from testing. However, now I can't rollback to 3.7.9 (it worked better me in terms of powersaving). Any time I try to boot 3.7.9 with newly generated initramfs images, I get message Waiting 10 seconds for device /dev/sda2. No need to say, I believe, that sda will never be discovered in this case...
Sorry for cumbersome reply. I'm a little bit exhausted with all these issues. I would never believe, that installing arch might require such enormous amount of effort.
Offline