missing initrd file for 4.2.8-1-pve

[lynn_yudi]

hi,

normal update system, but the lastest pve-kernel miss the initrd file.

......
Fetched 141 kB in 3s (36.2 kB/s)

The following NEW packages will be installed:
pve-kernel-4.2.8-1-pve{a}
The following packages will be upgraded:
proxmox-ve
1 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 4,682 B/43.3 MB of archives. After unpacking 0 B will be used.
Get: 1 http://download.proxmox.com/debian/ jessie/pvetest proxmox-ve all 4.1-39 [4,682 B]
Fetched 4,682 B in 0s (47.0 kB/s)
Reading changelogs... Done
Selecting previously unselected package pve-kernel-4.2.8-1-pve.
(Reading database ... 48662 files and directories currently installed.)
Preparing to unpack .../pve-kernel-4.2.8-1-pve_4.2.8-39_amd64.deb ...
Unpacking pve-kernel-4.2.8-1-pve (4.2.8-39) ...
Preparing to unpack .../proxmox-ve_4.1-39_all.deb ...
Unpacking proxmox-ve (4.1-39) over (4.0-22) ...
Setting up pve-kernel-4.2.8-1-pve (4.2.8-39) ...
Setting up proxmox-ve (4.1-39) ...
installing proxmox release key: OK

Current status: 0 updates [-1].

# ls -l /boot/
total 76852
-rw-r--r-- 1 root root 184557 Nov 15 23:13 config-4.2.3-2-pve
-rw-r--r-- 1 root root 184580 Jan 28 18:30 config-4.2.6-1-pve
-rw-r--r-- 1 root root 184613 Feb 26 23:42 config-4.2.8-1-pve
drwxr-xr-x 5 root root 7168 Mar 3 19:12 grub
-rw-r--r-- 1 root root 22948695 Feb 22 03:02 initrd.img-4.2.3-2-pve
-rw-r--r-- 1 root root 22889318 Mar 3 10:39 initrd.img-4.2.6-1-pve
drwx------ 2 root root 12288 Aug 2 2013 lost+found
-rw-r--r-- 1 root root 182704 Sep 11 2014 memtest86+.bin
-rw-r--r-- 1 root root 184840 Sep 11 2014 memtest86+_multiboot.bin
drwxr-xr-x 2 root root 1024 Mar 3 19:13 pve
-rw-r--r-- 1 root root 3763096 Nov 15 23:13 System.map-4.2.3-2-pve
-rw-r--r-- 1 root root 3763788 Jan 28 18:30 System.map-4.2.6-1-pve
-rw-r--r-- 1 root root 3767420 Feb 26 23:42 System.map-4.2.8-1-pve
-rw-r--r-- 1 root root 6867296 Nov 15 23:13 vmlinuz-4.2.3-2-pve
-rw-r--r-- 1 root root 6869408 Jan 28 18:30 vmlinuz-4.2.6-1-pve
-rw-r--r-- 1 root root 6879072 Feb 26 23:42 vmlinuz-4.2.8-1-pve

 

[wolfgang]

Hi,

try

apt-get install --reinstall pve-kernel-4.2.8-1-pve

 

[lynn_yudi]

Hi,

try

apt-get install --reinstall pve-kernel-4.2.8-1-pve

