Originally posted by mozo
View Post
x-systemd.mount-timeout= is how long it will wait in the mount process before aborting the mount. device-timeout is damaged device not damaged file system. mount-timeout can because of damaged file system.
Neither of these address how long systemd will wait attempting to fix a file system and it cannot because the tool is missing or a joke. repair tool missing/incomplete means you should not have a file system mounting as part of boot process. User mountable after system has come up is valid and will not result in you getting yourself locked out of your system.
mozo there is a reason why you can define a file system mount in fstab that does not mount on boot. One of the cases this is to handle is file systems that you don't have proper repair tools for that you will be using read/write. So that you can get into the system if something goes wrong..
Leave a comment: