smakovits

Should the new drive be precleared before it is assigned to replace a failed drive? I assume the answer is yes, but I want to ask first. Thanks

Is this board compatible? 785GT-E63 Socket AM2+ 785G ATX Motherboard http://www.microcenter.com/single_product_results.phtml?product_id=0332148 Thanks

Picked up a new drive today. Went with WD as the Seagates make me nervous. I was thinking about using the advanced format and skipping the jumper, but it appears I have the HPA issue that comes with the gigabyte boards and I know 4.7 will bark at me. Therefore, I was thinking that if I get rid of those errors now then I can go to 4.7, preclear the new drive and then add it to the array by tomorrow night to start the rebuild. I know the jumpered vs no jumper yields no benefit, but it is just one of those things. If I can do it I will. I want to get to 4.7 anyway so it is deal with the HPA issues now or deal with them later. It appears I have 2 drives affected. Mar 20 18:35:25 Tower kernel: usb 3-3: configuration #1 chosen from 1 choice Mar 20 18:35:25 Tower kernel: generic-usb 0003:0764:0501.0001: hiddev96,hidraw0: USB HID v1.10 Device [CPS UPS CP850AVRLCD ] on usb-0000:00:12.0-3/input0 Mar 20 18:35:25 Tower kernel: ata5: softreset failed (device not ready) Mar 20 18:35:25 Tower kernel: ata5: applying SB600 PMP SRST workaround and retrying Mar 20 18:35:25 Tower kernel: ata2: softreset failed (device not ready) Mar 20 18:35:25 Tower kernel: ata2: applying SB600 PMP SRST workaround and retrying Mar 20 18:35:25 Tower kernel: ata3: softreset failed (device not ready) Mar 20 18:35:25 Tower kernel: ata3: applying SB600 PMP SRST workaround and retrying Mar 20 18:35:25 Tower kernel: ata1: softreset failed (device not ready) Mar 20 18:35:25 Tower kernel: ata1: applying SB600 PMP SRST workaround and retrying Mar 20 18:35:25 Tower kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Mar 20 18:35:25 Tower kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Mar 20 18:35:25 Tower kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Mar 20 18:35:25 Tower kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Mar 20 18:35:25 Tower kernel: ata2.00: ATA-8: WDC WD20EADS-65R6B0, 01.00A01, max UDMA/133 Mar 20 18:35:25 Tower kernel: ata2.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA Mar 20 18:35:25 Tower kernel: ata1.00: ATA-8: WDC WD20EADS-65R6B0, 01.00A01, max UDMA/133 Mar 20 18:35:25 Tower kernel: ata5.00: HPA detected: current 1953523055, native 1953525168 Mar 20 18:35:25 Tower kernel: ata1.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA Mar 20 18:35:25 Tower kernel: ata5.00: ATA-8: WDC WD1001FALS-75J7B0, 05.00K05, max UDMA/133 Mar 20 18:35:25 Tower kernel: ata5.00: 1953523055 sectors, multi 0: LBA48 NCQ (depth 31/32), AA Mar 20 18:35:25 Tower kernel: ata2.00: configured for UDMA/133 Mar 20 18:35:25 Tower kernel: ata1.00: configured for UDMA/133 Mar 20 18:35:25 Tower kernel: ata5.00: configured for UDMA/133 Mar 20 18:35:25 Tower kernel: ata3.00: ATA-8: WDC WD15EADS-00P8B0, 01.00A01, max UDMA/133 Mar 20 18:35:25 Tower kernel: ata3.00: 2930277168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA Mar 20 18:35:25 Tower kernel: ata3.00: configured for UDMA/133 Mar 20 18:35:25 Tower kernel: scsi 1:0:0:0: Direct-Access ATA WDC WD20EADS-65R 01.0 PQ: 0 ANSI: 5 Mar 20 18:35:25 Tower kernel: sd 1:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) Mar 20 18:35:25 Tower kernel: scsi 2:0:0:0: Direct-Access ATA WDC WD20EADS-65R 01.0 PQ: 0 ANSI: 5 Mar 20 18:35:25 Tower kernel: scsi 3:0:0:0: Direct-Access ATA WDC WD15EADS-00P 01.0 PQ: 0 ANSI: 5 Mar 20 18:35:25 Tower kernel: sd 2:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) Mar 20 18:35:25 Tower kernel: sd 3:0:0:0: [sdc] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB) Mar 20 18:35:25 Tower kernel: sd 3:0:0:0: [sdc] Write Protect is off Mar 20 18:35:25 Tower kernel: sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00 Mar 20 18:35:25 Tower kernel: sd 2:0:0:0: [sdb] Write Protect is off Mar 20 18:35:25 Tower kernel: sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Mar 20 18:35:25 Tower kernel: sd 1:0:0:0: [sda] Write Protect is off Mar 20 18:35:25 Tower kernel: sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00 Mar 20 18:35:25 Tower kernel: sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Mar 20 18:35:25 Tower kernel: sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Mar 20 18:35:25 Tower kernel: sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Mar 20 18:35:25 Tower kernel: sdb: Mar 20 18:35:25 Tower kernel: sdc: Mar 20 18:35:25 Tower kernel: sda: sdb1 Mar 20 18:35:25 Tower kernel: sd 2:0:0:0: [sdb] Attached SCSI disk Mar 20 18:35:25 Tower kernel: sda1 Mar 20 18:35:25 Tower kernel: sd 1:0:0:0: [sda] Attached SCSI disk Mar 20 18:35:25 Tower kernel: sdc1 Mar 20 18:35:25 Tower kernel: sd 3:0:0:0: [sdc] Attached SCSI disk Mar 20 18:35:25 Tower kernel: ata4: softreset failed (device not ready) Mar 20 18:35:25 Tower kernel: ata4: applying SB600 PMP SRST workaround and retrying Mar 20 18:35:25 Tower kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Mar 20 18:35:25 Tower kernel: ata4.00: HPA detected: current 2930275055, native 2930277168 Mar 20 18:35:25 Tower kernel: ata4.00: ATA-8: WDC WD15EADS-00P8B0, 01.00A01, max UDMA/133 Mar 20 18:35:25 Tower kernel: ata4.00: 2930275055 sectors, multi 0: LBA48 NCQ (depth 31/32), AA Mar 20 18:35:25 Tower kernel: ata4.00: configured for UDMA/133 Mar 20 18:35:25 Tower kernel: scsi 4:0:0:0: Direct-Access ATA WDC WD15EADS-00P 01.0 PQ: 0 ANSI: 5 Mar 20 18:35:25 Tower kernel: sd 4:0:0:0: [sdd] 2930275055 512-byte logical blocks: (1.50 TB/1.36 TiB) Mar 20 18:35:25 Tower kernel: sd 4:0:0:0: [sdd] Write Protect is off Mar 20 18:35:25 Tower kernel: scsi 5:0:0:0: Direct-Access ATA WDC WD1001FALS-7 05.0 PQ: 0 ANSI: 5 Mar 20 18:35:25 Tower kernel: sd 4:0:0:0: [sdd] Mode Sense: 00 3a 00 00 Mar 20 18:35:25 Tower kernel: sd 4:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Mar 20 18:35:25 Tower kernel: sdd: Mar 20 18:35:25 Tower kernel: sd 5:0:0:0: [sde] 1953523055 512-byte logical blocks: (1.00 TB/931 GiB) Mar 20 18:35:25 Tower kernel: sd 5:0:0:0: [sde] Write Protect is off Mar 20 18:35:25 Tower kernel: sd 5:0:0:0: [sde] Mode Sense: 00 3a 00 00 Mar 20 18:35:25 Tower kernel: sd 5:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Mar 20 18:35:25 Tower kernel: sde: sde1 Mar 20 18:35:25 Tower kernel: sd 5:0:0:0: [sde] Attached SCSI disk Mar 20 18:35:25 Tower kernel: sdd1 Mar 20 18:35:25 Tower kernel: sd 4:0:0:0: [sdd] Attached SCSI disk Mar 20 18:35:25 Tower kernel: atiixp 0000:00:14.1: IDE controller (0x1002:0x439c rev 0x00) Mar 20 18:35:25 Tower kernel: ATIIXP_IDE 0000:00:14.1: PCI INT A -> GSI 16 (level, low) -> IRQ 16 Mar 20 18:35:25 Tower kernel: atiixp 0000:00:14.1: not 100%% native mode: will probe irqs later Mar 20 18:35:25 Tower kernel: ide0: BM-DMA at 0xfa00-0xfa07 Mar 20 18:35:25 Tower kernel: atiixp 0000:00:14.1: simplex device: DMA disabled Mar 20 18:35:25 Tower kernel: ide1: DMA disabled