# apt-get install --reinstall pve-kernel-4.2.8-1-pve
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/43.3 MB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 54038 files and directories currently installed.)
Preparing to unpack .../pve-kernel-4.2.8-1-pve_4.2.8-39_amd64.deb ...
Unpacking pve-kernel-4.2.8-1-pve (4.2.8-39) over (4.2.8-39) ...
Setting up pve-kernel-4.2.8-1-pve (4.2.8-39) ...
# ls -l /boot
total 76852
-rw-r--r-- 1 root root 184557 Nov 15 23:13 config-4.2.3-2-pve
-rw-r--r-- 1 root root 184580 Jan 28 18:30 config-4.2.6-1-pve
-rw-r--r-- 1 root root 184613 Feb 26 23:42 config-4.2.8-1-pve
drwxr-xr-x 5 root root 7168 Mar 3 20:00 grub
-rw-r--r-- 1 root root 22948695 Feb 22 03:02 initrd.img-4.2.3-2-pve
-rw-r--r-- 1 root root 22889318 Mar 3 10:39 initrd.img-4.2.6-1-pve
drwx------ 2 root root 12288 Aug 2 2013 lost+found
-rw-r--r-- 1 root root 182704 Sep 11 2014 memtest86+.bin
-rw-r--r-- 1 root root 184840 Sep 11 2014 memtest86+_multiboot.bin
drwxr-xr-x 2 root root 1024 Mar 3 19:13 pve
-rw-r--r-- 1 root root 3763096 Nov 15 23:13 System.map-4.2.3-2-pve
-rw-r--r-- 1 root root 3763788 Jan 28 18:30 System.map-4.2.6-1-pve
-rw-r--r-- 1 root root 3767420 Feb 26 23:42 System.map-4.2.8-1-pve
-rw-r--r-- 1 root root 6867296 Nov 15 23:13 vmlinuz-4.2.3-2-pve
-rw-r--r-- 1 root root 6869408 Jan 28 18:30 vmlinuz-4.2.6-1-pve
-rw-r--r-- 1 root root 6879072 Feb 26 23:42 vmlinuz-4.2.8-1-pve

can't fixed!

it's fixed by this:
# update-initramfs -c -k 4.2.8-1-pve
update-initramfs: Generating /boot/initrd.img-4.2.8-1-pve

# ls -l /boot
total 99276
-rw-r--r-- 1 root root 184557 Nov 15 23:13 config-4.2.3-2-pve
-rw-r--r-- 1 root root 184580 Jan 28 18:30 config-4.2.6-1-pve
-rw-r--r-- 1 root root 184613 Feb 26 23:42 config-4.2.8-1-pve
drwxr-xr-x 5 root root 7168 Mar 3 20:00 grub
-rw-r--r-- 1 root root 22948695 Feb 22 03:02 initrd.img-4.2.3-2-pve
-rw-r--r-- 1 root root 22889318 Mar 3 10:39 initrd.img-4.2.6-1-pve
-rw-r--r-- 1 root root 22961503 Mar 3 21:47 initrd.img-4.2.8-1-pve
drwx------ 2 root root 12288 Aug 2 2013 lost+found
-rw-r--r-- 1 root root 182704 Sep 11 2014 memtest86+.bin
-rw-r--r-- 1 root root 184840 Sep 11 2014 memtest86+_multiboot.bin
drwxr-xr-x 2 root root 1024 Mar 3 19:13 pve
-rw-r--r-- 1 root root 3763096 Nov 15 23:13 System.map-4.2.3-2-pve
-rw-r--r-- 1 root root 3763788 Jan 28 18:30 System.map-4.2.6-1-pve
-rw-r--r-- 1 root root 3767420 Feb 26 23:42 System.map-4.2.8-1-pve
-rw-r--r-- 1 root root 6867296 Nov 15 23:13 vmlinuz-4.2.3-2-pve
-rw-r--r-- 1 root root 6869408 Jan 28 18:30 vmlinuz-4.2.6-1-pve
-rw-r--r-- 1 root root 6879072 Feb 26 23:42 vmlinuz-4.2.8-1-pve

maybe this is another bug?

 

[wolfgang]

I don't think so, because you are the fist one and I can't reproduce it on our machines.
But I will keep an eye on it.

 

[xoxys]

Sorry for reactivating this thread. But same thing is happening to me... After Upgrade latest installed kernel version is pve-kernel-4.4.40-1-pve but the corresponding init ram disk file is missing.

