Arch Linux

xf

Member

Registered: 2017-12-11

Posts: 4

[SOLVED] Kernel Panic on booting from Installation USB

Error log:

[0.000000] [Firmware bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version 0x20 (or later)
[0.749587] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[0.749677] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 4.13.12-1-ARCH #1
[0.749741] Hardware name: Acer Aspire E5-571G/EA50_HB, BIOS V1.04 05/06/2014
[0.749811] Call Trace
[0.749840]  dump_stack+0x63/0x86
[0.749890]  panic+0xe4/0x23d
[0.749929]  mount_block_root+0x278/0x2ab
[0.749974]  ? set_debug_rodata+0x17/0x17
[0.750025]  mount_root+0x6a/0x6d
[0.750074]  prepare_namespace+0x134/0x16c
[0.750119]  kernel_init_freeable+0x1ec/0x205
[0.750167]  ? rest_init+0xe0/0xe0
[0.750206]  kernel_init+0xe/0xfc
[0.750244]  ret_from_fork+0x25/0x30
[0.750307] Kernel Offset: 0x0 from 0xffffffff01000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
[0.750405] ===[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

My processor is an Intel i3-4030u. I am using rEFInd to dual-boot Arch with Windows 8.1 and I created the Installation USB with Rufus and these settings:
https://i.imgur.com/t63KdJ4.png

I am aware of having to update the microcode, but the article is useless for me since I can't use Arch to solve the problem because the problem is not being able to use Arch.

Last edited by xf (2017-12-12 15:17:13)

jasonwryan

Anarchist

From: .nz

Registered: 2009-05-09

Posts: 30,424

Website

Re: [SOLVED] Kernel Panic on booting from Installation USB

Read the Code of Conduct and only post thumbnails http://wiki.archlinux.org/index.php/Cod … s_and_code

---

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

xf

Member

Registered: 2017-12-11

Posts: 4

Re: [SOLVED] Kernel Panic on booting from Installation USB

I did already post a thumbnail, with a size of 175x250 and it linking to a larger image.

Last edited by xf (2017-12-11 21:25:43)

jasonwryan

Anarchist

From: .nz

Registered: 2009-05-09

Posts: 30,424

Website

Re: [SOLVED] Kernel Panic on booting from Installation USB

You did it the other way around...

---

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

loqs

Member

Registered: 2014-03-06

Posts: 17,326

Re: [SOLVED] Kernel Panic on booting from Installation USB

The installation media under bios uses syslinux which includes boot/intel_ucode.img see https://git.archlinux.org/archiso.git/t … so_sys.cfg.

Head_on_a_Stick

Member

From: London

Registered: 2014-02-20

Posts: 7,732

Website

Re: [SOLVED] Kernel Panic on booting from Installation USB

I created the Installation USB with Rufus and these settings:
https://i.imgur.com/t63KdJ4.png

Well done, you have used the wrong settings

Rufus needs the "DD" [sic] mode to work with Arch ISO images.

---

Are you infected with Wetiko?

xf

Member

Registered: 2017-12-11

Posts: 4

Re: [SOLVED] Kernel Panic on booting from Installation USB

I already am using the DD mode you mentioned, the other option for DD mode doesn't even support ISO images.

Last edited by xf (2017-12-12 13:37:30)

lo1

Member

Registered: 2017-09-25

Posts: 584

Re: [SOLVED] Kernel Panic on booting from Installation USB

This is strange, because I used Rufus to make the bootable USB too, and I don't remember having to mess with the settings; which means: ISO mode worked just good.
Try to just update your Motherboard BIOS/UEFI firmware or whatever the hell they use to call it these days (sorry for being so reluctant  towards UEFI): it should include Microcode updates, but I don't know if this is going to prevent the kernel panic.

---

How To Ask Questions The Smart Way && Tacts Filters && K.I.S.S. &&
Rootless Root

xf

Member

Registered: 2017-12-11

Posts: 4

Re: [SOLVED] Kernel Panic on booting from Installation USB

Try to just update your Motherboard BIOS/UEFI firmware

Turns out that what you mentioned was exactly the culprit, I updated the BIOS and besides having to reinstall rEFInd and mess around with the BIOS some, it's working perfectly now.