Failed Update

Reply to Failed Update on Tue, 31 Oct 2023 14:02:50 GMT

DarkV — Tue, 31 Oct 2023 14:02:50 GMT

@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!

Reply to Failed Update on Thu, 04 Jan 2024 18:02:58 GMT

DarkV — Thu, 04 Jan 2024 18:02:58 GMT

@sdetweil Many thanks. Will backup the system before I try.

Reply to Failed Update on Fri, 05 Jan 2024 03:35:31 GMT

sdetweil — Fri, 05 Jan 2024 03:35:31 GMT

@DarkV I think I have fixed the upgrade script.
of course backup your mm system,

use my backup restore scripts.
https://github.com/sdetweil/MagicMirror-backup-restore

if you have space, copy the entire mm folder to another to save it.

don’t upgrade if there is nothing you need

Reply to Failed Update on Tue, 02 Jan 2024 09:19:09 GMT

DarkV — Tue, 02 Jan 2024 09:19:09 GMT

@DarkV Sorry to bug you again, but there is an update, since you said that my setup in a Hybrid setup, what script do I use? The wifey will kill me if I mess it up and for some reason I cannot backup my M2 Sata drive with Windows 11 as it is not detected, meaning I have one shot to get it right

Reply to Failed Update on Sat, 04 Nov 2023 10:29:05 GMT

sdetweil — Sat, 04 Nov 2023 10:29:05 GMT

@DarkV Thanks. I found a way to create the hybrid system so I could test your original.problem…

Reply to Failed Update on Sat, 04 Nov 2023 10:03:28 GMT

DarkV — Sat, 04 Nov 2023 10:03:28 GMT

@sdetweil My image is 112GB (although only 8.4 GB is used) as I used Win32 disc imager software. If you still want me to upload let me know although I don’t know a site that will allow a file that large.

Reply to Failed Update on Fri, 03 Nov 2023 16:08:40 GMT

sdetweil — Fri, 03 Nov 2023 16:08:40 GMT

@DarkV thanks

Reply to Failed Update on Fri, 03 Nov 2023 20:09:28 GMT

DarkV — Fri, 03 Nov 2023 20:09:28 GMT

@sdetweil The Image was my previous install I made in February when I migrated from SD to M2 SSD. So an older version of what I am using now.
I am using PI4.

Reply to Failed Update on Fri, 03 Nov 2023 07:54:29 GMT

lavolp3 — Fri, 03 Nov 2023 07:54:29 GMT

@sdetweil Sam, sorry for the confusion, everything is working. A said I had installed node 18 and then it all worked. I didn’t need help, just wanted to point out that node 20 seems to not be working with some systems. But as I see you got that covered in your script.

Reply to Failed Update on Thu, 02 Nov 2023 21:46:30 GMT

sdetweil — Thu, 02 Nov 2023 21:46:30 GMT

@lavolp3 ok, can you do

sudo apt update --fix-missing
sudo apt install -f

watch out for node changing…

Reply to Failed Update on Thu, 02 Nov 2023 21:09:39 GMT

lavolp3 — Thu, 02 Nov 2023 21:09:39 GMT

@sdetweil Sorry I have BUSTER installed. My mistake.

Here the lastlog

Upgrade started - Wed Nov  1 10:25:06 CET 2023
system is Linux magicmirror 5.10.103-v7+ #1529 SMP Tue Mar 8 12:21:37 GMT 2022 armv7l GNU/Linux
the os is Distributor ID: Raspbian Description: Raspbian GNU/Linux 10 (buster) Release: 10 Codename: buster
n (node version manager tool) not installed, doing test run, install skipped
doing test run = true, NO updates will be applied!
Check current Node installation ...
Node currently installed. Checking version number.
Minimum Node version: v18.18.0
Installed Node version: v16.20.2
Node should be upgraded.

