You are not logged in.

#26 2018-11-24 22:39:33

dicaiopolis
Member
Registered: 2010-07-21
Posts: 126

Re: [Solved] System broken after upgrading

seth wrote:

keyutils is at 1.6, I'd say the bogus db archieves spoil the db update, thus operating on dated versions.
Move away everything in /mnt/var/lib/pacman/sync/ and try again.

Moved away the files, as suggested. Now, I get:

https://ptpb.pw/BuZF

Offline

#27 2018-11-24 22:55:04

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 78,743

Re: [Solved] System broken after upgrading

Well, there seem quite some compromised packages.
Check all broken files w/ "pacman -Qo" and re-install the corresponding packages.

@loqs, makes sense (I missed the "no --sysroot" part)

Online

#28 2018-11-25 04:30:01

dicaiopolis
Member
Registered: 2010-07-21
Posts: 126

Re: [Solved] System broken after upgrading

seth wrote:

Well, there seem quite some compromised packages.
Check all broken files w/ "pacman -Qo" and re-install the corresponding packages.

@loqs, makes sense (I missed the "no --sysroot" part)

Re-installed the broken packages, but when I run 'pacman -Qo' I still get this message: https://ptpb.pw/w-ve.jpg

When I try to boot, I'm still stuck in "emergency mode" and now have no network connection anymore. So I can't send "journalctl -xb" to ptpb.pw Any way to export "journalctl -xb" to a file so that I would be able to upload it to ptpb.pw?

Please see this: https://ptpb.pw/YMVe.jpg

Any ideas?

Last edited by dicaiopolis (2018-11-25 04:49:37)

Offline

#29 2018-11-25 09:14:36

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 78,743

Re: [Solved] System broken after upgrading

The -Qkk output is "normal" and benign, those files are expected to change.
About the emergency mode: did you forget to mount the /boot partition into /mnt when running the updates? (The reason for the emergency mode isn't on the pictured part of the buffer)

Online

#30 2018-11-25 11:07:30

dicaiopolis
Member
Registered: 2010-07-21
Posts: 126

Re: [Solved] System broken after upgrading

seth wrote:

did you forget to mount the /boot partition into /mnt when running the updates? (The reason for the emergency mode isn't on the pictured part of the buffer)

Exactly, but after I mounted the boot partition and installed Linux package again, but couldn't solve the problem. Any ideas?

Offline

#31 2018-11-25 13:27:58

dicaiopolis
Member
Registered: 2010-07-21
Posts: 126

Re: [Solved] System broken after upgrading

I'd like to export the content of "journalctl -xb" to a file so that I can post it here. How could I do that?

Offline

#32 2018-11-25 14:13:24

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 78,743

Re: [Solved] System broken after upgrading

By redirecting it, bash style.
About the "I mounted the boot partition and installed Linux package again": how exactly? Using arch-chroot or --sysroot? And did you mount it at /boot or at /mnt/boot?
Do the timestamps on the /boot partition suggest up-to-date files?

Online

#33 2018-11-25 14:25:11

dicaiopolis
Member
Registered: 2010-07-21
Posts: 126

Re: [Solved] System broken after upgrading

Here's the content of 'journalctl -xb.
https://ptpb.pw/IpmZ.txt

Do you have any idea on how to fix this problem?

Thanks.

Offline

#34 2018-11-25 14:26:36

dicaiopolis
Member
Registered: 2010-07-21
Posts: 126

Re: [Solved] System broken after upgrading

seth wrote:

By redirecting it, bash style.
About the "I mounted the boot partition and installed Linux package again": how exactly? Using arch-chroot or --sysroot? And did you mount it at /boot or at /mnt/boot?
Do the timestamps on the /boot partition suggest up-to-date files?

using arch-chroot. First I mounted at /mnt/boot. I ended in emergency mode. Tried to fix mounting it at /boot. No results.
Timestamps show up-to-date files (11/25).

Last edited by dicaiopolis (2018-11-25 14:32:30)

Offline

#35 2018-11-25 14:39:11

dicaiopolis
Member
Registered: 2010-07-21
Posts: 126

Re: [Solved] System broken after upgrading

Hi there,

I could finally boot successfully after commenting the following lines in my fstab:

# /dev/sda2
UUID=6181af6a-94ff-4151-b7c7-442a6adb3110	/         	ext4      	rw,relatime,data=ordered	0 1

# /dev/sda1
UUID=3564-29EA      	/boot     	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro	0 2

# /dev/sda3
UUID=013931d0-98a4-4714-bfaa-76e43834596d	/home     	ext4      	rw,relatime,data=ordered	0 2

# /dev/sda4
UUID=ad0166fc-5789-446d-a916-9d55f567e9b7	none      	swap      	defaults,pri=-2	0 0

# /dev/sdb2
#UUID=90B5-B36F	/media/C     	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro	0 2

# /dev/sdb4
#UUID=F090BA4090BA0D5A	/media/D     	ntfs-3g      	rw,relatime,data=ordered	0 2

# /dev/sdc2

#UUID=B4D0E24CD0E21500	/media/F     	ntfs-3g      	rw,relatime,data=ordered	0 2

# /dev/sdc3
#UUID=8e4fece7-b4a5-4572-a69b-2ffa8d587e32	/media/Linux-Dados     	ext4      	rw,relatime,data=ordered	0 2

#/home/andre/Iso/Tlg.iso /media/Tlg 	iso9660  	user,loop  			0 	0
#/home/andre/Iso/Phi5.iso /media/Phi 	iso9660  	user,loop  			0 	0
#/home/andre/Iso/Il_Verbo_Greco.iso /media/VerboGreco 	iso9660  	user,loop  			0 	0

So we have a problem with mounting some partitions? Any ideas?

Offline

#36 2018-11-25 14:53:44

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 78,743

Re: [Solved] System broken after upgrading

uname -a
pacman -Qs linux
modprobe vfat

Online

#37 2018-11-25 14:59:42

dicaiopolis
Member
Registered: 2010-07-21
Posts: 126

Re: [Solved] System broken after upgrading

Solved. fsck /dev/sdc3 did it.
Thanks a lot everybody who helped me to recover the system.

Offline

Board footer

Powered by FluxBB