Is there any point in sudo apt upgrade with the lite OS?

[nick268]

I have installed the 32 bit lite version of the Pi OS on an SD card. I have picked the 32 bit image as I will be using the card in a Pi zero in due course.

In order to do some programming, I used this card in a Pi 3b.

I (made the mistake of) updating and upgrading the SD card with

Code: Select all

sudo apt update

and

Code: Select all

sudo apt upgrade

It seems that was a HUGE HUGE HUGE mistake.

I got loads of

Code: Select all

Adding 'diversion of /boot/overlays/vc4-kms-dsi-lt070me05000.dtbo to /usr/share/
rpikernelhack/overlays/vc4-kms-dsi-lt070me05000.dtbo by rpikernelhack'
Adding 'diversion of /boot/overlays/vc4-kms-kippah-7inch.dtbo to /usr/share/rpik
ernelhack/overlays/vc4-kms-kippah-7inch.dtbo by rpikernelhack'

and then loads of

Code: Select all

Removing 'diversion of /boot/overlays/camera-mux-2port.dtbo to /usr/share/rpiker
nelhack/overlays/camera-mux-2port.dtbo by rpikernelhack'
Removing 'diversion of /boot/overlays/camera-mux-4port.dtbo to /usr/share/rpiker
nelhack/overlays/camera-mux-4port.dtbo by rpikernelhack'

Which took an age, and even now after some 45 minutes the upgrade hasn't finished, apparently stalling at 61%, which has completely messed up my trying to do anything with the Pi tonight.

Is this an issue that means the only way to effectively use my Pi is to image a card with the latest version and then just leave it at that, never trying to update and upgrade the OS, as doing so brings on a whole world of pain, and is actually not possible effectively?

N.

[rpdom]

It sounds like you have a slow card or lack of free space or perhaps something running on you Pi that is using a lot of CPU or memory? Even my slowest Pi takes less than 10 minutes for a full update and upgrade.

I run Lite on all my Pis. I run an update and upgrade at least once a week on each of them.

[jahboater]

Which took an age, and even now after some 45 minutes the upgrade hasn't finished, apparently stalling at 61%, which has completely messed up my trying to do anything with the Pi tonight.

Is this the first update after the installation?

The first update might take a long time because it includes all the updates since the image was built.

Do the update once a week or so, and it usually takes very little time.

By the way, I do this on my Lite OS Pi's:

Code: Select all

sudo apt update && sudo apt full-upgrade -y && sudo apt autoremove -y

[klricks]

The diversion of..... lines are normal whenever there is a kernel update...

[nick268]

It sounds like you have a slow card or lack of free space ....

Yes, it's looking like a combination of both. A newer, bigger card seems to have resolved it.

Is this the first update after the installation?
The first update might take a long time because it includes all the updates since the image was built.

Yes it was. In combination with the issues above .

The diversion of..... lines are normal whenever there is a kernel update...

I did wonder. They looked a bit strange.

Thanks all.

N.

[rpdom]

The diversion of..... lines are normal whenever there is a kernel update...

I did wonder. They looked a bit strange.

It's a workaround for some of the Debian apt rules about file locations. iirc apt will refuse to install certain files in /boot so they are put somewhere else, then diverted to /boot, moved to /boot and the diversion removed. I can't remember the exact details. It would be nice if there were another way around it as that bit does take a long time.

[andrum99]

...
I did wonder. They looked a bit strange.
...

I've always thought the wording was rather curious. I don't think it looks particularly professional to have software that spits out messages with things like 'rpikernelhack' in them.

[ejolson]

The diversion of..... lines are normal whenever there is a kernel update...

I did wonder. They looked a bit strange.

It's a workaround for some of the Debian apt rules about file locations. iirc apt will refuse to install certain files in /boot so they are put somewhere else, then diverted to /boot, moved to /boot and the diversion removed. I can't remember the exact details. It would be nice if there were another way around it as that bit does take a long time.

Moving the files back and forth is also quite fragile as the system won't boot if interrupted before they are moved back.

[redvli]

...
I did wonder. They looked a bit strange.
...

I've always thought the wording was rather curious. I don't think it looks particularly professional to have software that spits out messages with things like 'rpikernelhack' in them.

Indeed, but it is like it is. I also don't like it at all. In case of an error or sudden power-loss, the system won't boot. I have had this a few times in the past. If the Pi is somewhere remote / build-in, it is an annoying process of taking out the SD-card, fixing it and putting it back. But I guess quite some Pi and RPiOS users don't know how to fix it, so they probably write a new image to the SD-card.