Arch Linux

etc

Member

Registered: 2023-02-28

Posts: 16

Re: [SOLVED] Compromised Laptop after Windows Update

uname -a

You seem to be booting a rather old kernel - maybe from the install iso?
You should™ not have to run mkinitcpio explicitly, installing the kernel would do that for the new kernel.
You can in doubt specify a kernel w/ the "-k" option.

Yes I realised the kernel defaulted to an older version, I then did

ls -l /lib/modules

to identify the kernel and used

mkinitcpio --kernel 6.2.2-arch1-1

according to the results. The gave me:

==> Starting dry run: 6.2.2-arch1-1
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Dry run complete, use -g IMAGE to generate a real image

2 warnings are omitted from the curl:

Possibly missing firmware for module: xhci_pci

and

consolefont: no font found in configuration

but I don't think these matter.

Do I now do

mkinitcpio -g /boot/initramfs-linux.img -k /boot/vmlinuz-linux

according to https://man.archlinux.org/man/mkinitcpio.8.en?

uname -a gives:

Linux archiso 6.1.8-arch1-1 #1 SMP PREEMPT_DYNAMIC Tue, 24 Jan 2023 21:07:04 +0000 x86_64 GNU/Linux

Last edited by etc (2023-03-03 21:59:37)

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 76,358

Re: [SOLVED] Compromised Laptop after Windows Update

Do I now do

You can, but again: (re-)installing the kernel should™ have generated an image anyway.
Check the timestamps on /boot/initramfs-*

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

etc

Member

Registered: 2023-02-28

Posts: 16

Re: [SOLVED] Compromised Laptop after Windows Update

Do I now do

You can, but again: (re-)installing the kernel should™ have generated an image anyway.
Check the timestamps on /boot/initramfs-*

The timestamps are from today, so that should be good. Arch still doesn't boot properly though. It takes a while and then I get the following:

Timed out waiting for device /dev/disk/bv-uuid/DA4B-C681.

and messages for failed dependencies:

Dependency failed for File System Check on /dev/disk/bv-uuid/DA4B-C681.

Dependency failed for /efi.

Dependency failed for Local File Systems.

leading me into emergency mode.

Last edited by etc (2023-03-03 22:15:44)

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 76,358

Re: [SOLVED] Compromised Laptop after Windows Update

You still reference the old /efi UUID in fstab?

lsblk -f

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

etc

Member

Registered: 2023-02-28

Posts: 16

Re: [SOLVED] Compromised Laptop after Windows Update

Ah!

You still reference the old /efi UUID in fstab?

lsblk -f

gives me

NAME        FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
loop0                                              
sda                                                
├─sda1                                             
└─sda2                                             
nvme0n1                                            
├─nvme0n1p1                           64.6M    33% /efi
├─nvme0n1p2                                        
├─nvme0n1p3                                        
└─nvme0n1p4                           75.3G    17% /

But I feel like you wanted me to find the UUID which for some reason isn't detailed here, so I did blkid

/dev/nvme0n1p3: BLOCK_SIZE="512" UUID="84AA4D0CAA4CFC64" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="e26b7f2f-9280-4d8d-b75f-0a72895d4c09"
/dev/sda1: BLOCK_SIZE="2048" UUID="2023-02-01-09-09-31-00" LABEL="ARCH_202302" TYPE="iso9660" PARTUUID="bdeca99d-01"
/dev/sda2: SEC_TYPE="msdos" LABEL_FATBOOT="ARCHISO_EFI" LABEL="ARCHISO_EFI" UUID="CA18-653E" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="bdeca99d-02"
/dev/nvme0n1p1: UUID="FE7B-A6AB" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="ce1bb1ad-5bb3-45a9-9c27-8f27af2fe177"
/dev/nvme0n1p4: UUID="03601300-763d-48bd-8fe7-26118b9bb4e6" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="d4597f78-5078-5a41-8423-96b3ee942e1e"
/dev/loop0: TYPE="squashfs"
/dev/nvme0n1p2: PARTLABEL="Microsoft reserved partition" PARTUUID="e3c80103-37c5-4871-9940-0cb8619c0e23"

And the fstab references a different UUID for the esp, namely the aforementioned DA4B-C681. I presume I change this now to FE7B-A6AB?

Edit: That worked. Now I just need to include Windows into GRUB.

Edit 2: All done, laptop saved. Thank you seth and d.ALT for your guidance!

Last edited by etc (2023-03-03 23:14:03)