Upgrade started - Wed Nov  1 10:45:19 CET 2023
system is Linux magicmirror 5.10.103-v7+ #1529 SMP Tue Mar 8 12:21:37 GMT 2022 armv7l GNU/Linux
user requested to force apply changes
the os is Distributor ID: Raspbian Description: Raspbian GNU/Linux 10 (buster) Release: 10 Codename: buster
node not installed, trying via apt-get
Reading package lists... Building dependency tree... Reading state information... nodejs is already the newest version (20.9.0-1nodesource1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
npm not installed, trying via apt-get
npm NOT installed now, install now
Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: npm : Depends: nodejs (>= 6.11~) Depends: node-abbrev (>= 1.1.1~) but it is not going to be installed Depends: node-ansi-regex (>= 3.0~) but it is not going to be installed Depends: node-ansistyles (>= 0.1.3~) but it is not going to be installed Depends: node-aproba (>= 1.2~) but it is not going to be installed Depends: node-archy (>= 1.0~) but it is not going to be installed Depends: node-cacache (>= 10.0.4~) but it is not going to be installed Depends: node-bluebird (>= 3.5.1~) but it is not going to be installed Depends: node-call-limit (>= 1.1~) but it is not going to be installed Depends: node-chownr (>= 1.0.1~) but it is not going to be installed Depends: node-config-chain (>= 1.1.11~) but it is not going to be installed Depends: node-detect-indent (>= 5.0~) but it is not going to be installed Depends: node-detect-newline (>= 2.1~) but it is not going to be installed Depends: node-editor (>= 1.0~) but it is not going to be installed Depends: node-fs-vacuum (>= 1.2.10~) but it is not going to be installed Depends: node-fs-write-stream-atomic (>= 1.0.10~) but it is not going to be installed Depends: node-glob (>= 7.1.2~) but it is not going to be installed Depends: node-graceful-fs (>= 4.1.11~) but it is not going to be installed Depends: node-has-unicode (>= 2.0.1~) but it is not going to be installed Depends: node-hosted-git-info (>= 2.6~) but it is not going to be installed Depends: node-iferr (>= 0.1.5~) but it is not going to be installed Depends: node-inflight (>= 1.0.6~) but it is not going to be installed Depends: node-inherits (>= 2.0.3~) but it is not going to be installed Depends: node-ini (>= 1.3.5~) but it is not going to be installed Depends: node-npm-package-arg but it is not going to be installed Depends: node-promzard but it is not going to be installed Depends: node-jsonstream (>= 1.3.2~) but it is not going to be installed Depends: node-json-parse-better-errors (>= 1.0.1~) but it is not going to be installed Depends: node-lazy-property (>= 1.0~) but it is not going to be installed Depends: node-libnpx (>= 10.0.1~) but it is not going to be installed Depends: node-lockfile (>= 1.0.3~) but it is not going to be installed Depends: node-lru-cache (>= 4.1.1~) but it is not going to be installed Depends: node-mississippi (>= 3.0~) but it is not going to be installed Depends: node-mkdirp (>= 0.3.3) but it is not going to be installed Depends: node-move-concurrently (>= 1.0.1~) but it is not going to be installed Depends: node-nopt but it is not going to be installed Depends: node-normalize-package-data (>= 2.4~) but it is not going to be installed Depends: node-gyp (>= 3.6.2~) but it is not going to be installed Depends: node-resolve-from (>= 4.0~) but it is not going to be installed Depends: node-encoding but it is not going to be installed Depends: node-errno but it is not going to be installed Depends: node-npmlog (>= 4.1.2~) but it is not going to be installed Depends: node-once (>= 1.4~) but it is not going to be installed Depends: node-opener (>= 1.4.3~) but it is not going to be installed Depends: node-osenv (>= 0.1.5~) but it is not going to be installed Depends: node-path-is-inside (>= 1.0.2~) but it is not going to be installed Depends: node-promise-inflight (>= 1.0.1~) but it is not going to be installed Depends: node-ansi but it is not going to be installed Depends: node-qw (>= 1.0.1~) but it is not going to be installed Depends: node-read (>= 1.0.7~) but it is not going to be installed Depends: node-read-package-json (>= 2.0.13~) but it is not going to be installed Depends: node-request (>= 2.83~) but it is not going to be installed Depends: node-retry (>= 0.10.1~) but it is not going to be installed Depends: node-rimraf (>= 2.6.2~) but it is not going to be installed Depends: node-safe-buffer (>= 5.1.1~) but it is not going to be installed Depends: node-semver (>= 5.5~) but it is not going to be installed Depends: node-sha (>= 2.0.1~) but it is not going to be installed Depends: node-slide (>= 1.1.6~) but it is not going to be installed Depends: node-sorted-object (>= 2.0.1~) but it is not going to be installed Depends: node-from2 but it is not going to be installed Depends: node-stream-iterate but it is not going to be installed Depends: node-ssri (>= 5.2.4~) but it is not going to be installed Depends: node-strip-ansi (>= 4.0~) but it is not going to be installed Depends: node-tar (>= 4.4~) but it is not going to be installed Depends: node-text-table (>= 0.2~) but it is not going to be installed Depends: node-uid-number (>= 0.0.6~) but it is not going to be installed Depends: node-unique-filename (>= 1.1~) but it is not going to be installed Depends: node-unpipe (>= 1.0~) but it is not going to be installed Depends: node-boxen (>= 1.2.1~) but it is not going to be installed Depends: node-import-lazy but it is not going to be installed Depends: node-is-npm (>= 1.0~) but it is not going to be installed Depends: node-latest-version (>= 3.0~) but it is not going to be installed Depends: node-semver-diff (>= 2.0~) but it is not going to be installed Depends: node-xdg-basedir (>= 3.0~) but it is not going to be installed Depends: node-validate-npm-package-name (>= 3.0~) but it is not going to be installed Depends: node-which (>= 1.3~) but it is not going to be installed Depends: node-wrappy (>= 1.0.2~) but it is not going to be installed Depends: node-write-file-atomic (>= 2.3~) but it is not going to be installed E: Unable to correct problems, you have held broken packages.
doing test run = false
Check current Node installation ...
Node currently installed. Checking version number.
forcing low Node version
Minimum Node version: v18.18.0
Installed Node version: V1.0.0
Node should be upgraded.

That was the last failed upgrade. Node V1.0.0 lol. Node 20 was installed.
After that I manually purged Node, installed Node 18 and did the npm run install-mm

Reply to Failed Update on Thu, 02 Nov 2023 14:20:56 GMT

sdetweil — Thu, 02 Nov 2023 14:20:56 GMT

@lavolp3 I check for buster and downgrade to node 18… not bullseye…

interested to see the log…

Reply to Failed Update on Thu, 02 Nov 2023 12:33:13 GMT

sdetweil — Thu, 02 Nov 2023 12:33:13 GMT

@lavolp3 can u send me the ~/MagicMirror/installers/upgrade.log

so I can see what happened…

same userid at gmail

Reply to Failed Update on Thu, 02 Nov 2023 12:31:03 GMT

lavolp3 — Thu, 02 Nov 2023 12:31:03 GMT

@sdetweil
Sam, I did an update yesterday and found Node 20.8 not working on my raspbian bullseye install.
I had an issue mentioned by someone else here before referring a missing GLIBCXX_3.4.26 file.
I needed to purge and install node 18.x. Then it worked.
Possible that this happens for more users with Raspbian
Bullseye.
I see your upgrade script requests Node 20.8.
Not sure if that may be an issue for other people as well?

Reply to Failed Update on Thu, 02 Nov 2023 13:50:50 GMT

sdetweil — Thu, 02 Nov 2023 13:50:50 GMT

@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

Reply to Failed Update on Tue, 31 Oct 2023 14:07:40 GMT

DarkV — Tue, 31 Oct 2023 14:07:40 GMT

@sdetweil No worries, thanks you for your time

Reply to Failed Update on Tue, 31 Oct 2023 14:06:34 GMT

sdetweil — Tue, 31 Oct 2023 14:06:34 GMT

@DarkV said in Failed Update:

–arch armv7l

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

fixing upgrade script now . sorry for your troubles

Reply to Failed Update on Tue, 31 Oct 2023 14:02:50 GMT

DarkV — Tue, 31 Oct 2023 14:02:50 GMT

@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!

Reply to Failed Update on Tue, 31 Oct 2023 13:59:06 GMT

sdetweil — Tue, 31 Oct 2023 13:59:06 GMT

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

Reply to Failed Update on Tue, 31 Oct 2023 13:55:35 GMT

DarkV — Tue, 31 Oct 2023 13:55:35 GMT

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

Reply to Failed Update on Tue, 31 Oct 2023 13:53:36 GMT

sdetweil — Tue, 31 Oct 2023 13:53:36 GMT

@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

Reply to Failed Update on Tue, 31 Oct 2023 13:52:49 GMT

DarkV — Tue, 31 Oct 2023 13:52:49 GMT

@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.

Reply to Failed Update on Tue, 31 Oct 2023 13:49:10 GMT

sdetweil — Tue, 31 Oct 2023 13:49:10 GMT

@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.

Reply to Failed Update on Tue, 31 Oct 2023 13:37:30 GMT

sdetweil — Tue, 31 Oct 2023 13:37:30 GMT

@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

Reply to Failed Update on Tue, 31 Oct 2023 13:18:52 GMT

DarkV — Tue, 31 Oct 2023 13:18:52 GMT

@sdetweil said in Failed Update:

file /bin/bash

unior@MAGIC-MIRROR:~ $ bash -c “$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)” apply
curl: (18) transfer closed with 23780100 bytes remaining to read
xz: (stdin): Unexpected end of input
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now

Error: failed to download archive for 20.8.0

doing test run = false
update log will be in /home/junior/MagicMirror/installers/upgrade.log
Check current Node installation …
Node currently installed. Checking version number.
Minimum Node version: v20.8.0
Installed Node version: v20.5.1
Node should be upgraded.
Installing Node.js …
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
nodejs is already the newest version (20.5.1-deb-1nodesource1).
The following packages were automatically installed and are no longer required:
libfuse2 raspinfo
Use ‘sudo apt autoremove’ to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
node version is
Node.js installation Done! version=v20.5.1
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.