Hi ActionA !
Frankly I don’t remember. The SSD was mounted and working allright.
Now it’s not there anymore.
Unit still hangs booting.
Thanks a lot.
Hi ActionA !
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.
Put Vero’s microSD into my Mac (which has linux fs drivers) and edited out two lines from my /etc/fstab:
#//192.168.174.9/WD1TB /mnt/WD1TB cifs username=xxx,password=yyy,uid=1000,gid=1000,iocharset=utf8,sec=ntlmv2 0 0 #/dev/sda1 /mnt/SSD128 ext4 defaults,noatime 0 0
And now OSMC booted, updated and we’re almost back. Thanks a lot ! Just 2 more questions:
First line is to mount a CIFS share with all my movies coming from a second RPi.
Second line is a locally mounted (USB) SSD with local files used by my torrent client.
How can I mount the ssd properly in the same mountpoint without getting in this rebooting problem ?
The CIFS mount behaves well and does not interfere with reboots but I must always issue a sudo mount -a to have it back after a reboot.
Thank you !!!
You should use the following mount options for both mounts:
I am starting to be afraid I have an HW issue with Vero itself (it’s one of the early Rev.1 units).
After modifying the fstab lines as you suggested Vero did not reboot at all.
I therefore found an IDENTICAL microSD to the original one.
The one on the bottom with the greyish felt pen marker on top of the micro logo is the new (used only twice before) card:
I installed OSMC installer onto it and inserted it into the Vero.
It booted and formatted/downloaded and installed stuff but then when it tried rebooting I got the following:
Not sure as to what else should I try. Suggestions ?
I’ll be traveling to London an a few hours and will not be able to act physically here at my house but please help me.
Thanks in advance.
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 !
Take care and talk soon.
Just back at home. Could not find any non-Sandisk MicroSDs !!!
Will go buy one tomorrow if necessary.
Just as another test DLed OSMC on same Sandisk which does not seem to work with the Vero and it works well with an RPi2 (mod B 1GB)
If necessary I can send my Vero to Sam to see if he can sort this out.
I’ll reply in here as it’s a similar problem.
Did an update a few days ago on the Vero - via the My OSMC menu and updates
On restart it only shows the OSMC spash screen now
I have no experience using linux commands & only have a chromebook in the house!
Any tips on what to do next
Can I re-install OSMC using a chromebook?
Long shot, but can someone try this:
- Insert the SD card in your PC
- You’ll see a file called ‘imx6dl-vero.dtb’.
- Delete it, and replace it with this file: http://collaborate.osmc.tv/index.php/s/qA8Y1Ivje2WYbXs. Give it the same name (imx6dl-vero.dtb).
Did the file replace using chromebook (mentioned in case that made any diff)
Inserted micro-SD into Vero while off and rebooted
Still stuck at OSMC logo screen
I don’t see any coding in the top left (never have) like others have mentioned
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
new thread for my OSMC problem
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.
Thanks a lot.
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.
If you can, install the June update on the bad card (last working update for those affected) and run these commands:
wget http://apt.osmc.tv/pool/main/v/vero-kernel-osmc/vero-kernel-osmc_1.8.7_armhf.deb -O vero-kernel.deb wget http://apt.osmc.tv/pool/main/v/vero-source-4.1.12-3-osmc/vero-image-4.1.12-3-osmc_3_armhf.deb -O vero-image.deb sudo dpkg -i vero-kernel.deb sudo dpkg -i vero-image.deb
and report back
Sam will do.
Just don’t hold your breath since I’m really OVERworked for the next couple of weeks.
bad news here.
Had to turn off the Vero (shutdown and unplug power) to connect another device.
Upon rebooting it with the NON Sandisk card that was working allright I get the dreaded message again
Identical to the picture I had posted a few posts above this one.
I am starting to lose hope.
I am trying to do what you suggested. Vero with June kernel boot allright.
When I try to wget the first file though it fails with a file not found error.
Ideas ? Can I just get 1.9.5 instead ?
No it seems I can’t. Waiting for updated instructions:
-rw-r–r-- 1 osmc osmc 988 Nov 23 11:18 vero-kernel.deb
osmc@osmc:~$ sudo dpkg -i vero-kernel.deb
(Reading database … 22794 files and directories currently installed.)
Preparing to unpack vero-kernel.deb …
Unpacking vero-kernel-osmc (1.9.5) over (1.4.2) …
dpkg: dependency problems prevent configuration of vero-kernel-osmc:
vero-kernel-osmc depends on vero-image-4.1.12-7-osmc; however:
Package vero-image-4.1.12-7-osmc is not installed.
dpkg: error processing package vero-kernel-osmc (–install):
dependency problems - leaving unconfigured
Errors were encountered while processing:
I posted these instructions two weeks ago, and while you were away we worked with some other users to ensure the issue is fixed. Some of the files you are trying to download have changed / been deleted, which is why the above instructions no longer work. The good news is the consensus is that the issue is fixed (from the Dependency failed thread), so I will make that kernel publicly available shortly via an OSMC update.