Okay, any idea why this happens. Is it hardware issue of the Vero or rather issues w/ the attached periphery?
The electronics in power supplies are know to age overtime and especially electrolytic capacitor can fail suddenly.
Thanks for sharing these insights, I’ll investigate further what triggered this episode
And if that does happen?
So, out of sheer masochism, I decided to update to the staging repository again. Prior to the update everything was running stably. I was updating from the command line rather than via MyOSMC. The upgrade went okay as far as I could tell - after everything had installed the SSH connection was still up. I told it to reboot, and BOOM! Red Light Of Death, and it won’t boot up.
This is the third time it’s happened like this, so something in the staging build is definitely either causing or triggering this. (And two previous times I’ve got it working again and completely stable by reinstalling OSMC from a memory card).
I captured some debug logs during the update process (uploading just prior to the reboot).
https://paste.osmc.tv/mejavuremu
I then unplugged everything - power, remote dongle, Ethernet, and HDMI, then plugged the power back in - and this time it booted up. Debug logging was still enabled, so I uploaded logs again:
https://paste.osmc.tv/ewevexebav
I tried rebooting again… and Red Light Of Death once more.
Since unplugging things helps, it seems likely that my power supply is on its way out - maybe, during rebooting, there is a sudden demand for current that it cannot supply, so rebooting isn’t successful, but once it’s up and running, it’s stable(ish).
What’s odd about this is that, if that’s what’s going on, there must be something in the staging build that is increasing the demand for current during rebooting.
@sam_nazarko (or anyone else!) is there anything else I can do to confirm that it’s a dodgy power supply, or is this sufficient evidence?
P.S. Unplugging just the HDMI cable and leaving the remote dongle and Ethernet cable plugged in allows it to boot. If I unplug both of the other two but leave HDMI plugged in, it won’t boot. I don’t know if that’s significant.
I can confirm HDMI plugged , no booting here. This is - for me - related to installing this build.
No question about that for me. Three times in a row mine stopped booting as a result of installing the staging build, and recovered after reinstalling OSMC.
I just want to say my experience, I am on the staging build too. I have older Vero4K( not +) Didn’t used vero 4K for a while, but yesterday got message that there is update. Updated. And everything is perfect. Can reboot, can connect to ssh. Everything plays.
And what I was surprised my blue ray concert recordings which is 25Hz or 30 Hz starts playing very smooth from beginning. What I mean ,before it was if start 25 Hz Blue ray movie it starts , tv confirms 25Hz , then black screen for couple seconds without sound and when everything plays fine and tv confirms 50Hz Now from begining tv confirms 50Hz no black screen , and no stop in sound , very smooth begining.
OSMC team, was any improvments in starting 25Hz or 30Hz blue ray video in latest builds or am I dreaming? 
Yes, that’s a recent change: 1080i/50 video now always plays at 1080p/50 even if 1080p/25 is whitelisted.
After looking in to this – it looks like the issue is caused by those that have forced an HDMI mode.
You can verify this by checking the output of fw_printenv hdmimode | grep force. If this returns output, then this is the reason you are experiencing an issue.
You can run sudo fw_setenv hdmimode=1080p60hz and this will allow you to update now.
We’ll work on a proper fix for this.
With any luck, this will be solved in the next update. See:
this didn’t change anything on my end. Had to unplug HDMI to boot.
Can you please check sudo fw_printenv | paste-log and send the output so I can check then please?
Thanks.
will do once I’m back home again.
I couldn’t see that you’ve set the parameter as recommended above from that output.
You could try the actual fix instead:
wget "https://collab.osmc.tv/s/FLaaxjHOzzhFjSu/download" -O kernel.deb
sudo dpkg -i kernel.deb
reboot
Sam
I ran [quote=“sam_nazarko, post:32, topic:90863”]
sudo fw_setenv hdmimode=1080p60hz
[/quote]
will try the fix now
can’t get it to boot w/ HDMI plugged in