ii  pve-firmware                   1.1-10                         all          Binary firmware code for the pve-kernel
rc  pve-kernel-2.6.32-39-pve       2.6.32-157                     amd64        The Proxmox PVE Kernel Image
rc  pve-kernel-2.6.32-43-pve       2.6.32-166                     amd64        The Proxmox PVE Kernel Image
rc  pve-kernel-4.2.2-1-pve         4.2.2-16                       amd64        The Proxmox PVE Kernel Image
ii  pve-kernel-4.2.6-1-pve         4.2.6-36                       amd64        The Proxmox PVE Kernel Image
ii  pve-kernel-4.2.8-1-pve         4.2.8-41                       amd64        The Proxmox PVE Kernel Image
rc  pve-kernel-4.4.10-1-pve        4.4.10-54                      amd64        The Proxmox PVE Kernel Image
rc  pve-kernel-4.4.13-1-pve        4.4.13-56                      amd64        The Proxmox PVE Kernel Image
rc  pve-kernel-4.4.13-2-pve        4.4.13-58                      amd64        The Proxmox PVE Kernel Image
ii  pve-kernel-4.4.15-1-pve        4.4.15-60                      amd64        The Proxmox PVE Kernel Image
ii  pve-kernel-4.4.19-1-pve        4.4.19-66                      amd64        The Proxmox PVE Kernel Image
ii  pve-kernel-4.4.24-1-pve        4.4.24-72                      amd64        The Proxmox PVE Kernel Image
ii  pve-kernel-4.4.35-1-pve        4.4.35-77                      amd64        The Proxmox PVE Kernel Image
ii  pve-kernel-4.4.35-2-pve        4.4.35-79                      amd64        The Proxmox PVE Kernel Image
ii  pve-kernel-4.4.40-1-pve        4.4.40-80                      amd64        The Proxmox PVE Kernel Image
rc  pve-kernel-4.4.8-1-pve         4.4.8-52                       amd64        The Proxmox PVE Kernel Image

-rw-r--r-- 1 root root 25425276 Dec  2 11:15 /boot/initrd.img-4.2.6-1-pve
-rw-r--r-- 1 root root 25438786 Dec  2 14:11 /boot/initrd.img-4.2.8-1-pve
-rw-r--r-- 1 root root 25940074 Dec  2 14:10 /boot/initrd.img-4.4.15-1-pve
-rw-r--r-- 1 root root 25953380 Dec  2 13:02 /boot/initrd.img-4.4.19-1-pve
-rw-r--r-- 1 root root 26388719 Dec  2 13:00 /boot/initrd.img-4.4.24-1-pve
-rw-r--r-- 1 root root 26395330 Dec 25 12:23 /boot/initrd.img-4.4.35-1-pve
-rw-r--r-- 1 root root 26394298 Feb 21 20:53 /boot/initrd.img-4.4.35-2-pve

Reinstalling the kernel does not fix the problem. Any idea why this happens?

 

[fabian]

Reinstalling the kernel does not fix the problem. Any idea why this happens?

could you post the complete output of re-installing the kernel? should look something like this:

# apt-get install --reinstall pve-kernel-4.4.40-1-pve
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 44.2 MB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 ... 4.4.40-80 [44.2 MB]
Fetched 44.2 MB in 1s (30.3 MB/s)
(Reading database ... 482668 files and directories currently installed.)
Preparing to unpack .../pve-kernel-4.4.40-1-pve_4.4.40-80_amd64.deb ...
Unpacking pve-kernel-4.4.40-1-pve (4.4.40-80) over (4.4.40-80) ...
Setting up pve-kernel-4.4.40-1-pve (4.4.40-80) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.40-1-pve /boot/vmlinuz-4.4.40-1-pve
run-parts: executing /etc/kernel/postinst.d/dkms 4.4.40-1-pve /boot/vmlinuz-4.4.40-1-pve
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.40-1-pve /boot/vmlinuz-4.4.40-1-pve
update-initramfs: Generating /boot/initrd.img-4.4.40-1-pve
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
W: mdadm: no arrays defined in configuration file.
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.4.40-1-pve /boot/vmlinuz-4.4.40-1-pve
Generating grub configuration file ...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Found linux image: /boot/vmlinuz-4.4.40-1-pve
Found initrd image: /boot/initrd.img-4.4.40-1-pve
Found linux image: /boot/vmlinuz-4.4.35-2-pve
Found initrd image: /boot/initrd.img-4.4.35-2-pve
Found memtest86+ image: /boot/memtest86+.bin
Found memtest86+ multiboot image: /boot/memtest86+_multiboot.bin
done

 

[xoxys]

Sure. Here it is

# apt-get install --reinstall pve-kernel-4.4.40-1-pve
Reading package lists... Done
Building dependency tree       
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/44,2 MB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 80057 files and directories currently installed.)
Preparing to unpack .../pve-kernel-4.4.40-1-pve_4.4.40-80_amd64.deb ...
Unpacking pve-kernel-4.4.40-1-pve (4.4.40-80) over (4.4.40-80) ...
Setting up pve-kernel-4.4.40-1-pve (4.4.40-80) ...

