File system gone Read Only

[DaleRobins (Dale Christian Aeron Robins)]

I just updated my configuration​.yaml file and rebooted, now the file system has gone read only.
I can’t change permissions over SSH with chmod or edit anything in Vi.

I also cannot copy or move any files off the Samba share.

Is it something to do with the Supervisor update?

[DaleRobins (Dale Christian Aeron Robins)]

Everything in my fstab is Read Only.

[Tinkerer (aka DubhAd on GitHub)]

A read only file system usually only happens if the system detects corruption during boot. You’ll want to connect to the console (keyboard and monitor) and see what the errors are.

[DaleRobins (Dale Christian Aeron Robins)]

There is no console with Hass.io via a monitor.
Quite difficult to figure out what’s happening at boot, I’m not clued up too well on Docker.

[pvizeli]

You need update your addons:

Release Notes

Hass.IO 0.28 Add docker device support with devices addon config option Maps are now default read only. For rw access use map: ["config:rw"] Important Please update all core add-ons to latest after update If you core add-on is older than 1 version behind, please copy past options and reinstall this core add-on to avoid problem with last change on 0.26

[DaleRobins (Dale Christian Aeron Robins)]

Any way I can do this from the shell?, I have an error in my configuration.yaml so can’t get to the web page…
Was this due to that update?

[pvizeli]

On device:

curl -X POST http://172.17.0.2/supervisor/restart
curl -X POST http://172.17.0.2/addons/core_ssh/update
curl -X POST http://172.17.0.2/addons/core_samba/update

[DaleRobins (Dale Christian Aeron Robins)]

Getting a 404 Error for the first line…

404: Not Foundroot@hassio:~#

The other 2 worked. Just rebooting…

[DaleRobins (Dale Christian Aeron Robins)]

Ok It’s all working, is there anything that can be put in place so if someone reboots without updating (They might not know, or have a power cut) to stop this happening?