Kash76
-
Posts
108 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Kash76
-
-
On 1/28/2018 at 4:50 PM, killeriq said:
Did u upgrade from Docker - via NextCloud web UI?
I just wonder if i should upgrade like that ...or there is some new Docker version coming with latest Nextcould release?
Thanks
Manually like CHBMB said.
-
On 11/30/2017 at 7:00 AM, opticon said:
Thanks to thomast_88 for setting up this docker
I've set it up and muddled through learning git at the same time and just wanted to post a config I've came up with to let you use the "Linuxserver.io - letsencrypt" docker to reverse proxy the this (gitlab-ce) docker without having to use SSH etc to edit the gitlab.rb config file or any other suggestion I've seen here that involves a workaround of sorts like Gizmotoy's port workaround (although it did work).
##### How to use reverse proxy gitlab-ce with the letsencrypt docker
Summary:
I use the letsencrypt docker to reverse proxy my home stuff with each service being on it's own host.domain.com:443. I couldn't/didn't want to:
- NAT 80/443 or custom ports to this docker's built in nginx server so I could use it externally
- Not mess around with custom editing the standard docker config files
- I wanted all my URL's in gitlab-ce to show the proper https://host.domain.com/blah.git URL that I could just copy and paste them
* These steps assume you have a NAT for letsencrypt:nginx set up correctly to reverse proxy on HTTPS/443. Don't ask for help here regarding getting that set up, please ask in the thread for that docker hereSteps
1. Stop the docker
2. Reset your gitlab.rb file to docker/factory defaults
3. Add/Update your letsencrypt ngix config file area for gitlab-ce to use the following config and restart it.
proxy_pass http://your.unraid.ip.here:9080;
proxy_set_header X-Forwarded-Proto https;
proxy_set_header X-Forwarded-Ssl on;4. Edit the gitlab-ce docker, open advanced settings
5. Edit the 'Extra Parameters:' section and paste in the following;
--env GITLAB_OMNIBUS_CONFIG="external_url 'https://host.domain.com/'; nginx['listen_port'] = 9080; nginx['listen_https'] = false"
This is the standard config line included in the docker where your supposed to change the DNS name only. The line above changes http:// to https:// and passes config to the dockers built in nginx server to listen for https:// but not enable it's own SSL port and config.
Reference:
Supporting Proxied SSL
https://docs.gitlab.com/omnibus/settings/nginx.html#supporting-proxied-ssl
The reference link mention's about including a few more config items I already have them in the default letsencrypt nginx config so I didn't need to add them
@opticonThank you very much for sharing this. I've been struggling with the 'external_url' parameter for a while.
I did get this working but I intermittently get sent back to my internal IP:port address. Any ideas on how to solve this?
-
1
-
***update - apparently my upgrade did not go well. I copied all of the 12.0.5 files over my existing (the new signer certs were missing completely) and now I'm back in business.
I am suddenly getting a "too many redirects" error after login when visiting my instance. I recently upgraded to 12.05 and use LetsEncrypt as a reverse proxy. Any ideas as to what could cause this error?
I have the same issue when I disable overwrite.cli.url and overwrite host and access the domain locally without my external LetsEncrypt reverse proxy.
-
Darn
I already did just to make sure things haven't changed but Cox Cable blocks port 80.
Sent from my ONEPLUS A5010 using Tapatalk
-
I thought Comcast did as well but I set the port forwarding on 80 and it works for me. Try it.Wow, this sucks! Our ISP blocks port 80 so there is absolutely nothing I can do but wait and it's already been 3 days.
Sent from my ONEPLUS A5010 using Tapatalk
-
I would also like to thank the great people at Linuxserver.io for all of the goodies that that offer us!!!
-
Interesting - I ended up forwarding port 80 to 8008 (container http port) and it started working along with HTTPVAL (under Docker, LetsEncrypt, advanced settings to true).
I believe that Comcast blocks 80 but it's working.
-
There does not seem to be a clear path to a fix for those of us with port 80 blocked correct?
Sent from my ONEPLUS A5010 using Tapatalk -
Thanks. I'll assume the same if I bite on a 512, I'd get half or less because of the increase?You can but you'll only get an extra 64GB if using the default raid1.
Sent from my ONEPLUS A5010 using Tapatalk
-
Good evening everyone!
I have 2 x 275GB Crucial SSD drives for my cache pool and I'm running short on space. I have a 128GB sitting at my desk and am wondering if I can add it to the pool? I assume that I will not get the full 128GB but will it allocate maybe half of that?
Thanks for the guidance, I'd rather not have to purchase two new 512GB or larger.
-
Up and running, thanks!!
-
Thanks for setting this up! I'll check it out as we are considering this for a Slack alternative at work.
-
I have. I created my user account as an admin, updated the server, and I don't see a way to delete the admin user. I never can login as my additional user. Not sure what I'm still doing wrong.
Sent from my ONEPLUS A5000 using Tapatalk -
I am struggling with this container as it seems others are. I have local users created in the docker image by using 'docker exec -it openvpn-as adduser username', I set a password with 'docker exec -it openvpn-as passwd username', add the user as an admin, and I still cannot use any user except for admin. I have also commented out the line 'boot_pam_users'.
What am I missing?
-
I have not had this issue
Sent from my ONEPLUS A5000 using Tapatalk -
I have added this to extra parameters to help control the sprawl of log files
"--log-opt max-size=50m --log-opt max-file=1"
Sent from my ONEPLUS A5000 using Tapatalk-
1
-
1
-
-
Yes, thank you very much
Sent from my ONEPLUS A5000 using Tapatalk -
-
Trying to use a proxy for my connections out and I have found the "--ProxyConnection=10.0.0.xx:xxxx" argument but when I add it to the extra params line the container fails to start. Any ideas?
-
Perfect. Thanks!
Sent from my ONEPLUS A3000 using Tapatalk -
That's odd isn't it? How would I keep it upgraded other than updating the docker settings version by version?
Sent from my ONEPLUS A3000 using Tapatalk -
Hey guys, I want to try out the new live tv feature and I am a PlexPass owner. Can I use this docker to enable the PlexPass release? I've changed the dropdown in the Plex gui and it wants a manual install and I tried "-e VERSION=plexpass" in the parameters section 'stealing' from another docker parameter.
What am I missing. Thanks!
-
Thanks!
Sent from my ONEPLUS A3000 using Tapatalk -
Any chance that this image will be updated to 2.5?
Thanks!
Wondering if my disk is going bad or if this has to do with a recent power outage
in General Support
Posted
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