kayel
Posts: 109
Joined: Sun May 13, 2012 4:45 am
Location: France

[SOLVED]raspi-config.serviZzzzz...

Mon Aug 21, 2017 7:00 am

Hi all,

I have a very slow Packard Bell EasyNote LE with an AMD Dual-Core Processor E1-1200 and 4GB DDR3 memory.

I just installed Raspberry Pi Desktop.

When I boot it gets "stuck" at "raspi-config.service" for more than a minute before continuing.

Is that normal or is there a timeout I can reduce somewhere?

Apart from that, it works a treat. :D
Last edited by kayel on Mon Aug 21, 2017 9:00 pm, edited 1 time in total.

ShiftPlusOne
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5339
Joined: Fri Jul 29, 2011 5:36 pm
Location: The unfashionable end of the western spiral arm of the Galaxy

Re: raspi-config.serviZzzzz...

Mon Aug 21, 2017 9:45 am

Definitely not expected. The output of 'sudo journalctl' and `systemd-analyze blame` could be helpful.

kayel
Posts: 109
Joined: Sun May 13, 2012 4:45 am
Location: France

Re: raspi-config.serviZzzzz...

Mon Aug 21, 2017 5:46 pm

Thanks for replying. Sorry I took so long to get back.
When I tried to attach analyze-blame.txt and journalctl.txt to this post I got an error message saying they had the wrong extension. I changed their names to analyze-blame and journalctl (no extension) and got the same error message. Hence the messy dump.


ANALYZE-BLAME OUTPUT

5.971s keyboard-setup.service
4.220s hdparm.service
1.971s raspi-config.service
1.423s lightdm.service
1.220s dphys-swapfile.service
1.128s ntp.service
891ms alsa-restore.service
863ms systemd-logind.service
850ms resolvconf.service
847ms dhcpcd.service
844ms triggerhappy.service
842ms irqbalance.service
806ms avahi-daemon.service
784ms systemd-tmpfiles-setup-dev.service
730ms dev-mqueue.mount
728ms dev-hugepages.mount
712ms networking.service
653ms rsyslog.service
628ms sys-kernel-debug.mount
627ms systemd-setup-dgram-qlen.service
508ms systemd-udev-trigger.service
466ms udev-finish.service
465ms kbd.service
394ms rc-local.service
347ms sys-fs-fuse-connections.mount
327ms kmod-static-nodes.service
317ms systemd-modules-load.service
242ms console-setup.service
218ms polkitd.service
214ms udisks2.service
209ms plymouth-quit-wait.service
208ms plymouth-quit.service
196ms systemd-tmpfiles-setup.service
184ms systemd-udevd.service
145ms plymouth-start.service
135ms [email protected]
127ms systemd-user-sessions.service
126ms plymouth-read-write.service
126ms systemd-tmpfiles-clean.service
119ms [email protected]
118ms [email protected]
113ms [email protected]:acpi_video0.service
103ms rtkit-daemon.service
88ms systemd-random-seed.service
77ms systemd-sysctl.service
74ms bluetooth.service
58ms systemd-journal-flush.service
57ms [email protected]:radeon_bl0.service
53ms systemd-update-utmp.service
52ms systemd-remount-fs.service
28ms live-tools.service
14ms systemd-update-utmp-runlevel.service

JOURNALCTL OUTPUT (tail)

Aug 21 17:21:30 raspberry systemd[1]: Job dev-disk-by\x2duuid-e38b2e0a\x2d1b36\x2d4ab1\x2d9cec\x2da98920859867.device/start timed out.
Aug 21 17:21:30 raspberry systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-e38b2e0a\x2d1b36\x2d4ab1\x2d9cec\x2da98920859867.device.
Aug 21 17:21:30 raspberry systemd[1]: Dependency failed for /dev/disk/by-uuid/e38b2e0a-1b36-4ab1-9cec-a98920859867.
Aug 21 17:21:30 raspberry systemd[1]: Startup finished in 6.555s (kernel) + 3min 1.739s (userspace) = 3min 8.294s.
Aug 21 17:30:13 raspberry sudo[1303]: pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/bin/journalctl
Aug 21 17:30:13 raspberry sudo[1303]: pam_unix(sudo:session): session opened for user root by (uid=0)
Aug 21 17:31:01 raspberry sudo[1303]: pam_unix(sudo:session): session closed for user root
Aug 21 17:31:22 raspberry sudo[1306]: pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/bin/journalctl
Aug 21 17:31:22 raspberry sudo[1306]: pam_unix(sudo:session): session opened for user root by (uid=0)

The system is on dual boot with Arch linux. The /dev/disk errors ring a bell. There was a problem with the swap partition after installing Pi Desktop, so I got rid of it and created a new one and changed the uuid to the new one in fstab. Everything works fine, even my home-made USB-Serial cable worked out-of-the-box (that's a first!)

I'd be happy with a quick 'n dirty, "sweep it under the carpet" solution like reducing the time-out delay, but as Duke Nukem would say, "Where is it?"

kayel
Posts: 109
Joined: Sun May 13, 2012 4:45 am
Location: France

Re: [SOLVED]raspi-config.serviZzzzz...

Mon Aug 21, 2017 9:38 pm

SOLVED

I had Q4OS on sda1, swap on sda2 and Arch on sda3. Q4os started getting a bit flaky, so I replaced it with Pi Desktop on sda1. The long wait was caused by the UUID of the swap partition being different to the one expected, causing a search for something that wasn't there until the timeout put an end to it.

I changed the UUID of the swap partition in fstab to what gparted said it was. This transferred the problem to Arch where on booting I got a message saying I'd have to wait 1min 30s. I changed the swap UUID in Arch's fstab so it was the same as in Pi Desktop's and that did it.

My Bubble-car has become a Ferrari! :D

Return to “Debian”