Cannot create new image on installed NVME

Good Morning!
Today I have tried to install my Volumio on a NVME disk.
First install went fine, was able to install, configure and ran Volumio.
After first setup (re-login) I’ve tried to install touchscreen plugin because a screen is connected locally.
After this system didn’t come up…

Unfortunately I’ve forgotten to enable ssh so I’m currently not able to connect to the system.
My idea for a re-vitalize is to install a new image over the already installed.
This doesn’t work - the process started but interrupts at 60% without an error message.

Logfile is here: http://logs.volumio.org/volumio/jHHNkUT.html

Can please anybody help me?
I want to avoid to decompile the hardware because it’s build in in a tiny chassis with complicated structure and I would have to remove lots of screws and GPIO cables (because I’m using rotary encoder…) …

Thanks for any hint!

Warmest regards,
Ralf
(Volumio 3.799 on Raspberry 5, HiFiBerry DAC 2 pro, Waveshare 7’’ Capacitive Touch Display (DSI))

Hey @rkorell,

Log you posted is confirming:

Apr 29 10:18:30 korellmusik volumio[1335]: info: Progress: 80
Apr 29 10:18:30 korellmusik systemd[1]: tmp-work-from.mount: Succeeded.
Apr 29 10:18:30 korellmusik systemd[1]: tmp-work-final.mount: Succeeded.
Apr 29 10:18:30 korellmusik volumio[1335]: info: Progress: 85
Apr 29 10:18:31 korellmusik volumio[1335]: info: Progress: 99
Apr 29 10:18:31 korellmusik systemd[1]: tmp-boot.mount: Succeeded.
Apr 29 10:18:31 korellmusik systemd[1]: tmp-volumio.mount: Succeeded.
Apr 29 10:18:32 korellmusik kernel: EXT4-fs (nvme0n1p2): unmounting filesystem 46fca46a-75ba-4a9c-a92e-20f66406e0cf.
Apr 29 10:18:33 korellmusik sudo[2240]: pam_unix(sudo:session): session closed for user root
Apr 29 10:18:33 korellmusik volumio[1335]: info: Successfully installed x86 factory copy to disk/dev/nvme0n1
Apr 29 10:18:33 korellmusik volumio[1335]: info: CoreCommandRouter::executeOnPlugin: networkfs , enableDeviceActions

Since:

… korellmusik volumio[1335]: info: Successfully installed … to disk/dev/nvme0n1…

Did you try to boot from it?

Kind Regards,

Dear @nerd , thanks for your advice!
No, didn’t try this before your hint…
Have installed “successfully” with 6th attempt just in this moment - and now I DO have rebooted - works :slight_smile:

Do you have an idea why system didn’t come up after installing “touch display” ?

Many thanks & warmest regards,
Ralf

(For your information: reason of NVME is my trial to install your bookworm alpha to provide some information to you - will primarily install on SD-card if it works …)

Hey @rkorell,

The KMS needs to read screen geometry. Have you added corresponding dtoverlay to /boot/userconfig.txt like you did for current Volumio?

Touch Display plugin maintainer is looking into this: caused by Google’s change from manifest v2 to manifest v3 while the keyboard extension is still on v2 (chrome-virtual-keyboard/manifest.json at master · xontab/chrome-virtual-keyboard · GitHub). However, problem reported is with on screen keyboard and mouse pointer.

Kind Regards,

Dear @nerd ,
OK; this sounds reasonable but I haven’t considered this during first attempt.
Now, at second attempt - I had remembered these dtoverlay changes and did made these changes before installing the plugin.
You are REALLY great!
THANKS a LOT!

Screen keyboard as well as mouse pointer are not in my use-case so these difficulties don’t appear…
Now I have to setup the other plugins for my “base” installation and hopefully find some time for alpha-testing bookworm…
(I’m curious if “now playing” plugin works there - to my big surprise it now works on the just installed V 3.799 - which was not the case earlier on the already given 3.799 SD-card installation).

1 Like