I decided to give “encrypted home folder” a go this time, as I normally have my entire /home partition encrypted.
The problem is that each time I try to boot I have to wait for quite a few seconds extra because of the failed write commits.
This is the sort of thing I’m getting in my startup log:
***[/sbin/fsck.reiserfs (1) – /] fsck.reiserfs -a /dev/disk/by-id/ata-ST9160821AS_5MA7HWM3-part4 ***
Reiserfs super block in block 16 on 0x804 of format 3.6 with standard journal
Blocks (total/free): 24774224/13785520 by 4096 bytes
Filesystem is NOT clean
Replaying journal: Trans replayed: mountid 19, transid 23448, desc 5914, len 4, commit 5919, next trans offset 5902
…lots of similar lines…
Replaying journal: Done.***
Reiserfs journal ‘/dev/disk/by-id/ata-ST9160821AS_5MA7HWM3-part4’ in blocks [18…8211]: 241 transactions replayed
fsck succeeded. Mounting root device read-write.
Mounting root /dev/disk/by-id/ata-ST9160821AS_5MA7HWM3-part4
I decided not to create a separate /home partition for this (for several reasons which are not important here), and so /home is simply a folder on the root filesystem.
If I shutdown by the menu I have this problem, if I open a terminal and run sync (as my user) then logout, switch to a VT and login as root, then run sync as root, it mostly avoids the problems (but not always).
Is there a way around this?
Thanks 