You are not logged in.

Pages: 1

#1 2019-12-06 04:57:03

Tuka
Member
Registered: 2019-12-06
Posts: 10

[Solved]Arch on VMware stuck in bootloader

Hi, I followed the guide here https://wiki.archlinux.org/index.php/Installation_guide# and installed Arch on VMware 15 workstation. But the bootloader is stuck in this screen: https://i.imgur.com/O12XE51.png, after 18 s "about" of bootloader is displayed but the system does not boot.

My disk structure (formatted with fdisk,UEFI)

\dev\sda
  \dev\sda1  Primary    \boot        512MB         boot
  \dev\sda2  Primary                 1GB           swap
  \dev\sda3  Primary    \            5GB           root
  \dev\sda4  Extended                Free          extended

VMware Settings:

Guest Os:Other Linux 2.6x 64 bit Kernel
RAM: 1GB
Hard Disk: 8GB
Processors: 2 (1 core each)
UEFI

My refind_linux.conf:

"Boot with standard options" "rw root=UUID=3883fcbd-7e24-417c-a210-522134e12641"

which is the UUID of /dev/sda3.

Output when /dev/sda3 is mounted to /mnt and /dev/sda1 is mounted to /mnt/boot from LiveCD:

ls /mnt/boot
EFI refind_linx.conf
ls /mnt/boot/EFI
refind tools
 ls /mnt/boot/EFI/refind
BOOT.csv icons keys refind.conf refind_x64.efi

I skipped the "passwd" step and "microcode" drivers step and every install completed without any errors. Any way to resolve this?

Thanks.

Update. After pressing Esc a few times the drive logo shows up and when I hit enter, the screen is stuck at this:
https://i.imgur.com/otLDadm.png

Ps.Sorry, V1del for the confusion, actually I was using a .zim file http://download.kiwix.org/zim/other/arc … 019-09.zim of Arch Wiki for installation purposes, I linked the wiki page thinking there was no revision, but then I spotted the difference.

Last edited by Tuka (2019-12-08 03:46:17)

Offline

#2 2019-12-06 08:10:50

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,736

Re: [Solved]Arch on VMware stuck in bootloader

Please don't post oversized images directly. https://wiki.archlinux.org/index.php/Co … s_and_code

Your refind_linux conf does not contain an initrd directive. Nor does your boot mount point contain a kernel. Did you forget to install a kernel? https://wiki.archlinux.org/index.php/In … l_packages or did you install that into your / partition instead of the ESP? In which case you still have to specify an initrd path.

Last edited by V1del (2019-12-06 08:11:40)

Online

#3 2019-12-06 08:24:25

Tuka
Member
Registered: 2019-12-06
Posts: 10

Re: [Solved]Arch on VMware stuck in bootloader

Hi V1del,sorry about the image. If I remember correctly the sequence was:

mount /dev/sda3 /mnt
mkdir /mnt/boot
mount /dev/sda1 /mnt/boot
pacstrap -i /mnt base base-devel

Last edited by Tuka (2019-12-06 08:27:24)

Offline

#4 2019-12-06 08:29:36

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,736

Re: [Solved]Arch on VMware stuck in bootloader

Well that's not yet complete, and makes me assume your initial assertion of following the installation guide not being quite honest, since that pacstrap command was never in the installation guide in that form (but in a lot of third party guides). Actually read the part I linked you to and install a kernel, then add a initrd line on initramfs-linux.img.

Online

#5 2019-12-06 10:37:20

Tuka
Member
Registered: 2019-12-06
Posts: 10

Re: [Solved]Arch on VMware stuck in bootloader

Hi V1del, I did this:

mount /dev/sda3 /mnt
mount /dev/sda1 /mnt/boot
pacstrap /mnt base linux linux-firmware
arch-chroot /mnt
pacman -S amd-ucode
exit
umount /mnt
reboot

I deleted the old refind_linux.conf and generated a new one, now it is:

"Boot with standard options" "root=PARTUUID=3883fcbd-7e24-417c-a210-522134e12641 add_efi_memmap initrd=/boot/amd-ucode.img initrd=/boot/initramfs-linux.img rw"

Upon rebooting I get the following error:

Starting vmlinuz-linux
Using load options 'root=PARTUUID=3883fcbd-7e24-417c-a210-522134e12641 add_efi_memmap initrd=/boot/amd-ucode.img initrd=/boot/initramfs-linux.img rw'
Failed to open file: boot\amd-ucode.img
Trying to load files to higher address
Failed to open file: boot\amd-ucode.img
_

Last edited by Tuka (2019-12-06 10:43:23)

Offline

#6 2019-12-06 10:45:48

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,736

Re: [Solved]Arch on VMware stuck in bootloader

You are on a virtual machine, you don't need to install processor microcodes...

Online

#7 2019-12-06 10:52:52

Tuka
Member
Registered: 2019-12-06
Posts: 10

Re: [Solved]Arch on VMware stuck in bootloader

Hi V1del,
So, I removed the package 

 pacman -R amd-ucode

and updated the refind_linux.conf. But the same error in case of linux.img:

Starting vmlinuz-linux
Using load options 'root=PARTUUID=3883fcbd-7e24-417c-a210-522134e12641 add_efi_memmap initrd=/boot/initramfs-linux.img rw'
Failed to open file: boot\initramfs-linux.img
Trying to load files to higher address
Failed to open file: boot\initramfs-linux.img

Offline

#8 2019-12-06 11:00:30

Lone_Wolf
Forum Moderator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,920

Re: [Solved]Arch on VMware stuck in bootloader

Read https://wiki.archlinux.org/index.php/RE … linux.conf thoroughly and make sure to pay attention to the colored boxes.

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#9 2019-12-06 11:09:43

Tuka
Member
Registered: 2019-12-06
Posts: 10

