OK. How do you know that mount does not follow fstab order?
Everything works fine, you do not seem to have order dependencies in fstab. So, how could you tell and why would it matter? Lines in syslog are probably written when mount finishes/fails. Systemd starts fstab lines in order, but asynchronously, so the end mount messages maybe out of order. I do not see any mount related connection to grub nor j2db. Grub happens long time before mount and j2db long time after successful mount. Your jdb2 type of problems are kind of expected - given that you did not install the OS, many system install state assumptions might not be valid. Perhaps the jdb2 output is not written or something else keeps hopelessly changing files in your home, triggering jdb2 updates. Would basic, default, clean install using a spare old disk verify if your problems are related to old or new Ubuntu? If it works, you would have something to compare your setup with. Default install should not take more than hour-ish and it might give you some answers. Good luck, Tomas On Sun, Dec 1, 2019, 13:37 John Jason Jordan <[email protected]> wrote: > On Sun, 1 Dec 2019 02:33:40 -0500 > Tomas Kuchta <[email protected]> dijo: > > >What are you trying to achieve? > >Is anything broken? > > The computer functions just fine, except that JBD2 is constantly > munching my /home partition, and I still have a grub error when I boot. > I don't know if these are related, but it's possible. In the meantime > I'm trying to educate myself about systemd, a formidable task for such > as me. > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
