Library update: Seems to crash Volumio on Raspi

Hi again,
I just updated two of my Volumio boxes to the latest Volumio2 . . . after adjusting the settings I did the last step and added my library as nfs mount.

Okay, it is around 1TB . . . .

The boxes seems to start the update but then the even disappear from the network. The WebUI shows the circling balls and that’s it so far. No answer to ping . . . I tend to leave them alone for the night.
I am not exactly sure which Raspi Models I have there, I believe one is a Model B the other a B+.
Of course I cannot access them with ssh even if I try . . . there is no network connection.
Is it possible that the update uses all the resources the poor Raspi can provide

cheers
T

ok. . .update: the WebUI now crashed/disappeared with the expected "host unreachable "message.

I modified the “library” to one folder/album only . . . same issue, after some time the connection just seem to collapse

Update:
I changed the mount to cifs now, as the nfs it mounts ( somehow) but when attempting to read the data Volumio dies . . . it seems that the connection stays for quite some time but then of course the ssh is closed as well.
Both Raspi boxes are connected to 100MBPS LAN . . .
The Raspi LEDs still show that there might be some activity but . . . .
Any ideas ?

here is some info:
github.com/volumio/Volumio2/issues/777

Issue #777 is a different problem, not related to what Torsten reported.
The alignment issue happens on armv7 (non-PI platforms) only and is being fixed right now.

– Gé –

Would it be possible for you to look at the journal logs (sudo journalctl -b) and see if there are any reported problems. Alternatively, you can send the logs via the “dev” interface to the Volumio UI (192.168.x.xx/dev), including your username for reference.

Hi again,

jepp I will setup another box to get the log. Not quite understood what the “dev” interface actually is but I am sure I will figure it out once I have the Volumio2 installed again. ( I moved back to 1.55 for now … since no music is not a solution :wink: )

So, it might require some time . . .

cheers
T

I have almost same problem with CuBox-i4Pro.

My NAS is detected and I added the library path. Than it scan it…(not a very big library)…Once finished scanning it collapses with turning icon wheel. When I refresh the browser it says “no connection” and I have to reboot Cubox.

I repeated this for several times.

Hi Daniel,
you probably have the above mentioned issue #777, which you can confirm when you are able to ssh into your cubox and do sudo journalctl -f before you start scanning. When you look at the logfile, chances are that you will will find an error “Alignment fault”.
In that case, the issue has been fixed and you need to wait a few days as we are generating a new cubox Image.

– Gé –

Well, I didn’t figure it out to be honest.
I wanted to attach a log here instead but I was not allowed ( the extension blablabla is not allowed )
So how do I do this ?

cheers
T

There is an option to upload attachments on the forum (at bottom of reply), but I don’t know what limitations there are. You can cut and paste text as an alternative.

(The “dev” log thing is very simple, but perhaps I wasn’t clear enough. Enter your normal IP address for Volumio, and add “/dev” to the end of it. This will take you to a page with various things, one of which is “Send a log”).

I was on the “dev” page but it is not transparent to see what I am actually sending . . .actually I did it and sent a log twice, not sure if it was a sufficient one.

logs.volumio.org/volumio/cRjgOwy.html
and
logs.volumio.org/volumio/9Mvy56F.html

Uploading an attachment failed since it constantly complained about extensions ( tried txt, log, none, and even no extension )
Copy paste is of course an option but then I would need to select prior to do this otherwise it will reach the limitations of the message body.

As of now after starting to populate the library the box is again hanging an unreachable I watched it with journalctl -f
it stopped for a while and then came back

