You are not logged in.

#1 2013-06-22 16:35:44

MickeyRat
Member
Registered: 2011-11-15
Posts: 128

mkinitcpio = Kernel panic - not syncing: No init found.

This is the original post in the thread.  If you want to know the whole history, start here.  At post 25, I discovered that mkinitcpio will cause that kernel panic without an upgrade.  So, it's not really a kernel problem at all.

Be nice I'm really an arch noob.  So, please educate me, if I did something wrong.  This morning I did a pacman -Syu and kernel 3.9.7-1 was part of it.  That's happened before and no problem.  This time though when I reboot.  I see the following error:

Kernel panic - not syncing: No init found.  Try passing init= option to kernel.  See Linux Documentation/init.txt

I get the same error out of the fallback.

I booted off the install CD and was able to chroot into the system and used the command mkinitcpio -p linux to rebuild the initramfs.  It did put new images into /boot but, it still has the same problem.  Any pointers/links would be appreciated.  I'm still working on it (I'll be looking into that init=) but, I'm not all that experienced so we'll have to see how that works out.

Last edited by MickeyRat (2013-06-30 00:05:23)


Some cause happiness wherever they go; others whenever they go.
- Oscar Wilde

Offline

#2 2013-06-22 16:42:20

karol
Archivist
Registered: 2009-05-06
Posts: 25,440

Re: mkinitcpio = Kernel panic - not syncing: No init found.

What init= options have you tried? What's the output of 'ls -l /sbin/init'?

Offline

#3 2013-06-22 17:14:28

MickeyRat
Member
Registered: 2011-11-15
Posts: 128

Re: mkinitcpio = Kernel panic - not syncing: No init found.

I'm reading up on what/how to put in init= now.  I haven't done anything there yet.

/sbin/init -> ../lib/systemd/systemd

I'm not sure about the ..  part but, /lib/systemd/systemd exists.


Some cause happiness wherever they go; others whenever they go.
- Oscar Wilde

Offline

#4 2013-06-22 18:27:18

MickeyRat
Member
Registered: 2011-11-15
Posts: 128

Re: mkinitcpio = Kernel panic - not syncing: No init found.

Well, I tried init=/sbin/init   and init=/lib/systemd/systemd same error.   Luckily I have a backup from yesterday morning.   I haven't done a lot since then but, play around with conky.  I'm probably going to just mount my home partition, backup what I want to save from that and restore he root partition unless someone posts something cool to try in the next few minutes.  I would prefer to learn how to correct this but, maybe it's time to take my fallback.

Thanks for trying to help regardless.

Last edited by MickeyRat (2013-06-22 18:28:03)


Some cause happiness wherever they go; others whenever they go.
- Oscar Wilde

Offline

#5 2013-06-22 18:32:53

DarkCerberus
Banned
From: Holsworthy, Devon
Registered: 2011-12-31
Posts: 252

Re: mkinitcpio = Kernel panic - not syncing: No init found.

Do you have "systemd-sysvcompat" installed? since the latest systemd version grub 2 doesn't need the

init=/usr/lib/systemd/systemd

in the grub 2 configuration file. If you haven't got systemd-sysvcompat then see if you can install it.

Edit: Also only edit the "/etc/default/grub" file - and NOT the "/boot/grub/grub.cfg" if you do edit /boot/grub/grub.cfg , do it at your own risk.

Last edited by DarkCerberus (2013-06-22 18:37:05)


Our enemies are your enemies, Nick. Disorder, war. It's just a matter of time before a dirty bomb goes off in Moscow, or an EMP fries Chicago.  ---  Alexander Pierce, Captain America: Winter Soldier
Access Denied! De-cryption failed, override denied all files sealed! --- Triskelion, Shield OS
-----
How to ask questions the smart way

Offline

#6 2013-06-22 19:06:33

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,739

Re: mkinitcpio = Kernel panic - not syncing: No init found.

MickeyRat wrote:

Be nice I'm really an arch noob.  So, please educate me, ...This time though when I reboot.  I see the following error:

Kernel panic - not syncing: No init found.  Try passing init= option to kernel.  See Linux Documentation/init.txt

Was filestem part of the upgrade?  If so, you might want to look at the stickied thread under the Pacman and upgrades section.  DarkCerberus provided the tl;dr version.

