After 3 months of going Little Red Hen on this, I think I figured it
out. My system had live-config & live-boot (with their dependencies,
live-boot-initramfs-tools, user-setup, live-tools and
live-config-systemd) installed. An aptitude purge command on these
packages got my system booting normally
I'm still stuck with this problem after wasting another 5 hours on it
last night. I'm still getting the time out error message but, without
any useful debugging information, don't know where to start
troubleshooting. Further, it appears the systemd maintainers have
given up responding to bug
As my previous messages have gone entirely ignored, I'm hoping that
someone can help me with this problem, which I hope is simpler. My
boot times out trying to start a number of devices. One of them, for
example, is dev-mapper-LVGx2dtmp.device. Another is
dev-disk-byx2duuid-.device. I can
During the 90 second wait before my boot times out, I dropped into a
debug-shell and ran `systemctl list-units`. This was the output:
http://paste.debian.net/783995/ (good for 3 days). Of curiosity is
that the other dev-mapper-LVG... devices show that they're inactive
except for
Thank you for your message, Michael, and please forgive the delay in responding.
I tried booting with the 4.5 kernel after 4.6 failed to boot. It
seems, by then, that the damage had been done as I got identical
symptoms on both boots. I agree with you that the cryptsetup/LVM is to
blame (although
Am 15.06.2016 um 09:58 schrieb Borden Rhodes:
> linux-image-4.6.0-1-amd64:amd64 (4.6.1-1, automatic)
...
> Could I get direction on how to troubleshoot this?
In your list of upgraded packages, only the kernel package looks
suspiciuos. I suspect your system worked correctly before the upgrade?
ut normal mode doesn't, then one of the
>> targets/services in normal mode is to blame for the lock up. I don't
>> suppose I could trouble the list for a resource on how to do that?
>>
>> > Date: Wed, 15 Jun 2016 19:35:34 +0200
>> > From: Sven Joachim <svenj...@gmx
nding any better ideas, I think I'm going to
redirect this conversation to bug 758808.
> Date: Thu, 16 Jun 2016 13:56:48 -0400
> From: Borden Rhodes <j...@bordenrhodes.com>
> To: debian-user@lists.debian.org
> Subject: Re: boot times out after dist-upgrade on Stretch
&g
, then one of the
> targets/services in normal mode is to blame for the lock up. I don't
> suppose I could trouble the list for a resource on how to do that?
>
> > Date: Wed, 15 Jun 2016 19:35:34 +0200
> > From: Sven Joachim <svenj...@gmx.de>
> > To: debian-user@lists.debi
19:35:34 +0200
> From: Sven Joachim <svenj...@gmx.de>
> To: debian-user@lists.debian.org
> Subject: Re: boot times out after dist-upgrade on Stretch
> Message-ID: <8760tapd7d@turtle.gmx.de>
> Content-Type: text/plain
>
> On 2016-06-15 07:58 +, Borden Rhode
On 2016-06-15 07:58 +, Borden Rhodes wrote:
> I ran apt dist-upgrade on Stretch (with a few Sid packages) which made
> the following changes:
>
> Start-Date: 2016-06-14 19:42:39
> Commandline: apt-get dist-upgrade
> Requested-By: me (1000)
> Install: libdw1:amd64 (0.163-5.1, automatic),
>
Good morning,
I ran apt dist-upgrade on Stretch (with a few Sid packages) which made
the following changes:
Start-Date: 2016-06-14 19:42:39
Commandline: apt-get dist-upgrade
Requested-By: me (1000)
Install: libdw1:amd64 (0.163-5.1, automatic),
linux-image-4.6.0-1-amd64:amd64 (4.6.1-1,
12 matches
Mail list logo
