Just Me

Hey! I've set up a test unraid server with some older disk I want to preclear. Two 1.5 TB disks and two 1 TB disk. The preclear plugin recognizes the two 1.5 TB disks as 2 TB disks Any ideas? It is a bug? Diagnostics attached. tower-diagnostics-20190813-1431.zip

Seems I'm pretty outdated with just 2GB of RAM. ?

Thank you very much. I'll give it a try as soon as my external drive arrives. Preclear is always a good way to "burn in" new drives, even if I don't plan to use it with unRAID. SATA or eSATA would be better but the device only has USB 3.0 and I don't want to open the external case, nowadays this always results in a destroyed case because of all these plastic clips :-/

Sorry, if this has been asked before, but is it also possible to preclear an external drive attached via USB or is preclear only able to use disks attached via SATA?

As said before it is a new script written by gfjardim so no need to add the "old" preclear script. (as fas as I unterstand the new beta plugin)

So I've tried to use the command line to preclear my USB disk but it seems it is not that easy. If I start the preclear script the following error appears: Of course I could prelcear the disk anyway but the script won't be able to grab the SMART data. I think the issue is the "-d ata" option. The USB device needs a "-d sat" command to read the SMART attributes. Maybe I could modify the preclear script to use the "-d sat" option instead of "-d ata" but the script is very complex and I don't think I'm able to modify it correctly Edit: okay, I confess I'm just stupid and didn't recognize that the script already allows to set a custom device type for SMART. My bad

Thanks for the quick reply. It seems the plugin is not able to use USB drives, the attached device is not listet as a valid disk to preclear the plugin just reports: No unassigned disks available. My USB drive seems to report SMART attributes, CrystalDiskInfo is able to deliver the same data as shown on internal disks. So it seems SMART report is not in issue. I'll check if I'm able to start a "manuell" preclear using screen and command line.

Is there a way to preclear USB attached drives? I like to "burn in" new disks with preclear even if I don't plan to use them in unRAID. I've got a new external 2 TB 2,5" USB disk and I would like to see if it will survive the first X hours preclearing before I'll put real data on it.

There is still a "/" missing: http://lime-technology.com/forum/index.php?topic=37490.msg382778#msg382778 rsync -nrcv /mnt/[source]/ /mnt/[dest]/t >/boot/verify.txt

You could but teracopy will already check the checksum and make sure all data are okay. I would trust teracopy and skip step 8.

Thank you

How do I use the bjp999 script? In the bjp999 archive are several files: preclear_bjp.sh, readvz and a x64 folder with (I guess) a 64 bit readvz. Do I have to copy the 64bit readvz and the script to /boot/config/plugins/preclear.disk/ ?

I was wrong, this works. Rsync just reads the whole source disk first, which takes hours, and then starts to compare the checksum with the destination disk. So it seems everything is fine. Thank you Freddie for your help

Okay I've tried rsync -nrcv /mnt/disk1/ /mnt/disk10/t >/boot/verify.txt but rsync still only reads disk1, disk10 ist still spun down. So I guess it is not working either?

Hey! Okay, it seems I'm too stupid for this I've tried to copy the content from disk1 to the new disk10. I've used this command to copy all files: cp -rpv /mnt/disk1/* /mnt/disk10/t This seemed to work, all files are in /disk10/t Now I want to check if all files are okay so I type this command in the command line: rsync -nrcv /mnt/disk1 /mnt/disk10/t >/boot/verify.txt But all it does was a lot of reading on disk1, no reading on disk10 so disk10 went to sleep after a while. After the process has finished I have a verify.txt file. It seems to contain a list of all files that are an disk1. e.g. sending incremental file list disk1/ disk1/Dokus/ disk1/Dokus/SDTV/ disk1/Dokus/SDTV/Ice Road Truckers/ disk1/Dokus/SDTV/Ice Road Truckers/Season 1/ disk1/Dokus/SDTV/Ice Road Truckers/Season 1/Ice Road Truckers - Season1 Disc1.dvd disk1/Dokus/SDTV/Ice Road Truckers/Season 1/Ice Road Truckers - Season1 Disc1.iso . . . sent 111,485 bytes received 8,188 bytes 5.49 bytes/sec total size is 2,964,339,119,913 speedup is 24,770,325.14 (DRY RUN) What I'm doing wrong? I thought the verify.txt should only contain files that are not okay but rsync never read any files an disk10. I'm confused, any help?

