Solved: mounting failed

Help and Support Help
1

Hi everyone!
I successfully got Volumio to works with my Raspberry Pi 3 Model B, an HifiBerry Amp+ and the official Raspberry Pi 7” touch screen display.

I’m now trying to polish it and get rid of some wired things.

First of, during the boot sequence I have an mounting command failing :

mount: mounting /dev/sda1 on /mnt/usb failed: Invalid argument

(I have an USB stick permanently plugged to the RPI with a bunch of songs) but this doesn’t prevent volumio to start.
After this error I have the volumio logo and then a command prompt (for a really long time maybe 2 minutes)

And then the UI show up.

First of : how do I get rid of the mounting fail error?
And then : is there a reason for the slow booting process?
What I’m understanding is that Volumio is starting chromium in kiosk mode but is that really that slow?

And some times chromium will ask me if I want to “restore” the page after a power off. I wonder if this is something that could me disabled.

Thanks for help!

2

The mounting error is something to do with your USB stick … what format is it? Can you access it when Volumio is booted up?

No idea for the long booting time, unless it is related to the above.

3

Tanks you a lot for your help.

Making a fresh install and a new formated USB stick solved it all.

For the slow boot issue I think that could be caused when my Wi-Fi hotspot isn’t detected. When I boot the pi with a wired connection the boot time is normal.

4

Greetings,
I was getting the “Chromium didn’t shut down correctly” message at startup, too. It is coming from the “exit_type” and “exited_cleanly” fields within Chromium’s Preferences file. It is located in “/data/volumiokiosk/Default”.

 Had seen post elsewhere that said to use sed in a startup script to change [b]"exit_type": "Crashed" to"exit_type": "None"[/b] and [b]"exited_cleanly": false to "exited_cleanly": true[/b].  This would not work for me for some reason I can't figure out.

 However, simply deleting the Preferences file does the trick.  If Chromium does not find the file it will create a new one with the default values.

 Rather than create a new startup script, I modified "[b]volumiokiosk.sh[/b]" in "[b]/opt[/b]" by placing "[b]rm /data/volumiokiosk/Default/Preferences[/b]" after the line "[b]xset 0 0 120[/b]" and before "[b]open-sission &"[/b].  See below.

#!/bin/bash
xset +dpms
xset s blank
xset 0 0 120
rm /data/volumiokiosk/Default/Preferences
openbox-session &
while true; do
/usr/bin/chromium-browser \
–disable-pinch \
–kiosk \
–no-first-run \
–disable-3d-apis \
–disable-breakpad \
–disable-crash-reporter \
–disable-infobars \
–disable-session-crashed-bubble \
–disable-translate \
–user-data-dir=’/data/volumiokiosk’
–no-sandbox
localhost:3000
done

I was also having an issue with the album covers not changing while being stuck on one cover. This turned out to be an issue with Chromium not flushing the cache. Adding “rm /data/volumiokiosk/Default/Cache/*” in the same place corrected this issue.

5

@Randy
Please make your own post rather than replying to an unrelated problem … it makes for much easier searching for people with future problems. Ty.