Apr 03 14:50:53 volumio mpd[517]: update: added NAS/Musik/Chiquinho Do Acordeon/Concerto para acordeão_ Allegro Moderato.mp3 Apr 03 14:52:52 volumio systemd-journal[154]: Missed 3340 kernel messages Apr 03 14:52:52 volumio kernel: [<c057163c>] (schedule_hrtimeout_range_clock) from [<c05716d0>] (schedule_hrtimeout_range+0x1c/0x20) Apr 03 14:52:52 volumio kernel: [<c05716d0>] (schedule_hrtimeout_range) from [<c017104c>] (SyS_epoll_wait+0x344/0x498) Apr 03 14:52:52 volumio kernel: [<c017104c>] (SyS_epoll_wait) from [<c000f820>] (ret_fast_syscall+0x0/0x1c) Apr 03 14:52:52 volumio kernel: Mem-Info: Apr 03 14:52:52 volumio kernel: active_anon:14196 inactive_anon:15725 isolated_anon:0 active_file:9467 inactive_file:9478 isolated_file:2 unevictable:0 dirty:0 writeback:0 unstable:0 slab_reclaimable:2180 slab_unreclaimable:1826 mapped:5606 shmem:377 pagetables:603 bounce:0 free:884 free_pcp:19 free_cma:712 Apr 03 14:52:52 volumio kernel: Normal free:3536kB min:1932kB low:2412kB high:2896kB active_anon:56784kB inactive_anon:62900kB active_file:37868kB inactive_file:37912kB unevictable:0kB isolated(anon):0kB isolated(file):8kB present:245760kB managed:234204kB mlocked:0kB dirty:0kB writeback:0kB mapped:22424kB shmem:1508kB slab_reclaimable:8720kB slab_unreclaimable:7304kB kernel_stack:1176kB pagetables:2412kB unstable:0kB bounce:0kB free_pcp:76kB local_pcp:76kB free_cma:2848kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no Apr 03 14:52:52 volumio kernel: lowmem_reserve[]: 0 0 Apr 03 14:52:52 volumio kernel: Normal: 136*4kB (MEC) 118*8kB (MC) 40*16kB (C) 18*32kB (C) 5*64kB (C) 4*128kB (C) 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 3536kB Apr 03 14:52:52 volumio kernel: 20254 total pagecache pages Apr 03 14:52:52 volumio kernel: 162 pages in swap cache Apr 03 14:52:52 volumio kernel: Swap cache stats: add 3766, delete 3604, find 462/537 Apr 03 14:52:52 volumio kernel: Free swap = 511012kB Apr 03 14:52:52 volumio kernel: Total swap = 524284kB Apr 03 14:52:52 volumio kernel: 61440 pages RAM Apr 03 14:52:52 volumio kernel: 0 pages HighMem/MovableOnly Apr 03 14:52:52 volumio kernel: 2889 pages reserved Apr 03 14:52:52 volumio kernel: 2048 pages cma reserved Apr 03 14:52:52 volumio kernel: smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped Apr 03 14:52:53 volumio kernel: node: page allocation failure: order:0, mode:0x2080020 Apr 03 14:52:53 volumio kernel: CPU: 0 PID: 1108 Comm: node Not tainted 4.4.9+ #884 Apr 03 14:52:53 volumio kernel: Hardware name: BCM2708 Apr 03 14:52:53 volumio kernel: [<c0016c9c>] (unwind_backtrace) from [<c0013c20>] (show_stack+0x20/0x24) Apr 03 14:52:53 volumio kernel: [<c0013c20>] (show_stack) from [<c02e319c>] (dump_stack+0x20/0x28) Apr 03 14:52:53 volumio kernel: [<c02e319c>] (dump_stack) from [<c00de5bc>] (warn_alloc_failed+0xe4/0x130) Apr 03 14:52:53 volumio kernel: [<c00de5bc>] (warn_alloc_failed) from [<c00e1aa0>] (__alloc_pages_nodemask+0x8a8/0xa8c) Apr 03 14:52:53 volumio kernel: [<c00e1aa0>] (__alloc_pages_nodemask) from [<c00e1eac>] (__alloc_page_frag+0x160/0x190) Apr 03 14:52:53 volumio kernel: [<c00e1eac>] (__alloc_page_frag) from [<c04870d8>] (__netdev_alloc_skb+0xa4/0x14c) Apr 03 14:52:53 volumio kernel: [<c04870d8>] (__netdev_alloc_skb) from [<c03c630c>] (rx_submit+0x3c/0x240) Apr 03 14:52:53 volumio kernel: [<c03c630c>] (rx_submit) from [<c03c69d8>] (rx_complete+0x1f8/0x21c) Apr 03 14:52:53 volumio kernel: [<c03c69d8>] (rx_complete) from [<c03d07a4>] (__usb_hcd_giveback_urb+0x80/0x160) Apr 03 14:52:53 volumio kernel: [<c03d07a4>] (__usb_hcd_giveback_urb) from [<c03d08cc>] (usb_hcd_giveback_urb+0x48/0x10c) Apr 03 14:52:53 volumio kernel: [<c03d08cc>] (usb_hcd_giveback_urb) from [<c03f9e6c>] (completion_tasklet_func+0x6c/0x98) Apr 03 14:52:53 volumio kernel: [<c03f9e6c>] (completion_tasklet_func) from [<c04089dc>] (tasklet_callback+0x20/0x24) Apr 03 14:52:53 volumio kernel: [<c04089dc>] (tasklet_callback) from [<c0025c40>] (tasklet_hi_action+0x84/0xd8) Apr 03 14:52:53 volumio kernel: [<c0025c40>] (tasklet_hi_action) from [<c00252d8>] (__do_softirq+0x124/0x314) Apr 03 14:52:53 volumio kernel: [<c00252d8>] (__do_softirq) from [<c002581c>] (irq_exit+0xbc/0x11c) Apr 03 14:52:53 volumio kernel: [<c002581c>] (irq_exit) from [<c005a360>] (__handle_domain_irq+0x60/0xb8) Apr 03 14:52:53 volumio kernel: [<c005a360>] (__handle_domain_irq) from [<c0010748>] (handle_IRQ+0x2c/0x30) Apr 03 14:52:53 volumio kernel: [<c0010748>] (handle_IRQ) from [<c000940c>] (bcm2835_handle_irq+0x3c/0x58) Apr 03 14:52:53 volumio kernel: [<c000940c>] (bcm2835_handle_irq) from [<c0572184>] (__irq_svc+0x44/0x5c) Apr 03 14:52:53 volumio kernel: Exception stack(0xceb97da0 to 0xceb97de8) Apr 03 14:52:53 volumio kernel: 7da0: 00000000 00000002 00000000 c081cf74 00000000 ceb7d1c0 00000000 c88d6d00 Apr 03 14:52:53 volumio kernel: 7dc0: c056e9b4 0000002a c88d7050 ceb97e24 ceb97df0 ceb97df0 c0043ae0 c0043ae4 Apr 03 14:52:53 volumio kernel: 7de0: 60000013 ffffffff Apr 03 14:52:53 volumio kernel: [<c0572184>] (__irq_svc) from [<c0043ae4>] (finish_task_switch+0x60/0x1dc) Apr 03 14:52:53 volumio kernel: [<c0043ae4>] (finish_task_switch) from [<c056e9b4>] (__schedule+0x2b0/0x610) Apr 03 14:52:53 volumio kernel: [<c056e9b4>] (__schedule) from [<c056ed64>] (schedule+0x50/0xa8) Apr 03 14:52:53 volumio kernel: [<c056ed64>] (schedule) from [<c057163c>] (schedule_hrtimeout_range_clock+0xb0/0x128) Apr 03 14:52:53 volumio kernel: [<c057163c>] (schedule_hrtimeout_range_clock) from [<c05716d0>] (schedule_hrtimeout_range+0x1c/0x20) Apr 03 14:52:53 volumio kernel: [<c05716d0>] (schedule_hrtimeout_range) from [<c017104c>] (SyS_epoll_wait+0x344/0x498) Apr 03 14:52:53 volumio kernel: [<c017104c>] (SyS_epoll_wait) from [<c000f820>] (ret_fast_syscall+0x0/0x1c) Apr 03 14:52:53 volumio kernel: Mem-Info: Apr 03 14:52:53 volumio kernel: active_anon:14196 inactive_anon:15725 isolated_anon:0 active_file:9467 inactive_file:9478 isolated_file:2 unevictable:0 dirty:0 writeback:0 unstable:0 slab_reclaimable:2180 slab_unreclaimable:1826 mapped:5606 shmem:377 pagetables:603 bounce:0 free:884 free_pcp:19 free_cma:712

and continued also with

Apr 03 14:52:53 volumio kernel: Normal free:3536kB min:1932kB low:2412kB high:2896kB active_anon:56784kB inactive_anon:62900kB active_file:37868kB inactive_file:37912kB unevictable:0kB isolated(anon):0kB isolated(file):8kB present:245760kB managed:234204kB mlocked:0kB dirty:0kB writeback:0kB mapped:22424kB shmem:1508kB slab_reclaimable:8720kB slab_unreclaimable:7304kB kernel_stack:1176kB pagetables:2412kB unstable:0kB bounce:0kB free_pcp:76kB local_pcp:76kB free_cma:2848kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no Apr 03 14:52:53 volumio kernel: lowmem_reserve[]: 0 0 Apr 03 14:52:53 volumio kernel: Normal: 136*4kB (MEC) 118*8kB (MC) 40*16kB (C) 18*32kB (C) 5*64kB (C) 4*128kB (C) 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 3536kB Apr 03 14:52:53 volumio kernel: 20254 total pagecache pages Apr 03 14:52:53 volumio kernel: 162 pages in swap cache Apr 03 14:52:53 volumio kernel: Swap cache stats: add 3766, delete 3604, find 462/537 Apr 03 14:52:53 volumio kernel: Free swap = 511012kB Apr 03 14:52:53 volumio kernel: Total swap = 524284kB Apr 03 14:52:53 volumio kernel: 61440 pages RAM Apr 03 14:52:53 volumio kernel: 0 pages HighMem/MovableOnly Apr 03 14:52:53 volumio kernel: 2889 pages reserved Apr 03 14:52:53 volumio kernel: 2048 pages cma reserved Apr 03 14:52:53 volumio kernel: smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped Apr 03 14:52:53 volumio kernel: node: page allocation failure: order:0, mode:0x2080020 Apr 03 14:52:53 volumio kernel: CPU: 0 PID: 1108 Comm: node Not tainted 4.4.9+ #884 Apr 03 14:52:53 volumio kernel: Hardware name: BCM2708