Just out of curiosity, is it worth it to try and kill the drive vs just RMA-ing the thing? Probably going to try a seagate drive since I can get it from amazon pretty quick, 2 days with prime

is there any real benefit using a gree drive as the cache drive? all the talk is 7200 and up, so i was just curious if there is gain. thinking about the warm spare route

Here is a good one. So, I took the new switch out of the equation. It is a TRENDnet TEG-S80G and it gets really great reviews so I am surprised it is the culprit, maybe it is bad. So, I took and plugged directly into my Dlink gigabit switch. I believe it is this one, DGS-2208 8-Port 10/100/1000 Desktop Switch http://www.dlink.com/products/?pid=495. This is also where my desktop system connects to. Between the 2 switches I simply have another network cable, like anything, stringing the devices together. Once I connected to the other switch, I ran my same transfer again and everything went through without a hatch, I have no idea what to make of it. Do the Dlink and Trendnet not play nice together? is it because they are both green devices? I also have a 10/100 dlink switch connected to the Trendnet for some other devices as well, so I dont know if that too possibly has an effect, I dont know. All the connections seem to work fine, it is only when I start to transmit large amounts of data that I have this issue. I copied some smaller files with no issue at all. The Trendnet has a 5 year warranty so I may try to get it replaced, but I am really unsure if that is truly the issue, it is just really strange. I mean if it didnt work, I would simply expect it to fail for all transfers, but the fact that some work and others dont is what i so weird. I have attached another syslog just in case it tells us anything new. I plan to RMA the bad drive tomorrow as well as maybe pick up a replacement from microcenter instead of being without the failing drive for a week, or should I put it back in the array since it isnt failed yet, just some sectors going bad and relocating, at least till the new drive comes? syslog-2011-03-20.txt

