[SOLVED] Kernel panic - not syncing: Attempted to kill init!

CLFAS · 2015-12-19 22:17:01

I have been attempting to install Arch x86_64 on this PC:

CPU: AMD Athlon 64 x2 4200
MOBO: MSI M2N4 SLI
GPU: NVidia 8400GS

With IDE hard disks.

- I modified the .iso to use the same linux kernel as what I am using on my current Ubuntu install (vmlinuz-3.19.0-25-generic), since the kernel originally provided didn't work (Panic errors).
- There is nothing wrong with the naming of the USB and I have the same issue when installing from CD.

Please see reply #6

I get this error:

Waiting 30 seconds for device /dev/disk/by-label/ARCH_201512 ...
Error: Boot device didn't show up after 30 seconds...
Falling back to interactive prompt.
You can try and fix the problem manually....

So I try "cat /proc/partitions" but nothing shows up:

major minor  #blocks  name

/dev/sdx does not exist
/dev/idx does not exist
/dev/srx does not exist

That's all I've tried and I'm unsure what to do now, so any help would be useful.

Thanks in advance.

Last edited by CLFAS (2015-12-22 10:21:28)

__bjoern_02 · 2015-12-19 23:36:50

I recently had the same issue. I worked around it with the following procedure:
* Wait until it times out and gives you the minimal shell
* Do this: cd /dev; ln -s sdX by-label/ARCH_201512; exit

sdX must be the name of your boot medium. Then it should boot.
For some reason the installation medium doesn't create that symlink (missing udev rule?).

Last edited by __bjoern_02 (2015-12-19 23:39:50)

CLFAS · 2015-12-20 11:27:34

__bjoern_02 wrote:

I recently had the same issue. I worked around it with the following procedure:
* Wait until it times out and gives you the minimal shell
* Do this: cd /dev; ln -s sdX by-label/ARCH_201512; exit
sdX must be the name of your boot medium. Then it should boot.
For some reason the installation medium doesn't create that symlink (missing udev rule?).

This doesn't work as there is no such file or directory. There is no /dev/sdx. I had tried all of them as explained in my original post.

As I am not using SCSI, I am using IDE, surely it's possible that it isn't recognised as sdx, although I'm not sure what else it would be named as, if it properly recognised it at all, due to this issue.

Last edited by CLFAS (2015-12-20 11:38:14)

Ropid · 2015-12-20 12:05:03

Weren't IDE drives /dev/hda etc.? I can't remember.

tom.ty89 · 2015-12-20 14:26:42

No sd-mod take care of all of them with the help of libata. There is probably no more /dev/hdx unless you configured your kernel in some special way.

And you cannot expect the hybrid ISO to work after you randomly modify it that way tbh. You expect the archiso initramfs to work with a completely different kernel from another distro? Not to mention that you might have already destroyed the hybrid structure of it.

You better paste a screenshot of what the panic error from the original ISO is instead. You'll be wasting time fixing it anyway 'cause even if it boots you'll have troube having an installation.

CLFAS · 2015-12-20 15:50:45

tom.ty89 wrote:

No sd-mod take care of all of them with the help of libata. There is probably no more /dev/hdx unless you configured your kernel in some special way.
And you cannot expect the hybrid ISO to work after you randomly modify it that way tbh. You expect the archiso initramfs to work with a completely different kernel from another distro? Not to mention that you might have already destroyed the hybrid structure of it.
You better paste a screenshot of what the panic error from the original ISO is instead. You'll be wasting time fixing it anyway 'cause even if it boots you'll have troube having an installation.

Fair enough, I only swapped it with this kernel since I wasn't aware that kernels are necessarily OS specific.

Original install .iso USB created using 'dd' in Ubuntu

Error screen:

[     0.167671]  0000000000000000 ffff88007b457ec8 ffffffff819145ee 0000000000000000]
[     0.167801]  0000000000000000 ffff88007b457ef8 ffffffff81925a4b 0000000000000000]
[     0.167932] Call Trace:
[     0.167968]  [<ffffffff819183c7>] ? setup_ioapic_dest+0xd1/0xed
[     0.168006]  [<ffffffff819145ee>] native_smp_cpus_done+0xf3/0xfd
[     0.168042]  [<ffffffff81925a4b>] smp_init+0x63/0x83
[     0.168078]  [<ffffffff81900133>] kernel_init_freeable+0xf0/0x218
[     0.168115]  [<ffffffff815672c0>] ? rest_init+0x90/0x90
[     0.168150]  [<ffffffff815672ce>] kernel_init+0xe/0xe0
[     0.168186]  [<ffffffff8157665f>] ret_from_fork+0x3f/0x70
[     0.168222]  [<ffffffff815672c0>] ? rest_init+0x90/0x90
[     0.168257] Code:   Bad RIP value.
[     0.168334] RIP   [<        (null)>]        (null)
[     0.168390]  RSP <ffff88007b457e80>
[     0.168423] CR2: 0000000000000000
[     0.168463] ---[ end trace c9ebcd2a06897652 ]---
[     0.168508] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009
[     0.168508]
[     0.168565] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009
[     0.168565]
_

I've updated the topic title accordingly.

tom.ty89 · 2015-12-20 16:05:37

Try adding "noapic" to the kernel command line when booting. This is likely an upstream bug.

ewaller · 2015-12-20 16:16:00

Why are you trying to use an Ancient Ubuntu kernel? Did you also update the kernel modules in the iso? The Ubuntu kernel cannot use the Arch modules.

CLFAS · 2015-12-22 10:21:04

ewaller wrote:

Why are you trying to use an Ancient Ubuntu kernel? Did you also update the kernel modules in the iso? The Ubuntu kernel cannot use the Arch modules.

I didn't update the modules. Rookie mistake.

tom.ty89 wrote:

Try adding "noapic" to the kernel command line when booting. This is likely an upstream bug.

Thanks, that worked! All installed. Also had to add it to the grub entries so it would pass the "initiate ramdisk..." stage.

Arch Linux

#1 2015-12-19 22:17:01

[SOLVED] Kernel panic - not syncing: Attempted to kill init!

#2 2015-12-19 23:36:50

Re: [SOLVED] Kernel panic - not syncing: Attempted to kill init!

#3 2015-12-20 11:27:34

Re: [SOLVED] Kernel panic - not syncing: Attempted to kill init!

#4 2015-12-20 12:05:03

Re: [SOLVED] Kernel panic - not syncing: Attempted to kill init!

#5 2015-12-20 14:26:42

Re: [SOLVED] Kernel panic - not syncing: Attempted to kill init!

#6 2015-12-20 15:50:45

Re: [SOLVED] Kernel panic - not syncing: Attempted to kill init!

#7 2015-12-20 16:05:37

Re: [SOLVED] Kernel panic - not syncing: Attempted to kill init!

#8 2015-12-20 16:16:00

Re: [SOLVED] Kernel panic - not syncing: Attempted to kill init!

#9 2015-12-22 10:21:04

Re: [SOLVED] Kernel panic - not syncing: Attempted to kill init!

Board footer