Automounted drives show up in /media while your’s is in /mnt so that would indicate that you have used fstab. If you plugged the SDcard into a linux machine, you could access /etc/fstab and remove or comment out the line for that drive and it would likely boot. Then we could move on from there.
Mine is an early preproduction unit (it doesn’t even have the logo on the top ) and no problem here.
Did you add those options only to your two extra mount points, not to the original / and /boot partitions I hope ?
The issue you show in the very first picture of this thread is one that we have been trying to solve in another thread:
This seems to be affecting a small number of units when updated to the recent kernels (July update onwards) and despite several months attempts Sam has not been able to get back a confirmed affected unit from a user so we can see and work on the problem first hand.
There is also a strong possibility that the problem is a compatibility issue between the newer kernels and certain batches of Sandisk cards - Sam has also asked affected users if they could try a different brand of card to see if that helps but again nobody has actually done so to date.
It would be very helpful if you were able to try a different card of a different make than Sandisk to see if you have the same “Dependency failed for /boot” issue when trying to install the October version. Even if you temporarily borrow a card from a camera etc. Anything from about 4GB up (maybe even 2GB) should be enough for a test to see whether it boots or not.
If we could confirm for sure whether a different card works OK or not then it would help narrow the issue down to a batch of Vero’s or a batch of Sandisk SD cards.
Ok thanks. I’ll definitely be able to experiment with different card brands. I tried with an identical card (which I had since a while back and got here in Italy for a camera) to avoid introducing more variables.
I’ll be back in Rome next Monday, as I’m enjoying London’s fog right now on a business trip !
Does not sound like the same issue then. You can re-image the card from osmc.tv/download. On your Chromebook you may have to manually image the SD card with dd. If you have any trouble, send me a PM or start a new post and I’ll be glad to help
Ok downloaded Oct 2015 update on a non Sandisk 8GB MicroSD. Now in vero, formatting, installing files, installed succesfully with full bar, reboot, me trembles, OSMC splash screen and … IT FRIGGIN WORKS …
Now this is really unexpected !
So I had problems with several identical to the original Sandisk 8GB MicroSDs which have been bought in different countries (UK and Italy) and in different times, from both EBay and amazon … go guess.
I will test extensively the MicroSD with hwtest but I am pretty sure they’ll come out clean.
Will report if the situation changes again uncovering a non 100% replicable problem. For now all seems ok.
while your problem might be different please note that the errors at the top left of the OSMC screen took a few minutes to appear. Until then all you could see was the simple and naked OSMC splash screen.