[SOLVED] Update getting stuck on "Unpacking pve-kernel..."

[cjones]

I am unable to update without apt getting stuck on Unpacking pve-kernel-5.4.128-1-pve (5.4.128-2) over (5.4.128-1) ....

I end up having to kill the process. I have noticed that there are *.dpkg-tmp files under /boot for config, System.map, and vmlinuz of 5.4-128-1-pve. I've tried removing those, but get the same behavior. I'm not sure how else to troubleshoot this.

I am running PVE 6.4-13 using the "pve-no-subscription" repository.

Any suggestions?

 

[Stoiko Ivanov]

am unable to update without apt getting stuck on Unpacking pve-kernel-5.4.128-1-pve (5.4.128-2) over (5.4.128-1) ....

I end up having to kill the process. I have noticed that there are *.dpkg-tmp files under /boot for config, System.map, and vmlinuz of 5.4-128-1-pve. I've tried removing those, but get the same behavior. I'm not sure how else to troubleshoot this.

I would run the upgrade in tmux - and check in another shell which process is stuck (`ps auxwf` - look for processes in D state or D+)

else - check the journal in yet another shell (let `journalctl -f` run during the upgrade)

I hope this helps!

 

[cjones]

I would run the upgrade in tmux - and check in another shell which process is stuck (`ps auxwf` - look for processes in D state or D+)

else - check the journal in yet another shell (let `journalctl -f` run during the upgrade)

I hope this helps!

ps auxwf showed me that the sync command was hanging. This led me to investigate my rpool disks. One of the disks had quite a high "Reallocated_Sector_Ct" value relative to the other disk (which was at 0). Ended up replacing the disk and after that the upgrade completed fully.

Thanks!