# ls -l /boot/initrd*
-rw-r--r-- 1 root root 25425276 Dez  2 11:15 /boot/initrd.img-4.2.6-1-pve
-rw-r--r-- 1 root root 25438786 Dez  2 14:11 /boot/initrd.img-4.2.8-1-pve
-rw-r--r-- 1 root root 25940074 Dez  2 14:10 /boot/initrd.img-4.4.15-1-pve
-rw-r--r-- 1 root root 25953380 Dez  2 13:02 /boot/initrd.img-4.4.19-1-pve
-rw-r--r-- 1 root root 26388719 Dez  2 13:00 /boot/initrd.img-4.4.24-1-pve
-rw-r--r-- 1 root root 26395330 Dez 25 12:23 /boot/initrd.img-4.4.35-1-pve
-rw-r--r-- 1 root root 26394298 Feb 21 20:53 /boot/initrd.img-4.4.35-2-pve

/etc/kernel/postinst.d scripts are not executed.... but why?

 

[fabian]

does the folder exist?

 

[xoxys]

Yes. Folder exist and the scripts are present (especially script for initrd).

 

[fabian]

please do the following:

• what happens when you run "dpkg-reconfigure pve-kernel-4.4.40-1-pve" ?
• does the file "/proxmox_install_mode" exist?
• does "depmod 4.4.40-1-pve" exit cleanly (check "$?" afterwards) and without warnings?
• does "run-parts --verbose --exit-on-error --arg=4.4.40-1-pve --arg=/boot/vmlinux-4.4.40-1-pve /etc/kernel/postinst.d" generate the initrd?

 

[xoxys]

• what happens when you run "dpkg-reconfigure pve-kernel-4.4.40-1-pve" ?
  noting, no output/errors
• does the file "/proxmox_install_mode" exist?
  yes
• does "depmod 4.4.40-1-pve" exit cleanly (check "$?" afterwards) and without warnings?
  no output/errors
  echo "$?" returns 0
• does "run-parts --verbose --exit-on-error --arg=4.4.40-1-pve --arg=/boot/vmlinux-4.4.40-1-pve /etc/kernel/postinst.d" generate the initrd?

# run-parts --verbose --exit-on-error --arg=4.4.40-1-pve --arg=/boot/vmlinux-4.4.40-1-pve /etc/kernel/postinst.d/
run-parts: executing /etc/kernel/postinst.d//apt-auto-removal 4.4.40-1-pve /boot/vmlinux-4.4.40-1-pve
run-parts: executing /etc/kernel/postinst.d//initramfs-tools 4.4.40-1-pve /boot/vmlinux-4.4.40-1-pve
update-initramfs: Generating /boot/initrd.img-4.4.40-1-pve
run-parts: executing /etc/kernel/postinst.d//zz-update-grub 4.4.40-1-pve /boot/vmlinux-4.4.40-1-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.4.40-1-pve
Found initrd image: /boot/initrd.img-4.4.40-1-pve
Found linux image: /boot/vmlinuz-4.4.35-2-pve
Found initrd image: /boot/initrd.img-4.4.35-2-pve
Found linux image: /boot/vmlinuz-4.4.35-1-pve
Found initrd image: /boot/initrd.img-4.4.35-1-pve
Found linux image: /boot/vmlinuz-4.4.24-1-pve
Found initrd image: /boot/initrd.img-4.4.24-1-pve
Found linux image: /boot/vmlinuz-4.4.19-1-pve
Found initrd image: /boot/initrd.img-4.4.19-1-pve
Found linux image: /boot/vmlinuz-4.4.15-1-pve
Found initrd image: /boot/initrd.img-4.4.15-1-pve
Found linux image: /boot/vmlinuz-4.2.8-1-pve
Found initrd image: /boot/initrd.img-4.2.8-1-pve
Found linux image: /boot/vmlinuz-4.2.6-1-pve
Found initrd image: /boot/initrd.img-4.2.6-1-pve
Found memtest86+ image: /boot/memtest86+.bin
Found memtest86+ multiboot image: /boot/memtest86+_multiboot.bin
done