another “red” headline

Apr 03 14:52:58 volumio kernel: smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped Apr 03 14:52:58 volumio kernel: CIFS VFS: Server HOSTSERVER has not responded in 120 seconds. Reconnecting... Apr 03 14:52:52 volumio mpd[517]: client: [1] closed Apr 03 14:52:53 volumio mpd[517]: client: [4] opened from ::ffff:127.0.0.1:38288 Apr 03 14:52:56 volumio mpd[517]: update: added NAS/Musik/Sukru Tunar/Bir Muhabbet Kusu.mp3 Apr 03 14:52:56 volumio mpd[517]: update: added NAS/Musik/João Gilberto/O amor, o sorriso e a flor/04 João Gilberto - Trevo de quatro folhas.mp3 Apr 03 14:52:56 volumio mpd[517]: update: added NAS/Musik/João Gilberto/O amor, o sorriso e a flor/09 João Gilberto - Corcovado.mp3 Apr 03 14:52:56 volumio mpd[517]: update: added NAS/Musik/João Gilberto/O amor, o sorriso e a flor/11 João Gilberto - Amor certinho.mp3 Apr 03 14:52:57 volumio mpd[517]: update: added NAS/Musik/João Gilberto/O amor, o sorriso e a flor/03 João Gilberto - Só em teus braços.mp3 Apr 03 14:52:57 volumio mpd[517]: update: added NAS/Musik/João Gilberto/O amor, o sorriso e a flor/10 João Gilberto - Discussão.mp3 Apr 03 14:52:57 volumio mpd[517]: update: added NAS/Musik/João Gilberto/O amor, o sorriso e a flor/06 João Gilberto - Um abraço no bonfá.mp3 Apr 03 14:52:57 volumio mpd[517]: update: added NAS/Musik/João Gilberto/Desafinado/19 Outra vez.mp3 Apr 03 14:52:57 volumio mpd[517]: update: added NAS/Musik/João Gilberto/Desafinado/10 Manhã de Carnaval.mp3 Apr 03 14:52:58 volumio mpd[517]: update: added NAS/Musik/João Gilberto/Desafinado/04 Meditação.mp3 Apr 03 14:52:58 volumio mpd[517]: update: added NAS/Musik/João Gilberto/Desafinado/02 Você e eu.mp3 Apr 03 14:52:59 volumio mpd[517]: update: added NAS/Musik/João Gilberto/Desafinado/11 O amor em paz.mp3 Apr 03 14:52:59 volumio mpd[517]: update: added NAS/Musik/João Gilberto/Desafinado/05 Samba de uma nota só.mp3 Apr 03 14:52:59 volumio mpd[517]: update: added NAS/Musik/João Gilberto/Desafinado/12 O barquinho.mp3 Apr 03 14:52:52 volumio systemd[1]: systemd-logind.service watchdog timeout (limit 1min)! Apr 03 14:52:53 vol

