Arch Linux

floxynta

Member

Registered: 2013-01-29

Posts: 3

[SOLVED] systemctl failed:systemd-random-seed-load slim NetworkManager

Hi,
I'm using Arch for almost 4 year, and I could solve all problems that I had before, but this I can't.
After update, my system doesn't work properly.

UNIT                             LOAD   ACTIVE SUB    DESCRIPTION
httpd.service                    loaded failed failed Apache Web Server
NetworkManager.service           loaded failed failed Network Manager
slim.service                     loaded failed failed SLiM Simple Login Manager
systemd-random-seed-load.service loaded failed failed Load Random Seed

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.

4 loaded units listed.
To show all installed unit files use 'systemctl list-unit-files'.

systemctl status systemd-random-seed-load slim NetworkManager

Slim, NetworkManager, httpd are not so important, i ignored them, and disabled for the moment. After rebooting i have only one tty (tty1) any others a dead, or at least i can't switch to them. Logging in on tty1 with my user, I'm getting an error something like this> systemd-login.service failed and after this I can  continue work.

cat /var/log/pacman.log. Previous update was on 2013-01-11.

I don't know what broke the systems : /

Last edited by floxynta (2013-02-02 16:05:29)

Jub

Member

From: Secret Fort

Registered: 2009-11-18

Posts: 10

Website

Re: [SOLVED] systemctl failed:systemd-random-seed-load slim NetworkManager

Are you using the LTS kernel? I noticed in your pacman.log that you have 3 different kernels. Also,

WARNING: errors were encountered during the build. The image may not be complete.

can't be good..
Go into your /boot and try a mkinitcpio -k vmlinuz-linux -g /boot/initramfs-vmlinuz-linux2.img
Does it work?

---

I never know what to make my signature...

floxynta

Member

Registered: 2013-01-29

Posts: 3

Re: [SOLVED] systemctl failed:systemd-random-seed-load slim NetworkManager

No, I'm using kernel-pae, but with stock kernel I get the same result.

Go into your /boot and try a mkinitcpio -k vmlinuz-linux -g /boot/initramfs-vmlinuz-linux2.img

builds with no errors. Booting on this nothing changes.

Last edited by floxynta (2013-01-29 21:32:00)

floxynta

Member

Registered: 2013-01-29

Posts: 3

Re: [SOLVED] systemctl failed:systemd-random-seed-load slim NetworkManager

Ok, i figured it out. The problem was in upgrading the filesystem.
I have two Hard Disk, and one of them is SSD. My root partition is on SSD, but  /var i linked  to an folder from second HDD. 

# ls -alh /var
lrwxrwxrwx 1 root root 16 Jan 22 15:33 /var -> /media/root/var2

# ls -alh /var/
total 44K
drwxr-xr-x 11 root root  4.0K Feb  1 21:36 .
drwxr-xr-x 24 root root  4.0K Feb  1 20:50 ..
drwxr-xr-x  4 root root  4.0K Jan 29 14:46 db
drwxr-xr-x  2 root root  4.0K Jan 22 15:13 empty
drwxrwxr-x  2 root games 4.0K Jan 27 09:28 games
drwxr-xr-x 35 root root  4.0K Jan 29 14:47 lib
drwxr-xr-x  2 root root  4.0K Jan 27 09:28 local
drwxr-xr-x 10 root root  4.0K Feb  2 12:26 log
drwxr-xr-x  2 root root  4.0K Jan 27 09:28 opt
drwxr-xr-x  5 root root  4.0K Jan 29 14:46 spool
drwxrwxrwt 62 root root  4.0K Feb  2 17:49 tmp
lrwxrwxrwx  1 root root    21 Jan 22 15:32 cache -> /media/root/var/cache
lrwxrwxrwx  1 root root     9 Feb  1 21:35 lock -> /run/lock
lrwxrwxrwx  1 root root    11 Jan 27 09:28 lock.bk -> ../run/lock #after upgrade it was rewritten
lrwxrwxrwx  1 root root    10 Jan 27 09:28 mail -> spool/mail
lrwxrwxrwx  1 root root     4 Feb  1 21:36 run -> /run 
lrwxrwxrwx  1 root root     6 Jan 27 09:28 run.bk -> ../run #after upgrade it was rewritten

So, I renamed my run and lock to run.bk and lock.bk, and recreated the links

But issues with systemd-random-seed-load.service anyway persist.

Last edited by floxynta (2013-02-02 16:02:28)

drtechie

Member

Registered: 2012-02-29

Posts: 5

Re: [SOLVED] systemctl failed:systemd-random-seed-load slim NetworkManager

Ok, i figured it out. The problem was in upgrading the filesystem.
I have two Hard Disk, and one of them is SSD. My root partition is on SSD, but  /var i linked  to an folder from second HDD. 

So, I renamed my run and lock to run.bk and lock.bk, and recreated the links

But issues with systemd-random-seed-load.service anyway persist.

Hey I had the same issue too. I have a SSD and a HDD. /var is located in HDD. I got some errors during boot especially the 'Random seed' one.
Problem is all these errors occured because these services depended on /var and were started before /var on the HDD was mounted. I edited those unit files and added

After=hdd.mount #I have a partition that mounts on /hdd 

For each service that failed to load, I added the line.
And it worked !

Unit files are located in

/usr/lib/systemd/system

The one concerning you should be 'systemd-random-seed-load.service'