Skip to main content
Unix & Linux

Return to Answer

Updated redirecting URL to stop it going stale
Source Link
edit approved Feb 10 at 18:46
AJM
edit approved Feb 10 at 18:46
AJM
  • 295
  • 1
  • 10

I had the similar problem but didn't find any suitable solution. I only can give some workarounds:

Create unit files for each volume you want to mount. E.g.

[Unit] Description=Start home [Service] Type=oneshot RemainAfterExit=yes ExecStart=/bin/mount /dev/mapper/vg-home ExecStop=/bin/umount /dev/mapper/vg-home [Install] WantedBy=local-fs.target

Or add `x-systemd.device-timeout` option to your fstab mount rules. E.g. ``` UUID=d276a0d4-c95f-4792-a222-6d1451899de2 /home ext4 noatime,x-systemd.device-timeout=60s,errors=remount-ro 0 1 ``` This will give systemd some time to do the work.
Official workaround from OpenSuse [Devices time out at boot time but appear later][2]

EDIT:

Also you can play around with: ``` [Install]

Or add x-systemd.device-timeout option to your fstab mount rules. E.g.

WantedBy=dev-mapper-vg\x2dhome.device
UUID=d276a0d4-c95f-4792-a222-6d1451899de2 /home ext4 noatime,x-systemd.device-timeout=60s,errors=remount-ro 0 1
```

This will give systemd some time to do the work.

For trigger unit file.

Official workaround from OpenSUSE: Devices time out at boot time but appear later

EDIT:

Also you can play around with:


 
[Install] WantedBy=dev-mapper-vg\x2dhome.device
To get escaped path use [systemd-escape][3]

For trigger unit file.
To get escaped path use systemd-escape

I had the similar problem but didn't find any suitable solution. I only can give some workarounds:

Create unit files for each volume you want to mount. E.g.

[Unit] Description=Start home [Service] Type=oneshot RemainAfterExit=yes ExecStart=/bin/mount /dev/mapper/vg-home ExecStop=/bin/umount /dev/mapper/vg-home [Install] WantedBy=local-fs.target

Or add `x-systemd.device-timeout` option to your fstab mount rules. E.g. ``` UUID=d276a0d4-c95f-4792-a222-6d1451899de2 /home ext4 noatime,x-systemd.device-timeout=60s,errors=remount-ro 0 1 ``` This will give systemd some time to do the work.
Official workaround from OpenSuse [Devices time out at boot time but appear later][2]

EDIT:

Also you can play around with: ``` [Install] WantedBy=dev-mapper-vg\x2dhome.device ``` For trigger unit file.
  To get escaped path use [systemd-escape][3]

I had the similar problem but didn't find any suitable solution. I only can give some workarounds:

Create unit files for each volume you want to mount. E.g.

[Unit] Description=Start home [Service] Type=oneshot RemainAfterExit=yes ExecStart=/bin/mount /dev/mapper/vg-home ExecStop=/bin/umount /dev/mapper/vg-home [Install] WantedBy=local-fs.target

Or add x-systemd.device-timeout option to your fstab mount rules. E.g.

UUID=d276a0d4-c95f-4792-a222-6d1451899de2 /home ext4 noatime,x-systemd.device-timeout=60s,errors=remount-ro 0 1

This will give systemd some time to do the work.

Official workaround from OpenSUSE: Devices time out at boot time but appear later

EDIT:

Also you can play around with:

[Install] WantedBy=dev-mapper-vg\x2dhome.device

For trigger unit file.
To get escaped path use systemd-escape

deleted 182 characters in body
Source Link
dpleshakov
dpleshakov
  • 56
  • 4

I had the similar problem but didn't find any suitable solution. I only can give some workarounds:

Create unit files for each volume you want to mount. E.g.

[Unit] Description=Start home [Service] Type=oneshot RemainAfterExit=yes ExecStart=/bin/mount /dev/mapper/vg-home ExecStop=/bin/umount /dev/mapper/vg-home [Install] WantedBy=local-fs.target

Here we will start service after all system service (yes i simplify a little). More here Systemd service - what is `multi-user.target`


Or add `x-systemd.device-timeout` option to your fstab mount rules. E.g. ``` UUID=d276a0d4-c95f-4792-a222-6d1451899de2 /home ext4 noatime,x-systemd.device-timeout=60s,errors=remount-ro 0 1 ``` This will give systemd some time to do the work.
Official workaround from OpenSuse [Devices time out at boot time but appear later][2]

EDIT:

Also you can play around with: ``` [Path][Install] PathExists=/dev/WantedBy=dev-mapper/vg-homevg\x2dhome.device ``` For trigger unit file.
To get escaped path use [systemd-escape][3]

I had the similar problem but didn't find any suitable solution. I only can give some workarounds:

Create unit files for each volume you want to mount. E.g.

[Unit] Description=Start home [Service] Type=oneshot RemainAfterExit=yes ExecStart=/bin/mount /dev/mapper/vg-home ExecStop=/bin/umount /dev/mapper/vg-home [Install] WantedBy=local-fs.target

Here we will start service after all system service (yes i simplify a little). More here Systemd service - what is `multi-user.target`


Or add `x-systemd.device-timeout` option to your fstab mount rules. E.g. ``` UUID=d276a0d4-c95f-4792-a222-6d1451899de2 /home ext4 noatime,x-systemd.device-timeout=60s,errors=remount-ro 0 1 ``` This will give systemd some time to do the work.
Official workaround from OpenSuse [Devices time out at boot time but appear later][2]

EDIT:

Also you can play around with: ``` [Path] PathExists=/dev/mapper/vg-home ``` For trigger unit file.

I had the similar problem but didn't find any suitable solution. I only can give some workarounds:

Create unit files for each volume you want to mount. E.g.

[Unit] Description=Start home [Service] Type=oneshot RemainAfterExit=yes ExecStart=/bin/mount /dev/mapper/vg-home ExecStop=/bin/umount /dev/mapper/vg-home [Install] WantedBy=local-fs.target

Or add `x-systemd.device-timeout` option to your fstab mount rules. E.g. ``` UUID=d276a0d4-c95f-4792-a222-6d1451899de2 /home ext4 noatime,x-systemd.device-timeout=60s,errors=remount-ro 0 1 ``` This will give systemd some time to do the work.
Official workaround from OpenSuse [Devices time out at boot time but appear later][2]

EDIT:

Also you can play around with: ``` [Install] WantedBy=dev-mapper-vg\x2dhome.device ``` For trigger unit file.
To get escaped path use [systemd-escape][3]
added 137 characters in body
Source Link
dpleshakov
dpleshakov
  • 56
  • 4

I had the similar problem but didn't find any suitable solution. I only can give some workarounds:

Create unit files for each volume you want to mount. E.g.

[Unit] Description=Start home [Service] Type=oneshot RemainAfterExit=yes ExecStart=/bin/mount /dev/mapper/vg-home ExecStop=/bin/umount /dev/mapper/vg-home [Install] WantedBy=multiWantedBy=local-userfs.target

Here we will start service after all system service (yes i simplify a little). More here Systemd service - what is `multi-user.target`


Or add `x-systemd.device-timeout` option to your fstab mount rules. E.g. ``` UUID=d276a0d4-c95f-4792-a222-6d1451899de2 /home ext4 noatime,x-systemd.device-timeout=60s,errors=remount-ro 0 1 ``` This will give systemd some time to do the work.
Official workaround from OpenSuse [Devices time out at boot time but appear later][2]

EDIT:

Also you can play around with: ``` [Path] PathExists=/dev/mapper/vg-home ``` For trigger unit file.

I had the similar problem but didn't find any suitable solution. I only can give some workarounds:

Create unit files for each volume you want to mount. E.g.

[Unit] Description=Start home [Service] Type=oneshot RemainAfterExit=yes ExecStart=/bin/mount /dev/mapper/vg-home ExecStop=/bin/umount /dev/mapper/vg-home [Install] WantedBy=multi-user.target

Here we will start service after all system service (yes i simplify a little). More here Systemd service - what is `multi-user.target`


Or add `x-systemd.device-timeout` option to your fstab mount rules. E.g. ``` UUID=d276a0d4-c95f-4792-a222-6d1451899de2 /home ext4 noatime,x-systemd.device-timeout=60s,errors=remount-ro 0 1 ``` This will give systemd some time to do the work.
Official workaround from OpenSuse [Devices time out at boot time but appear later][2]

I had the similar problem but didn't find any suitable solution. I only can give some workarounds:

Create unit files for each volume you want to mount. E.g.

[Unit] Description=Start home [Service] Type=oneshot RemainAfterExit=yes ExecStart=/bin/mount /dev/mapper/vg-home ExecStop=/bin/umount /dev/mapper/vg-home [Install] WantedBy=local-fs.target

Here we will start service after all system service (yes i simplify a little). More here Systemd service - what is `multi-user.target`


Or add `x-systemd.device-timeout` option to your fstab mount rules. E.g. ``` UUID=d276a0d4-c95f-4792-a222-6d1451899de2 /home ext4 noatime,x-systemd.device-timeout=60s,errors=remount-ro 0 1 ``` This will give systemd some time to do the work.
Official workaround from OpenSuse [Devices time out at boot time but appear later][2]

EDIT:

Also you can play around with: ``` [Path] PathExists=/dev/mapper/vg-home ``` For trigger unit file.
Source Link
dpleshakov
dpleshakov
  • 56
  • 4