Failed Update

[sdetweil]

@DarkV man this is a pain

one more try

sudo apt-get remove nodejs npm -y
hash -r
which node
which n

if which n response with empty then do

sudo apt-get install n 

once n responds then

sudo n 20.8.0	--arch armv7l
hash -r 
node -v 

should say V20.8.0

i notice that I didn’t copy this little part from the install script…

please let me know

[sdetweil]

@DarkV never mind that won’t work… need node and npm to install n… grr…

ok, only way out is to redo the sd card
backup your MM
see https://github.com/sdetweil/MagicMirror-backup-restore

copy the backup folder MM_backup off the sd card (it can save to github too)

reflash the sd card with latest os
boot, no updates,
run install script to install MM
verify it runs
restore your config using my restore script (can restore directly from github too)

test

sorry, the nodejs guys made a mess of this as they changed the node install process too… and it doesn’t work.

[DarkV]

@sdetweil All is OK. I am so grateful for all of your assistance. In my opinion, what you performed was alchemy or witchcraft. I’ve been attempting to identify the problem and have made multiple unsuccessful attempts. An old picture I had from a few months ago was my saviour. My wife was becoming tired of my futile attempts at updating.
You have brought me happiness and protected me from madness. That’s a significant victory.

[sdetweil]

@DarkV before you jump off the bridge! try this

sudo apt-get remove nodejs npm -y
hash -r

make sure gone
which node

then 

sudo apt-get install nodejs:armv7l
node -v

[DarkV]

@sdetweil I don’t know what happened, but the reply is above. Many thanks

[sdetweil]

@DarkV cool… i didn’t expect that it, i’m glad!!

[DarkV]

@sdetweil I did this
sudo apt-get remove nodejs npm -y
hash -r
which node
which n

if which n response with empty then do

sudo apt-get install n

once n responds then

sudo n 20.8.0 --arch armv7l
hash -r
node -v

Then both scripts and it went through!

[sdetweil]

@DarkV said in Failed Update:

–arch armv7l

awesome… it was that sneaky little --arch parm…

fixing upgrade script now . sorry for your troubles

[DarkV]

@sdetweil No worries, thanks you for your time

[sdetweil]

@DarkV any chance you still have the os image file you are running

the info says (from the upgrade.log)

6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux
the os is Distributor ID: Raspbian Description: Raspbian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye

only one I can find online says
6.1.21-v7+

trying to test fix for the problem you encountered.

if you still have the image file can you give me its name…

also, what pi is this, 3 or 4?
thanks

| edit: was able to make one
| install bullseye armhf
| edit /boot/config.txt
add
arm_64bit=1

then u will boot 64bit kernel, (seen with uname -a, aarch64)

Linux raspberrypi4 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr  3 17:24:16 BST 2023 aarch64 GNU/Linux

and have 32 bit runtime (seen with file /bin/bash

/bin/bash: ELF 32-bit LSB executable