[SOLVED]Power out during kernel upgrade, can't boot...

Bilskirnir3124 · 2022-08-31 22:42:33

So, this is a bit of a mess and some negligence on my part.

I'm running Linux zen as my main kernel. I have standard Linux as my back-up kernel. I installed using the archinstall script from the standard ISO. I did select disk encryption when setting my system up, again, through the archinstall script. I was updating my system last night on my laptop. I'd forgotten to bring my power cable with me, but figured it would be fine. There were just a bunch of Haskell upgrades as far as I could see. However, it started to generate DKMS modules from a kernel upgrade I'd missed. This is quite CPU intensive and drained my laptop's battery very quickly. It attempted to hibernate. When I got home and got it on power again I received the message:

loading Linux linux-zen
error file '/vmlinuz-linux-zen' not found
loading initial ramdisk
error you need to load the kernel first

I then attempted to boot into an Arch USB disk following the instruction from the wiki using the latest 2022.08.05 iso. I used rufus 3.20 from my Windows gaming computer to write the disk. I can boot the install medium. I just can't figure out what to do from there. The wiki's pacman article that I'm chasing down for help states to run:

mount /mnt
mount /mnt/boot

Then to chroot using

arch-chroot

However I can not mount /mnt. It returns

mount: /mnt: can't find in /etc/fstab.

I attempted to mount the partitions intermediately instead with mount returning some variation of

mount: /dev/sda1: can't find in /etc/sda1

Running

lsblk -f

returns the drive I'm attempting to mount however, I still can not mount any of the partitions listed there. I attempted to mount via UUID. I receive a variation of the same message.

mount: <UUID>: can't find mount source UUID="UUID" in /etc/fstab.

I've also attempted to use systemd-mount to get into the drive with similar results.

systemd-mount /mnt
invalid file type: /mnt

Attempting to mount /dev/sda1 is successful however I still can not mount /mnt to run arch-chroot. Nor can I figure out how to get into /dev/sda1 to ensure that the points I'm looking for (/mnt and /mnt/boot) exist.

I'm at a bit of dead end with my own knowledge at this point. I would very much appreciate any help that can be offered to get this system up and running again. I'll be happy to provide anymore details you may require to that end. Thanks.

Last edited by Bilskirnir3124 (2022-09-01 04:44:21)

Scimmia · 2022-08-31 23:06:18

man mount

Seriously, you skipped learning anything about your system by using archinstall, and now you're paying for it. Start reading man pages and the wiki (even the installation guide), figure out how partitions work.

Bilskirnir3124 · 2022-08-31 23:28:41

Scimmia wrote:

man mount
Seriously, you skipped learning anything about your system by using archinstall, and now you're paying for it. Start reading man pages and the wiki (even the installation guide), figure out how partitions work.

I've manually installed Arch before. I just didn't feel like taking the extra time to manually type out all of the commands this time. That said, I haven't had to use the mount command in quite some time and was incorrectly targeting it. I'll fully own being an intermediate user. The problem is the disk encryption as near as I can tell. Running

mount /dev/sda2 /mnt

returns

mount: /mnt: unknown filesystem type 'crypto_LUKS'.

Attempting

cryptsetup open --type luks /dev/sda1 crypto_LUKS

allows me to unlock the drive, but I can not then mount it.

I understand there are some gaps in my knowledge. I just need to know what they are so that I can fill them in and get this computer running again. I'd like to know how to fix these problems so that I don't have to resort to, "let's nuke this install and start over," in the future.

Thanks for the help.

Scimmia · 2022-08-31 23:30:15

When you open the container, it should create block devices under /dev/mapper/. That's what you need to mount.

Bilskirnir3124 · 2022-09-01 00:08:35

Scimmia wrote:

When you open the container, it should create block devices under /dev/mapper/. That's what you need to mount.

Thanks. I'll take a stab at that and report back.

Bilskirnir3124 · 2022-09-01 00:26:31

So, I was able to get into the drive. I was able to run arch-chroot afterwards as well. However, this did not resolve the issue.

I ran

arch-chroot /mnt
pacman -Syu mkinitcpio systemd linux linux-zen

It ran pacman and installed everything successfully.

