I’m sorry that things aren’t working as expected for you. I’d like to help you get them fixed.
We’re not asking you to repeatedly set up your device. The fact is that you should be able to install OSMC once and that should be it; unless you make changes that change the system behaviour significantly enough to warrant an installation.
My advice was to start with a fresh installation of OSMC and add make changes to the system slowly to see if we could identify the problem as being caused by a specific add-on or change on your system.
Thanks for letting me know that you’ve had the device since it was launched. I hope you can appreciate that this is a peculiar issue. We’ve seen corruption of the filesystem on Pi and Vero 4K before; but this doesn’t usually extend to attached media, as OSMC doesn’t store system files there.
We can get this swapped out on an RMA. But to save time, and avoid you ending up receiving another device where you experience the problem, and we then discover that it’s related to some customisations made or attached peripherals, it would be better to work on identifying the problem first.
As I understand it, you currently have a non-booting device. As such, the next logical step would be to install OSMC so that you can boot. It would then be good if you could make your customisations, and then forward SSH details to me so that I can log in to your device and see what the problem is.
I could understand the eMMC on the Vero 4K potentially developing a fault, and corruption preventing the device from booting. What I can’t get my head around is why attached media would also suffer data loss. Can you confirm whether the attached drives are being powered independently of the Vero 4K?
I’d be happy to take a call if you’d like to discuss this or jump on TeamViewer and take a look