Disk decryption slow

hotsauce · #1 7th March 2012, 03:25 AM

I've been using full disk encryption by way of luks for some time now. I'm on a 2TB hardrive, full Fedora install. If I remember right, it used to only take about 60 secs to get through the decryption progress bar. Now it takes about 7-8 minutes to go from disk decryption to gui login. Are there any way's to speed this up?

biosphere · #2 10th March 2012, 05:23 PM

Apologies if you've already checked this hotsauce, but are you sure this is a problem with disk encryption? It sounds like a daemon might be taking it's time to run or something. There was a recent post here which should hopefully help with analysing your boot time if it's something you've not already looked in to.

hotsauce · #3 13th March 2012, 05:20 AM

Hmm, that post was interesting, here are my results btw:

Code:

7451ms dkms_autoinstaller.service
  4600ms lvm2-monitor.service
  4166ms abrtd.service
  4133ms NetworkManager.service
  3986ms rsyslog.service
  3230ms lm_sensors.service
  2838ms ip6tables.service
  2831ms iscsid.service
  2822ms iptables.service
  2720ms multipathd.service
  2345ms fedora-storage-init-late.service
  1853ms udev-settle.service
  1554ms cups.service
  1298ms cryptsetup@luks\x2d036d4a5f\x2db88b\x2d4401\x2da8e8\x2d20293494395b.service
  1176ms console-kit-log-system-start.service
  1172ms fedora-sysinit-unhack.service
  1085ms sshd.service
  1012ms fedora-storage-init.service
   921ms acpid.service
   880ms gpm.service
   877ms sandbox.service
   840ms vboxdrv.service
   711ms udev.service
   685ms home.mount
   642ms usr-local.mount
   616ms systemd-binfmt.service
   548ms systemd-tmpfiles-setup.service
   524ms rtkit-daemon.service
   516ms dbus.service
   463ms tmp.mount
   446ms systemd-vconsole-setup.service
   425ms systemd-remount-api-vfs.service
   424ms netfs.service
   407ms remount-rootfs.service
   383ms irqbalance.service
   378ms media.mount
   365ms usr.mount
   364ms opt.mount
   349ms fedora-sysinit-hack.service
   317ms mcelog.service
   295ms auditd.service
   283ms var.mount
   274ms rc-local.service
   234ms systemd-sysctl.service
   232ms wpa_supplicant.service
   227ms psacct.service
   216ms xinetd.service
   197ms proc-sys-fs-binfmt_misc.mount
   165ms iscsi.service
   149ms fedora-wait-storage.service
   140ms fedora-autoswap.service
   134ms systemd-user-sessions.service
   123ms fedora-readonly.service
   121ms vboxballoonctrl-service.service
   102ms boot.mount
    93ms console-kit-daemon.service
    66ms udev-trigger.service
    63ms vboxweb-service.service
    51ms mdmonitor.service
    44ms dev-hugepages.mount
    29ms var-lock.mount
    29ms dev-mqueue.mount
     1ms var-run.mount
63 services: Total = 65.621 seconds

Now, I will say a recent update did seem to make things boot a little faster, maybe down to 2-4 minutes now as I hadn't logged the Fedora disk on my machine in a couple months. However, it's still a bit long; despite the awk commands output of 65 secs. I think what that command does is measure how long it takes for the services to start, but doesn't count how long some of the effects of the services starting have on the system take. Maybe throw more RAM in the system? I was considering this anyway.

biosphere · #4 18th March 2012, 09:46 AM

Not too sure then I'm afraid, perhaps a someone here with a little more experience may be able to help? I wouldn't have thought extra RAM would help in this instance (if it is 4GB you're running). Even 2-4 minutes is definitely slow so there's something else going on here.

The only last thing I'd check is just to see if one of your drives may not be unmounting properly and the system is performing an fsck when it boots but other than that, I'm not too sure I'm afraid

hotsauce · #5 19th March 2012, 01:51 AM

It could possibly be that, and I think I am seeing something about a partition not unmounting on shutdown. However, I am suspecting it also has something to do with the fact im using an encrypted disk and lvm, as far as raw speed goes. I've trimmed some services with no real optimization gains. I'm guessing decrypting a 2TB drive takes much longer to decrypt than a 500GB drive for instance; 4x as long possibly?

*Now as far as actually viewing the shutdown messages at readable speed, how would I go about setting that up so I can either step through them on shutdown, or is there a particular log im not seeing for that?