I then ran

exit
umount /mnt/boot
reboot

When attempting to reboot however, it returned

loading Linux linux-zen
error file '/vmlinuz-linux-zen' not found
loading initial ramdisk
error you need to load the kernel first

and

loading Linux linux
error file '/vmlinuz-linux' not found
loading initial ramdisk
error you need to load the kernel first

I am unsure how to proceed from here.

Scimmia · 2022-09-01 00:51:11

It sounds like your /boot partition wasn't mounted when you reinstalled them.

Bilskirnir3124 · 2022-09-01 02:03:42

Scimmia wrote:

It sounds like your /boot partition wasn't mounted when you reinstalled them.

So, I went back and made sure that I arch-chroot into /mnt/boot. I ran it again. I also reinstalled nvidia-dkms again just to make make sure I had a working graphics driver module. Still no luck. I'm not sure if maybe it isn't a grub problem at this point.

Scimmia · 2022-09-01 02:27:46

With the same error? Does the file actually exist on root of the boot partition?

cfr · 2022-09-01 03:27:54

Bilskirnir3124 wrote:

So, I went back and made sure that I arch-chroot into /mnt/boot.

Is this a typo or did you really do this? You want to make sure your root partition is mounted at /mnt and your boot partition is mounted at /mnt/boot and then arch-chroot into /mnt.

Bilskirnir3124 · 2022-09-01 03:46:05

Scimmia wrote:

With the same error? Does the file actually exist on root of the boot partition?

It appears so. When I arch-chroot into /mnt/boot on /dev/sda2 and run

pacman -Qs linux

I see linux 5.19.5.arch1-1, linux-api-headers 5.19.5.arch1-1, linux-zen 5.19.5.arch1-1, and linux-zen-headers 5.19.5.arch1-1 installed. I don't know that this means they're installed in root though. Everything it returns is listed in the form local/{packagename}.

Edited for clarity.

Last edited by Bilskirnir3124 (2022-09-01 04:05:21)

Bilskirnir3124 · 2022-09-01 04:07:12

cfr wrote:

Bilskirnir3124 wrote:
So, I went back and made sure that I arch-chroot into /mnt/boot.
Is this a typo or did you really do this? You want to make sure your root partition is mounted at /mnt and your boot partition is mounted at /mnt/boot and then arch-chroot into /mnt.

I did not see this reply. Sorry. I did do it that way. Thanks for letting me know about that. I'll do it like that and see if I can get in that way. Thanks.

Bilskirnir3124 · 2022-09-01 04:42:07

CFR, this fixed it. Thank you very much for the help. I'll doubtless need to clean up whatever damage I did flailing around in chroot, but I can get back into the desktop again. Thanks again for the help.

Arch Linux

#1 2022-08-31 22:42:33

[SOLVED]Power out during kernel upgrade, can't boot...

#2 2022-08-31 23:06:18

Re: [SOLVED]Power out during kernel upgrade, can't boot...

#3 2022-08-31 23:28:41

Re: [SOLVED]Power out during kernel upgrade, can't boot...

#4 2022-08-31 23:30:15

Re: [SOLVED]Power out during kernel upgrade, can't boot...

#5 2022-09-01 00:08:35

Re: [SOLVED]Power out during kernel upgrade, can't boot...

#6 2022-09-01 00:26:31

Re: [SOLVED]Power out during kernel upgrade, can't boot...

#7 2022-09-01 00:51:11

Re: [SOLVED]Power out during kernel upgrade, can't boot...

#8 2022-09-01 02:03:42

Re: [SOLVED]Power out during kernel upgrade, can't boot...

#9 2022-09-01 02:27:46

Re: [SOLVED]Power out during kernel upgrade, can't boot...

#10 2022-09-01 03:27:54

Re: [SOLVED]Power out during kernel upgrade, can't boot...

#11 2022-09-01 03:46:05

Re: [SOLVED]Power out during kernel upgrade, can't boot...

#12 2022-09-01 04:07:12

Re: [SOLVED]Power out during kernel upgrade, can't boot...

#13 2022-09-01 04:42:07

Re: [SOLVED]Power out during kernel upgrade, can't boot...

Board footer