* Andrey Borzenkov <arvidjaar@gmail.com> [02-16-14 00:50]:

В Sat, 15 Feb 2014 17:14:51 -0500 Patrick Shanahan <paka@opensuse.org> пишет: [...] mkdir /etc/systemd/system/emergency.service.d cat << EOF

...

/etc/systemd/system/emergency.service.d/stop_syslog_socket.conf [Unit] Conflicts=syslog.socket EOF

done

https://bugzilla.novell.com/show_bug.cgi?id=852021

read, tks

...

Almost pulled my remaining hairs out before realizing that drive was the problem rather than my lvm ssd system drive. The new speedy boot makes err msgs fly by quite quickly.

I can boot with a "live" cd/dvd and the lvm is "Active" and I can mount it w/o any action other than creating a mount point and: mount -t ext4 /dev/mapper/<lvm-name> mount-point

I realize that this undoubtedly deserves a bug report. What should be reported against what and what logs provide relative info?

With above workaround, boot with systemd.log_level=debug on kernel command line, enter emergency shell and provide output of "journalctl -l -b"

As I seem to have a workable cludge and affected system is mail/web server, will reboot and test next available opportunity and provide log results re gpt/lvm disk problem.

...

kernel-desktop-3.11.10-7.1.x86_64

thanks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

* Per Jessen <per@computer.org> [02-18-14 05:09]:

Patrick Shanahan wrote:

...

I have a 4T seagate drive formatted GPT by yast and family which works fine in openSUSE 13.1 as long as I do not try to reboot the box with the drive set to auto-mount. It is lvm one partition ext4 and when trying to boot 13.1 with the drive auto-mount, boot fails with lvm problem and reports it is in "maintenance mode" but never provides a prompt to log in.

This sounds like LVM not being started or started early enough. I seem to recall having written up a bugreport on that.

I guess possible but I would hazzard improbable as the system install also exists, root, home, var, ..., in lvm contained partitions. System boot fine as-long-as the 4T drive is not auto-mounted. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Per Jessen wrote:

Patrick Shanahan wrote:

...

* Per Jessen <per@computer.org> [02-18-14 05:09]:

...

Patrick Shanahan wrote:

...

I have a 4T seagate drive formatted GPT by yast and family which works fine in openSUSE 13.1 as long as I do not try to reboot the box with the drive set to auto-mount. It is lvm one partition ext4 and when trying to boot 13.1 with the drive auto-mount, boot fails with lvm problem and reports it is in "maintenance mode" but never provides a prompt to log in.

This sounds like LVM not being started or started early enough. I seem to recall having written up a bugreport on that.

I guess possible but I would hazzard improbable as the system install also exists, root, home, var, ..., in lvm contained partitions. System boot fine as-long-as the 4T drive is not auto-mounted.

