[Solved] Kernel panics with "No init found" after upgrade

Jauch · 2013-11-25 21:40:27

Hello

Saturday, after an update, my computer stop booting (only can get to boot Windows).

The message was

Failed to execute /init
Kernel panic - not syncing. No init found

Because there was an update of the kernel, I think maybe it was this that happened.

The kernel now is 3.12.1

I looked into https://wiki.archlinux.org/index.php/Ke … What_To_Do.

But I'm at a loss.
Could be the kernel? Or the update maybe broke something?

COuld you guys guide me on how to check things in order to try to recover the system without the need to re-install it?

The initram fallback gives the same problem...

I didn't changed any hardware, also, nor changed partitions.

Any help would be highly appreciated.
My wife want's her computer back hehe

Cheers,
Eduardo.

Last edited by Jauch (2013-11-27 17:04:17)

Max-P · 2013-11-25 21:59:59

Arch has moved to systemd a very long while ago. You need to tell the kernel what init system to use. See the systemd installation procedure and it should fix your problem. The /sbin/init link is usually provided by systemd-sysvcompat and the link from /sbin/ to /usr/bin/ by filesystem

Check your /var/log/pacman.log to see what was updated to have a better idea. When was the last time you updated? You can either follow the systemd wiki page and tell the kernel where to find systemd init or make sure systemd-sysvcompat is installed. You can change the boot command directly from GRUB or syslinux, so you shouldn't need to get a live CD or anything to boot back in your system and fix it.

Hope this helps.

Last edited by Max-P (2013-11-25 22:01:41)

Jauch · 2013-11-25 22:16:12

Hello Max,

I was pretty sure that I was using systemd already and that I had systemd-sysvcompat installed...
I update my system almost every day, before shutdown. So, the last time I updated before saturday was last week, for sure. More than once

I'll try to follow your advises, but I have a few questions...

Like, grub finishes with:

linux /boot/vmlinuz-linux root=UUID=guid ro
initrd /boot/initrmfs-linux.img

Where should I put the "init=/usr/lib/systemd/systemd"?

I'm pretty sure systemd is already installed...

ewaller · 2013-11-25 22:20:25

You did not mention which bootloader you are using. Look at the kernel command line being invoked by the bootloader. You really should not need to specify any init system. It should find systemd by itself. If you are forcing the init system, it is possible you are pointing it to the wrong place (tl;dr: do not include init= in the kernel command line)

Have you added a disk recently? How are you specifying the root file system ( / ) in your bootloader? (UUID or by /dev/sda1, or whatever?)
Have you done anything that could have changed your UUID on your drive?
What file system is (was) your root file system? Does your boot loader have the proper driver installed for that type of FS?

Max-P · 2013-11-25 22:26:48

It should go anywhere in the first line. It try something like this:

linux /boot/vmlinuz-linux root=UUID=guid init=/usr/lib/systemd/systemd rw

(note that I also changed ro to rw, as it causes disks to be fsck-ed twice)

You probably were using systemd already, my guess is more that either sysvcompat has been removed somehow (package conflict that removed it?), or that the link got corrupt. From the information you gave us, it really looks like the kernel can't find systemd or any init system. Is there any errors before, like "Failed to mount /dev/xxx", or a broken symlink or anything?

@ewaller Interesting, all my systems failed to boot when I have gone full systemd and removed sysvcompat. I had to put the init= line on all of them. I alway assumed it was because the kernel boots /sbin/init by default and that it was because it didn't exist on my system. Is it really supposed to find /usr/lib/systemd/systemd all by itself without the symlinks?

Jauch · 2013-11-25 22:29:57

Sorry.

I did a more "complete" post before, but it takes too long and I was logout.
I use grub.

Grub is using UUID to locate the root.
I think I didn't do anything that could have changed the UUID of the drives...
I have two Hard Disks, one with arch and one with windows, but I didin't changed anything...

The only thing I did was an update, and the kernel was updated to 3.12.1...

The filesystem of the root is ext3, I think... But I'm not sure. It was some time ago...

jasonwryan · 2013-11-25 22:34:07

chroot in and paste the relevant part of pacman's log, your grub and mkinitcpio configs and the output of `blkid` (as root)...

Jauch · 2013-11-25 22:35:15

No error messages. Just the "Failed to execute /init."
The init= added a "Failed to execute "/usr/lib/systemd/systemd" to the error message...

