Jbod is missing

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

    • Jbod is missing

      Hello everybody,

      this is my first post and i hope i do everything right :-).

      I had until recently the following JBod composite consisting of:

      - 7TB hard drive (/dev/sde)
      - 4TB hard drive (/dev/sdb)
      - 4TB hard drive (/dev/sdc)
      - 3TB hard drive (/dev/sda)

      The OS is on a usd-ssd-drive. Everything was formated with ext4.

      In the new year I wanted to extend this to a hard drive. Something went wrong. Now I no longer see my JBod network. My attempts to read data from the partitions with gparted and other rescue tools unfortunately failed.

      Gparted says that "The gptable is corrupt. The backup is ok."

      What can I do to save the jbod - or do I need to restore the backup?

      I have already executed the following commands and I add the result.


      Source Code

      1. Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
      2. unused devices: <none>

      Source Code

      1. Disk /dev/sdb: 3,7 TiB, 4000787030016 bytes, 7814037168 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. Disklabel type: gpt
      6. Disk identifier: C9745195-6062-4F94-849A-BAC949E1D309
      7. Device Start End Sectors Size Type
      8. /dev/sdb1 34 2081 2048 1M Microsoft LDM metadata
      9. /dev/sdb2 2082 262177 260096 127M Microsoft reserved
      10. /dev/sdb3 262178 7814037134 7813774957 3,7T Microsoft LDM data
      11. Partition 1 does not start on physical sector boundary.
      12. Partition 2 does not start on physical sector boundary.
      13. Partition 3 does not start on physical sector boundary.
      14. Disk /dev/sdc: 3,7 TiB, 4000787030016 bytes, 7814037168 sectors
      15. Units: sectors of 1 * 512 = 512 bytes
      16. Sector size (logical/physical): 512 bytes / 4096 bytes
      17. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      18. Disklabel type: gpt
      19. Disk identifier: B67521C5-FA4B-41CE-AB40-6D5DB5CD5C5E
      20. Device Start End Sectors Size Type
      21. /dev/sdc1 34 2081 2048 1M Microsoft LDM metadata
      22. /dev/sdc2 2082 262177 260096 127M Microsoft reserved
      23. /dev/sdc3 262178 7814037134 7813774957 3,7T Microsoft LDM data
      24. Partition 1 does not start on physical sector boundary.
      25. Partition 2 does not start on physical sector boundary.
      26. Partition 3 does not start on physical sector boundary.
      27. The primary GPT table is corrupt, but the backup appears OK, so that will be used.
      28. Disk /dev/sdd: 7,3 TiB, 8001563222016 bytes, 15628053168 sectors
      29. Units: sectors of 1 * 512 = 512 bytes
      30. Sector size (logical/physical): 512 bytes / 4096 bytes
      31. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      32. Disklabel type: gpt
      33. Disk identifier: EB53941D-D4A1-4D61-A1D2-4266D4687302
      34. Device Start End Sectors Size Type
      35. /dev/sdd1 34 2081 2048 1M Microsoft LDM metadata
      36. /dev/sdd2 2082 262177 260096 127M Microsoft reserved
      37. /dev/sdd3 262178 15628053134 15627790957 7,3T Microsoft LDM data
      38. Partition 1 does not start on physical sector boundary.
      39. Partition 2 does not start on physical sector boundary.
      40. Partition 3 does not start on physical sector boundary.
      41. Disk /dev/sde: 7,3 TiB, 8001563222016 bytes, 15628053168 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. Disklabel type: gpt
      46. Disk identifier: E8011AD4-A4B4-F241-8123-C7CF860E75A8
      47. Device Start End Sectors Size Type
      48. /dev/sde1 2048 15628053127 15628051080 7,3T Microsoft basic data
      49. Disk /dev/sda: 2,7 TiB, 3000592982016 bytes, 5860533168 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. Disklabel type: gpt
      54. Disk identifier: BFCCF720-5B6F-4F85-8FD5-8C927067A265
      55. Device Start End Sectors Size Type
      56. /dev/sda1 34 2081 2048 1M Microsoft LDM metadata
      57. /dev/sda2 2082 262177 260096 127M Linux RAID
      58. /dev/sda3 262178 5860533134 5860270957 2,7T Linux RAID
      59. Partition 1 does not start on physical sector boundary.
      60. Partition 2 does not start on physical sector boundary.
      61. Partition 3 does not start on physical sector boundary.
      62. Disk /dev/sdf: 3,7 GiB, 3932160000 bytes, 7680000 sectors
      63. Units: sectors of 1 * 512 = 512 bytes
      64. Sector size (logical/physical): 512 bytes / 512 bytes
      65. I/O size (minimum/optimal): 512 bytes / 512 bytes
      66. Disklabel type: dos
      67. Disk identifier: 0x40a087e5
      68. Device Boot Start End Sectors Size Id Type
      69. /dev/sdf1 * 0 1376255 1376256 672M 0 Empty
      70. /dev/sdf2 580 8771 8192 4M ef EFI (FAT-12/16/32)
      71. Disk /dev/sdg: 29,8 GiB, 32017047552 bytes, 62533296 sectors
      72. Units: sectors of 1 * 512 = 512 bytes
      73. Sector size (logical/physical): 512 bytes / 512 bytes
      74. I/O size (minimum/optimal): 512 bytes / 512 bytes
      75. Disklabel type: dos
      76. Disk identifier: 0xa5f63862
      77. Device Boot Start End Sectors Size Id Type
      78. /dev/sdg1 * 2048 59895807 59893760 28,6G 83 Linux
      79. /dev/sdg2 59897854 62531583 2633730 1,3G 5 Extended
      80. /dev/sdg5 59897856 62531583 2633728 1,3G 82 Linux swap / Solaris
      Display All


      I hope you can help me! Maybe @ryecoaaron

      schlaubi
    • There are a lot of problems with what you have done:
      - You didn't wipe the drives. That is why there still partitions on those drives.
      - You created a jbod that has no redundancy. Lots of better ways to create a pool of disks.
      - You didn't create the array with OMV
      - I can't tell how the array was assembled.
      omv 4.1.17 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!
    • _schlaubi_ wrote:

      Do you still see a way to save something, or should I rebuild everything and import the backup?
      I would wipe the disks and not use raid. Format each disk ext4 and pool them with the unionfilesystems plugin. Then import your backup.

      With that setup, if a disk fails, you only lose (or have to restore from backup) the info on that disk
      omv 4.1.17 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!