05-23-2023, 07:19 PM
@Sehnsucht , since I have destroyed multiple SD cards and one SSD through power loss, I don‘t see it as myth. Regarding how this can happen: I haven‘t researched it, but two immediate possibilities would be that in the controller we get conflicting potentials during the power loss that fry part of the control logic (remember, the internal voltage is much lower than the external voltage) the other could be that single cells or banks could be lost in the same way. But I would have to look into it…
The second question is whether with the low cost of an SD card and the comparably low risk thinking about it is worth the time.
Otoh, thinking about it is fun and a challenge (and a learning opportunity). The simplest way to introduce a read-only mode is to simply use raspi-config and turn on the overlayfs. This turns everything to read-only, and adds a „ram disk“ that contains all the changes. Turning the RPi off means throwing away every change. [this would be the simplest approach, without syncing back, as could be done with zram-config]
For my use case this would be absolutely ok, since I want to use the player as a frontend to my LMS. My question remains: Is there any Moode process that relies on changes being kept over reboots? And are there any processes that produce a large number of changes (the size of the overlay, kept in RAM, is limited)?
If not, then I think I will put this experiment on my list…
Cheers, Joe
The second question is whether with the low cost of an SD card and the comparably low risk thinking about it is worth the time.
Otoh, thinking about it is fun and a challenge (and a learning opportunity). The simplest way to introduce a read-only mode is to simply use raspi-config and turn on the overlayfs. This turns everything to read-only, and adds a „ram disk“ that contains all the changes. Turning the RPi off means throwing away every change. [this would be the simplest approach, without syncing back, as could be done with zram-config]
For my use case this would be absolutely ok, since I want to use the player as a frontend to my LMS. My question remains: Is there any Moode process that relies on changes being kept over reboots? And are there any processes that produce a large number of changes (the size of the overlay, kept in RAM, is limited)?
If not, then I think I will put this experiment on my list…
Cheers, Joe
