Arch Linux

jarvx

Member

Registered: 2017-12-19

Posts: 7

Arch cannnot start after rebooting emergency shell

When I reboot my system, I got error message like this:

[Firmware bug] TSC_DEADLINE disabled duto Errata; please update microcode to version: 0xb2 (or later)

::running early hook [udev]

Warning: /lib/modules/4.14.5-1ARCH/modules.devname not found - ignoring starting version 235

::running hook [udev]
::Triggering uevents ...
Waiting 10 seconds for device /dev/disk/by-partuuid/5f26bda7-0187-48bf-94f4-60006431789e ...
ERROR:device 'PARTUUID=5f26bda7-0187-48bf-94f4-60006431789e' on real root
mount:/new_root: can't find PARTUUID=5f26bda7-0187-48bf-94f4-60006431789e.
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off

[riitfs]:

I woud appreciate for any help

Last edited by jarvx (2017-12-19 01:14:08)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,729

Re: Arch cannnot start after rebooting emergency shell

Sounds like your initramfs didn't get regenerated.

jarvx

Member

Registered: 2017-12-19

Posts: 7

Re: Arch cannnot start after rebooting emergency shell

Sounds like your initramfs didn't get regenerated.

So what should I do to get it work ?  Or What information should I provide here. Thanks so much

I have tried mkinitcpio -p in arch chroot mode but it didn't work.

Last edited by jarvx (2017-12-19 03:30:10)

circleface

Member

Registered: 2012-05-26

Posts: 639

Re: Arch cannnot start after rebooting emergency shell

I assume you did enable the microcode update?

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,729

Re: Arch cannnot start after rebooting emergency shell

You ran mkinicpio, and your boot partition was mounted?

jarvx

Member

Registered: 2017-12-19

Posts: 7

Re: Arch cannnot start after rebooting emergency shell

You ran mkinicpio, and your boot partition was mounted?

I use arch installation media to enter the computer. Then I mounted the all partitions then  ran mkinitcpio after arch-chroot

jarvx

Member

Registered: 2017-12-19

Posts: 7

Re: Arch cannnot start after rebooting emergency shell

I assume you did enable the microcode update?

I think so 

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,729

Re: Arch cannnot start after rebooting emergency shell

So what's actually in /lib/modules/ while you're at the emergency shell?

jarvx

Member

Registered: 2017-12-19

Posts: 7

Re: Arch cannnot start after rebooting emergency shell

So what's actually in /lib/modules/ while you're at the emergency shell?

I cannot type anything  in emergency. When went to chroot mode, the result is

4.11.2-1-ARCH
4.14.6-1-ARCH
4.9.70-1-ARCH
4.9.70-1-lts
extramodules-4.14-ARCH
extramodules-4.9-lts

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,729

Re: Arch cannnot start after rebooting emergency shell

OK, so you have many problems. Normally that output wouldn't be helpful, but it appears that you have 4.14.6 installed but are booting 4.14.5. That usually means your boot partition wasn't mounted when you updated, but the initramfs appears to be updated, so you probably have filesystem problems on /boot. Why do you still have 4.11.2-1-ARCH, and WTF is 4.9.70-1-ARCH? If you can't type anything in the initramfs, your config is screwed up there, too.

Last edited by Scimmia (2017-12-19 05:24:29)

jarvx

Member

Registered: 2017-12-19

Posts: 7

Re: Arch cannnot start after rebooting emergency shell

OK, so you have many problems. Normally that output wouldn't be helpful, but it appears that you have 4.14.6 installed but are booting 4.14.5. That usually means your boot partition wasn't mounted when you updated, but the initramfs appears to be updated, so you probably have filesystem problems on /boot. Why do you still have 4.11.2-1-ARCH, and WTF is 4.9.70-1-ARCH? If you can't type anything in the initramfs, your config is screwed up there, too.

Did you mean I need regenerate /boot partition

The content in /boot is
EFI/
grub/
loader/
syslinux/

initramfs-linux-fallback.img
initramfs-linux.img
initramfs-linux-lts-fallback.img
initramfs-linux-lts.img
intel-ucode.img
vmlinuz-linux
vmlinuz-linux-lts

Last edited by jarvx (2017-12-19 05:52:51)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,729

Re: Arch cannnot start after rebooting emergency shell

I would start by reinstalling both of your kernels.

jarvx

Member

Registered: 2017-12-19

Posts: 7

Re: Arch cannnot start after rebooting emergency shell

I would start by reinstalling both of your kernels.

Okay 

Thank you so much.

flortsch

Member

From: Austria

Registered: 2015-07-21

Posts: 40

Website

Re: Arch cannnot start after rebooting emergency shell

Had the same problem a few days ago, where my desktop crashed while I was making a system upgrade (including kernel upgrade).
Simply booted into an Arch Live System, chrooted into my installation and reinstalled the kernel which solved the problem.

Last edited by flortsch (2017-12-19 11:42:21)