Palooka
5th March 2012, 02:06 PM
Fedora 17 Alpha (64 bit) in VirtualBox.
I noticed a message during the (non-quiet) boot.
Looking at /var/log/messages I see this:
Mar 5 13:20:23 f17b systemd[1]: Job dev-disk-by\x2duuid-e1076e59\x2d4be9\x2d4709\x2d867d\x2df19d7fc7e210.d evice/start timed out.
Mar 5 13:20:23 f17b systemd[1]: Job dev-disk-by\x2duuid-e1076e59\x2d4be9\x2d4709\x2d867d\x2df19d7fc7e210.s wap/start failed with result 'dependency'.
Mar 5 13:20:23 f17b systemd[1]: Job dev-disk-by\x2duuid-e1076e59\x2d4be9\x2d4709\x2d867d\x2df19d7fc7e210.d evice/start failed with result 'timeout'.
The uuid corresponds to my swap partition.
swapon -s comes up empty. So I infer that the error is the reason why the swap partition is not being made available during boot.
checking /etc/sftab - all looks in order. The swap partition is listed.
So a quick test: sudo swapon -a
works!swapon -s now lists my swap partition.
So my question is this: How come it is failing at boot time?
I noticed a message during the (non-quiet) boot.
Looking at /var/log/messages I see this:
Mar 5 13:20:23 f17b systemd[1]: Job dev-disk-by\x2duuid-e1076e59\x2d4be9\x2d4709\x2d867d\x2df19d7fc7e210.d evice/start timed out.
Mar 5 13:20:23 f17b systemd[1]: Job dev-disk-by\x2duuid-e1076e59\x2d4be9\x2d4709\x2d867d\x2df19d7fc7e210.s wap/start failed with result 'dependency'.
Mar 5 13:20:23 f17b systemd[1]: Job dev-disk-by\x2duuid-e1076e59\x2d4be9\x2d4709\x2d867d\x2df19d7fc7e210.d evice/start failed with result 'timeout'.
The uuid corresponds to my swap partition.
swapon -s comes up empty. So I infer that the error is the reason why the swap partition is not being made available during boot.
checking /etc/sftab - all looks in order. The swap partition is listed.
So a quick test: sudo swapon -a
works!swapon -s now lists my swap partition.
So my question is this: How come it is failing at boot time?