That's the correct directory

Oh, I see. So 81 MB/s is the average speed. Thank you very much for the quick reply.

Hey! Thanks for this plugin. I have a question about the read speed. As you can see in the screenshot the preclear status shows a read speed of 81MB/s but if I open the preview window by clicking on the eye icon it says the read speed is 11,2 MB/s I'm confused

dito

Hey! Sorry to bother you guys. A friend of mine gave me a 3TB hard drive, which has abnormal SMART values. That's why I started a three-cycle-preclear to test the drive. Here is the preclear report: ========================================================================1.14 == invoked as: ./preclear_disk.sh -A -c 3 /dev/sdd == ST3000DM001-9YN166 S1F14GED == Disk /dev/sdd has been successfully precleared == with a starting sector of 1 == Ran 3 cycles == == Using :Read block size = 8388608 Bytes == Last Cycle's Pre Read Time : 6:22:11 (130 MB/s) == Last Cycle's Zeroing time : 5:33:40 (149 MB/s) == Last Cycle's Post Read Time : 14:56:28 (55 MB/s) == Last Cycle's Total Time : 20:31:10 == == Total Elapsed Time 68:28:52 == == Disk Start Temperature: 26C == == Current Disk Temperature: 29C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdd /tmp/smart_finish_sdd ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 114 97 6 ok 60561760 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 3320 Airflow_Temperature_Cel = 71 74 45 In_the_past 29 Temperature_Celsius = 29 26 0 ok 29 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 3. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 3. 0 sectors were pending re-allocation after post-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 3. 0 sectors were pending re-allocation after post-read in cycle 2 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 3. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 2136 sectors had been re-allocated before the start of the preclear. 2144 sectors are re-allocated at the end of the preclear, a change of 8 in the number of sectors re-allocated. ============================================================================ I've attached the SMART reports below. It would be nice if someone could take a look at the reports. Would you still trust the hard drive and save data on it? Or is it more a case for disposal? :'( Thanks in advance. preclear_start_SMART.txt preclear_finish_SMART.txt

Looks like you should RMA this drive.

Thanks

Drives >2.2TB always start on sector 1 no matter if you add the -A option or not. I precleared an older hard drive and I am a little concerned about the S.M.A.R.T. values. Disk: /dev/sde smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.11 family Device Model: ST31500341AS Serial Number: 9VSXXXXX Firmware Version: CC1H User Capacity: 1,500,301,910,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Mon Mar 11 00:09:27 2013 CET 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: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. 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: ( 617) 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: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x103f) SCT Status supported. SCT Error Recovery Control 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 FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 117 099 006 Pre-fail Always - 152796779 3 Spin_Up_Time 0x0003 097 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 676 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 2 7 Seek_Error_Rate 0x000f 073 060 030 Pre-fail Always - 24775969 9 Power_On_Hours 0x0032 096 096 000 Old_age Always - 4339 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 6 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 328 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 098 000 Old_age Always - 38655361034 189 High_Fly_Writes 0x003a 001 001 000 Old_age Always - 369 190 Airflow_Temperature_Cel 0x0022 068 043 045 Old_age Always In_the_past 32 (0 91 36 29) 194 Temperature_Celsius 0x0022 032 057 000 Old_age Always - 32 (0 17 0 0) 195 Hardware_ECC_Recovered 0x001a 063 022 000 Old_age Always - 152796779 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 - 181578332377046 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 4086532387 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 1450557504 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% 4266 - # 2 Short offline Completed without error 00% 4104 - 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. The High_Fly_Writes value seems to be a problem although I'm not sure whether this is really a problem. Spin_Retry_Counts should not happen but the value haven't raised in over a year, so I don't think it's a real issue. Should I still use the drive?