OK, I have reverted back to 4.6 and now those 2 drives are in fact back, so that is a plus. Well, I ran my test again that would break things and it did break again, however, this time it came back up on its own. New syslog attached. syslog-2011-03-20.txt

Apparently removing the failing disk was a horrible idea. Now I am seeing this at boot, Model/Serial 65R_WD-WCAVY2217816 65R_WD-WCAVY2136899 00P_WD-WMAVU0856021 00P_WD-WMAVU0526394 <-- was old disk in this slot WDC WD15EADS-00P_WD-WMAVU0526394 <-- current disk in this slot 75J7B0_WD-WMATV2054515 <-- was old disk in this slot WDC WD1001FALS-7_WD-WMATV2054515 <-- current disk in this slot 00MVWB0_WD-WMAZ20082367 00M_WD-WCAZA1264935 00M_WD-WCAZA1253619 What in the world? All I did was remove 1 disk and now the whole system is blowing up. Going to go shut down and wait for assistance, this is crazy. The only thing I will mention is that I did put 4.7 on my flash since I had everything shut down. I figured it couldnt hurt, but maybe that is what caused this. Now that I look at it again, the serial number is right, but it is identifying the disk different. Holy smokes, I hope this is an easy fix, or should I return to 4.6?

Are these safe to buy then? I have been using all WD in my system and one is failing so I want to get it replaced ASAP. Amazon prime or a trip to Microcenter for the Samsungs will be the fastest way to get a new drive, just trying to decide which to get, thanks.

Are the Samsung drives safe as long as you apply the firmware? I just had a drive go bad and I want to get one ASAP and Microcenter has the samsungs for 70 bucks, http://www.microcenter.com/single_product_results.phtml?product_id=0349903 However, if there are issues with them, then obviously I dont want to put it in my system. Thanks

