Not able to boot after pacman update was interrupted

General system Newbie
1

I was upgrading packages with sudo pacman -Syu, and my laptop’s battery died in between.
When I try to boot, it gets stuck on the screen shown below.

image
image663×884 73.4 KB

After this, it gets stuck on a blank screen with a blinking cursor at the top left.
I’m still pretty new to this, what should I do?

2

when batery died, can you recall what stage the command was at?
if it was just downloading the content understandable
but if it was applying proper upgrades to the packages and it died, then you have corrupted packages and looks like they are required to finish the booting system
which you could do a fresh instal but before that you will need to extract all the data so i recomend booting with a USB drive and extract all the importand data
and do a fresh install

thats all i can come to think off, but wait and see there might be a better solution than doing the whole reinstallment

3

You could try to repair the system from the live session.

Use your EnOS live usb and chroot into your system.

Depending on your filesystem, choose the appropriate instructions given in the following article:

https://discovery.endeavouros.com/system-rescue/arch-chroot/2022/12/

Once you are in the chroot, run the update command: pacman -Syu

If you get any error at any any step, post it here before doing anything else.

If all goes well, quit chroot by typing exit followed by enter.

Reboot the system.

2 Likes
4

I’m in chroot, but I don’t have wifi. Wifi works outside chroot.

I noticed my /etc/resolv.conf file is just has:

# Resolver configuration file.
# See resolv.conf(5) for details.
5

Normally when you use arch-chroot the /etc/resolv.conf should be available inside the chroot:

:eye: https://wiki.archlinux.org/title/Chroot#Using_arch-chroot

If it is not working copy the resolv.conf from the live session to its location inside chroot.

Or perhaps you could edit /etc/resolv.conf inside chroot and add something like:

nameserver 9.9.9.9
nameserver 8.8.8.8
nameserver 1.1.1.1

Also post:

lsblk -f

and

parted -l

6

Sorry, forgot to mention, I already tried editing the file, but I’m not able to,

It gives me this error in vim
"/etc/resolv.conf" E212: Can't open file for writing

also tried

echo "nameserver 8.8.8.8" > /etc/resolv.conf
bash: /etc/resolv.conf: File exists

lsblk -f
NAME        FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
loop0                                              
sda                                                
├─sda1                                             
└─sda2                               246.6G    11% /home
sdb                                                
├─sdb1                                             
└─sdb2                                             
nvme0n1                                            
├─nvme0n1p1                                        
├─nvme0n1p2                                        
├─nvme0n1p3                                        
├─nvme0n1p4                                        
├─nvme0n1p5                          510.7M     0% /boot/efi
└─nvme0n1p6                           26.1G    44% /


parted -l
Model: ATA WDC WD10SPZX-24Z (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size   File system  Name                  Flags
 1      1049kB  266GB  266GB  ntfs         Basic data partition  msftdata
 2      266GB   588GB  322GB  ext4


Model: WD My Passport 07A8 (scsi)
Disk /dev/sdb: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size   Type     File system  Flags
 2      2483MB  2608MB  125MB  primary  fat16        esp


Model: SAMSUNG MZVLB256HBHQ-000L2 (nvme)
Disk /dev/nvme0n1: 256GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size    File system  Name                          Flags
 1      1049kB  106MB  105MB   fat32        EFI system partition          boot, esp, no_automount
 2      106MB   123MB  16.8MB               Microsoft reserved partition  msftres, no_automount
 3      123MB   199GB  199GB   ntfs         Basic data partition          msftdata
 5      199GB   199GB  537MB   fat32                                      boot, esp
 6      199GB   255GB  56.2GB  ext4
 4      255GB   256GB  707MB   ntfs                                       hidden, diag, no_automount
1 Like
7

In the live session (outside chroot), open a terminal and run:

  1. su
  2. at the # prompt
    cp /etc/resolv.conf /mnt/etc/resolv.conf

Check if the connection works inside chroot

1 Like
8

su was asking for a password, so I did
sudo cp /etc/resolv.conf /mnt/etc/resolv.conf

I upgraded packages and it’s able to boot now, thanks a lot, appreciate your help!

Now I don’t need to change the resolv.conf file again right?

9

Glad to hear that you got the problem solved!

I shouldn’t think so if everything is working fine unless you want to make specific changes for the DNS queries.

And also, if you are satisfied with the outcome of the topic, please mark the relevant post leading to the solution as such. Doing so may help other users with similar problem to find the solution more easily.

2 Likes
10

Alright, thanks again

1 Like
11

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.