EROFS error message after running homebridge with people plug-in for a few minutes

[AKoch1]

EROFS error message after running homebridge with people plug-in for a few minutes

[PeteLawrence]

Hi André,

Sounds like the user that you're running homebridge under doesn't have permission to write to /home/pi/.homebridge/persist. Could you paste the output from the following commands:

whoami
and
ls -la /home/pi/.homebridge/persist

[AKoch1]

Hi Pete,

thanks for your quick reply.

I got the following outputs:

whoami --> pi

pi@raspberrypi:~ $ ls -la /home/pi/.homebridge/persist
insgesamt 40
drwxr-xr-x 2 pi pi 4096 Mär 13 13:20 .
drwxr-xr-x 4 pi pi 4096 Mär 13 00:09 ..
-rw-r--r-- 1 pi pi 704 Mär 13 18:26 AccessoryInfo.CC223DE3CE30.json
-rw-r--r-- 1 pi pi 8239 Mär 13 18:26 IdentifierCache.CC223DE3CE30.json
-rw-r--r-- 1 pi pi 13 Mär 13 16:58 person_10.0.1.16
-rw-r--r-- 1 pi pi 13 Mär 13 19:16 person_10.0.1.2
-rw-r--r-- 1 pi pi 13 Mär 13 19:16 person_10.0.1.3
-rw-r--r-- 1 pi pi 13 Mär 13 19:16 person_10.0.1.9

Just to give you some additional information:

I am using the new Raspberry Pi 3 Model B with the newest stable version of Raspbian.

Furthermore, each time the described problem occurs, the Raspberry Pi becomes unresponsive so that I cannot use SSH, VNC or RDP any more to connect to it using my laptop.

[PeteLawrence]

Strange, those permissions look fine. Things I'd try:

1. Check that the SD card isn't full
2. Check that homebridge is definitely running as the 'pi' user
3. Try deleting the file in question
4. Try restarting, in case something somewhere has left the file open.

[AKoch1]

1. Only 30% of the SD card are used.
2. Yep, homebridge is running as the "pi" user.
3. Deleting the files for all observed people did the trick, at least so far.
4. Each time the RPi became unresponsive, I had to restart it by unplugging its USB power supply since no commands were accepted any more.

I will observe the issue and keep you updated.

If the problem occurs again, do you think a hardware defect may be the cause?

[AKoch1]

Unfortunately, deleting the files did not solve the issue after all.

This time it only to longer for the problem to arise.

[PeteLawrence]

I use the latest version of Raspbian on my Pi1 and can't replicate this problem. I'm wondering if the plugin crashing is a symptom rather than the actual problem. If you uninstall the plugin does the Pi work fine for an extended amount of time? What make/class of SD card are you using? It could be a fault with the card, or the card not being able to handle continual writes, which causes Raspbian to put the card into read only mode, and the plugin crashing is the first thing that errors.