LinuxQuestions.org
Help answer threads with 0 replies.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > SUSE / openSUSE
User Name
Password
SUSE / openSUSE This Forum is for the discussion of Suse Linux.

Notices


Reply
  Search this Thread
Old 01-20-2016, 05:12 AM   #1
Tellum
LQ Newbie
 
Registered: Dec 2015
Distribution: Fedora, FreeBSD
Posts: 4

Rep: Reputation: Disabled
Unhappy lvm2 service slows boot


Hello I am using OpenSUSE Tumbleweed. After upgrading to kernel 4.4.0.1 from 4.3.3.6. boot and shut down are taking a lot of time. Seems it is because of a cron job about LVM2, but I do not use it.

Doing:

Code:
systemctl mask lvm2-activation-early.service
systemctl mask lvm2-activation.service
(According to this recomendation: https://forums.opensuse.org/showthre...-DVB-S2-driver )
And
Code:
systemctl disable lvm2-lvmetad.service lvm2-lvmetad.socket
systemctl stop lvm2-lvmetad.service lvm2-lvmetad.socket
(according to this: http://lists.opensuse.org/opensuse/2.../msg00372.html)
Not solves the problem. In Yast->services: lvm2-activation-net,
lvm2-lvmetad, and lvm2-monitor are dishabled and inhabilited. The boot log shows:

Code:
http://pastebin.com/qq2zeqkY
In the power off it says that could not unmount the linux partition because /var/run is busy.

This coomand
Code:
systemctl status lvm2-activation-net.service
shows:

Code:
lvm2-activation-net.service - Activation of LVM2 logical volumes
   Loaded: loaded (/etc/lvm/lvm.conf)
   Active: failed (Result: exit-code) since mar 2016-01-19 16:57:06 CET; 9min ago
     Docs: man:lvm2-activation-generator(8)
  Process: 1127 ExecStartPre=/usr/bin/udevadm settle (code=exited, status=1/FAILURE)
This command
Code:
systemd-analyze blame
shows:
Code:
 2min 180ms lvm2-activation-net.service
         16.813s dev-sda7.device
         14.385s apparmor.service
         11.335s systemd-journal-flush.service
          3.516s display-manager.service
          2.876s postfix.service
          2.686s lm_sensors.service
          2.476s cups.service
          2.333s systemd-udevd.service
          2.245s alsa-restore.service
          2.086s SuSEfirewall2.service
          1.919s SuSEfirewall2_init.service
          1.024s systemd-tmpfiles-setup-dev.service
           884ms home-windows.mount
           847ms systemd-tmpfiles-clean.service
           etc


But if instead of starting with new kernel (4.4.0.1) I select the previous (4.3.3.6) then it is working:


Code:
http://pastebin.com/TSagp0GL
And
Code:
systemctl status lvm2-activation-net.service
output is:
Code:
systemd-udev-settle.service
   Loaded: masked (/dev/null)
   Active: inactive (dead)
Boot and shutdown are fast again. And returning to new installed kernel (4.4.0.1) drives to previous problem. (And every time I change kernel I reinstall nvidia driver).


My fdisk -l its:
Code:
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x76692ca8

Device     Boot      Start        End    Sectors   Size Id Type
/dev/sda1             2048   30716279   30714232  14.7G 1c Hidden W95 FAT32 (L
/dev/sda2         30716280  239400629  208684350  99.5G  7 HPFS/NTFS/exFAT
/dev/sda3  *     239416688 1953520064 1714103377 817.4G  f W95 Ext'd (LBA)
/dev/sda5        239416751 1634742324 1395325574 665.4G  7 HPFS/NTFS/exFAT
/dev/sda6       1634744320 1638934527    4190208     2G 82 Linux swap / Solari
/dev/sda7       1638935298 1848647744  209712447   100G 83 Linux
/dev/sda8       1932539238 1953520064   20980827    10G 83 Linux
And blkid:
Code:
/dev/sda1: LABEL="RECOVERY" UUID="3C98-AC5D" TYPE="vfat" PARTUUID="76692ca8-01"
/dev/sda2: LABEL="OS" UUID="6E40872F4086FCD9" TYPE="ntfs" PARTUUID="76692ca8-02"
/dev/sda5: LABEL="DATA" UUID="B26C01CAB53315F1" TYPE="ntfs" PTTYPE="dos" PARTUUID="76692ca8-05"
/dev/sda6: UUID="de3f60c8-44dc-4aff-aadb-0cac1303db71" TYPE="swap" PARTUUID="76692ca8-06"
/dev/sda7: UUID="509f86da-eb1b-464a-840f-9d9c17575846" TYPE="ext4" PARTUUID="76692ca8-07"
/dev/sda8: LABEL="Android-x86" UUID="d37f905a-40e3-4451-8b2e-32f52ef08726" TYPE="ext3" PARTUUID="76692ca8-08"
(sda1 is recovery, sda2 is windows, sda3 is extended partition, sda5 is data partition, sda6 swap, sda7 opensuse and sda8 android-x86)

Last edited by Tellum; 01-20-2016 at 05:34 AM. Reason: increased resolution of boot log
 
Old 02-02-2016, 07:54 AM   #2
gronline
LQ Newbie
 
Registered: Sep 2007
Location: Italy
Distribution: OpenSuSE Tumbleweed
Posts: 4

Rep: Reputation: 1
Same problem here....
Activation of LVM2 logical volumes takes too long and it doesn't shutdown because it can't umount the /var/run partition because it is busy.
If i start the system with the previous kernel (4.3.x) everything works ok.
Did you find a way to fix this?

OpenSUSE Tumbleweed 4.4.0.2-default
Asus M51Vr
ati hd3470
4gb ram
ssd samsung 850 evo 250gb
 
Old 02-02-2016, 10:04 AM   #3
Tellum
LQ Newbie
 
Registered: Dec 2015
Distribution: Fedora, FreeBSD
Posts: 4

Original Poster
Rep: Reputation: Disabled
No luck sorry. I tried with a fresh installation and problem appears inmediately booting the first time. Seems that our hardware is not well supported but no problem, there are many cool distros out there.

Here: https://forums.opensuse.org/showthre...-kernel-update
infinity-it said that for him worked this:
# systemctl mask systemd-udev-settle.service
# systemctl mask lvm2-activation-net.service

I can not try because already changed distro. :P So try it if you not done it already and then if you still want a cuting edge release as Tumbleweed (and you do not hate gnome) I recommed Fedora, last version 23 is working without problems .

If this code works for you let me know and I will mark my 3 threads about this solved.

Last edited by Tellum; 02-02-2016 at 10:07 AM.
 
Old 02-02-2016, 01:31 PM   #4
gronline
LQ Newbie
 
Registered: Sep 2007
Location: Italy
Distribution: OpenSuSE Tumbleweed
Posts: 4

Rep: Reputation: 1
The trick fixed the slow boot, but not the /var/run locked at the shutdown/reboot.
Actually /var/run is a partition mounted in ram (tmpfs) so... is it really mandatory to unmount it before shutdown?
 
  


Reply

Tags
boot, lvm2



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Odd boot errors after installing a new kernel. Slows boot process Alpha90 Linux - Software 2 10-07-2012 06:55 AM
[SOLVED] Intelfbdrm slows boot? soxplayer Slackware 2 06-15-2010 10:33 PM
Samba slows down shortly after restart of service asagar00 Linux - Server 0 08-24-2009 03:00 PM
Dual boot with LVM2 dbonnell Linux - General 2 08-03-2005 08:41 AM
dhcp slows boot javierj Linux - Newbie 3 03-02-2005 11:24 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > SUSE / openSUSE

All times are GMT -5. The time now is 08:24 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration