too bad,after 90 mins,still not work,
the wifi always show up,but never be connected
so i have to connect by wire to see if i can ssh,
ssh,ping is ok
but the wifi,web ui never ok
i will remove the hifi berry and try all over again
Sorry for that, we’re trying to understand what goes wrong on your systems, since on all my old pis it works without any issue…
thanks for all of your help
I’m waiting for another hour to see if any magic
Please let me know if i can provide any information to make it easy to trace what happen.
Yes, please connect via SSH and type
sudo journalctl -f
when you see errors happening please copy and paste them here
mi
Oct 26 16:35:06 volumio volumio[10190]: /volumio/node_modules/fs-extra/lib/mkdirs/mkdirs-sync.js:47
Oct 26 16:35:06 volumio volumio[10190]: throw err0
Oct 26 16:35:06 volumio volumio[10190]: ^
Oct 26 16:35:06 volumio volumio[10190]: Error: ENOSPC: no space left on device, mkdir ‘/data/albumart’
Oct 26 16:35:06 volumio volumio[10190]: at Error (native)
Oct 26 16:35:06 volumio volumio[10190]: at Object.fs.mkdirSync (fs.js:922:18)
Oct 26 16:35:06 volumio volumio[10190]: at mkdirsSync (/volumio/node_modules/fs-extra/lib/mkdirs/mkdirs-sync.js:29:9)
Oct 26 16:35:06 volumio volumio[10190]: at Object.mkdirsSync (/volumio/node_modules/fs-extra/lib/mkdirs/mkdirs-sync.js:35:16)
Oct 26 16:35:06 volumio volumio[10190]: at Object.setFolder (/volumio/app/plugins/miscellanea/albumart/albumart.js:29:8)
Oct 26 16:35:06 volumio volumio[10190]: at Object. (/volumio/index.js:17:10)
Oct 26 16:35:06 volumio volumio[10190]: at Module._compile (module.js:541:32)
Oct 26 16:35:06 volumio volumio[10190]: at Object.Module._extensions…js (module.js:550:10)
Oct 26 16:35:06 volumio volumio[10190]: at Module.load (module.js:458:32)
Oct 26 16:35:06 volumio volumio[10190]: at tryModuleLoad (module.js:417:12)
Oct 26 16:35:06 volumio systemd[1]: volumio.service: main process exited, code=exited, status=1/FAILURE
Oct 26 16:35:06 volumio systemd[1]: Unit volumio.service entered failed state.
Oct 26 16:35:06 volumio systemd[1]: Starting dynamicswap.service…
Oct 26 16:35:06 volumio systemd[1]: Started dynamicswap.service.
Oct 26 16:35:06 volumio volumio[10203]: 512 MB or less RAM Detected, need to enable swap
Oct 26 16:35:06 volumio volumio[10203]: Enabling Swap
Oct 26 16:35:06 volumio volumio[10203]: swapon: /data/swapfile: swapon failed: Device or resource busy
Oct 26 16:35:06 volumio systemd[1]: dynamicswap.service: main process exited, code=exited, status=255/n/a
Oct 26 16:35:06 volumio systemd[1]: Unit dynamicswap.service entered failed state.
Oct 26 16:35:06 volumio systemd[1]: volumio.service holdoff time over, scheduling restart.
Oct 26 16:35:06 volumio systemd[1]: Starting dynamicswap.service…
Oct 26 16:35:06 volumio systemd[1]: Started dynamicswap.service.
Oct 26 16:35:06 volumio systemd[1]: Stopping Volumio Backend Module…
Oct 26 16:35:06 volumio systemd[1]: Starting Volumio Backend Module…
Oct 26 16:35:06 volumio systemd[1]: Started Volumio Backend Module.
Oct 26 16:35:06 volumio volumio[10210]: 512 MB or less RAM Detected, need to enable swap
Oct 26 16:35:06 volumio volumio[10210]: Enabling Swap
Oct 26 16:35:06 volumio volumio[10210]: swapon: /data/swapfile: swapon failed: Device or resource busy
Oct 26 16:35:06 volumio systemd[1]: dynamicswap.service: main process exited, code=exited, status=255/n/a
Oct 26 16:35:06 volumio systemd[1]: Unit dynamicswap.service entered failed state.
@ djwang
I checked for the differences between our systems and found that you have a Pi 1 B whereas I have a Pi 1 Bplus. To me that suggests that you might have a memory problem.
b.t.w. if you started up with a WiFi that failed to come up I would think that this is an interrupted first boot. I always used cable and had a good ping and ssh, so this is fine but in the end it did not mean much.
I never removed the HiFi-Berry but it might make a difference when you have less memory, so it might be worth to try it without.
And again I tried many things but the success came when I made a new card = rewrite partition, format, copy .img
Good luck
warp2
@dwang
yes to me it seems that first boot was interrupted, the third partition never got resized, so there is no space left on the device…
PS: do you have a 256 MB RAM PI or a 512MB one?
Hello volumio-team,
first of all thanks for that great piece of software.
Unfortunatelly I expirience the same problems as described in this post.
I receive roughly the same messages when checking via ssh as mentioned by the other people here.
I made several fresh flashes, booted up with nothing connected but the ethernet cable and waited for some time (max. 60 min.). Always the same result: ssh working, IP available but no connection to the WebUI.
When checking the SD-Card with GParted I see that the third partition is corrupted. On the information I receive the following message (translated from German):
“12.32 GiB unallocated space within the partition.
To increase the file system to the size of the partition, select the partition and then the menu item:
Partition -> Check.”
When doing exactly this the partition is fully usable.
Afterwards I put the SD back into the Pi and then the magic happens 
I can access the WebUi through volumio.local and everything seems to be working fine so far (I have not added my NAS shares yet, but webradio is working).
So the problem seems to be the resizing of the main partition as Michelangelo allready guessed.
BTW: My Model is a Pi B+ with 512 MB Ram.
Hope this helps.
Hi all, I finally got the web UI to respond by reimaging the SD card then waiting one hour.
I’m not sure if this was influenced by the microsd or the PI3 but I would suggest something gets added to the official install guide that if you have a certain model/card then you need to wait x number of minutes.
Thanks to everyone for their help in getting this working !
@michelangelo
My Model is a Pi B+ with 512 MB Ram.
Thanks everyone for reporting. To me is not acceptable that to use Volumio someone needs to wait an hour.
We’re working to understand what goes wrong and where the problem is.
sorry
My Model is a Pi B with 512 MB Ram.
@michelangelo
I am not so sure about the time required for the first boot. I simply wanted to make sure I would not interrupt it. After all you never know whether
you interrupted the initialization or it failed for some other reason. Speaking for my situation I tried to avoid removing the card because this required some mechanical disassembling of my system.
But I can confirm that on a failed first boot there were warnings about limited memory and there was no chance of storing a log or a listing. So obviously no partition was expanded and consequently the UI could not run. I hope this will help you with troubleshooting.
Best regards and thanks for the nice product.
warp2
Hi,
I was having the same problem on an RPi B.
I tried several fresh flashes, in place updates, manual fdisk…
What worked was removing the SD card, and using gparted on another computer. I applied the Partition>Check option on the third and largest partition.
I put the SD back in the Pi, powered on and setup completed.
Thanks to stormrider2k above for the heads up.
Now to solve the Touch Display Plugin hanging at 70% installed as it did on my RPi3 too…