Re: [Solved]Arch on VMware stuck in bootloader

Hi Lone_Wolf,
So as I understand:
My /boot is on /dev/sda1, I should edit it as 

 "Boot with standard options" "root=PARTUUID=3883fcbd-7e24-417c-a210-522134e12641 add_efi_memmap initrd=/initramfs-%v.img rw"

?
The UUID above is of /dev/sda3 which is the root.

I went ahead and did the change, bootloader shows no error. But:

:: running early hook [udev]
Starting version 244-1-arch
:: running hook [udev]
:: Triggering uevents
[   4.48669] sd 2:0:0:0: [sda] Assuming drive cache: write through
Waiting 10 seconds for device /dev/disk/3883fcbd-7e24-417c-a210-522134e12641 ...
ERROR: device 'PARTUUID=3883fcbd-7e24-417c-a210-522134e12641' not found. Skipping fsck
:: mounting 'PARTUUID=3883fcbd-7e24-417c-a210-522134e12641' on real root
mount: /new_root: can't find PARTUUID=3883fcbd-7e24-417c-a210-522134e12641
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off
[rootfs ]# _

So I looked at this thread https://bbs.archlinux.org/viewtopic.php?id=167109 and chrooted into /mnt from live environment and ran mkinitcpio -P. I got two warnings:

==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: wd719x 

....

==>Image generation successful.

which I guess, I can safely ignore https://wiki.archlinux.org/index.php/Mk … odule_XXXX

My /etc/fstab

# <file systems> <dir> <type> <options> <dump> <pass>
# UUID=3883fcbd-7e24-417c-a210-522134e12641
/dev/sda3 / ext4  rw,realtime 0 1        

# UUID=E042-8B59
/dev/sda1 /boot vfat rw,realtime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shor>

# UUID=0c262d2e-7875-4208-b59c-d7fa13a8e410
/dev/sda2 none swap defaults 0 0

I read several posts on systemd 240 bug causing this. Here is some extra outputs which I think are relevant:

[root@archiso /]bootctl status
Couldn't find EFI system partition.It is recommended to mount it to /boot or /efi. 
Alternatively use --esp-path=to specify the mount point.                                                   # I tried with path=/boot, same result.   
                                                                                                           # My /boot is on /dev/sda1, mounted at /mnt/boot
System                                                                                                     # /root is on /dev/sda3 mounted at /mnt                                                                                                                              
 Firmware: UEFI 2.31(VMware, Inc 1.00)
 Secure Boot: disabled
 Setup mode: user
Current boot loader:
 Product: systemd-boot 243.162-2-arch
 Features:  Boot counting
                  Menu timeout control
                  One-shot menu timeout control
                  Default entry control
                  One-shot entry control
                  Support for XBOOTLDR partition
                  Support for passing random seed to os
ESP: na
File: ↳/EFI/boot/loader.efi

Random seed:
 Passed to os: no
 System Token: not set

Boot loaders listed in EFI variables:
[root@archiso /] _

Should I start a separate thread for this?

Last edited by Tuka (2019-12-07 02:17:10)

Offline

#10 2019-12-07 11:51:12

Tuka
Member
Registered: 2019-12-06
Posts: 10

Re: [Solved]Arch on VMware stuck in bootloader

Seems like the issue was with refind. I resolved this with:

#Login in as root in Live environment
efibootmgr -v
efibootmgr -b x -B  #Deleted corresponding refind entries from pervious output
mount /dev/sda3 /mnt
mount /dev/sda1 /mnt/boot
arch-chroot /mnt
pacman -R refind-efi
cd /mnt/boot
rm refind_linux.conf
cd /EFI
rm -rf refind
pacman -S grub
grub-install  --efi-directory=/boot        #Grub was unable to find the EFI
grub-mkconfig -o /boot/grub/grub.cfg
exit
reboot

Now it boots perfectly with a tty1 login screen, thanks V1del and Lone_Wolf for your initial help.

Last edited by Tuka (2019-12-07 11:54:05)

Offline

#11 2019-12-07 12:22:08

Lone_Wolf
Forum Moderator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,920

Re: [Solved]Arch on VMware stuck in bootloader

Switching to another bootloader feels more like a workaround then a solution, but it's your system.

One additonal comment
device designations like sdx rely on the order in which the system firmware attaches those devices on boot.
Putting the UUID in the fstab line helps  a lot to avoid this.
You can put the /dev/sdxy or /dev/nvmexxxx designation in a comment to make things more readable for humans.

Edit:

Add [Solved} to the thread title (edit your first post to access the title)

Last edited by Lone_Wolf (2019-12-07 12:23:13)

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#12 2019-12-08 09:32:11

g2g591
Member
Registered: 2007-12-24
Posts: 54

Re: [Solved]Arch on VMware stuck in bootloader

Tuka wrote:

Hi Lone_Wolf,
So as I understand:
My /boot is on /dev/sda1, I should edit it as 

 "Boot with standard options" "root=PARTUUID=3883fcbd-7e24-417c-a210-522134e12641 

# <file systems> <dir> <type> <options> <dump> <pass>
# UUID=3883fcbd-7e24-417c-a210-522134e12641
/dev/sda3 / ext4  rw,realtime 0 1

As to why refined didn't work.
PARTUUID != UUID.

Partuuid is the uuid of the partition as listed in a gpt partition table, while UUID is part of the file system metadata. Different numbers, used for similar purposes.

Offline

#13 2019-12-08 12:35:54

latalante1
Member
Registered: 2018-08-30
Posts: 110

Re: [Solved]Arch on VMware stuck in bootloader

Good point.
https://git.kernel.org/pub/scm/linux/ke … nts.c#n203

Offline

Pages: 1

Board footer

Powered by FluxBB