Physical Disk Disappeared

    • OMV 3.x
    • Physical Disk Disappeared

      For the past few days my Time Machine Backup hasn't been working so I logged in to OMV on my raspberry pi today to try and figure out why. I noticed that the hard drive that I had previously labeled NAS3 is not in my list of physical disks anymore and as a result, the Apple Filing share now says

      TimeMachine [on cfb7420a-dcb0-4cef-bcc2-8d39784e0a09, TimeMachine/]

      When it used to say

      TimeMachine [on NAS3, TimeMachine/]

      What should I do?
    • This happens quite often where the usb to sata controller doesn't seem to be ready when the RPi is booting. Haven't really found a solution other than use something other than an RPi or don't reboot. mount -a should fix it once it is booted though.
      omv 4.1.14 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • fdisk -l outputs

      Source Code

      1. Disk /dev/ram0: 4 MiB, 4194304 bytes, 8192 sectors
      2. Units: sectors of 1 * 512 = 512 bytes
      3. Sector size (logical/physical): 512 bytes / 4096 bytes
      4. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      5. Disk /dev/ram1: 4 MiB, 4194304 bytes, 8192 sectors
      6. Units: sectors of 1 * 512 = 512 bytes
      7. Sector size (logical/physical): 512 bytes / 4096 bytes
      8. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      9. Disk /dev/ram2: 4 MiB, 4194304 bytes, 8192 sectors
      10. Units: sectors of 1 * 512 = 512 bytes
      11. Sector size (logical/physical): 512 bytes / 4096 bytes
      12. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      13. Disk /dev/ram3: 4 MiB, 4194304 bytes, 8192 sectors
      14. Units: sectors of 1 * 512 = 512 bytes
      15. Sector size (logical/physical): 512 bytes / 4096 bytes
      16. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      17. Disk /dev/ram4: 4 MiB, 4194304 bytes, 8192 sectors
      18. Units: sectors of 1 * 512 = 512 bytes
      19. Sector size (logical/physical): 512 bytes / 4096 bytes
      20. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      21. Disk /dev/ram5: 4 MiB, 4194304 bytes, 8192 sectors
      22. Units: sectors of 1 * 512 = 512 bytes
      23. Sector size (logical/physical): 512 bytes / 4096 bytes
      24. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      25. Disk /dev/ram6: 4 MiB, 4194304 bytes, 8192 sectors
      26. Units: sectors of 1 * 512 = 512 bytes
      27. Sector size (logical/physical): 512 bytes / 4096 bytes
      28. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      29. Disk /dev/ram7: 4 MiB, 4194304 bytes, 8192 sectors
      30. Units: sectors of 1 * 512 = 512 bytes
      31. Sector size (logical/physical): 512 bytes / 4096 bytes
      32. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      33. Disk /dev/ram8: 4 MiB, 4194304 bytes, 8192 sectors
      34. Units: sectors of 1 * 512 = 512 bytes
      35. Sector size (logical/physical): 512 bytes / 4096 bytes
      36. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      37. Disk /dev/ram9: 4 MiB, 4194304 bytes, 8192 sectors
      38. Units: sectors of 1 * 512 = 512 bytes
      39. Sector size (logical/physical): 512 bytes / 4096 bytes
      40. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      41. Disk /dev/ram10: 4 MiB, 4194304 bytes, 8192 sectors
      42. Units: sectors of 1 * 512 = 512 bytes
      43. Sector size (logical/physical): 512 bytes / 4096 bytes
      44. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      45. Disk /dev/ram11: 4 MiB, 4194304 bytes, 8192 sectors
      46. Units: sectors of 1 * 512 = 512 bytes
      47. Sector size (logical/physical): 512 bytes / 4096 bytes
      48. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      49. Disk /dev/ram12: 4 MiB, 4194304 bytes, 8192 sectors
      50. Units: sectors of 1 * 512 = 512 bytes
      51. Sector size (logical/physical): 512 bytes / 4096 bytes
      52. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      53. Disk /dev/ram13: 4 MiB, 4194304 bytes, 8192 sectors
      54. Units: sectors of 1 * 512 = 512 bytes
      55. Sector size (logical/physical): 512 bytes / 4096 bytes
      56. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      57. Disk /dev/ram14: 4 MiB, 4194304 bytes, 8192 sectors
      58. Units: sectors of 1 * 512 = 512 bytes
      59. Sector size (logical/physical): 512 bytes / 4096 bytes
      60. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      61. Disk /dev/ram15: 4 MiB, 4194304 bytes, 8192 sectors
      62. Units: sectors of 1 * 512 = 512 bytes
      63. Sector size (logical/physical): 512 bytes / 4096 bytes
      64. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      65. Disk /dev/mmcblk0: 14.4 GiB, 15476981760 bytes, 30228480 sectors
      66. Units: sectors of 1 * 512 = 512 bytes
      67. Sector size (logical/physical): 512 bytes / 512 bytes
      68. I/O size (minimum/optimal): 512 bytes / 512 bytes
      69. Disklabel type: dos
      70. Disk identifier: 0x000b5098
      71. Device Boot Start End Sectors Size Id Type
      72. /dev/mmcblk0p1 8192 122879 114688 56M c W95 FAT32 (LBA)
      73. /dev/mmcblk0p2 122880 7028735 6905856 3.3G 83 Linux
      74. /dev/mmcblk0p3 7028736 30228479 23199744 11.1G 83 Linux
      75. Disk /dev/sdb: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
      76. Units: sectors of 1 * 512 = 512 bytes
      77. Sector size (logical/physical): 512 bytes / 4096 bytes
      78. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      79. Disk /dev/sdc: 3.7 TiB, 4000786153472 bytes, 7814035456 sectors
      80. Units: sectors of 1 * 512 = 512 bytes
      81. Sector size (logical/physical): 512 bytes / 4096 bytes
      82. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      83. Disklabel type: gpt
      84. Disk identifier: 6BED9640-6DFA-4E42-A68A-7F514F44D6E8
      85. Device Start End Sectors Size Type
      86. /dev/sdc1 2048 7814035422 7814033375 3.7T Linux filesystem
      Display All

      and blkid outputs


      Source Code

      1. /dev/mmcblk0p1: SEC_TYPE="msdos" LABEL="boot" UUID="7D5C-A285" TYPE="vfat" PARTUUID="000b5098-01"
      2. /dev/mmcblk0p2: LABEL="omv" UUID="5d18be51-3217-4679-9c72-a54e0fc53d6b" TYPE="ext4" PARTUUID="000b5098-02"
      3. /dev/mmcblk0p3: UUID="fa36508a-b3c4-4499-b30a-711dd5994225" TYPE="ext4" PARTUUID="000b5098-03"
      4. /dev/sdc1: LABEL="NAS4" UUID="a40e1929-de25-454c-afd1-2f372f0b6d43" TYPE="ext4" PARTUUID="e58d0716-073a-48c7-9e3f-b07eff79c80f"
      5. /dev/mmcblk0: PTUUID="000b5098" PTTYPE="dos"
    • You still don't the NAS4 (/dev/sdc1) in the filesystems tab? Your other drive doesn't have a filesystem on it according to that output.
      omv 4.1.14 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • enano2054 wrote:

      t's just the NAS3 that's gone that I had my Time Machine backups and photo library backups on before.
      Not sure what happened but Linux (not just OMV) doesn't know there is a filesystem on the NAS3 disk.
      omv 4.1.14 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!