Last edited by ewaller (2013-06-22 19:07:01)


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#7 2013-06-22 19:21:57

MickeyRat
Member
Registered: 2011-11-15
Posts: 128

Re: mkinitcpio = Kernel panic - not syncing: No init found.

DarkCerberus wrote:

Do you have "systemd-sysvcompat" installed? since the latest systemd version grub 2 doesn't need the

init=/usr/lib/systemd/systemd

in the grub 2 configuration file. If you haven't got systemd-sysvcompat then see if you can install it.

Edit: Also only edit the "/etc/default/grub" file - and NOT the "/boot/grub/grub.cfg" if you do edit /boot/grub/grub.cfg , do it at your own risk.

Thanks for the reply.  I was only trying the init= because I was running out of things to try and it was suggested in the error message.  It wasn't in there to begin with and I was pretty sure it wouldn't fix it.  Any changes I made were by hitting e in the grub menu.   My understanding is that's not permanent.  If I'm wrong about that, please let me know.  Is it possible that ext4 support was left out of the kernel?  The root partition I'm using is ext4. 

As for systemd-sysvcompat, if I chroot into there, I actually probably can install it but, given the fact that this is a new install (about 2 weeks old), I'm a little cautious on that one.  If it didn't come on the system, I'm not sure I want it around.


Some cause happiness wherever they go; others whenever they go.
- Oscar Wilde

Offline

#8 2013-06-22 20:04:31

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,739

Re: mkinitcpio = Kernel panic - not syncing: No init found.


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#9 2013-06-22 21:00:20

steinchen
Member
Registered: 2013-05-21
Posts: 4

Re: mkinitcpio = Kernel panic - not syncing: No init found.

-deleted-

Edit: Posted in the wrong thread; silly me

Last edited by steinchen (2013-06-22 21:13:26)

Offline

#10 2013-06-23 00:04:46

MickeyRat
Member
Registered: 2011-11-15
Posts: 128

Re: mkinitcpio = Kernel panic - not syncing: No init found.

ewaller wrote:

Interesting thread but, I have to wonder if it's from before bin and sbin were consolidated.  I tried this and I got the error message mentioned in post #16 in that thread, "failed to initialize alpm library (could not find or read directory)"..  What I wound up with is a BUNCH of stuff in /mnt/usr/sbin-backup.  It seems that /mnt/usr/sbin is a symbolic link to /mnt/usr/bin.  That means /usr/bin is now empty.  Unless I'm mistaken, if I tried to boot off that disk, a large chunk of the OS would be inaccessible.  Think I'm going to move it back.  Nothing but, the filesystem owned /usr/sbin BTW.

Think it might be time to pull things back from backup, straighten out grub and figure out how to block that kernel update in pacman.


Some cause happiness wherever they go; others whenever they go.
- Oscar Wilde

Offline

#11 2013-06-27 11:17:46

MickeyRat
Member
Registered: 2011-11-15
Posts: 128

Re: mkinitcpio = Kernel panic - not syncing: No init found.

I thought I'd update this.  I did restore from backup.  I've got that down pretty well now.  I've also done a lot of research and tried that install numerous times with different options.  Each time I've had to go back to my backup.   DarkCerberus, I do have systemd-sysvcompat installed.  ewaller the filesystem wasn't part of the upgrade.  Here's what was and the list keeps getting longer.

Packages (33): ca-certificates-20130610-1  calibre-0.9.36-1  cronie-1.4.9-5
               e2fsprogs-1.42.8-1  firefox-22.0-1  freetype2-2.5.0.1-1
               gimp-2.8.6-1  intel-dri-9.1.3-2  lib32-e2fsprogs-1.42.8-1
               lib32-gdk-pixbuf2-2.28.2-1  lib32-glib2-2.36.3-2
               lib32-libjpeg-turbo-1.3.0-3  lib32-libxi-1.7.1-3
               lib32-libxv-1.0.9-1  lib32-mesa-9.1.3-3
               lib32-mesa-libgl-9.1.3-3  libxi-1.7.1-3  libxv-1.0.9-1
               linux-3.9.7-1  linux-headers-3.9.7-1  logrotate-3.8.5-1
               mesa-9.1.3-2  mesa-libgl-9.1.3-2  ppp-2.4.5-8  procps-ng-3.3.8-2
               skype-4.2.0.11-3  thunderbird-17.0.7-1  virtualbox-4.2.14-1
               virtualbox-guest-iso-4.2.14-1  virtualbox-host-modules-4.2.14-1
               xf86-video-intel-2.21.10-2  xorg-server-1.14.2-1
               xorg-server-common-1.14.2-1

