jbuszkie

It ran another session just fine. I'm not sure what to do! I really don't like the fact that it came back as unformatted twice over the course of a couple months. Not too much of a big deal as I don't keep any of my save games on it. I'm so glad that I didn't! I guess I'll just put it back in and see if it happens again. Thanks for taking a look. Jim

The process id described pretty well is the thread about the script here. It's been a while since I added a drive to the array. I use preclear on ALL my disks before they go into any system for any purpose! Follow the instruction in that thread for when the disk is done with pre-clear and you should be fine.

I often use a separate system to pre-clear my discs before I add them to the un raid array

I have a 250GB drive I put in my xbox. Twice now it has magically come back as unformatted. So I yanked it out and ran preclear on it. I beleive I bought this as a factory reconditioned drive. I'm sure I ran pre-clear on it before I threw it in the xbox. There is also an ATA error in the smart results. Here are the results. think it should be RMA'ed?? 9 pending seems like too many.. ============================================================================ ** Changed attributes in files: /tmp/smart_start_sda /tmp/smart_finish_sda ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Seek_Error_Rate = 100 200 0 ok 0 Temperature_Celsius = 88 108 0 ok 55 No SMART attributes are FAILING_NOW 2 sectors were pending re-allocation before the start of the preclear. 9 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, a change of -2 in the number of sectors pending re-allocation. 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. ============================================================================ 250gb.txt

I look forward to reading it when you are done! Please let us know here when you post it!

did they change the design of the norco? I don't remember the back looking like this! Is it better? Is anything else different?? I believe I have two of the older ones and I was thinking about replacing the stock fans. I saw some pictures that didn't look like the ones I have! Jim

I've seen that PSU as low as $100, but that's once in a blue moon. I'll create a PSU good deals thread once another good deal on a PSU comes up! I think it's a blue moon!! SeaSonic X650 for $99!!! Even though I don't believe my issue is the PSU.. I might be tempted to get this BMW of PSUs!

Oh.. and now it is throwing errors on the post read! I may have to kill the pre-clear script and it is bringing the system to a halt! Well.. at least Unmenu isn't responding... and the preclear screen session doesn't seem to be updating. Now it make me wonder again about my PSU being an issue... I still don't think so as more than 1/2 my drives were spun down before the errors started showing up. and it failed the seaTools test on a completely different machine and threw ATA errors on an even different machine that I ran the first preclear on the preread?? RMA??

So I was getting some ATA errors on this drive when doing a parity check. It even red-balled. So I took the files off the drive and I took it out of the array. I ran SeaTools on it and it failed (but didn't give me an error code) So the I decided to run it through 2 cycles of preclear. The first pre-read gave me those ATA errors again. After that, I don't think I got any more in the post read or the next pre/post read cycle. There were, at one point, 37 sectors pending re-allocation. Now there are 0 with none of then being relocated. so it must have fixed its self There are some SMART errors: 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 0x000f 100 093 051 Pre-fail Always - 11 3 Spin_Up_Time 0x0007 061 061 011 Pre-fail Always - 12530 4 Start_Stop_Count 0x0032 093 093 000 Old_age Always - 7245 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 100 100 051 Pre-fail Always - 0 8 Seek_Time_Performance 0x0025 100 100 015 Pre-fail Offline - 12720 9 Power_On_Hours 0x0032 096 096 000 Old_age Always - 21526 10 Spin_Retry_Count 0x0033 100 100 051 Pre-fail Always - 0 11 Calibration_Retry_Count 0x0012 100 100 000 Old_age Always - 1 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 111 13 Read_Soft_Error_Rate 0x000e 100 093 000 Old_age Always - 11 183 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 184 Unknown_Attribute 0x0033 100 100 000 Pre-fail Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 790 188 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 080 061 000 Old_age Always - 20 (Lifetime Min/Max 17/22) 194 Temperature_Celsius 0x0022 080 060 000 Old_age Always - 20 (Lifetime Min/Max 17/24) 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 940515921 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0012 100 099 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 1 199 UDMA_CRC_Error_Count 0x003e 100 100 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x000a 100 100 000 Old_age Always - 0 201 Soft_Read_Error_Rate 0x000a 100 100 000 Old_age Always - 0 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: read failure 20% 21456 2151583487 # 2 Short offline Completed: read failure 20% 21456 2151583475 # 3 Short offline Completed: read failure 20% 20556 2044423822 Right now I'm currently running another preclear cycle on the same machine that it lived in. (as opposed to running it on a separate machine where I normally do my pre-clears) And it got past the preread and is in the post read phase with no ATA errors reported so far. Now I don't know whether to trust this drive or not. I have till December to RMA it. I'm worried if I RMA it they will say the drive is good and not replace it! what should I do? Should I add it back to the array or not? Here is the bits of the preclear rpt. ============================================================================ ** Changed attributes in files: /tmp/smart_start_sda /tmp/smart_finish_sda ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Airflow_Temperature_Cel = 71 72 0 ok 29 Temperature_Celsius = 71 72 0 ok 29 Current_Pending_Sector = 100 99 0 ok 0 No SMART attributes are FAILING_NOW 24 sectors were pending re-allocation before the start of the preclear. 37 sectors were pending re-allocation after pre-read in cycle 1 of 2. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 2. 0 sectors were pending re-allocation after post-read in cycle 1 of 2. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 2. 0 sectors are pending re-allocation at the end of the preclear, a change of -24 in the number of sectors pending re-allocation. 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. ============================================================================

What is the lowest you guys have seen the SeaSonic X 650 PSU go for? I having some issues with my rig (That's a seperate thread!) and I'm trying to see how much it would cost me to eliminate my PSU as the issue. Right now the x650 is ~$140 w/FS Does is go much lower than that? Raj, Maybe we need a dedicated PSU good deals thread like the ram and others! Jim

Well.. I took apart the PS and moved some stuff around.. I believe it is just one 12V regulator rail that has separate crude current limiting on each branch. Anyway.. Rail 1 was the 12V to the MB 24pin connector and all the hard drive connectors. Rail 2 was the 12V for the CPU power the 4+4 connector) Rail 3 was PCIe power 1 Rail 4 was PCIe power 2. I yanked the PCIe power 1 and moved it to Rail 1 I split the 4 drive cables: 2 go to Rail 3 and 2 go to rail 4 And wouldn't you know it.. They have a 620W PS single rail for $30 AR FS from Antec today!! Figures! I would have got that one instead of hacking mine.. Oh well... Jim

That's the Engineer in me! I'd rather fix it then buy a new one! It wouldn't be the first time (or last, I'm sure) that I've take apart a PS...

Has anyone tried to hack their PS to move 1/2 of the disk cables to the PCIe rail? Seems like it might be pretty easy (if you have soldering skills..) I'd hate to waste my 630W PS if it can be re-engineered

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

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

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

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 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

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

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!