Hmm, yeah, that's not it then. I've only just yesterday acquired some of those 4Tb Seagate drives myself, I might play with LVM and see what happens (they're for a couple of mythtv backends).

Here's what I did today : - added a 4Tb Seagate drive - pvcreate, vgcreate, created 3.6Tb LV. - make jfs filesystem on the lv. - mkdir /var/spool/test99 - amend /etc/fstab to mount /dev/mythtv/vol1 on /var/spool/test99 reboot ... failed. Cause: the LV had not been activated on startup. Then I ran "systemctl enable boot.lvm.service", and rebooted again, this time no problems. This is on 12.2 however, so YMMV. -- Per Jessen, Zürich (10.2°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Patrick Shanahan wrote:

* Per Jessen <per@computer.org> [02-25-14 11:00]:

...

Per Jessen wrote:

...

Patrick Shanahan wrote:

...

* Per Jessen <per@computer.org> [02-18-14 05:09]:

...

Patrick Shanahan wrote:

...

I have a 4T seagate drive formatted GPT by yast and family which works fine in openSUSE 13.1 as long as I do not try to reboot the box with the drive set to auto-mount. It is lvm one partition ext4 and when trying to boot 13.1 with the drive auto-mount, boot fails with lvm problem and reports it is in "maintenance mode" but never provides a prompt to log in.

This sounds like LVM not being started or started early enough. I seem to recall having written up a bugreport on that.

I guess possible but I would hazzard improbable as the system install also exists, root, home, var, ..., in lvm contained partitions. System boot fine as-long-as the 4T drive is not auto-mounted.

Hmm, yeah, that's not it then. I've only just yesterday acquired some of those 4Tb Seagate drives myself, I might play with LVM and see what happens (they're for a couple of mythtv backends).

Here's what I did today :

added a 4Tb Seagate drive pvcreate, vgcreate, created 3.6Tb LV. make jfs filesystem on the lv. mkdir /var/spool/test99 amend /etc/fstab to mount /dev/mythtv/vol1 on /var/spool/test99 reboot ... failed. Cause: the LV had not been activated on startup.

Then I ran "systemctl enable boot.lvm.service", and rebooted again, this time no problems. This is on 12.2 however, so YMMV.

So, perhaps we are closer to seeing the problem. On 13.1 I ran:

13:58 wahoo: ~ # systemctl status boot.lvm.service boot.lvm.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead)

On my 13.1 and Tw systems there is no boot.lvm.service, nor even an lvm.service ????

Presumably because the lvm activation has been moved elsewhere. Next top: bugzilla. -- Per Jessen, Zürich (5.3°C) http://www.hostsuisse.com/ - virtual servers, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

* Frederic Crozat <fcrozat@suse.com> [02-26-14 03:32]:

Le mardi 25 février 2014 à 14:15 -0500, Patrick Shanahan a écrit :

...

* Per Jessen <per@computer.org> [02-25-14 11:00]:

...

Per Jessen wrote:

...

Patrick Shanahan wrote:

...

* Per Jessen <per@computer.org> [02-18-14 05:09]:

...

Patrick Shanahan wrote: > I have a 4T seagate drive formatted GPT by yast and family which > works fine in openSUSE 13.1 as long as I do not try to reboot the > box with the drive set to auto-mount. It is lvm one partition > ext4 and when trying to boot 13.1 with the drive auto-mount, boot > fails with lvm problem and reports it is in "maintenance mode" but > never provides a prompt to log in.

This sounds like LVM not being started or started early enough. I seem to recall having written up a bugreport on that.

I guess possible but I would hazzard improbable as the system install also exists, root, home, var, ..., in lvm contained partitions. System boot fine as-long-as the 4T drive is not auto-mounted.

Hmm, yeah, that's not it then. I've only just yesterday acquired some of those 4Tb Seagate drives myself, I might play with LVM and see what happens (they're for a couple of mythtv backends).

Here's what I did today :

added a 4Tb Seagate drive pvcreate, vgcreate, created 3.6Tb LV. make jfs filesystem on the lv. mkdir /var/spool/test99 amend /etc/fstab to mount /dev/mythtv/vol1 on /var/spool/test99 reboot ... failed. Cause: the LV had not been activated on startup.

Then I ran "systemctl enable boot.lvm.service", and rebooted again, this time no problems. This is on 12.2 however, so YMMV.

So, perhaps we are closer to seeing the problem. On 13.1 I ran:

13:58 wahoo: ~ # systemctl status boot.lvm.service boot.lvm.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead)

On my 13.1 and Tw systems there is no boot.lvm.service, nor even an lvm.service ????

FYI: boot.* initscript should be queried without the boot. prefix when using systemctl :

systemctl status lvm.service

does it matter that no "lvm.service" exists? systemctl status lvm.service lvm.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead) But there *is* lvm, lvdisplay: --- Logical volume --- LV Path /dev/system/home LV Name home VG Name system LV UUID cXrdnX-RnHU-JSAv-6ufJ-ug6R-Ufun-LeDNRc LV Write Access read/write LV Creation host, time 192.168.1.3, 2013-12-09 19:06:23 -0500 LV Status available # open 1 LV Size 50.00 GiB Current LE 12800 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:0 --- Logical volume --- LV Path /dev/system/root LV Name root ... and others lvscan -v Finding all logical volumes ACTIVE '/dev/VGpix/photos' [3.64 TiB] inherit ACTIVE '/dev/system/home' [50.00 GiB] inherit ACTIVE '/dev/system/root' [50.00 GiB] inherit ACTIVE '/dev/system/var' [20.00 GiB] inherit ACTIVE '/dev/system/srv' [50.21 GiB] inherit ACTIVE '/dev/system/swap' [3.00 GiB] inherit -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

* Jan Engelhardt <jengelh@inai.de> [02-26-14 17:49]:

On Wednesday 2014-02-26 14:09, Patrick Shanahan wrote:

...

does it matter that no "lvm.service" exists?

systemctl status lvm.service lvm.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead)

Between 12.3 and 13.1, /etc/init.d/boot.lvm was removed, but apparently without providing an equal systemd service (and it does not look like systemd would have a generator for LVM the same way it does for cryptsetup and fstab, either).

That alone would seem to cause enough breakage.

But still doesn't explain how /home, /, /var, /, /srv and /tmp all work from startup/boot and are all lvm ???? lsof |grep lvm systemd 1 root 38u unix 0xffff8801365b03c00t0 5478 /run/lvm/lvmetad.socket -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org