On 06/03/2025 00:00, Eben King wrote:
On 3/4/25 21:59, Max Nikulin wrote:
In this particular case I do not think it is a drive failure. I suspect
mounting /home was a mistake.
Indeed. "-ro" is not read only when a journal is in play.
In some post on data recovery I have seen a mention that for forensic
investigation (topics are actually closely related) some special mount
options are required to ensure that data on the drive are not modified.
You may try to find relevant recommendations an to check if "norecovery"
suggested by Michael is enough or more options are necessary.
Alternatively for backups without browser restart you may try LVM snapshots.
Booting a live image may destroy hibernation data since live system may
mount the same swap partition and reinitialize it. Eben, have you find a
reliable way to avoid swap reuse?
The environment from which I do the backups is system-rescue.org .
Thanks for a hint. It is reasonable to expect that tools like
SystemRescue should not mount anything by default. Maybe I will check if
they disable some settings or vice versa "desktop" live images have some
script that tries to enable as much swap space as possible. A decade ago
after extracting an Ubuntu image on a USB drive I usually edited kernel
command line to disable swap. When systemd arrived, old recipe stopped
working and that time I did not find a replacement. I did not realized
that live images intended for repair should have some way to disable swap.