I did find some things wrong.  My swap partition wasn't working.  I probably screwed that up during the install.  That's fixed.   I found some files in the root directory tree that had my personal account's ownership rather than root's.  The ones I found are fixed but, I can't be sure I found them all.  I'm learning a lot about what I can do with a live install and chroot.  That's a good thing but, the list of things that need to be updated is getting longer and that increases the chance I'll have trouble with something else if I ever do get it to work.

Is there any other information about my hardware or installation (please provide commands to get it) that I can post?   I'm considering reinstalling but, that's not something I want to be doing on a regular basis and I'd really prefer to learn how to fix problems like this.  That's like giving up.


Some cause happiness wherever they go; others whenever they go.
- Oscar Wilde

Offline

#12 2013-06-27 23:11:32

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,130

Re: mkinitcpio = Kernel panic - not syncing: No init found.

What does

pacman -Qs grub

give?


CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#13 2013-06-27 23:51:01

MickeyRat
Member
Registered: 2011-11-15
Posts: 128

Re: mkinitcpio = Kernel panic - not syncing: No init found.

cfr wrote:

What does

pacman -Qs grub

give?

Thanks for the reply.  Actually when I've restored from backup and do a pacman -Syu it does ask me if I want to replace grub-bios and local/grub-common.  I'm pretty sure I've tried it at least once.  Right now, I'm on another computer. The Arch installation that is having the trouble is having trouble till I restore that backup again.  I have booted from an Arch install disk and chrooted in though.   I don't have any way to cut and paste so I'm typing this.

local/grub-bios 2.00-2
    GNU GRand Unified Bootloader - i386 PC BIOS Modules
local/grub-common 2.00-2
    GNU GRand Unified Bootloader - Utilities and Common Files
local/startupmanager 1.9.13-5
    GUI app for changing the settings of GRUB, GRUB2, Usplash and Splashy

This is a 64 bit installation.

Last edited by MickeyRat (2013-06-28 00:01:13)


Some cause happiness wherever they go; others whenever they go.
- Oscar Wilde

Offline

#14 2013-06-28 00:30:28

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,130

Re: mkinitcpio = Kernel panic - not syncing: No init found.

You do know that partial upgrades are not supported? If you are saying no to stuff pacman wants to replace, you are essentially doing a partial upgrade. I'm not saying that is the problem here but just generally you should expect partial upgrades to break things.

EDIT: wgetpaste makes it easy to post stuff from the command line.

Last edited by cfr (2013-06-28 00:31:32)


CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#15 2013-06-28 01:16:33

MickeyRat
Member
Registered: 2011-11-15
Posts: 128

Re: mkinitcpio = Kernel panic - not syncing: No init found.

cfr wrote:

You do know that partial upgrades are not supported? If you are saying no to stuff pacman wants to replace, you are essentially doing a partial upgrade. I'm not saying that is the problem here but just generally you should expect partial upgrades to break things.

EDIT: wgetpaste makes it easy to post stuff from the command line.

Thanks!

I've tried it both ways.  It doesn't seem to make any difference.  My thinking was that because the grub upgrades were queried separate from the other 20 or so upgrades which were queried together, it was optional.  Guess not.  I'm not sure how I would use wgetpaste or anything else to paste something when I'm booted from an arch install disk an all I have is the single text console but, I'd love to know how.

I did run across something interesting though.  I'm not sure why I did it but, this time after I'd restored my root partition, when I was chrooted in there to reinstall grub, I tried a mkinitcpio -p linux.  Everything looked alright but, when I rebooted, the old kernel got the same panic.  That would seem to indicate that mkinitcpio is generating an erroneous initramfs.  That does get run as part of the kernel install so it fits with the little I know.  Any suggetions what can be done to correct it or perhaps to get more information to correct it?

Last edited by MickeyRat (2013-06-28 01:20:14)


Some cause happiness wherever they go; others whenever they go.
- Oscar Wilde

Offline

#16 2013-06-28 01:57:39

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,130