I read somewhere that one have a problem with the symlink related to "lib"... could be this?

Jauch · 2013-11-25 22:37:59

Jason,

I'll prepare a usb with arch linux installer and will do as you told.

gian72 · 2013-11-25 23:23:03

I've the same problem!
Already tried to rollback to the previous kernel... same problem.
my boot fs is ext2 and root fs is ext4.
Already checked and initramfs files have ext4 support.
Here are some info.

grub.cfg (relevant part)

menuentry 'Arch Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-a2b13bd3-9ca4-4c32-89f0-e4a06bde8b18' {
	load_video
	set gfxpayload=keep
	insmod gzio
	insmod part_gpt
	insmod ext2
	set root='hd1,gpt1'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt1 --hint-efi=hd1,gpt1 --hint-baremetal=ahci1,gpt1  b9c3e1ce-fb25-4fc9-9c5f-04fe97be520e
	else
	  search --no-floppy --fs-uuid --set=root b9c3e1ce-fb25-4fc9-9c5f-04fe97be520e
	fi
	echo	'Loading Linux core repo kernel ...'
	linux	/vmlinuz-linux root=UUID=a2b13bd3-9ca4-4c32-89f0-e4a06bde8b18 rw  quiet
	echo	'Loading initial ramdisk ...'
	initrd	/initramfs-linux.img
}

mkinitcpio.conf

# 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=""

/etc/mkinitcpio.d/linux.preset

# 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"

blkid output (note that I've booted from usb pen...sdaX)

/dev/sda1: UUID="2013-11-01-08-10-26-00" LABEL="ARCH_201311" TYPE="iso9660" PTUUID="0d738582" PTTYPE="dos" PARTUUID="0d738582-01" 
/dev/sda2: SEC_TYPE="msdos" LABEL="ARCHISO_EFI" UUID="1B5C-32EF" TYPE="vfat" PARTUUID="0d738582-02" 
/dev/sdb1: UUID="b9c3e1ce-fb25-4fc9-9c5f-04fe97be520e" TYPE="ext2" PARTLABEL="Linux filesystem" PARTUUID="6632b7fc-32ad-4e23-b295-7e8b25833152" 
/dev/sdb2: UUID="a2b13bd3-9ca4-4c32-89f0-e4a06bde8b18" TYPE="ext4" PARTLABEL="Linux filesystem" PARTUUID="0d71612f-00e8-4c06-8618-a1391dc4585d" 
/dev/loop0: TYPE="squashfs" 
/dev/loop1: UUID="f844a479-9328-482b-a105-8a11d0274e4f" TYPE="ext4" 
/dev/loop2: UUID="f844a479-9328-482b-a105-8a11d0274e4f" TYPE="ext4" 
/dev/mapper/arch_root-image: UUID="f844a479-9328-482b-a105-8a11d0274e4f" TYPE="ext4"

thanks for any help!

Gianluca

Scimmia · 2013-11-26 03:22:45

Just how far are you guys getting? Is the initramfs loading?

Jauch · 2013-11-26 09:41:14

Hello Scimmia,

I couldn't boot yet...
My usb pen boot was working, but know, probably due something I changed in BIOS, it keep given an error about not being able to override security bla bla. I think this is related to EFI boot, because the bios is recognizing the usb pen as a UEFI device. Strangely, because I thought that creating the boot disk with dd would prevent this...

Anyway, I will have to create a liveCD in order to get access to my disks and see the log's that were asked for.

About your question.
I don't know if initramfs is loading.
But I think in my case, not.

When I tried the passing the option "init=/usr/lib/systemd/systemd" to the kernel, it complained about not finding it, reverting to the "default" and not finding it either.
So, I think initramfs is not getting load and the problem happens "before"...

But I'm just learning with this problem, so the most probable is that I am completely wrong in my assumptions...

Cheers,
Eduardo.

gian72 · 2013-11-26 17:51:26

I'm on the same idea... no initram is loading...
Gianluca

brain0 · 2013-11-26 17:54:42

From a live system, chroot in and use

mkinitcpio -P

to regenerate the initramfs. After that, send pacman logs from the last update.

gian72 · 2013-11-26 21:29:36

the problem is definitely the initramfs-linux.img file. Somehow it gets not built correctly. I can boot because I've copied the file from another system...
But if I try to regenerate the file via mkinitcpio then I get a file much smaller (1.7M vs 3M) and I'm unable to boot

Last edited by gian72 (2013-11-27 11:41:19)

Jauch · 2013-11-26 21:55:08

I confirm.

Also regenerate the initramfs file and it has 1.7M. No errors messages during the mkinitcpio run.
The fallback image has 15M.

But is impossible to boot with either.

As was asked, here are the info:

grub.conf

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-cdc9ae09-e451-477b-b2db-c1bcc7185246' {
	load_video
	set gfxpayload=keep
	insmod gzio
	insmod part_msdos
	insmod ext2
	set root='hd0,msdos1'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1  cdc9ae09-e451-477b-b2db-c1bcc7185246
	else
	  search --no-floppy --fs-uuid --set=root cdc9ae09-e451-477b-b2db-c1bcc7185246
	fi
	echo	'Loading Linux core repo kernel ...'
	linux	/boot/vmlinuz-linux root=UUID=cdc9ae09-e451-477b-b2db-c1bcc7185246 ro  
	echo	'Loading initial ramdisk ...'
	initrd	/boot/initramfs-linux.img
}
menuentry 'Arch Linux, with Linux core repo kernel (Fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-fallback-cdc9ae09-e451-477b-b2db-c1bcc7185246' {
	load_video
	set gfxpayload=keep
	insmod gzio
	insmod part_msdos
	insmod ext2
	set root='hd0,msdos1'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1  cdc9ae09-e451-477b-b2db-c1bcc7185246
	else
	  search --no-floppy --fs-uuid --set=root cdc9ae09-e451-477b-b2db-c1bcc7185246
	fi
	echo	'Loading Linux core repo kernel ...'
	linux	/boot/vmlinuz-linux root=UUID=cdc9ae09-e451-477b-b2db-c1bcc7185246 ro  
	echo	'Loading initial ramdisk ...'
	initrd	/boot/initramfs-linux-fallback.img
}

