MvL

Members
  • Posts

    593
  • Joined

  • Last visited

Posts posted by MvL

  1. On 5/10/2018 at 12:29 AM, saarg said:

     

    You shouldn't need to do anything normally as time is set the same as unraid as default. What is your docker run command. 

     

    It seems it's solved now. I did some investigation but found no glues. The reboot solved the issue. Thanks!

  2. To be sure I restarted my unRAID server and checked the bios. The time that the bios displayed was good. After everything booted I checked the time in unRAID OS. That was now also good. I checked all Docker containers and all container from unRAID developers are also in sync. Only the official Plex docker container is 2 hours behind. I'm moving to the Linuxserver.io Plex Docker. I had issue with that container but it seems it's resolved. So everything is then okay. Not sure what caused the time issues...

  3. I have a weird issue on my server. Last week the time on the server was 2 hours behind local time and now it's 2 hours ahead of local time. My local time is one hour ahead of GMT. How can I solve this issue?

  4. I my opinion multiply protected arrays is a great feature. Also multiply cache drives is a great feature, and maybe we need a separate ssd for storage of system, app data, domains, iso's. So many cool feature all take time to develop, and yeah what are the priorities.... I think for everyone they are different. 

  5. I think the idea is not bad. You can add chassis with a expander backplane (has a power supply and power board) to a existing server. So add for example a 9207-8e to you existing sever and connect the backplane expander chassis with a SFF-8088 cable. Boom you have 48 drives!

  6. So you can use the drives for 3 - 4 years.

     

    If your happy with your SDD's then it's okay! :)

     

    The Sandisks uses TLC memory cells. They are cheaper as the Samsung Pro's but that uses MLC memory cells. If I'm correct MLC memory cells can do more writes. So I have to figure out to go for a cheaper TLC model or a Expensive MLC model...

  7. I want to request a Docker app of Jaikoz. 

     

    http://www.jthink.net/jaikoz/

     

    Quote

    Are you frustrated by missing information in your audio files? This is known as metadata and is stored in a Tag. The Jaikoz Audio Tag Editor is a powerful yet simple to use tool that allows you to organize, edit and correct thousands of these tags with ease.

    Jaikoz uses MusicBrainz, an online database of over eleven million songs and Discogs another database of over 4 million releases. Many of the songs also have an Acoustic Id provided by Acoustid, allowing a song to be identified by the actual music, so it can do a match even if you have no metadata! These feature means that Jaikoz gives you the flexibility to lookup your songs by both the acoustic id and the metadata making Jaikoz a very accurate tool. But no identification system is 100% accurate so we have made it as quick and easy as possible to edit your data manually as well using a convenient spreadsheet view, with many autoformatting features.

    The current release supports tagging of Mp4, M4a, M4p, Mp3, Wma, Flac, Aiff, Wav, Dsf and Ogg files. The latest release is Jaikoz 9.3.0, this was released on October 17th 2017

     

  8. Device Statistics (GP Log 0x04)
    Page  Offset Size        Value Flags Description
    0x01  =====  =               =  ===  == General Statistics (rev 2) ==
    0x01  0x008  4              31  ---  Lifetime Power-On Resets
    0x01  0x018  6   3123168738799  ---  Logical Sectors Written !!!!!!!!!!!!!!!!!!!!!!
    0x01  0x020  6       976967253  ---  Number of Write Commands
    0x01  0x028  6    953863139911  ---  Logical Sectors Read
    0x01  0x030  6       265474636  ---  Number of Read Commands
    0x07  =====  =               =  ===  == Solid State Device Statistics (rev 1) ==
    0x07  0x008  1              47  ---  Percentage Used Endurance Indicator !!!!!!!!!!!!!!!!!!!!!!
                                    |||_ C monitored condition met
                                    ||__ D supports DSN
                                    |___ N normalized value

    Missed that part. Interesting!

  9. SMART Attributes Data Structure revision number: 4
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
      5 Reallocated_Sector_Ct   -O--CK   100   100   ---    -    0
      9 Power_On_Hours          -O--CK   253   100   ---    -    19292
     12 Power_Cycle_Count       -O--CK   100   100   ---    -    31
    165 Total_Write/Erase_Count -O--CK   100   100   ---    -    4321327194145
    166 Min_W/E_Cycle           -O--CK   100   100   ---    -    293
    167 Min_Bad_Block/Die       -O--CK   100   100   ---    -    20
    168 Maximum_Erase_Cycle     -O--CK   100   100   ---    -    382
    169 Total_Bad_Block         -O--CK   100   100   ---    -    0
    171 Program_Fail_Count      -O--CK   100   100   ---    -    0
    172 Erase_Fail_Count        -O--CK   100   100   ---    -    0
    173 Avg_Write/Erase_Count   -O--CK   100   100   ---    -    334
    174 Unexpect_Power_Loss_Ct  -O--CK   100   100   ---    -    11
    187 Reported_Uncorrect      -O--CK   100   100   ---    -    0
    194 Temperature_Celsius     -O---K   049   055   ---    -    51 (Min/Max 11/55)
    199 SATA_CRC_Error          -O--CK   100   100   ---    -    0
    230 Perc_Write/Erase_Count  -O--CK   100   100   ---    -    14595092066119
    232 Perc_Avail_Resrvd_Space PO--CK   100   100   004    -    100
    233 Total_NAND_Writes_GiB   -O--CK   100   100   ---    -    310422
    234 Perc_Write/Erase_Ct_BC  -O--CK   100   100   ---    -    348690
    241 Total_Writes_GiB        ----CK   253   253   ---    -    138826
    242 Total_Reads_GiB         ----CK   253   253   ---    -    57432
    244 Thermal_Throttle        -O--CK   000   100   ---    -    0
                                ||||||_ K auto-keep
                                |||||__ C event count
                                ||||___ R error rate
                                |||____ S speed/performance
                                ||_____ O updated online
                                |______ P prefailure warning

     

    19292 hours on that is more as 800 days. So 2 years and 2 months used.

    0 reallocated sectors nice!

    138826GiB writes  that is 138TB ?

     

    btw this SSD has TLC memory.

  10. 4 hours ago, trurl said:

     

    You might reconsider how you use cache. There is no requirement to cache user share writes. Most of the writes to my server are unattended - scheduled backups or queued downloads - and I am not waiting for them to complete anyway. So those user shares aren't cached, don't use up space on cache, don't have to be moved later, and are immediately protected by parity.

     

     

    1 hour ago, Tybio said:

    The problem with direct writes (for /me/) is that it causes disks to spin up a lot.  In the evening during the TV season I'll get 2-5+ episodes a night, spinning up the drives in a staggered way for each one is pointless when I can cache them and then move them at once.

     

    For the Movies share, it would make sense to do that as those tend to be larger and less frequent additions.

     

    ie: it is a balance, usage management combined with cache size :).

     

    Yeah, good one! Maybe it's better to just cache the tv shows and not the movies or other stuff. Then I'll can use it a little longer. At the moment I'll rather prefer to spend my money on a new rack (open or closed) then a couple of SSD's. Then I'll can buy the SSD's 3 -6 months later...

  11. 2 hours ago, trurl said:

     

    You might reconsider how you use cache. There is no requirement to cache user share writes. Most of the writes to my server are unattended - scheduled backups or queued downloads - and I am not waiting for them to complete anyway. So those user shares aren't cached, don't use up space on cache, don't have to be moved later, and are immediately protected by parity.

     

     

    Yeah, true. Only it's still not enough. If I have a couple of season of a tv show and a UHD rip the SSD is full.

     

    1 hour ago, doubleohwhatever said:

    Sure. I've attached two of them. I *think* these are the two oldest drives.

    SanDisk_SDSSDHII960G_151740411432-20180507-0825.txt

    SanDisk_SDSSDHII960G_151855401818-20180507-0823.txt

     

    Thanks. I'll check them!

  12. Quote

    I have had zero problems with them and they haven't been used lightly. My cache array runs eleven dockers and two VMs. One VM is a security camera server. 16 4k cameras are writing to the cache array 24/7 (not motion triggered but 16 24/7 4k h.265 streams). On top of that the cache drive is still used for storage array writes (mover runs nightly). They also survived a 140F temps when a fan failed.

     

     

    Interesting! 

     

    Can you post the S.M.A.R.T values of the SSD?

  13. Quote
    • The context menu for a running docker container now includes a function to open a terminal window for the container console, very handy.
    • You can rearrange the start order of containers by dragging the rows up and down.

     

    Not sure if this allowed in this thread but I want to say that are two cool features you guys added! Thank you. Looking forward when stable comes out.