csimmons222

Awhile back I had a power outage that caused an unclean shutdown. Upon coming back online, UNRAID performed a parity check and 17701 errors. I re-ran the parity check and it found the same number of errors again. How do go about resolving this problem? Thanks in advance for the help! sim-unraid-01-diagnostics-20221213-1907.zip

Thanks!

I have a share called TV Shows. Unraid has an orange triangle next to the share. When hovering over the icon, it states that some or all files are unprotected. Doing some quick digging around in the forums, this may be caused by some files still existing on the cache drive. I looked in the cache drive and there is a folder on their called Tv Shows. When looking inside the TV Shows directory on the cache drive, there are no files. How can I go about deleting the TV Shows folder off of the cache drive and to get rid of this "unprotected" warning?

I started messing with settings last night trying and now I cannot connect to Emby via HTTPs. For the life of me, I cannot figure out what is wrong. Within the Emby Server both my local and public https port is listed at 8920. I have tried to access the server using https://<internal ip>:8920 using the Edge browser and I receive the following error: "Hmmm...can't reach this page. It looks like <internal ip> closed the connection" I have tried to access the server using https://media.mydomain.com:8920 using the Edge browser and I receive the following error: "Forbidden. You don't have permission to access / on this server." I have tried to telnet to the server on port 8920 and it tells me that the connection failed. Everything noted above works just fine on HTTP. Any ideas?

I would greatly appreciate it if someone could help this noob out. I am using NZBGetVPN and I am using slickvpn as my service. Within the container, I have entered the following: Container Variable: VPN_USER: <My VPN Username> Container Variable: VPN_PASS: <My VPN Password> Container Variable: VPN_REMOTE: gw1.zrh2.slickvpn.com Container Variable: VPN_PORT: 443 Container Variable: VPN_PROV: custom Container Variable: VPN_PROTOCOL: udp Container Variable: LAN_NETWORK: 10.1.0.0/24 Also within the Appdata/NZBGetVPN directory, I have created another directory named "openvpn". Within that file, I placed the openvpn file provided by my slickvpn and renamed it ovpn.ovpn. If I leave the VPN off in the settings then I can access the NZBGet user interface without any problems. However, if I enable the VPN in the container settings, the NZBGet application shows as started in the Docker menu but I am unable to access the NZBGet user interface via the browser. Any thoughts what I could possibly be doing wrong?

I had a 5 TB drive fail so I replaced it with an 8 TB WD Red drive. I started the rebuild process and went to bed as it was going to take about 24 hours to complete. Got home from work the next day and decided to see if it was finished yet or not. However, I cannot access the web gui. The server is still running and I can see the command prompt on the screen. This was a few days ago and I figured I would just let it go to ensure that there was enough time for the rebuild to complete. Should I simply reboot the server? Note: I cannot ping the server either using the IP address. Everything else on my network seems to be working fine with no other issues.

Thanks, I wasn't sure about the raw value of raw read error rate or the seek error rate.

I upgraded my parity drive to a new 5 TB drive. I decided to ran a preclear on my old parity drive before adding to the array as a data disk. Here are my preclear reports. Is the drive safe to use as a data disk? Disk: /dev/sdc smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.1.13-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Desktop HDD.15 Device Model: ST4000DM000-1F2168 Serial Number: S300PY2F LU WWN Device Id: 5 000c50 074bdce53 Firmware Version: CC54 User Capacity: 4,000,787,030,016 bytes [4.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5900 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Sun Dec 27 05:03:27 2015 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 107) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 502) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x1085) SCT Status supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 119 099 006 Pre-fail Always - 216037104 3 Spin_Up_Time 0x0003 093 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 099 099 020 Old_age Always - 1094 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 071 060 030 Pre-fail Always - 13768820 9 Power_On_Hours 0x0032 091 091 000 Old_age Always - 8643 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 45 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 0 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 065 056 045 Old_age Always - 35 (Min/Max 21/39) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 29 193 Load_Cycle_Count 0x0032 097 097 000 Old_age Always - 6520 194 Temperature_Celsius 0x0022 035 044 000 Old_age Always - 35 (0 14 0 0 0) 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 2272h+42m+32.977s 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 105257985103 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 112398477869 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 8613 - 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. ========================================================================1.15b == invoked as: /boot/config/plugins/preclear.disk/preclear_disk.sh -c 1 -f -J /dev/sdc == ST4000DM000-1F2168 S300PY2F == Disk /dev/sdc has been successfully precleared == with a starting sector of 1 == Ran 1 cycle == == Using :Read block size = 1000448 Bytes == Last Cycle's Pre Read Time : 10:44:47 (103 MB/s) == Last Cycle's Zeroing time : 8:02:03 (138 MB/s) == Last Cycle's Post Read Time : 10:45:42 (103 MB/s) == Last Cycle's Total Time : 29:33:33 == == Total Elapsed Time 29:33:33 == == Disk Start Temperature: 23C == == Current Disk Temperature: 35C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdc /tmp/smart_finish_sdc ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 119 118 6 ok 216037104 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 65 76 45 near_thresh 35 Temperature_Celsius = 35 24 0 ok 35 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================