OK, system locked completely again but the screen was off and I couldnt bring it to life to see the tail of the log. Obviously the health of this system is bad. I am curious, as a test, can I just remove my disk 5 from the server and power it back on? I want to test to see if it that is the cause. I figure if I bring it up and everything starts working again, then I will get a new drive in there ASAP. I would assume then I just power down add new disk and saw it is disk 5 and parity will rebuild it...just like with any other drive failure. But the key for me is to get the thing running so I can test and make sure that is what is causing my problem. Drive 5 will need replaced anyway since there are the bad sectors, but I dont want to wait for the new drive just to test to see if that is what was causing my issue. Thoughts?

So if the drive is starting to fail, could that be what causes my lockup? I would assume pull the drive and see what happens? Only weird thing is that drive 5 isn't the one being written to during my file copy.

Just to add a little more information, just took a peek at the smart history page in unRAID and saw the following, Disk 5: *ERROR* - Current_Pending_Sector it is now 134 (error threshold is 5) Could this be as simple as a bad cable of one that came loose during moving, or is it more than likely a bad drive? Dont really want to do anything in fear of making it worse, so I want to wait for direction. Thanks. Got this about my Disk 5, Statistics for /dev/sdf 00MVWB0_WD-WMAZ20082367 smartctl -a -d ata /dev/sdf smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WMAZ20082367 Firmware Version: 50.0AB50 User Capacity: 2,000,398,934,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Sun Mar 20 12:39:10 2011 EDT 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 General SMART Values: Offline data collection status: (0x84) Offline data collection activity was suspended by an interrupting command from host. 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: (37200) 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: ( 2) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3035) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. 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 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 162 161 021 Pre-fail Always - 6875 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 125 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 091 091 000 Old_age Always - 6690 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 11 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 1 193 Load_Cycle_Count 0x0032 129 129 000 Old_age Always - 215086 194 Temperature_Celsius 0x0022 123 115 000 Old_age Always - 27 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 134 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 189 000 Old_age Offline - 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 without error 00% 6690 - # 2 Short offline Completed without error 00% 6656 - 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.

Well, this is something interesting. I just unplugged the network cable and left it for a bit and then the console became active again... Finally, I plugged the cable back in and things remained up, so I remoted in and was able to pull the syslog down without hard rebooting. It is now attached, I see some red Emask errors which I can only assume means something bad. Also, how do I exit the tail command now that I was able to pull the log or will I still need that? Le me know if I should invoke another failure and capture. Thanks. syslog-2011-03-20.txt

Yeah, but that is the crazy thing, none of this should make the server completely hang where the system does not even accept input from the keyboard connected directly to the server. It seems the entire system is frozen. One thing I did find is a user with a similar issue and he said he had a bad drive. Can a bad drive cause the system to hang like this? I know looking at the disk after a hard reset they all show healthy. Because I am not able to get any logs, I was thinking about a hard reset so I can access the system again. If there is a drive issue, would the log indicate anything right after boot? If I could make any suggestion at all, it would be that instead of the log file being over written, that instead it would copy the old logs into a new folder at time of boot and then start a new log. This way when the server crashes and hangs like this we can still get to the logs after rebooting to hopefully find a cause. You would simply date stamp the folder with the time and date at the time of boot. No idea what it would involve but I think it would be a great enhancement feature if it could be done.

I recently moved my devices around at home and re-configured my network and now my 4.6 device appears to be blowing up when I start copying files to it. The system boots and I can ping it all day, but as soon as I start moving data to it, I lose connection to the server and the copy fails and then sometimes the connection returns and other times it may not. This never used to be an issue in the past, and the only real change is a new gigabit switch. All my other network connections seem to stay solid, but I also am not moving 20gig files between the rest. Just not sure where this issue could be creeping in from since everything used to function great until I moved my equipment around, but the overall configuration is essentially the same still. I thought for a second it was because of a parity check, but I stopped it and it still fails. It really makes zero sense, so I am in search of some assistance. I cannot even attach the log because the system is just frozen. When I look at the light on the switch it is flickering super fast while the rest just flash like normal when they transmit data. The unraid one is certainly messed up, but I am not understanding it. Does anyone have any thoughts? The system is locked where even the console doesnt work, the keyboard right at the system does not work. A hard reset seems as though it would be the only fix, which i already tried once.

With the newer versions, I believe even the logging and messages were updated. I know I used to run a super old version that did not display the best results, but the new version is awesome. I mean really, can it get any easier to understand than this? Awesome work! No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 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.

