On Wednesday, December 6, 2017 at 10:40:11 PM UTC+2, Dave Barndt wrote: > > Does anything there look strange to you? >
Can't say it does. Your /var/ file system is writable and gets corrupted - this is expected. fsck failing to run is unexpected. Looks like systemd has taken over the responsibility of boot-time fsck-ing. A look at the service which fails (/lib/systemd/system/systemd-fsck@.service) tells me that there is some scant documentation available in "man systemd-fsck". However, it looks like you might have to dig into systemd source to analyze how exactly boot-time fsck-s are triggered and what could go wrong there. Alternatively, perhaps you'd want to have a quick glance at changelog for systemd, to see if they've fixed any bugs in this area since your installed version. My BBB with Debian 8 is running systemd version "230-7~bpo8+2" (dpkg -l systemd) and they've made 5 releases since. -- Kind regards, Tarmo Kuuse -- 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 beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/09bb67af-fd7e-461d-abaa-242b8f225fb2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
