Rock64 not mount disk after reboot

    • OMV 4.x
    • Rock64 not mount disk after reboot

      Hi,
      I`m using Rock64 with OMV 4. I observe after reboot from time to time disk is not mounted, is not visible from GUI. I need to disconnect disk, make another reboot, after OMV is running connect disk again - than everything is fine until next reboot.
      Is it any solutions for this problem?
      I setup weekly automatic reboot.
    • macom wrote:

      If you turn on Rock64 and the HDD spins up, but the filesystem is not mounted, can you try mount -a from CLI?

      And what is the output of blkid?
      To be honest I didn`t try mount -a from CLI, only from web interface in scheduled tasks I add a new task with mount -a command.

      Output of blkid

      Source Code

      1. /dev/mmcblk1p6: SEC_TYPE="msdos" LABEL="boot" UUID="9EDC-9F0B" TYPE="vfat" PARTLABEL="boot" PARTUUID="fa7b8eca-ad12-475c-8dcf-1c6a59d813fd"
      2. /dev/mmcblk1p7: LABEL="linux-root" UUID="b8c23142-1f40-4ed3-b46f-9b0c786e5583" TYPE="ext4" PARTLABEL="root" PARTUUID="35eb320a-8fd2-47c0-be33-c4ffe655f753"
      3. /dev/sda1: LABEL="NAS" UUID="37ed4398-0796-40a6-b01f-a6b35a6111a5" TYPE="ext4" PARTUUID="4c50a175-dc8d-40ef-9d97-64ac98aae56e"
      4. /dev/mmcblk1: PTUUID="b2dd447e-398e-4430-b563-56a38fa1ed42" PTTYPE="gpt"
      5. /dev/mmcblk1p1: PARTLABEL="loader1" PARTUUID="4247738d-4f5e-45be-96f6-472a2f59a804"
      6. /dev/mmcblk1p2: PARTLABEL="reserved1" PARTUUID="152441f4-fbde-4742-a0cd-39bb1b4e8a71"
      7. /dev/mmcblk1p3: PARTLABEL="reserved2" PARTUUID="9ad6fe91-3f12-4920-baa1-fe2158e7d972"
      8. /dev/mmcblk1p4: PARTLABEL="loader2" PARTUUID="12a38b07-2d50-4808-9ccc-d9b03eeafca4"
      9. /dev/mmcblk1p5: PARTLABEL="atf" PARTUUID="b53a4fe9-d373-41d3-a18e-a6dc958b5da1"
      Images
      • openmedia.jpg

        55.11 kB, 1,307×751, viewed 21 times
    • maciekelga wrote:

      To be honest I didn`t try mount -a from CLI
      Maybe you can try someday. Based on the output of blkid I would think it will be mounted. If that is the case you probably need to find a way to execute the command with some delay. E.g. by using a simple script with sleep 5 and mount -a.

      EDIT:
      What should also work is to replace the command in scheduled jobs by sleep 5 && mount -a.
      You can check by running the command manually in the GUI of OMV and observe the output.
      Odroid HC2 - armbian - OMV4.x | Asrock Q1900DC-ITX - Intenso SSD 120GB - OMV4.x
      :!: Backup - Solutions to common problems - OMV setup videos - OMV4 Documentation - user guide :!:
    • macom wrote:

      If you turn on Rock64 and the HDD spins up, but the filesystem is not mounted, can you try mount -a from CLI?

      And what is the output of blkid?
      To be honest I didn`t try mount -a from CLI, only from web interface in scheduled tasks I add a new task with mount -a command.

      Output of blkid

      Source Code

      1. /dev/mmcblk1p6: SEC_TYPE="msdos" LABEL="boot" UUID="9EDC-9F0B" TYPE="vfat" PARTLABEL="boot" PARTUUID="fa7b8eca-ad12-475c-8dcf-1c6a59d813fd"
      2. /dev/mmcblk1p7: LABEL="linux-root" UUID="b8c23142-1f40-4ed3-b46f-9b0c786e5583" TYPE="ext4" PARTLABEL="root" PARTUUID="35eb320a-8fd2-47c0-be33-c4ffe655f753"
      3. /dev/sda1: LABEL="NAS" UUID="37ed4398-0796-40a6-b01f-a6b35a6111a5" TYPE="ext4" PARTUUID="4c50a175-dc8d-40ef-9d97-64ac98aae56e"
      4. /dev/mmcblk1: PTUUID="b2dd447e-398e-4430-b563-56a38fa1ed42" PTTYPE="gpt"
      5. /dev/mmcblk1p1: PARTLABEL="loader1" PARTUUID="4247738d-4f5e-45be-96f6-472a2f59a804"
      6. /dev/mmcblk1p2: PARTLABEL="reserved1" PARTUUID="152441f4-fbde-4742-a0cd-39bb1b4e8a71"
      7. /dev/mmcblk1p3: PARTLABEL="reserved2" PARTUUID="9ad6fe91-3f12-4920-baa1-fe2158e7d972"
      8. /dev/mmcblk1p4: PARTLABEL="loader2" PARTUUID="12a38b07-2d50-4808-9ccc-d9b03eeafca4"
      9. /dev/mmcblk1p5: PARTLABEL="atf" PARTUUID="b53a4fe9-d373-41d3-a18e-a6dc958b5da1"
      -----edit-----
      Ok, I think I solved a problem modyfing a little bit a hardware site.
      I changed a SATA USB adapter. Previously HDD was powered up from USB 3.0, now adapter have additional USB cable to power up HDD. So one cable is connected to 3.0 as communication, second to 2.0 as power supply.
      I did few times reboot and since now is ok, I will observe it.