• [6.9.2] Parity Drive will not spin down via GUI or Schedule


    SimonF
    • Minor

    Since upgrading to 6.9.2 I cannot spin down parity via GUI, as soon as I spin down it comes back up.

     

    Apr 8 10:18:45 Tower emhttpd: spinning down /dev/sdf
    Apr 8 10:18:58 Tower SAS Assist v0.85: Spinning down device /dev/sdf
    Apr 8 10:18:58 Tower emhttpd: read SMART /dev/sdf

     

    Revert to 6.9.1 issue no longer happens.

     

    I can manually spin down the drive. All other array drives which are also SAS spin down fine.

    root@Tower:~# sg_start -rp 3 /dev/sdf
    root@Tower:~# sdparm -C sense /dev/sdf
        /dev/sdf: SEAGATE   ST4000NM0023      XMGJ
    Additional sense: Standby condition activated by command

     

     

    Also is it possible to get an updated version of smartctl added.

     

    Will continue to do more testing.

     



    User Feedback

    Recommended Comments



    SimonF

    Posted (edited)

    @limetech is it possible to revert/disable these changes so we can look to see if its kernel/driver specific.

     

    emhttpd: detect out-of-band device spin-up

     

    I have reverted to 6.9.1 for now.

     

    For info I have replaced doron's Smartctl wrapper with r5215 of smartctl and its working fine in 6.9.1. and 6.9.2 for both SAS and SATA. Could it be updated for 6.10 or next 6.9 release?

     

    root@Tower:/usr/sbin# ls smart*
    smartctl*  smartctl.doron*  smartctl.real*  smartd*
    root@Tower:/usr/sbin# smartctl
    smartctl 7.3 2021-04-07 r5215 [x86_64-linux-5.10.21-Unraid] (CircleCI)
    Copyright (C) 2002-21, Bruce Allen, Christian Franke, www.smartmontools.org
    
    ERROR: smartctl requires a device name as the final command-line argument.
    
    
    Use smartctl -h to get a usage summary
    
    root@Tower:/usr/sbin# smartctl -n standby /dev/sde
    smartctl 7.3 2021-04-07 r5215 [x86_64-linux-5.10.21-Unraid] (CircleCI)
    Copyright (C) 2002-21, Bruce Allen, Christian Franke, www.smartmontools.org
    
    Device is in ACTIVE or IDLE mode
    root@Tower:/usr/sbin# smartctl -n standby /dev/sdf
    smartctl 7.3 2021-04-07 r5215 [x86_64-linux-5.10.21-Unraid] (CircleCI)
    Copyright (C) 2002-21, Bruce Allen, Christian Franke, www.smartmontools.org
    
    Device is in STANDBY BY COMMAND mode, exit(2)
    root@Tower:/usr/sbin# 

     

    Edited by SimonF
    • Like 1
    Link to comment
    Share on other sites

    At the behest of SimonF - here is an issue that I've found (and only corrected by reverting back to 6.9.1)

    I recently got my first HBA (LSI 9305-16i) with SAS-to-4xSATA cables to be able to add more SATA drives to my rig...the drives are a mixture of:
     

    • ST8000VN004
    • ST4000VN008
    • WDC_WD60EFAX

     

    I did the hardware change AND the update to 6.9.2 at the same time and noticed that none of my drives would spin-down automatically (which they had earlier) and thought it was due to the change in hardware.  I could force the drives and they would spin-down but not automatically after the set '15 minute' timeout (had 'Enable Spinup Groups' also set to 'No').  After looking at the logs - I would never see spindown requests?

     

    Reverted back to 6.9.1 and it automagically worked with no additional changes.

     

    HTH and looking forward to 6.9.3?

     

    -dave

    Link to comment
    Share on other sites
    On 4/12/2021 at 5:27 PM, ds679 said:

    After looking at the logs - I would never see spindown requests?

    Funnily I have completely the same after upgrading from 12TB Ultrastar to 18TB White Label,  why I wrote this script:

    https://forums.unraid.net/topic/106508-force-spindown-script/

     

    But I was not able to test 6.9.x by now. Maybe it does not happen there?!

     

    • Like 1
    Link to comment
    Share on other sites

    @limetechAre you able to advise on the out of band checking for 6.9.2? 

     

    emhttpd: detect out-of-band device spin-up how is this being done? It may be kernel or driver issue also as not all devices are affected.

    Link to comment
    Share on other sites

    So what's the answer? This is happening to me and I don't like it at. It's a replicable bug that is causing ware and tear on the system. This is a 40 day old bug that would not even be acceptable on FREE open source software. Does anyone know that is up? 

    Link to comment
    Share on other sites
    16 hours ago, SFord said:

    So what's the answer? This is happening to me and I don't like it at. It's a replicable bug that is causing ware and tear on the system. This is a 40 day old bug that would not even be acceptable on FREE open source software. Does anyone know that is up? 

    Have you tried installing 6.9.1?

    Link to comment
    Share on other sites
    1 hour ago, SimonF said:

    Have you tried installing 6.9.1?

    No. I don’t like that idea. Does a roll back clean up every bit of code? I’ll have to check every single change I made to the system, that’s kind of maddening. Then do I need to delete and reinstall all the Community plug-ins? It also looks like problems stated showing up in 6.9 and not just 6.9.2 so there were many changes to that code base. I’m surprised official SAS support took this long but hell you can’t even setup UnRAID as a iSCSI initiator. I guess this is all a “minor” bug and data is not lost. I’m not going to mess with a running system.

     

    I’m ranting a bit. Thanks for the suggestion. It will get fixed at some point it’s just weird that it’s taking so long. 

    Link to comment
    Share on other sites
    53 minutes ago, SFord said:

    Does a roll back clean up every bit of code?

    The rootfs is stored in the bzfiles so it will revert to 6.9.1 code at reboot.

     

    54 minutes ago, SFord said:

    Then do I need to delete and reinstall all the Community plug-ins

    Plugin are reloaded each reboot, you dont need to delete and reinstall.

     

    As long as they are compatible with 6.9.1 they will be loaded.

    55 minutes ago, SFord said:

    stated showing up in 6.9

    6.9.1 for me spun down SATA and SAS drives correct as long as you had doron SAS helper plugin.

     

     

    Link to comment
    Share on other sites

    Hi Guys,

    I'm facing some strange issues. My disks do spin down, but spin up again after a few minutes. I did try turning off docker and all scripts, but it still behaves the same way. VMs are not even installed.

    I have no clue how to track down the issue. I tried the SAS plugin, but nothing changed there.

    natasha-diagnostics-20210524-1829.zip

    Link to comment
    Share on other sites
    48 minutes ago, Jaster said:

    Hi Guys,

    I'm facing some strange issues. My disks do spin down, but spin up again after a few minutes. I did try turning off docker and all scripts, but it still behaves the same way. VMs are not even installed.

    I have no clue how to track down the issue. I tried the SAS plugin, but nothing changed there.

    natasha-diagnostics-20210524-1829.zip 198.57 kB · 0 downloads

    If you only have sata drives then SAS plugin is unlikely to help.

     

    Have you tried installing 6.9.1?

    Link to comment
    Share on other sites
    14 hours ago, SimonF said:

    If you only have sata drives then SAS plugin is unlikely to help.

     

    Have you tried installing 6.9.1?

    "solved" :(

    Link to comment
    Share on other sites

    Same bug here. It's been a long time since first bug report. When the fix will be ready?

    Link to comment
    Share on other sites



    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.