Problems with Install - Cant get anything to work

Hoping someone can tell me were the hell I’m going wrong here
I’m probably re-flashed 10 or more times now!

Some background on my setup.

Raspberry Pi 3 Model B V2 2015
Official 7" Touchscreen

I’ve used both 1TB and 32GB SSD cards

Previously working with Rune and have also used Max2Play without problems.

Where I’m at - I have tried the following with both the 1TB and the 32GB cards same outcome

Flash the card, insert into the pi and boot, all boots normally and wait till i get to the login prompt on the display.
I can now access the web interface and go through the initial setup. I have tried connecting to my WiFi and while it says connected there’s nothing after I restart.
At the moment I’m leaving out connecting to WiFi and just trying to use the hotspot.
I’ve changed the default P/W. I can see the access point and can test connect.
I’ve enabled SSH via the dev menu and can connect using Putty.
Initial connections over Ethernet is fine.

At this point everything is fine, so I’m using the shutdown button on the web ui to close everything down as eventually everything needs to be moved into a wall mounted frame. I’m waiting about 10 Mins before removing the power.

On powering backup I get the following

Everything looks ok and you get to the login prompt, however at this point:

I Have no Web Ui, error is server cannot be found.
Hotspot has disappeared.
SSH juts gives connection rejected.
You can ping the Pi but thats it.

All I can do at this point is use a USB keyboard and login.
If i shutdown at this point I just get a corrupt filesystem on restart and a dead system.

So anyone tell me where i’m going wrong, everything I can see on the web says this is an easy to set up and use system and it look perfect for what I want.

Firstly, don’t change the default password … it’s not ideal, but it will cause problems with plugins.

Secondly, after your reboot from an apparently working system, connect your keyboard, and type ‘ip addr’ to get some info on what’s happening with networking. . You can also look at the system logs with the command ‘sudo journalctl -b’. You could also repeat the journalctl and send the info to a file ‘sudo journalctl -b > mylog.log’. This can either be transferred directly to your Windows machine via ‘scp’ or some other file transfer protocol, or you could type ‘cp mylog.log /mnt/INTERNAL’ which will copy the log to a Samba share that you should be able to access from WIndows. Sorry it’s so complex, but if you don’t have access to the GUI, then you can’t automatically generate a log, and you obviously said that ssh wasn’t working either.

I suspect that you are doing something wrong here in your installation, but it is impossible to tell what from your description. Have you altered anything else other than the default password? No attempt at a system update? No other software installed? Have a look at the ‘Quick Start’ link in my signature, and other documentation (linked at the bottom of the forum) to go through step by step your installation procedure with the correct one.

Let us know how you get on.

My guess is that your system is low on power.
The 7’’ display consumes lot of power and if you add a 1TB HDD you will ask too much current to the PI, which results in SD card corruption.

I suggest:

  • Use the system without display, and see if it survives a reboot
  • If it does, add the display, and see if it works
  • If it works, add the HDD

You will see what kills your system this way.

When you found out who is responsible for the high power consumption, power it separately.

Thanks for the info - I’ll get on it ASAP. For the record its not a 1TB HDD its just a 1TB SSD. I was hoping to have everything on the card (partially as i’d reasoned that would be better power wise)

I’ll go through the suggestions and report back soon as a I can, thanks for the quick responses.

SSD using a lot less power than an HDD is what you might expect looking at the lack of moving parts.
But that is only half the story, in a lot of cases the small difference will surprise you.

Google it and you will find plenty of articles wrt this issue.

First off I’ve completely disconnected the touch screen, re-flashed and started again. As far as setup goes its just next,next,next etc. No connecting to WiFi or changing anything. Only thing I have done other than run through the initial setup screens is go into dev and enable SSH.

By leaving the hotspot p/w as default the hotspot survived the 1st power off/restart. However that was the only change. I still have no Web UI, nor can i SSH after a reboot. Connecting over ethernet or connecting to the hotspot is the same result

Obviously without the display I cant go any further at this stage and not having an hdmi screen I can use at the i could only pull the plug at this point.

What I have done is reconnected the touchscreen with just the ribon cable and powered it separately from a usb port on my laptop (not ideal but it works). This has allowed me to run through everything again and get a log file as you’ve described (although at over 31000 line long I’ve no idea what I’m looking at)

If you can tell me what to look for I’ll start trawling the log.

As far as the IP goes the IP shown for ETH0 on the Pi is the same as I get if I ping -a volumio.local

Also As i’m not convinced about the power supply I’m using, I’ve ordered an official 2.5A PI Power Supply from Amazon that should be here tomorrow, I’ll see if that helps

OK Update at last

