On Thu, Oct 18, 2018 at 2:49 PM <[email protected]> wrote: > > I know how to recover the file system but I do not want to happen it again as > manual intervention is required every time and this is not desired. > > Is it that you are saying that the system is not designed to survive a sudden > unlisted power loss?
Correct, the "system" as shipped is not designed for "sudden unlisted power loss".. > If 4 devices display exactly the same process (systemd/timesyncd) that had > corrupted the file system I would not consider this as noise, but some sort > of regular event. It's noise, it's one of the first process's started, as it's responsible to figure out the a better clock time then blank.. Back to the issue, if you want the system to survive "sudden unlisted power loss", YOU need to configure it for that situation. One recent tool, that works well with systems using "systemd" is overlayroot, all current images (https://beagleboard.org/latest-images Debian 9.5 2018-10-07) have this available, you just have to open /boot/uEnv.txt and enable it at the bottom and reboot. Prior to that ^ image (and systemd) you had to split the main partition into two partition, a read only and a read write section.. aka read only root, but with systemd based systems this was hard to implement properly.. Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYg3T-z1FGVi6m8B9D9OSyNnKCrp9eZGfuBSMsC40xbKkw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
