HDT
-
Posts
53 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by HDT
-
-
8 minutes ago, Squid said:
The above still applies - Within same share, the file stays on the same disk. Different shares the destination will follow the use cache rules on the destination. Using a rootshare file stays on the same disk
Thank you sir!
-
1 minute ago, Squid said:
Depends on what you mean by "move" and how you're moving them.
If you're moving them between shares, and the destination share is use cache yes / prefer then it will wind up on the cache pool
If you're moving within the same share, then the move is instantaneous and the file will stay on the exact same hard drive as the source.
If you're using a so-called "rootshare", then the file will also always stay on the same drive.
I'm using this Windows 10 app to perform automated reorganizing:
https://www.howtogeek.com/howto/19707/quickly-copy-movie-files-to-individually-named-folders/ -
I need to reorganize some files and folders in my primary array.
The total amount of data that I need to move is way larger than my cache pool.
If I move the files in Windows 10, will UNRAID consider those as "new" files and move them into the cache pool?
If so, then I'm thinking that I might have to temporarily disable my cache pool. Would that be the best practice way to do this?
I have to move the files in Windows 10, not using UNRAID.
I am using a Windows 10 app to move "orphaned" movie files (.mkv, .srt, etc) into their own folders.
Thank you!
-
On 6/13/2022 at 7:30 AM, Meannekes said:
i bought that exact model and it fu**ed up 2 of my drives.
First i wasnt able to stop the array and then the whole Server was inaccesable.
After some investigation on that Card, i saw that the cooler was touching some resistors because the thermalpad was too small and the Black paint was already scrached up..
Those generic cards are hit or miss. The one I got from Amazon caused a CRC error on one of my drives.
Get the LSI one or a clone.
Info:
I sprung for the LSI brand one and probably wasted money because NEC or IBM are probably just as good. I'll just skip drinking beer for a month to make up the difference.
-
On 6/13/2022 at 1:28 PM, minority said:
The 9207’s have been working flawlessly, though a bit power hungry vs the ASMs.
How much power were the 9207's using in comparison to the ASM's?
-
5 hours ago, trurl said:
Also builtin Midnight Commander textGUI file manager (mc at command line).
However you do it, DON'T mix disks and user shares when moving or copying.
won't allow you to make that mistake.
I'll use Dynamix and not risk anything.
Thank you!
-
I am running a parity check and UNRAID randomly pauses the activity randomly. It did it a second time just now.
Why would UNRAID do this?
I do have PARITY CHECK TUNING set up but the schedule doesn't even start until the first week of next month. I'm doing a manual check before I swap SATA cards.
It's been pausing randomly for 2 days now.
-
3 minutes ago, trurl said:
Dynamix File Explorer plugin is best way, requires at least Unraid 6.10
What about Krusader?
SpaceInvaders from YT says he likes to use that -
On 10/25/2018 at 1:42 PM, itimpi said:
UnRAID never moves files between array disks automatically, this always has to be done manually if you want it to happen.
Thank you. How would we move the files?
Is it as simple as using a file explorer?
-
22 hours ago, alturismo said:
Find out what the oldest files are and remove them until it hits the 50% in-use threshold. <- somehow covered, "only move older ..."
Respectfully, this doesn't cover it. There can be situations where all of the files are less than 7 days old but fills more than 50% of storage.
This situation will occur more often the higher the age threshold is set. For example, if the age threshold is set to 30 days or older = move off the cache pool ...then, there will be a much higher chance that many of the files are still under 30 days old but using more than 50% of storage.
This is where some kind of sort by age would be useful and use that list to move off the oldest files.
-
3 hours ago, alturismo said:
look for mover tuning, plugin almost all covered already
They told me this feature wasn't implemented yet?
-
FEATURE REQUEST:
It would be nice if MOVER TUNING could:
- Always make sure that 50% of the cache pool storage is in use.
- Find out what the oldest files are and remove them until it hits the 50% in-use threshold.
- Repeat daily.
- This way, all the newest files can have quick access from the cache pool.
-
What is the proper way to keep the most recent files backed up in the array and in the cache pool?
This is what I tried but it is not having the result that I was expecting:
-
Use cache pool (for new files/directories): = PREFER
-
Use CA Mover Tuning plugin settings:
-
Only move at this threshold of used cache space: = 50%
-
Move files off cache based on age? = YES
-
Move files that are greater than this many days old: = 7
-
Use CTIME: = YES
-
Everything else is set to NO
-
Ideally, it would be nice if MOVER could:
- Always make sure that 50% of the cache pool storage is in use.
- Find out what the oldest files are and remove them until it hits the 50% in-use threshold.
- Repeat daily.
- This way, all the newest files can have quick access from the cache pool.
Is this possible?
-
-
Is there a way for MOVER to move files by oldest first until x % of space is free?
Not by age, like any file over 9 days old, but by moving the oldest file first out of all the files in the cache pool until the cache pool has x % of space free.
-
1
-
-
On 6/27/2015 at 10:17 AM, jeffreywhunter said:
click on the Log from the WebGUi
Does anyone where this button is in the most up to date GUI?
-
35 minutes ago, JorgeB said:
Note that since the extended SMART test failed you still have a disk problem, you can try another full disk write, it might remap the sectors, it won't on a read.
Okay, I'm going to retire the drive.
Thanks for all your help, you guys have the BEST SUPPORT in the industry!
-
30 minutes ago, dlandon said:
The post read verification failed. This could be due to bad memory. You should run a memory test.
The SMART report also reports that the drive has overheated in the past. This may have caused the errors.
Run the memory test and fix any issues there. Then if you really want to use the disk, run another preclear.
If you are on Unraid 6.9 or greater, remove the preclear disk plugin and install the UD Preclear plugin. It's an updated preclear.
Will do! Thank you sir!
-
7 hours ago, ChatNoir said:
The temperature is not a problem, however other SMART attribues are.
Jun 08 22:42:16 preclear_disk_X348T61A_4640: S.M.A.R.T.: Reported_Uncorrect 0 3 Up 3 Jun 08 22:42:16 preclear_disk_X348T61A_4640: S.M.A.R.T.: Current_Pending_Sector 0 8 Up 8 Jun 08 22:42:16 preclear_disk_X348T61A_4640: S.M.A.R.T.: Offline_Uncorrectable 0 8 Up 8
You can try to run an Extended SMART test on the drive (make sure that spin down it turned OFF for the drive). However, I am not sure that it would clear those.
Oh no! Do you think this drive is bad and I cannot use it?
Extended self test failed at 10%
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-5.15.43-Unraid] (local build) Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Archive HDD (SMR) Device Model: ST8000AS0002-1NA17Z Serial Number: X348T61A LU WWN Device Id: 5 000c50 0a27f6c8a Firmware Version: RT18 User Capacity: 8,001,563,222,016 bytes [8.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5980 rpm Device is: In smartctl database 7.3/5387 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: Thu Jun 9 06:35:53 2022 PDT 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 See vendor-specific Attribute list for marginal Attributes. 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: ( 121) The previous self-test completed having the read element of the test failed. Total time to complete Offline data collection: ( 0) 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 951) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x30b5) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-- 116 086 006 - 222342091 3 Spin_Up_Time PO---- 090 090 000 - 0 4 Start_Stop_Count -O--CK 089 089 020 - 11421 5 Reallocated_Sector_Ct PO--CK 100 100 010 - 0 7 Seek_Error_Rate POSR-- 069 060 030 - 64590058685 9 Power_On_Hours -O--CK 055 055 000 - 39465 10 Spin_Retry_Count PO--C- 100 100 097 - 0 12 Power_Cycle_Count -O--CK 097 097 020 - 3430 183 Runtime_Bad_Block -O--CK 100 100 000 - 0 184 End-to-End_Error -O--CK 100 100 099 - 0 187 Reported_Uncorrect -O--CK 097 097 000 - 3 188 Command_Timeout -O--CK 100 096 000 - 90195951648 189 High_Fly_Writes -O-RCK 100 100 000 - 0 190 Airflow_Temperature_Cel -O---K 070 030 045 Past 30 (255 255 30 25 0) 191 G-Sense_Error_Rate -O--CK 100 100 000 - 0 192 Power-Off_Retract_Count -O--CK 001 001 000 - 601050 193 Load_Cycle_Count -O--CK 001 001 000 - 622279 194 Temperature_Celsius -O---K 030 070 000 - 30 (0 9 0 0 0) 195 Hardware_ECC_Recovered -O-RC- 119 099 000 - 222342091 197 Current_Pending_Sector -O--C- 100 100 000 - 8 198 Offline_Uncorrectable ----C- 100 100 000 - 8 199 UDMA_CRC_Error_Count -OSRCK 200 200 000 - 0 240 Head_Flying_Hours ------ 100 253 000 - 12443 (227 29 0) 241 Total_LBAs_Written ------ 100 253 000 - 57249371118 242 Total_LBAs_Read ------ 100 253 000 - 358304724855 ||||||_ 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 5 Ext. Comprehensive SMART error log 0x04 GPL,SL R/O 8 Device Statistics log 0x06 SL R/O 1 SMART self-test log 0x07 GPL R/O 1 Extended self-test log 0x08 GPL R/O 8 Power Conditions 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 0x21 GPL R/O 8 Write stream error log 0x22 GPL R/O 8 Read stream error log 0x24 GPL R/O 512 Current Device Internal Status Data log 0x30 GPL,SL R/O 9 IDENTIFY DEVICE data log 0x80-0x9f GPL,SL R/W 16 Host vendor specific log 0xa1 GPL,SL VS 24 Device vendor specific log 0xa2 GPL VS 8160 Device vendor specific log 0xa8-0xa9 GPL,SL VS 136 Device vendor specific log 0xab GPL VS 1 Device vendor specific log 0xb0 GPL VS 9048 Device vendor specific log 0xbe-0xbf GPL VS 65528 Device vendor specific log 0xc0 GPL,SL VS 1 Device vendor specific log 0xc1 GPL,SL VS 16 Device vendor specific log 0xd1 GPL VS 80 Device vendor specific log 0xd3 GPL VS 1920 Device vendor specific log 0xda GPL,SL VS 8 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 (5 sectors) Device Error Count: 3 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 3 [2] occurred at disk power-on lifetime: 39464 hours (1644 days + 8 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 -- 53 00 00 00 02 9c f0 3a b8 00 00 Error: UNC at LBA = 0x29cf03ab8 = 11222923960 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 -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 00 00 08 00 02 9c f0 3a b8 40 00 2d+00:45:04.890 READ FPDMA QUEUED ef 00 10 00 02 00 00 00 00 00 00 a0 00 2d+00:45:04.889 SET FEATURES [Enable SATA feature] 27 00 00 00 00 00 00 00 00 00 00 e0 00 2d+00:45:04.889 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 00 00 00 00 00 a0 00 2d+00:45:04.888 IDENTIFY DEVICE ef 00 03 00 46 00 00 00 00 00 00 a0 00 2d+00:45:04.888 SET FEATURES [Set transfer mode] Error 2 [1] occurred at disk power-on lifetime: 39464 hours (1644 days + 8 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 -- 53 00 00 00 02 9c f0 3a b8 00 00 Error: UNC at LBA = 0x29cf03ab8 = 11222923960 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 -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 00 00 08 00 02 9c f0 3a b8 40 00 2d+00:45:02.105 READ FPDMA QUEUED 60 00 00 00 08 00 02 9c f0 3a b0 40 00 2d+00:45:02.105 READ FPDMA QUEUED 60 00 00 00 08 00 02 9c f0 3a a8 40 00 2d+00:45:02.105 READ FPDMA QUEUED 60 00 00 00 08 00 02 9c f0 3a a0 40 00 2d+00:45:02.105 READ FPDMA QUEUED 60 00 00 00 08 00 02 9c f0 3a 98 40 00 2d+00:45:02.104 READ FPDMA QUEUED Error 1 [0] occurred at disk power-on lifetime: 39464 hours (1644 days + 8 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 -- 53 00 00 00 02 9c f0 3a b8 00 00 Error: UNC at LBA = 0x29cf03ab8 = 11222923960 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 -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 00 05 40 00 02 9c f0 44 00 40 00 2d+00:44:59.223 READ FPDMA QUEUED 60 00 00 04 c0 00 02 9c f0 3f 40 40 00 2d+00:44:59.223 READ FPDMA QUEUED 60 00 00 05 40 00 02 9c f0 3a 00 40 00 2d+00:44:59.223 READ FPDMA QUEUED b0 00 d0 00 01 00 00 00 c2 4f 00 00 00 2d+00:44:59.031 SMART READ DATA 60 00 00 00 c0 00 02 9c f0 39 40 40 00 2d+00:44:58.975 READ FPDMA QUEUED 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 90% 39465 11222923960 # 2 Extended offline Completed: read failure 90% 39465 11222923960 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): 522 (0x020a) Device State: Active (0) Current Temperature: 30 Celsius Power Cycle Min/Max Temperature: 25/30 Celsius Lifetime Min/Max Temperature: 9/70 Celsius Under/Over Temperature Limit Count: 0/0 SCT Temperature History Version: 2 Temperature Sampling Period: 3 minutes Temperature Logging Interval: 59 minutes Min/Max recommended Temperature: 14/55 Celsius Min/Max Temperature Limit: 10/60 Celsius Temperature History Size (Index): 128 (80) Index Estimated Time Temperature Celsius 81 2022-06-04 01:15 26 ******* 82 2022-06-04 02:14 ? - 83 2022-06-04 03:13 25 ****** 84 2022-06-04 04:12 ? - 85 2022-06-04 05:11 24 ***** 86 2022-06-04 06:10 ? - 87 2022-06-04 07:09 25 ****** 88 2022-06-04 08:08 ? - 89 2022-06-04 09:07 24 ***** 90 2022-06-04 10:06 ? - 91 2022-06-04 11:05 26 ******* 92 2022-06-04 12:04 ? - 93 2022-06-04 13:03 28 ********* 94 2022-06-04 14:02 ? - 95 2022-06-04 15:01 29 ********** 96 2022-06-04 16:00 ? - 97 2022-06-04 16:59 27 ******** 98 2022-06-04 17:58 ? - 99 2022-06-04 18:57 29 ********** 100 2022-06-04 19:56 ? - 101 2022-06-04 20:55 29 ********** 102 2022-06-04 21:54 ? - 103 2022-06-04 22:53 25 ****** 104 2022-06-04 23:52 ? - 105 2022-06-05 00:51 24 ***** 106 2022-06-05 01:50 ? - 107 2022-06-05 02:49 26 ******* 108 2022-06-05 03:48 ? - 109 2022-06-05 04:47 25 ****** 110 2022-06-05 05:46 ? - 111 2022-06-05 06:45 26 ******* 112 2022-06-05 07:44 ? - 113 2022-06-05 08:43 29 ********** 114 2022-06-05 09:42 ? - 115 2022-06-05 10:41 24 ***** 116 2022-06-05 11:40 ? - 117 2022-06-05 12:39 20 * 118 2022-06-05 13:38 ? - 119 2022-06-05 14:37 21 ** 120 2022-06-05 15:36 ? - 121 2022-06-05 16:35 26 ******* 122 2022-06-05 17:34 ? - 123 2022-06-05 18:33 28 ********* 124 2022-06-05 19:32 ? - 125 2022-06-05 20:31 29 ********** 126 2022-06-05 21:30 ? - 127 2022-06-05 22:29 30 *********** 0 2022-06-05 23:28 ? - 1 2022-06-06 00:27 27 ******** 2 2022-06-06 01:26 ? - 3 2022-06-06 02:25 25 ****** 4 2022-06-06 03:24 ? - 5 2022-06-06 04:23 26 ******* 6 2022-06-06 05:22 ? - 7 2022-06-06 06:21 27 ******** 8 2022-06-06 07:20 ? - 9 2022-06-06 08:19 27 ******** 10 2022-06-06 09:18 ? - 11 2022-06-06 10:17 28 ********* 12 2022-06-06 11:16 ? - 13 2022-06-06 12:15 25 ****** 14 2022-06-06 13:14 ? - 15 2022-06-06 14:13 30 *********** 16 2022-06-06 15:12 ? - 17 2022-06-06 16:11 31 ************ 18 2022-06-06 17:10 ? - 19 2022-06-06 18:09 24 ***** 20 2022-06-06 19:08 ? - 21 2022-06-06 20:07 26 ******* 22 2022-06-06 21:06 ? - 23 2022-06-06 22:05 30 *********** 24 2022-06-06 23:04 ? - 25 2022-06-07 00:03 31 ************ 26 2022-06-07 01:02 ? - 27 2022-06-07 02:01 29 ********** 28 2022-06-07 03:00 ? - 29 2022-06-07 03:59 31 ************ 30 2022-06-07 04:58 33 ************** 31 2022-06-07 05:57 33 ************** 32 2022-06-07 06:56 32 ************* 33 2022-06-07 07:55 33 ************** 34 2022-06-07 08:54 32 ************* ... ..( 2 skipped). .. ************* 37 2022-06-07 11:51 32 ************* 38 2022-06-07 12:50 31 ************ 39 2022-06-07 13:49 33 ************** ... ..( 4 skipped). .. ************** 44 2022-06-07 18:44 33 ************** 45 2022-06-07 19:43 34 *************** 46 2022-06-07 20:42 34 *************** 47 2022-06-07 21:41 35 **************** 48 2022-06-07 22:40 33 ************** 49 2022-06-07 23:39 33 ************** 50 2022-06-08 00:38 35 **************** 51 2022-06-08 01:37 34 *************** 52 2022-06-08 02:36 34 *************** 53 2022-06-08 03:35 33 ************** 54 2022-06-08 04:34 35 **************** 55 2022-06-08 05:33 35 **************** 56 2022-06-08 06:32 33 ************** 57 2022-06-08 07:31 34 *************** 58 2022-06-08 08:30 33 ************** 59 2022-06-08 09:29 33 ************** 60 2022-06-08 10:28 33 ************** 61 2022-06-08 11:27 32 ************* ... ..( 2 skipped). .. ************* 64 2022-06-08 14:24 32 ************* 65 2022-06-08 15:23 33 ************** ... ..( 2 skipped). .. ************** 68 2022-06-08 18:20 33 ************** 69 2022-06-08 19:19 34 *************** 70 2022-06-08 20:18 35 **************** 71 2022-06-08 21:17 35 **************** 72 2022-06-08 22:16 35 **************** 73 2022-06-08 23:15 34 *************** 74 2022-06-09 00:14 34 *************** 75 2022-06-09 01:13 34 *************** 76 2022-06-09 02:12 33 ************** 77 2022-06-09 03:11 34 *************** 78 2022-06-09 04:10 34 *************** 79 2022-06-09 05:09 ? - 80 2022-06-09 06:08 25 ****** SCT Error Recovery Control command not supported Device Statistics (GP Log 0x04) Page Offset Size Value Flags Description 0x01 ===== = = === == General Statistics (rev 1) == 0x01 0x008 4 3430 --- Lifetime Power-On Resets 0x01 0x010 4 39465 --- Power-on Hours 0x01 0x018 6 57249240798 --- Logical Sectors Written 0x01 0x020 6 54570980 --- Number of Write Commands 0x01 0x028 6 358300732244 --- Logical Sectors Read 0x01 0x030 6 602424975 --- Number of Read Commands 0x01 0x038 6 - --- Date and Time TimeStamp 0x03 ===== = = === == Rotating Media Statistics (rev 1) == 0x03 0x008 4 643119272 N-- Spindle Motor Power-on Hours 0x03 0x010 4 643100623 N-- Head Flying Hours 0x03 0x018 4 622279 --- Head Load Events 0x03 0x020 4 0 --- Number of Reallocated Logical Sectors 0x03 0x028 4 2 --- Read Recovery Attempts 0x03 0x030 4 0 --- Number of Mechanical Start Failures 0x04 ===== = = === == General Errors Statistics (rev 1) == 0x04 0x008 4 129 --- Number of Reported Uncorrectable Errors 0x04 0x010 4 32 --- Resets Between Cmd Acceptance and Completion 0x05 ===== = = === == Temperature Statistics (rev 1) == 0x05 0x008 1 30 N-- Current Temperature 0x05 0x010 1 33 N-- Average Short Term Temperature 0x05 0x018 1 33 N-- Average Long Term Temperature 0x05 0x020 1 70 N-- Highest Temperature 0x05 0x028 1 9 N-- Lowest Temperature 0x05 0x030 1 68 N-- Highest Average Short Term Temperature 0x05 0x038 1 1 N-- Lowest Average Short Term Temperature 0x05 0x040 1 65 N-- Highest Average Long Term Temperature 0x05 0x048 1 0 N-- Lowest Average Long Term Temperature 0x05 0x050 4 34523 --- Time in Over-Temperature 0x05 0x058 1 55 --- Specified Maximum Operating Temperature 0x05 0x060 4 0 --- Time in Under-Temperature 0x05 0x068 1 13 --- Specified Minimum Operating Temperature |||_ C monitored condition met ||__ D supports DSN |___ N normalized value Pending Defects log (GP Log 0x0c) not supported SATA Phy Event Counters (GP Log 0x11) ID Size Value Description 0x000a 2 2 Device-to-host register FISes sent due to a COMRESET 0x0001 2 0 Command failed due to ICRC error 0x0003 2 0 R_ERR response for device-to-host data FIS 0x0004 2 0 R_ERR response for host-to-device 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 -
I precleared one of my drives that I'm planned to add to my array and it was stopped due to an error.
Can someone please help me understand this error log?
Jun 07 07:22:15 preclear_disk_X348T61A_4640: Preclear Disk Version: 1.0.25 Jun 07 07:22:16 preclear_disk_X348T61A_4640: Disk size: 8001563222016 Jun 07 07:22:16 preclear_disk_X348T61A_4640: Disk blocks: 1953506646 Jun 07 07:22:16 preclear_disk_X348T61A_4640: Blocks (512 bytes): 15628053168 Jun 07 07:22:16 preclear_disk_X348T61A_4640: Block size: 4096 Jun 07 07:22:16 preclear_disk_X348T61A_4640: Start sector: 0 Jun 07 07:22:19 preclear_disk_X348T61A_4640: Pre-read: pre-read verification started (1/5) ... Jun 07 07:33:19 preclear_disk_X348T61A_4640: Pause requested Jun 07 07:33:19 preclear_disk_X348T61A_4640: Paused Jun 07 07:35:46 preclear_disk_X348T61A_4640: Resumed Jun 07 10:18:42 preclear_disk_X348T61A_4640: Pre-Read: progress - 25% read @ 188 MB/s Jun 07 13:30:15 preclear_disk_X348T61A_4640: Pre-Read: progress - 50% read @ 152 MB/s Jun 07 17:15:33 preclear_disk_X348T61A_4640: Pre-Read: progress - 75% read @ 130 MB/s Jun 07 22:12:34 preclear_disk_X348T61A_4640: Pre-Read: elapsed time - 14:47:45 Jun 07 22:12:34 preclear_disk_X348T61A_4640: Pre-read: pre-read verification completed! Jun 07 22:12:34 preclear_disk_X348T61A_4640: Zeroing: zeroing the disk started (1/5) ... Jun 07 22:12:34 preclear_disk_X348T61A_4640: Zeroing: emptying the MBR. Jun 08 01:09:13 preclear_disk_X348T61A_4640: Zeroing: progress - 25% zeroed @ 179 MB/s Jun 08 04:23:59 preclear_disk_X348T61A_4640: Zeroing: progress - 50% zeroed @ 151 MB/s Jun 08 08:12:28 preclear_disk_X348T61A_4640: Zeroing: progress - 75% zeroed @ 133 MB/s Jun 08 13:13:17 preclear_disk_X348T61A_4640: Zeroing: progress - 100% zeroed @ 24 MB/s Jun 08 13:13:17 preclear_disk_X348T61A_4640: Pause (smartctl run time: 26s) Jun 08 13:13:17 preclear_disk_X348T61A_4640: /usr/local/emhttp/plugins/unassigned.devices.preclear/scripts/preclear_disk.sh: line 910: kill: (562) - No such process Jun 08 13:13:18 preclear_disk_X348T61A_4640: Paused Jun 08 13:13:20 preclear_disk_X348T61A_4640: Zeroing: zeroing the disk completed! Jun 08 13:13:20 preclear_disk_X348T61A_4640: Signature: writing signature... Jun 08 13:13:22 preclear_disk_X348T61A_4640: Signature: verifying Unraid's signature on the MBR ... Jun 08 13:13:22 preclear_disk_X348T61A_4640: Signature: Unraid preclear signature is valid! Jun 08 13:13:23 preclear_disk_X348T61A_4640: Post-Read: post-read verification started (1/5) ... Jun 08 13:13:23 preclear_disk_X348T61A_4640: Post-Read: verifying the beginning of the disk. Jun 08 13:13:24 preclear_disk_X348T61A_4640: Post-Read: verifying the rest of the disk. Jun 08 16:10:15 preclear_disk_X348T61A_4640: Post-Read: progress - 25% verified @ 180 MB/s Jun 08 19:24:59 preclear_disk_X348T61A_4640: Post-Read: progress - 50% verified @ 146 MB/s Jun 08 22:42:13 preclear_disk_X348T61A_4640: Post-Read: elapsed time - 9:28:47 Jun 08 22:42:13 preclear_disk_X348T61A_4640: Post-Read: dd command failed, exit code [1]. Jun 08 22:42:13 preclear_disk_X348T61A_4640: Post-Read: dd output: 2734276+0 records out Jun 08 22:42:13 preclear_disk_X348T61A_4640: Post-Read: dd output: 5734192381952 bytes (5.7 TB, 5.2 TiB) copied, 34010.8 s, 169 MB/s Jun 08 22:42:13 preclear_disk_X348T61A_4640: Post-Read: dd output: 2735062+0 records in Jun 08 22:42:13 preclear_disk_X348T61A_4640: Post-Read: dd output: 2735061+0 records out Jun 08 22:42:13 preclear_disk_X348T61A_4640: Post-Read: dd output: 5735838646272 bytes (5.7 TB, 5.2 TiB) copied, 34023.6 s, 169 MB/s Jun 08 22:42:14 preclear_disk_X348T61A_4640: Post-Read: dd output: 2735840+0 records in Jun 08 22:42:14 preclear_disk_X348T61A_4640: Post-Read: dd output: 2735839+0 records out Jun 08 22:42:14 preclear_disk_X348T61A_4640: Post-Read: dd output: 5737470230528 bytes (5.7 TB, 5.2 TiB) copied, 34035.4 s, 169 MB/s Jun 08 22:42:14 preclear_disk_X348T61A_4640: Post-Read: dd output: 2736554+0 records in Jun 08 22:42:14 preclear_disk_X348T61A_4640: Post-Read: dd output: 2736553+0 records out Jun 08 22:42:14 preclear_disk_X348T61A_4640: Post-Read: dd output: 5738967597056 bytes (5.7 TB, 5.2 TiB) copied, 34047.2 s, 169 MB/s Jun 08 22:42:14 preclear_disk_X348T61A_4640: Post-Read: dd output: 2737401+0 records in Jun 08 22:42:14 preclear_disk_X348T61A_4640: Post-Read: dd output: 2737400+0 records out Jun 08 22:42:14 preclear_disk_X348T61A_4640: Post-Read: dd output: 5740743884800 bytes (5.7 TB, 5.2 TiB) copied, 34060 s, 169 MB/s Jun 08 22:42:14 preclear_disk_X348T61A_4640: Post-Read: dd output: 2738225+0 records in Jun 08 22:42:14 preclear_disk_X348T61A_4640: Post-Read: dd output: 2738224+0 records out Jun 08 22:42:14 preclear_disk_X348T61A_4640: Post-Read: dd output: 5742471938048 bytes (5.7 TB, 5.2 TiB) copied, 34072.8 s, 169 MB/s Jun 08 22:42:14 preclear_disk_X348T61A_4640: Post-Read: dd output: 2739041+0 records in Jun 08 22:42:14 preclear_disk_X348T61A_4640: Post-Read: dd output: 2739040+0 records out Jun 08 22:42:14 preclear_disk_X348T61A_4640: Post-Read: dd output: 5744183214080 bytes (5.7 TB, 5.2 TiB) copied, 34085.7 s, 169 MB/s Jun 08 22:42:14 preclear_disk_X348T61A_4640: Post-Read: dd output: 2739798+0 records in Jun 08 22:42:14 preclear_disk_X348T61A_4640: Post-Read: dd output: 2739797+0 records out Jun 08 22:42:14 preclear_disk_X348T61A_4640: Post-Read: dd output: 5745770758144 bytes (5.7 TB, 5.2 TiB) copied, 34097.4 s, 169 MB/s Jun 08 22:42:14 preclear_disk_X348T61A_4640: Post-Read: dd output: 2739969+0 records in Jun 08 22:42:14 preclear_disk_X348T61A_4640: Post-Read: dd output: 2739968+0 records out Jun 08 22:42:14 preclear_disk_X348T61A_4640: Post-Read: dd output: 5746129371136 bytes (5.7 TB, 5.2 TiB) copied, 34115.9 s, 168 MB/s Jun 08 22:42:14 preclear_disk_X348T61A_4640: Post-Read: dd output: dd: error reading '/dev/sdh': Input/output error Jun 08 22:42:14 preclear_disk_X348T61A_4640: Post-Read: dd output: 2739970+1 records in Jun 08 22:42:14 preclear_disk_X348T61A_4640: Post-Read: dd output: 2739970+1 records out Jun 08 22:42:14 preclear_disk_X348T61A_4640: Post-Read: dd output: 5746134970368 bytes (5.7 TB, 5.2 TiB) copied, 34124.9 s, 168 MB/s Jun 08 22:42:14 preclear_disk_X348T61A_4640: Post-Read: post-read verification failed! Jun 08 22:42:16 preclear_disk_X348T61A_4640: S.M.A.R.T.: Error: Jun 08 22:42:16 preclear_disk_X348T61A_4640: S.M.A.R.T.: Jun 08 22:42:16 preclear_disk_X348T61A_4640: S.M.A.R.T.: ATTRIBUTE INITIAL NOW STATUS Jun 08 22:42:16 preclear_disk_X348T61A_4640: S.M.A.R.T.: Reallocated_Sector_Ct 0 0 - Jun 08 22:42:16 preclear_disk_X348T61A_4640: S.M.A.R.T.: Power_On_Hours 39425 39464 Up 39 Jun 08 22:42:16 preclear_disk_X348T61A_4640: S.M.A.R.T.: Runtime_Bad_Block 0 0 - Jun 08 22:42:16 preclear_disk_X348T61A_4640: S.M.A.R.T.: End-to-End_Error 0 0 - Jun 08 22:42:16 preclear_disk_X348T61A_4640: S.M.A.R.T.: Reported_Uncorrect 0 3 Up 3 Jun 08 22:42:16 preclear_disk_X348T61A_4640: S.M.A.R.T.: Airflow_Temperature_Cel 31 34 Up 3 ->Failed in Past<- Jun 08 22:42:16 preclear_disk_X348T61A_4640: S.M.A.R.T.: Current_Pending_Sector 0 8 Up 8 Jun 08 22:42:16 preclear_disk_X348T61A_4640: S.M.A.R.T.: Offline_Uncorrectable 0 8 Up 8 Jun 08 22:42:16 preclear_disk_X348T61A_4640: S.M.A.R.T.: UDMA_CRC_Error_Count 0 0 - Jun 08 22:42:16 preclear_disk_X348T61A_4640: S.M.A.R.T.: SMART overall-health self-assessment test result: PASSED Jun 08 22:42:17 preclear_disk_X348T61A_4640: error encountered, exiting ...To me, it seems like a temperature error, but it went from 31 C to 34 C - is that really a major issue to stop the test?
How do I recover from this? What's the next step?
-
On 6/6/2022 at 11:11 PM, itimpi said:
You want to make sure that going forward you have a backup of the flash drive so you can quickly recover if a flash drive fails. You can take a manual backup of your flash drive at any time by clicking on it on the Main tab and selecting the Backup option. You can have automated backups to the cloud on Limetech servers if you install the MyServers plugin or locally using the CA Appdata backup plugin.
Thank you for the recommendations! I will set up automatic backups of the Flash USB drive.
BTW...
CA Auto Update Applications says:QuoteNOTE: USB Backup is deprecated on Unraid version 6.9.0 It is advised to use the Unraid.net plugin instead
-
Does anyone know if the TRIM SSD plugin, by default, trims all SSD's regardless if their file system is XFS or BTRFS?
Or, does it only trim XFS SSD's since I've read that performing TRIM on a BTRFS SSD can be bad?
There is no way to exclude BTRFS in the settings of this plugin.
-
1
-
-
2 hours ago, Squid said:
Clicking anywhere on the card (or the info button) brings up the sidebar which will tell you that it requires Unassigned Devices, and that requirement isn't met (hovering over the + on the card will also tell you that it requires UD installed)
You're absolutely correct! But, can you please post a screen shot of what you mean? I don't see any listed dependencies in the sidebar?
-
7 minutes ago, itimpi said:
What version of Unraid are you running? It is likely that it is to old for that plugin.
Version is: [6.10.2]
I just recently created this new server and had to redo some things because my USB stick went bad.
Any ideas why preclear has no install button?
-
I had to setup my UNRAID boot USB disk again and install all of my plugins again. Why is the install button missing?
It's not installed and there's no ACTION button either.
[Plugin] Mover Tuning
in Plugin Support
Posted
May you please share a screenshot of your settings?