mkinitcpio.conf

# 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=""

blkid output

/dev/sda1: UUID="cdc9ae09-e451-477b-b2db-c1bcc7185246" TYPE="ext4" PARTUUID="dd96f9b1-01" 
/dev/sda2: UUID="79e53f18-3e45-4c0a-84f6-f0b267ead784" TYPE="swap" PARTUUID="dd96f9b1-02" 
/dev/sda3: UUID="5534fa7f-e46f-45f9-815a-c459da791abe" TYPE="ext4" PARTUUID="dd96f9b1-03" 
/dev/sdb1: LABEL="System Reserved" UUID="0E1CF1E81CF1CAAB" TYPE="ntfs" PARTUUID="49dd5992-01" 
/dev/sdb2: UUID="C6941B2A941B1D0D" TYPE="ntfs" PARTUUID="49dd5992-02" 
/dev/sdg1: LABEL="ARCH_201311" UUID="14B5-E907" TYPE="vfat" PARTUUID="04d3e825-01" 
/dev/loop0: TYPE="squashfs" 
/dev/loop1: UUID="f844a479-9328-482b-a105-8a11d0274e4f" TYPE="ext4" 
/dev/loop2: UUID="f844a479-9328-482b-a105-8a11d0274e4f" TYPE="ext4" 
/dev/mapper/arch_root-image: UUID="f844a479-9328-482b-a105-8a11d0274e4f" TYPE="ext4" 
/dev/sdh1: LABEL="Elements" UUID="4E1AEA7B1AEA6007" TYPE="ntfs" PARTUUID="00023f15-01"

sda1 is the root, sda2 is swap, sda3 is home, sdb1 and 2 is windows disk, sdg is the pen with arch install, sdh1 is an external HDD.

And at last, here are the 3 last logs of pacman:

