hunter69 Posted October 27, 2010 Share Posted October 27, 2010 Here are the results from a drive I had in my whs. I was thinking I could ude it as a cache disk. ============================================================================ Oct 24 02:36:35 Tower preclear_disk-diff[14738]: S.M.A.R.T. error count differences detected after pre-clear Oct 24 02:36:35 Tower preclear_disk-diff[14738]: note, some 'raw' values may change, but not be an indication of a problem Oct 24 02:36:35 Tower preclear_disk-diff[14738]: 54c54 Oct 24 02:36:35 Tower preclear_disk-diff[14738]: < 1 Raw_Read_Error_Rate 0x000f 101 099 006 Pre-fail Always - 3525934 Oct 24 02:36:35 Tower preclear_disk-diff[14738]: --- Oct 24 02:36:35 Tower preclear_disk-diff[14738]: > 1 Raw_Read_Error_Rate 0x000f 118 099 006 Pre-fail Always - 171199195 Oct 24 02:36:35 Tower preclear_disk-diff[14738]: 58c58 Oct 24 02:36:35 Tower preclear_disk-diff[14738]: < 7 Seek_Error_Rate 0x000f 078 060 030 Pre-fail Always - 76815635 Oct 24 02:36:35 Tower preclear_disk-diff[14738]: --- Oct 24 02:36:35 Tower preclear_disk-diff[14738]: > 7 Seek_Error_Rate 0x000f 078 060 030 Pre-fail Always - 76912546 Oct 24 02:36:35 Tower preclear_disk-diff[14738]: 64,66c64,66 Oct 24 02:36:35 Tower preclear_disk-diff[14738]: < 189 High_Fly_Writes 0x003a 039 039 000 Old_age Always - 61 Oct 24 02:36:35 Tower preclear_disk-diff[14738]: < 190 Airflow_Temperature_Cel 0x0022 072 055 045 Old_age Always - 28 (Lifetime Min/Max 23/28) Oct 24 02:36:35 Tower preclear_disk-diff[14738]: < 195 Hardware_ECC_Recovered 0x001a 029 025 000 Old_age Always Oct 24 02:36:35 Tower preclear_disk-diff[14738]: --- Oct 24 02:36:35 Tower preclear_disk-diff[14738]: > 189 High_Fly_Writes 0x003a 031 031 000 Old_age Always - 69 Oct 24 02:36:35 Tower preclear_disk-diff[14738]: > 190 Airflow_Temperature_Cel 0x0022 069 055 045 Old_age Always - 31 (Lifetime Min/Max 23/34) Oct 24 02:36:35 Tower preclear_disk-diff[14738]: > 195 Hardware_ECC_Recovered 0x001a 055 025 000 Old_age Always Oct 24 02:36:35 Tower preclear_disk-diff[14738]: I am not sure how to read these results. Do you think I could possibly have problems or do you think it is good? Quote Link to comment
talmania Posted October 30, 2010 Share Posted October 30, 2010 Here are the results from a drive I had in my whs. I was thinking I could ude it as a cache disk. ============================================================================ Oct 24 02:36:35 Tower preclear_disk-diff[14738]: S.M.A.R.T. error count differences detected after pre-clear Oct 24 02:36:35 Tower preclear_disk-diff[14738]: note, some 'raw' values may change, but not be an indication of a problem Oct 24 02:36:35 Tower preclear_disk-diff[14738]: 54c54 Oct 24 02:36:35 Tower preclear_disk-diff[14738]: < 1 Raw_Read_Error_Rate 0x000f 101 099 006 Pre-fail Always - 3525934 Oct 24 02:36:35 Tower preclear_disk-diff[14738]: --- Oct 24 02:36:35 Tower preclear_disk-diff[14738]: > 1 Raw_Read_Error_Rate 0x000f 118 099 006 Pre-fail Always - 171199195 Oct 24 02:36:35 Tower preclear_disk-diff[14738]: 58c58 Oct 24 02:36:35 Tower preclear_disk-diff[14738]: < 7 Seek_Error_Rate 0x000f 078 060 030 Pre-fail Always - 76815635 Oct 24 02:36:35 Tower preclear_disk-diff[14738]: --- Oct 24 02:36:35 Tower preclear_disk-diff[14738]: > 7 Seek_Error_Rate 0x000f 078 060 030 Pre-fail Always - 76912546 Oct 24 02:36:35 Tower preclear_disk-diff[14738]: 64,66c64,66 Oct 24 02:36:35 Tower preclear_disk-diff[14738]: < 189 High_Fly_Writes 0x003a 039 039 000 Old_age Always - 61 Oct 24 02:36:35 Tower preclear_disk-diff[14738]: < 190 Airflow_Temperature_Cel 0x0022 072 055 045 Old_age Always - 28 (Lifetime Min/Max 23/28) Oct 24 02:36:35 Tower preclear_disk-diff[14738]: < 195 Hardware_ECC_Recovered 0x001a 029 025 000 Old_age Always Oct 24 02:36:35 Tower preclear_disk-diff[14738]: --- Oct 24 02:36:35 Tower preclear_disk-diff[14738]: > 189 High_Fly_Writes 0x003a 031 031 000 Old_age Always - 69 Oct 24 02:36:35 Tower preclear_disk-diff[14738]: > 190 Airflow_Temperature_Cel 0x0022 069 055 045 Old_age Always - 31 (Lifetime Min/Max 23/34) Oct 24 02:36:35 Tower preclear_disk-diff[14738]: > 195 Hardware_ECC_Recovered 0x001a 055 025 000 Old_age Always Oct 24 02:36:35 Tower preclear_disk-diff[14738]: I am not sure how to read these results. Do you think I could possibly have problems or do you think it is good? Just finished my preclear run as well and mine look extremely simlar to yours. Not sure what it means but it reports the same items. Quote Link to comment
justaguy Posted November 3, 2010 Share Posted November 3, 2010 Oct 24 02:36:35 Tower preclear_disk-diff[14738]: < 1 Raw_Read_Error_Rate 0x000f 101 099 006 Pre-fail Always - 3525934 Oct 24 02:36:35 Tower preclear_disk-diff[14738]: > 1 Raw_Read_Error_Rate 0x000f 118 099 006 Pre-fail Always - 171199195 The rows with "<" are the readings before the test, the ">" are the readings after the test. So, your raw read error rate *improved* over the course of the test. For SMART parameters, you are supposed to look at the "normalized" numbers of "101 099 006" in the middle. The value 101 is the current reading of your drive (lower is bad), and the value 099 is the lowest (worst case) it's had in the distant past. The value 006 is not a reading from the status of *your* drive, rather it is considered to be the threshold when you should consider your drive to be junk. When the 101 or 099 values drop below 006, throw out the drive. For Seagate drives, the "raw" value (number after the dash -) is not a direct count for some of the SMART parameters. For raw read error rate, you cannot interpret that value directly, because it is some encoding of various data. Oct 24 02:36:35 Tower preclear_disk-diff[14738]: < 7 Seek_Error_Rate 0x000f 078 060 030 Pre-fail Always - 76815635 Oct 24 02:36:35 Tower preclear_disk-diff[14738]: > 7 Seek_Error_Rate 0x000f 078 060 030 Pre-fail Always - 76912546 The seek error rate is unchanged. Again, the raw value cannot be interpreted. The value 078 is a good measure above the threshold of 030. Oct 24 02:36:35 Tower preclear_disk-diff[14738]: < 189 High_Fly_Writes 0x003a 039 039 000 Old_age Always - 61 Oct 24 02:36:35 Tower preclear_disk-diff[14738]: > 189 High_Fly_Writes 0x003a 031 031 000 Old_age Always - 69 High fly writes are a sign the disk head comes too high off the media to do a reliable write. The normalized value got slightly worse over the course of the test, dropping from 039 to 031, but you don't need to worry until it reaches 000. The count of these incidents increased from 61 to 69. Due to the slight increase, you might be a bit but not overly concerned. You should continue to monitor this value. Oct 24 02:36:35 Tower preclear_disk-diff[14738]: > 190 Airflow_Temperature_Cel 0x0022 069 055 045 Old_age Always - 31 (Lifetime Min/Max 23/34) Oct 24 02:36:35 Tower preclear_disk-diff[14738]: < 190 Airflow_Temperature_Cel 0x0022 072 055 045 Old_age Always - 28 (Lifetime Min/Max 23/28) Temperatures look good and cool. Oct 24 02:36:35 Tower preclear_disk-diff[14738]: < 195 Hardware_ECC_Recovered 0x001a 029 025 000 Old_age Always Oct 24 02:36:35 Tower preclear_disk-diff[14738]: > 195 Hardware_ECC_Recovered 0x001a 055 025 000 Old_age Always ECC recovery rate has actually improved from 029 to 055. The worst value in drive's history is 025, and you didn't even come close to that. Worry only when this value reaches 000, or if it starts to reach new minimums. Just to note, this thread should be regarding discussion of the script itself, not about interpreting its results. The thread for interpreting results is here: http://lime-technology.com/forum/index.php?topic=4068.0 Quote Link to comment
ix400 Posted November 4, 2010 Share Posted November 4, 2010 Hi, let's say I have a running array with 6 discs. When I then mount a 7th disc to my rig, will this one then be the only disc that shows up in the preclear script, since it is the only disc not being part of the array at that point? I don't want to preclear an array disc by accident. Cheers, Chris Quote Link to comment
heffneil Posted November 4, 2010 Share Posted November 4, 2010 So I precleared my WD20Ears drives and I just got my jumpers. When I went to preclear the drive again I get an error in the script on line 550 or something. I assume it is a problem because the disk was precleared once before. How do I remedy this situation? format? If so how:) Thanks! Neil Quote Link to comment
heffneil Posted November 4, 2010 Share Posted November 4, 2010 Ok I fdisked the one drive and got it pre-clearing now. Since I have filled up the 6 ports on board I have moved to the Supermicro 8 port card. In the unraid web interface I see the drives listed. When I go to clear them I get a message saying they are not a block device and it cancels out. Also I can't run fdisk on these drives. Any thoughts? Thanks! Quote Link to comment
Joe L. Posted November 4, 2010 Share Posted November 4, 2010 So I precleared my WD20Ears drives and I just got my jumpers. When I went to preclear the drive again I get an error in the script on line 550 or something.It would have helped if you had captured the details of the error. I could have tried to figure out what happened on your server. I assume it is a problem because the disk was precleared once before.Nope... it can be pre-cleared as many times as you like. It had something to do with you adding the jumper and the resulting geometry being reported weirdly How do I remedy this situation? format? If so how:) Thanks! Neil Apparently you used fdisk to overwrite the partition table... If you saved the errors from the prior attempt at using preclear_disk.sh on the newly jumpered disk, post them. Joe L. Quote Link to comment
heffneil Posted November 4, 2010 Share Posted November 4, 2010 I was on console so I couldn't copy the error. Here is the error below: Elapsed Time: 0:00:00 ./preclear_disk.sh: line 550: 1+( 1913351618)%() : syntax error: operand expected (error token is ") ") Thanks, Neil Quote Link to comment
Joe L. Posted November 4, 2010 Share Posted November 4, 2010 I was on console so I couldn't copy the error. Here is the error below: Elapsed Time: 0:00:00 ./preclear_disk.sh: line 550: 1+( 1913351618)%() : syntax error: operand expected (error token is ") ") Thanks, Neil That helps... I know what math failed... In the empty "()" should have been the number of blocks to be read on the disk based on the geometry returned from the fdisk -l /dev/sdX command. The "blocks" is calculated based on the Total Bytes as reported on the fdisk line that starts with "Disk" divided by the Units as reported by fdisk. It is too late now, but if you have another disk you'll be putting through the same process, capture the output of fdisk -l /dev/sdX for me. (using of course the correct device name instead of sdX) Joe L. Quote Link to comment
heffneil Posted November 4, 2010 Share Posted November 4, 2010 Wait what is too late now? I need to pre-clear this disk and get it in use. How do I do that? Thanks, Neil Quote Link to comment
Joe L. Posted November 4, 2010 Share Posted November 4, 2010 Wait what is too late now? I need to pre-clear this disk and get it in use. How do I do that? Thanks, Neil If you have not yet run the "dd" command on the drive, and it still fails when you try to run the pre-clear script, or, if you have a second drive that acts the same as the first, please post the output of fdisk -l /dev/sdX (with sdX being the correct device on your server) I thought you had already done those steps, so I'd not get to see the output that crashes the preclear_disk.sh script. That's why I said too late now. Too late for me to have you help me make the program better. Quote Link to comment
heffneil Posted November 4, 2010 Share Posted November 4, 2010 Ok I bought 3 of these drives without jumpers. I then pre-cleared all of them originally and they worked when plugged in to the on board SATA controller. I ordered some seagates and put them in its place and had to wait for the supermicro 8 port card to show up. Now I have ONE WD on the onboard that I am currently pre-clearing without incident after formatting. The other two are now on the supermicro card and it isn't working however when I see devices in the web interface it shows the drives! Quote Link to comment
heffneil Posted November 4, 2010 Share Posted November 4, 2010 fdisk -l /dev/sdb has no output? After running it I still can't pre-clear the disk. Thanks! Quote Link to comment
Joe L. Posted November 4, 2010 Share Posted November 4, 2010 fdisk -l /dev/sdb has no output? After running it I still can't pre-clear the disk. Thanks! Now that is interesting... The fdisk command does not change the disk in any way, it just reports the existing partitioning. I've never seen it report nothing. It would explain why the preclear script could not figure out the block size. What output do you get with dd if=/dev/sdb count=2 | od -x -A d and sfdisk -l /dev/sdb Joe L. Quote Link to comment
heffneil Posted November 4, 2010 Share Posted November 4, 2010 root@Storage:/boot# dd if=/dev/sdb count=2 | od -x -A d dd: reading `/dev/sdb': Input/output error 0+0 records in 0+0 records out 0000000 0 bytes (0 B) copied, 0.00323911 s, 0.0 kB/s root@Storage:/boot# sfdisk -l /dev/sdb Disk /dev/sdb: 243201 cylinders, 255 heads, 63 sectors/track read: Input/output error sfdisk: read error on /dev/sdb - cannot read sector 0 /dev/sdb: unrecognized partition table type No partitions found Quote Link to comment
heffneil Posted November 5, 2010 Share Posted November 5, 2010 Joe any idea here? Looks like there is a problem with that card. SUPERMICRO AOC-SASLP-MV8 is what I am attempting to use? Thanks, Neil Quote Link to comment
papnikol Posted November 5, 2010 Share Posted November 5, 2010 I was on console so I couldn't copy the error. Here is the error below: Elapsed Time: 0:00:00 ./preclear_disk.sh: line 550: 1+( 1913351618)%() : syntax error: operand expected (error token is ") ") Thanks, Neil That helps... I know what math failed... In the empty "()" should have been the number of blocks to be read on the disk based on the geometry returned from the fdisk -l /dev/sdX command. The "blocks" is calculated based on the Total Bytes as reported on the fdisk line that starts with "Disk" divided by the Units as reported by fdisk. It is too late now, but if you have another disk you'll be putting through the same process, capture the output of fdisk -l /dev/sdX for me. (using of course the correct device name instead of sdX) Joe L. Joe I have to report a similar error: I bought a new EARS and i used the jumper. the preread reached 99% and then stuck I stopped it and tried to rerun preclear This is what i get: root@Tower:/dev# /boot/preclear_disk.sh /dev/sdc BLKRRPART: Input/output error Pre-Clear unRAID Disk ######################################################################## ######################################################################## Are you absolutely sure you want to clear this drive? (Answer Yes to continue. Capital 'Y', lower case 'es'): Yes /boot/preclear_disk.sh: line 415: [: : integer expression expected /boot/preclear_disk.sh: line 436: let: blocks=( / ): syntax error: operand expected (error token is "/ )") /boot/preclear_disk.sh: line 498: let: bytes_read=(0 * ): syntax error: operand expected (error token is ")") /boot/preclear_disk.sh: line 499: let: br=( * 100): syntax error: operand expected (error token is "* 100)") /boot/preclear_disk.sh: line 500: let: percent_read=( / ): syntax error: operand expected (error token is "/ )") /boot/preclear_disk.sh: line 505: [: -gt: unary operator expected =========================================================================== = unRAID server Pre-Clear disk /dev/sdc = cycle 1 of 1 = Disk Pre-Read in progress: % complete = ( bytes of read ) = = = = = = = = = = Elapsed Time: 0:00:01 /boot/preclear_disk.sh: line 550: 1+( 2575561687)%() : syntax error: operand expected (error token is ") ") ============================================================================ == == Disk /dev/sdc has been successfully precleared == ============================================================================ root@Tower:/dev# I may add that there is no partition of my Hard drive and that i followed the same procedure with a same disk few days ago and it worked fine... Quote Link to comment
Joe L. Posted November 5, 2010 Share Posted November 5, 2010 I was on console so I couldn't copy the error. Here is the error below: Elapsed Time: 0:00:00 ./preclear_disk.sh: line 550: 1+( 1913351618)%() : syntax error: operand expected (error token is ") ") Thanks, Neil That helps... I know what math failed... In the empty "()" should have been the number of blocks to be read on the disk based on the geometry returned from the fdisk -l /dev/sdX command. The "blocks" is calculated based on the Total Bytes as reported on the fdisk line that starts with "Disk" divided by the Units as reported by fdisk. It is too late now, but if you have another disk you'll be putting through the same process, capture the output of fdisk -l /dev/sdX for me. (using of course the correct device name instead of sdX) Joe L. Joe I have to report a similar error: I bought a new EARS and i used the jumper. the preread reached 99% and then stuck I stopped it and tried to rerun preclear This is what i get: root@Tower:/dev# /boot/preclear_disk.sh /dev/sdc BLKRRPART: Input/output error Pre-Clear unRAID Disk ######################################################################## ######################################################################## Are you absolutely sure you want to clear this drive? (Answer Yes to continue. Capital 'Y', lower case 'es'): Yes /boot/preclear_disk.sh: line 415: [: : integer expression expected /boot/preclear_disk.sh: line 436: let: blocks=( / ): syntax error: operand expected (error token is "/ )") /boot/preclear_disk.sh: line 498: let: bytes_read=(0 * ): syntax error: operand expected (error token is ")") /boot/preclear_disk.sh: line 499: let: br=( * 100): syntax error: operand expected (error token is "* 100)") /boot/preclear_disk.sh: line 500: let: percent_read=( / ): syntax error: operand expected (error token is "/ )") /boot/preclear_disk.sh: line 505: [: -gt: unary operator expected =========================================================================== = unRAID server Pre-Clear disk /dev/sdc = cycle 1 of 1 = Disk Pre-Read in progress: % complete = ( bytes of read ) = = = = = = = = = = Elapsed Time: 0:00:01 /boot/preclear_disk.sh: line 550: 1+( 2575561687)%() : syntax error: operand expected (error token is ") ") ============================================================================ == == Disk /dev/sdc has been successfully precleared == ============================================================================ root@Tower:/dev# I may add that there is no partition of my Hard drive and that i followed the same procedure with a same disk few days ago and it worked fine... Now that I know what to look for in the script I can code to detect when fdisk returns no output. Obviously the disk had not been successfully precleared. Joe L. Quote Link to comment
papnikol Posted November 5, 2010 Share Posted November 5, 2010 Now that I know what to look for in the script I can code to detect when fdisk returns no output. Obviously the disk had not been successfully precleared. Joe L. Do you have any advice as to how i should proceed? Or should I wait until you had a look at the code? Quote Link to comment
Joe L. Posted November 5, 2010 Share Posted November 5, 2010 What output do you get with fdisk -l /dev/sdc and hdparm -I /dev/sdc and dd if=/dev/sdc count=2 | od -x -A d and sfdisk -l /dev/sdc and smartctl -d ata -a /dev/sdc Joe L. Quote Link to comment
papnikol Posted November 5, 2010 Share Posted November 5, 2010 I am copying and pasting from the telnet console: root@Tower:/dev# fdisk -l /dev/sdc root@Tower:/dev# root@Tower:/dev# hdparm -I /dev/sdc /dev/sdc: HDIO_DRIVE_CMD(identify) failed: Input/output error root@Tower:/dev# root@Tower:/dev# dd if=/dev/sdc count=2 | od -x -A d dd: reading `/dev/sdc': Input/output error 0+0 records in 0+0 records out 0 bytes (0 B) copied, 0.0051591 s, 0.0 kB/s 0000000 root@Tower:/dev# root@Tower:/dev# sfdisk -l /dev/sdc Disk /dev/sdc: 243201 cylinders, 255 heads, 63 sectors/track read: Input/output error sfdisk: read error on /dev/sdc - cannot read sector 0 /dev/sdc: unrecognized partition table type No partitions found root@Tower:/dev# root@Tower:/dev# smartctl -d ata -a /dev/sdc smartctl version 5.38 [i486-slackware-linux-gnu] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ Smartctl: Device Read Identity Failed (not an ATA/ATAPI device) A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. root@Tower:/dev# Quote Link to comment
Joe L. Posted November 5, 2010 Share Posted November 5, 2010 All of those show the disk is completely un-responsive. Now, if you can, stop the array, power down, power back up, and see if any of those work after a power cycle. Joe L. Edit: although sfdisk diid report some geometry. It still could not read sector 0 Joe L. Quote Link to comment
papnikol Posted November 5, 2010 Share Posted November 5, 2010 All of those show the disk is completely un-responsive. Now, if you can, stop the array, power down, power back up, and see if any of those work after a power cycle. Joe L. Edit: although sfdisk diid report some geometry. It still could not read sector 0 Joe L. You are right, after rebooting it seems to see the disk. I get: root@Tower:/# fdisk -l /dev/sdc Disk /dev/sdc: 2000.3 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Disk /dev/sdc doesn't contain a valid partition table root@Tower:/# which seems strange because look at my fully working EARS: root@Tower:/# fdisk -l /dev/sdb Disk /dev/sdb: 2000.3 GB, 2000398934016 bytes 1 heads, 63 sectors/track, 62016336 cylinders Units = cylinders of 63 * 512 = 32256 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdb1 2 62016336 1953514552+ 83 Linux Partition 1 does not end on cylinder boundary. root@Tower:/# Here are the other commands you asked: root@Tower:/# hdparm -I /dev/sdc /dev/sdc: ATA device, with non-removable media Model Number: WDC WD20EARS-00MVWB0 Serial Number: WD-WMAZA1300377 Firmware Revision: 51.0AB51 Transport: Serial, SATA 1.0a, SATA II Extensions, SATA Rev 2.5 Standards: Supported: 8 7 6 5 Likely used: 8 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBA user addressable sectors: 268435455 LBA48 user addressable sectors: 3907029168 device size with M = 1024*1024: 1907729 MBytes device size with M = 1000*1000: 2000398 MBytes (2000 GB) Capabilities: LBA, IORDY(can be disabled) Queue depth: 32 Standby timer values: spec'd by Standard, with device specific minimum R/W multiple sector transfer: Max = 16 Current = 0 Recommended acoustic management value: 128, current value: 254 DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=120ns IORDY flow control=120ns Commands/features: Enabled Supported: * SMART feature set Security Mode feature set * Power Management feature set * Write cache * Look-ahead * Host Protected Area feature set * WRITE_BUFFER command * READ_BUFFER command * NOP cmd * DOWNLOAD_MICROCODE Power-Up In Standby feature set * SET_FEATURES required to spinup after power up SET_MAX security extension Automatic Acoustic Management feature set * 48-bit Address feature set * Device Configuration Overlay feature set * Mandatory FLUSH_CACHE * FLUSH_CACHE_EXT * SMART error logging * SMART self-test * General Purpose Logging feature set * 64-bit World wide name * WRITE_UNCORRECTABLE_EXT command * {READ,WRITE}_DMA_EXT_GPL commands * Segmented DOWNLOAD_MICROCODE * SATA-I signaling speed (1.5Gb/s) * SATA-II signaling speed (3.0Gb/s) * Native Command Queueing (NCQ) * Host-initiated interface power management * Phy event counters * unknown 76[12] DMA Setup Auto-Activate optimization * Software settings preservation * SMART Command Transport (SCT) feature set * SCT LBA Segment Access (AC2) * SCT Features Control (AC4) * SCT Data Tables (AC5) unknown 206[12] (vendor specific) unknown 206[13] (vendor specific) Security: Master password revision code = 65534 supported not enabled not locked not frozen not expired: security count supported: enhanced erase 376min for SECURITY ERASE UNIT. 376min for ENHANCED SECURITY ERASE UNIT. Logical Unit WWN Device Identifier: 50014ee6ab266c5e NAA : 5 IEEE OUI : 14ee Unique ID : 6ab266c5e Checksum: correct root@Tower:/# dd if=/dev/sdc count=2 | od -x -A d 2+0 records in 2+0 records out 1024 bytes (1.0 kB) copied, 0.000227406 s, 4.5 MB/s 0000000 0000 0000 0000 0000 0000 0000 0000 0000 * 0001024 root@Tower:/# sfdisk -l /dev/sdc Disk /dev/sdc: 243201 cylinders, 255 heads, 63 sectors/track sfdisk: ERROR: sector 0 does not have an msdos signature /dev/sdc: unrecognized partition table type No partitions found root@Tower:/# root@Tower:/# smartctl -d ata -a /dev/sdc smartctl version 5.38 [i486-slackware-linux-gnu] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WMAZA1300377 Firmware Version: 51.0AB51 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: Fri Nov 5 21:55:59 2010 GMT-2 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: (36960) 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 172 170 021 Pre-fail Always - 6400 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 12 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 100 100 000 Old_age Always - 15 10 Spin_Retry_Count 0x0032 100 253 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 - 10 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 9 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 139 194 Temperature_Celsius 0x0022 121 117 000 Old_age Always - 29 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged 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 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. root@Tower:/# I will be away for sometime i will get back to you a bit later.... Quote Link to comment
Joe L. Posted November 5, 2010 Share Posted November 5, 2010 Thanks... Your power cycle results indicate to me that either the disk itself, or the disk controller gets locked up after adding the jumper. We don't yet know what locks it up, but we know it can be gotten to respond once more after a power cycle (and potentially an attempt to read the disk in between) You can see the various programs attempting to report on the geometry. About the only think they agree on is the number of bytes. You certainly do not have 1 disk head, and I can guarantee you do not have 255. Your other disk that is "working" simply has a different idea of the cylinders/heads/sectors than the one you just tested for me. I too will be out later... Going to a dance with my wife... (Can't live by being a geek entirely... need to have some social skills too) Quote Link to comment
papnikol Posted November 5, 2010 Share Posted November 5, 2010 Thanks... Your power cycle results indicate to me that either the disk itself, or the disk controller gets locked up after adding the jumper. We don't yet know what locks it up, but we know it can be gotten to respond once more after a power cycle (and potentially an attempt to read the disk in between) You can see the various programs attempting to report on the geometry. About the only think they agree on is the number of bytes. You certainly do not have 1 disk head, and I can guarantee you do not have 255. Your other disk that is "working" simply has a different idea of the cylinders/heads/sectors than the one you just tested for me. Also, check this link: http://linuxconfig.org/linux-wd-ears-advanced-format The guy doesnt seem to mind that there are 255 heads reported (although I must admit there is not much I understand about the mechanics of HDs). Could this be normal? I too will be out later... Going to a dance with my wife... (Can't live by being a geek entirely... need to have some social skills too) It was my understanding that once you get married, social skills become redundant Anyway, I have a few questions and comments: 1)do you have any suggestions (should i try to format it under windows as someone suggested)? Maybe I should remove the jumper? Or do I have to RMA it? Btw, i tried preclearing now that I restarted and it says it is doing so... 2)Also, check this link: http://linuxconfig.org/linux-wd-ears-advanced-format The guy doesnt seem to mind about the 255 heads. Could it be normal? Also, searching the internet, I think there is the possibility to change the specs such as number of heads by a command i think. 3)Finally, is there a problem with my other EARS since it is reporting a wrong number of heads? (This makes me a bit worried since I already have it working in my array...) UPDATE: just had a look in my other 2TB disks and they also report 1 head so I guess this is not a problem Sorry for all the bubbling (is this the right use of the word?) but i am confused... Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.