Docker Daemon won't start due to graphdriver uuid verification error on Centos

General
1

Hey

My docker daemon just crashed out and now fails to start with the following error:

docker.service - Docker Application Container Engine
   Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Tue 2016-08-09 10:30:44 BST; 23min ago
     Docs: https://docs.docker.com
  Process: 2610 ExecStart=/usr/bin/dockerd (code=exited, status=1/FAILURE)
 Main PID: 2610 (code=exited, status=1/FAILURE)

Aug 09 10:30:43 qa-docker01 systemd[1]: Starting Docker Application Container Engine...
Aug 09 10:30:43 qa-docker01 dockerd[2610]: time="2016-08-09T10:30:43.734710210+01:00" level=info msg="libcontainerd: new containerd process, pid: 2616"
Aug 09 10:30:44 qa-docker01 dockerd[2610]: time="2016-08-09T10:30:44.767439991+01:00" level=warning msg="devmapper: Usage of loopback devices is strongly discouraged for production use. Please use `--storage-opt dm.thinpooldev` or use `man docker` to refer to dm.thinpooldev section."
Aug 09 10:30:44 qa-docker01 dockerd[2610]: time="2016-08-09T10:30:44.822069024+01:00" level=error msg="[graphdriver] prior storage driver \"devicemapper\" failed: devmapper: Base Device UUID and Filesystem verification failed: devmapper: Failed to find uuid for device /dev/mapper/docker-253:0-525713-base:exit status 2"
Aug 09 10:30:44 qa-docker01 dockerd[2610]: time="2016-08-09T10:30:44.822285680+01:00" level=fatal msg="Error starting daemon: error initializing graphdriver: devmapper: Base Device UUID and Filesystem verification failed: devmapper: Failed to find uuid for device /dev/mapper/docker-253:0-525713-base:exit status 2"
Aug 09 10:30:44 qa-docker01 systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE
Aug 09 10:30:44 qa-docker01 systemd[1]: Failed to start Docker Application Container Engine.
Aug 09 10:30:44 qa-docker01 systemd[1]: Unit docker.service entered failed state.
Aug 09 10:30:44 qa-docker01 systemd[1]: docker.service failed.

No idea why this has happened randomly. I did extend the centos partition a few days ago and have seem some similar threads on the web about this but nothing specifically about this.

Any help would be greatly appreciated Really hope I don;t lose my data :frowning:

Cheers,
R.

2

I think it was this - https://github.com/docker/docker/issues/15721

Essentially the message is don’t use devicemapper, it can corrupt and lead to data loss. We’ve switched to overlay2 now.