Interesting, I had the same drive and the same end-to-end error. Coincidence? Probably.

I've similar errors in my log: Mar 3 16:03:23 NAS kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) Mar 3 16:03:23 NAS kernel: ata4.00: failed command: SMART (Minor Issues) Mar 3 16:03:23 NAS kernel: ata4.00: cmd b0/d1:01:01:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in (Drive related) Mar 3 16:03:23 NAS kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Mar 3 16:03:23 NAS kernel: ata4.00: status: { DRDY } (Drive related) Mar 3 16:03:23 NAS kernel: ata4: hard resetting link (Minor Issues) Mar 3 16:03:24 NAS kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related) Mar 3 16:03:24 NAS kernel: ata4.00: configured for UDMA/133 (Drive related) Mar 3 16:03:24 NAS kernel: ata4: EH complete (Drive related) Mar 3 16:16:39 NAS kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) Mar 3 16:16:39 NAS kernel: ata4.00: failed command: SMART (Minor Issues) Mar 3 16:16:39 NAS kernel: ata4.00: cmd b0/d1:01:01:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in (Drive related) Mar 3 16:16:39 NAS kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Mar 3 16:16:39 NAS kernel: ata4.00: status: { DRDY } (Drive related) Mar 3 16:16:39 NAS kernel: ata4: hard resetting link (Minor Issues) Mar 3 16:16:40 NAS kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related) Mar 3 16:16:40 NAS kernel: ata4.00: configured for UDMA/133 (Drive related) Mar 3 16:16:40 NAS kernel: ata4: EH complete (Drive related) Mar 3 16:19:32 NAS kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) Mar 3 16:19:32 NAS kernel: ata4.00: failed command: SMART (Minor Issues) Mar 3 16:19:32 NAS kernel: ata4.00: cmd b0/d1:01:01:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in (Drive related) Mar 3 16:19:32 NAS kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Mar 3 16:19:32 NAS kernel: ata4.00: status: { DRDY } (Drive related) Mar 3 16:19:32 NAS kernel: ata4: hard resetting link (Minor Issues) Mar 3 16:19:33 NAS kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related) Mar 3 16:19:33 NAS kernel: ata4.00: configured for UDMA/133 (Drive related) Mar 3 16:19:33 NAS kernel: ata4: EH complete (Drive related) Mar 3 16:26:14 NAS kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) Mar 3 16:26:14 NAS kernel: ata4.00: failed command: SMART (Minor Issues) Mar 3 16:26:14 NAS kernel: ata4.00: cmd b0/d1:01:01:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in (Drive related) Mar 3 16:26:14 NAS kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Mar 3 16:26:14 NAS kernel: ata4.00: status: { DRDY } (Drive related) Mar 3 16:26:14 NAS kernel: ata4: hard resetting link (Minor Issues) Mar 3 16:26:15 NAS kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related) Mar 3 16:26:15 NAS kernel: ata4.00: configured for UDMA/133 (Drive related) Mar 3 16:26:15 NAS kernel: ata4: EH complete (Drive related) Mar 3 19:12:57 NAS kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) Mar 3 19:12:57 NAS kernel: ata4.00: failed command: SMART (Minor Issues) Mar 3 19:12:57 NAS kernel: ata4.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in (Drive related) Mar 3 19:12:57 NAS kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Mar 3 19:12:57 NAS kernel: ata4.00: status: { DRDY } (Drive related) Mar 3 19:12:57 NAS kernel: ata4: hard resetting link (Minor Issues) Mar 3 19:12:58 NAS kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related) Mar 3 19:12:58 NAS kernel: ata4.00: configured for UDMA/133 (Drive related) Mar 3 19:12:58 NAS kernel: ata4: EH complete (Drive related)