Re: Please stop systemd-fsck on _every_ boot!
On 01/06/2015 07:23 PM, ~Stack~ wrote:
I keep seeing all of these posts online saying how easy it is to disable
systemd from runing fsck because it "honors" the '0' in the sixth field
of /etc/fstab. Well that's just pure bull$h1t... That was one of the
first things I tried some time ago. As far as I can tell on neither of
my Jessie machines (one physical one virtual) does systemd honor the
fstab in terms of doing a fsck. All of the partitions are set to 0 in
/etc/fstab.
That doesn't make it "bullshit", it means that in your instance it
doesn't help. Instead, just maybe your system is trying to tell you
something when it continually forces fsck. Read the man page.
The trick is to get your poor stupid dumb machine to tell it's human
where it hurts and how to fix it. It's like dealing with a puppy that
whines.
OK, your next message reveals that you are encrypting your drives,
including swap?? Insert "encrypted hard drive fsck" into your search
bar. Lately, others report problems.
Another thought would be to disable swap, if you have enough memory to
see if that helps at all. man swapoff
Since it was encrypted no telling what this would do: man swapoff
--------------------------------
swapoff-f, --fixpgsz
Reinitialize (exec /sbin/mkswap) the swap space if its page size
does not match that of the current running kernel. mkswap(2)
initializes the whole device and does not check for bad blocks.
-------------------------------
At any rate all the fsck'ing is telling you something is broken. That is
what it is supposed to do. If you are running luks check this:
http://serverfault.com/tags/luks/hot
Happy hunting troubleshooting with a shotgun. :) Ric
--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
Linux user# 44256
Reply to: