I’ve just emailed you at sales@osmc.tv
I have received your email and I am replying now
Sam
Headless install failed with same symptoms. Will try with a completely different display in the next day or two
If you are truly convinced the issue is not environment specific, just send the device back (this was mentioned in our email correspondence) and save the two days.
Sam
Sam, can you confirm that you currently have stock available so that if you are unable to solve the problem within a reasonably amount of time (shall we say 48 hours) then you will be able to send a replacement unit? If you can confirm this I shall put it in the post tomorrow, but I need some sort of commitment on timescales from you.
Tom
Tom
I have already outlined that another batch is on its way in our email. I cannot give a firm delivery date at this time but we are expecting it for Friday.
Once we receive a unit back we will work hard to identify the issue
Sam
The new batch has arrived earlier than expected.
Sam
I have sent it today by recorded delivery, so you will receive it on Monday. Please keep me up to date on its status.
Will let you know when I get it
Sam
I received it today and took a look at it. It did not boot initially – there were files missing on the boot partition. After reimaging the SD card with the latest (September update) Vero image, the device started booting. I then saw the expected ‘OSMC installed successfully’. The device then rebooted straight in to OSMC.
From what I could see, the image was not properly written to the SD card prior to this. I downloaded the image and ran the following command:
sudo gunzip -c OSMC_TGT_vero1_20150929.img.gz | dd of=/dev/sdb bs=1M conv=fdatasync
I suspect this may have arisen when you chose to avoid using the OSMC installer to write the image to the card.
I will install the June image and perform a full upgrade from that as well to see if I can replicate the issue that others have posted here.
Sam
Its been a while since Ive looked at this thread due to loosing my Vero at the hotel when I took it with me to run thru test cases.
However looking at the logs from @tombertie , l think he might have had a different problem than the rest of us had as I was never able to get that far on the install.
I installed the June update and performed an upgrade via My OSMC -> Manual Controls -> Scan for updates now. The device upgraded to the September update and is working fine. I have re-imaged the device with a fresh installation for you.
@tombertie I will contact you by email to discuss how to best proceed with this.
Sam
I’ve always used the installer and have this problem. Sam, I’ll send mine back for you to do an install on. Just don’t complain about the battle scarred case as I had to cut it to get an optical cable to fit (design flaw on the Vero.) Regards. Would you please send me your postal address?
Hi
I have concluded that @tombertie’s Vero is not affected with this issue. In my testing it performs fine with the September update or when I install the June upgrade and perform a full upgrade via My OSMC.
I spoke with @DBMandrake about this issue yesterday, and while neither of us can replicate the issue, I have worked on some SD card improvements that will improve SD card stability and performance for all Veros, but as sad on countless occasions, we are working in the dark here.
@fxschaeffer / @AdR, I just need one Vero, but we need to confirm it is affected with the bug discussed above. If you email me at sam@osmc.tv I can run a couple of quick tests and then walk you through a return.
Sam
Perhaps a silly idea but I would also ask for the used power supply, so the affected Vero can be analyzed under same conditions.
Ok sam i’m emailing you in the following minutes.
And the SD card that goes with it, unless it has been confirmed that the issue also happens with another different make of SD card, (eg not Sandisk) because the problem might only affect compatibility with certain makes/models of SD card.
I don’t recall anyone in this thread affected by this issue having tried a different make/model of SD card in their Vero with the recent updates which is a real shame, because that would have helped narrow the problem down somewhat.
Thank you for sorting my Vero out. To answer one of your points, I formatted the SD card before sending to avoid any personal information being included. I had been using Win32 Disk Imager to transfer the image onto SD card as this is what I do with Raspberry Pis, and am not entirely sure why that would create a problem. This also worked with the Jun image hence was the way that I could maintain a working unit, but always failed on all images after that. Irrespective of this, and regardless of the fact that mine failed under the same conditions (perfectly working unit from delivery failing only after updating through osmc in July in the same way as others on this forum), it is good to know that you seem to have solved it now. Please advise when I will receive it back. Yours, Tom
Hi Tom,
I have once again followed up with you by email. I could not exhibit any symptoms you described – a simple re-imaging resolved the issue. I have advised you how to correctly re-image your card in the future, namely, use the OSMC installer. I understand you were concerned about malware in our installer, but have provided you some further assurances that our installer is indeed safe.
Sam
Dear Sam,
I am slightly at a loss for words. Your post and email almost suggest that I have made the symptoms up. My previous post laid out the characteristics of the issue arising and is repeatability by me, I sent the box to you at your urging, and you were aware that I had been copying the image direct rather than using the installer. I am rather amazed that goodwill doesn’t extend to you returning my Vero without charge; perhaps the crowdfunding route that you rejected would have given you enough capital to run this a little more as a business, albeit at the expense of some of your equity. I shall of course pay the invoice but have probably learnt a lesson with regards to doing business with a startup.
Yours, Tom