Good news. Thanks for the continued effort. I will install jumpered drives this time around as the preclear is almost complete with Jumper in place. No sense shutting down to remove jumpers to format again, so I will just run 4.7 and then install non-jumpered "-A" cleared disk next time around... Great work!

Thanks peter. Maybe I did a bad job explaining. The third drive with data has the jumper and it was pre-cleared so it should be aligned properly, just like the newest drive I formatted most recently that is still not in the array. I am most worried about performance between the 2methods. Jumper in place vs no jumper and 4k alignment with -A formatting.

I'm referring to smakovits' post where he stated he had a jumpered and pre-cleaded EARS drive. I recommended he just install that drive as is and use it. It will be partitioned at sector 63 and it will be aligned via the jumper which shifts the partition at sector 63 so it is really at sector 64. It's ready to go and removing the jumper and pre-clearing it again has no benefits other than being able to sleep at night not worrying about that stray jumper being left on the disk. In other words, removing the jumper is nothing but a waste of time for no gains. Peter I was thinking he had precleared with the 4K alignment AND the jumper on. If the original preclear was done with the 63 sector alignment AND the jumper on, you're right, there would be no need to re-preclear it. Yes guys, I want to clarify. I have 2 new disks and one existing in array with data. All 3 have jumper currently in place. The one with the data was precleared regular, with the older preclear when the -A didnt even exist. One of the 2 new drives was also precleared without the -A, but with the jumper. This disk is not in the array yet. The third disk also has the jumper on it, but nothing has been done to it in the way of preclear. The talk about the small files, then is that even relevant, or was that because somebody was misunderstanding my setup? I mean if there is truly no gain, then I guess I should just leave the disk already in the array alone. However, the other 2 not yet in the array, I guess maybe remove the jumper and format or is that just dumb because it is a complete waste of time and I should just leave things running and worry about it the next time I need to add disk and just power things down then.

I am thinking to install 4.7 B1. I am going to keep my one drive with the jumper in place, at least for now... So, I have 2 new drive, both not in the array yet. Both have the jumper right now and one has been pre-cleared. If I now go back and remove the jumper from both, I will need to run pre-clear with -A on the one that hasnt been touched, but what about the other that is already cleared? Do I have to run the whole clear again for 24 hours, or is there a faster way to handle this?

Yes, basically all data on that physical disk is lost if the jumper setting is changed. It will if it can write to the drive. Most times the drive will lock up and not be readable or writable until power cycled. It has been determined that if you zero out the first few sectors the disk can be made to work once more (after a power cycle) No. Up to you. -A does not "format" It puts a pre-clear signature in place after completely writing zeros to the drive that asks that the partition that will be created by unRAID start on sector 64. Again up to you. Electrically, the jumper was adding 1 to the sector numbers being requested. Sector 63 actually accessed a 4k aligned sector 64. Sector 64 requested accessed sector 65, etc. You remove the jumper and a request for the data that is on sector 63 gets what is on 63... In other words the data is all offset and you get back garbage instead of what is expected. None of the above. If on 4.7 onward, select the MBR 4k-aligned setting in the settings page. Do not add or delete existing jumpers on drives already in the array. Do NOT add jumpers to new AF drives. Use the "-A" option to the pre-clear script. Joe L. Perfect, Thanks for the response Joe. So basically it is up to me to do beta or not. Beyond that, I just need to not be so OCD that I need all jumpered or not jumpered disks. I can add my disks now on 4.6 and when 4.7 goes gold, I just set the 4k setting and moving forward new disks have no jumper, while leaving the rest alone. Or, if it is really going to bother me. I can go to 4.7 beta now and remove the jumpers. Either way my data is safe, it is more a matter of how crazy I am about keeping things the same across the board. Perfect, it is all up to me... Thanks again for the response. Give me a better understanding of it all.

Your drive is fine. No re-allocated sectors, and none pending re-allocation. Great, thanks. Is there anything obvious to look at? If there is an issue, will it report a fail vs pass? Also, is there a log that only contains the preclear log vs using the whole syslog? If not, it would be a good feature add. thanks again

