SWAP partition needed when running OMV in USB Stick?

    • Resolved

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

    • SWAP partition needed when running OMV in USB Stick?

      Hello guys,

      I am sorry if the answer to this question is in the forum but I did look and didn't find it...
      When running OMV on a usb stick or microsd flash, the pluggin "Flash memory" is needed in order to avoid the massive read/writes on the flash memory and therefore to break it.
      When installing the pluggin, one need to "comment out the swap partition" in etc/fstab as part of the instructions.

      Well...my question is then... Do we need a swap partition in this case or can we just remove it with gparted and take benefict from this space for the system partition in EXT4? I would say we can remove it but maybe I am missing something so I need confirmation.


      Thank you in advance.
    • The requirement for swap depends on how much memory your system has. I have 16GB of RAM in my OMV server and have run it with 8GB in the past and run it without swap. I have never had a problem. And if your hardware isn't really ancient, you can't even find RAM modules that would be too small to run without swap enabled.

      I suggest that you disable swap in fstab, and reboot, but leave the swap partition in place on the disk for a while. If your machine runs out of RAM under heavy use, it will then crash because there is no available swap. If this happens reboot it, immediately re-enable swap in fstab, and reboot it again. If you are forced to re-enable swap I would like to know how much RAM you have :)

      If the machine doesn't run out of RAM and crash, then you can delete the swap partition and make use of that space.
      OMV 3.x - ASRock Rack C2550D4I - 16GB ECC - Silverstone DS380

      The post was edited 1 time, last by gderf ().

    • gderf wrote:

      The requirement for swap depends on how much memory your system has. I have 16GB of RAM in my OMV server and have run it with 8GB in the past and run it without swap. I have never had a problem. And if your hardware isn't really ancient, you can't even find RAM modules that would be too small to run without swap enabled.

      I suggest that you disable swap in fstab, and reboot, but leave the swap partition in place on the disk for a while. If your machine runs out of RAM under heavy use, it will then crash because there is no available swap. If this happens reboot it, immediately re-enable swap in fstab, and reboot it again.

      If the machine doesn't run out of RAM and crash, then you can delete the swap partition and make use of that space.

      Hi,

      it is already as this as required by the "flash memory" pluggin that requires to comment the swap partition to avoid any over-writes in the flash memory. That's the reason I am asking if it's already commented, then I guess I don't need the partition in the drive and I can benefict from additiional space.



      siulman@omv:/srv/Data$ cat /etc/fstab
      # /etc/fstab: static file system information.
      #
      # Use 'blkid' to print the universally unique identifier for a
      # device; this may be used with UUID= as a more robust way to name devices
      # that works even if disks are added and removed. See fstab(5).
      #
      # <file system> <mount point> <type> <options> <dump> <pass>
      # / was on /dev/sdf1 during installation
      UUID=bf71f21c-e6d3-4650-ae60-7765056a76fa / ext4 noatime,nodiratime, errors=remount-ro 0 1
      # swap was on /dev/sdf5 during installation
      #UUID=92096a5f-ee5f-4efe-aaaf-c610f8cc9685 none swap sw 0 0
      tmpfs /tmp tmpfs defaults 0 0
      # >>> [openmediavault]
      /dev/disk/by-label/Data /srv/dev-disk-by-label-Data ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
      /dev/disk/by-label/Media /srv/dev-disk-by-label-Media ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
      /dev/disk/by-label/Backup /srv/dev-disk-by-label-Backup ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
      /dev/disk/by-label/VM /srv/dev-disk-by-label-VM ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,discard,acl 0 2
      # <<< [openmediavault]



    • I think you are missing the point.

      Unless your system memory is inadequate to run without swap, then the swap partition will not be written to at all. In this case, the Flash Memory plugin offers no benefit with respect to disk writes to swap - you can not reduce writes to swap that never happen in the first place - so just try running without swap first and see what happens.

      Why the Flash Memory plugin helps is because it moves the the more heavily written to areas of the physical disk into RAM disks (primarily the logs and RRD graph data).

      If you don't have enough RAM, then you must have swap on disk. And if you don't have enough RAM you can't further reduce available RAM by utilizing some of it for the RAM disks that the Flash Memory plugin sets up and uses.

      Another way to look at this is to say that using the Flash Memory plugin on a system that will not run without active swap space is pointless. You will either have an unstable system that crashes due lack of swap, or if swap is enabled on a delicate Flash type drive, and it has to be enabled to keep the machine running, you might burn out the disk eventually.

      It's all about having enough RAM, period. That's why I suggested disabling swap and running with the Flash Memory plugin for a while. If you can't keep the machine running, then get more RAM and then try again.
      OMV 3.x - ASRock Rack C2550D4I - 16GB ECC - Silverstone DS380
    • New

      Understood.

      Thanks for the explanation.

      I just tryed to move my OMV system from the USB stick to a 2.5 HDD in USB. Then I removed "Flash memory" pluggin as long as noatime,nodiratime in /etc/fstab and re-enabled "swap" partition in /etc/fstab too.
      Something weird is happening... It is taking a lot of time to boot because of this....

      Would you know what is it?

      "A start job is running...."

      At the end, it boots and everything is ok but it delays A LOT the booting process... a couple of minutes. I tryed to reboot a couple of times but nothing changed.

      Please help.





      UPDATE:

      Got it, that was was easy.... When migrating from USB stick to 2.5 HDD I had to use gparted to use the unallocated size (new HDD was bigger than the stick) and I needed to change the swap partition (remove and re-create) so at the end the UUID changed. Updating the UUID in /etc/fstab fixed it.

      Do you know how to check that the "flash memory" was completely reverted and my system is running in a "standard mode" and it does not (quoting you): "move the the more heavily written to areas of the physical disk into RAM disks (primarily the logs and RRD graph data)"

      [i][b]??
      [/i][/b]

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

    • New

      A UUID change will cause that loooooooooong pause you were seeing. Wasn't that annoying?

      One way to see if the Flash Memory plugin is in use is to open a shell and type:

      df -h

      If you see stuff like the below (folder2ram) those are the RAM disks the Flash Memory plugin sets up and uses.

      folder2ram 7.9G 32M 7.8G 1% /var/log
      folder2ram 7.9G 20K 7.9G 1% /var/tmp
      folder2ram 7.9G 1.2M 7.9G 1% /var/lib/openmediavault/rrd
      folder2ram 7.9G 1.9M 7.9G 1% /var/spool
      folder2ram 7.9G 36M 7.8G 1% /var/lib/rrdcached
      folder2ram 7.9G 8.0K 7.9G 1% /var/lib/monit
      folder2ram 7.9G 0 7.9G 0% /var/lib/netatalk/CNID
      folder2ram 7.9G 496K 7.9G 1% /var/cache/samba
      OMV 3.x - ASRock Rack C2550D4I - 16GB ECC - Silverstone DS380
    • New

      gderf wrote:

      A UUID change will cause that loooooooooong pause you were seeing. Wasn't that annoying?

      One way to see if the Flash Memory plugin is in use is to open a shell and type:

      df -h

      If you see stuff like the below (folder2ram) those are the RAM disks the Flash Memory plugin sets up and uses.

      folder2ram 7.9G 32M 7.8G 1% /var/log
      folder2ram 7.9G 20K 7.9G 1% /var/tmp
      folder2ram 7.9G 1.2M 7.9G 1% /var/lib/openmediavault/rrd
      folder2ram 7.9G 1.9M 7.9G 1% /var/spool
      folder2ram 7.9G 36M 7.8G 1% /var/lib/rrdcached
      folder2ram 7.9G 8.0K 7.9G 1% /var/lib/monit
      folder2ram 7.9G 0 7.9G 0% /var/lib/netatalk/CNID
      folder2ram 7.9G 496K 7.9G 1% /var/cache/samba



      I think I am ok then.

      Thanks man! that was instructive. Sending a like!


      siulman@omv:/$ df -h
      Filesystem Size Used Avail Use% Mounted on
      udev 10M 0 10M 0% /dev
      tmpfs 1.2G 8.9M 1.2G 1% /run
      /dev/sdd1 135G 2.5G 126G 2% /
      tmpfs 2.9G 4.0K 2.9G 1% /dev/shm
      tmpfs 5.0M 0 5.0M 0% /run/lock
      tmpfs 2.9G 0 2.9G 0% /sys/fs/cgroup
      tmpfs 2.9G 1.7M 2.9G 1% /tmp
      /dev/sda1 59G 39G 21G 66% /srv/dev-disk-by-label-VM
      /dev/sde1 1.8T 524G 1.3T 29% /srv/dev-disk-by-label-Backup
      /dev/sdb1 2.7T 375G 2.4T 14% /srv/dev-disk-by-label-Data
      /dev/sdc1 2.7T 780G 2.0T 29% /srv/dev-disk-by-label-Media
      siulman@omv:/$


      Last question if I may. Do you know how to backup only the effective DATA used in a disk when doing a clonezilla? Because if you try to restore in a smaller disk it just does not work....
    • New

      I have never tried this, but it is supposed to allow clonezilla to restore an image to a smaller disk.

      Select Advanced mode and use the -icds option.

      Just be sure that the actual amount of data being restored really will fit onto the smaller drive.
      OMV 3.x - ASRock Rack C2550D4I - 16GB ECC - Silverstone DS380
    • New

      gderf wrote:

      have never tried this, but it is supposed to allow clonezilla to restore an image to a smaller disk.

      Select Advanced mode and use the -icds option.

      Just be sure that the actual amount of data being restored really will fit onto the smaller drive.
      It does work some times but not always. I have used it many times. It usually fails the most when going to a much smaller drive.
      omv 4.0.14 arrakis | 64 bit | 4.13 backports kernel | omvextrasorg 4.1.0
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • New

      Brainfuck Source Code

      1. [spoiler]
      2. smartctl 6.4 2014-10-07 r4002 [x86_64-linux-4.9.0-0.bpo.4-amd64] (local build)
      3. Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
      4. === START OF INFORMATION SECTION ===
      5. Model Family: Toshiba 2.5" HDD MK..37GSX
      6. Device Model: TOSHIBA MK1637GSX
      7. Serial Number: 57LPFBS5S
      8. Firmware Version: DL030M
      9. User Capacity: 160,041,885,696 bytes [160 GB]
      10. Sector Size: 512 bytes logical/physical
      11. Device is: In smartctl database [for details use: -P show]
      12. ATA Version is: ATA/ATAPI-7 (minor revision not indicated)
      13. Local Time is: Wed Dec 6 23:19:45 2017 CET
      14. SMART support is: Available - device has SMART capability.
      15. SMART support is: Enabled
      16. AAM feature is: Unavailable
      17. APM level is: 128 (minimum power consumption without standby)
      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 Status not supported: Incomplete response, ATA output registers missing
      24. SMART overall-health self-assessment test result: PASSED
      25. Warning: This result is based on an Attribute check.
      26. General SMART Values:
      27. Offline data collection status: (0x80) Offline data collection activity
      28. was never started.
      29. Auto Offline Data Collection: Enabled.
      30. Self-test execution status: ( 248) Self-test routine in progress...
      31. 80% of test remaining.
      32. Total time to complete Offline
      33. data collection: ( 120) seconds.
      34. Offline data collection
      35. capabilities: (0x5b) SMART execute Offline immediate.
      36. Auto Offline data collection on/off support.
      37. Suspend Offline collection upon new
      38. command.
      39. Offline surface scan supported.
      40. Self-test supported.
      41. No Conveyance Self-test supported.
      42. Selective Self-test supported.
      43. SMART capabilities: (0x0003) Saves SMART data before entering
      44. power-saving mode.
      45. Supports SMART auto save timer.
      46. Error logging capability: (0x01) Error logging supported.
      47. General Purpose Logging supported.
      48. Short self-test routine
      49. recommended polling time: ( 2) minutes.
      50. Extended self-test routine
      51. recommended polling time: ( 92) minutes.
      52. SCT capabilities: (0x0001) SCT Status supported.
      53. SMART Attributes Data Structure revision number: 16
      54. Vendor Specific SMART Attributes with Thresholds:
      55. ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
      56. 1 Raw_Read_Error_Rate PO-R-- 100 100 050 - 0
      57. 2 Throughput_Performance P-S--- 100 100 050 - 0
      58. 3 Spin_Up_Time POS--K 100 100 001 - 1805
      59. 4 Start_Stop_Count -O--CK 100 100 000 - 4847
      60. 5 Reallocated_Sector_Ct PO--CK 100 100 050 - 16
      61. 7 Seek_Error_Rate PO-R-- 100 100 050 - 0
      62. 8 Seek_Time_Performance P-S--- 100 100 050 - 0
      63. 9 Power_On_Hours -O--CK 078 078 000 - 9069
      64. 10 Spin_Retry_Count PO--CK 196 100 030 - 0
      65. 12 Power_Cycle_Count -O--CK 100 100 000 - 4531
      66. 192 Power-Off_Retract_Count -O--CK 100 100 000 - 425
      67. 193 Load_Cycle_Count -O--CK 083 083 000 - 178224
      68. 194 Temperature_Celsius -O---K 100 100 000 - 36 (Min/Max 11/56)
      69. 196 Reallocated_Event_Count -O--CK 100 100 000 - 16
      70. 197 Current_Pending_Sector -O--CK 100 100 000 - 0
      71. 198 Offline_Uncorrectable ----CK 100 100 000 - 0
      72. 199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 0
      73. 220 Disk_Shift -O---- 100 100 000 - 8314
      74. 222 Loaded_Hours -O--CK 082 082 000 - 7208
      75. 223 Load_Retry_Count -O--CK 100 100 000 - 0
      76. 224 Load_Friction -O---K 100 100 000 - 0
      77. 226 Load-in_Time -OS--K 100 100 000 - 330
      78. 240 Head_Flying_Hours P----- 100 100 001 - 0
      79. ||||||_ K auto-keep
      80. |||||__ C event count
      81. ||||___ R error rate
      82. |||____ S speed/performance
      83. ||_____ O updated online
      84. |______ P prefailure warning
      85. ATA_READ_LOG_EXT (addr=0x00:0x00, page=0, n=1) failed: scsi error unsupported scsi opcode
      86. Read GP Log Directory failed
      87. SMART Log Directory Version 1 [multi-sector log support]
      88. Address Access R/W Size Description
      89. 0x00 SL R/O 1 Log Directory
      90. 0x01 SL R/O 1 Summary SMART error log
      91. 0x02 SL R/O 51 Comprehensive SMART error log
      92. 0x06 SL R/O 1 SMART self-test log
      93. 0x09 SL R/W 1 Selective self-test log
      94. 0x80-0x9f SL R/W 16 Host vendor specific log
      95. 0xe0 SL R/W 1 SCT Command/Status
      96. 0xe1 SL R/W 1 SCT Data Transfer
      97. SMART Extended Comprehensive Error Log (GP Log 0x03) not supported
      98. SMART Error Log Version: 1
      99. ATA Error Count: 300 (device log contains only the most recent five errors)
      100. CR = Command Register [HEX]
      101. FR = Features Register [HEX]
      102. SC = Sector Count Register [HEX]
      103. SN = Sector Number Register [HEX]
      104. CL = Cylinder Low Register [HEX]
      105. CH = Cylinder High Register [HEX]
      106. DH = Device/Head Register [HEX]
      107. DC = Device Command Register [HEX]
      108. ER = Error register [HEX]
      109. ST = Status register [HEX]
      110. Powered_Up_Time is measured from power on, and printed as
      111. DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
      112. SS=sec, and sss=millisec. It "wraps" after 49.710 days.
      113. Error 300 occurred at disk power-on lifetime: 5507 hours (229 days + 11 hours)
      114. When the command that caused the error occurred, the device was active or idle.
      115. After command completion occurred, registers were:
      116. ER ST SC SN CL CH DH
      117. -- -- -- -- -- -- --
      118. 40 51 2f 39 aa 44 e0 Error: UNC 47 sectors at LBA = 0x0044aa39 = 4500025
      119. Commands leading to the command that caused the error were:
      120. CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
      121. -- -- -- -- -- -- -- -- ---------------- --------------------
      122. 25 00 00 68 a9 44 e0 00 00:22:08.430 READ DMA EXT
      123. 25 00 00 68 a8 44 e0 00 00:22:08.428 READ DMA EXT
      124. 25 00 00 68 a7 44 e0 00 00:22:08.425 READ DMA EXT
      125. 25 00 00 68 a6 44 e0 00 00:22:08.407 READ DMA EXT
      126. ea 00 00 00 00 00 a0 00 00:22:08.362 FLUSH CACHE EXT
      127. Error 299 occurred at disk power-on lifetime: 5507 hours (229 days + 11 hours)
      128. When the command that caused the error occurred, the device was active or idle.
      129. After command completion occurred, registers were:
      130. ER ST SC SN CL CH DH
      131. -- -- -- -- -- -- --
      132. 40 51 2f 39 aa 44 e0 Error: UNC 47 sectors at LBA = 0x0044aa39 = 4500025
      133. Commands leading to the command that caused the error were:
      134. CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
      135. -- -- -- -- -- -- -- -- ---------------- --------------------
      136. 25 00 00 68 a9 44 e0 00 00:21:36.787 READ DMA EXT
      137. 25 00 00 68 a8 44 e0 00 00:21:36.784 READ DMA EXT
      138. 25 00 00 68 a7 44 e0 00 00:21:36.780 READ DMA EXT
      139. 25 00 00 68 a6 44 e0 00 00:21:36.743 READ DMA EXT
      140. 35 00 88 78 ea 80 e0 00 00:21:36.742 WRITE DMA EXT
      141. Error 298 occurred at disk power-on lifetime: 5507 hours (229 days + 11 hours)
      142. When the command that caused the error occurred, the device was active or idle.
      143. After command completion occurred, registers were:
      144. ER ST SC SN CL CH DH
      145. -- -- -- -- -- -- --
      146. 40 51 2f 39 aa 44 e0 Error: UNC 47 sectors at LBA = 0x0044aa39 = 4500025
      147. Commands leading to the command that caused the error were:
      148. CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
      149. -- -- -- -- -- -- -- -- ---------------- --------------------
      150. 25 00 00 68 a9 44 e0 00 00:21:25.097 READ DMA EXT
      151. 25 00 00 68 a8 44 e0 00 00:21:25.095 READ DMA EXT
      152. 25 00 00 68 a7 44 e0 00 00:21:25.091 READ DMA EXT
      153. 25 00 00 68 a6 44 e0 00 00:21:25.074 READ DMA EXT
      154. 35 00 88 08 44 34 e0 00 00:21:25.073 WRITE DMA EXT
      155. Error 297 occurred at disk power-on lifetime: 5507 hours (229 days + 11 hours)
      156. When the command that caused the error occurred, the device was active or idle.
      157. After command completion occurred, registers were:
      158. ER ST SC SN CL CH DH
      159. -- -- -- -- -- -- --
      160. 40 51 2f 39 aa 44 e0 Error: UNC 47 sectors at LBA = 0x0044aa39 = 4500025
      161. Commands leading to the command that caused the error were:
      162. CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
      163. -- -- -- -- -- -- -- -- ---------------- --------------------
      164. 25 00 00 68 a9 44 e0 00 00:21:12.919 READ DMA EXT
      165. 25 00 00 68 a8 44 e0 00 00:21:12.917 READ DMA EXT
      166. 25 00 00 68 a7 44 e0 00 00:21:12.913 READ DMA EXT
      167. 25 00 00 68 a6 44 e0 00 00:21:12.872 READ DMA EXT
      168. 35 00 88 98 58 81 e0 00 00:21:12.871 WRITE DMA EXT
      169. Error 296 occurred at disk power-on lifetime: 5507 hours (229 days + 11 hours)
      170. When the command that caused the error occurred, the device was active or idle.
      171. After command completion occurred, registers were:
      172. ER ST SC SN CL CH DH
      173. -- -- -- -- -- -- --
      174. 40 51 2f 39 aa 44 e0 Error: UNC 47 sectors at LBA = 0x0044aa39 = 4500025
      175. Commands leading to the command that caused the error were:
      176. CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
      177. -- -- -- -- -- -- -- -- ---------------- --------------------
      178. 25 00 00 68 a9 44 e0 00 00:21:00.574 READ DMA EXT
      179. 25 00 00 68 a8 44 e0 00 00:21:00.572 READ DMA EXT
      180. 25 00 00 68 a7 44 e0 00 00:21:00.568 READ DMA EXT
      181. 25 00 00 68 a6 44 e0 00 00:21:00.532 READ DMA EXT
      182. 35 00 88 98 a7 81 e0 00 00:21:00.531 WRITE DMA EXT
      183. SMART Extended Self-test Log (GP Log 0x07) not supported
      184. SMART Self-test log structure revision number 1
      185. Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
      186. # 1 Short offline Completed without error 00% 9069 -
      187. SMART Selective self-test log data structure revision number 1
      188. SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
      189. 1 0 0 Not_testing
      190. 2 0 0 Not_testing
      191. 3 0 0 Not_testing
      192. 4 0 0 Not_testing
      193. 5 0 0 Not_testing
      194. Selective self-test flags (0x0):
      195. After scanning selected spans, do NOT read-scan remainder of disk.
      196. If Selective self-test is pending on power-up, resume after 0 minute delay.
      197. SCT Status Version: 2
      198. SCT Version (vendor specific): 1 (0x0001)
      199. SCT Support Level: 1
      200. Device State: DST executing in background (3)
      201. Current Temperature: 36 Celsius
      202. Power Cycle Max Temperature: 36 Celsius
      203. Lifetime Max Temperature: 56 Celsius
      204. SCT Data Table command not supported
      205. SCT Error Recovery Control command not supported
      206. Device Statistics (GP/SMART Log 0x04) not supported
      207. ATA_READ_LOG_EXT (addr=0x11:0x00, page=0, n=1) failed: scsi error unsupported scsi opcode
      208. Read SATA Phy Event Counters failed
      209. [/spoiler]
      Display All
    • New

      Dude... you have your usb stick plugged in!! That is where the other kernel is coming from in your other thread.

      Run a long test on the 2.5" drive. Really up to you if you want to risk using the drive. If you have a backup and handle a bit of downtime, don't worry about the 2.5" drive.
      omv 4.0.14 arrakis | 64 bit | 4.13 backports kernel | omvextrasorg 4.1.0
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • New

      Brainfuck Source Code

      1. [spoiler]
      2. smartctl 6.4 2014-10-07 r4002 [x86_64-linux-4.9.0-0.bpo.4-amd64] (local build)
      3. Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
      4. === START OF INFORMATION SECTION ===
      5. Model Family: Toshiba 2.5" HDD MK..37GSX
      6. Device Model: TOSHIBA MK1637GSX
      7. Serial Number: 57LPFBS5S
      8. Firmware Version: DL030M
      9. User Capacity: 160,041,885,696 bytes [160 GB]
      10. Sector Size: 512 bytes logical/physical
      11. Device is: In smartctl database [for details use: -P show]
      12. ATA Version is: ATA/ATAPI-7 (minor revision not indicated)
      13. Local Time is: Wed Dec 6 23:19:45 2017 CET
      14. SMART support is: Available - device has SMART capability.
      15. SMART support is: Enabled
      16. AAM feature is: Unavailable
      17. APM level is: 128 (minimum power consumption without standby)
      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 Status not supported: Incomplete response, ATA output registers missing
      24. SMART overall-health self-assessment test result: PASSED
      25. Warning: This result is based on an Attribute check.
      26. General SMART Values:
      27. Offline data collection status: (0x80) Offline data collection activity
      28. was never started.
      29. Auto Offline Data Collection: Enabled.
      30. Self-test execution status: ( 248) Self-test routine in progress...
      31. 80% of test remaining.
      32. Total time to complete Offline
      33. data collection: ( 120) seconds.
      34. Offline data collection
      35. capabilities: (0x5b) SMART execute Offline immediate.
      36. Auto Offline data collection on/off support.
      37. Suspend Offline collection upon new
      38. command.
      39. Offline surface scan supported.
      40. Self-test supported.
      41. No Conveyance Self-test supported.
      42. Selective Self-test supported.
      43. SMART capabilities: (0x0003) Saves SMART data before entering
      44. power-saving mode.
      45. Supports SMART auto save timer.
      46. Error logging capability: (0x01) Error logging supported.
      47. General Purpose Logging supported.
      48. Short self-test routine
      49. recommended polling time: ( 2) minutes.
      50. Extended self-test routine
      51. recommended polling time: ( 92) minutes.
      52. SCT capabilities: (0x0001) SCT Status supported.
      53. SMART Attributes Data Structure revision number: 16
      54. Vendor Specific SMART Attributes with Thresholds:
      55. ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
      56. 1 Raw_Read_Error_Rate PO-R-- 100 100 050 - 0
      57. 2 Throughput_Performance P-S--- 100 100 050 - 0
      58. 3 Spin_Up_Time POS--K 100 100 001 - 1805
      59. 4 Start_Stop_Count -O--CK 100 100 000 - 4847
      60. 5 Reallocated_Sector_Ct PO--CK 100 100 050 - 16
      61. 7 Seek_Error_Rate PO-R-- 100 100 050 - 0
      62. 8 Seek_Time_Performance P-S--- 100 100 050 - 0
      63. 9 Power_On_Hours -O--CK 078 078 000 - 9069
      64. 10 Spin_Retry_Count PO--CK 196 100 030 - 0
      65. 12 Power_Cycle_Count -O--CK 100 100 000 - 4531
      66. 192 Power-Off_Retract_Count -O--CK 100 100 000 - 425
      67. 193 Load_Cycle_Count -O--CK 083 083 000 - 178224
      68. 194 Temperature_Celsius -O---K 100 100 000 - 36 (Min/Max 11/56)
      69. 196 Reallocated_Event_Count -O--CK 100 100 000 - 16
      70. 197 Current_Pending_Sector -O--CK 100 100 000 - 0
      71. 198 Offline_Uncorrectable ----CK 100 100 000 - 0
      72. 199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 0
      73. 220 Disk_Shift -O---- 100 100 000 - 8314
      74. 222 Loaded_Hours -O--CK 082 082 000 - 7208
      75. 223 Load_Retry_Count -O--CK 100 100 000 - 0
      76. 224 Load_Friction -O---K 100 100 000 - 0
      77. 226 Load-in_Time -OS--K 100 100 000 - 330
      78. 240 Head_Flying_Hours P----- 100 100 001 - 0
      79. ||||||_ K auto-keep
      80. |||||__ C event count
      81. ||||___ R error rate
      82. |||____ S speed/performance
      83. ||_____ O updated online
      84. |______ P prefailure warning
      85. ATA_READ_LOG_EXT (addr=0x00:0x00, page=0, n=1) failed: scsi error unsupported scsi opcode
      86. Read GP Log Directory failed
      87. SMART Log Directory Version 1 [multi-sector log support]
      88. Address Access R/W Size Description
      89. 0x00 SL R/O 1 Log Directory
      90. 0x01 SL R/O 1 Summary SMART error log
      91. 0x02 SL R/O 51 Comprehensive SMART error log
      92. 0x06 SL R/O 1 SMART self-test log
      93. 0x09 SL R/W 1 Selective self-test log
      94. 0x80-0x9f SL R/W 16 Host vendor specific log
      95. 0xe0 SL R/W 1 SCT Command/Status
      96. 0xe1 SL R/W 1 SCT Data Transfer
      97. SMART Extended Comprehensive Error Log (GP Log 0x03) not supported
      98. SMART Error Log Version: 1
      99. ATA Error Count: 300 (device log contains only the most recent five errors)
      100. CR = Command Register [HEX]
      101. FR = Features Register [HEX]
      102. SC = Sector Count Register [HEX]
      103. SN = Sector Number Register [HEX]
      104. CL = Cylinder Low Register [HEX]
      105. CH = Cylinder High Register [HEX]
      106. DH = Device/Head Register [HEX]
      107. DC = Device Command Register [HEX]
      108. ER = Error register [HEX]
      109. ST = Status register [HEX]
      110. Powered_Up_Time is measured from power on, and printed as
      111. DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
      112. SS=sec, and sss=millisec. It "wraps" after 49.710 days.
      113. Error 300 occurred at disk power-on lifetime: 5507 hours (229 days + 11 hours)
      114. When the command that caused the error occurred, the device was active or idle.
      115. After command completion occurred, registers were:
      116. ER ST SC SN CL CH DH
      117. -- -- -- -- -- -- --
      118. 40 51 2f 39 aa 44 e0 Error: UNC 47 sectors at LBA = 0x0044aa39 = 4500025
      119. Commands leading to the command that caused the error were:
      120. CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
      121. -- -- -- -- -- -- -- -- ---------------- --------------------
      122. 25 00 00 68 a9 44 e0 00 00:22:08.430 READ DMA EXT
      123. 25 00 00 68 a8 44 e0 00 00:22:08.428 READ DMA EXT
      124. 25 00 00 68 a7 44 e0 00 00:22:08.425 READ DMA EXT
      125. 25 00 00 68 a6 44 e0 00 00:22:08.407 READ DMA EXT
      126. ea 00 00 00 00 00 a0 00 00:22:08.362 FLUSH CACHE EXT
      127. Error 299 occurred at disk power-on lifetime: 5507 hours (229 days + 11 hours)
      128. When the command that caused the error occurred, the device was active or idle.
      129. After command completion occurred, registers were:
      130. ER ST SC SN CL CH DH
      131. -- -- -- -- -- -- --
      132. 40 51 2f 39 aa 44 e0 Error: UNC 47 sectors at LBA = 0x0044aa39 = 4500025
      133. Commands leading to the command that caused the error were:
      134. CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
      135. -- -- -- -- -- -- -- -- ---------------- --------------------
      136. 25 00 00 68 a9 44 e0 00 00:21:36.787 READ DMA EXT
      137. 25 00 00 68 a8 44 e0 00 00:21:36.784 READ DMA EXT
      138. 25 00 00 68 a7 44 e0 00 00:21:36.780 READ DMA EXT
      139. 25 00 00 68 a6 44 e0 00 00:21:36.743 READ DMA EXT
      140. 35 00 88 78 ea 80 e0 00 00:21:36.742 WRITE DMA EXT
      141. Error 298 occurred at disk power-on lifetime: 5507 hours (229 days + 11 hours)
      142. When the command that caused the error occurred, the device was active or idle.
      143. After command completion occurred, registers were:
      144. ER ST SC SN CL CH DH
      145. -- -- -- -- -- -- --
      146. 40 51 2f 39 aa 44 e0 Error: UNC 47 sectors at LBA = 0x0044aa39 = 4500025
      147. Commands leading to the command that caused the error were:
      148. CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
      149. -- -- -- -- -- -- -- -- ---------------- --------------------
      150. 25 00 00 68 a9 44 e0 00 00:21:25.097 READ DMA EXT
      151. 25 00 00 68 a8 44 e0 00 00:21:25.095 READ DMA EXT
      152. 25 00 00 68 a7 44 e0 00 00:21:25.091 READ DMA EXT
      153. 25 00 00 68 a6 44 e0 00 00:21:25.074 READ DMA EXT
      154. 35 00 88 08 44 34 e0 00 00:21:25.073 WRITE DMA EXT
      155. Error 297 occurred at disk power-on lifetime: 5507 hours (229 days + 11 hours)
      156. When the command that caused the error occurred, the device was active or idle.
      157. After command completion occurred, registers were:
      158. ER ST SC SN CL CH DH
      159. -- -- -- -- -- -- --
      160. 40 51 2f 39 aa 44 e0 Error: UNC 47 sectors at LBA = 0x0044aa39 = 4500025
      161. Commands leading to the command that caused the error were:
      162. CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
      163. -- -- -- -- -- -- -- -- ---------------- --------------------
      164. 25 00 00 68 a9 44 e0 00 00:21:12.919 READ DMA EXT
      165. 25 00 00 68 a8 44 e0 00 00:21:12.917 READ DMA EXT
      166. 25 00 00 68 a7 44 e0 00 00:21:12.913 READ DMA EXT
      167. 25 00 00 68 a6 44 e0 00 00:21:12.872 READ DMA EXT
      168. 35 00 88 98 58 81 e0 00 00:21:12.871 WRITE DMA EXT
      169. Error 296 occurred at disk power-on lifetime: 5507 hours (229 days + 11 hours)
      170. When the command that caused the error occurred, the device was active or idle.
      171. After command completion occurred, registers were:
      172. ER ST SC SN CL CH DH
      173. -- -- -- -- -- -- --
      174. 40 51 2f 39 aa 44 e0 Error: UNC 47 sectors at LBA = 0x0044aa39 = 4500025
      175. Commands leading to the command that caused the error were:
      176. CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
      177. -- -- -- -- -- -- -- -- ---------------- --------------------
      178. 25 00 00 68 a9 44 e0 00 00:21:00.574 READ DMA EXT
      179. 25 00 00 68 a8 44 e0 00 00:21:00.572 READ DMA EXT
      180. 25 00 00 68 a7 44 e0 00 00:21:00.568 READ DMA EXT
      181. 25 00 00 68 a6 44 e0 00 00:21:00.532 READ DMA EXT
      182. 35 00 88 98 a7 81 e0 00 00:21:00.531 WRITE DMA EXT
      183. SMART Extended Self-test Log (GP Log 0x07) not supported
      184. SMART Self-test log structure revision number 1
      185. Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
      186. # 1 Short offline Completed without error 00% 9069 -
      187. SMART Selective self-test log data structure revision number 1
      188. SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
      189. 1 0 0 Not_testing
      190. 2 0 0 Not_testing
      191. 3 0 0 Not_testing
      192. 4 0 0 Not_testing
      193. 5 0 0 Not_testing
      194. Selective self-test flags (0x0):
      195. After scanning selected spans, do NOT read-scan remainder of disk.
      196. If Selective self-test is pending on power-up, resume after 0 minute delay.
      197. SCT Status Version: 2
      198. SCT Version (vendor specific): 1 (0x0001)
      199. SCT Support Level: 1
      200. Device State: DST executing in background (3)
      201. Current Temperature: 36 Celsius
      202. Power Cycle Max Temperature: 36 Celsius
      203. Lifetime Max Temperature: 56 Celsius
      204. SCT Data Table command not supported
      205. SCT Error Recovery Control command not supported
      206. Device Statistics (GP/SMART Log 0x04) not supported
      207. ATA_READ_LOG_EXT (addr=0x11:0x00, page=0, n=1) failed: scsi error unsupported scsi opcode
      208. Read SATA Phy Event Counters failed
      209. [/spoiler]
      Display All
      The /dev/sdd is the HDD 2.5 plugged via USB. It’s the one that olds OMV right now where the system runs and the one that just showed the red light.
      The long test is running right now. I am not able to measure the risk according to the information provided by SMART. I understand the some sectors are failing but I don’t konw how risky it is or the probability of everything failing....
      do you?
    • New

      Relocating sectors can be done for many reasons. I cant measure risk for you but I wouldnt use it for an important system. I might use it for a test system.
      omv 4.0.14 arrakis | 64 bit | 4.13 backports kernel | omvextrasorg 4.1.0
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • New

      If they are new usb sticks and you use the flashmemory plugin, they might be better.

      I’ve seen flash fail before smart would report
      it. So I dont waste my time with smart.
      omv 4.0.14 arrakis | 64 bit | 4.13 backports kernel | omvextrasorg 4.1.0
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • New

      ryecoaaron wrote:

      If they are new usb sticks and you use the flashmemory plugin, they might be better.

      I’ve seen flash fail before smart would report
      it. So I dont waste my time with smart.
      Ok then, I am rolling back to usb stick with “flash memory” plugin as I have some of them at home and it would be easier and quicker to replace one 4G or 8G usb stick by another one 4G or 8G with clonezilla than replacing an HDD 2.5 150Gigs by an USB stick 4G/8G.

      I could even keep one “backup stick” plugged in, in case the primary fails just restore clonezilla to the other one with my ILO.