Siduction Forum
Siduction Forum => Software - Support => Topic started by: GrafMager on 2018/12/29, 15:01:22
-
Hola Männer,
habe zur Zeit das Problem, dass beim Booten ein angebliches USB-Gerät nicht erkannt wird und somit die Startzeit unnötig verlängert wird. Hier das log:
Dez 29 14:54:15 livingroom-pc systemd[1]: dev-disk-by\x2duuid-38038b22\x2d9468\x2d4147\x2d8c13\x2df4cb560bc52d.device: Job dev-disk-by\x2duuid-38038b22\x2d9468\x2d4147\x2d8c13\x2df4cb560bc52d.device/start timed out.
Dez 29 14:54:15 livingroom-pc systemd[1]: Timed out waiting for device /dev/disk/by-uuid/38038b22-9468-4147-8c13-f4cb560bc52d.
Dez 29 14:54:15 livingroom-pc systemd[1]: Dependency failed for /dev/disk/by-uuid/38038b22-9468-4147-8c13-f4cb560bc52d.
Dez 29 14:54:15 livingroom-pc systemd[1]: dev-disk-by\x2duuid-38038b22\x2d9468\x2d4147\x2d8c13\x2df4cb560bc52d.swap: Job dev-disk-by\x2duuid-38038b22\x2d9468\x2d4147\x2d8c13\x2df4cb560bc52d.swap/start failed with result 'dependency'.
Dez 29 14:54:15 livingroom-pc systemd[1]: Startup finished in 2.539s (kernel) + 3min 666ms (userspace) = 3min 3.206s.
Dez 29 14:54:15 livingroom-pc systemd[1]: dev-disk-by\x2duuid-38038b22\x2d9468\x2d4147\x2d8c13\x2df4cb560bc52d.device: Job dev-disk-by\x2duuid-38038b22\x2d9468\x2d4147\x2d8c13\x2df4cb560bc52d.device/start failed with result 'timeout'.
Dez 29 14:55:01 livingroom-pc CRON[8886]: pam_unix(cron:session): session opened for user root by (uid=0)
Dez 29 14:55:01 livingroom-pc CRON[8887]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Dez 29 14:55:01 livingroom-pc CRON[8886]: pam_unix(cron:session): session closed for user root
was ist zu tun? Ich vermute, dass er nach dem USB-Bootstick sucht, mit dem ich neulich gparted gebootet habe, um meine root-Partition zu vergrößern ...
-
Zeig mal bitte die Ausgabe von
systemd-analyze blame
-
And try
# blkid -c /dev/null -o list
-
systemd-analyse blame:
2.838s NetworkManager-wait-online.service
1.298s udisks2.service
751ms apt-daily.service
718ms dev-sda2.device
573ms apt-daily-upgrade.service
323ms phpsessionclean.service
311ms apache2.service
300ms virtualbox.service
279ms systemd-journal-flush.service
270ms logrotate.service
262ms systemd-logind.service
260ms ModemManager.service
234ms accounts-daemon.service
195ms NetworkManager.service
183ms systemd-udev-trigger.service
177ms systemd-sysusers.service
176ms proc-fs-nfsd.mount
169ms exim4.service
165ms nfs-blkmap.service
160ms systemd-random-seed.service
148ms avahi-daemon.service
135ms x1920.service
135ms keyboard-setup.service
134ms smbd.service
132ms wpa_supplicant.service
102ms systemd-fsck@dev-disk-by\x2duuid-f0617869\x2dd4a6\x2d4f15\x2d9cb8\x2d469833abfab2.service
98ms loadcpufreq.service
96ms systemd-journald.service
95ms systemd-timesyncd.service
83ms fancontrol.service
76ms nfs-server.service
75ms lvm2-lvmetad.service
74ms preload.service
73ms blk-availability.service
69ms gpm.service
68ms media-Videos.mount
68ms systemd-tmpfiles-setup-dev.service
66ms ifupdown-pre.service
66ms systemd-sysctl.service
64ms nmbd.service
62ms ssh.service
60ms nfs-mountd.service
52ms lm-sensors.service
48ms systemd-fsck@dev-disk-by\x2duuid-4874c536\x2df944\x2d43bf\x2d8898\x2d02423db5d439.service
47ms systemd-udevd.service
45ms networking.service
43ms lvm2-monitor.service
42ms user@1000.service
39ms run-rpc_pipefs.mount
36ms systemd-remount-fs.service
35ms ifupdown-wait-online.service
35ms systemd-fsck@dev-disk-by\x2duuid-8e16eefe\x2d47da\x2d4b66\x2d9373\x2de8ea30d0b3c3.service
32ms dev-mqueue.mount
31ms atd.service
31ms kmod-static-nodes.service
29ms alsa-restore.service
29ms polkit.service
29ms sys-kernel-debug.mount
27ms binfmt-support.service
26ms dev-hugepages.mount
25ms sysstat.service
25ms saned.service
24ms sddm.service
22ms home.mount
22ms boot.mount
19ms rpcbind.service
18ms systemd-user-sessions.service
18ms hddtemp.service
14ms user-runtime-dir@1000.service
14ms systemd-tmpfiles-setup.service
14ms cpufrequtils.service
14ms systemd-modules-load.service
10ms systemd-update-utmp.service
10ms sys-fs-fuse-connections.mount
9ms console-setup.service
8ms proc-sys-fs-binfmt_misc.mount
8ms nfs-config.service
8ms home-grafmager-Videos.mount
7ms nfs-idmapd.service
7ms home-reesee-Videos.mount
6ms tmp.mount
6ms systemd-update-utmp-runlevel.service
blkid -c /dev/null -o list
device fs_type label mount point UUID
/dev/sdb1 ext4 /media/Videos f0617869-d4a6-4f15-9cb8-469833abfab2
/dev/sda1 ext2 /boot 8e16eefe-47da-4b66-9373-e8ea30d0b3c3
/dev/sda2 ext4 root / 18b68ba7-aa30-4ec1-be77-d6c7be2e1ba0
/dev/sda3 swap (not mounted) eaea065e-70cf-4457-bdbc-716a71778a40
/dev/sda4 ext4 home /home 4874c536-f944-43bf-8898-02423db5d439
-
cat /etc/fstab
-
UUID=8e16eefe-47da-4b66-9373-e8ea30d0b3c3 /boot ext2 defaults,relatime,errors=remount-ro 0 2
UUID=18b68ba7-aa30-4ec1-be77-d6c7be2e1ba0 / ext4 defaults,relatime,errors=remount-ro 0 1
UUID=38038b22-9468-4147-8c13-f4cb560bc52d none swap sw 0 0
UUID=4874c536-f944-43bf-8898-02423db5d439 /home ext4 defaults,relatime,errors=remount-ro 0 2
UUID=f0617869-d4a6-4f15-9cb8-469833abfab2 /media/Videos ext4 defaults,relatime,errors=remount-ro 0 2
UUID=4b686eaf-cb98-4e2c-88ae-dbceeed2bd02 /media/4tb_wdblue ext4 noauto,defaults,relatime,errors=remount-ro 0 2
Lese ich das korrekt, dass der Swap-Speicher Schuld ist?
-
Lese ich das korrekt, dass der Swap-Speicher Schuld ist?
Ja.
In /etc/fstab, replace 38038b22-9468-4147-8c13-f4cb560bc52d with eaea065e-70cf-4457-bdbc-716a71778a40
then
# mount -a
-
Noch besser - gib dem doofen swap nen namen und bind den über den Namen ein
-
Naja, allzu oft ändere ich die Position des swap auf der Platte ja nicht. In dem Fall musste ich ihn verschieben, damit ich meine root-Partition vergrößern kann. Wenn ich das nächste Mal keinen Platz mehr habe, kommt eh ne neue Platte rein ;)
Danke für eure - immer - kompetente Hilfe!