On Tue, 17 Apr 2018, Gdsi wrote: > Hi all. > I have sought a file for explain the booting delay. nothing besides this > wasn't:
[...] > Apr 17 05:10:15 debian systemd[1]: > dev-disk-by\x2duuid-3a64784b\x2d9807\x2d446a\x2dbc39\x2dc9011ba6ed6b.device: > Job > dev-disk-by\x2duuid-3a64784b\x2d9807\x2d446a\x2dbc39\x2dc9011ba6ed6b.device/start > timed out. > Apr 17 05:10:15 debian systemd[1]: Timed out waiting for device > dev-disk-by\x2duuid-3a64784b\x2d9807\x2d446a\x2dbc39\x2dc9011ba6ed6b.device. > Apr 17 05:10:15 debian systemd[1]: Dependency failed for > /dev/disk/by-uuid/3a64784b-9807-446a-bc39-c9011ba6ed6b. > Apr 17 05:10:15 debian systemd[1]: Dependency failed for Swap. > Apr 17 05:10:15 debian systemd[1]: swap.target: Job swap.target/start failed > with result 'dependency'. You have a swap device listed in /etc/fstab which doesn't exist. Edit /etc/fstab and comment out (type a # before everything) the line which starts with something like: UUID=3a64784b-9807-446a-bc39-c9011ba6ed6b swap sw and then you won't have this particular boot delay anymore. [Most likely, you caused it by running mkswapfs on this device, which changed the UUID.] -- Don Armstrong https://www.donarmstrong.com [A] theory is falsifiable [(and therefore scientific) only] if the class of its potential falsifiers is not empty. -- Sir Karl Popper _The Logic of Scientific Discovery_ ยง21
