[sles-beta] LVM startup issues...

Mon Nov 16 10:17:13 MST 2015

I am still having this issue with a fresh build based on RC3.

So I don't know if that is a re-open of an SR, an new SR, or how it should be handled.

I can probably share the custom ISO we create to assist troubleshooting, or the yast profile, or whatnot.

The boot time message is...

[ TIME ] Timed out waiting for device dev-vg00-lv_emageon.device.
[DEPEND] Dependency failed for /opt/emageon.
[DEPEND] Dependency failed for Local File Systems.
[DEPEND] Dependency failed for Postfix Mail Transport Agent.

OK...don't understand why Postfix has a message on this, but, it is there...

Disk layout is...
/dev/sda1 /boot/efi 156M
/dev/sda2 / 4G
/dev/sda3 [swap] 4G
/dev/sda4 /usr 8G
/dev/sda5 /tmp 2G
/dev/sda6 /var 4G
/dev/sda7 /opt 16G
/dev/sda8 LVM vg00, contains lv_emageon at 8G [initial]...

All filesystems are xfs, except for /boot/efi which is a DOS variant as required.

We use by name.  I would argue it is still nicer.  Humans don't deal well with UUIDs, though I would consider using them in a SAN environment, but would probably still utilize the bindings file from mpath.

-Joel

-----Original Message-----
From: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] On Behalf Of Joel Barbieri
Sent: Monday, November 16, 2015 10:06 AM
To: Vincent Moutoussamy <vmoutoussamy at suse.com>; Waite, Dick (External) <Dick.Waite at softwareag.com>
Cc: sles-beta at lists.suse.com
Subject: Re: [sles-beta] LVM startup issues...

I will check the status of this issue with a fresh build and post status later today.

Thanks,

-Joel

-----Original Message-----
From: Vincent Moutoussamy [mailto:vmoutoussamy at suse.com] 
Sent: Monday, November 16, 2015 9:50 AM
To: Waite, Dick (External) <Dick.Waite at softwareag.com>
Cc: Joel Barbieri <Joel.Barbieri at merge.com>; sles-beta at lists.suse.com
Subject: Re: [sles-beta] LVM startup issues...

Hi,

bsc#934965 was resolved in RC1. 
@Joel could you confirm the status of your issue? 

Regards,
-- 
Vincent Moutoussamy
SUSE Beta Program and SDK Project Manager

> On 09 Nov 2015, at 19:25, Waite, Dick (External) <Dick.Waite at softwareag.com> wrote:
> 
> The issues I had with LVM I think we're due. to systemd and ‎how it worked with LVM. I'm on the move at the moment but a bit of paper I have says bug 945095 was covering the issues.
> The lady looking after LVM is Liuhua Wang. She is working out of Beijing.
> __R
> 
> 
> Sent from my BlackBerry 10 smartphone.
>  Original Message
> From: Joel Barbieri
> Sent: Monday, 9 November 2015 19:16
> To: sles-beta at lists.suse.com
> Subject: Re: [sles-beta] LVM startup issues...
> 
> 
> sles-release-12.1-1.292.x86_64 from RC3.
> 
> So...an SR?  I am just surprised that no one else is still experiencing...
> 
> But then again, I'm always surprised when things I have been doing for a decade just stop working...
> 
> -Joel
> 
> -----Original Message-----
> From: Waite, Dick (External) [mailto:Dick.Waite at softwareag.com]
> Sent: Monday, November 09, 2015 12:07 PM
> To: Joel Barbieri <Joel.Barbieri at merge.com>; sles-beta at lists.suse.com
> Subject: Re: [sles-beta] LVM startup issues...
> 
> Evening,
> If this is Beta2 or 3 then it's known. If you see it with RC2 then it's an issue.
> __R
> 
> 
> Sent from my BlackBerry 10 smartphone.
>  Original Message
> From: Joel Barbieri
> Sent: Monday, 9 November 2015 18:41
> To: sles-beta at lists.suse.com
> Subject: [sles-beta] LVM startup issues...
> 
> 
> I am having issues with LVM startup on boot.  My autoyast profile creates a traditional disk layout, and automatically creates an LVM volume.  On system reboot after installation [or anytime] it cannot successfully mount the volume it created.  It instead times out waiting for the device [dev-vg00-lv_emageon].
> 
> All volumes are done by name and not by UUID or anything more exotic.
> 
> Logging in shows the device to be available from via vgs and lvs, and active, but it is not available via /dev [e.g. /dev/vg00/lv_emageon].
> 
> /dev/mapper is empty...
> 
> Running journalctl tells me...
> 
> /var/lock/lvm/V_vg00:aux: open failed: No such file or directory
> Can't get lock for vg00
> Failed to read Volume Group "vg00" (xkrW06-vHO2-12OW-DX...) during autoactivation.
> Starting Activation of VM2 logical volumes...
> Lvmetad is active, skipping direct activation during sysinit...
> ...
> Looks like attempts to start encrypted, lvm2, remote, with all LVM "skipping direct activation"...
> 
> Followed by the timeout and fail...
> 
> Anyone have any great hints?  I may be ablet o workaround with some autoyast profile changes, or by using uuid, but possibly not.
> 
> It seems similar to prior lvm systemd startup issues that occurred in OpenSuSE.
> 
> This does not occur in SLES12SP0 with the same autoyast profile.
> 
> Bug?  Or is it more likely I'm doing something not quite supported any longer with systemd?
> 
> -Joel
> 
> Joel Barbieri
> Merge Healthcare
> 900 Walnut Ridge Drive
> Hartland, WI 53029
> 262-369-3118
> joel.barbieri at merge.com
> 
> _______________________________________________
> sles-beta mailing list
> sles-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sles-beta
> 
> Software AG – Sitz/Registered office: Uhlandstraße 12, 64297 Darmstadt, Germany – Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com
> 
> _______________________________________________
> sles-beta mailing list
> sles-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sles-beta
> _______________________________________________
> sles-beta mailing list
> sles-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sles-beta

_______________________________________________
sles-beta mailing list
sles-beta at lists.suse.com
http://lists.suse.com/mailman/listinfo/sles-beta