1st Power supply was DOA, replacement arrived today.

Setup system again with screen attached. Re-Flashed and Powered up.
No colored squares indicating power issues, no lighting bolts or messages about low power (we had the lighting bolt and a warning about low power with the previous power supply)

Boot sequence shows its 5 Phases, thne message about extending filesystem. Finally a filesystem display before the Volumio splash screen and the the login prompt.

Using Ethernet cable between laptop and Pi can connect to volumio.local in firefox.
Walk through initial setup just choosing next, leaving all defaults intact. Do not try and connect to WiFi
Access Dev screen and enable SSH.

Check SSH access is working ok.
Connect to volumio WiFI hotspot. PC connects but cannot connect to volumio.local if the ethernet cable is disconnected. Tried ipconfig /flushdns still no access cant ping volumio.local.
Re-Connect Ethernet cable and access is restored.

Powered down Pi from volumio webpage.

Wait 5 Mins, can only see red light on Pi showing no disk access. Power on Pi , wait till I see splash screen then get login prompt.
System is then as all other previous times. No Webaccess, no SSH access, can connect to hotspot but makes no difference. Can ping volumio.local but only via ethernet.

Use USB keyboard and log on

ip addr shows IP address for ETH0 is what I see if I ping -a volumio.local on the laptop.

I can produce a logfile with journalctl -b. After transferring this back to the laptop, notepad++ says is now only 13000 lines long :slight_smile:

looking at it with my untrained eye there seams to be a lot of things repeated after the second power on. Below is what appears to be the repeated lines. I can email the whole log if it will help. I’ve tried attaching it but every time and no matter what name I try I just get The Extension is not allowed.

Nov 03 15:11:27 volumio volumio[5417]: info: -------------------------------------------
Nov 03 15:11:27 volumio volumio[5417]: info: ----- Volumio2 ----
Nov 03 15:11:27 volumio volumio[5417]: info: -------------------------------------------
Nov 03 15:11:27 volumio volumio[5417]: info: ----- System startup ----
Nov 03 15:11:27 volumio volumio[5417]: info: -------------------------------------------
Nov 03 15:11:27 volumio volumio[5417]: info: Found new core plugin music_service/airplay_emulation. Adding it
Nov 03 15:11:27 volumio volumio[5417]: info: Found new core plugin music_service/mpd. Adding it
Nov 03 15:11:27 volumio volumio[5417]: info: Found new core plugin music_service/webradio. Adding it
Nov 03 15:11:27 volumio volumio[5417]: info: Found new core plugin music_service/example_plugin. Adding it
Nov 03 15:11:27 volumio volumio[5417]: info: Found new core plugin music_service/last_100. Adding it
Nov 03 15:11:27 volumio volumio[5417]: info: Found new core plugin music_service/upnp_browser. Adding it
Nov 03 15:11:27 volumio volumio[5417]: info: Found new core plugin audio_interface/upnp. Adding it
Nov 03 15:11:27 volumio volumio[5417]: info: Found new core plugin audio_interface/alsa_controller. Adding it
Nov 03 15:11:27 volumio volumio[5417]: info: Found new core plugin miscellanea/alarm-clock. Adding it
Nov 03 15:11:27 volumio volumio[5417]: info: Found new core plugin miscellanea/albumart. Adding it
Nov 03 15:11:27 volumio volumio[5417]: info: Found new core plugin miscellanea/appearance. Adding it
Nov 03 15:11:27 volumio volumio[5417]: info: Found new core plugin miscellanea/wizard. Adding it
Nov 03 15:11:27 volumio volumio[5417]: info: Found new core plugin miscellanea/my_music. Adding it
Nov 03 15:11:27 volumio volumio[5417]: info: Found new core plugin user_interface/websocket. Adding it
Nov 03 15:11:27 volumio volumio[5417]: info: Found new core plugin user_interface/mpdemulation. Adding it
Nov 03 15:11:27 volumio volumio[5417]: info: Found new core plugin user_interface/rest_api. Adding it
Nov 03 15:11:27 volumio volumio[5417]: info: Found new core plugin system_controller/updater_comm. Adding it
Nov 03 15:11:27 volumio volumio[5417]: info: Found new core plugin system_controller/network. Adding it
Nov 03 15:11:27 volumio volumio[5417]: info: Found new core plugin system_controller/networkfs. Adding it
Nov 03 15:11:27 volumio volumio[5417]: info: Found new core plugin system_controller/services. Adding it
Nov 03 15:11:27 volumio volumio[5417]: info: Found new core plugin system_controller/system. Adding it
Nov 03 15:11:27 volumio volumio[5417]: info: Found new core plugin system_controller/i2s_dacs. Adding it
Nov 03 15:11:27 volumio volumio[5417]: info: Found new core plugin system_controller/volumiodiscovery. Adding it
Nov 03 15:11:27 volumio volumio[5417]: info: Found new core plugin system_controller/volumio_command_line_client. Adding it
Nov 03 15:11:27 volumio volumio[5417]: info: Plugin folders cleanup
Nov 03 15:11:27 volumio volumio[5417]: info: Scanning into folder /volumio/app/plugins/
Nov 03 15:11:27 volumio volumio[5417]: info: Scanning category audio_interface
Nov 03 15:11:27 volumio volumio[5417]: info: Scanning category miscellanea
Nov 03 15:11:27 volumio volumio[5417]: info: Scanning category music_service
Nov 03 15:11:27 volumio volumio[5417]: info: Scanning category plugins.json
Nov 03 15:11:27 volumio volumio[5417]: info: Scanning category system_controller
Nov 03 15:11:27 volumio volumio[5417]: info: Scanning category user_interface
Nov 03 15:11:27 volumio volumio[5417]: info: Scanning into folder /data/plugins/
Nov 03 15:11:27 volumio volumio[5417]: info: Plugin folders cleanup completed
Nov 03 15:11:27 volumio volumio[5417]: info: -------------------------------------------
Nov 03 15:11:27 volumio volumio[5417]: info: ----- Core plugins startup ----
Nov 03 15:11:27 volumio volumio[5417]: info: -------------------------------------------
Nov 03 15:11:27 volumio volumio[5417]: info: Loading plugins from folder /volumio/app/plugins/
Nov 03 15:11:27 volumio volumio[5417]: info: Adding plugin upnp to MyMusic Plugins
Nov 03 15:11:27 volumio volumio[5417]: info: Adding plugin airplay_emulation to MyMusic Plugins
Nov 03 15:11:27 volumio volumio[5417]: info: Adding plugin upnp_browser to MyMusic Plugins
Nov 03 15:11:27 volumio volumio[5417]: info: Loading plugins from folder /data/plugins/
Nov 03 15:11:27 volumio volumio[5417]: info: Loading plugin “system”…
Nov 03 15:11:27 volumio volumio[5417]: No id defined. Creating one
Nov 03 15:11:27 volumio volumio[5417]: info: Loading plugin “appearance”…
Nov 03 15:11:28 volumio volumio[5417]: info: Loading plugin “network”…
Nov 03 15:11:28 volumio volumio[5417]: info: Loading plugin “services”…
Nov 03 15:11:28 volumio volumio[5417]: info: Loading plugin “alsa_controller”…
Nov 03 15:11:29 volumio volumio[5417]: info: CoreCommandRouter::volumioUpdateVolumeSettings
Nov 03 15:11:29 volumio volumio[5417]: info: CoreCommandRouter::executeOnPlugin: i2s_dacs , getI2sStatus
Nov 03 15:11:29 volumio volumio[5417]: info: Found match in Cards Database: setting mixer PCM for card Audio Jack
Nov 03 15:11:29 volumio volumio[5417]: info: CoreCommandRouter::volumioUpdateVolumeSettings
Nov 03 15:11:29 volumio volumio[5417]: info: CoreCommandRouter::volumioUpdateVolumeSettings
Nov 03 15:11:29 volumio volumio[5417]: info: CoreCommandRouter::volumioUpdateVolumeSettings
Nov 03 15:11:29 volumio volumio[5417]: info: Loading plugin “wizard”…
Nov 03 15:11:29 volumio volumio[5417]: info: Loading plugin “volumio_command_line_client”…
Nov 03 15:11:29 volumio volumio[5417]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam
Nov 03 15:11:29 volumio volumio[5417]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam
Nov 03 15:11:29 volumio volumio[5417]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam
Nov 03 15:11:29 volumio volumio[5417]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam
Nov 03 15:11:29 volumio volumio[5417]: info: Loading plugin “upnp”…
Nov 03 15:11:29 volumio volumio[5417]: info: [1541257889209] Starting Upmpd Daemon
Nov 03 15:11:29 volumio volumio[5417]: info: CoreCommandRouter::executeOnPlugin: system , registerCallback
Nov 03 15:11:29 volumio volumio[5417]: info: Loading plugin “my_music”…
Nov 03 15:11:29 volumio volumio[5417]: info: Loading plugin “mpd”…
Nov 03 15:11:29 volumio volumio[5417]: info: Loading plugin “upnp_browser”…
Nov 03 15:11:30 volumio volumio[5417]: info: Loading plugin “networkfs”…
Nov 03 15:11:30 volumio volumio[5417]: info: CoreCommandRouter::executeOnPlugin: system , registerCallback
Nov 03 15:11:30 volumio volumio[5417]: info: Loading plugin “alarm-clock”…
Nov 03 15:11:30 volumio volumio[5417]: info: Loading plugin “airplay_emulation”…
Nov 03 15:11:30 volumio volumio[5417]: info: Starting Shairport Sync
Nov 03 15:11:30 volumio volumio[5417]: info: Loading plugin “last_100”…
Nov 03 15:11:30 volumio volumio[5417]: info: Loading plugin “webradio”…
Nov 03 15:11:30 volumio volumio[5417]: info: Loading plugin “i2s_dacs”…
Nov 03 15:11:30 volumio volumio[5417]: info: I2S DAC not set, start Auto-detection
Nov 03 15:11:30 volumio volumio[5417]: info: Loading plugin “volumiodiscovery”…
Nov 03 15:11:30 volumio volumio[5417]: *** WARNING *** The program ‘node’ uses the Apple Bonjour compatibility layer of Avahi.
Nov 03 15:11:30 volumio node[5417]: *** WARNING *** The program ‘node’ uses the Apple Bonjour compatibility layer of Avahi.
Nov 03 15:11:30 volumio node[5417]: *** WARNING *** Please fix your application to use the native API of Avahi!
Nov 03 15:11:30 volumio node[5417]: *** WARNING *** For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=node
Nov 03 15:11:30 volumio node[5417]: *** WARNING *** The program ‘node’ called ‘DNSServiceRegister()’ which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
Nov 03 15:11:30 volumio node[5417]: *** WARNING *** Please fix your application to use the native API of Avahi!
Nov 03 15:11:30 volumio node[5417]: *** WARNING *** For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=node&f=DNSServiceRegister
Nov 03 15:11:30 volumio volumio[5417]: *** WARNING *** Please fix your application to use the native API of Avahi!
Nov 03 15:11:30 volumio volumio[5417]: *** WARNING *** For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=node
Nov 03 15:11:30 volumio volumio[5417]: *** WARNING *** The program ‘node’ called ‘DNSServiceRegister()’ which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
Nov 03 15:11:30 volumio volumio[5417]: *** WARNING *** Please fix your application to use the native API of Avahi!
Nov 03 15:11:30 volumio volumio[5417]: *** WARNING *** For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=node&f=DNSServiceRegister
Nov 03 15:11:30 volumio volumio[5417]: info: Applying required configuration parameters for plugin volumiodiscovery
Nov 03 15:11:30 volumio volumio[5417]: Discovery: StartAdv! undefined
Nov 03 15:11:30 volumio volumio[5417]: Discovery: Started advertising… undefined - undefined
Nov 03 15:11:30 volumio volumio[5417]: info: CoreCommandRouter::executeOnPlugin: system , registerCallback
Nov 03 15:11:30 volumio volumio[5417]: info: Loading plugin “albumart”…
Nov 03 15:11:30 volumio volumio[5417]: info: Plugin example_plugin is not enabled
Nov 03 15:11:30 volumio volumio[5417]: info: Loading plugin “updater_comm”…
Nov 03 15:11:30 volumio volumio[5417]: info: Plugin mpdemulation is not enabled
Nov 03 15:11:30 volumio volumio[5417]: info: Loading plugin “rest_api”…
Nov 03 15:11:30 volumio volumio[5417]: info: Loading plugin “websocket”…
Nov 03 15:11:30 volumio volumio[5417]: info: ___________ START PLUGINS ___________
Nov 03 15:11:30 volumio volumio[5417]: info: CoreCommandRouter::executeOnPlugin: mpd , getConfigParam
Nov 03 15:11:30 volumio volumio[5417]: info: CoreCommandRouter::volumioAddToBrowseSources[object Object]
Nov 03 15:11:30 volumio volumio[5417]: info: [1541257890788] CoreMusicLibrary::Adding element Media Servers
Nov 03 15:11:30 volumio volumio[5417]: info: CoreCommandRouter::volumioAddToBrowseSources[object Object]
Nov 03 15:11:30 volumio volumio[5417]: info: [1541257890817] CoreMusicLibrary::Adding element Last_100
Nov 03 15:11:30 volumio volumio[5417]: info: CoreCommandRouter::volumioAddToBrowseSources[object Object]
Nov 03 15:11:30 volumio volumio[5417]: info: [1541257890820] CoreMusicLibrary::Adding element Webradio
Nov 03 15:11:30 volumio volumio[5417]: info: CoreCommandRouter::executeOnPlugin: system , getSystemVersion
Nov 03 15:11:30 volumio volumio[5417]: info: -------------------------------------------
Nov 03 15:11:30 volumio volumio[5417]: info: ----- MyVolumio plugins startup ----
Nov 03 15:11:30 volumio volumio[5417]: info: -------------------------------------------
Nov 03 15:11:30 volumio volumio[5417]: info: Loading plugins from folder /myvolumio/plugins
Nov 03 15:11:30 volumio volumio[5417]: info: Loading plugins from folder /data/myvolumio/plugins
Nov 03 15:11:30 volumio volumio[5417]: info: Loading i18n strings for locale undefined
Nov 03 15:11:30 volumio volumio[5417]: /volumio/node_modules/fs-extra/node_modules/jsonfile/index.js:73
Nov 03 15:11:30 volumio volumio[5417]: throw err
Nov 03 15:11:30 volumio volumio[5417]: ^
Nov 03 15:11:30 volumio volumio[5417]: Error: /volumio/app/i18n/strings_undefined.json: ENOENT: no such file or directory, open ‘/volumio/app/i18n/strings_undefined.json’
Nov 03 15:11:30 volumio volumio[5417]: at Object.fs.openSync (fs.js:646:18)
Nov 03 15:11:30 volumio volumio[5417]: at Object.fs.readFileSync (fs.js:551:33)
Nov 03 15:11:30 volumio volumio[5417]: at Object.readFileSync (/volumio/node_modules/fs-extra/node_modules/jsonfile/index.js:67:22)
Nov 03 15:11:30 volumio volumio[5417]: at CoreCommandRouter.loadI18nStrings (/volumio/app/index.js:1580:25)
Nov 03 15:11:30 volumio volumio[5417]: at new CoreCommandRouter (/volumio/app/index.js:64:10)
Nov 03 15:11:30 volumio volumio[5417]: at Object. (/volumio/index.js:35:21)
Nov 03 15:11:30 volumio volumio[5417]: at Module._compile (module.js:652:30)
Nov 03 15:11:30 volumio volumio[5417]: at Object.Module._extensions…js (module.js:663:10)
Nov 03 15:11:30 volumio volumio[5417]: at Module.load (module.js:565:32)
Nov 03 15:11:30 volumio volumio[5417]: at tryModuleLoad (module.js:505:12)
Nov 03 15:11:30 volumio volumio[5417]: at Function.Module._load (module.js:497:3)
Nov 03 15:11:30 volumio volumio[5417]: at Function.Module.runMain (module.js:693:10)
Nov 03 15:11:30 volumio volumio[5417]: at startup (bootstrap_node.js:188:16)
Nov 03 15:11:30 volumio volumio[5417]: at bootstrap_node.js:609:3
Nov 03 15:11:30 volumio systemd[1]: volumio.service: main process exited, code=exited, status=1/FAILURE
Nov 03 15:11:30 volumio systemd[1]: Unit volumio.service entered failed state.
Nov 03 15:11:30 volumio systemd[1]: Starting dynamicswap service…
Nov 03 15:11:30 volumio systemd[1]: Started dynamicswap service.
Nov 03 15:11:30 volumio volumio-remote-updater[642]: [2018-11-03 15:11:30] [info] asio async_connect error: system:111 (Connection refused)
Nov 03 15:11:30 volumio volumio-remote-updater[642]: [2018-11-03 15:11:30] [info] Error getting remote endpoint: system:107 (Transport endpoint is not connected)
Nov 03 15:11:30 volumio volumio-remote-updater[642]: [2018-11-03 15:11:30] [error] handle_connect error: Underlying Transport Error
Nov 03 15:11:31 volumio systemd[1]: volumio.service holdoff time over, scheduling restart.
Nov 03 15:11:31 volumio systemd[1]: Starting dynamicswap service…
Nov 03 15:11:31 volumio systemd[1]: Started dynamicswap service.
Nov 03 15:11:31 volumio systemd[1]: Stopping Volumio Backend Module…
Nov 03 15:11:31 volumio systemd[1]: Starting Volumio Backend Module…
Nov 03 15:11:31 volumio systemd[1]: Started Volumio Backend Module.

Thank you very much for the logs! I was able to spot the issue (it’s an edge case that results from a strange interaction from your browser). I will add the fix to next release.

In the meanwhile to solve it you can do this: flash a new image, go trough the first install wizard. Before restarting, go to appearance and set language to english. After reboot it will survive :wink:

Tanks for the reply

I’ve just flashed with the latest build and done as suggested, unfortunately its made no difference ( I didn’t even enable SSH)

Guess I’ll wait for the fix and see what happens