# ls -l /boot/initrd*
-rw-r--r-- 1 root root 25425276 Dez  2 11:15 /boot/initrd.img-4.2.6-1-pve
-rw-r--r-- 1 root root 25438786 Dez  2 14:11 /boot/initrd.img-4.2.8-1-pve
-rw-r--r-- 1 root root 25940074 Dez  2 14:10 /boot/initrd.img-4.4.15-1-pve
-rw-r--r-- 1 root root 25953380 Dez  2 13:02 /boot/initrd.img-4.4.19-1-pve
-rw-r--r-- 1 root root 26388719 Dez  2 13:00 /boot/initrd.img-4.4.24-1-pve
-rw-r--r-- 1 root root 26395330 Dez 25 12:23 /boot/initrd.img-4.4.35-1-pve
-rw-r--r-- 1 root root 26394298 Feb 21 20:53 /boot/initrd.img-4.4.35-2-pve
-rw-r--r-- 1 root root 26394623 Feb 23 20:07 /boot/initrd.img-4.4.40-1-pve

Looks good for me, initrd created successfully.

 

[fabian]

• what happens when you run "dpkg-reconfigure pve-kernel-4.4.40-1-pve" ?
  noting, no output/errors
• does the file "/proxmox_install_mode" exist?
  yes

the latter causes the former - that file should only exist while the installer is running and is used to skip some operations that are not needed during the installation. in the kernel package's postinst script, running the kernel hooks is disabled if it exists, because we explicitly only generate the initrd and grub config at the end of the installation process and don't need the other hooks.

if you remove the file, future kernel upgrades should generate the initrd again. but before you do:

what does "ls -lh /proxmox_install_mode" and "dpkg -S /proxmox_install_mode" say? how did you install this system? from the official iso, via Debian Jessie, with some template / iso provided by a hoster? I've never seen this file around after installation before, and it should not be possible unless the install failed and you manually repaired it to a point of getting it to boot and continued from there

 

[xoxys]

the latter causes the former

... i don't realized it Thanks for your help. But it is strange... I have installed proxmox from the official iso. Proxmox is running in my homelab since 3 years and initrd was working all the time. The problem comes up the first time a few months ago but till now i had no time to dig into this. I have no idea why the file exists and i have certainly not fixed issues by hand.

I can give you some more informations when i'm at home

Edit:
dpkg -S /proxmox_install_mode
dpkg-query: no path found matching pattern /proxmox_install_mode

ls -lh /proxmox_install_mode
-rw-r--r-- 1 root root 0 Dez 12 2015 /proxmox_install_mode

After removing /proxmox_install_mode all is working as expected Thank you very much

 

[radn]

Hi,

