Thanks Michael, and sorry for the delay. I can confirm that this issue
is fixed after the latest update to my system.
--
Joel Cross
j...@kazbak.co.uk
On Tue, 20 Jun 2017, at 09:59 PM, Michael Biebl wrote:
> Am 20.06.2017 um 22:54 schrieb Michael Biebl:
> > Unfortunately the problem is not re
Am 20.06.2017 um 22:54 schrieb Michael Biebl:
> Unfortunately the problem is not reproducible here (tried with a VM with
> several attached disks and a split /usr on the second disk).
I take that back. I just installed live-config-systemd in the test VM
and that completely hosed the systemd and I'
Am 20.06.2017 um 22:54 schrieb Michael Biebl:
> Mar 29 21:23:39 abijah systemd[268]:
> /lib/systemd/system-generators/live-config-getty-generator failed with
> error code 2.
>
> How exactly did you install the system?
> This file seems to belong to live-config-systemd, can you try and purge
> that
Am 20.06.2017 um 12:32 schrieb Joel Cross:
> Dear Michael/Maintainers,
>
> Just to update you on this: it has been 2 months since my last
> submission, and I am still having the same problem. Has anyone had the
> chance to look into what the cause could be here?
Unfortunately the problem is not r
Dear Michael/Maintainers,
Just to update you on this: it has been 2 months since my last
submission, and I am still having the same problem. Has anyone had the
chance to look into what the cause could be here?
On Wed, 12 Apr 2017, at 02:28 PM, Michael Biebl wrote:
> Am 12.04.2017 um 22:11 schrieb Joel Cross:
> > Mar 29 21:25:09 abijah systemd[1]:
> > dev-disk-by\x2duuid-F0C4F042C4F00C9A.device: Job
> > dev-disk-by\x2duuid-F0C4F042C4F00C9A.device/start failed with result
> > 'timeout'.
> > Mar 29 21:25
Am 12.04.2017 um 22:11 schrieb Joel Cross:
> Mar 29 21:25:09 abijah systemd[1]:
> dev-disk-by\x2duuid-F0C4F042C4F00C9A.device: Job
> dev-disk-by\x2duuid-F0C4F042C4F00C9A.device/start failed with result
> 'timeout'.
> Mar 29 21:25:09 abijah systemd[1]:
> dev-disk-by\x2duuid-0797ee37\x2dd1b9\x2d4
(Apologies all - it seems I accidentally sent these logs only to Michael
before)
On Mon, 27 Mar 2017, at 10:43 PM, Michael Biebl wrote:
>
> When you are dropped into the recovery shell, please save the output of
> udevadm info /sys/class/block/sdb2
> and attach it to the bug report.
> A complete
Hi,
Le 31/03/2017 à 10:21, Michael Biebl a écrit :
The udevadm info dump you attached shows that TAGS=:systemd: is missing
for all your partitions, thus systemd doesn't consider them ready.
The flag is no more missing, and the boot problem is still present.
udevadm info /dev/sda6
P:
/devices
Am 31.03.2017 um 09:13 schrieb Emmanuel DECAEN:
> Hi,
>
> The system boots correctly using sysV grub option, but randomly fails
> during boot using systemd (grub default).
>
> /etc/fstab:
> #
> proc/proc procdefaults0 0
> # / was on /dev/sda
Hi,
The system boots correctly using sysV grub option, but randomly fails
during boot using systemd (grub default).
/etc/fstab:
#
proc/proc procdefaults0 0
# / was on /dev/sda1 during installation
UUID=0ab4af79-6e21-4c58-8514-2cf849d53ae1
Am 30.03.2017 um 23:07 schrieb Emmanuel DECAEN:
> Hi,
>
> I have the same of problem on multiple servers with systemd/232-19.
>
> You will find journalctl -alb et udevadm info in attachments.
Your journal shows problems with /var, /tmp, /home and swap.
Makes me wonder if your /etc/fstab is actu
Control: tags -1 + moreinfo
Am 02.03.2017 um 19:20 schrieb Joel Cross:
> -- Subject: Unit dev-sdb2.device has failed
> -- Defined-By: systemd
> -- Support: https://www.debian.org/support
> --
> -- Unit dev-sdb2.device has failed.
> --
> -- The result is timeout.
> Mar 02 11:26:47 abijah systemd[1
13 matches
Mail list logo