Re: mkinitcpio = Kernel panic - not syncing: No init found.

Post mkinitcpio.conf? And the output when you run mkinitcpio -p linux.

In the live environment:
Configure network.
Install wgetpaste. Or chroot and install it as required.
Enjoy.


CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#17 2013-06-28 03:47:54

MickeyRat
Member
Registered: 2011-11-15
Posts: 128

Re: mkinitcpio = Kernel panic - not syncing: No init found.

cfr wrote:

Post mkinitcpio.conf? And the output when you run mkinitcpio -p linux.

In the live environment:
Configure network.
Install wgetpaste. Or chroot and install it as required.
Enjoy.

Okay, I'm officially impressed with wgetpaste!  smile 

The output from mkinitcpio -p linux

==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 3.9.7-1-ARCH
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 3.9.7-1-ARCH
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful

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

Oh and just so I can use wgetpaste again.  Here the current output from pacman -Qs

local/grub 2.00.5043-2
    GNU GRand Unified Bootloader (2)
local/startupmanager 1.9.13-5
    GUI app for changing the settings of GRUB, GRUB2, Usplash and Splashy

Last edited by MickeyRat (2013-06-28 10:45:36)


Some cause happiness wherever they go; others whenever they go.
- Oscar Wilde

Offline

#18 2013-06-28 21:33:54

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,130

Re: mkinitcpio = Kernel panic - not syncing: No init found.

