Boot drive mirror satadom

    • OMV 4.x

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

    • Boot drive mirror satadom

      New

      Hey guys,

      I just received my 2x SATADOM 32GB drives. (I was planning on using FreeNAS)

      Is there a way I can use these for OMV? And mirror the drives incase ones dies we can just reboot and run off the backup?

      Lastly, I have 128gb ram, so I'll need to remove a bunch of ram in order to use the OMV installer, will there be any repercussions if I remove ram down to 16gb, install OMV, configure the mirror (if possible), and then reinstall the ram back to 128gb? Would this have any lasting negative effects?
    • New

      The BIOS boot order should allow you to pick which drive you want to boot from, and switch if needed.
      You can clone drives with dd, using something like; dd if=/dev/sda of=/dev/sdb bs=32M
      I'm not sure of the effect of cloning an active (on-line) boot drive.

      Cloning might require an off line process, like clonezilla, which can be installed using OMV-Extras. Clonezilla, as it is installed by OMV-Extra's, is accessible by SSH so an off-line cloning process can still be accomplished on a headless server.

      Command lines like the above can be added to scheduled tasks and run automatically, or set inactive and run manually using the run button.
      (Manual is probably best in this case.)
      Based on what I read regrading SATADOM drives, you probably should use the flashmemory plugin.
      _____________________________________

      Regarding the RAM question, tagging @ryecoaaron . He knows more about the OMV/Debian installer, X86 hardware, and potential ram limitations than I do.

      The post was edited 1 time, last by crashtest: edit ().

    • New

      Thanks @crashtest, I'll wait for @ryecoaaron for a reply about RAM limitations.

      Lastly the SATADoms I have are the SuperMicro SUPERDoms. They 'seem' to be more like little SATA devices more than glorified USB.
      I am happy to stand corrected, and happy to install the flashmemory plugin just didnt think it would be needed.

      If I did DD or clonezilla would it still clone the boot so it would make a 100% like for like and be able to boot from the spare device?
    • New

      savellm wrote:

      I'll wait for @ryecoaaron for a reply about RAM limitations.
      He'll most probably explain what he already explained here for example: Switching to OMV from unRaid

      As for your SuperMicro flash modules... they're flash after all and will wear out. Those SUPERDoms we use seem to provide a 'wear out indicator' SMART attribute but I've neither an idea whether it's the right one nor how to interpret it (that's the great thing about 'good' SSDs: they tell you when they are almost worn out so you can replace them prior to a mess, but you need to be able to interpret the respective SMART attributes for this to work):

      Source Code

      1. root@datengrab:~# smartctl -q noserial -x /dev/sdq
      2. smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-51-generic] (local build)
      3. Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
      4. === START OF INFORMATION SECTION ===
      5. Device Model: SuperMicro SSD
      6. Firmware Version: SOB20R
      7. User Capacity: 31,675,383,808 bytes [31.6 GB]
      8. Sector Size: 512 bytes logical/physical
      9. Rotation Rate: Solid State Device
      10. Device is: Not in smartctl database [for details use: -P showall]
      11. ATA Version is: ACS-2 (minor revision not indicated)
      12. SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
      13. Local Time is: Wed Jun 12 11:53:18 2019 CEST
      14. SMART support is: Available - device has SMART capability.
      15. SMART support is: Enabled
      16. AAM feature is: Disabled
      17. APM feature is: Unavailable
      18. Rd look-ahead is: Enabled
      19. Write cache is: Enabled
      20. ATA Security is: Disabled, NOT FROZEN [SEC1]
      21. Wt Cache Reorder: Unavailable
      22. === START OF READ SMART DATA SECTION ===
      23. SMART overall-health self-assessment test result: PASSED
      24. General SMART Values:
      25. Offline data collection status: (0x02) Offline data collection activity
      26. was completed without error.
      27. Auto Offline Data Collection: Disabled.
      28. Self-test execution status: ( 0) The previous self-test routine completed
      29. without error or no self-test has ever
      30. been run.
      31. Total time to complete Offline
      32. data collection: ( 0) seconds.
      33. Offline data collection
      34. capabilities: (0x71) SMART execute Offline immediate.
      35. No Auto Offline data collection support.
      36. Suspend Offline collection upon new
      37. command.
      38. No Offline surface scan supported.
      39. Self-test supported.
      40. Conveyance Self-test supported.
      41. Selective Self-test supported.
      42. SMART capabilities: (0x0002) Does not save SMART data before
      43. entering power-saving mode.
      44. Supports SMART auto save timer.
      45. Error logging capability: (0x01) Error logging supported.
      46. General Purpose Logging supported.
      47. Short self-test routine
      48. recommended polling time: ( 2) minutes.
      49. Extended self-test routine
      50. recommended polling time: ( 10) minutes.
      51. Conveyance self-test routine
      52. recommended polling time: ( 2) minutes.
      53. SMART Attributes Data Structure revision number: 1
      54. Vendor Specific SMART Attributes with Thresholds:
      55. ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
      56. 1 Raw_Read_Error_Rate ------ 100 100 000 - 0
      57. 5 Reallocated_Sector_Ct ------ 100 100 000 - 0
      58. 9 Power_On_Hours ------ 100 100 000 - 9444
      59. 12 Power_Cycle_Count ------ 100 100 000 - 35
      60. 15 Unknown_Attribute ------ 100 100 000 - 61865984
      61. 160 Unknown_Attribute ------ 100 100 000 - 0
      62. 161 Unknown_Attribute ------ 100 100 000 - 159
      63. 163 Unknown_Attribute ------ 100 100 000 - 14
      64. 164 Unknown_Attribute ------ 100 100 000 - 104693
      65. 165 Unknown_Attribute ------ 100 100 000 - 134
      66. 166 Unknown_Attribute ------ 100 100 000 - 3
      67. 167 Unknown_Attribute ------ 100 100 000 - 50
      68. 168 Unknown_Attribute ------ 100 100 000 - 3000
      69. 172 Unknown_Attribute ------ 100 100 000 - 0
      70. 175 Program_Fail_Count_Chip ------ 100 100 000 - 14
      71. 177 Wear_Leveling_Count ------ 100 100 000 - 14
      72. 181 Program_Fail_Cnt_Total ------ 100 100 000 - 0
      73. 187 Reported_Uncorrect ------ 100 100 000 - 0
      74. 192 Power-Off_Retract_Count ------ 100 100 000 - 0
      75. 194 Temperature_Celsius ------ 100 100 000 - 39 (Min/Max 15/52)
      76. 195 Hardware_ECC_Recovered ------ 100 100 000 - 264
      77. 197 Current_Pending_Sector ------ 100 100 000 - 0
      78. 198 Offline_Uncorrectable ------ 100 100 000 - 0
      79. 199 UDMA_CRC_Error_Count ------ 100 100 000 - 0
      80. 231 Temperature_Celsius ------ 100 100 000 - 100
      81. 232 Available_Reservd_Space ------ 100 100 000 - 99
      82. 233 Media_Wearout_Indicator ------ 100 100 000 - 1635
      83. 241 Total_LBAs_Written ------ 100 100 000 - 1320
      84. 242 Total_LBAs_Read ------ 100 100 000 - 190
      85. ||||||_ K auto-keep
      86. |||||__ C event count
      87. ||||___ R error rate
      88. |||____ S speed/performance
      89. ||_____ O updated online
      90. |______ P prefailure warning
      91. General Purpose Log Directory Version 1
      92. SMART Log Directory Version 1 [multi-sector log support]
      93. Address Access R/W Size Description
      94. 0x00 GPL,SL R/O 1 Log Directory
      95. 0x01 GPL,SL R/O 1 Summary SMART error log
      96. 0x02 GPL,SL R/O 1 Comprehensive SMART error log
      97. 0x03 GPL,SL R/O 1 Ext. Comprehensive SMART error log
      98. 0x04 GPL,SL R/O 8 Device Statistics log
      99. 0x06 GPL,SL R/O 1 SMART self-test log
      100. 0x07 GPL,SL R/O 1 Extended self-test log
      101. 0x09 GPL,SL R/W 1 Selective self-test log
      102. 0x10 GPL,SL R/O 1 SATA NCQ Queued Error log
      103. 0x30 GPL,SL R/O 9 IDENTIFY DEVICE data log
      104. 0x80-0x9f GPL,SL R/W 16 Host vendor specific log
      105. SMART Extended Comprehensive Error Log Version: 1 (1 sectors)
      106. No Errors Logged
      107. SMART Extended Self-test Log Version: 1 (1 sectors)
      108. No self-tests have been logged. [To run self-tests, use: smartctl -t]
      109. SMART Selective self-test log data structure revision number 1
      110. SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
      111. 1 0 0 Not_testing
      112. 2 0 0 Not_testing
      113. 3 0 0 Not_testing
      114. 4 0 0 Not_testing
      115. 5 0 0 Not_testing
      116. Selective self-test flags (0x0):
      117. After scanning selected spans, do NOT read-scan remainder of disk.
      118. If Selective self-test is pending on power-up, resume after 0 minute delay.
      119. SCT Commands not supported
      120. Device Statistics (GP Log 0x04)
      121. Page Offset Size Value Flags Description
      122. 0x01 ===== = = === == General Statistics (rev 2) ==
      123. 0x01 0x008 4 35 --- Lifetime Power-On Resets
      124. 0x01 0x010 4 9444 --- Power-on Hours
      125. 0x01 0x018 6 2768641860 --- Logical Sectors Written
      126. 0x01 0x020 6 89124078 --- Number of Write Commands
      127. 0x01 0x028 6 400486258 --- Logical Sectors Read
      128. 0x01 0x030 6 13942235 --- Number of Read Commands
      129. 0x02 ===== = = === == Free-Fall Statistics (empty) ==
      130. 0x03 ===== = = === == Rotating Media Statistics (empty) ==
      131. 0x04 ===== = = === == General Errors Statistics (rev 1) ==
      132. 0x04 0x008 4 0 --- Number of Reported Uncorrectable Errors
      133. 0x04 0x010 4 0 --- Resets Between Cmd Acceptance and Completion
      134. 0x05 ===== = = === == Temperature Statistics (empty) ==
      135. 0x06 ===== = = === == Transport Statistics (rev 1) ==
      136. 0x06 0x008 4 226 --- Number of Hardware Resets
      137. 0x06 0x018 4 0 --- Number of Interface CRC Errors
      138. 0x07 ===== = = === == Solid State Device Statistics (rev 1) ==
      139. 0x07 0x008 1 1 --- Percentage Used Endurance Indicator
      140. |||_ C monitored condition met
      141. ||__ D supports DSN
      142. |___ N normalized value
      143. SATA Phy Event Counters (GP Log 0x11) not supported
      Display All

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

    • New

      savellm wrote:

      If I did DD or clonezilla would it still clone the boot so it would make a 100% like for like and be able to boot from the spare device?
      I don't have experience with using dd, with on-line drives, which was why I added the caveat in the first post.
      (Perhaps someone who has experience with using dd with on-line drives might chime in.)

      On the other hand, using (and booting) the clonezilla add-on is an off-line cloning process, and cloning perfect copies is what clonzilla is designed for. Again, with SSH to get access to a one time boot, I believe it will do what you're looking for.
      ______________________________________________

      I use and clone USB thumbdrives for the same reason - OS backup that's easy to restore.
    • New

      savellm wrote:

      still wondering on if there are any issues with removing ram, installing and putting ram back?
      Sure but why? Just use the debian installer and then install OMV.
      omv 4.1.22 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      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!
    • New

      savellm wrote:

      Because I tried that and it didnt work with the UEFI installer.
      I need to go back and look into it again but just havent had the time and I can get the 4.1.3 installed no problem.
      Strange that the OMV ISO would work better with UEFI than the Debian ISO. I guess if 4.1.3 works and you are willing to remove dimms, go for it. It won't resize swap when you re-install the dimms.
      omv 4.1.22 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      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!
    • New

      savellm wrote:

      Besides smaller swap, that wont be a long term issue right?
      Nope. If you have that much ram, you probably don't need swap.
      omv 4.1.22 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      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!
    • New

      crashtest wrote:

      savellm wrote:

      When a new OMV update comes out, would I have to keep removing ram to do the updates?
      Assuming that nothing major changes in OMV, the next version may be available as a command line package upgrade. omv-release-upgrade
      My understanding of what will become OMV 5 is that an upgrade over any prior version will be impossible and a new install from scratch will be the only way to have it.
      --
      Google is your friend and Bob's your uncle!

      OMV 4.x - ASRock Rack C2550D4I - 16GB ECC - Silverstone DS380