Then it continued to read some more folders . . . and ends with “broken pipe” error message on ssh . . . once the connection is dead like this I have to restart the device

From your uploaded logs the problem appears to occur without library scanning. You say you have tried it on more than one RPi, but I presume that is the same image. Can you download a fresh image & check it’s md5sum before flashing? Make sure that you leave the RPi alone for 10 mins on first boot.

you are right both got the same image.
I now downloaded it again and flashed again ( after checking MD5) the result is the same . . .
What I did now in addition I started sudo journactl -f > logfile

So now I have at least a huge log . . . how would I be able to upload it here ( the upload function does not allow me )
cheers
Torsten

BTW: Could it be that there is an issue with character coding in file or folder names? I do have quite some tracks in kyrillic and some with spanish characters.

This is the end of journalctl -f ( I was curious to see it again :slight_smile:) ) copied from the screen

Apr 04 14:04:16 volumio kernel: Mem-Info: Apr 04 14:04:16 volumio kernel: active_anon:4681 inactive_anon:15669 isolated_anon:0 active_file:11782 inactive_file:17405 isolated_file:32 unevictable:0 dirty:10 writeback:0 unstable:0 slab_reclaimable:2541 slab_unreclaimable:1898 mapped:6269 shmem:1688 pagetables:508 bounce:0 free:370 free_pcp:80 free_cma:195 Apr 04 14:04:16 volumio kernel: Normal free:1480kB min:1932kB low:2412kB high:2896kB active_anon:18724kB inactive_anon:62676kB active_file:47128kB inactive_file:69620kB unevictable:0kB isolated(anon):0kB isolated(file):128kB present:245760kB managed:234204kB mlocked:0kB dirty:40kB writeback:0kB mapped:25076kB shmem:6752kB slab_reclaimable:10164kB slab_unreclaimable:7592kB kernel_stack:1056kB pagetables:2032kB unstable:0kB bounce:0kB free_pcp:320kB local_pcp:320kB free_cma:780kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no Apr 04 14:04:16 volumio kernel: lowmem_reserve[]: 0 0 Apr 04 14:04:16 volumio kernel: Normal: 176*4kB (MC) 33*8kB (UMC) 22*16kB (MC) 5*32kB (C) 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 1480kB Apr 04 14:04:16 volumio kernel: 31928 total pagecache pages Apr 04 14:04:16 volumio kernel: 707 pages in swap cache Apr 04 14:04:16 volumio kernel: Swap cache stats: add 4705, delete 3998, find 645/767 Apr 04 14:04:16 volumio kernel: Free swap = 509860kB Apr 04 14:04:16 volumio kernel: Total swap = 524284kB Apr 04 14:04:16 volumio kernel: 61440 pages RAM Apr 04 14:04:16 volumio kernel: 0 pages HighMem/MovableOnly Apr 04 14:04:16 volumio kernel: 2889 pages reserved Apr 04 14:04:16 volumio kernel: 2048 pages cma reserved Apr 04 14:04:16 volumio kernel: smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped Apr 04 14:04:16 volumio systemd[1]: Starting Journal Service... Apr 04 14:04:16 volumio systemd[1]: systemd-logind.service watchdog timeout (limit 1min)! Apr 04 14:04:16 volumio systemd[1]: Unit systemd-logind.service entered failed state. Apr 04 14:04:16 volumio systemd[1]: systemd-logind.service has no holdoff time, scheduling restart. Apr 04 14:04:16 volumio systemd[1]: Stopping Login Service... Apr 04 14:04:16 volumio systemd[1]: Starting Login Service... Apr 04 14:04:16 volumio systemd[1]: Started Login Service. Apr 04 14:04:11 volumio systemd[1]: systemd-journald.service watchdog timeout (limit 1min)! Apr 04 14:04:12 volumio systemd-logind[1591]: New seat seat0. Apr 04 14:04:12 volumio systemd-logind[1591]: New session c1 of user volumio. Apr 04 14:04:17 volumio systemd-journal[1569]: Journal stopped Apr 04 14:04:17 volumio systemd-journal[1595]: Runtime journal is using 12.0M (max allowed 30.0M, trying to leave 17.1M free of 101.7M available → current limit 30.0M). Apr 04 14:04:17 volumio systemd-journald[1569]: Received SIGTERM from PID 1 (systemd). Apr 04 14:04:17 volumio systemd[1]: Unit systemd-journald.service entered failed state. Apr 04 14:04:17 volumio systemd[1]: systemd-journald.service has no holdoff time, scheduling restart. Apr 04 14:04:17 volumio systemd[1]: Stopping Journal Service... Apr 04 14:04:17 volumio systemd[1]: Starting Journal Service... Apr 04 14:04:17 volumio systemd[1]: Started Journal Service. Apr 04 14:04:17 volumio systemd-journal[1595]: Journal started Apr 04 14:04:17 volumio systemd[1]: Starting Trigger Flushing of Journal to Persistent Storage... Apr 04 14:04:17 volumio systemd[1]: Started Trigger Flushing of Journal to Persistent Storage. Apr 04 14:04:17 volumio mpd[472]: client: [7] opened from ::ffff:127.0.0.1:42322 Apr 04 14:04:17 volumio mpd[472]: client: [6] closed

