Your message dated Thu, 30 Jan 2014 11:03:30 +0100
with message-id <x6mwid4wi5....@midna.zekjur.net>
and subject line fixed with lvm2 2.02.104-1
has caused the Debian Bug report #736092,
regarding systemd-sysv: Systemd mount lvm root but do not mount /usr on lvm.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
736092: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736092
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd-sysv
Version: 204-6
Severity: critical
Justification: breaks the whole system
Hello dear Maintener,
I have installed systemd on several debian boxes around me,
based on systemd and systemd-sysv.
It fail to mount the usr partition witch is a logical-volume,
it was working well with sysvinit, so I suspect to come from systemd-sysv.
When I try to boot, it show up an error :
[FAILED] Failed to start Remount Root and Kernel File Systems.
See 'systemctl status systemd-remount-fs.service' for details.
[......] systemd[1]: Failed to start Remount Root and Kernel File Systems.
[......] systemd[1]: Unit systemd-remount-fs.service entered failed state.
[......] systemd[1]: Started Various fixup to make systemd work better on
debian.
[ *** ] (2 of 5) A start job is running for
dev-840\x2d\x2dpro\x2d\x2d256\x2dtmp.device
And it fail to mount it too, so drop me to emergency console,
witch show that just root is well mounted.
My setup (not so strange, I hope), is full LVM,
and got a distinct volume for : root, usr, var, tmp, home.
This is my fstab :
# <file system> <mount point> <type>
<options> <dump> <pass>
/dev/mapper/840--pro--256-root / ext4
discard,noatime,rw,errors=remount-ro 0 1
UUID="246c0cc0-2632-4c95-ad26-482d25e2bdee" /usr ext4
discard,noatime,rw,errors=remount-ro 0 1
UUID="6b638a81-2ce9-4c39-a3ed-9bd3d7b6508e" /var ext4
discard,noatime,rw,errors=remount-ro 0 1
UUID="ba875131-e6a5-4808-9e34-4a94ab5906de" /tmp ext4
discard,noatime,rw,errors=remount-ro 0 1
UUID="f2ad93f8-f2ef-4172-8c56-d01f7cc5f34b" none swap
discard,noatime,sw 0 0
UUID="34ad3bbb-9148-46f1-9667-3bb692c54c63" /home ext4
discard,noatime,rw,errors=remount-ro 0 1
I try to change the UUID to the location '/dev/mapper/840--pro--256-*',
with an update-grub after, like in the debian wiki, but it still not work.
I also try to refresh the initramfs, not working too.
I think that the broblem bppend because systemd need,
the /usr binaries to mount the lvm, and so can not do,
because the /usr is not already mounted, I am searching
for a way to get /usr mounted before systemd need it.
Regards,
Guillaume Seren.
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (900, 'testing'), (300, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-3-686-pae (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages systemd-sysv depends on:
ii systemd 204-6
systemd-sysv recommends no packages.
systemd-sysv suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,
this bug is fixed with Bastian’s lvm2 2.02.104-1 upload to
unstable. Please upgrade to that version.
--
Best regards,
Michael
--- End Message ---
