Arch Linux

pedrodurek

Member

Registered: 2014-09-04

Posts: 1

Systemd bugs

Hi everyone, i'm using the toolchain Buildroot to build a custom OS for embedded, and the init which i 'm using is the systemd, but im having some problems with it, when i try to reboot the system with socket, serial open i have some erros like these:

[  307.687170] EXT4-fs (mmcblk0p2): error count: 2
[  307.687209] EXT4-fs (mmcblk0p2): initial error at 1: ext4_find_entry:1309: inode 149
[  307.687232] EXT4-fs (mmcblk0p2): last error at 1: htree_dirblock_to_tree:920: inode 262174: block 1056817

[ 6956.520833] EXT4-fs error (device mmcblk0p2): ext4_mb_generate_buddy:755: group 0, 23785 clusters in bitmap, 23788 in gd

[  301.287142] EXT4-fs (mmcblk0p2): error count: 6
[  301.287179] EXT4-fs (mmcblk0p2): initial error at 1: ext4_find_entry:1309: inode 149
[  301.287204] EXT4-fs (mmcblk0p2): last error at 1409861788: ext4_mb_generate_buddy:755

[   42.448904] EXT4-fs error (device mmcblk0p2): ext4_mb_generate_buddy:755: group 0, 23781 clusters in bitmap, 23784 in gd
[   47.067364] JBD2: Spotted dirty metadata buffer (dev = mmcblk0p2, blocknr = 0). There's a risk of filesystem corruption in case of system crash.
[   47.087307] JBD2: Spotted dirty metadata buffer (dev = mmcblk0p2, blocknr = 0). There's a risk of filesystem corruption in case of system crash.

[  301.287190] EXT4-fs (mmcblk0p2): error count: 7
[  301.287228] EXT4-fs (mmcblk0p2): initial error at 1: ext4_find_entry:1309: inode 149
[  301.287253] EXT4-fs (mmcblk0p2): last error at 1409926938: ext4_mb_generate_buddy:755

[  301.287157] EXT4-fs (mmcblk0p2): error count: 9
[  301.287196] EXT4-fs (mmcblk0p2): initial error at 1: ext4_find_entry:1309: inode 149
[  301.287223] EXT4-fs (mmcblk0p2): last error at 1409939054: ext4_mb_generate_buddy:755

And when i try to reboot system using "systemctl reboot", the systemd returns "Failed to get D-Bus connection: No connection to service manager.". How can i fix it? Plx help-me.

Last edited by pedrodurek (2014-09-09 14:13:20)

Trilby

Inspector Parrot

Registered: 2011-11-29

Posts: 30,480

Website

Re: Systemd bugs

Welcome to the forums.  Can you clarify if/how this is an archlinux question?  Wouldn't this be better directed upstream to a systemd mailing list or bug tracker?

---

"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

ANOKNUSA

Member

Registered: 2010-10-22

Posts: 2,141

Re: Systemd bugs

And when i try to reboot system using "systemctl reboot", the systemd returns "Failed to get D-Bus connection: No connection to service manager.".

The only time I've seen that error is when running systemctl on a system not booted via systemd. Since systemd absolutely must start dbus and connect to a socket to successfully bring up a system, I can't see how else it would crop up. I don't claim to understand all the systemd internals, though.

---

Linux != Windows  ::  Ask Questions the Smart Way  ::  Configs