Bug#804056: Systemd
Felipe Sateler
fsateler at debian.org
Wed Nov 4 12:45:51 GMT 2015
Control: tags -1 moreinfo
On 4 November 2015 at 08:15, <mila_s at op.pl> wrote:
> Package: systemd
> Version: jessie 8.2
> Severity: critical
> Date: 30 Oct 2015
>
> After upgrade from wheezy 7.9 to jessie 8.2 *server* boot in single ro mode. (Squeeze to Wheezy: OK)
> No network services.
> No remote login.
> No signs of problems on monitor:
> - sysvinit leave a couple of diagnostic messages on screen (anyone can read if server is ill)
> - systemd after upgrade - zero messages (server is OK but do not work -> it's like Microsoft)
The journal (inspect with `journalctl -b`) should have more information.
>
> My solution:
> A. Back to wheezy.
> B. In file /etc/fstab: bad UUID's for root file system. (UUID changed to /dev/sda2)
That is a documented change in the release notes.
> - after reboot - problem with /etc/init.d/iptables - don't load firewall.
I don't see this file in any debian package. Where did it come from?
Can we see its contents?
>
> Upgrade to jessie: suspended.
If you have the sysvinit package installed you can still boot using
sysv init adding init=/lib/sysvinit/init to your kernel command line.
--
Saludos,
Felipe Sateler
More information about the Pkg-systemd-maintainers
mailing list