Opps....I didn't realize that I was in the wrong area! Thanks for the advice!

I just purchased two 5 TB Toshiba drives for my server. One will be used as a data drive and the other as the parity drive since the current parity drive is only 4 TB. Here is what I have done so far: 1. Ran preclear twice on both 5 TB drives. 2. Performed a parity check on the existing array. My next step is to stop the array and take a backup of the config directory of my USB stick. Because I'm OCD, I like to have my parity drive as the first drive in my Norco 24 disc case. Is it okay to shut down the server, remove my old parity drive from its slot and place the 5 TB drive in the #1 spot? I would then be placing the "old" parity drive in the next available data drive slot in my case. From the directions I read, I should not format the unformatted old parity disk or write to the array while the new parity disk is being created. Am I better off removing the old parity disk from the array altogether during the new parity disk build....then run a preclear on it and add it as a data disk afterward? On a side note....if I reboot the server, I won't "lose" the preclear information on the two 5 TB disks will I? This info is saved to the disk so that they can be quickly added to the array regardless if the server has been shutdown or not, correct? I am on version 6.1.6

Thanks, I restarted the server and was able to access the preclear option.

I just completed a preclear on a new disk using this plugin. However, I want to run the preclear for a second time on the same disk using the plugin. How to I go about doing so? When I go to Unassigned Devices, it shows the disk and that the preclear was successful. I see no option to run the preclear again.

Thank you!

