jbuszkie

well.. maybe if I get bored I'll open up the PS and see if I can see what goes where! Looks like I'll have to start scouring the good deals for power supplies in the next year or so.. I'm probably good for 10 drives since most (if not all) are green... but I only have 9 for now... Jim

I don't believe so...

So there's no way of knowing which of my cable's go to which rails?

I bought this power supply a while ago. I'm going to add another drive so I thought I'd look into my PS to see if it could handle it. I've got 4 rails @ 20A each.. but how do I know which cables go to which rails? Attached is the PS ratings. I currently have 8 drives and I want to go up to 12.. but for now I'm testing #9 and it doesn't seem to be choking.. Jim

I do have another question... I noticed that on my second pass It went right to zeroing? There is no pre-read? I did a search on this thread for "skip pre" and I only got info about the added command line options. Is new and expected? Jim EDIT: Never mind... I saw it on the .9.9 or so version notes.. SO I guess that it's not needed since you just did a post read on the previous cycle?

ok.. I see there is a bunch of info in the /tmp directory.. so you do it.. Can you add the diff to the e-mail report between cycles? Also can you add the pending report also the e-mail reports? I can probably add them.. but would probably be faster for you to add it to the next release.. Thanks, Jim

Joe, I can't remember... in your script between cycles.. Do you run another SMART test? I'm running two cycles on my new 3TB drive and I'd be interested to see if there were SMART differences after the first cycle. The first cycle took 45hours!! I'd hate to wait another 45 hours only to find there were errors on the first run! ========================================================================1.12 == == Disk /dev/sdd has successfully finished a preclear cycle == == Finished Cycle 1 of 2 cycles == == Using read block size = 8,225,280 Bytes == Last Cycle's Pre Read Time : 9:39:14 (86 MB/s) == Last Cycle's Zeroing time : 8:59:39 (92 MB/s) == Last Cycle's Post Read Time : 26:30:13 (31 MB/s) == Last Cycle's Total Time : 45:10:16 == == Total Elapsed Time 45:10:16 == == Disk Start Temperature: 30C == == Current Disk Temperature: 37C, == == Starting next cycle == ========================================================================1.12 I suppose I can do manual diff if it's in the /tmp area...

Were you running it using the "screen" program? If yes.. The just reconnect to it.. But it sounds like you were jsut telneted into it... in which case... you have to start over... Screen will run in the background and you can connect to the session or disconnect as many times as you want and the session is still there... I have had this happen before so I always run using screen! Jim

If you look back at a couple of other people's posts, you can see this is normal. Joe will have to explain why.... but it's in other's results as well.. Jim

There is a thread for looking at those results. There are also several other posts that show good and bad disks. Take a look there.. http://lime-technology.com/forum/index.php?topic=4068.0

