在一台新机子上面，docker处理完lvs数据卷之后，启动docker服务时，出现了启动失败，失败信息如下：
[root@hxin221 ~]# systemctl status docker
● docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)
Drop-In: /usr/lib/systemd/system/docker.service.d
└─flannel.conf
Active: failed (Result: exit-code) since Tue 2018-07-24 14:06:15 CST; 4s ago
Docs: https://docs.docker.com
Process: 28723 ExecStart=/usr/bin/dockerd $DOCKER_NETWORK_OPTIONS $DOCKER_NETWORK_OPTIONS $DOCKER_STORAGE_OPTIONS (code=exited, status=1/FAILURE)
Main PID: 28723 (code=exited, status=1/FAILURE)
Memory: 412.0K
CGroup: /system.slice/docker.service
Jul 24 14:06:14 hxin221 systemd[1]: Starting Docker Application Container Engine...
Jul 24 14:06:14 hxin221 dockerd[28723]: time="2018-07-24T14:06:14.416711161+08:00" level=info msg="libcontainerd: new containerd process, pid: 28738"
Jul 24 14:06:15 hxin221 dockerd[28723]: Error starting daemon: error initializing graphdriver: devmapper: Base Device UUID and Filesystem verification failed: devicemapper: Error running deviceCreate (ActivateDevice) dm_task_run failed
Jul 24 14:06:15 hxin221 systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE
Jul 24 14:06:15 hxin221 systemd[1]: Failed to start Docker Application Container Engine.
Jul 24 14:06:15 hxin221 systemd[1]: Unit docker.service entered failed state.
Jul 24 14:06:15 hxin221 systemd[1]: docker.service failed.
总的来说就是：
Error starting daemon: error initializing graphdriver: devmapper: Base Device UUID and Filesystem verification failed: devicemapper: Error running deviceCreate (ActivateDevice) dm_task_run failed
好吧，这个错误，之前没有遇到过，踩了很多坑，最终，想了想，莫非这台机子早先时候已经装了docker，然后旧数据导致的？
于是乎，就抱着试试看的目的，执行了如下操作：
[root@hxin221 ~]# rm -rf /var/lib/docker/*
没错，清除了docker的数据，由于是新机子，我也没有做什么备份处理，其他小伙伴如果又遇到的话，记得先备份数据。
于是，重启服务
[root@hxin221 ~]# systemctl restart docker
OK，问题不大，解决了。
以上
devicemapper: Error running deviceCreate (ActivateDevice) dm_task_run failed