Protecting config.txt on RaspberryPi? #561
Comments
|
The best way would be to make a backup. The card shouldn't be getting corrupted regularly, so I would verify the card. LibreELEC doesn't use a read-only FAT32 partition, or updates would be impossible. I believe that they use squashfs for their root filesystem, but the boot files themselves are indeed writable. It's possible they mount the boot partition as RO unless there is an update action occurring. |
|
yes, at the moment i have placed a config.txt.bak in the same path. but this needs some steps (removing card, boot up an other pc, put card into adapter, restore the file, put card back in pi). in LE it's mounted as ro. |
|
You could mount it ro in /etc/fstab and change this on each update, but it seems a bit cumbersome. Unfortunately the current My OSMC implementation wouldn't make it trivial for us to make it RO by default. |
|
tried to figure out, where is the sub process to place before and after these commands in: is there a hidden background process to run the update? my.osmc/script.module.osmcsetting.pi |
|
Be careful: we need a writable /boot for updating the kernel and firmware too.
On 15 Jun 2020, at 18:32, harryberlin <notifications@github.com> wrote:
tried to figure out, where is the sub process to place before and after these commands in:
my.osmc/script.module.osmcsetting.updates/resources/lib/update_service.py
or
my.osmc/script.module.osmcsetting.updates/resources/lib/apt_cache_action.py
mount -o remount,rw /boot
#do update
mount -o remount,ro /boot
is there a hidden background process to run the update?
my.osmc/script.module.osmcsetting.pi
my.osmc/script.module.osmcsetting.pioverclock
are more easy to find the step.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#561 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAHDWLDDYAWG4CGQCUCWRIDRWZLKTANCNFSM4NWJ4LQQ>.
|
|
yes, i understood. |
|
No - but I’m happy to accept a pull request to change this behaviour.
On 15 Jun 2020, at 18:51, harryberlin <notifications@github.com> wrote:
yes, i understood.
is there a process before and after updating, to placew the commands for rw and ro?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#561 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAHDWLFF53LMJKNZ6DM2UBLRWZNRRANCNFSM4NWJ4LQQ>.
|
Is there a way to protect the config.txt on Raspberry Pi?
In some cases by turning power off (pi is not shut down), the config.txt gets empty 0KB file.
So, on next power on, the Raspberry don't boot up.
Could it be to set the file(s) as "read only" like LibreElec to solve the issue?
The text was updated successfully, but these errors were encountered: