[SOLVED]boot failure after pacman -Syu

sebastian · 2013-12-05 10:51:05

I got this problem in november(photo taken november 25) after i upgraded the system with pacman -Syu where a lot of packages where upgraded. i have tried different versions of linux and i have also done another system upgrade without success(via arch-chroot). I only get to syslinux meny. I am currently using my old linux mint installation.
http://i41.tinypic.com/20ubtoj.jpg

Moderator Edit: Changed img tags to large photo to url tags. -- ewaller

edit: the silutuon was very simple and i didn't have to format the / partition or anything

Last edited by sebastian (2013-12-25 10:04:01)

WorMzy · 2013-12-05 11:17:27

Chroot into Arch and regenerate your initramfs. Post any error messages you get here.

https://wiki.archlinux.org/index.php/Change_Root

Last edited by WorMzy (2013-12-05 11:18:10)

sebastian · 2013-12-05 14:11:56

i chrooted and run "mkinitcpio" but i got
ERROR: ’/lib/modules/3.10.10-1-ARCH‘ is not a valid kernel module directory

WorMzy · 2013-12-05 14:26:46

If you have a separate boot partition, make sure that you've mounted it to the chroot's /boot folder.

Then try

mkinitcpio -p linux

sebastian · 2013-12-05 14:37:54

WorMzy wrote:

If you have a separate boot partition, make sure that you've mounted it to the chroot's /boot folder.
Then try
mkinitcpio -p linux

i do not have a seperate boot partition. Only /home , / , SWAP

Last edited by sebastian (2013-12-05 14:43:36)

WorMzy · 2013-12-05 14:42:14

Okay, that simplifies things.

Can you post the output of

pacman -Q linux

and

file /boot/vmlinuz-linux

sebastian · 2013-12-05 15:06:04

I think we have found the error source

WorMzy wrote:

Okay, that simplifies things.
Can you post the output of
pacman -Q linux
and
file /boot/vmlinuz-linux

linux 3.12.1-3
linux kernel x86 boot executable, version 3.12.1-3-ARCH (tobias@T-POWA-LX) #1 SMP PREEMT Tue nov 26 11:1, RO- rootFS, swap_dev 0x3, Normal VGA

Last edited by sebastian (2013-12-05 15:07:36)

ewaller · 2013-12-05 16:14:43

Hello sebastian,
Welcome to Arch Linux. Your image was a bit over the size permitted by our policy, So I edited your post to make it a link rather than an image. If you wish, you may edit that post and create a click through link to the full size picture through a thumbnail image, if you so choose.

WorMzy · 2013-12-05 16:24:18

sebastian wrote:

I think we have found the error source
WorMzy wrote:
Okay, that simplifies things.
Can you post the output of
pacman -Q linux
and
file /boot/vmlinuz-linux
linux 3.12.1-3
linux kernel x86 boot executable, version 3.12.1-3-ARCH (tobias@T-POWA-LX) #1 SMP PREEMT Tue nov 26 11:1, RO- rootFS, swap_dev 0x3, Normal VGA

Nope, that looks fine. Did you try running

mkinitcpio -p linux

?

I think that 3.10.10 kernel is the one that your Mint install is using.

sebastian · 2013-12-05 16:54:05

WorMzy wrote:

sebastian wrote:
I think we have found the error source
WorMzy wrote:
Okay, that simplifies things.
Can you post the output of
pacman -Q linux
and
file /boot/vmlinuz-linux
linux 3.12.1-3
linux kernel x86 boot executable, version 3.12.1-3-ARCH (tobias@T-POWA-LX) #1 SMP PREEMT Tue nov 26 11:1, RO- rootFS, swap_dev 0x3, Normal VGA
Nope, that looks fine. Did you try running
mkinitcpio -p linux
?
I think that 3.10.10 kernel is the one that your Mint install is using.

yes i did, i got some warnings and things happened but the problem persisted. i will try again only with my TB SSD drive with the arch install connected.

EDIT: no difference and the warnings was about misding kernel modules: aic94xx, smsmdtv

the linux 3.10.10 directory does not exist

Last edited by sebastian (2013-12-05 17:07:28)

WorMzy · 2013-12-05 17:26:26

Assuming they only appeared for the fallback image, you can ignore those.