Crud! The last drive, after power cycling, passed the preclear test.. but there are some more errors. My guess is I should RMA this drive. There are 28 ATA Errors. There were 15 before the 2nd preclear attempt. Here is an excerpt. Full smart report attached. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 0 2 Throughput_Performance 0x0026 252 252 000 Old_age Always - 0 3 Spin_Up_Time 0x0023 067 066 025 Pre-fail Always - 10113 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 4 5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 252 252 051 Old_age Always - 0 8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0 10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 252 252 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 4 181 Unknown_Attribute 0x0022 252 252 000 Old_age Always - 0 191 G-Sense_Error_Rate 0x0022 252 252 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always - 0 195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always 196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 252 252 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0036 100 100 000 Old_age Always - 31 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 0 223 Load_Retry_Count 0x0032 252 252 000 Old_age Always - 0 225 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 4 SMART Error Log Version: 1 ATA Error Count: 28 (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 28 occurred at disk power-on lifetime: 50 hours (2 days + 2 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 -- -- -- -- -- -- -- 84 51 00 00 4f c2 00 Error: ABRT What do you think? I moved the drive to a different cable and power cord for the 2nd pre-clear try.. So it's not a cabling issue.. Thanks, Jim smart_start3805.txt smart_start3805.txt

Ok.. I'll try the reseat and switch the cables around... The drives are being cleared in a separate machine. so it's not my main UnRaid machine. Interestingly.. Even on this separate machine I'm seeing much slower reads on the post read. I still am baffled by this. I'm getting about 40MB/s calculated while the test says 84MB/s Post Read in progress on /dev/sda: 75% complete. ( 1,501,936,128,000 of 2,000,398,934,016 bytes read )at 84.3 MB/s Disk Temperature: 35C, Using Block size of 8,225,280 Bytes Next report at 100% Calculated Read Speed: 40 MB/s Elapsed Time of current cycle: 10:15:27 Total Elapsed time: 22:31:51 All three remaining drives exhibit this... The pre-read and the zeroing all were fast... Pre Read finished on /dev/sdc ( 2,000,388,096,000 of 2,000,398,934,016 bytes read) Pre Read Elapsed Time: 6:15:27 Total Elapsed Time: 6:15:32 Disk Temperature: -->41<--C, Using Block size of 8,225,280 Bytes Calculated Read Speed - 88 MB/s Zeroing Disk /dev/sdc Done. Zeroing Elapsed Time: 5:55:17 Total Elapsed Time: 12:10:52 Disk Temperature: -->42<--C, Calculated Write Speed: 93 MB/s

Joe, I'm trying to preclear 4 2T samsung drives. 3 are chugging along but one failed right after zeroing. I grabbed the first smart report as the drive, now, is un responsive. There are some errors reported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 0 2 Throughput_Performance 0x0026 252 252 000 Old_age Always - 0 3 Spin_Up_Time 0x0023 066 066 025 Pre-fail Always - 10438 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 2 5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 252 252 051 Old_age Always - 0 8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 4 10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 252 252 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 2 181 Unknown_Attribute 0x0022 252 252 000 Old_age Always - 0 191 G-Sense_Error_Rate 0x0022 252 252 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always - 0 195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always - 0 196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 252 252 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0036 100 100 000 Old_age Always - 7 200 Multi_Zone_Error_Rate 0x002a 252 252 000 Old_age Always - 0 223 Load_Retry_Count 0x0032 252 252 000 Old_age Always - 0 225 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 2 SMART Error Log Version: 1 ATA Error Count: 7 (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 7 occurred at disk power-on lifetime: 3 hours (0 days + 3 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 -- -- -- -- -- -- -- 84 51 00 00 4f c2 00 Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- b0 d0 01 00 4f c2 00 08 00:00:13.498 SMART READ DATA b0 d0 01 00 4f c2 00 08 00:00:13.498 SMART READ DATA b0 da 00 00 4f c2 00 08 00:00:13.498 SMART RETURN STATUS b0 da 00 00 4f c2 00 08 00:00:13.497 SMART RETURN STATUS ec 00 00 00 00 00 00 08 00:00:13.497 IDENTIFY DEVICE Error 6 occurred at disk power-on lifetime: 3 hours (0 days + 3 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 -- -- -- -- -- -- -- 84 51 00 00 4f c2 00 Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- b0 d1 01 01 4f c2 00 08 00:00:10.913 SMART READ ATTRIBUTE THRESHOLDS [OBS-4] b0 d0 01 00 4f c2 00 08 00:00:10.913 SMART READ DATA b0 da 00 00 4f c2 00 08 00:00:10.912 SMART RETURN STATUS b0 da 00 00 4f c2 00 08 00:00:10.912 SMART RETURN STATUS ec 00 00 00 00 00 00 08 00:00:10.912 IDENTIFY DEVICE Error 5 occurred at disk power-on lifetime: 2 hours (0 days + 2 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 -- -- -- -- -- -- -- 84 51 00 00 4f c2 00 Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- b0 d0 01 00 4f c2 00 08 00:00:08.413 SMART READ DATA b0 d0 01 00 4f c2 00 08 00:00:08.413 SMART READ DATA b0 da 00 00 4f c2 00 08 00:00:08.413 SMART RETURN STATUS b0 da 00 00 4f c2 00 08 00:00:08.412 SMART RETURN STATUS ec 00 00 00 00 00 00 08 00:00:08.412 IDENTIFY DEVICE Error 4 occurred at disk power-on lifetime: 1 hours (0 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 SC SN CL CH DH -- -- -- -- -- -- -- 84 51 00 00 00 00 00 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ec 00 00 00 00 00 00 08 00:00:07.044 IDENTIFY DEVICE 60 d1 00 18 ea e6 40 08 00:00:07.044 READ FPDMA QUEUED 60 d1 00 18 e9 e6 40 08 00:00:07.044 READ FPDMA QUEUED 60 d1 00 18 e8 e6 40 08 00:00:07.044 READ FPDMA QUEUED 60 d1 00 18 e7 e6 40 08 00:00:07.044 READ FPDMA QUEUED Error 3 occurred at disk power-on lifetime: 1 hours (0 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 SC SN CL CH DH -- -- -- -- -- -- -- 84 51 00 00 4f c2 00 Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- b0 d1 01 01 4f c2 00 08 00:00:06.651 SMART READ ATTRIBUTE THRESHOLDS [OBS-4] b0 d0 01 00 4f c2 00 08 00:00:06.650 SMART READ DATA b0 da 00 00 4f c2 00 08 00:00:06.650 SMART RETURN STATUS b0 da 00 00 4f c2 00 08 00:00:06.649 SMART RETURN STATUS ec 00 00 00 00 00 00 08 00:00:06.649 IDENTIFY DEVICE 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 (0) should be 1 SMART Selective self-test log data structure revision number 0 Warning: ATA Specification requires selective self-test log data structure revision number = 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Completed [00% left] (0-65535) 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. I'll try power cycling once the other drives finish (about 2 hours or so) and see if the drive comes back.. and grab another SMART report... but my guess is this drive might be a dud! Do you concur?

Was your unraid array on the same system and was it up? Mine's on the same system (but most of the time wasn't doing anything!) So if you have 1GB and I have 1GB, then maybe it's the processor speed? I think mine's at 900MHz.... Maybe I'll try to bump it up and see what I get for speeds. Maybe I'll just hack the script to do the post read... I'd hate to wait another two days just for a speed experiment! Jim And I have the jumper installed...

Wow it took ~52 hours for the 2T to finish. I added a second disk (also 2T) to the mix so that probably added some time! Results posted in the pre-clear results. No questions.. just FYI... Now on to replacing my parity and removing two 500GB drives (One is PATA) And since when did 500GB drive become small to me! Thanks again for the great script! Jim

Wow the 2T disks take a while.. Disk1 == Disk /dev/sdh has been successfully precleared == == Ran 1 preclear-disk cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 7:41:11 (72 MB/s) == Last Cycle's Zeroing time : 9:42:22 (57 MB/s) == Last Cycle's Post Read Time : 35:29:32 (15 MB/s) == Last Cycle's Total Time : 52:54:19 == == Total Elapsed Time 52:54:19 == == Disk Start Temperature: 33C == == Current Disk Temperature: 36C, == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 58c58 < 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 --- > > 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 63c63 < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 83 --- > > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 821 ============================================================================ Disk 2 Date: Sun Jun 13 22:59:32 EDT 2010 ============================================================================ == == Disk /dev/sdb has been successfully precleared == == Ran 1 preclear-disk cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 7:29:39 (74 MB/s) == Last Cycle's Zeroing time : 8:24:39 (66 MB/s) == Last Cycle's Post Read Time : 35:33:46 (15 MB/s) == Last Cycle's Total Time : 51:29:23 == == Total Elapsed Time 51:29:23 == == Disk Start Temperature: 26C == == Current Disk Temperature: 32C, == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 19,20c19,20 < Offline data collection status: (0x80) Offline data collection activity < was never started. --- > > Offline data collection status: (0x84) Offline data collection activity > > was suspended by an interrupting command from host. 54c54 < 1 Raw_Read_Error_Rate 0x002f 100 253 051 Pre-fail Always - 0 --- > > 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 63c63 < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 19 --- > > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 760 67c67 < 199 UDMA_CRC_Error_Count 0x0032 200 253 000 Old_age Always - 0 --- > > 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 ============================================================================ I went from 72MB/s down to 15MB/s for the Post read! 52 hours!! Granted I was running two disks at once. I wonder if it would have gone faster if I had more memory. Or Maybe boosted the cpu speed. Right now I have one 1GB and running at 900MHz (under clocked to save power) It also seems like the 2 port syba 1x PCIe sata card is slightly faster than the on board (sdb was on that card). Maybe because the rest of the array is on the on board as well. Jim

That's what I thought and was hoping for... Now I'm going to have to wait ~6 extra hours for the test to finish! Jim

Joe, I'm currently pre-clearing a new 2T disk. The post read is going way slower than the pre-read or zeroing phase. I averaged about 70MB/s for the first 2 and now I'm getting about 30MB/s (the display still say 85-95MB/s which is also weird) Is this normal with the new zero checking? Thanks, Jim

This may be a stupid question.. but how do I get minicom to work? I looked in the forum and did a search for a slackware minicom package... But that yielded no fruits! Is there another serial port communication package that's built in or has a package for it? Will I have to run a full slackware distribution? Thanks, Jim

I think I fiured out what was happening with the speed of my tests. It turn out the disks are slower when they are formatted. Not sure why.. but if I "clear" the disk and wipe out the partitions, the test is much faster. It uses a much smaller block size when it's formatted vs when it's clear. fdisk (formatted): root@Tower2:/boot/scripts# fdisk -l /dev/sda Disk /dev/sda: 1500.3 GB, 1500301910016 bytes 1 heads, 63 sectors/track, 46512336 cylinders Units = cylinders of 63 * 512 = 32256 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sda1 2 46512336 1465138552+ 83 Linux Partition 1 does not end on cylinder boundary. fdisk after clearing: root@Tower2:/boot/scripts# fdisk -l /dev/sda Disk /dev/sda: 1500.3 GB, 1500301910016 bytes 255 heads, 63 sectors/track, 182401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sda1 1 182402 1465138552+ 0 Empty Partition 1 does not end on cylinder boundary. The smaller block size makes the test run much slower. Have you seen this? This makes my reads drop to about 30-40MB/s from 90ish MB/s Why does fdisk report differently? Does the smaller block size make the test any better? As in more thrashing? This explains why I had two very different speeds! Jim

There is a program called screen. It allows you to disconnect and reconnect to a particular session. I have that setup and it works nicely. there is a post somewhere that describes what you need.. You might be able to search the forums for it. Also.. if you have mail setup.. you can use the mail parameters and it will e-mail you the differences as well.. Jim

If you didn't get any results when precear finished then your disk is good! Also looking at the smart results you posted look great. If you had issues you would have seen output along the lines of: S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 57c57 < 1 Raw_Read_Error_Rate 0x000f 099 099 051 Pre-fail Always - 5005 --- > 1 Raw_Read_Error_Rate 0x000f 099 099 051 Pre-fail Always - 5264 66c66 < 13 Read_Soft_Error_Rate 0x000e 099 099 000 Old_age Always - 4648 --- > 13 Read_Soft_Error_Rate 0x000e 099 099 000 Old_age Always - 4912 69c69 < 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 4952 --- > 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 9596 71c71 < 190 Airflow_Temperature_Cel 0x0022 071 067 000 Old_age Always - 29 (Lifetime Min/Max 29/33) --- > 190 Airflow_Temperature_Cel 0x0022 068 067 000 Old_age Always - 32 (Lifetime Min/Max 29/33) 74c74 < 197 Current_Pending_Sector 0x0012 092 092 000 Old_age Always - 331 --- > 197 Current_Pending_Sector 0x0012 100 092 000 Old_age Always - 0 78c78 < 201 Soft_Read_Error_Rate 0x000a 097 097 000 Old_age Always - 228 --- > 201 Soft_Read_Error_Rate 0x000a 100 097 000 Old_age Always - 0 You probably got a "pre-clear was successful" or something like that.. Enjoy the new drive!

There is something weird going on... I ran the test on both disks again concurrently and this time I got the same results as running a single. I can't duplicate the 25MB/s or even the 34MB/s Maybe I should just be happy I'm getting the faster speeds! Maybe I was running a some modifed version of the script that ran slow? Bizarre..

I after I ran it a second time by its self, I got to 17.8ish hours. So I feel better.. I would have thought that running two disks wouldn't have THAT much of an effect! Maybe I'll boost the memory speed and CPU speed. Maybe that will help concurrent pre-clears. I've got it crippled to lower the power...