You are not logged in.

#26 2023-11-16 22:54:23

korimitsu
Member
Registered: 2016-08-14
Posts: 137

Re: [Solved] Error preparing initrd: Not Found after today update

After last updates I'm getting the same error "not upgraded exists in filesystem" and
==> WARNING: Preset file '/etc/mkinitcpio.d/linux-lts.preset' is empty or does not contain any presets.
==> WARNING: Preset file '/etc/mkinitcpio.d/linux.preset' is empty or does not contain any presets.

Could you please stop breaking the updates? Also distros based on Arch are having this issue as well:
https://forum.garudalinux.org/t/constan … ting/21201

Offline

#27 2023-11-17 00:50:03

Scimmia
Fellow
Registered: 2012-09-01
Posts: 11,966

Re: [Solved] Error preparing initrd: Not Found after today update

Linking to a completely different issue that has nothing to do with Arch? Come on now.

Filesystem issues are not an Arch issue, either.

Online

#28 2023-11-17 07:37:36

seth
Member
Registered: 2012-09-03
Posts: 57,289

Re: [Solved] Error preparing initrd: Not Found after today update

seth wrote:

=> Unless you're aware of "I did stupid things in the past…" check the overall filesystem integrity and https://wiki.archlinux.org/title/SMART
The "overall health status: passed" there is useless. If unsure post the output of "smartctl -a" for the drive.
Until you actually positively know that the disk is ok, the smart move is to have a backup of the valuable data (everything you cannot download from the internet again) NOW.

So you didn't?

Offline

#29 2023-11-17 21:16:44

korimitsu
Member
Registered: 2016-08-14
Posts: 137

Re: [Solved] Error preparing initrd: Not Found after today update

Scimmia wrote:

Linking to a completely different issue that has nothing to do with Arch? Come on now.

Filesystem issues are not an Arch issue, either.

The issue was caused exactly by the kernel upgrade. There's something wrong with the Arch kernel:

$ pacman -Q | grep linux
archlinux-appstream-data 20231010-1
archlinux-keyring 20231113-1
lib32-util-linux 2.39.2-1
linux 6.6.1.arch1-1
linux-api-headers 6.4-1
linux-firmware 20231030.2b304bfe-1
linux-firmware-whence 20231030.2b304bfe-1
linux-headers 6.6.1.arch1-1
linux-lts 6.1.62-1
linux-lts-headers 6.1.62-1
linuxtv-dvb-apps 1505-5
mips-linux-gnu-binutils 2.39-1
util-linux 2.39.2-2
util-linux-libs 2.39.2-2
zfs-linux-git 2.2.99.r185.g0527774066.k6.5.9-1
seth wrote:
seth wrote:

=> Unless you're aware of "I did stupid things in the past…" check the overall filesystem integrity and https://wiki.archlinux.org/title/SMART
The "overall health status: passed" there is useless. If unsure post the output of "smartctl -a" for the drive.
Until you actually positively know that the disk is ok, the smart move is to have a backup of the valuable data (everything you cannot download from the internet again) NOW.

So you didn't?

This is the current value:

smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.6.1-arch1-1] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, [url=http://www.smartmontools.org]www.smartmontools.org[/url]

=== START OF INFORMATION SECTION ===
Model Family:     SandForce Driven SSDs
Device Model:     
Serial Number:    
Firmware Version: 
User Capacity:    1,024,209,543,168 bytes [1.02 TB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      < 1.8 inches
TRIM Command:     Available
Device is:        In smartctl database 7.3/5528
ATA Version is:   ACS-4 (minor revision not indicated)
SATA Version is:  SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Fri Nov 17 10:11:45 2023
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever
					been run.
Total time to complete Offline
data collection: 		(65535) seconds.
Offline data collection
capabilities: 			 (0x79) SMART execute Offline immediate.
					No Auto Offline data collection support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 (  30) minutes.
Conveyance self-test routine
recommended polling time: 	 (   6) minutes.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   050    Pre-fail  Always       -       0/0
  5 Retired_Block_Count     0x0013   100   100   050    Pre-fail  Always       -       0
  9 Power_On_Hours_and_Msec 0x0012   100   100   000    Old_age   Always       -       562h+00m+00.000s
 12 Power_Cycle_Count       0x0012   100   100   000    Old_age   Always       -       456
162 Unknown_SandForce_Attr  0x0003   100   100   000    Pre-fail  Always       -       19
170 Reserve_Block_Count     0x0002   100   100   000    Old_age   Always       -       121
172 Erase_Fail_Count        0x0032   100   100   000    Old_age   Always       -       0
173 Unknown_SandForce_Attr  0x0000   100   100   000    Old_age   Offline      -       327697
174 Unexpect_Power_Loss_Ct  0x0012   100   100   000    Old_age   Always       -       435
181 Program_Fail_Count      0x0012   100   100   000    Old_age   Always       -       0
187 Reported_Uncorrect      0x0012   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0012   100   100   000    Old_age   Always       -       435
194 Temperature_Celsius     0x0023   067   067   000    Pre-fail  Always       -       33
196 Reallocated_Event_Count 0x0000   100   100   000    Old_age   Offline      -       0
218 Unknown_SandForce_Attr  0x0000   100   100   000    Old_age   Offline      -       0
231 SSD_Life_Left           0x0013   100   100   000    Pre-fail  Always       -       99
241 Lifetime_Writes_GiB     0x0012   100   100   000    Old_age   Always       -       3674
242 Lifetime_Reads_GiB      0x0012   100   100   000    Old_age   Always       -       12696

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

SMART Selective self-test log data structure revision number 0
Note: revision number not 1 implies that no selective self-test has ever been run
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

The above only provides legacy SMART information - try 'smartctl -x' for more

Offline

#30 2023-11-17 21:56:49

seth
Member
Registered: 2012-09-03
Posts: 57,289

Re: [Solved] Error preparing initrd: Not Found after today update

The issue was caused exactly by the kernel upgrade. There's something wrong with the Arch kernel:

No.
The file is written by the mkinitcpio hook ONCE and then left alone.
You previously had MASSIVE filesystem corruption and there're 435 unexpected power losses.

This is either down to those power losses of overaggressive (continuous) trimming - but it is a problem of your system, not the update.
The update merely exposes that the file previously was nuked.
Let's see whether there's more corruption.

sudo LC_ALL=C pacman -Qkk | grep -v ', 0 altered files'

You can use https://wiki.archlinux.org/title/Audit_ … ies_access to monitor access to the file and in any event, before running (kernel) updates, check its contents.

Edit:

Model Family:     SandForce Driven SSDs
Device Model:     
Serial Number:    
Firmware Version: 
User Capacity:    1,024,209,543,168 bytes [1.02 TB]

Did you clear those values or don't they show up?
(I wanted to check the model for systematic issues…)

Last edited by seth (2023-11-17 22:05:45)

Offline

#31 2023-11-18 15:01:29

korimitsu
Member
Registered: 2016-08-14
Posts: 137

Re: [Solved] Error preparing initrd: Not Found after today update

seth wrote:

(I wanted to check the model for systematic issues…)

Yes I've removed the serial number, here's the rest:

=== START OF INFORMATION SECTION ===
Model Family:     SandForce Driven SSDs
Device Model:     Corsair Voyager GTX
Firmware Version: SBFM61.5

The unexpected power losses could be due to nvidia or vmware workstation proprietary driver, I notice that keeps waiting several minutes to shutdown sometimes. I don't notice that if Arch is inside Virtualbox, which shuts down instantly.
how can I see the shut down log from previous poweroff so see what took so much time?

Altered files:

$ sudo LC_ALL=C pacman -Qkk | grep -v ', 0 altered files'
backup file: filesystem: /etc/fstab (Modification time mismatch)
backup file: filesystem: /etc/fstab (Size mismatch)
backup file: filesystem: /etc/fstab (MD5 checksum mismatch)
backup file: filesystem: /etc/fstab (SHA256 checksum mismatch)
backup file: filesystem: /etc/group (Modification time mismatch)
backup file: filesystem: /etc/group (Size mismatch)
backup file: filesystem: /etc/group (MD5 checksum mismatch)
backup file: filesystem: /etc/group (SHA256 checksum mismatch)
backup file: filesystem: /etc/gshadow (Modification time mismatch)
backup file: filesystem: /etc/gshadow (Size mismatch)
backup file: filesystem: /etc/gshadow (MD5 checksum mismatch)
backup file: filesystem: /etc/gshadow (SHA256 checksum mismatch)
backup file: filesystem: /etc/passwd (Modification time mismatch)
backup file: filesystem: /etc/passwd (Size mismatch)
backup file: filesystem: /etc/passwd (MD5 checksum mismatch)
backup file: filesystem: /etc/passwd (SHA256 checksum mismatch)
backup file: filesystem: /etc/resolv.conf (Modification time mismatch)
backup file: filesystem: /etc/resolv.conf (Size mismatch)
backup file: filesystem: /etc/resolv.conf (MD5 checksum mismatch)
backup file: filesystem: /etc/resolv.conf (SHA256 checksum mismatch)
backup file: filesystem: /etc/shadow (Modification time mismatch)
backup file: filesystem: /etc/shadow (Size mismatch)
backup file: filesystem: /etc/shadow (MD5 checksum mismatch)
backup file: filesystem: /etc/shadow (SHA256 checksum mismatch)
backup file: filesystem: /etc/shells (Modification time mismatch)
backup file: filesystem: /etc/shells (Size mismatch)
backup file: filesystem: /etc/shells (MD5 checksum mismatch)
backup file: filesystem: /etc/shells (SHA256 checksum mismatch)
backup file: filesystem: /etc/subgid (Modification time mismatch)
backup file: filesystem: /etc/subgid (Size mismatch)
backup file: filesystem: /etc/subgid (MD5 checksum mismatch)
backup file: filesystem: /etc/subgid (SHA256 checksum mismatch)
backup file: filesystem: /etc/subuid (Modification time mismatch)
backup file: filesystem: /etc/subuid (Size mismatch)
backup file: filesystem: /etc/subuid (MD5 checksum mismatch)
backup file: filesystem: /etc/subuid (SHA256 checksum mismatch)
filesystem: 120 total files, 1 altered file
backup file: glibc: /etc/locale.gen (Modification time mismatch)
backup file: glibc: /etc/locale.gen (Size mismatch)
backup file: glibc: /etc/locale.gen (MD5 checksum mismatch)
backup file: glibc: /etc/locale.gen (SHA256 checksum mismatch)
intel-ucode: 7 total files, 1 altered file
java-runtime-common: 21 total files, 2 altered files
libutempter: 20 total files, 1 altered file
backup file: libvirt: /etc/libvirt/nwfilter/allow-arp.xml (Modification time mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/allow-arp.xml (Size mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/allow-arp.xml (MD5 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/allow-arp.xml (SHA256 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/allow-dhcp-server.xml (Modification time mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/allow-dhcp-server.xml (Size mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/allow-dhcp-server.xml (MD5 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/allow-dhcp-server.xml (SHA256 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/allow-dhcp.xml (Modification time mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/allow-dhcp.xml (Size mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/allow-dhcp.xml (MD5 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/allow-dhcp.xml (SHA256 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/allow-dhcpv6-server.xml (Modification time mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/allow-dhcpv6-server.xml (Size mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/allow-dhcpv6-server.xml (MD5 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/allow-dhcpv6-server.xml (SHA256 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/allow-dhcpv6.xml (Modification time mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/allow-dhcpv6.xml (Size mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/allow-dhcpv6.xml (MD5 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/allow-dhcpv6.xml (SHA256 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/allow-incoming-ipv4.xml (Modification time mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/allow-incoming-ipv4.xml (Size mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/allow-incoming-ipv4.xml (MD5 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/allow-incoming-ipv4.xml (SHA256 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/allow-incoming-ipv6.xml (Modification time mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/allow-incoming-ipv6.xml (Size mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/allow-incoming-ipv6.xml (MD5 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/allow-incoming-ipv6.xml (SHA256 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/allow-ipv4.xml (Modification time mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/allow-ipv4.xml (Size mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/allow-ipv4.xml (MD5 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/allow-ipv4.xml (SHA256 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/allow-ipv6.xml (Modification time mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/allow-ipv6.xml (Size mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/allow-ipv6.xml (MD5 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/allow-ipv6.xml (SHA256 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/clean-traffic-gateway.xml (Modification time mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/clean-traffic-gateway.xml (Size mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/clean-traffic-gateway.xml (MD5 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/clean-traffic-gateway.xml (SHA256 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/clean-traffic.xml (Modification time mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/clean-traffic.xml (Size mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/clean-traffic.xml (MD5 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/clean-traffic.xml (SHA256 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-arp-ip-spoofing.xml (Modification time mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-arp-ip-spoofing.xml (Size mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-arp-ip-spoofing.xml (MD5 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-arp-ip-spoofing.xml (SHA256 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-arp-mac-spoofing.xml (Modification time mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-arp-mac-spoofing.xml (Size mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-arp-mac-spoofing.xml (MD5 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-arp-mac-spoofing.xml (SHA256 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-arp-spoofing.xml (Modification time mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-arp-spoofing.xml (Size mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-arp-spoofing.xml (MD5 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-arp-spoofing.xml (SHA256 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-ip-multicast.xml (Modification time mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-ip-multicast.xml (Size mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-ip-multicast.xml (MD5 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-ip-multicast.xml (SHA256 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-ip-spoofing.xml (Modification time mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-ip-spoofing.xml (Size mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-ip-spoofing.xml (MD5 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-ip-spoofing.xml (SHA256 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-ipv6-multicast.xml (Modification time mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-ipv6-multicast.xml (Size mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-ipv6-multicast.xml (MD5 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-ipv6-multicast.xml (SHA256 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-ipv6-spoofing.xml (Modification time mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-ipv6-spoofing.xml (Size mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-ipv6-spoofing.xml (MD5 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-ipv6-spoofing.xml (SHA256 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-mac-broadcast.xml (Modification time mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-mac-broadcast.xml (Size mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-mac-broadcast.xml (MD5 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-mac-broadcast.xml (SHA256 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-mac-spoofing.xml (Modification time mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-mac-spoofing.xml (Size mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-mac-spoofing.xml (MD5 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-mac-spoofing.xml (SHA256 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-other-l2-traffic.xml (Modification time mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-other-l2-traffic.xml (Size mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-other-l2-traffic.xml (MD5 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-other-l2-traffic.xml (SHA256 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-other-rarp-traffic.xml (Modification time mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-other-rarp-traffic.xml (Size mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-other-rarp-traffic.xml (MD5 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/no-other-rarp-traffic.xml (SHA256 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/qemu-announce-self-rarp.xml (Modification time mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/qemu-announce-self-rarp.xml (Size mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/qemu-announce-self-rarp.xml (MD5 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/qemu-announce-self-rarp.xml (SHA256 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/qemu-announce-self.xml (Modification time mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/qemu-announce-self.xml (Size mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/qemu-announce-self.xml (MD5 checksum mismatch)
backup file: libvirt: /etc/libvirt/nwfilter/qemu-announce-self.xml (SHA256 checksum mismatch)
backup file: libvirt: /etc/libvirt/qemu/networks/default.xml (Modification time mismatch)
backup file: libvirt: /etc/libvirt/qemu/networks/default.xml (Size mismatch)
backup file: libvirt: /etc/libvirt/qemu/networks/default.xml (MD5 checksum mismatch)
backup file: libvirt: /etc/libvirt/qemu/networks/default.xml (SHA256 checksum mismatch)
mercurial: 1622 total files, 1306 altered files
backup file: mkinitcpio: /etc/mkinitcpio.conf (Modification time mismatch)
backup file: mkinitcpio: /etc/mkinitcpio.conf (Size mismatch)
backup file: mkinitcpio: /etc/mkinitcpio.conf (MD5 checksum mismatch)
backup file: mkinitcpio: /etc/mkinitcpio.conf (SHA256 checksum mismatch)
modemmanager-qt5: no mtree file
networkmanager-qt5: no mtree file
nvidia: no mtree file
backup file: openssh: /etc/ssh/ssh_config (Modification time mismatch)
backup file: openssh: /etc/ssh/ssh_config (Size mismatch)
backup file: openssh: /etc/ssh/ssh_config (MD5 checksum mismatch)
backup file: openssh: /etc/ssh/ssh_config (SHA256 checksum mismatch)
backup file: pacman: /etc/pacman.conf (Modification time mismatch)
backup file: pacman: /etc/pacman.conf (Size mismatch)
backup file: pacman: /etc/pacman.conf (MD5 checksum mismatch)
backup file: pacman: /etc/pacman.conf (SHA256 checksum mismatch)
backup file: pacman-mirrorlist: /etc/pacman.d/mirrorlist (Modification time mismatch)
backup file: pacman-mirrorlist: /etc/pacman.d/mirrorlist (Size mismatch)
backup file: pacman-mirrorlist: /etc/pacman.d/mirrorlist (MD5 checksum mismatch)
backup file: pacman-mirrorlist: /etc/pacman.d/mirrorlist (SHA256 checksum mismatch)
perl-io-socket-ssl: no mtree file
plasma-wayland-session: no mtree file
plasma-welcome: no mtree file
plasma-workspace: no mtree file
prison5: no mtree file
python-pillow: no mtree file
python-platformdirs: no mtree file
python-poetry-core: no mtree file
shadow: 588 total files, 1 altered file
spectacle: no mtree file
sudo: no mtree file
backup file: systemd: /etc/systemd/timesyncd.conf (Modification time mismatch)
backup file: systemd: /etc/systemd/timesyncd.conf (Size mismatch)
backup file: systemd: /etc/systemd/timesyncd.conf (MD5 checksum mismatch)
backup file: systemd: /etc/systemd/timesyncd.conf (SHA256 checksum mismatch)
systemd: 1366 total files, 1 altered file
systemd-sysvcompat: no mtree file
backup file: texlive-basic: /etc/texmf/web2c/fmtutil.cnf (Modification time mismatch)
backup file: texlive-basic: /etc/texmf/web2c/fmtutil.cnf (Size mismatch)
backup file: texlive-basic: /etc/texmf/web2c/fmtutil.cnf (MD5 checksum mismatch)
backup file: texlive-basic: /etc/texmf/web2c/fmtutil.cnf (SHA256 checksum mismatch)
vde2: no mtree file
vlc: no mtree file
vmware-workstation: 2301 total files, 4 altered files
webkit2gtk: no mtree file
webkit2gtk-4.1: no mtree file
wine-staging: no mtree file
wolfssl: no mtree file
wxwidgets-common: no mtree file
wxwidgets-gtk3: no mtree file

Do I fix all the errors like before or wait until some updates?
At least this second time I can boot into the system, but when try to login into kde from sddm (I think) after entering the password, Enter does not work. I enter my user's password (shown by black dots) and hit enter but nothing happens.

Last edited by korimitsu (2023-11-18 15:04:39)

Offline

#32 2023-11-18 15:06:48

seth
Member
Registered: 2012-09-03
Posts: 57,289

Re: [Solved] Error preparing initrd: Not Found after today update

sudo journalctl -b -1

But "delay" doesn't typically cause uexpected power losses - you yanking the power cord or holding down the power button would.

modemmanager-qt5: no mtree file
networkmanager-qt5: no mtree file
nvidia: no mtree file
perl-io-socket-ssl: no mtree file
plasma-wayland-session: no mtree file
plasma-welcome: no mtree file
plasma-workspace: no mtree file
prison5: no mtree file
python-pillow: no mtree file
python-platformdirs: no mtree file
python-poetry-core: no mtree file
spectacle: no mtree file
sudo: no mtree file
systemd-sysvcompat: no mtree file
vde2: no mtree file
vlc: no mtree file
webkit2gtk: no mtree file
webkit2gtk-4.1: no mtree file
wine-staging: no mtree file
wolfssl: no mtree file
wxwidgets-common: no mtree file
wxwidgets-gtk3: no mtree file

is most certainly not to be expected - your sudo package is corrupted.

What about

seth wrote:

overaggressive (continuous) trimming

?

mount

Edit:

Do I fix all the errors like before or wait until some updates?

You figure why your FS is repeatedly corrupting before doing anything else with the system.

Edit #2:
Hold on

Device Model:     Corsair Voyager GTX

Is that any external USB drive??

Last edited by seth (2023-11-18 15:09:38)

Offline

#33 2023-11-18 15:54:57

korimitsu
Member
Registered: 2016-08-14
Posts: 137

Re: [Solved] Error preparing initrd: Not Found after today update

seth wrote:
sudo journalctl -b -1

Is that any external USB drive??

Yes, is USB storage.

Do you want the output of journalctl now (1844 lines) or is just when I have the problem?

How to I know if trimming is enabled and how to disable it, or is just a hardware thing which can't be changed?

Last edited by korimitsu (2023-11-18 15:55:24)

Offline

#34 2023-11-18 15:58:48

seth
Member
Registered: 2012-09-03
Posts: 57,289

Re: [Solved] Error preparing initrd: Not Found after today update

Neither.

You wrote:

how can I see the shut down log from previous poweroff so see what took so much time?

https://wiki.archlinux.org/title/Power_ … utosuspend
"usbcore.autosuspend=-1" disables it, but nb. that userspace powermanagement tools can and will override that.

How to I know if trimming is enabled

Because you enabled it and "mount" would tell you about the continuous approach…
https://wiki.archlinux.org/title/Solid_state_drive#TRIM

Edit: also make sure to have read https://wiki.archlinux.org/title/Instal … ble_medium
Using an external USB as root partition isn't the most robust setup…

Last edited by seth (2023-11-18 16:00:10)

Offline

#35 2023-11-18 16:25:46

korimitsu
Member
Registered: 2016-08-14
Posts: 137

Re: [Solved] Error preparing initrd: Not Found after today update

seth wrote:

Using an external USB as root partition isn't the most robust setup…

I have another USB drive (same model) with Ubuntu and another with Manjaro and no problems at all...maybe the installers changed some configuration.
i'll try some changes with the links you provided to see if there's some improvement.

Last edited by korimitsu (2023-11-18 16:26:33)

Offline

#36 2023-11-18 19:28:17

seth
Member
Registered: 2012-09-03
Posts: 57,289

Re: [Solved] Error preparing initrd: Not Found after today update

Did you check what trimming you currently implement?
Do NOT opt for continuous trimming.

I have another USB drive

But not the same - oc. the drive might just be falling apart hmm

Offline

#37 2023-11-25 18:14:07

korimitsu
Member
Registered: 2016-08-14
Posts: 137

Re: [Solved] Error preparing initrd: Not Found after today update

These are the values of TRIM:

$ lsblk --discard /dev/sdg
NAME        DISC-ALN DISC-GRAN DISC-MAX DISC-ZERO
sdg                0        0B       0B         0
├─sdg1             0        0B       0B         0
└─sdg2             0        0B       0B         0
  └─luksdev        0        0B       0B         0
# hdparm -I /dev/sdg | grep TRIM
           *    Data Set Management TRIM supported (limit 8 blocks)
# smartctl -g security /dev/sdg
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.6.2-arch1-1] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

ATA Security is:  Disabled, NOT FROZEN [SEC1]
# sg_readcap -l /dev/sdg
Read Capacity results:
   Protection: prot_en=0, p_type=0, p_i_exponent=0
   Logical block provisioning: lbpme=0, lbprz=0
   Last LBA=2000409263 (0x773bd2af), Number of logical blocks=2000409264
   Logical block length=512 bytes
   Logical blocks per physical block exponent=0
   Lowest aligned LBA=0
Hence:
   Device size: 1024209543168 bytes, 976762.3 MiB, 1024.21 GB
# sg_vpd -a /dev/sdg
Supported VPD pages VPD page:
  Supported VPD pages [sv]
  Unit serial number [sn]
  Device identification [di]
  Block limits (SBC) [bl]
  Block device characteristics (SBC) [bdc]
  Logical block provisioning (SBC) [lbpv]

Unit serial number VPD page:
  Unit serial number: (deleted)

Device Identification VPD page:
  Addressed logical unit:
    designator type: NAA,  code set: Binary
      0x5000000000000001

Block limits VPD page (SBC):
  Write same non-zero (WSNZ): 0
  Maximum compare and write length: 0 blocks [Command not implemented]
  Optimal transfer length granularity: 1 blocks
  Maximum transfer length: 65535 blocks
  Optimal transfer length: 65535 blocks
  Maximum prefetch transfer length: 65535 blocks
  Maximum unmap LBA count: 4194240
  Maximum unmap block descriptor count: 1
  Optimal unmap granularity: 1 blocks
  Unmap granularity alignment valid: false
  Unmap granularity alignment: 0 [invalid]
  Maximum write same length: 0 blocks [not reported]
  Maximum atomic transfer length: 0 blocks [not reported]
  Atomic alignment: 0 [unaligned atomic writes permitted]
  Atomic transfer length granularity: 0 [no granularity requirement
  Maximum atomic transfer length with atomic boundary: 0 blocks [not reported]
  Maximum atomic boundary size: 0 blocks [can only write atomic 1 block]

Block device characteristics VPD page (SBC):
  Non-rotating medium (e.g. solid state)
  Product type: Not specified
  WABEREQ=0
  WACEREQ=0
  Nominal form factor: 2.5 inch
  MACT=0
  ZONED=0
  RBWZ=0
  BOCS=0
  FUAB=0
  VBULS=0
  DEPOPULATION_TIME=0 (seconds)

Logical block provisioning VPD page (SBC):
  Unmap command supported (LBPU): 1
  Write same (16) with unmap bit supported (LBPWS): 0
  Write same (10) with unmap bit supported (LBPWS10): 0
  Logical block provisioning read zeros (LBPRZ): 0
  Anchored LBAs supported (ANC_SUP): 0
  Threshold exponent: 0 [threshold sets not supported]
  Descriptor present (DP): 0
  Minimum percentage: 0 [not reported]
  Provisioning type: 0 (not known or fully provisioned)
  Threshold percentage: 0 [percentages not supported]
# cat /sys/block/sdg/device/scsi_disk/*/provisioning_mode
full

Should I disable write-cache? How do I disable TRIM for USB devices?
I have added the "sync" option to both "/" and "/boot" mount points in /etc/fstab in case it helps.

What about this?
https://forum.endeavouros.com/t/how-com … e/37178/15
https://forum.endeavouros.com/t/how-to- … rage/38020

Both times I had the issues where just after upgrading the kernel, so there must be something related to it.

Last edited by korimitsu (2023-11-26 14:20:08)

Offline

#38 2023-11-25 20:03:30

seth
Member
Registered: 2012-09-03
Posts: 57,289

Re: [Solved] Error preparing initrd: Not Found after today update

You *noticed* the issue when running into the flawed mkinitcpio presets - it has nothing. NOTHING to do with the kernel updates per sē - get that out of your head.
If anything it might be related to the IO load or pattern you're creating w/ bigger updates (downloading the packages and then replacing some gigabyte with the actual update in typically small files)

I have added the "sync" option to both "/" and "/boot" mount points in /etc/fstab in case it helps.

It helps to turn your disk into a brick. Why would you do that?

You don't disable trimming for usb devices, but for filesystems.
What's the output of "mount"?

smartctl -g security /dev/sdg

What's that's supposed to tell?

Disabling the write cache will just age the disk faster - all partitions are supposed to be properly unmounted on a clean shutdown.

Offline

#39 2023-11-26 14:19:52

korimitsu
Member
Registered: 2016-08-14
Posts: 137

Re: [Solved] Error preparing initrd: Not Found after today update

seth wrote:

You *noticed* the issue when running into the flawed mkinitcpio presets - it has nothing. NOTHING to do with the kernel updates per sē - get that out of your head.
If anything it might be related to the IO load or pattern you're creating w/ bigger updates (downloading the packages and then replacing some gigabyte with the actual update in typically small files)

I have added the "sync" option to both "/" and "/boot" mount points in /etc/fstab in case it helps.

It helps to turn your disk into a brick. Why would you do that?

You don't disable trimming for usb devices, but for filesystems.
What's the output of "mount"?

smartctl -g security /dev/sdg

What's that's supposed to tell?

Disabling the write cache will just age the disk faster - all partitions are supposed to be properly unmounted on a clean shutdown.

No idea what "smartctl -g security" is supposed to tell, it's just mentioned in the wiki.
How to I disable trim for my filesystems?
The output of mount:

$ mount
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
dev on /dev type devtmpfs (rw,nosuid,relatime,size=16399156k,nr_inodes=4099789,mode=755,inode64)
run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755,inode64)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
/dev/mapper/luksdev on / type ext4 (rw,noatime,stripe=8191)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=35,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=7304)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,nosuid,nodev,relatime,pagesize=2M)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,size=16413232k,nr_inodes=1048576,inode64)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
/dev/sdg1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)
none on /sys/fs/cgroup/net_cls type cgroup (rw,relatime,net_cls)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=3282644k,nr_inodes=820661,mode=700,uid=1000,gid=1000,inode64)
portal on /run/user/1000/doc type fuse.portal (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)

Last edited by korimitsu (2023-11-26 14:21:22)

Offline

#40 2023-11-26 16:24:32

seth
Member
Registered: 2012-09-03
Posts: 57,289

Re: [Solved] Error preparing initrd: Not Found after today update

The interesting smartctl switch is "-a"

Did you read the article about trimming?
You're not mounting w/ "discard", so you're not continuously trimming. If you're scheduling trims otherwise you'd hopefully know so.

stripe=8191

Do you configure that in your fstab or is it autoselected?

You didn't mention why you sync mounted  the partitions?

Offline

#41 2023-11-26 17:14:16

korimitsu
Member
Registered: 2016-08-14
Posts: 137

Re: [Solved] Error preparing initrd: Not Found after today update

seth wrote:

The interesting smartctl switch is "-a"

Did you read the article about trimming?
You're not mounting w/ "discard", so you're not continuously trimming. If you're scheduling trims otherwise you'd hopefully know so.

stripe=8191

Do you configure that in your fstab or is it autoselected?

You didn't mention why you sync mounted  the partitions?

How to I know if I have scheduled trims? I never set up such thing.
I tried the use sync for mounted partitions because was mentioned in another forums as a good practice for USB devices.
"stripe=8191" was not added by me.

I just want to know where my errors come from.

This is the information I've got:

# systemctl |grep fstrim
  fstrim.timer                                                                                               loaded active waiting   Discard unused filesystem blocks once a week
# systemctl status fstrim
○ fstrim.service - Discard unused blocks on filesystems from /etc/fstab
     Loaded: loaded (/usr/lib/systemd/system/fstrim.service; static)
     Active: inactive (dead)
TriggeredBy: ● fstrim.timer
       Docs: man:fstrim(8)

Should I disable fstrim?

Last edited by korimitsu (2023-11-26 17:26:54)

Offline

#42 2023-11-26 17:30:00

korimitsu
Member
Registered: 2016-08-14
Posts: 137

Re: [Solved] Error preparing initrd: Not Found after today update

These are the messages when disabling it:

# systemctl stop fstrim
Stopping 'fstrim.service', but its triggering units are still active:
fstrim.timer
# systemctl disable fstrim
Disabling 'fstrim.service', but its triggering units are still active:
fstrim.timer
The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
template units). This means they are not meant to be enabled or disabled using systemctl.
 
Possible reasons for having this kind of units are:
• A unit may be statically enabled by being symlinked from another unit's
  .wants/, .requires/, or .upholds/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
  a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
  D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
  instance name specified.

I had to run this as well:

# systemctl disable fstrim.timer
Removed "/etc/systemd/system/timers.target.wants/fstrim.timer".

Last edited by korimitsu (2023-11-26 17:33:10)

Offline

#43 2023-11-26 17:36:58

seth
Member
Registered: 2012-09-03
Posts: 57,289

Re: [Solved] Error preparing initrd: Not Found after today update

I tried the use sync for mounted partitions because was mentioned in another forums as a good practice for USB devices.

This is imbecile. People do this to get a sync copy progress in their GUI FM, but it's stupid and systematically harmful to the drive.

systemctl list-timers

but it's probably not active anyway.

I just want to know where my errors come from.

Did you setup an audit rule for the file? (permanently)
Did you frequently inspect the file and esp. after reboots?
Do you get frequently corrupted filesystem warnings and fsck runs?

Offline

#44 2023-11-27 17:05:26

korimitsu
Member
Registered: 2016-08-14
Posts: 137

Re: [Solved] Error preparing initrd: Not Found after today update

seth wrote:
systemctl list-timers

but it's probably not active anyway.

Did you setup an audit rule for the file? (permanently)
Did you frequently inspect the file and esp. after reboots?
Do you get frequently corrupted filesystem warnings and fsck runs?

# systemctl list-timers
NEXT                            LEFT LAST                               PASSED UNIT                             ACTIVATES                         
Mon 2023-11-27 18:12:24        10min -                                       - systemd-tmpfiles-clean.timer     systemd-tmpfiles-clean.service
Tue 2023-11-28 00:00:00     5h 58min -                                       - atop-rotate.timer                atop-rotate.service
Tue 2023-11-28 00:00:00     5h 58min Mon 2023-11-27 12:57:41      4min 11s ago shadow.timer                     shadow.service
Tue 2023-11-28 09:31:44          15h Fri 2023-08-25 21:33:38                 - archlinux-keyring-wkd-sync.timer archlinux-keyring-wkd-sync.service
Sat 2023-12-02 15:00:00       4 days Sun 2023-11-05 20:06:23                 - pamac-cleancache.timer           pamac-cleancache.service

5 timers listed.
Pass --all to see loaded but inactive timers, too.

I didn't setup any audir file
I don't inspect the file
I don't get corrupt filesystems or fsck runs. In fact, running fsck.ext4 from chroot with live arch iso shows no errors, I've already posted it.

Last edited by korimitsu (2023-11-27 21:20:41)

Offline

#45 2023-11-27 20:37:14

seth
Member
Registered: 2012-09-03
Posts: 57,289

Re: [Solved] Error preparing initrd: Not Found after today update

I didn't setup any audir file
I don't inspect the file

If you want to know what's happening, that'd maybe a good idea to start?

chckdsk is a windows program from ntfs and I rather meant during reboots (as sign of an unclean shutdown)

Offline

#46 2023-11-27 21:21:18

korimitsu
Member
Registered: 2016-08-14
Posts: 137

Re: [Solved] Error preparing initrd: Not Found after today update

seth wrote:

I didn't setup any audir file
I don't inspect the file

If you want to know what's happening, that'd maybe a good idea to start?

chckdsk is a windows program from ntfs and I rather meant during reboots (as sign of an unclean shutdown)

I meant fsck.ext4
How to I get ready before next kernel upgrade to log the error?

Offline

#47 2023-11-27 21:58:30

seth
Member
Registered: 2012-09-03
Posts: 57,289

Re: [Solved] Error preparing initrd: Not Found after today update

https://bbs.archlinux.org/viewtopic.php … 8#p2132368
As for the file, you could setup a cronjob or systemd timer that periodically checks its size and sends a notification if something's off.

ready before next kernel upgrade

Once more: unless you set up an alpm hook that does something stupid with the files, this is NOT RELATED TO THE KERNEL UPDATE. Get that the fuck out of your head.
The data will disintegrate at somepoint™ for reasons™. If you're waiting for a kernel update to happen, that is most likely too late.

Offline

#48 2023-11-28 17:14:56

korimitsu
Member
Registered: 2016-08-14
Posts: 137

Re: [Solved] Error preparing initrd: Not Found after today update

seth wrote:

https://bbs.archlinux.org/viewtopic.php … 8#p2132368
As for the file, you could setup a cronjob or systemd timer that periodically checks its size and sends a notification if something's off.

Check the size of what? How exactly do I do that?

Offline

#49 2023-11-28 17:59:27

seth
Member
Registered: 2012-09-03
Posts: 57,289

Re: [Solved] Error preparing initrd: Not Found after today update

The preset files you keep loosing?

Offline

#50 2023-12-07 20:23:46

korimitsu
Member
Registered: 2016-08-14
Posts: 137

Re: [Solved] Error preparing initrd: Not Found after today update

Today I've updated the kernels and had 2 terminals side by side, one with pacman and another checking the presets:

$ sudo pacman -S linux linux-headers linux-lts linux-lts-headers
resolving dependencies...
looking for conflicting packages...

Packages (4) linux-6.6.4.arch1-1  linux-headers-6.6.4.arch1-1  linux-lts-6.1.65-1  linux-lts-headers-6.1.65-1

Total Download Size:   296.44 MiB
Total Installed Size:  517.14 MiB
Net Upgrade Size:        0.02 MiB

:: Proceed with installation? [Y/n]

What I've seen is that before installing the new kernels, the previous ones are uninstalled (which nobody mentioned in this thread), removing alongside linux.preset and linux-lts.preset. Then it installs the new versions of the kernels with the new presets.
During this upgrade no issue happened, so my guess is that it was some misconfiguration in some script which caused the presets not to be installed after being removed.

Let's see if in future upgrades happens again, for now I consider it fixed.

Offline

Board footer

Powered by FluxBB