Could you post your syslinux config, please. I just realised that your screenshot is talking about a 3.11.2 kernel, so something isn't adding up.

sebastian · 2013-12-05 17:38:51

WorMzy wrote:

Assuming they only appeared for the fallback image, you can ignore those.
Could you post your syslinux config, please. I just realised that your screenshot is talking about a 3.11.2 kernel, so something isn't adding up.

it's an old image, but i get almost the same now http://i44.tinypic.com/2dt57yx.jpg

# Config file for Syslinux -
# /boot/syslinux/syslinux.cfg
#
# Comboot modules:
#   * menu.c32 - provides a text menu
#   * vesamenu.c32 - provides a graphical menu
#   * chain.c32 - chainload MBRs, partition boot sectors, Windows bootloaders
#   * hdt.c32 - hardware detection tool
#   * reboot.c32 - reboots the system
#   * poweroff.com - shutdown the system
#
# To Use: Copy the respective files from /usr/lib/syslinux to /boot/syslinux.
# If /usr and /boot are on the same file system, symlink the files instead
# of copying them.
#
# If you do not use a menu, a 'boot:' prompt will be shown and the system
# will boot automatically after 5 seconds.
#
# Please review the wiki: https://wiki.archlinux.org/index.php/Syslinux
# The wiki provides further configuration examples

DEFAULT arch
PROMPT 0        # Set to 1 if you always want to display the boot: prompt 
TIMEOUT 50
# You can create syslinux keymaps with the keytab-lilo tool
#KBDMAP de.ktl

# Menu Configuration
# Either menu.c32 or vesamenu32.c32 must be copied to /boot/syslinux 
UI menu.c32
#UI vesamenu.c32

# Refer to http://syslinux.zytor.com/wiki/index.php/Doc/menu
MENU TITLE Arch Linux
#MENU BACKGROUND splash.png
MENU COLOR border       30;44   #40ffffff #a0000000 std
MENU COLOR title        1;36;44 #9033ccff #a0000000 std
MENU COLOR sel          7;37;40 #e0ffffff #20ffffff all
MENU COLOR unsel        37;44   #50ffffff #a0000000 std
MENU COLOR help         37;40   #c0ffffff #a0000000 std
MENU COLOR timeout_msg  37;40   #80ffffff #00000000 std
MENU COLOR timeout      1;37;40 #c0ffffff #00000000 std
MENU COLOR msg07        37;40   #90ffffff #a0000000 std
MENU COLOR tabmsg       31;40   #30ffffff #00000000 std

# boot sections follow
#
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
#
#-*

LABEL arch
	MENU LABEL Arch Linux
	LINUX ../vmlinuz-linux
	APPEND root=/dev/sda1 rw
	INITRD ../initramfs-linux.img
	radeon.dpm=1

LABEL archfallback
	MENU LABEL Arch Linux Fallback
	LINUX ../vmlinuz-linux
	APPEND root=/dev/sda1 rw
	INITRD ../initramfs-linux-fallback.img

#LABEL windows
#        MENU LABEL Windows
#        COM32 chain.c32
#        APPEND hd0 1

LABEL hdt
        MENU LABEL HDT (Hardware Detection Tool)
        COM32 hdt.c32
 
LABEL reboot
        MENU LABEL Reboot
        COM32 reboot.c32
 
LABEL off
        MENU LABEL Power Off
        COMBOOT poweroff.com

Last edited by sebastian (2013-12-05 17:41:44)

WorMzy · 2013-12-05 20:19:46

That "radeon.dpm=1" under the arch LABEL shouldn't be there, it should be on the APPEND line if anywhere, not sure if that would cause any problems though. I think the rest of your config is fine.

Could you post your /etc/mkinitcpio.conf and /etc/mkinitcpio.d/linux.preset please.

sebastian · 2013-12-05 20:46:40

WorMzy wrote:

That "radeon.dpm=1" under the arch LABEL shouldn't be there, it should be on the APPEND line if anywhere, not sure if that would cause any problems though. I think the rest of your config is fine.
Could you post your /etc/mkinitcpio.conf and /etc/mkinitcpio.d/linux.preset please.

no the "radeon.dpm=1" does not do anything, i replaced syslinux.cfg with syslinux.cfg.pacnew but it didn't change anything.

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES="piix ide_disk reiserfs"
MODULES=""

# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=""

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way.  This is useful for config files.
FILES=""

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
##   This setup specifies all modules in the MODULES setting above.
##   No raid, lvm2, or encrypted root is needed.
#    HOOKS="base"
#
##   This setup will autodetect all modules for your system and should
##   work as a sane default
#    HOOKS="base udev autodetect block filesystems"
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS="base udev block filesystems"
#
##   This setup assembles a pata mdadm array with an encrypted root FS.
##   Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
#    HOOKS="base udev block mdadm encrypt filesystems"
#
##   This setup loads an lvm2 volume group on a usb device.
#    HOOKS="base udev block lvm2 filesystems"
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr, fsck and shutdown hooks.
HOOKS="base udev autodetect modconf block filesystems keyboard fsck"

# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""

# mkinitcpio preset file for the 'linux' package

ALL_config="/etc/mkinitcpio.conf"
ALL_kver="/boot/vmlinuz-linux"

PRESETS=('default' 'fallback')

#default_config="/etc/mkinitcpio.conf"
default_image="/boot/initramfs-linux.img"
#default_options=""

#fallback_config="/etc/mkinitcpio.conf"
fallback_image="/boot/initramfs-linux-fallback.img"
fallback_options="-S autodetect"

Last edited by sebastian (2013-12-05 20:53:43)

WorMzy · 2013-12-05 21:11:40

Those look fine too. I'm running out of ideas. It may help show what's happening if you run mkinitcpio in verbose mode, then upload the output to a pastebin site and share the link here.

e.g.

mkinitcpio -v -p linux-mainline &> output
wgetpaste output

sebastian · 2013-12-05 21:40:09

i get an error http://bpaste.net/show/155879/ if i use -v -p linux instead of -v -p linux-mainline i get http://bpaste.net/show/155882/ but when i choose ar saschlinux- fallback i get the same error as before. the first command does absolutely nothing.

Last edited by sebastian (2013-12-05 21:58:04)

WorMzy · 2013-12-05 22:14:40

Sorry about that, I copied and pasted from my terminal and forgot to modify it for the default Arch kernel.

For some reason, your initcpio images are missing the libc and ld-linux files and symlinks. Could you check whether /usr/lib/ld-2.18.so and
/usr/lib/libc-2.18.so exist on your arch filesystem. If not, reinstall glibc and then rebuild the images again.

sebastian · 2013-12-06 09:36:22

WorMzy wrote:

Sorry about that, I copied and pasted from my terminal and forgot to modify it for the default Arch kernel.
For some reason, your initcpio images are missing the libc and ld-linux files and symlinks. Could you check whether /usr/lib/ld-2.18.so and
/usr/lib/libc-2.18.so exist on your arch filesystem. If not, reinstall glibc and then rebuild the images again.

they both exist and reinstalling glibc did not help.

WorMzy · 2013-12-06 12:29:04

After reading up on how mkinitcpio adds binaries to te image, I've come to the conclusion that there's something wrong with your busybox binary. and it's not reporting any sodeps. Can you post the output of:

file /usr/lib/initcpio/busybox
ldd /usr/lib/initcpio/busybox

sebastian · 2013-12-06 12:53:17

WorMzy wrote:

After reading up on how mkinitcpio adds binaries to te image, I've come to the conclusion that there's something wrong with your busybox binary. and it's not reporting any sodeps. Can you post the output of:
file /usr/lib/initcpio/busybox
ldd /usr/lib/initcpio/busybox

http://bpaste.net/show/156041/
from the second command i get "not a dynamic executable"

WorMzy · 2013-12-06 13:13:21

Well the first output is fine, but the second is not. Try reinstalling mkinitcpio-busybox.

sebastian · 2013-12-06 14:28:46

WorMzy wrote:

Well the first output is fine, but the second is not. Try reinstalling mkinitcpio-busybox.

reinstalling mkinitcpio-busybox didn't change anything. There was no previus versions in the pacman cache either.

WorMzy · 2013-12-06 15:21:54

Does ldd give you the same error? Lets try inspecting the binary manually:

test -x /usr/lib/ld-linux-x86-64.so.2
echo $?
/usr/lib/ld-linux-x86-64.so.2 --verify "/usr/lib/initcpio/busybox"
echo $?