2013-11-21 23:16] [PACMAN] Running 'pacman --color auto -Sy'
[2013-11-21 23:16] [PACMAN] synchronizing package lists
[2013-11-21 23:16] [PACMAN] Running 'pacman --color auto -S -u'
[2013-11-21 23:16] [PACMAN] starting full system upgrade
[2013-11-21 23:16] [PACMAN] upgraded colord (1.0.2-2 -> 1.0.4-1)
[2013-11-21 23:16] [PACMAN] upgraded libgdiplus (2.10.9-2 -> 2.10.9-3)
[2013-11-21 23:16] [PACMAN] upgraded libgpod (0.8.2-7 -> 0.8.2-8)
[2013-11-21 23:16] [PACMAN] upgraded libiec61883 (1.2.0-3 -> 1.2.0-4)
[2013-11-21 23:16] [PACMAN] upgraded python2-cssselect (0.8-1 -> 0.9.1-1)
[2013-11-21 23:16] [PACMAN] upgraded tar (1.27-1 -> 1.27.1-1)
[2013-11-22 20:21] [PACMAN] Running 'pacman --color auto -U /home/jauch/tmp/yaourt-tmp-jauch/PKGDEST.BNF/gtk-sharp-git-2.99.1.106.g51f102b-1-x86_64.pkg.tar.xz'
[2013-11-22 20:21] [PACMAN] installed gtk-sharp-git (2.99.1.106.g51f102b-1)
[2013-11-22 21:00] [PACMAN] Running 'pacman --color auto -U /home/jauch/tmp/yaourt-tmp-jauch/PKGDEST.By4/gtk-sharp-3-2.99.1-1-x86_64.pkg.tar.xz'
[2013-11-22 21:00] [PACMAN] removed gtk-sharp-git (2.99.1.106.g51f102b-1)
[2013-11-22 21:00] [PACMAN] installed gtk-sharp-3 (2.99.1-1)
[2013-11-22 21:28] [PACMAN] Running 'pacman --color auto -U /home/jauch/tmp/yaourt-tmp-jauch/PKGDEST.lXI/firebird-superserver-2.5.2.26540_0-1-x86_64.pkg.tar.xz'
[2013-11-23 15:36] [PACMAN] Running 'pacman --color auto -Sy'
[2013-11-23 15:36] [PACMAN] synchronizing package lists
[2013-11-23 15:37] [PACMAN] Running 'pacman --color auto -S -u'
[2013-11-23 15:37] [PACMAN] starting full system upgrade
[2013-11-23 15:37] [PACMAN] upgraded bluez (5.10-3 -> 5.11-1)
[2013-11-23 15:37] [PACMAN] upgraded bluez-libs (5.10-3 -> 5.11-1)
[2013-11-23 15:37] [PACMAN] upgraded bluez-utils (5.10-3 -> 5.11-1)
[2013-11-23 15:38] [PACMAN] upgraded calibre (1.11.0-1 -> 1.12.0-1)
[2013-11-23 15:38] [PACMAN] upgraded caribou (0.4.11-1 -> 0.4.13-1)
[2013-11-23 15:38] [PACMAN] upgraded libtracker-sparql (0.16.3-1 -> 0.16.4-1)
[2013-11-23 15:38] [PACMAN] upgraded tracker (0.16.3-1 -> 0.16.4-1)
[2013-11-23 15:38] [PACMAN] upgraded gnome-online-miners (3.10.0-1 -> 3.10.2-1)
[2013-11-23 15:38] [ALPM] warning: /etc/services installed as /etc/services.pacnew
[2013-11-23 15:38] [PACMAN] upgraded iana-etc (2.30-3 -> 2.30-4)
[2013-11-23 15:38] [PACMAN] upgraded lib32-glib2 (2.38.1-1 -> 2.38.2-1)
[2013-11-23 15:38] [PACMAN] upgraded libdrm (2.4.48-1 -> 2.4.49-1)
[2013-11-23 15:38] [PACMAN] upgraded lib32-libdrm (2.4.48-1 -> 2.4.49-1)
[2013-11-23 15:38] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2013-11-23 15:38] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio.  Please wait...
[2013-11-23 15:38] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2013-11-23 15:38] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2013-11-23 15:38] [ALPM-SCRIPTLET] ==> Starting build: 3.12.1-1-ARCH
[2013-11-23 15:38] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2013-11-23 15:38] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2013-11-23 15:38] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2013-11-23 15:38] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2013-11-23 15:38] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2013-11-23 15:38] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2013-11-23 15:38] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2013-11-23 15:38] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2013-11-23 15:38] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-11-23 15:38] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2013-11-23 15:38] [ALPM-SCRIPTLET] ==> Image generation successful
[2013-11-23 15:38] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2013-11-23 15:38] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2013-11-23 15:38] [ALPM-SCRIPTLET] ==> Starting build: 3.12.1-1-ARCH
[2013-11-23 15:38] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2013-11-23 15:38] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2013-11-23 15:38] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2013-11-23 15:38] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2013-11-23 15:38] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2013-11-23 15:38] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: smsmdtv
[2013-11-23 15:38] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2013-11-23 15:38] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2013-11-23 15:38] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2013-11-23 15:38] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-11-23 15:38] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2013-11-23 15:38] [ALPM-SCRIPTLET] ==> Image generation successful
[2013-11-23 15:38] [PACMAN] upgraded linux (3.12-1 -> 3.12.1-1)
[2013-11-23 15:38] [PACMAN] upgraded wine (1.7.6-1 -> 1.7.7-1)

