Hi Michael,
thanks for your quick reply!
Quoting Michael Biebl (2014-08-21 16:06:57)
> Hi Johannes,
>
> Am 21.08.2014 15:55, schrieb Johannes Schauer:
> > I see that you closed this bugreport. Is the issue of my filesystems not
> > being
> > mounted tracked under another bug?
>
> LVM volumes s
Hi Johannes,
Am 21.08.2014 15:55, schrieb Johannes Schauer:
> I see that you closed this bugreport. Is the issue of my filesystems not being
> mounted tracked under another bug?
LVM volumes should work. If they don't then this is a regression
Please file a separate bug report for this. Conflating
Hi Michael,
sorry that it took me two days to come back to you but I was attending the
Debian Bootstrap sprint and could not afford to reboot my laptop and end up
with a possibly broken system these days.
Quoting Michael Biebl (2014-08-19 16:15:31)
> Johannes, it seems that we tracked this issue
Am 22.07.2014 13:23, schrieb Michael Biebl:
> Am 22.07.2014 09:45, schrieb Johannes Schauer:
>> Secondly, it is not very helpful to have the emergency mode message
>> spawn in an (seemingly) infinite loop. I should not have to boot with
>> init=/bin/bash. Instead, the emergency mode should start an
Removing the old udev rules did indeed resolve the precipitating error and allow
a smooth boot.
I kept the files so I could recreate the boot dependency failure, so if anyone
has an idea as to what output would be useful for me to collect to diagnose the
strange emergency shell behavior, I can ta
It took a while to grep the vol_id culprit. It's probably this:
/usr/share/initramfs-tools/scripts/functions: elif [ "$FSTYPE" = "unknown" ]
&& [ -x /lib/udev/vol_id ]; then
/usr/share/initramfs-tools/scripts/functions:
FSTYPE=$(/lib/udev/vol_id -t "${FS}" 2> /dev/null)
--
To UNS
Am 27.07.2014 04:04, schrieb Brian Julin:
>
> Michael Biebl wrote:
>
>> You have a broken/outdated 60-persistent-storage.rules in
>> /etc/udev/rules.d. Why?
>
> I don't know why. I pasted my package history for udev|systemd at the end of
> the email.
>
>> You have a device listed in /etc/fsta
Michael Biebl wrote:
> You have a broken/outdated 60-persistent-storage.rules in
> /etc/udev/rules.d. Why?
I don't know why. I pasted my package history for udev|systemd at the end of
the email.
> You have a device listed in /etc/fstab which doesn't exist during boot,
> Please double check if
Am 26.07.2014 21:33, schrieb Brian Julin:
>
> Michael Biebl wrote:
>> Am 26.07.2014 20:10, schrieb Brian Julin:
>>> 3) If you enable "quiet" and run the recovery mode, you will get login
>>> prompts
>>> within a minute or two. You will get two login prompts running
>>> simultaneously.
>>> Once
Michael Biebl wrote:
>Am 26.07.2014 20:10, schrieb Brian Julin:
>> 3) If you enable "quiet" and run the recovery mode, you will get login
>> prompts
>> within a minute or two. You will get two login prompts running
>> simultaneously.
>> Once you have provided a password to one of the prompts, t
Am 26.07.2014 20:10, schrieb Brian Julin:
>
> I just went through this ordeal myself. Here are some observations.
>
> 1) The problem causing the OP to enter emergency mode in the first place
> is likely because systemd does not seem to (with current packages) want
> to do anything with swap or n
I just went through this ordeal myself. Here are some observations.
1) The problem causing the OP to enter emergency mode in the first place
is likely because systemd does not seem to (with current packages) want
to do anything with swap or non-root partitions that are referenced by
UUID in /etc
Hi,
Quoting Michael Biebl (2014-07-22 13:54:48)
> Might also be the same as
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751624#49
maybe. Except that for me, a prompt was never displayed.
cheers, josch
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject
Am 22.07.2014 13:34, schrieb Johannes Schauer:
> Hi,
>
> Quoting Michael Biebl (2014-07-22 13:23:13)
>> Am 22.07.2014 09:45, schrieb Johannes Schauer:
>>> Secondly, it is not very helpful to have the emergency mode message
>>> spawn in an (seemingly) infinite loop. I should not have to boot with
>
Hi,
Quoting Michael Biebl (2014-07-22 13:23:13)
> Am 22.07.2014 09:45, schrieb Johannes Schauer:
> > Secondly, it is not very helpful to have the emergency mode message
> > spawn in an (seemingly) infinite loop. I should not have to boot with
> > init=/bin/bash. Instead, the emergency mode should
Am 22.07.2014 09:45, schrieb Johannes Schauer:
> Package: systemd
> Version: 208-6
> Severity: normal
>
> Hi,
>
> after I upgraded systemd today my system became unbootable. I removed
> the "quiet" option from the kernel boot options and after waiting a
> while I can see the following:
>
> [ TIM
Am 22.07.2014 09:45, schrieb Johannes Schauer:
> Secondly, it is not very helpful to have the emergency mode message
> spawn in an (seemingly) infinite loop. I should not have to boot with
> init=/bin/bash. Instead, the emergency mode should start and allow me to
> analyze the situation.
Samuel fi
Package: systemd
Version: 208-6
Severity: normal
Hi,
after I upgraded systemd today my system became unbootable. I removed
the "quiet" option from the kernel boot options and after waiting a
while I can see the following:
[ TIME ] Timed out waiting for device dev-mapper-volumegroup/x2dhome.devic
18 matches
Mail list logo