Are you chrooted when you generate the initramfs? Because that output does not look as I would expect. Recent mkinitcpio spits warnings for missing firmware and most people are missing 2 things it looks for. Unless you have these 2 things installed, I'd expect the output to show those warnings. So I'm wondering if you are using an old version of mkinitcpio. That might happen if you were not properly chrooted when you generated the initramfs, for example. (The warnings are entirely harmless unless you need the firmware which most people don't. It is the fact you are not seeing them which I find suspicious...)

PS Yes, isn't wgetpaste fantastic?

Last edited by cfr (2013-06-28 21:35:30)


CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#19 2013-06-28 22:47:03

MickeyRat
Member
Registered: 2011-11-15
Posts: 128

Re: mkinitcpio = Kernel panic - not syncing: No init found.

cfr wrote:

Are you chrooted when you generate the initramfs? Because that output does not look as I would expect. Recent mkinitcpio spits warnings for missing firmware and most people are missing 2 things it looks for. Unless you have these 2 things installed, I'd expect the output to show those warnings. So I'm wondering if you are using an old version of mkinitcpio. That might happen if you were not properly chrooted when you generated the initramfs, for example. (The warnings are entirely harmless unless you need the firmware which most people don't. It is the fact you are not seeing them which I find suspicious...)

PS Yes, isn't wgetpaste fantastic?


Sorry, I was in there with chroot and I should have mentioned that it did show that missing firmware.  Wgetpaste didn't capture those messages though.  I'm guessing they come out on stderr rather than stdout.  Maybe there's something fancy I don't know about for wgetpaste to get them but. it didn't with just a pipe which is what I did.  I think it was BFS and one other one.  I've looked them up before.  Everything I could find said they shouldn't be a problem. 

I'll be breaking my system again in a minute.  I'm getting to where I can do the restore in my sleep. smile  I think I'm going to chroot in and try reinstalling mkinitcpio.   I have my doubts but, it's worth a shot.  I have a windows box that can look at these forums while it's screwed up.  So, If you or anyone else has any other suggestions, don't wait for me. smile

Oh and you got me checking around.  I think I should have done

mkinitcpiio -p linux |& wgetpaste

I just had the pipe alone.  I'm learning. smile

EDIT

Here's the mkinitcpio with the errors:

==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 3.9.7-1-ARCH
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 3.9.7-1-ARCH
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: bfa
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful

Last edited by MickeyRat (2013-06-28 23:56:46)


Some cause happiness wherever they go; others whenever they go.
- Oscar Wilde

Offline

#20 2013-06-28 23:57:28

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,130

Re: mkinitcpio = Kernel panic - not syncing: No init found.

MickeyRat wrote:

I'm learning. smile

Me, too.

I didn't think of that. I guess it sends the warnings to standard error - regular output and error goes to different places so redirect or pipes need to explicitly capture error if they want it as they otherwise just operate on the standard stuff. (I'm not using the right terms, probably.)

Reinstalling mkinitcpio, making sure everything is up to date and regenerating the initramfs seems the best option at this point. [Interpretation: I'm out of ideas.]


CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#21 2013-06-29 00:46:28

MickeyRat
Member
Registered: 2011-11-15
Posts: 128

Re: mkinitcpio = Kernel panic - not syncing: No init found.

cfr wrote:

I didn't think of that. I guess it sends the warnings to standard error - regular output and error goes to different places so redirect or pipes need to explicitly capture error if they want it as they otherwise just operate on the standard stuff. (I'm not using the right terms, probably.)

Reinstalling mkinitcpio, making sure everything is up to date and regenerating the initramfs seems the best option at this point. [Interpretation: I'm out of ideas.]

If you enter your command |& wgetpaste, you will get both the errors/warnings and the standard output.  I reinstalled udev, mkinitcpio, and linux.  No luck.  Every time I think I'm out of ideas, I seem to run across something else to try.  I appreciate your help regardless and thanks for telling me about wgetpaste. smile

Still might have to wimp out and reinstall.  SHEESH!!! I hate giving in like that.


Some cause happiness wherever they go; others whenever they go.
- Oscar Wilde

Offline

#22 2013-06-29 02:03:01

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,130

Re: mkinitcpio = Kernel panic - not syncing: No init found.

Did you reinstall grub to disk following the update and regenerate grub.cfg?


CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#23 2013-06-29 04:33:07

MickeyRat
Member
Registered: 2011-11-15
Posts: 128

Re: mkinitcpio = Kernel panic - not syncing: No init found.

cfr wrote:

Did you reinstall grub to disk following the update and regenerate grub.cfg?

The upgrade included a grub install.  I didn't try reinstalling it to disk.  I'll try it next time I do that upgrade.  Right now I've restored the backup again.  Might try that in the morning.


Some cause happiness wherever they go; others whenever they go.
- Oscar Wilde

Offline

#24 2013-06-29 11:55:10

Sanne
Member
Registered: 2012-03-13
Posts: 87

Re: mkinitcpio = Kernel panic - not syncing: No init found.

MickeyRat wrote:

... the list of things that need to be updated is getting longer and that increases the chance I'll have trouble with something else if I ever do get it to work.

If you want to update your system from your backup to a specific date, you could use the Arch Rollback Machine, see the example Server... line there. Then you could focus temporarily on just your problematic update. It's an unofficial user supplied service, as far as I know, but worked nicely for me when I once had to update in steps.

Good luck with your main problem, I have no further ideas aside from the already given suggestions, unfortunately.

Last edited by Sanne (2013-06-29 12:01:07)


If our currency were not money but appreciation and acknowledgement for what we do for others, for the community, for the benefit of all, we would have paradise on earth.

Offline

#25 2013-06-29 13:18:26

MickeyRat
Member
Registered: 2011-11-15
Posts: 128

Re: mkinitcpio = Kernel panic - not syncing: No init found.

Sanne wrote:
MickeyRat wrote:

... the list of things that need to be updated is getting longer and that increases the chance I'll have trouble with something else if I ever do get it to work.

If you want to update your system from your backup to a specific date, you could use the Arch Rollback Machine, see the example Server... line there. Then you could focus temporarily on just your problematic update. It's an unofficial user supplied service, as far as I know, but worked nicely for me when I once had to update in steps.

Good luck with your main problem, I have no further ideas aside from the already given suggestions, unfortunately.

Thanks!  That sounds like it'll allow me to update in steps instead of braving that harrowing list of upgrades in one go...assuming I ever get to update again.

I've made some progress in isolating the problem.  It's not with the kernel.  It's not even with the upgrade.  It's with mkinitcpio which is part of the kernel install.  On my system restored from backup, I get the same kernel panic if I run mkinitcpio - p linux and reboot.  No upgrade at all.  Of course I backed up the initramfs images first.  So, now to get it back, I just have to copy some files rather than restore the whole system partition.  I tried reinstalliing udev and mkinitcpio but, that didn't do it.

I might need to start a different thread now.  This isn't really a kernel problem now.  Sometimes that's not appreciated.  So, I'm open to suggestions on that.


Some cause happiness wherever they go; others whenever they go.
- Oscar Wilde

Offline

Board footer

Powered by FluxBB