sebastian · 2013-12-06 15:43:13

WorMzy wrote:

Does ldd give you the same error? Lets try inspecting the binary manually:
test -x /usr/lib/ld-linux-x86-64.so.2
echo $?
/usr/lib/ld-linux-x86-64.so.2 --verify "/usr/lib/initcpio/busybox"
echo $?

1
but for the second command /usr/lib/initcpio does not exist
i tried to add init=3 in syslinux.cfg but than i gothttp://i41.tinypic.com/2mn5eft.jpg

the not a dynamic executable error persists

Last edited by sebastian (2013-12-06 17:28:57)

WorMzy · 2013-12-06 18:05:51

sebastian wrote:

WorMzy wrote:
Does ldd give you the same error? Lets try inspecting the binary manually:
test -x /usr/lib/ld-linux-x86-64.so.2
echo $?
/usr/lib/ld-linux-x86-64.so.2 --verify "/usr/lib/initcpio/busybox"
echo $?
1
but for the second command /usr/lib/initcpio does not exist

?

What do you mean it doesn't exist? Is that the message /usr/lib/ld-linux-x86-64.so.2 outputs? Are you sure you entered the command correctly? It's the same file you ran ldd on not so long ago, it should still be there..

In any case, you should be getting a 0 for that first $?, so maybe something is wrong with your ld-linux-x86-64.so.2.
Can you post the output of:

ls -l /usr/lib/ld-linux-x86-64.so.2
ls -l /usr/lib/ld-2.18.so
mount

Use [ code ] tags for the output, please.

You don't need to add an init= to your syslinux config, the /init file is there, it's just not being executed due to missing libraries in the image (as far as I can tell). So remove that init= argument.

Arch Linux

#1 2013-12-05 10:51:05

[SOLVED]boot failure after pacman -Syu

#2 2013-12-05 11:17:27

Re: [SOLVED]boot failure after pacman -Syu

#3 2013-12-05 14:11:56

Re: [SOLVED]boot failure after pacman -Syu

#4 2013-12-05 14:26:46

Re: [SOLVED]boot failure after pacman -Syu

#5 2013-12-05 14:37:54

Re: [SOLVED]boot failure after pacman -Syu

#6 2013-12-05 14:42:14

Re: [SOLVED]boot failure after pacman -Syu

#7 2013-12-05 15:06:04

Re: [SOLVED]boot failure after pacman -Syu

#8 2013-12-05 16:14:43

Re: [SOLVED]boot failure after pacman -Syu

#9 2013-12-05 16:24:18

Re: [SOLVED]boot failure after pacman -Syu

#10 2013-12-05 16:54:05

Re: [SOLVED]boot failure after pacman -Syu

#11 2013-12-05 17:26:26

Re: [SOLVED]boot failure after pacman -Syu

#12 2013-12-05 17:38:51

Re: [SOLVED]boot failure after pacman -Syu

#13 2013-12-05 20:19:46

Re: [SOLVED]boot failure after pacman -Syu

#14 2013-12-05 20:46:40

Re: [SOLVED]boot failure after pacman -Syu

#15 2013-12-05 21:11:40

Re: [SOLVED]boot failure after pacman -Syu

#16 2013-12-05 21:40:09

Re: [SOLVED]boot failure after pacman -Syu

#17 2013-12-05 22:14:40

Re: [SOLVED]boot failure after pacman -Syu

#18 2013-12-06 09:36:22

Re: [SOLVED]boot failure after pacman -Syu

#19 2013-12-06 12:29:04

Re: [SOLVED]boot failure after pacman -Syu

#20 2013-12-06 12:53:17

Re: [SOLVED]boot failure after pacman -Syu

#21 2013-12-06 13:13:21

Re: [SOLVED]boot failure after pacman -Syu

#22 2013-12-06 14:28:46

Re: [SOLVED]boot failure after pacman -Syu

#23 2013-12-06 15:21:54

Re: [SOLVED]boot failure after pacman -Syu

#24 2013-12-06 15:43:13

Re: [SOLVED]boot failure after pacman -Syu

#25 2013-12-06 18:05:51

Re: [SOLVED]boot failure after pacman -Syu

Board footer