Odroid hc2 diskparking on OMV4

  • Hi, I'm having trouble with "192 Power-Off_Retract_Count" increase on Odroid Hc 2 (Omv 4), despite having added the correction from this link:


    https://wiki.odroid.com/odroid…eshooting/shutdown_script


    On a Seagate IronWolf 4 Tb


    I'm not a nerd but can understand that this problem smashes the hard drive?


    What should I do ?


    (I have purchased 2 hc2 to solve the problems that occurred at Cloudshell2 with unstable usb connection / unmount and are now having trouble with "192 Power-Off_Retract_Count" on Hc2 as if the issues will never end :()


    Knowing this is not a problem due to openmeidavault but maybe some nerds could give some advice :) - Thanks in advance :)



    smartctl 6.6 2016-05-31 r4324 [armv7l-linux-4.14.69-odroidxu4] (local build)
    Copyright (C) 2002-16, Bruce Allen, Christian Franke, http://www.smartmontools.org


    === START OF INFORMATION SECTION ===
    Model Family: Seagate IronWolf
    Device Model: ST4000VN008-2DR166
    Serial Number: WDH2XW3K
    LU WWN Device Id: 5 000c50 0aacce2a7
    Firmware Version: SC60
    User Capacity: 4,000,787,030,016 bytes [4.00 TB]
    Sector Sizes: 512 bytes logical, 4096 bytes physical
    Rotation Rate: 5980 rpm
    Form Factor: 3.5 inches
    Device is: In smartctl database [for details use: -P show]
    ATA Version is: ACS-3 T13/2161-D revision 5
    SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
    Local Time is: Wed Nov 14 14:21:52 2018 UTC
    SMART support is: Available - device has SMART capability.
    SMART support is: Enabled


    === START OF READ SMART DATA SECTION ===
    SMART overall-health self-assessment test result: PASSED


    General SMART Values:
    Offline data collection status: (0x82) Offline data collection activity
    was completed without error.
    Auto Offline Data Collection: Enabled.
    Self-test execution status: ( 0) The previous self-test routine completed
    without error or no self-test has ever
    been run.
    Total time to complete Offline
    data collection: ( 591) seconds.
    Offline data collection
    capabilities: (0x7b) SMART execute Offline immediate.
    Auto Offline data collection on/off support.
    Suspend Offline collection upon new
    command.
    Offline surface scan supported.
    Self-test supported.
    Conveyance Self-test supported.
    Selective Self-test supported.
    SMART capabilities: (0x0003) Saves SMART data before entering
    power-saving mode.
    Supports SMART auto save timer.
    Error logging capability: (0x01) Error logging supported.
    General Purpose Logging supported.
    Short self-test routine
    recommended polling time: ( 1) minutes.
    Extended self-test routine
    recommended polling time: ( 655) minutes.
    Conveyance self-test routine
    recommended polling time: ( 2) minutes.
    SCT capabilities: (0x50bd) SCT Status supported.
    SCT Error Recovery Control supported.
    SCT Feature Control supported.
    SCT Data Table supported.


    SMART Attributes Data Structure revision number: 10
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
    1 Raw_Read_Error_Rate 0x000f 083 064 044 Pre-fail Always - 198761572
    3 Spin_Up_Time 0x0003 094 093 000 Pre-fail Always - 0
    4 Start_Stop_Count 0x0032 099 099 020 Old_age Always - 1261
    5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
    7 Seek_Error_Rate 0x000f 076 060 045 Pre-fail Always - 36301290
    9 Power_On_Hours 0x0032 090 090 000 Old_age Always - 9004 (6 158 0)
    10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
    12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 189
    184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
    187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0
    188 Command_Timeout 0x0032 099 099 000 Old_age Always - 17180131332
    189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
    190 Airflow_Temperature_Cel 0x0022 062 061 040 Old_age Always - 38 (Min/Max 38/39)
    191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0
    192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 885
    193 Load_Cycle_Count 0x0032 097 097 000 Old_age Always - 6263
    194 Temperature_Celsius 0x0022 038 040 000 Old_age Always - 38 (0 20 0 0 0)
    197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
    198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
    199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
    240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 423 (220 221 0)
    241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 2012647957
    242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 3274270929


    SMART Error Log Version: 1
    No Errors Logged


    SMART Self-test log structure revision number 1
    Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
    # 1 Short offline Completed without error 00% 8857 -
    # 2 Short offline Completed without error 00% 8857 -


    SMART Selective self-test log data structure revision number 1
    SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
    1 0 0 Not_testing
    2 0 0 Not_testing
    3 0 0 Not_testing
    4 0 0 Not_testing
    5 0 0 Not_testing
    Selective self-test flags (0x0):
    After scanning selected spans, do NOT read-scan remainder of disk.
    If Selective self-test is pending on power-up, resume after 0 minute delay.

    • Offizieller Beitrag

    I use 12TB IronWolves with two of my hc2.


    I updated SATA and disabled all physical disk properties. Disk->edit. Otherwise OMV quickly dropped/unmounted them.


    When I updated SATA I also set spindown to 30 minuters.


    Now my IronWolves seem happy...


    https://wiki.odroid.com/odroid-xu4/software/jms578_fw_update

    • Offizieller Beitrag

    It doesn't seem so.


    nas1: (My first HC2.)
    Power_cycle_count is 75
    Start_stop_count is 951
    Power_on_hours is 2006
    Power_off_retract_count is 21


    nas2:
    Power_cycle_count is 41
    Start_stop_count is 274
    Power_on_hours is 1339
    Power_off_retract_count is 14

    • Offizieller Beitrag

    Yes. I set it to 30 minutes when I updated the firmware to SATA. You can set it to whatever you want, as long as it is 3 minutes or longer. See example 4 in the link above. It works fine without hdparm settings in physical disk properties. When I tried the physical disk properties the HDD was permanently unmounted after the first spindown and would not mount on reboot.

    • Offizieller Beitrag

    Also I underclocked four of my HC2 to 1400 MHz because they are still able to saturate GbE and I only use them as file servers. That makes the HC2s run cooler with less power. One HC2 runs full speed. It is the one with a SSD and on which I run Emby, LMS and some other software. I updated the SATA firmware on all 5, and set spin down to 30 minutes on all of them.

    • Offizieller Beitrag

    https://wiki.odroid.com/odroid…requtils_cpufreq_govornor


    I don't run S. M. A. R. T. other than manually from the GUI. I used it initially only to get HDD temperatures to ensure that the HDDs didn't run too hot. I had problems with the cooling, but I fixed it with a ultra low noise Noctua A12x25 FLX fan for all five HC2s.

    • Offizieller Beitrag

    Yes that looks right. Everything disabled.


    But it should be "/dev/sda" not "/ dev / sda". I assume that the firmware update fails otherwise?


    You should get:


    "Programming & Compare Success!!" response if the update was successful.


    You have to power cycle after successfully updating the firmware. A reboot is not enough. Pull the power plug and wait a few seconds before reinserting it again.


    The drive should now spin down after 30 minutes. However you need to make sure that you don't run any software that access the drive, or the 30 minute spin down delay restarts. You must have the rootfs on the SD card or on a remote network share, and not access /dev/sda at all for 30 minutes for this to work.


    When you access /dev/sda the HDD will spin up again. That may take a second or two. A small delay in the access while the drive spins up. As you saw above in my smart data it means an increase in start_stop_count. Also you hear the drive spin down or up.


    This works fine on all of my HC2s, including with my two 12 TB Ironwolf HDDs.

  • sudo smartctl -a /dev/sda :)


    What device do you use for nas trohn_javolta?

    Odroid Hc2 like others here. Thx that worked:


    192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 0


    Looks good to me. I have it running a couple month now and immediately updated the firmware of sata bridge and also installed the script on odroid wiki. But honestly never checked this value.

  • Okay, it seems to me that I've got it working now by following Adoby's advice & and disabel S.M.A.R.T check so it does not read on the disk constantly :)


    Most:


    "192 Power-Off_Retract_Count 0x0032 100 100,000 Old_age Always"


    Have my hard drives got while they were in a cloudshell2 which tells me that the problem is also there but it's not possible to keep an eye on that when S.M.A.R.T is broken on cloudshell 2 :)


    (The hard dishes were brand new when I put them in cloudshell 2)

    • Offizieller Beitrag

    wiki.odroid.com/odroid-xu4/app…requtils_cpufreq_govornor

    If you do like this, it will not be persistent.


    You can adjust the values of the related environmental variables in /etc/default/openmediavault

    Code
    OMV_CPUFREQUTILS_GOVERNOR=conservative
    OMV_CPUFREQUTILS_MINSPEED=300000
    OMV_CPUFREQUTILS_MAXSPEED=2000000

    and then


    omv-mkconf cpufrequtils

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!