1 |
On Wed, Nov 1, 2017 at 2:12 PM, Wols Lists <antlists@××××××××××××.uk> wrote: |
2 |
> |
3 |
> Windows WON'T SHUT DOWN PROPERLY most of the time. |
4 |
> |
5 |
> And something messed up /home. |
6 |
> |
7 |
> Easy enough to fix, when I eventually found out the cause. Run fsck on |
8 |
> /dev/sda8. Re-configure windows to tell it "shut down does NOT mean |
9 |
> hibernate, damn you!", and finally reboot actually got me into SUSE proper. |
10 |
> |
11 |
> But I wish they'd document - and fix!!! - how to get systemd to mount |
12 |
> drives properly!!! |
13 |
> |
14 |
|
15 |
By "properly" it sounds like you want it to mount filesystems that |
16 |
were not cleanly unmounted without user intervention, or ignore a |
17 |
failure to do so? |
18 |
|
19 |
I think I'll stick with the way it works now. |
20 |
|
21 |
However, if you want it to boot without warnings if the drive won't |
22 |
cleanly mount you can just add a nofail option to fstab for the |
23 |
filesystem. Then your system will just continue booting without the |
24 |
filesystem mounted if the linux mount command wouldn't mount it with |
25 |
the normal invocation. And then you get to clean up after whatever |
26 |
daemon goes writing stuff in the empty mountpoint. |
27 |
|
28 |
I imagine systemd is dropping to a recovery console in these |
29 |
situations because most sysadmins want to know when a filesystem is |
30 |
not cleanly mounting, and continued operation in this state is |
31 |
unpredictable. I'm sure it could be overriden if you really wanted |
32 |
to... |
33 |
|
34 |
-- |
35 |
Rich |