LammeN3rd

Members
 View Profile  See their activity

  • Posts

    83

  • Joined

 Content Type 

Report Comments posted by LammeN3rd

    [6.9.2] & [6.10.0-rc5] Dell H730 Avago SAS based MegaRAID driver - Spin Up Performance Broken

    in Stable Releases

    Posted · Edited by LammeN3rd

    All drives are connected via a 26 port SAS expander backplane (8 ports to H330 and 18 for disks) 

    the system fully supports SAS but I only use SATA drives and have never had any issue with spindown (one of the main reasons I use unRAID

    without aggressive spin-down the average power usage is at least 50% higher

     

    I still run 6.9.2 (server is remote and until I have the iKVM connected again I don't dare to do remote upgrades :)

     

    P.S. the HW is a Dell Poweredge T630 so that should be extremely similar to your R530. All the firmware is u2date but I have been running this system for about 5 years and never had any of the issues you describe

     

     

    Unraid OS version 6.9.0-beta25 available

    in Prereleases

    Posted

    16 hours ago, limetech said:

    This is Settings/Disk Settings/Tunable (poll_attributes)

     

    This determines how often to issue 'smartctl' commands to the storage devices in order to read the temperatures.  The 'smartctl' program issues a couple special commands to a storage device to read the SMART data.  Typically with HDD's not only will this spin them up (if spun down) but will also flush and pause the I/O queue and send the r/w heads to the inner cylinder of the drive.  This is a pretty large disruption in I/O flow and if it happens too often can result in 'glitching' when reading a video stream for example.

     

    The default value of '1800' means 30 min between polls.  Probably you want to ask, "If a fan fails, how long before a drive burns up?" and set the poll_interval lower than that ;)

     

    You can set it really low, like to 10 sec, and watch your HDD activity LED's burst with activity every 10 sec as 'smartctl' does it's thing.

     

    Other notes:

    • If a drive is already spun-down when it's time to read it's temperature, we skip issuing 'smartctl' so as not to spin the drive up.
    • Whenever a HDD is spun-up, either via command or new I/O to the device, after the spin-up has completed, we'll use 'smartctl' to read the temperature.
    • Clicking on a device from the Main page will issue 'smartctl' in order to obtain and report the current SMART data for that device.  This will result in spinning up a spun-down HDD.
    • Even though 'smartctl' itself generates I/O to a drive, that I/O is not counted toward "activity" for purposes of spinning down the drive as a result of inactivity.

    please add this to the help notes in Unraid, when I started with Unraid I googled around for this info and having it in the help text will help a lot of new users :)

    • Like 1

    [6.8.0] log window shows auth screen in safari

    in Stable Releases

    Posted

    found a few more places with the same issue, these are all places I found:

    • opening log from top right corner
    • opening the log of an individual VM  
    • Settings --> VM Manager --> View Libvirt LOG
    • opening Console from a Docker (both from docker tab as well as Dashboard)

     

    The following places do not have the issue and work as normal:

    • opening Terminal from top right corner
    • opening a docker log from docker tab

     

    if I find any others I will update :)  

    • Thanks 1

    Unraid OS version 6.8.0-rc3 available

    in Prereleases

    Posted

    13 minutes ago, meep said:

    I note deprecation of AFP from 6.9.

    Is there any impact on maintaining TimeMachine volumes?

    Thanks

     

    nevermind, I found a rather testy exchange on the matter across in another thread.
     

    I guess I'll be doing my own research ;-(

     

     

     

    Before unRaid 6.7.x I used AFP but had a lot of issue's with the introduction of unRaid 6.7.x time-machine over SMB works flawless!

    • Like 1
    • Thanks 1

    Unraid OS version 6.7.0-rc8 available

    in Prereleases

    Posted

    6 hours ago, limetech said:

    The code is not in place to fix this yet, just the packages required for a fix.  I only have limited SAS h/w to test with and so far things not working correctly but I think it might be an issue with the enclosure I'm using.

    Do you need the SAS drives to be part of the array? I have some SAS drives laying around that I can add to my server they are just not part of the array (connected via an SAS expander to a Dell H330 SAS controller.)

    If this suffices for your test let me know and I will upgrade / run it tonight (EU time).