coronicus

sending the drive back.. thanks for the help.

Ty so much for helping me.. here is the download smart report. i hoping this is what you were looking for gunraid-smart-20210819-0905.zip

ok the test completed with errors.. so what should i tell the seller that im getting smart errors? is that enuff info.. Last SMART test result: Errors occurred - Check SMART report ATA Error Count: 10 (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 10 occurred at disk power-on lifetime: 35 hours (1 days + 11 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 02 ce 5d 0d 08 Error: UNC at LBA = 0x080d5dce = 135093710 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 08 88 c8 5d 0d 40 00 08:14:32.663 READ FPDMA QUEUED ef 10 02 00 00 00 a0 00 08:14:32.661 SET FEATURES [Enable SATA feature] 27 00 00 00 00 00 e0 00 08:14:32.661 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 a0 00 08:14:32.660 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 08:14:32.660 SET FEATURES [Set transfer mode] Error 9 occurred at disk power-on lifetime: 35 hours (1 days + 11 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 02 ce 5d 0d 08 Error: UNC at LBA = 0x080d5dce = 135093710 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 08 40 c8 5d 0d 40 00 08:14:29.344 READ FPDMA QUEUED 60 08 38 c0 5d 0d 40 00 08:14:29.344 READ FPDMA QUEUED 60 08 30 b8 5d 0d 40 00 08:14:29.344 READ FPDMA QUEUED 60 08 28 b0 5d 0d 40 00 08:14:29.344 READ FPDMA QUEUED 60 08 20 a8 5d 0d 40 00 08:14:29.344 READ FPDMA QUEUED Error 8 occurred at disk power-on lifetime: 35 hours (1 days + 11 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 72 ce 5d 0d 08 Error: UNC at LBA = 0x080d5dce = 135093710 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 c0 d0 40 5f 0d 40 00 08:14:25.902 READ FPDMA QUEUED 60 40 c8 00 5a 0d 40 00 08:14:25.902 READ FPDMA QUEUED 60 c0 08 40 59 0d 40 00 08:14:25.885 READ FPDMA QUEUED 60 40 00 00 54 0d 40 00 08:14:25.885 READ FPDMA QUEUED 60 c0 f0 40 4f 0d 40 00 08:14:25.872 READ FPDMA QUEUED Error 7 occurred at disk power-on lifetime: 19 hours (0 days + 19 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 04 bc 4a 0d 08 Error: UNC at LBA = 0x080d4abc = 135088828 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 08 a8 b8 4a 0d 40 00 19:46:42.241 READ FPDMA QUEUED ef 10 02 00 00 00 a0 00 19:46:42.240 SET FEATURES [Enable SATA feature] 27 00 00 00 00 00 e0 00 19:46:42.240 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 a0 00 19:46:42.238 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 19:46:42.238 SET FEATURES [Set transfer mode] Error 6 occurred at disk power-on lifetime: 19 hours (0 days + 19 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 04 bc 4a 0d 08 Error: UNC at LBA = 0x080d4abc = 135088828 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 08 a0 b8 4a 0d 40 00 19:46:38.922 READ FPDMA QUEUED 60 08 98 b0 4a 0d 40 00 19:46:38.921 READ FPDMA QUEUED 60 08 78 a8 4a 0d 40 00 19:46:38.921 READ FPDMA QUEUED 60 08 70 a0 4a 0d 40 00 19:46:38.921 READ FPDMA QUEUED 60 08 68 98 4a 0d 40 00 19:46:38.921 READ FPDMA QUEUED

well didn't know about the extended smart test in unraid, ty for pointing that out, running it now.. At this point I just want to prove its bad and get a new drive.

new to unraid so im still trying to understand errors in logs.. i have run preclear 3 times now (dif cables dif controlers) on this drive with similar error logs so im going to assume this drive is bad. I purchased this drive from amazon and i guess i just want to verification that it is bad and why. im assuming it cause the zero out of drive went ok but the read of the zeroed out drive failed?? am i on the right track? Thanks coro Aug 19 04:30:39 preclear_disk_MK0371YHKYJYNA_17205: Post-Read: dd output: dd: error reading '/dev/sdg': Input/output error Aug 19 04:30:39 preclear_disk_MK0371YHKYJYNA_17205: Post-Read: dd output: 360660+1 records in Aug 19 04:30:39 preclear_disk_MK0371YHKYJYNA_17205: Post-Read: dd output: 360660+1 records out Aug 19 04:30:39 preclear_disk_MK0371YHKYJYNA_17205: Post-Read: dd output: 756360646656 bytes (756 GB, 704 GiB) copied, 4953.73 s, 153 MB/s Aug 19 04:30:39 preclear_disk_MK0371YHKYJYNA_17205: Post-Read: post-read verification failed! Aug 19 04:30:42 preclear_disk_MK0371YHKYJYNA_17205: S.M.A.R.T.: Error: Aug 19 04:30:42 preclear_disk_MK0371YHKYJYNA_17205: S.M.A.R.T.: Aug 19 04:30:42 preclear_disk_MK0371YHKYJYNA_17205: S.M.A.R.T.: ATTRIBUTE INITIAL NOW STATUS Aug 19 04:30:42 preclear_disk_MK0371YHKYJYNA_17205: S.M.A.R.T.: Reallocated_Sector_Ct 3 3 -Aug 19 04:30:42 preclear_disk_MK0371YHKYJYNA_17205: S.M.A.R.T.: Power_On_Hours 27 35 Up 8 Aug 19 04:30:42 preclear_disk_MK0371YHKYJYNA_17205: S.M.A.R.T.: Temperature_Celsius 32 32 -Aug 19 04:30:42 preclear_disk_MK0371YHKYJYNA_17205: S.M.A.R.T.: Reallocated_Event_Count 3 3 -Aug 19 04:30:42 preclear_disk_MK0371YHKYJYNA_17205: S.M.A.R.T.: Current_Pending_Sector 0 1 Up 1 Aug 19 04:30:42 preclear_disk_MK0371YHKYJYNA_17205: S.M.A.R.T.: Offline_Uncorrectable 0 0 -Aug 19 04:30:42 preclear_disk_MK0371YHKYJYNA_17205: S.M.A.R.T.: UDMA_CRC_Error_Count 0 0 -Aug 19 04:30:42 preclear_disk_MK0371YHKYJYNA_17205: S.M.A.R.T.: SMART overall-health self-assessment test result: PASSED Aug 19 04:30:43 preclear_disk_MK0371YHKYJYNA_17205: error encountered, exiting...

That explains why no videos on my crazy idea.. so more of a hardware issue with ssd's overuse without trim. ok.. so im guessing i can setup two cache drives one for the system stuff and one for my transfer junk so the ssd doesnt get overused atleast thats my thinking Thank you for the quick reply will play around with two caches and see if it works the way my crazy brain thinks. will have to search around for that backup thing coro

new to unraid so still learning 1x4tb parity 4x3tb array drives 1x120gb SSD (thinking of adding to array for system files) 1x750gb cache so I watched some vids on how to setup cache or pool drive but once i do that i lose parity for the system or the shares setup with prefer-cahce options or yes cache options. Can i not just setup the ssd in the array as a drive ecluding all the other shares but the system ones and just move the files to it so atleast i get faster reads with parity? I guess the question is do the writes to those shares happen that often or constant. i cant find an app yet to give me that info on how many reads and writes are going on in those specific shares (if anyone has a suggestion on what app to try for that plz do) (appdate/domains/isos/system) I dont see myself doing allot of writes that often, altho i wasnt prepaired for how slow transfering speeds to a parity array would be, i get only 30-50mb so with that one hd as a cahce that should give a little speed bump and good enuff for my needs atm just dont wanna put system files on it. what im after is just speeding up the docker stuff (emby/krusader) with parity bakcup and stop the hd spining up and down constantly for system files. along with avoiding this wierd backup configuration for cache drive stuff. (dont trust myself to set that up flawlessly tbh) Thanks for any help or advise. coro