Kash76

Members
  • Posts

    106
  • Joined

  • Last visited

Posts posted by Kash76

  1. Simple question, why do you need to transcode? Can your clients not handle direct play? It may be far simpler to upgrade your client hardware than your server. That can enable direct play and eliminate the need for transcoding completely. But it depends on the circumstances.



    I use Roku units so I don’t have to transcode today. I think my concern lies in the 4K ATSC 3.0 capabilities that my new HD homerun has and not knowing if I can play those streams native.


    Sent from my iPhone using Tapatalk Pro
  2. Hey all, I'm looking to upgrade from my old AMD 8350 which has onboard video to a AMD 3900XT which does not have onboard video. I understand that only the Intel chips are currently supported for offloading video transcoding for things containers such as Plex.

     

    My questions

    1. Can I successfully transcode video for Plex using the 3900x?

    2. Are there any limitations to running headless or running something simple like this - https://www.microcenter.com/product/462020/visiontek-radeon-hd-5450-low-profile-passive-cooled-1gb-ddr3-pcie-21-graphics-card

    3. Is there any value to getting something like a 8GB RX 580?

     

    I run many dockers including NextCloud, Plex, and others. I only run a single Windows VM but not for gaming.

     

    Thanks for any help you can offer!

  3. 2 hours ago, Kash76 said:

    Thank you! Making progress, did that and am now getting "ERR_SSL_PROTOCOL_ERROR" in Chrome and "SSL_ERROR_RX_RECORD_TOO_LONG" in Firefox. I usually do not have issues like this but am having a hell of a time troubleshooting this.

     

    Nothing in my error log, access log has entries like this...

    
    10.x.x.x - - [27/Nov/2019:12:15:12 -0600] "\x16\x03\x01\x01.\x01\x00\x01*\x04\x03H\xC4z\xDE\x0B(\xF8\x9E-\x88\xD0l0\x8EC\xC9\x14\xBD\xC2\xD0\xFEq{\xE8\x07H\x9EX\xFDs\xF6D\x00\x00\x88\xC00\xC0,\xC0(\xC0$\xC0\x14\xC0" 400 157 "-" "-"

     

    Well this is embarrassing. I had the http and https ports for LetsEncrypt crossed. Thanks for the support and sorry for the bother!!

  4. 37 minutes ago, aptalca said:

    Turn off cloudflare proxy (click on the orange cloud)

    Thank you! Making progress, did that and am now getting "ERR_SSL_PROTOCOL_ERROR" in Chrome and "SSL_ERROR_RX_RECORD_TOO_LONG" in Firefox. I usually do not have issues like this but am having a hell of a time troubleshooting this.

     

    Nothing in my error log, access log has entries like this...

    10.x.x.x - - [27/Nov/2019:12:15:12 -0600] "\x16\x03\x01\x01.\x01\x00\x01*\x04\x03H\xC4z\xDE\x0B(\xF8\x9E-\x88\xD0l0\x8EC\xC9\x14\xBD\xC2\xD0\xFEq{\xE8\x07H\x9EX\xFDs\xF6D\x00\x00\x88\xC00\xC0,\xC0(\xC0$\xC0\x14\xC0" 400 157 "-" "-"

     

  5. 5 hours ago, saarg said:

    @Kash76
    You do not change the port in the proxy conf when using a custom bridge as letsencryptaand nextcloud are talking internally  and don't use the port forwards.

    Change it from 8000 back to 443.

    Thanks much for the response.  I changed it back to this and am still getting 522 errors on network and 523 off network

     

    server {
        listen 443 ssl;
        listen [::]:443 ssl;
    
        server_name cloud.*;
    
        include /config/nginx/ssl.conf;
    
        client_max_body_size 0;
    
        location / {
            include /config/nginx/proxy.conf;
            resolver 127.0.0.11 valid=30s;
            set $upstream_nextcloud nextcloud;
            proxy_max_temp_file_size 2048m;
            proxy_pass https://$upstream_nextcloud:443;
        }
    }

     

  6. Hey everyone, I had to change DNS configurations recently due to port 80 being blocked and I'm having a heck of a time since moving to Cloudflare and trying to use DNS authentication. I have tried many things and am getting 522 errors from Cloudflare and am hoping that you can help me.

     

    I most recently started over with the letsencrypt container, here is my configs....

     

    Log file output

    Variables set:
    PUID=99
    PGID=100
    TZ=America/Chicago
    URL=xxx.net
    SUBDOMAINS=cloud
    EXTRA_DOMAINS=
    ONLY_SUBDOMAINS=false
    DHLEVEL=2048
    VALIDATION=dns
    DNSPLUGIN=cloudflare
    EMAIL=support@xxx.com
    STAGING=
    
    2048 bit DH parameters present
    SUBDOMAINS entered, processing
    SUBDOMAINS entered, processing
    Sub-domains processed are: -d cloud.xxx.net
    E-mail address entered: support@xxx.com
    dns validation via cloudflare plugin is selected
    Certificate exists; parameters unchanged; starting nginx
    [cont-init.d] 50-config: exited 0.
    [cont-init.d] 99-custom-files: executing...
    [custom-init] no custom files found exiting...
    [cont-init.d] 99-custom-files: exited 0.
    [cont-init.d] done.
    [services.d] starting services
    [services.d] done.
    nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html)
    Server ready

     

    My Cloudflare.ini is set okay based on the cert being setup - skipping that

     

    Proxy config for nextcloud (also the name in my docker settings:

    
    server {
        listen 443 ssl;
        listen [::]:443 ssl;
    
        server_name cloud.*;
    
        include /config/nginx/ssl.conf;
    
        client_max_body_size 0;
    
        location / {
            include /config/nginx/proxy.conf;
            resolver 127.0.0.11 valid=30s;
            set $upstream_nextcloud nextcloud;
            proxy_max_temp_file_size 2048m;
            proxy_pass https://$upstream_nextcloud:8000;
        }
    }

     

    Nextcloud and Letsencrypt Docker configs are attached. Unraid web interface runs on another port so I do actually use 443 for Letsencrypt

     

    My Cloudflare settings are also attached. I'm not sure if my subdomains should be proxied or not and what my SSL setting should be.

     

    Thanks for any help you can offer!

     

     

    Annotation 2019-11-26 183616.png

    cf_list.png

    cf_ssl.png

     

     

    letsencrypt.png

  7. 4 hours ago, Pim Bliek said:

    I just installed this docker container and I have a little problem. I did change the parameter --env GITLAB_OMNIBUS_CONFIG="external_url 'http://192.168.178.15:9080/'" to reflect my situation. This works fine, for one exception (I have found so far).

    When you try to create a new milestone it tries to go to: http://unraid:9080/pim/pimbliek.nl/milestones/new  which is not reachable since that is not resolvable.

     

    How to make sure the 192.168.178.15 is used in the *whole* application?

    I've had the same issue and have not gotten past it. This makes for erratic behavior in the GUI.

  8. Thank you for the response. This is all I see when I click on the thumbs-down icon in the dashboard...

    It means the SSD reached the estimated life, it doesn't mean it's failing, it can work for a long time without issues, you can acknowledge the SMART attribute by clicking on the dashboard warning.
    16d774a19dc49aa1425692790c4a9114.jpg

    Sent from my ONEPLUS A6013 using Tapatalk

  9. Hey guys, I had an error show up on one of my cache drives (Crucial 275GB SSD) - percent lifetime remain (failing now) is 99. 

     

    There is a 'thumbs down' next to the drive in my dashboard. Do I replace the drive? If it's okay, how do I clear the error?

     

    Thanks!

     

    I do not see any errors reported in the SMART log. Here is what I see in the drive info...

     

    Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
    # 1  Vendor (0xff)       Completed without error       00%     17049         -
    # 2  Vendor (0xff)       Completed without error       00%     16971         -
    # 3  Vendor (0xff)       Completed without error       00%     16396         -
    # 4  Vendor (0xff)       Completed without error       00%     15846         -
    # 5  Vendor (0xff)       Completed without error       00%     15335         -
    # 6  Vendor (0xff)       Completed without error       00%     14859         -
    # 7  Vendor (0xff)       Completed without error       00%     14352         -
    # 8  Vendor (0xff)       Completed without error       00%     13846         -
    # 9  Vendor (0xff)       Completed without error       00%     13703         -
    #10  Vendor (0xff)       Completed without error       00%     13614         -
    #11  Vendor (0xff)       Completed without error       00%     13151         -
    #12  Vendor (0xff)       Completed without error       00%     12715         -
    #13  Vendor (0xff)       Completed without error       00%     12447         -
    #14  Vendor (0xff)       Completed without error       00%     12311         -
    #15  Vendor (0xff)       Completed without error       00%     11901         -
    #16  Vendor (0xff)       Completed without error       00%     11419         -
    #17  Vendor (0xff)       Completed without error       00%     10831         -
    #18  Vendor (0xff)       Completed without error       00%     10084         -
    #19  Vendor (0xff)       Completed without error       00%      9613         -
    #20  Vendor (0xff)       Completed without error       00%      9248         -
    #21  Vendor (0xff)       Completed without error       00%      8886         -

     

  10. On 10/2/2018 at 5:16 PM, TCosta29 said:

    Hello guys!
    I've been reading this thread in order to figure out how can I setup my GitLab Docker with my letsencrypt docker. 
     

    Right now my letsencrypt docker is like this

    
      location /gitlab {
                    include /config/nginx/proxy.conf;
                    proxy_pass http://192.168.1.104:9080;
                    proxy_set_header X-Forwarded-Proto https;
                    proxy_set_header X-Forwarded-Ssl on;
            }

    and my GitLab docker is like this :http://prntscr.com/l1gatc

    Extra Parameters:

    --env GITLAB_OMNIBUS_CONFIG="external_url 'https://"subdomain".duckdns.org/'; nginx['listen_port'] = 9080; nginx['listen_https'] = false"

     

    But for some reason, when I try to connect to my gitlab through  https://"subdomain".duckdns.org/gitlab it show's me 502 bad gateway error. 

     

    If someone could help me, I would be very gratefull 
    Also I'm still new to this unraid and docker stuff so please be patient with me. 

    Did you ever get this working?

  11.  
    This is the first docker i've installed thats restricting me from accessing its config and log files. If I change the permissions is the program going to freak out?
    It looks like all settings have a # in front, is this config file actually being used for anything?
    Those # lines are currently commented out. Take them away with the correct config and you should be set.

    Sent from my ONEPLUS A6003 using Tapatalk

  12. Advice is appreciated! I have 9,100 read errors on this disk...

     

    Thanks!

    smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.14.35-unRAID] (local build)
    Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org
    
    === START OF INFORMATION SECTION ===
    Model Family:     Western Digital Green
    Device Model:     WDC WD30EZRX-00DC0B0
    Serial Number:    WD-WMC1T1274820
    LU WWN Device Id: 5 0014ee 00378dbe0
    Firmware Version: 80.00A80
    User Capacity:    3,000,592,982,016 bytes [3.00 TB]
    Sector Sizes:     512 bytes logical, 4096 bytes physical
    Device is:        In smartctl database [for details use: -P show]
    ATA Version is:   ACS-2 (minor revision not indicated)
    SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
    Local Time is:    Sun Jun  3 12:04:19 2018 CDT
    SMART support is: Available - device has SMART capability.
    SMART support is: Enabled
    AAM feature is:   Unavailable
    APM feature is:   Unavailable
    Rd look-ahead is: Enabled
    Write cache is:   Enabled
    DSN feature is:   Unavailable
    ATA Security is:  Disabled, NOT FROZEN [SEC1]
    Wt Cache Reorder: 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:      ( 119)	The previous self-test completed having
    					the read element of the test failed.
    Total time to complete Offline 
    data collection: 		(41520) 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: 	 (   2) minutes.
    Extended self-test routine
    recommended polling time: 	 ( 417) minutes.
    Conveyance self-test routine
    recommended polling time: 	 (   5) minutes.
    SCT capabilities: 	       (0x70b5)	SCT Status supported.
    					SCT Feature Control supported.
    					SCT Data Table supported.
    
    SMART Attributes Data Structure revision number: 16
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
      1 Raw_Read_Error_Rate     POSR-K   200   200   051    -    1548
      3 Spin_Up_Time            POS--K   189   183   021    -    5516
      4 Start_Stop_Count        -O--CK   100   100   000    -    47
      5 Reallocated_Sector_Ct   PO--CK   200   200   140    -    0
      7 Seek_Error_Rate         -OSR-K   200   200   000    -    0
      9 Power_On_Hours          -O--CK   085   085   000    -    11531
     10 Spin_Retry_Count        -O--CK   100   253   000    -    0
     11 Calibration_Retry_Count -O--CK   100   253   000    -    0
     12 Power_Cycle_Count       -O--CK   100   100   000    -    45
    192 Power-Off_Retract_Count -O--CK   200   200   000    -    26
    193 Load_Cycle_Count        -O--CK   100   100   000    -    301196
    194 Temperature_Celsius     -O---K   125   105   000    -    25
    196 Reallocated_Event_Count -O--CK   200   200   000    -    0
    197 Current_Pending_Sector  -O--CK   200   200   000    -    0
    198 Offline_Uncorrectable   ----CK   200   200   000    -    0
    199 UDMA_CRC_Error_Count    -O--CK   200   200   000    -    0
    200 Multi_Zone_Error_Rate   ---R--   200   200   000    -    4
                                ||||||_ K auto-keep
                                |||||__ C event count
                                ||||___ R error rate
                                |||____ S speed/performance
                                ||_____ O updated online
                                |______ P prefailure warning
    
    General Purpose Log Directory Version 1
    SMART           Log Directory Version 1 [multi-sector log support]
    Address    Access  R/W   Size  Description
    0x00       GPL,SL  R/O      1  Log Directory
    0x01           SL  R/O      1  Summary SMART error log
    0x02           SL  R/O      5  Comprehensive SMART error log
    0x03       GPL     R/O      6  Ext. Comprehensive SMART error log
    0x06           SL  R/O      1  SMART self-test log
    0x07       GPL     R/O      1  Extended self-test log
    0x09           SL  R/W      1  Selective self-test log
    0x10       GPL     R/O      1  NCQ Command Error log
    0x11       GPL     R/O      1  SATA Phy Event Counters log
    0x80-0x9f  GPL,SL  R/W     16  Host vendor specific log
    0xa0-0xa7  GPL,SL  VS      16  Device vendor specific log
    0xa8-0xb7  GPL,SL  VS       1  Device vendor specific log
    0xbd       GPL,SL  VS       1  Device vendor specific log
    0xc0       GPL,SL  VS       1  Device vendor specific log
    0xc1       GPL     VS      93  Device vendor specific log
    0xe0       GPL,SL  R/W      1  SCT Command/Status
    0xe1       GPL,SL  R/W      1  SCT Data Transfer
    
    SMART Extended Comprehensive Error Log Version: 1 (6 sectors)
    Device Error Count: 489 (device log contains only the most recent 24 errors)
    	CR     = Command Register
    	FEATR  = Features Register
    	COUNT  = Count (was: Sector Count) Register
    	LBA_48 = Upper bytes of LBA High/Mid/Low Registers ]  ATA-8
    	LH     = LBA High (was: Cylinder High) Register    ]   LBA
    	LM     = LBA Mid (was: Cylinder Low) Register      ] Register
    	LL     = LBA Low (was: Sector Number) Register     ]
    	DV     = Device (was: Device/Head) Register
    	DC     = Device Control Register
    	ER     = Error register
    	ST     = Status register
    Powered_Up_Time is measured from power on, and printed as
    DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
    SS=sec, and sss=millisec. It "wraps" after 49.710 days.
    
    Error 489 [8] occurred at disk power-on lifetime: 11497 hours (479 days + 1 hours)
      When the command that caused the error occurred, the device was active or idle.
    
      After command completion occurred, registers were:
      ER -- ST COUNT  LBA_48  LH LM LL DV DC
      -- -- -- == -- == == == -- -- -- -- --
      40 -- 51 04 e8 00 00 8e 7e 6d 08 e0 00  Error: UNC 1256 sectors at LBA = 0x8e7e6d08 = 2390650120
    
      Commands leading to the command that caused the error were:
      CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
      -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
      25 00 00 04 e8 00 00 8e 7e 69 a8 e0 08     05:16:13.186  READ DMA EXT
      25 00 00 02 08 00 00 8e 7e 67 a0 e0 08     05:16:13.184  READ DMA EXT
      25 00 00 05 10 00 00 8e 7e 62 90 e0 08     05:16:13.178  READ DMA EXT
      25 00 00 02 08 00 00 8e 7e 60 88 e0 08     05:16:13.176  READ DMA EXT
      25 00 00 04 e8 00 00 8e 7e 5b a0 e0 08     05:16:13.170  READ DMA EXT
    
    Error 488 [7] occurred at disk power-on lifetime: 11497 hours (479 days + 1 hours)
      When the command that caused the error occurred, the device was active or idle.
    
      After command completion occurred, registers were:
      ER -- ST COUNT  LBA_48  LH LM LL DV DC
      -- -- -- == -- == == == -- -- -- -- --
      40 -- 51 05 40 00 00 8d f3 13 a8 e0 00  Error: UNC 1344 sectors at LBA = 0x8df313a8 = 2381517736
    
      Commands leading to the command that caused the error were:
      CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
      -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
      25 00 00 05 40 00 00 8d f3 0f f8 e0 08     05:15:23.435  READ DMA EXT
      25 00 00 02 80 00 00 8d f3 0d 78 e0 08     05:15:23.431  READ DMA EXT
      25 00 00 02 e0 00 00 8d f3 0a 98 e0 08     05:15:23.429  READ DMA EXT
      25 00 00 02 08 00 00 8d f3 08 90 e0 08     05:15:23.427  READ DMA EXT
      25 00 00 01 68 00 00 8d f3 07 28 e0 08     05:15:23.425  READ DMA EXT
    
    Error 487 [6] occurred at disk power-on lifetime: 11497 hours (479 days + 1 hours)
      When the command that caused the error occurred, the device was active or idle.
    
      After command completion occurred, registers were:
      ER -- ST COUNT  LBA_48  LH LM LL DV DC
      -- -- -- == -- == == == -- -- -- -- --
      40 -- 51 02 08 00 00 8d 65 54 b0 e0 00  Error: UNC 520 sectors at LBA = 0x8d6554b0 = 2372228272
    
      Commands leading to the command that caused the error were:
      CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
      -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
      25 00 00 02 08 00 00 8d 65 54 28 e0 08     05:14:29.735  READ DMA EXT
      25 00 00 04 d8 00 00 8d 65 4f 50 e0 08     05:14:29.731  READ DMA EXT
      25 00 00 02 08 00 00 8d 65 4d 48 e0 08     05:14:29.719  READ DMA EXT
      25 00 00 05 20 00 00 8d 65 48 28 e0 08     05:14:28.757  READ DMA EXT
      25 00 00 02 08 00 00 8d 65 46 20 e0 08     05:14:28.755  READ DMA EXT
    
    Error 486 [5] occurred at disk power-on lifetime: 11497 hours (479 days + 1 hours)
      When the command that caused the error occurred, the device was active or idle.
    
      After command completion occurred, registers were:
      ER -- ST COUNT  LBA_48  LH LM LL DV DC
      -- -- -- == -- == == == -- -- -- -- --
      40 -- 51 05 40 00 00 8d 3f f7 68 e0 00  Error: UNC 1344 sectors at LBA = 0x8d3ff768 = 2369779560
    
      Commands leading to the command that caused the error were:
      CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
      -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
      25 00 00 05 40 00 00 8d 3f f4 e8 e0 08     05:14:05.349  READ DMA EXT
      25 00 00 02 10 00 00 8d 3f f2 d8 e0 08     05:14:05.337  READ DMA EXT
      25 00 00 05 40 00 00 8d 3f ed 98 e0 08     05:14:05.275  READ DMA EXT
      25 00 00 01 b0 00 00 8d 3f eb e8 e0 08     05:14:05.209  READ DMA EXT
      25 00 00 05 40 00 00 8d 3f e6 a8 e0 08     05:14:05.155  READ DMA EXT
    
    Error 485 [4] occurred at disk power-on lifetime: 11497 hours (479 days + 1 hours)
      When the command that caused the error occurred, the device was active or idle.
    
      After command completion occurred, registers were:
      ER -- ST COUNT  LBA_48  LH LM LL DV DC
      -- -- -- == -- == == == -- -- -- -- --
      40 -- 51 05 40 00 00 8d 3f cd b8 e0 00  Error: UNC 1344 sectors at LBA = 0x8d3fcdb8 = 2369768888
    
      Commands leading to the command that caused the error were:
      CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
      -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
      25 00 00 05 40 00 00 8d 3f c8 88 e0 08     05:13:57.365  READ DMA EXT
      25 00 00 02 58 00 00 8d 3f c6 30 e0 08     05:13:57.363  READ DMA EXT
      25 00 00 05 40 00 00 8d 3f c0 f0 e0 08     05:13:57.305  READ DMA EXT
      35 00 00 01 60 00 00 8d 3f b8 c0 e0 08     05:13:57.300  WRITE DMA EXT
      25 00 00 04 c8 00 00 8d 3f bc 28 e0 08     05:13:57.286  READ DMA EXT
    
    Error 484 [3] occurred at disk power-on lifetime: 11497 hours (479 days + 1 hours)
      When the command that caused the error occurred, the device was active or idle.
    
      After command completion occurred, registers were:
      ER -- ST COUNT  LBA_48  LH LM LL DV DC
      -- -- -- == -- == == == -- -- -- -- --
      40 -- 51 05 30 00 00 8d 3f b8 c0 e0 00  Error: UNC 1328 sectors at LBA = 0x8d3fb8c0 = 2369763520
    
      Commands leading to the command that caused the error were:
      CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
      -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
      25 00 00 05 30 00 00 8d 3f b4 f0 e0 08     05:13:54.314  READ DMA EXT
      25 00 00 02 08 00 00 8d 3f b2 e8 e0 08     05:13:54.312  READ DMA EXT
      25 00 00 01 70 00 00 8d 3f b1 78 e0 08     05:13:54.311  READ DMA EXT
      25 00 00 05 40 00 00 8d 3f ac 38 e0 08     05:13:54.305  READ DMA EXT
      25 00 00 00 10 00 00 8d 3f ac 28 e0 08     05:13:54.305  READ DMA EXT
    
    Error 483 [2] occurred at disk power-on lifetime: 11497 hours (479 days + 1 hours)
      When the command that caused the error occurred, the device was active or idle.
    
      After command completion occurred, registers were:
      ER -- ST COUNT  LBA_48  LH LM LL DV DC
      -- -- -- == -- == == == -- -- -- -- --
      40 -- 51 02 08 00 00 8d 3e 9a 40 e0 00  Error: UNC 520 sectors at LBA = 0x8d3e9a40 = 2369690176
    
      Commands leading to the command that caused the error were:
      CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
      -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
      25 00 00 02 08 00 00 8d 3e 98 e0 e0 08     05:13:50.191  READ DMA EXT
      25 00 00 02 f8 00 00 8d 3e 95 e8 e0 08     05:13:50.177  READ DMA EXT
      25 00 00 02 00 00 00 8d 3e 93 e8 e0 08     05:13:50.176  READ DMA EXT
      25 00 00 02 08 00 00 8d 3e 91 e0 e0 08     05:13:50.175  READ DMA EXT
      25 00 00 02 80 00 00 8d 3e 8f 60 e0 08     05:13:50.168  READ DMA EXT
    
    Error 482 [1] occurred at disk power-on lifetime: 11497 hours (479 days + 1 hours)
      When the command that caused the error occurred, the device was active or idle.
    
      After command completion occurred, registers were:
      ER -- ST COUNT  LBA_48  LH LM LL DV DC
      -- -- -- == -- == == == -- -- -- -- --
      40 -- 51 02 88 00 00 8d 3e 70 48 e0 00  Error: UNC 648 sectors at LBA = 0x8d3e7048 = 2369679432
    
      Commands leading to the command that caused the error were:
      CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
      -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
      25 00 00 02 88 00 00 8d 3e 6f 38 e0 08     05:13:46.868  READ DMA EXT
      25 00 00 02 00 00 00 8d 3e 6d 38 e0 08     05:13:46.867  READ DMA EXT
      25 00 00 02 08 00 00 8d 3e 6b 30 e0 08     05:13:46.866  READ DMA EXT
      25 00 00 03 70 00 00 8d 3e 67 c0 e0 08     05:13:46.863  READ DMA EXT
      25 00 00 02 00 00 00 8d 3e 65 c0 e0 08     05:13:46.862  READ DMA EXT
    
    SMART Extended Self-test Log Version: 1 (1 sectors)
    Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
    # 1  Extended offline    Completed: read failure       70%     11517         1483616232
    # 2  Short offline       Completed without error       00%     11515         -
    # 3  Extended offline    Completed without error       00%      1756         -
    # 4  Short offline       Completed without error       00%      1748         -
    
    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.
    
    SCT Status Version:                  3
    SCT Version (vendor specific):       258 (0x0102)
    SCT Support Level:                   1
    Device State:                        Active (0)
    Current Temperature:                    25 Celsius
    Power Cycle Min/Max Temperature:     20/27 Celsius
    Lifetime    Min/Max Temperature:     18/45 Celsius
    Under/Over Temperature Limit Count:   0/0
    Vendor specific:
    01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    
    SCT Temperature History Version:     2
    Temperature Sampling Period:         1 minute
    Temperature Logging Interval:        1 minute
    Min/Max recommended Temperature:      0/60 Celsius
    Min/Max Temperature Limit:           -41/85 Celsius
    Temperature History Size (Index):    478 (233)
    
    Index    Estimated Time   Temperature Celsius
     234    2018-06-03 04:07    25  ******
     ...    ..( 20 skipped).    ..  ******
     255    2018-06-03 04:28    25  ******
     256    2018-06-03 04:29    24  *****
     ...    ..( 35 skipped).    ..  *****
     292    2018-06-03 05:05    24  *****
     293    2018-06-03 05:06    25  ******
     ...    ..(  5 skipped).    ..  ******
     299    2018-06-03 05:12    25  ******
     300    2018-06-03 05:13    24  *****
     ...    ..(  2 skipped).    ..  *****
     303    2018-06-03 05:16    24  *****
     304    2018-06-03 05:17    25  ******
     ...    ..(  5 skipped).    ..  ******
     310    2018-06-03 05:23    25  ******
     311    2018-06-03 05:24    24  *****
     ...    ..( 84 skipped).    ..  *****
     396    2018-06-03 06:49    24  *****
     397    2018-06-03 06:50    25  ******
     ...    ..(  5 skipped).    ..  ******
     403    2018-06-03 06:56    25  ******
     404    2018-06-03 06:57    24  *****
     ...    ..( 24 skipped).    ..  *****
     429    2018-06-03 07:22    24  *****
     430    2018-06-03 07:23    25  ******
     ...    ..(  6 skipped).    ..  ******
     437    2018-06-03 07:30    25  ******
     438    2018-06-03 07:31    24  *****
     ...    ..(  4 skipped).    ..  *****
     443    2018-06-03 07:36    24  *****
     444    2018-06-03 07:37    25  ******
     445    2018-06-03 07:38    24  *****
     ...    ..( 23 skipped).    ..  *****
     469    2018-06-03 08:02    24  *****
     470    2018-06-03 08:03    25  ******
     471    2018-06-03 08:04    24  *****
     ...    ..(  3 skipped).    ..  *****
     475    2018-06-03 08:08    24  *****
     476    2018-06-03 08:09    25  ******
     477    2018-06-03 08:10    24  *****
       0    2018-06-03 08:11    24  *****
       1    2018-06-03 08:12    24  *****
       2    2018-06-03 08:13    25  ******
       3    2018-06-03 08:14    25  ******
       4    2018-06-03 08:15    24  *****
     ...    ..(  3 skipped).    ..  *****
       8    2018-06-03 08:19    24  *****
       9    2018-06-03 08:20    25  ******
     ...    ..(  5 skipped).    ..  ******
      15    2018-06-03 08:26    25  ******
      16    2018-06-03 08:27    24  *****
     ...    ..(  2 skipped).    ..  *****
      19    2018-06-03 08:30    24  *****
      20    2018-06-03 08:31    25  ******
      21    2018-06-03 08:32    24  *****
      22    2018-06-03 08:33    24  *****
      23    2018-06-03 08:34    25  ******
     ...    ..(  2 skipped).    ..  ******
      26    2018-06-03 08:37    25  ******
      27    2018-06-03 08:38    24  *****
     ...    ..(  2 skipped).    ..  *****
      30    2018-06-03 08:41    24  *****
      31    2018-06-03 08:42    25  ******
     ...    ..(  9 skipped).    ..  ******
      41    2018-06-03 08:52    25  ******
      42    2018-06-03 08:53    24  *****
      43    2018-06-03 08:54    25  ******
     ...    ..(  9 skipped).    ..  ******
      53    2018-06-03 09:04    25  ******
      54    2018-06-03 09:05    24  *****
      55    2018-06-03 09:06    24  *****
      56    2018-06-03 09:07    24  *****
      57    2018-06-03 09:08    25  ******
     ...    ..(  3 skipped).    ..  ******
      61    2018-06-03 09:12    25  ******
      62    2018-06-03 09:13    24  *****
      63    2018-06-03 09:14    24  *****
      64    2018-06-03 09:15    24  *****
      65    2018-06-03 09:16    25  ******
     ...    ..(  4 skipped).    ..  ******
      70    2018-06-03 09:21    25  ******
      71    2018-06-03 09:22    24  *****
      72    2018-06-03 09:23    24  *****
      73    2018-06-03 09:24    25  ******
     ...    ..( 11 skipped).    ..  ******
      85    2018-06-03 09:36    25  ******
      86    2018-06-03 09:37    24  *****
      87    2018-06-03 09:38    25  ******
     ...    ..(  8 skipped).    ..  ******
      96    2018-06-03 09:47    25  ******
      97    2018-06-03 09:48    24  *****
      98    2018-06-03 09:49    25  ******
     ...    ..(  7 skipped).    ..  ******
     106    2018-06-03 09:57    25  ******
     107    2018-06-03 09:58    24  *****
     108    2018-06-03 09:59    24  *****
     109    2018-06-03 10:00    24  *****
     110    2018-06-03 10:01    25  ******
     ...    ..(  8 skipped).    ..  ******
     119    2018-06-03 10:10    25  ******
     120    2018-06-03 10:11    24  *****
     121    2018-06-03 10:12    25  ******
     ...    ..(  7 skipped).    ..  ******
     129    2018-06-03 10:20    25  ******
     130    2018-06-03 10:21    24  *****
     131    2018-06-03 10:22    24  *****
     132    2018-06-03 10:23    24  *****
     133    2018-06-03 10:24    25  ******
     ...    ..(  5 skipped).    ..  ******
     139    2018-06-03 10:30    25  ******
     140    2018-06-03 10:31    24  *****
     ...    ..( 15 skipped).    ..  *****
     156    2018-06-03 10:47    24  *****
     157    2018-06-03 10:48    25  ******
     158    2018-06-03 10:49    25  ******
     159    2018-06-03 10:50    25  ******
     160    2018-06-03 10:51    24  *****
     ...    ..( 14 skipped).    ..  *****
     175    2018-06-03 11:06    24  *****
     176    2018-06-03 11:07    25  ******
     177    2018-06-03 11:08    25  ******
     178    2018-06-03 11:09    24  *****
     179    2018-06-03 11:10    25  ******
     180    2018-06-03 11:11    25  ******
     181    2018-06-03 11:12    25  ******
     182    2018-06-03 11:13    24  *****
     ...    ..(  4 skipped).    ..  *****
     187    2018-06-03 11:18    24  *****
     188    2018-06-03 11:19    25  ******
     ...    ..(  5 skipped).    ..  ******
     194    2018-06-03 11:25    25  ******
     195    2018-06-03 11:26    24  *****
     ...    ..(  2 skipped).    ..  *****
     198    2018-06-03 11:29    24  *****
     199    2018-06-03 11:30    25  ******
     ...    ..(  6 skipped).    ..  ******
     206    2018-06-03 11:37    25  ******
     207    2018-06-03 11:38    24  *****
     208    2018-06-03 11:39    24  *****
     209    2018-06-03 11:40    24  *****
     210    2018-06-03 11:41    25  ******
     ...    ..( 22 skipped).    ..  ******
     233    2018-06-03 12:04    25  ******
    
    SCT Error Recovery Control command not supported
    
    Device Statistics (GP/SMART Log 0x04) not supported
    
    Pending Defects log (GP Log 0x0c) not supported
    
    SATA Phy Event Counters (GP Log 0x11)
    ID      Size     Value  Description
    0x0001  2            0  Command failed due to ICRC error
    0x0002  2            0  R_ERR response for data FIS
    0x0003  2            0  R_ERR response for device-to-host data FIS
    0x0004  2            0  R_ERR response for host-to-device data FIS
    0x0005  2            0  R_ERR response for non-data FIS
    0x0006  2            0  R_ERR response for device-to-host non-data FIS
    0x0007  2            0  R_ERR response for host-to-device non-data FIS
    0x0008  2            0  Device-to-host non-data FIS retries
    0x0009  2            4  Transition from drive PhyRdy to drive PhyNRdy
    0x000a  2            3  Device-to-host register FISes sent due to a COMRESET
    0x000b  2            0  CRC errors within host-to-device FIS
    0x000f  2            0  R_ERR response for host-to-device data FIS, CRC
    0x0012  2            0  R_ERR response for host-to-device non-data FIS, CRC
    0x8000  4       140697  Vendor specific