I guess I am a bit confused. Is all data lost on a disk when the jumper is removed and changed to advanced format? However, parity will then rebuild the drive and things will be OK? Next, does it matter if the Parity drive is AF vs not when rebuilding the new disk? Can I test with 4.7b1 with drives with jumper in place before taking the plunge and pulling it? I have 2 new drives and am trying to decide what to do. Do I upgrade and format with the -A or wait for gold release? If I do remove the jumper of an existing drive, what is actually happening? the drive gets formated, data lost and parity rebuilds? Or am I way off and missing something completely about the process. I have 1 advanced format drive now and want to add 2, but I want the least work moving forward. My understanding is that it really doesn't matter, but what is the real opinion? Is this upgrade more for those without WD that can use the jumper fix or is 64bit AF recommended for all moving forward?

OK, I always thought it would be obvious, but after some reading I have gotten paranoid and now I dont know what to do with these logs. I completed preclear on a drive and I believe I have the logs needed to tell me if I am safe: an 16 21:30:42 Tower preclear_disk-start[6075]: === START OF INFORMATION SECTION === Jan 16 21:30:42 Tower preclear_disk-start[6075]: Device Model: WDC WD20EARS-00MVWB0 Jan 16 21:30:42 Tower preclear_disk-start[6075]: Serial Number: WD-WCAZA1264935 Jan 16 21:30:42 Tower preclear_disk-start[6075]: Firmware Version: 51.0AB51 Jan 16 21:30:42 Tower preclear_disk-start[6075]: User Capacity: 2,000,398,934,016 bytes Jan 16 21:30:42 Tower preclear_disk-start[6075]: Device is: Not in smartctl database [for details use: -P showall] Jan 16 21:30:42 Tower preclear_disk-start[6075]: ATA Version is: 8 Jan 16 21:30:42 Tower preclear_disk-start[6075]: ATA Standard is: Exact ATA specification draft version not indicated Jan 16 21:30:42 Tower preclear_disk-start[6075]: Local Time is: Sun Jan 16 21:30:41 2011 EST Jan 16 21:30:42 Tower preclear_disk-start[6075]: SMART support is: Available - device has SMART capability. Jan 16 21:30:42 Tower preclear_disk-start[6075]: SMART support is: Enabled Jan 16 21:30:42 Tower preclear_disk-start[6075]: Jan 16 21:30:42 Tower preclear_disk-start[6075]: === START OF READ SMART DATA SECTION === Jan 16 21:30:42 Tower preclear_disk-start[6075]: SMART overall-health self-assessment test result: PASSED Jan 16 21:30:42 Tower preclear_disk-start[6075]: Jan 16 21:30:42 Tower preclear_disk-start[6075]: General SMART Values: Jan 16 21:30:42 Tower preclear_disk-start[6075]: Offline data collection status: (0x80)^IOffline data collection activity Jan 16 21:30:42 Tower preclear_disk-start[6075]: ^I^I^I^I^Iwas never started. Jan 16 21:30:42 Tower preclear_disk-start[6075]: ^I^I^I^I^IAuto Offline Data Collection: Enabled. Jan 16 21:30:42 Tower preclear_disk-start[6075]: Self-test execution status: ( 0)^IThe previous self-test routine completed Jan 16 21:30:42 Tower preclear_disk-start[6075]: ^I^I^I^I^Iwithout error or no self-test has ever Jan 16 21:30:42 Tower preclear_disk-start[6075]: ^I^I^I^I^Ibeen run. Jan 16 21:30:42 Tower preclear_disk-start[6075]: Total time to complete Offline Jan 16 21:30:42 Tower preclear_disk-start[6075]: data collection: ^I^I (38100) seconds. Jan 16 21:30:42 Tower preclear_disk-start[6075]: Offline data collection Jan 16 21:30:42 Tower preclear_disk-start[6075]: capabilities: ^I^I^I (0x7b) SMART execute Offline immediate. Jan 16 21:30:42 Tower preclear_disk-start[6075]: ^I^I^I^I^IAuto Offline data collection on/off support. Jan 16 21:30:42 Tower preclear_disk-start[6075]: ^I^I^I^I^ISuspend Offline collection upon new Jan 16 21:30:42 Tower preclear_disk-start[6075]: ^I^I^I^I^Icommand. Jan 16 21:30:42 Tower preclear_disk-start[6075]: ^I^I^I^I^IOffline surface scan supported. Jan 16 21:30:42 Tower preclear_disk-start[6075]: ^I^I^I^I^ISelf-test supported. Jan 16 21:30:42 Tower preclear_disk-start[6075]: ^I^I^I^I^IConveyance Self-test supported. Jan 16 21:30:42 Tower preclear_disk-start[6075]: ^I^I^I^I^ISelective Self-test supported. Jan 16 21:30:42 Tower preclear_disk-start[6075]: SMART capabilities: (0x0003)^ISaves SMART data before entering Jan 16 21:30:42 Tower preclear_disk-start[6075]: ^I^I^I^I^Ipower-saving mode. Jan 16 21:30:42 Tower preclear_disk-start[6075]: ^I^I^I^I^ISupports SMART auto save timer. Jan 16 21:30:42 Tower preclear_disk-start[6075]: Error logging capability: (0x01)^IError logging supported. Jan 16 21:30:42 Tower preclear_disk-start[6075]: ^I^I^I^I^IGeneral Purpose Logging supported. Jan 16 21:30:42 Tower preclear_disk-start[6075]: Short self-test routine Jan 16 21:30:42 Tower preclear_disk-start[6075]: recommended polling time: ^I ( 2) minutes. Jan 16 21:30:42 Tower preclear_disk-start[6075]: Extended self-test routine Jan 16 21:30:42 Tower preclear_disk-start[6075]: recommended polling time: ^I ( 255) minutes. Jan 16 21:30:42 Tower preclear_disk-start[6075]: Conveyance self-test routine Jan 16 21:30:42 Tower preclear_disk-start[6075]: recommended polling time: ^I ( 5) minutes. Jan 16 21:30:42 Tower preclear_disk-start[6075]: SCT capabilities: ^I (0x3035)^ISCT Status supported. Jan 16 21:30:42 Tower preclear_disk-start[6075]: ^I^I^I^I^ISCT Feature Control supported. Jan 16 21:30:42 Tower preclear_disk-start[6075]: ^I^I^I^I^ISCT Data Table supported. Jan 16 21:30:42 Tower preclear_disk-start[6075]: Jan 16 21:30:42 Tower preclear_disk-start[6075]: SMART Attributes Data Structure revision number: 16 Jan 16 21:30:42 Tower preclear_disk-start[6075]: Vendor Specific SMART Attributes with Thresholds: Jan 16 21:30:42 Tower preclear_disk-start[6075]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Jan 16 21:30:42 Tower preclear_disk-start[6075]: 1 Raw_Read_Error_Rate 0x002f 100 253 051 Pre-fail Always - 0 Jan 16 21:30:42 Tower preclear_disk-start[6075]: 3 Spin_Up_Time 0x0027 168 168 021 Pre-fail Always - 6575 Jan 16 21:30:42 Tower preclear_disk-start[6075]: 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 10 Jan 16 21:30:42 Tower preclear_disk-start[6075]: 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 Jan 16 21:30:42 Tower preclear_disk-start[6075]: 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 Jan 16 21:30:42 Tower preclear_disk-start[6075]: 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 0 Jan 16 21:30:42 Tower preclear_disk-start[6075]: 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 Jan 16 21:30:42 Tower preclear_disk-start[6075]: 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 Jan 16 21:30:42 Tower preclear_disk-start[6075]: 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 8 Jan 16 21:30:42 Tower preclear_disk-start[6075]: 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 7 Jan 16 21:30:42 Tower preclear_disk-start[6075]: 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 9 Jan 16 21:30:42 Tower preclear_disk-start[6075]: 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 Jan 16 21:30:42 Tower preclear_disk-start[6075]: 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 Jan 16 21:30:42 Tower preclear_disk-start[6075]: 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 Jan 16 21:30:42 Tower preclear_disk-start[6075]: 199 UDMA_CRC_Error_Count 0x0032 200 253 000 Old_age Always - 0 Jan 16 21:30:42 Tower preclear_disk-start[6075]: 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 ============================================================================ Jan 18 04:51:10 Tower preclear_disk-diff[24304]: == Jan 18 04:51:10 Tower preclear_disk-diff[24304]: == Disk /dev/sdh has been successfully precleared Jan 18 04:51:10 Tower preclear_disk-diff[24304]: == Jan 18 04:51:10 Tower preclear_disk-diff[24304]: == Ran 1 preclear-disk cycle Jan 18 04:51:10 Tower preclear_disk-diff[24304]: == Jan 18 04:51:10 Tower preclear_disk-diff[24304]: == Using :Read block size = 8225280 Bytes Jan 18 04:51:10 Tower preclear_disk-diff[24304]: == Last Cycle's Pre Read Time : 8:04:15 (68 MB/s) Jan 18 04:51:10 Tower preclear_disk-diff[24304]: == Last Cycle's Zeroing time : 8:12:22 (67 MB/s) Jan 18 04:51:10 Tower preclear_disk-diff[24304]: == Last Cycle's Post Read Time : 15:02:37 (36 MB/s) Jan 18 04:51:10 Tower preclear_disk-diff[24304]: == Last Cycle's Total Time : 31:20:29 Jan 18 04:51:10 Tower preclear_disk-diff[24304]: == Jan 18 04:51:10 Tower preclear_disk-diff[24304]: == Total Elapsed Time 31:20:29 Jan 18 04:51:10 Tower preclear_disk-diff[24304]: == Jan 18 04:51:10 Tower preclear_disk-diff[24304]: == Disk Start Temperature: 27C Jan 18 04:51:10 Tower preclear_disk-diff[24304]: == Jan 18 04:51:10 Tower preclear_disk-diff[24304]: == Current Disk Temperature: 33C, Jan 18 04:51:10 Tower preclear_disk-diff[24304]: == Jan 18 04:51:10 Tower preclear_disk-diff[24304]: ============================================================================ Jan 18 04:51:10 Tower preclear_disk-diff[24304]: S.M.A.R.T. error count differences detected after pre-clear Jan 18 04:51:10 Tower preclear_disk-diff[24304]: note, some 'raw' values may change, but not be an indication of a problem Jan 18 04:51:10 Tower preclear_disk-diff[24304]: 19,20c19,20 Jan 18 04:51:10 Tower preclear_disk-diff[24304]: < Offline data collection status: (0x80)^IOffline data collection activity Jan 18 04:51:10 Tower preclear_disk-diff[24304]: < ^I^I^I^I^Iwas never started. Jan 18 04:51:10 Tower preclear_disk-diff[24304]: --- Jan 18 04:51:10 Tower preclear_disk-diff[24304]: > Offline data collection status: (0x84)^IOffline data collection activity Jan 18 04:51:10 Tower preclear_disk-diff[24304]: > ^I^I^I^I^Iwas suspended by an interrupting command from host. Jan 18 04:51:10 Tower preclear_disk-diff[24304]: 54c54 Jan 18 04:51:10 Tower preclear_disk-diff[24304]: < 1 Raw_Read_Error_Rate 0x002f 100 253 051 Pre-fail Always - 0 Jan 18 04:51:10 Tower preclear_disk-diff[24304]: --- Jan 18 04:51:10 Tower preclear_disk-diff[24304]: > 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 Jan 18 04:51:10 Tower preclear_disk-diff[24304]: 58c58 Jan 18 04:51:10 Tower preclear_disk-diff[24304]: < 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 Jan 18 04:51:10 Tower preclear_disk-diff[24304]: --- Jan 18 04:51:10 Tower preclear_disk-diff[24304]: > 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 Jan 18 04:51:10 Tower preclear_disk-diff[24304]: 63c63 Jan 18 04:51:10 Tower preclear_disk-diff[24304]: < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 9 Jan 18 04:51:10 Tower preclear_disk-diff[24304]: --- Jan 18 04:51:10 Tower preclear_disk-diff[24304]: > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 10 Jan 18 04:51:10 Tower preclear_disk-diff[24304]: 67c67 Jan 18 04:51:10 Tower preclear_disk-diff[24304]: < 199 UDMA_CRC_Error_Count 0x0032 200 253 000 Old_age Always - 0 Jan 18 04:51:10 Tower preclear_disk-diff[24304]: --- Jan 18 04:51:10 Tower preclear_disk-diff[24304]: > 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 Jan 18 04:51:10 Tower preclear_disk-diff[24304]: