Mount local disk failed: Where= setting doesn't match unit name

[sieben tupel]

Hi,

i have the following problem:

When i try to mount a secondary disk via the cloud-config file i get the following error:

Failed to apply cloud-config: Unit secondary-disk-docker.mount failed to load: Invalid argument.

Systemctl status tells me

secondary-disk-docker.mount's Where= setting doesn't match unit name. Refusing.

The disk seems to be formatted correctly, manualy mounting the disk works just fine.
The maschine i'm running coreos is a dedicated server and the disk is attached directly over sata without any hardware raid controler.
This is the entry in my cloud-config file:

# mount secondary disk for docker storage
    - name: secondary-disk-docker.mount
      command: start
      content: |
        [Unit]
        Description=Mount secondary disk for docker data
        Before=docker.service
        [Mount]
        What=/dev/sdb1
        Where=/var/lib/docker
        Type=ext4
        TimeoutSec=10

I found this entry that seems to address the same problem. Unfortunately without any solution.

[Stefan Groß]

Hello, this is a systemd-thing, as the error says:

secondary-disk-docker.mount's Where= setting doesn't match unit name. Refusing.

so you'll have to change the units name from

 

    - name: secondary-disk-docker.mount

to: "var-lib-docker.mount"; that is to match the path where you want to mount the filesystem:

        Where=/var/lib/docker

Look here for further info:

http://www.freedesktop.org/software/systemd/man/systemd.mount.html

But i'm not sure if it's a good idea to mount an ext4-fs to /var/lib/docker -- see my post: "mount /var/lib/docker/volumes ..." on this forum.

__

s.

[Alex Crawford]

On 02/28, sieben tupel wrote:
> Hi,
>
> i have the following problem:
>
> When i try to mount a secondary disk via the cloud-config file i get the
> following error:
>

> *Failed to apply cloud-config: Unit secondary-disk-docker.mount failed to
> load: Invalid argument.*
>
> Systemctl status tells me
>
> *secondary-disk-docker.mount's Where= setting doesn't match unit name.
> Refusing.*

>
> The disk seems to be formatted correctly, manualy mounting the disk works
> just fine.
> The maschine i'm running coreos is a dedicated server and the disk is
> attached directly over sata without any hardware raid controler.
> This is the entry in my cloud-config file:
>
>
>
>
>
>
>
>
>
>
>
>

> *# mount secondary disk for docker storage - name:

> secondary-disk-docker.mount command: start content: |
> [Unit] Description=Mount secondary disk for docker data
> Before=docker.service [Mount] What=/dev/sdb1

> Where=/var/lib/docker Type=ext4 TimeoutSec=10*
>
> I found this <https://github.com/coreos/etcd/issues/977> entry that seems

> to address the same problem. Unfortunately without any solution.
>

> --
> You received this message because you are subscribed to the Google Groups "CoreOS User" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to coreos-user...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

Your mount unit needs to be named "dev-sdb1.mount". From [1], "Mount
units must be named after the mount point directories they control.
Example: the mount point /home/lennart must be configured in a unit file
home-lennart.mount."

[1] http://www.freedesktop.org/software/systemd/man/systemd.mount.html

-Alex

[sieben tupel]

thx. now it is working as expected.

cheers mo

[Alex Crawford]

Whoops, that should be "var-lib-docker.mount" (as Stefan pointed out).

-Alex