After update to 4.x "A start job is running for..."

    • OMV 4.x
    • Resolved

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • After update to 4.x "A start job is running for..."

      Hi,

      yesterday I've updated to v4... First it looked pretty good. The first reboot took a while, so I wondered and walked to the server: "[1 of 2] A start job is running for..." I asked Google and searched the forum, no solution for my problem :(

      Please someone can help me? Sorry for my English :(




      Source Code

      1. root@omv:~# lsblk -f
      2. NAME FSTYPE LABEL UUID MOUNTPOINT
      3. sda
      4. ├─sda1 ext4 b4677258-c0a1-4c0e-8583-1015f3759a65 /
      5. ├─sda2
      6. └─sda5 swap 5956afcb-2480-49cb-a50d-bcb46835f149 [SWAP]
      7. sdb linux_r omv:RAID10 596d72f7-24d9-909d-c4f8-ffeae7558f0e
      8. └─md127 ext4 RAID10 77e26cdb-fa41-4538-a312-eab604ccab96 /srv/dev-disk-by
      9. sdc linux_r omv:RAID10 596d72f7-24d9-909d-c4f8-ffeae7558f0e
      10. └─md127 ext4 RAID10 77e26cdb-fa41-4538-a312-eab604ccab96 /srv/dev-disk-by
      11. sdd linux_r omv:RAID10 596d72f7-24d9-909d-c4f8-ffeae7558f0e
      12. └─md127 ext4 RAID10 77e26cdb-fa41-4538-a312-eab604ccab96 /srv/dev-disk-by
      13. sde linux_r omv:RAID10 596d72f7-24d9-909d-c4f8-ffeae7558f0e
      14. └─md127 ext4 RAID10 77e26cdb-fa41-4538-a312-eab604ccab96 /srv/dev-disk-by
      Display All


      Source Code

      1. root@omv:~# cat /etc/fstab
      2. # /etc/fstab: static file system information.
      3. #
      4. # Use 'blkid' to print the universally unique identifier for a
      5. # device; this may be used with UUID= as a more robust way to name devices
      6. # that works even if disks are added and removed. See fstab(5).
      7. #
      8. # <file system> <mount point> <type> <options> <dump> <pass>
      9. # / was on /dev/sdb1 during installation
      10. UUID=b4677258-c0a1-4c0e-8583-1015f3759a65 / ext4 errors=remount -ro 0 1
      11. # swap was on /dev/sdb5 during installation
      12. UUID=5956afcb-2480-49cb-a50d-bcb46835f149 none swap sw 0 0
      13. tmpfs /tmp tmpfs defaults 0 0
      14. # >>> [openmediavault]
      15. /dev/disk/by-id/md-name-omv:RAID10 /srv/dev-disk-by-id-md-name-omv-RAID10 ext4 d efaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jq fmt=vfsv0,acl 0 2
      16. # <<< [openmediavault]
      Display All

      Best regards
      Lukas

      The post was edited 2 times, last by Beo666 ().

    • Beo666 wrote:

      Every time I reboot?
      Do you let it finish and it still happens every time you reboot?
      omv 4.1.8.2 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.9
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please read this before posting a question.
      Please don't PM for support... Too many PMs!
    • Hard to say. I would look through the logs in the omv web interface. If you can't find anything there, look in /var/log/
      omv 4.1.8.2 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.9
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please read this before posting a question.
      Please don't PM for support... Too many PMs!
    • Between "Okt 16 19:32:12 omv systemd[1]: Mounted /tmp." and the next event there are exactly the 90s.


      Source Code

      1. Okt 16 19:32:12 omv systemd[1]: Mounted /tmp.
      2. Okt 16 19:33:41 omv systemd[1]: dev-disk-by\x2duuid-5956afcb\x2d2480\x2d49cb\x2da50d\x2dbcb46835f149.device: Job dev-disk-by\x2duuid-5956afcb\x2d2480\x2d49cb\x2da50d\x2dbcb46835f149.device/start timed out.
      3. Okt 16 19:33:41 omv systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-5956afcb\x2d2480\x2d49cb\x2da50d\x2dbcb46835f149.device.
      4. Okt 16 19:33:41 omv systemd[1]: Dependency failed for /dev/disk/by-uuid/5956afcb-2480-49cb-a50d-bcb46835f149.
      5. Okt 16 19:33:41 omv systemd[1]: Dependency failed for Swap.
      6. Okt 16 19:33:41 omv systemd[1]: swap.target: Job swap.target/start failed with result 'dependency'.
      7. Okt 16 19:33:41 omv systemd[1]: dev-disk-by\x2duuid-5956afcb\x2d2480\x2d49cb\x2da50d\x2dbcb46835f149.swap: Job dev-disk-by\x2duuid-5956afcb\x2d2480\x2d49cb\x2da50d\x2dbcb46835f149.swap/start failed with result 'dependency'.
      8. Okt 16 19:33:41 omv systemd[1]: dev-disk-by\x2duuid-5956afcb\x2d2480\x2d49cb\x2da50d\x2dbcb46835f149.device: Job dev-disk-by\x2duuid-5956afcb\x2d2480\x2d49cb\x2da50d\x2dbcb46835f149.device/start failed with result 'timeout'.
      9. Okt 16 19:33:41 omv systemd[1]: dev-disk-by\x2did-md\x2dname\x2domv:RAID10.device: Job dev-disk-by\x2did-md\x2dname\x2domv:RAID10.device/start timed out.
      10. Okt 16 19:33:41 omv systemd[1]: Timed out waiting for device dev-disk-by\x2did-md\x2dname\x2domv:RAID10.device.
      11. Okt 16 19:33:41 omv systemd[1]: Dependency failed for /srv/dev-disk-by-id-md-name-omv-RAID10.
      12. Okt 16 19:33:41 omv systemd[1]: srv-dev\x2ddisk\x2dby\x2did\x2dmd\x2dname\x2domv\x2dRAID10.mount: Job srv-dev\x2ddisk\x2dby\x2did\x2dmd\x2dname\x2domv\x2dRAID10.mount/start failed with result 'dependency'.
      13. Okt 16 19:33:41 omv systemd[1]: Dependency failed for File System Check on /dev/disk/by-id/md-name-omv:RAID10.
      14. Okt 16 19:33:41 omv systemd[1]: systemd-fsck@dev-disk-by\x2did-md\x2dname\x2domv:RAID10.service: Job systemd-fsck@dev-disk-by\x2did-md\x2dname\x2domv:RAID10.service/start failed with result 'dependency'.
      15. Okt 16 19:33:41 omv systemd[1]: dev-disk-by\x2did-md\x2dname\x2domv:RAID10.device: Job dev-disk-by\x2did-md\x2dname\x2domv:RAID10.device/start failed with result 'timeout'.
      16. Okt 16 19:33:41 omv systemd[1]: Starting File System Quota Check...
      Display All
    • Just looking at the logs looks like swap device and md device gets activated much after local-fs-pre target. How long does it wait there until is finishes booting?

      If you comment the swap fstab line and reboot does it get stuck ?
      New wiki
      chat support at #openmediavault@freenode IRC | Spanish & English | GMT+10
      telegram.me/openmediavault broadcast channel
      openmediavault discord server
    • No. I saw this a couple of times in testing vm’s but I couldn’t solve it.
      Now looking at the logs seems like the disk get mounted at the end, if that’s the case you can try to add a directive so the timeout is shorter maybe 10 seconds.

      In fstab entries that are causing problems add



      x-systemd.device-timeout=10
      New wiki
      chat support at #openmediavault@freenode IRC | Spanish & English | GMT+10
      telegram.me/openmediavault broadcast channel
      openmediavault discord server
    • After update to 4.x "A start job is running for..."

      subzero79 wrote:

      No. I saw this a couple of times in testing vm’s but I couldn’t solve it.


      I also had this issue while passing my sas controller to a vm under proxmox:

      forum.proxmox.com/threads/prox…h-lsi-3008-mpt3sas.29577/

      The solution I described there in the proxmox forum, but I think it won‘t help here.

      Greetings Hoppel
      ---------------------------------------------------------------------------------------------------------------
      frontend software - android tv | libreelec | win10 | kodi krypton
      frontend hardware - nvidia shield tv | odroid c2 | yamaha rx-a1020 | quadral chromium style 5.1 | samsung le40-a789r2 | harmony smart control
      -------------------------------------------
      backend software - debian | kernel 4.4 lts | proxmox | openmediavault | zfs raid-z2 | docker | emby | vdr | vnsi | fhem
      backend hardware - supermicro x11ssh-ctf | xeon E3-1240L-v5 | 64gb ecc | 8x4tb wd red | digital devices max s8
      ---------------------------------------------------------------------------------------------------------------------------------------