Disk: /dev/sdk smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.17.4-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.14 (AF) Device Model: ST3000DM001-9YN166 Serial Number: S1F06DXL LU WWN Device Id: 5 000c50 04a38c0b7 Firmware Version: CC4C User Capacity: 3,000,592,982,016 bytes [3.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Sat Apr 4 11:41:54 2015 EDT ==> WARNING: A firmware update for this drive is available, see the following Seagate web pages: http://knowledge.seagate.com/articles/en_US/FAQ/207931en http://knowledge.seagate.com/articles/en_US/FAQ/223651en SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED See vendor-specific Attribute list for marginal Attributes. General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 575) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 341) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x3085) SCT Status supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 119 082 006 Pre-fail Always - 209617240 3 Spin_Up_Time 0x0003 092 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 216 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 936 7 Seek_Error_Rate 0x000f 070 060 030 Pre-fail Always - 12207268 9 Power_On_Hours 0x0032 072 072 000 Old_age Always - 24957 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 93 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 923 188 Command_Timeout 0x0032 100 099 000 Old_age Always - 2 2 2 189 High_Fly_Writes 0x003a 092 092 000 Old_age Always - 8 190 Airflow_Temperature_Cel 0x0022 064 034 045 Old_age Always In_the_past 36 (1 22 42 23 0) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 88 193 Load_Cycle_Count 0x0032 084 084 000 Old_age Always - 32890 194 Temperature_Celsius 0x0022 036 066 000 Old_age Always - 36 (0 15 0 0 0) 197 Current_Pending_Sector 0x0012 100 058 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 058 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 12610h+05m+43.191s 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 50906821544257 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 50071252329690 SMART Error Log Version: 1 ATA Error Count: 778 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] 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 778 occurred at disk power-on lifetime: 24905 hours (1037 days + 17 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 ff ff ff 4f 00 4d+09:07:51.252 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+09:07:51.251 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+09:07:51.142 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+09:07:51.133 READ FPDMA QUEUED e5 00 00 00 00 00 00 00 4d+09:07:51.090 CHECK POWER MODE Error 777 occurred at disk power-on lifetime: 24905 hours (1037 days + 17 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 ff ff ff 4f 00 4d+09:07:45.078 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+09:07:44.380 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+09:07:44.242 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+09:07:44.043 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+09:07:44.042 READ FPDMA QUEUED Error 776 occurred at disk power-on lifetime: 24905 hours (1037 days + 17 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 ff ff ff 4f 00 4d+09:06:25.482 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+09:06:25.318 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+09:06:25.024 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+09:06:24.950 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+09:06:24.784 READ FPDMA QUEUED Error 775 occurred at disk power-on lifetime: 24905 hours (1037 days + 17 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 ff ff ff 4f 00 4d+09:06:09.616 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+09:06:05.354 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+09:06:03.818 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+09:06:03.807 READ FPDMA QUEUED e5 00 00 00 00 00 00 00 4d+09:06:03.806 CHECK POWER MODE Error 774 occurred at disk power-on lifetime: 24905 hours (1037 days + 17 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 ff ff ff 4f 00 4d+09:05:45.802 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+09:05:45.791 READ FPDMA QUEUED e5 00 00 00 00 00 00 00 4d+09:05:45.791 CHECK POWER MODE 60 00 00 ff ff ff 4f 00 4d+09:05:45.783 READ FPDMA QUEUED b0 da 00 00 4f c2 00 00 4d+09:05:45.770 SMART RETURN STATUS SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] 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. Thanks in advance!

Here are my logs from the other disk: Disk: /dev/sdk smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.17.4-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.14 (AF) Device Model: ST3000DM001-9YN166 Serial Number: S1F06DXL LU WWN Device Id: 5 000c50 04a38c0b7 Firmware Version: CC4C User Capacity: 3,000,592,982,016 bytes [3.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Fri Apr 3 11:16:34 2015 EDT ==> WARNING: A firmware update for this drive is available, see the following Seagate web pages: http://knowledge.seagate.com/articles/en_US/FAQ/207931en http://knowledge.seagate.com/articles/en_US/FAQ/223651en SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED See vendor-specific Attribute list for marginal Attributes. General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 575) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 341) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x3085) SCT Status supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 117 082 006 Pre-fail Always - 145369120 3 Spin_Up_Time 0x0003 092 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 216 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 896 7 Seek_Error_Rate 0x000f 070 060 030 Pre-fail Always - 11969193 9 Power_On_Hours 0x0032 072 072 000 Old_age Always - 24933 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 93 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 923 188 Command_Timeout 0x0032 100 099 000 Old_age Always - 2 2 2 189 High_Fly_Writes 0x003a 092 092 000 Old_age Always - 8 190 Airflow_Temperature_Cel 0x0022 067 034 045 Old_age Always In_the_past 33 (1 22 40 23 0) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 88 193 Load_Cycle_Count 0x0032 084 084 000 Old_age Always - 32890 194 Temperature_Celsius 0x0022 033 066 000 Old_age Always - 33 (0 15 0 0 0) 197 Current_Pending_Sector 0x0012 100 058 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 058 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 12585h+40m+08.035s 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 50269617233804 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 49362153686802 SMART Error Log Version: 1 ATA Error Count: 778 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] 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 778 occurred at disk power-on lifetime: 24905 hours (1037 days + 17 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 ff ff ff 4f 00 4d+09:07:51.252 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+09:07:51.251 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+09:07:51.142 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+09:07:51.133 READ FPDMA QUEUED e5 00 00 00 00 00 00 00 4d+09:07:51.090 CHECK POWER MODE Error 777 occurred at disk power-on lifetime: 24905 hours (1037 days + 17 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 ff ff ff 4f 00 4d+09:07:45.078 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+09:07:44.380 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+09:07:44.242 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+09:07:44.043 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+09:07:44.042 READ FPDMA QUEUED Error 776 occurred at disk power-on lifetime: 24905 hours (1037 days + 17 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 ff ff ff 4f 00 4d+09:06:25.482 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+09:06:25.318 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+09:06:25.024 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+09:06:24.950 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+09:06:24.784 READ FPDMA QUEUED Error 775 occurred at disk power-on lifetime: 24905 hours (1037 days + 17 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 ff ff ff 4f 00 4d+09:06:09.616 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+09:06:05.354 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+09:06:03.818 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+09:06:03.807 READ FPDMA QUEUED e5 00 00 00 00 00 00 00 4d+09:06:03.806 CHECK POWER MODE Error 774 occurred at disk power-on lifetime: 24905 hours (1037 days + 17 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 ff ff ff 4f 00 4d+09:05:45.802 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+09:05:45.791 READ FPDMA QUEUED e5 00 00 00 00 00 00 00 4d+09:05:45.791 CHECK POWER MODE 60 00 00 ff ff ff 4f 00 4d+09:05:45.783 READ FPDMA QUEUED b0 da 00 00 4f c2 00 00 4d+09:05:45.770 SMART RETURN STATUS SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] 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. ========================================================================1.15 == invoked as: ./preclear_disk.sh -r 65536 -w 65536 -b 2000 -A /dev/sdk == ST3000DM001-9YN166 S1F06DXL == Disk /dev/sdk has been successfully precleared == with a starting sector of 1 == Ran 1 cycle == == Using :Read block size = 65536 Bytes == Last Cycle's Pre Read Time : 6:46:48 (122 MB/s) == Last Cycle's Zeroing time : 5:19:24 (156 MB/s) == Last Cycle's Post Read Time : 12:18:08 (67 MB/s) == Last Cycle's Total Time : 24:25:20 == == Total Elapsed Time 24:25:20 == == Disk Start Temperature: 33C == == Current Disk Temperature: 36C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdk /tmp/smart_finish_sdk ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 119 117 6 ok 209617240 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Reported_Uncorrect = 1 1 0 near_thresh 923 Airflow_Temperature_Cel = 64 67 45 In_the_past 36 Temperature_Celsius = 36 33 0 ok 36 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 896 sectors had been re-allocated before the start of the preclear. 936 sectors are re-allocated at the end of the preclear, a change of 40 in the number of sectors re-allocated. ============================================================================