I am experiencing the same issue since approximately September 2022 or so (can't recall exactly). I have checked my system and I do *not* have the file /proxmox_install_mode.

In my case, the latest kernel where this happened is pve-kernel-5.15.83-1-pve. Following the troubleshooting asked before, this is the output of
dpkg-reconfigure pve-kernel-5.15.83-1-pve:

dpkg-reconfigure pve-kernel-5.15.83-1-pve

Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/zz-proxmox-boot 5.15.83-1-pve /boot/vmlinuz-5.15.83-1-pve
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 5.15.83-1-pve /boot/vmlinuz-5.15.83-1-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.15.83-1-pve
Found memtest86+ image: /boot/memtest86+.bin
Found memtest86+ multiboot image: /boot/memtest86+_multiboot.bin
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
done

(NOTE: This BIOS does not support UEFI, so I am using legacy BIOS and not UEFI for boot, not sure if this affects).

As you can see, there is no reference to the initrd which should have been generated.

depmod 5.15.83-1-pve resulted in no errors. echo $? returned 0

I adapted the run-parts command to what I believe should be executed:

run-parts --verbose --exit-on-error --arg=5.15.83-1-pve --arg=/boot/vmlinuz-5.15.83-1-pve /etc/kernel/postinst.d

Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 5.15.83-1-pve /boot/vmlinuz-5.15.83-1-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.15.83-1-pve
Found memtest86+ image: /boot/memtest86+.bin
Found memtest86+ multiboot image: /boot/memtest86+_multiboot.bin
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
done

This, however, did *not* generate the initrd either.

I also tried to reinstall using apt-get install --reinstall:

# apt-get install --reinstall pve-kernel-5.15.83-1-pve  
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following package was automatically installed and is no longer required:
  pve-headers-5.15.74-1-pve
Use 'apt autoremove' to remove it.
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
(Reading database ... 136476 files and directories currently installed.)
Preparing to unpack .../pve-kernel-5.15.83-1-pve_5.15.83-1_amd64.deb ...
Unpacking pve-kernel-5.15.83-1-pve (5.15.83-1) over (5.15.83-1) ...
Setting up pve-kernel-5.15.83-1-pve (5.15.83-1) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/zz-proxmox-boot 5.15.83-1-pve /boot/vmlinuz-5.15.83-1-pve
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 5.15.83-1-pve /boot/vmlinuz-5.15.83-1-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.15.83-1-pve
Found memtest86+ image: /boot/memtest86+.bin
Found memtest86+ multiboot image: /boot/memtest86+_multiboot.bin
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
done
Scanning processes...                                                                                                                                                                                                                                                        
Scanning processor microcode...                                                                                                                                                                                                                                              
Scanning linux images...                                                                                                                                                                                                                                                      
Running kernel seems to be up-to-date.

The processor microcode seems to be up-to-date.

No services need to be restarted.

No containers need to be restarted.

No user sessions are running outdated binaries.

Still, no initrd, despite links to it are created in /boot/pve/:

# find /boot -name '*initrd*'
/boot/pve/initrd.img-4.15
/boot/pve/initrd.img-5.11
/boot/pve/initrd.img-5.3
/boot/pve/initrd.img-5.4
/boot/pve/initrd.img-5.13
/boot/pve/initrd.img-5.15
/boot/pve/initrd.img

# ls -l /boot/pve/initrd.img*
lrwxrwxrwx 1 root root 25 Nov 22 17:11 /boot/pve/initrd.img -> /boot/pve/initrd.img-5.15
lrwxrwxrwx 1 root root 31 Jul 14  2019 /boot/pve/initrd.img-4.15 -> /boot/initrd.img-4.15.18-18-pve
lrwxrwxrwx 1 root root 30 Nov 14  2021 /boot/pve/initrd.img-5.11 -> /boot/initrd.img-5.11.22-7-pve
lrwxrwxrwx 1 root root 30 Mar 12  2022 /boot/pve/initrd.img-5.13 -> /boot/initrd.img-5.13.19-6-pve
lrwxrwxrwx 1 root root 30 Dec 26 18:48 /boot/pve/initrd.img-5.15 -> /boot/initrd.img-5.15.83-1-pve
lrwxrwxrwx 1 root root 29 Mar 23  2020 /boot/pve/initrd.img-5.3 -> /boot/initrd.img-5.3.18-3-pve
lrwxrwxrwx 1 root root 30 Jul  1  2021 /boot/pve/initrd.img-5.4 -> /boot/initrd.img-5.4.124-1-pve

# ls /boot/initrd*
ls: cannot access '/boot/initrd*': No such file or directory

I am using Proxmox version 7.3-4. Following is the output of pveversion:

# pveversion 
pve-manager/7.3-4/d69b70d4 (running kernel: 5.15.83-1-pve)

Any ideas on what could be wrong? Thank you very much in advance!!

 

[fabian]

did you remove /etc/kernel/postinst.d/initramfs-tools ? it's not called according to your output, so it's no wonder no initramfs generation/update is happening.. check the state of the "initramfs-tools" package, which is responsible for this hook script.

if it is installed and you (or someone else) accidentally removed this (and possibly other) scripts, the following should help:

apt install --reinstall -o Dpkg::Options::="--force-confask,confnew,confmiss" initramfs-tools

it will ask for any config files provided by the packaged which are different on your system compared to what the package ships, and reinstall any missing ones that were manually deleted at some point.

 

[radn]

Hi, I have not (knowingly) removed anything under /etc/kernel/postinst.d/*, but there is nothing there regarding initramfs-tools:

# ls /etc/kernel/postinst.d/*
/etc/kernel/postinst.d/zz-proxmox-boot
/etc/kernel/postinst.d/zz-update-grub

I do have initramfs-tools installed as pero dpkg output:

# dpkg -l initramfs-tools
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name            Version      Architecture Description
+++-===============-============-============-================================================
ii  initramfs-tools 0.140        all          generic modular initramfs generator (automation)

apt-get install --reinstall would not recreate that file, but your line did. Thanks!

 

[fabian]

yes, because all files shipped by packages in /etc are treated as configuration files which are tracked - if you remove one of them, apt/dpkg will not install it again unless you explicitly tell it to (because it thinks you removed it on purpose and don't want it to be created again )