System Broken - udev fails to start

theta · 2021-10-30 05:23:32

I had recently broken my package database. I rebuilt it using Xyne’s script at

After that on case to case basis I have had to use the —overwrite functionality with PacMan and yay to upgrade my system. It has been working fine since about a month.

Yesterday after an upgrade my system seems to have had an issue with udev.

Now I am unable to even type with my keyboard in my emergency mode after reboot.

Since my keyboard was non functional in emergency mode I could only take a picture of the errors.

https://imagebin.ca/v/6KtZZxY3eiuj

I have a dual boot with windows installed. The hardware seems to be functioning well with my windows partition.

seth · 2021-10-30 07:12:07

Did you use the updated version in https://bbs.archlinux.org/viewtopic.php … 4#p1924194 ?

Boot a live system (eg. the install iso, actually prefereably that) (arch-)chroot into the installed system and check the package integrity

pacman -Qikk system systemd-libs

And maybe for all

pacman -Qikk

And you may want to re-install all packages to sanitize the system, https://wiki.archlinux.org/title/Pacman … dependency?

theta · 2021-10-30 10:48:22

I tried booting through a live medium. I had an old arch install medium (I believe the 2011 kernel). My laptop is about 5 yrs old. This should have booted.
This is what I got on booting.

Initial Boot ACPI Error

I have been ignoring these ACPI errors since the time I bought this laptop.

Post Initial Bootup Phase - Stuck in Loop

I have refined as my boot manager.

Windows on a different partition running fine.

Any suggestion?

I am thinking next to try the latest iso. But the old one should have at least booted.

seth · 2021-10-30 12:05:41

Windows on a different partition running fine.

3rd link below. Mandatory.

The ACPI errors are not your problem but the kernel oops and the timeouts when modprobe tries to load a module for a PCI device(s) - seems the USB.
Do you have other usb devices attached (except for the "old arch install medium")

I had an old arch install medium (I believe the 2011 kernel). My laptop is about 5 yrs old. This should have booted.

* Checks calendar
* Checks basic math
* looksup bc manpage
* % echo 2021-5 | bc => 2016
* % echo 2021-5-2011 | bc => 5
* Looksup basic logic… … processing … … you mean the kernel is 5 years older than the notebook?
*

theta · 2021-10-30 14:15:10

The second command

pacman -Quik

started giving a lot of warnings. I quit and issued a pacman -Syu

It appears that the database may have broken again.

When you say sanitise the system, what all are you referring to…
Just a system upgrade or… something else

seth · 2021-10-30 14:20:27

"-Qikk"…

And you may want to re-install all packages to sanitize the system, https://wiki.archlinux.org/title/Pacman … dependency

See the linked wiki entry, be sure to issue the proper parameters to pacman.
You will re-install all packages, whether there's an update or not. "pacman -Qikk" should™ not yell too many deviances afterwards (while some are normal)

theta · 2021-10-31 12:27:44

I issued a

pacman -Qnq | pacman -S -

As mentioned in the wiki.

1. For some reason every time I retry pacman re-downloads all the packages.

2. I got a lot of already exists in filesystem errors. Similar to when my database was corrupted.
I tried an overwrite for xscreensaver but that also failed.

Refer:

Long List of errors

seth · 2021-10-31 13:00:04

1. transient cache location or you're cleaning it?
https://wiki.archlinux.org/title/Pacman … kage_cache

pacman -Qnq | pacman -S --cachedir /path/to/some/storage/space -

2. Something went wrong during the dbase reconstruction, you somehow have the package list, but no mtree data
See https://wiki.archlinux.org/title/Pacman … l_database

tried an overwrite for xscreensaver

That's not a thing, --overwrite requires a file pattern to be overwritten.

theta · 2021-10-31 13:34:09

So should I repeat the entire process of regenerating the database or from some particular step for the mtree data?

Also I just realised my /var is on a different partition. Reseizerfs.

Until now I was running pacman in the chroot without the original /var mounted.

Maybe that’s causing more confusion for pacman.

Also once I chroot. It’s not possible to change the var?

[edit]

I mounted the var partition at the corresponding location before commencing chroot into the root directory.

Will update on result.

Last edited by theta (2021-10-31 13:44:21)

Arch Linux

#1 2021-10-30 05:23:32

System Broken - udev fails to start

#2 2021-10-30 07:12:07

Re: System Broken - udev fails to start

#3 2021-10-30 10:48:22

Re: System Broken - udev fails to start

#4 2021-10-30 12:05:41

Re: System Broken - udev fails to start

#5 2021-10-30 14:15:10

Re: System Broken - udev fails to start

#6 2021-10-30 14:20:27

Re: System Broken - udev fails to start

#7 2021-10-31 12:27:44

Re: System Broken - udev fails to start

#8 2021-10-31 13:00:04

Re: System Broken - udev fails to start

#9 2021-10-31 13:34:09

Re: System Broken - udev fails to start

Board footer