I usually use yaourt.

Any ideas?

Jauch · 2013-11-26 22:52:05

Hum...

I tried to reinstall the base packet, but had problems with the /usr/lib64. It was not empty and, well it existed...
So I moved the files inside (some libraries of libfbclient that pacman didn't found) and deleted the folder.

After reinstall filesystem, mkinitcpio and linux (that generated a new initramfs), the new image was 3.7M and voualá!

My system is booting again!!!!

yahuuuuuU!!!!!!

gian72 · 2013-11-27 11:03:44

ok same here... did what you did and voilaaaaaa image size correct and booting!
Thanks Gianluca

Jauch · 2013-11-27 11:20:32

Good to hear, Gianluca!

I'm curious about why this problem happened, but being able to solve it is the most important.
So, I think the post can be marked as solved... Maybe an administrator can do that?

Thanks to everybody!

Cheers,
Eduardo.

Sanne · 2013-11-27 16:04:24

Jauch wrote:

So, I think the post can be marked as solved... Maybe an administrator can do that?

No admin needed, just edit the first post and prepend [SOLVED] to the title.

Jauch · 2013-11-27 17:04:41

Thanks for the tip, Sanne

nigelg · 2013-12-09 12:57:24

Not convinced this is solved as no cause has been identified.

In brief: I had exactly the same problem.

regularly run pacman -Syu

broke after latest upgrade December 6th.

Followed apparent fix with no success.

Tried various edits to grub on boot.

updating grub default and rerunning grub failed. no efi partition. This is a long running system that migrated from grub to grub2 but is still MBR based.

tried grub-install -target=i386-pc --recheck --debug etc but boot screen was legacy grub, hmm.

this link led me to suspect that GRUB might be the culprit in part due to this

http://comments.gmane.org/gmane.linux.a … eral/47987

Downgraded Grub to last version in /var/cache/pacman, reran the same grub-install command, much more debug output.

reran mkinitcpio -p linux, much larger file 3.2M instead of earlier 1.7M (same as OP)

rebooted and all was well.

Nigel
Do

brain0 · 2013-12-09 13:54:27

nigelg wrote:

Tried various edits to grub on boot.
updating grub default and rerunning grub failed. no efi partition. This is a long running system that migrated from grub to grub2 but is still MBR based.
tried grub-install -target=i386-pc --recheck --debug etc but boot screen was legacy grub, hmm.
this link led me to suspect that GRUB might be the culprit in part due to this
http://comments.gmane.org/gmane.linux.a … eral/47987
Downgraded Grub to last version in /var/cache/pacman, reran the same grub-install command, much more debug output.

So, you first did a bunch of stuff that is obviously entirely unrelated to the problem.

nigelg wrote:

reran mkinitcpio -p linux, much larger file 3.2M instead of earlier 1.7M (same as OP)

Then you did what you were told from the start and it actually helped. How surprising.

Anyway, I would love to know how you ended up with that incomplete image in the first place.

nigelg · 2013-12-09 15:27:02

Like you I would like to know why the image was incomplete. This has occured for both the OP and myself so there is possibly a common issue somewhere :-).

Both systems appear to have the following in common

i) This was after a routine system update with previously working systemd etc etc.
ii) mkinitcpio ran as part of this update (Given that it is an automatic process, it should not have resulted in the incomplete image.)
iii) both had been migrated from init to systemd
iv) both had sysvcompat
v) both had explicit init=path/to/systemd

How was the OP booting? via MBR or EFI, this system still uses MBR, EFI will have to wait till I chnage the partition setup. Currently /, /boot, /usr and /home are separate partitions.

