You are not logged in.
Hi there,
My computer is not booting. I do not know what caused the issue, but what happened before is that I fell asleep while downloading updates, the computer was frozen when I tried to use it the following day, and I forced poweroff it. When I powered it on again, it wasn't booting.
I am using a Dell XPS 13 and there is no dual boot, I have only Arch installed on this computer.
I am getting the following messages:
Error loading \vmlinuz-linux: Not Found
Failed to execute Arch Linux (\vmlinuz-linux): Not Found
Failed to execute EFI Default Loader (\EFI\Boot\bootx64.efi): Not FoundI found an old post here with a similar problem and the following solution:
mount /dev/X /mnt
mount /dev/Y /mnt/boot
arch-chroot
pacman -S linux
pacman -S mkinitcpioLink to the post: https://bbs.archlinux.org/viewtopic.php?id=250486
So I tried to use this with an install media, but it didn't work because it failed to mount one of the partitions.
Using the fdisk -l showed me something like this:
/dev/sda1 Boot = * Type = Empty
/dev/sda2 Boot = (nothing here) Type = EFI (FAT-12/16/32)Sorry about not posting the full output, but I can not copy it here. I think it is understandable.
So I concluded that /dev/sda1 is the boot and tried the folowing:
mount /dev/sda2 /mnt
mount /dev/sda1 /mnt/bootThe problem is that I could mount sda2, but could not mount sda1.
After "mount /dev/sda1 /mnt/boot" I got the following message:
mount: /mnt/boot: mount point does not exist.I tried something like "mkdir /mnt/boot" and it seemed to make a difference, but again when I tried to mount it again it says that /mnt/boot is ready-only (or something like this).
This is where I got stucked.
I guess this problem is due to /dev/sda1 being "Type = Empty", but I don't what to do about it.
Is this mount issue fixable? Or is there another way of solving this boot issue?
Offline
When you boot from the install disk, do you have Internet access?
If so, you should be able to use a pastebin-like client to share your console output.
Please post the results of
fdisk -l
lsblk -fCheers,
"Before Enlightenment chop wood, carry water. After Enlightenment chop wood, carry water." -- Zen proverb
Offline
Hi Dakota,
Thanks a lot for your attention.
Here it goes the outputs:
fdisk -l
Disk /dev/nvme0n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: PC401 NVMe SK hynix 512GB
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: A01D54CB-983C-4CA8-B06C-6125709387A3
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 2099199 2097152 1G EFI System
/dev/nvme0n1p2 2099200 6293503 4194304 2G Linux swap
/dev/nvme0n1p3 6293504 69208063 62914560 30G Linux filesystem
/dev/nvme0n1p4 69208064 1000215182 931007119 443.9G Linux filesystem
Disk /dev/sda: 7.45 GiB, 8002732032 bytes, 15630336 sectors
Disk model: Cruzer Fit
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x962fa445
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 64 1878015 1877952 917M 0 Empty
/dev/sda2 1878016 1908735 30720 15M ef EFI (FAT-12/16/32)
Disk /dev/loop0: 766.51 MiB, 803741696 bytes, 1569808 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 byteslsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
loop0 squashfs 4.0 0 100% /run/archiso/airootfs
sda iso9660 Joliet Extension ARCH_202402 2024-02-01-12-07-52-00
├─sda1 iso9660 Joliet Extension ARCH_202402 2024-02-01-12-07-52-00
└─sda2 vfat FAT16 ARCHISO_EFI 9C7A-9A67
nvme0n1
├─nvme0n1p1 vfat FAT32 A4F2-E881
├─nvme0n1p2 swap 1 2420be6c-512e-4178-8dac-3bc3776fa4a7
├─nvme0n1p3 ext4 1.0 40e362fa-61cb-4bdd-9c14-011bd295a9c6
└─nvme0n1p4 ext4 1.0 880ab5d7-0aca-400e-8662-1f2f50dea620 Any ideia on what can I do?
Cheers!
Offline
I thought that I solved the issue...
This what worked:
mount /dev/nvme0n1p3 /mnt
mount /dev/nvme0n1p1 /mnt/boot
arch-chroot /mnt
pacman -S linux
pacman -S mkinitcpioI was on the right way, it was just a matter of choosing the right partitions to mount.
But, when the system came back, resolution had changed and when I tried to fix it the system configuration crashed. I tried to update the system, and KDE crashed.
I had to poweroff by holding the power button. Back to where it all started.
When I turned to computer on again, it didn't boot again...
So what I did was to repeat the process and hope for the best...
But after mounting and trying "pacman -S linux" again, it is giving the following message:
error: failed to init transaction (unable to lock database)
error: could not lock database: File exists
If you' re sure a package manager is not already
running, you can remove /var/lib/pacman/db.lckI tried to remove this file and it said it does not exist.
Is there solution to this?
Offline
mount /dev/nvme0n1p3 /mnt
mount /dev/nvme0n1p1 /mnt/boot
arch-chroot /mntThat part is correct.
Once you have chrooted, you'll need to update your system, and (before you reboot) reinstall the bootloader and/or check that the bootloader is installed correctly.
1. Which boot loader are you using?
2. As far as removing the db lock file, what was the exact command you typed and what was the exact error message?
Cheers,
Edit -- we'll also need to check for broken packages, but first get the lock file removed.
To check for broken packages
sudo LC_ALL=C pacman -Qkk | grep -v ', 0 altered files'Last edited by dakota (2024-02-09 06:57:35)
"Before Enlightenment chop wood, carry water. After Enlightenment chop wood, carry water." -- Zen proverb
Offline