Hello we have some nodes that don't boot cleanly, CTRL-D or logging into the node
allows the system to finish the startup properly.
selinux-autorelabel-mark.service: Job selinux-autorelabel-mark.service/start failed with
result 'dependency'
systemd[1]: Timed out waiting for device
dev-disk-by\x2duuid-3839035f\x2db3be\x2d4b8b\x2db711\x2df19bee4785f2.device.
systemd[1]: Dependency failed for /gluster_bricks/extra.
systemd[1]: Dependency failed for Local File Systems.
systemd[1]: Dependency failed for Mark the need to relabel after reboot.
systemd[1]: selinux-autorelabel-mark.service: Job selinux-autorelabel-mark.service/start
failed with result 'dependency'.
systemd[1]: local-fs.target: Job local-fs.target/start failed with result
'dependency'.
systemd[1]: local-fs.target: Triggering OnFailure= dependencies.
systemd[1]: gluster_bricks-extra.mount: Job gluster_bricks-extra.mount/start failed with
result 'dependency'.
systemd[1]: dev-disk-by\x2duuid-3839035f\x2db3be\x2d4b8b\x2db711\x2df19bee4785f2.device:
Job dev-disk-by\x2duuid-3839035f\x2db3be\x2d4b8b\x2db711\x2df19bee4785f2.device/start
failed with result 'timeout'.
The other gluster bricks created at install time don't have this problem.
Thanks,
Paul S.
Show replies by date