I agree there should have been no need to do anything else. I stated that I followed the steps taken by the OP. In other words reinstalled base (why? it installed ok the first time and it's Linux not windows) reran mkinitcpio as per etc and still had a 1.7M image. ie the solution did not work.

I was keeping my reply brief (probably a bad idea) but in slightly more detail...

as part of looking for a solution I edited the grub default to remove the init=/usr/lib/systemd/systemd line

(added to enable grub to find the image after update that moved systemd from sbin ). This was discussed as a possible problem.

Re-running grub-install with unspecified target failed as there is no efi partition and the boot script remained unchanged.

Is there an assumption by developers that all systems are now efi? or was it due to booting from current arch-iso (then mounting relevant partitions, arch-chroot and so forth) causing default to x86_64-efi. (It is an x86_64 system with multilib, disks migrated from a previous system)

Changing the target to i386-pc worked but the resulting grub boot screen was obviously wrong, it was a grub-legacy screen, didn't get beyond a grub prompt. hmm. I noticed that the grub package had been updated on 25/11/13 so, clutching at straws at this point, thought I would try reverting to the previous package as that had worked with my setup.

for whatever reason, this earlier version of grub seems to have worked as expected with i386-pc as target. Following this rerunning mkinitcpio resulted in a complete image. Rebooting gave the grub2 boot select screen and all went fine.

It bugs me when I can't find the cause for a problem and unfortunately don't have as much time to dig deep into fixes as I would like :-(

BTY I've been running Linux in various forms since the earliest days of Slackware and only moved to Arch 3 years ago

Jauch · 2013-12-10 11:51:27

Hello nigelg

nigelg wrote:

Not convinced this is solved as no cause has been identified.

Well, The problem was not being able to boot.
We found that the image was somehow corrupted.
Re-installing filesystem e building again the image solved the problem (being able to boot). Without re-installing the filesystem the problem persisted, even after rebuilding the image.

After many updates, the problem didn't happened again.

So, was something very specific, maybe related to a specific update, that only a few users reported.

The reason why the problem (broken image) happened?
No idea.

But it to me is solved, for sure

Cheers,
Jauch.

Last edited by Jauch (2013-12-10 12:12:29)

Arch Linux

#1 2013-11-25 21:40:27

[Solved] Kernel panics with "No init found" after upgrade

#2 2013-11-25 21:59:59

Re: [Solved] Kernel panics with "No init found" after upgrade

#3 2013-11-25 22:16:12

Re: [Solved] Kernel panics with "No init found" after upgrade

#4 2013-11-25 22:20:25

Re: [Solved] Kernel panics with "No init found" after upgrade

#5 2013-11-25 22:26:48

Re: [Solved] Kernel panics with "No init found" after upgrade

#6 2013-11-25 22:29:57

Re: [Solved] Kernel panics with "No init found" after upgrade

#7 2013-11-25 22:34:07

Re: [Solved] Kernel panics with "No init found" after upgrade

#8 2013-11-25 22:35:15

Re: [Solved] Kernel panics with "No init found" after upgrade

#9 2013-11-25 22:37:59

Re: [Solved] Kernel panics with "No init found" after upgrade

#10 2013-11-25 23:23:03

Re: [Solved] Kernel panics with "No init found" after upgrade

#11 2013-11-26 03:22:45

Re: [Solved] Kernel panics with "No init found" after upgrade

#12 2013-11-26 09:41:14

Re: [Solved] Kernel panics with "No init found" after upgrade

#13 2013-11-26 17:51:26

Re: [Solved] Kernel panics with "No init found" after upgrade

#14 2013-11-26 17:54:42

Re: [Solved] Kernel panics with "No init found" after upgrade

#15 2013-11-26 21:29:36

Re: [Solved] Kernel panics with "No init found" after upgrade

#16 2013-11-26 21:55:08

Re: [Solved] Kernel panics with "No init found" after upgrade

#17 2013-11-26 22:52:05

Re: [Solved] Kernel panics with "No init found" after upgrade

#18 2013-11-27 11:03:44

Re: [Solved] Kernel panics with "No init found" after upgrade

#19 2013-11-27 11:20:32

Re: [Solved] Kernel panics with "No init found" after upgrade

#20 2013-11-27 16:04:24

Re: [Solved] Kernel panics with "No init found" after upgrade

#21 2013-11-27 17:04:41

Re: [Solved] Kernel panics with "No init found" after upgrade

#22 2013-12-09 12:57:24

Re: [Solved] Kernel panics with "No init found" after upgrade

#23 2013-12-09 13:54:27

Re: [Solved] Kernel panics with "No init found" after upgrade

#24 2013-12-09 15:27:02

Re: [Solved] Kernel panics with "No init found" after upgrade

#25 2013-12-10 11:51:27

Re: [Solved] Kernel panics with "No init found" after upgrade

Board footer