El Wed, 14 Aug 2013 21:01:47 +0200
Michael Stapelberg escribio:
> Hi Antonio-M.,
>
> Have a look at http://bugs.debian.org/719738 which contains a patch
> that hopefully fixes your issue.
>
> You can use the lvm packages built with that patch by adding
>
> deb http://people.debian.org/~sta
Hi Antonio-M.,
Have a look at http://bugs.debian.org/719738 which contains a patch that
hopefully fixes your issue.
You can use the lvm packages built with that patch by adding
deb http://people.debian.org/~stapelberg/lvm ./
to /etc/apt/sources.list and installing lvm2 2.02.98-5+systemd1
P
Hi Antonio-M.,
"Antonio-M. Corbi Bellot" writes:
> I attach udevadm.log, but let me explain, when I fall in that
> shell...in '/dev/mapper/' only exist:
>
> /dev/mapper/hal9000-root and
> /dev/mapper/hal9000-swap_1
Can you — before you undertake any other steps — run udevadm on the root
and swap
Hi Michael:
El Tue, 06 Aug 2013 20:07:40 +0200
Michael Stapelberg escribio:
> Hi Antonio-M.,
>
> "Antonio-M. Corbi Bellot" writes:
> > I did what you told me, here attached are the logs (dmesg,
> > journalctl) for a working and a nonworking boot.
> Thanks.
>
> Can you please attach the output
Hi Antonio-M.,
"Antonio-M. Corbi Bellot" writes:
> I did what you told me, here attached are the logs (dmesg, journalctl)
> for a working and a nonworking boot.
Thanks.
Can you please attach the output of
udevadm info --query all --name=/dev/mapper/hal9000-home
inside the emergency shell you get
Hi Antonio-M.,
"Antonio-M. Corbi Bellot" writes:
> After applying the patch, rebooted the laptop and I had a failed boot
> again, here are attached the logs ("dmesg", "journalctl -xb")
> and /etc/init.d/lvm2.
Thanks, this rules out the possibility that it’s the lock dir. In fact,
/etc/init.d/lvm2
Hi Antonio-M.,
"Antonio-M. Corbi Bellot" writes:
> Attached are the outputs from dmesg and 'journalctl -xb' after a failed
> boot. Hope this helps.
Thanks! I spotted this in your log file:
ago 02 12:01:42 hal9000 lvm2[316]: Setting up LVM Volume Groups...
/run/lock/lvm/V_hal9000:aux: open failed
Hi Antonio-M.,
"Antonio-M. Corbi Bellot" writes:
> I've to say that I've just had another bad boot with systemd after
> moving 'usr' and 'var' to '/'.
> I got a time out trying to moun 'home' that is on another lvm
> 'partition'... so I'm lost now, it must be a problem with lvm.
>
> As always wh
El Mon, 29 Jul 2013 21:30:41 +0200
Michael Stapelberg escribio:
> 2) You could boot a live cd and move /usr to the root volume, then
>delete the separate /usr volume.
Hi Michael:
Just for the record:
After moving my 'usr' partition to '/' I had another bad-boot...then I
realized that I als
El Mon, 29 Jul 2013 21:30:41 +0200
Michael Stapelberg escribio:
> Hi Antonio-M.,
>
> "Antonio-M. Corbi Bellot" writes:
> > I think I've all the logs you asked for.
> Thanks for providing the logs. They reveal that you have /usr on a
> separate volume and don’t mount it in the initramfs, which i
Hi Antonio-M.,
"Antonio-M. Corbi Bellot" writes:
> I think I've all the logs you asked for.
Thanks for providing the logs. They reveal that you have /usr on a
separate volume and don’t mount it in the initramfs, which is not
supported:
[ 3.840308] systemd[1]: /usr appears to be on its own filesy
Hi Antonio-M.,
Thanks for your report and for helping us to track down this issue.
"Antonio-M. Corbi Bellot" writes:
> When boot hangs...I get dropped into a shell, issuing there this command:
> "vgchange -a y" and exiting with Ctrl-D is effective.
Can you please provide the output of “lsblk” an
Package: systemd
Version: 204-2
Severity: important
Dear Maintainer,
After installing systemd from experimental the boot process sometimes hangs and
sometimes (the least) works as expected.
* What led up to the situation?
Installing systemd from experimental (204-2).
* What exactly did y
13 matches
Mail list logo