cheers
T

Torsten,
I can see your logs from yesterday and internally copied the link for @chsims1
Will post it as a PM to you as well

– Gé –

Your logs are showing multiple error messages, which are not typical of a “normal” installation.

Can you please:

(1) confirm that you downloaded the Volumio software from here;

(2) give details of how you flashed the image to the sd card, and the sd card size;

(3) post the result of typing ‘cat /proc/cpuinfo’ from an ssh session.

P.S. Have you tried more than one sd card?

HI,

(1) confirm that you downloaded the Volumio software from here;
confirmed

(2) give details of how you flashed the image to the sd card, and the sd card size;
I used the etcher tool on my Linux computer to flash three different 8GB cards unfortunately all are same brand SanDisk Ultra

(3) post the result of typing ‘cat /proc/cpuinfo’ from an ssh session.

Volumio Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
volumio@volumio:~$ cat /proc/cpuinfo
processor	: 0
model name	: ARMv6-compatible processor rev 7 (v6l)
BogoMIPS	: 697.95
Features	: half thumb fastmult vfp edsp java tls 
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0xb76
CPU revision	: 7

Hardware	: BCM2708
Revision	: 0002
Serial		: 000000006495fa04
Volumio Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
volumio@volumio:~$ cat /proc/cpuinfo
processor	: 0
model name	: ARMv6-compatible processor rev 7 (v6l)
BogoMIPS	: 697.95
Features	: half thumb fastmult vfp edsp java tls 
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0xb76
CPU revision	: 7

Hardware	: BCM2708
Revision	: 0002
Serial		: 000000006495fa04

P.S. Have you tried more than one sd card?

Well, I flashed the same card with the same image but . . . used Ubuntu imagewriter now.

So far after booting a while ago and updating the library now . . .the system is still alive, even when I see a lot of error messages and it hangs from time to time . . . it is still populating the library

Ah ok, it becomes clearer. The RPi that you reported the cpuinfo for only has 256MB of RAM. Volumio needs a minimum of 512MB to run properly. Good excuse for an upgrade :smiley: ??