Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
"Failed to talk to init daemon"
523 views
Skip to first unread message
D.M. Procida
May 1, 2017, 5:03:48 PM5/1/17
to
My AFP server stopped working, so I decided to reboot it:
pi@raspberry-pi-server:~ $ sudo reboot
Failed to start reboot.target: Activation of
org.freedesktop.systemd1 timed out
Failed to open initctl FIFO: No such device or address
Failed to talk to init daemon.
Any idea what's up?
Daniele
pi@raspberry-pi-server:~ $ sudo reboot
Failed to start reboot.target: Activation of
org.freedesktop.systemd1 timed out
Failed to open initctl FIFO: No such device or address
Failed to talk to init daemon.
Any idea what's up?
Daniele
D.M. Procida
May 1, 2017, 5:48:43 PM5/1/17
to
D.M. Procida <real-not-anti...@apple-juice.co.uk> wrote:
> My AFP server stopped working, so I decided to reboot it:
>
> pi@raspberry-pi-server:~ $ sudo reboot
> Failed to start reboot.target: Activation of
> org.freedesktop.systemd1 timed out
> Failed to open initctl FIFO: No such device or address
> Failed to talk to init daemon.
I ran apt-get upgrade, as this seems to be some sort of kernel issue.
> My AFP server stopped working, so I decided to reboot it:
>
> pi@raspberry-pi-server:~ $ sudo reboot
> Failed to start reboot.target: Activation of
> org.freedesktop.systemd1 timed out
> Failed to open initctl FIFO: No such device or address
> Failed to talk to init daemon.
Now we are stuck on:
Unpacking raspberrypi-bootloader (1.20170427-1) over (1.20170405-1)
...
Setting up raspberrypi-bootloader (1.20170427-1) ...
Removing 'diversion of /boot/start.elf to
/usr/share/rpikernelhack/start.elf by rpikernelhack'
and have been for quite some time...
Daniele
Eli the Bearded
May 1, 2017, 6:56:07 PM5/1/17
to
In comp.sys.raspberry-pi,
That's a symptom of systemd dying. I've had that happen to me before,
and I've needed to resort to "magic sysrequests" to reboot.
https://en.wikipedia.org/wiki/Magic_SysRq_key
There are ways for a root user to activate the magic sysrequests via
the filesystem, if you can't type them with a SysRq key, eg over a
network connection.
Elijah
------
my dictionary says AFP: alpha fetoprotein
and I've needed to resort to "magic sysrequests" to reboot.
https://en.wikipedia.org/wiki/Magic_SysRq_key
There are ways for a root user to activate the magic sysrequests via
the filesystem, if you can't type them with a SysRq key, eg over a
network connection.
Elijah
------
my dictionary says AFP: alpha fetoprotein
D.M. Procida
May 2, 2017, 5:02:31 PM5/2/17
to
$ ~ f3write /Volumes/Untitled
Free space: 3.61 GB
Creating file 1.h2w ... OK!
Creating file 2.h2w ... OK!
Creating file 3.h2w ... OK!
Creating file 4.h2w ... OK!
Free space: 0.00 Byte
Average writing speed: 1.15 MB/s
$ ~ f3read /Volumes/Untitled
SECTORS ok/corrupted/changed/overwritten
Validating file 1.h2w ... 2097152/ 0/ 0/ 0
Validating file 2.h2w ... 2097152/ 0/ 0/ 0
Validating file 3.h2w ... 404848/ 0/ 0/ 0 - NOT fully
read due to "Resource busy"
Validating file 4.h2w ... 1275912/ 0/ 0/ 0
Assertion failed: (tot_size / SECTOR_SIZE == (tot_ok + tot_corrupted +
tot_changed + tot_overwritten)), function iterate_files, file f3read.c,
line 210.
[1] 15899 abort f3read /Volumes/Untitled
Dainele
0 new messages