Superorb Posted June 6, 2011 Share Posted June 6, 2011 Ty Super. i already started it with the -a. now another dilemna... this drive is HOT. it's at 41 degree before starting it. already at 43. it's at least 4 years old. so i'm hoping it doesn't croak on me oh it was a WD mybook that the power supply died on. That's too hot, especially for idle. Is it a 7200rpm drive? Quote Link to comment
Joe L. Posted June 6, 2011 Share Posted June 6, 2011 Ty Super. i already started it with the -a. now another dilemna... this drive is HOT. it's at 41 degree before starting it. already at 43. it's at least 4 years old. so i'm hoping it doesn't croak on me oh it was a WD mybook that the power supply died on. That's too hot, especially for idle. Is it a 7200rpm drive? A lot of the older drives ran very hot. It might be normal for that drive to consume a lot of power, and waste a lot of it in heat. Probably just needs a lot of air-flow across it. (A 36" fan, spaced about an inch or two away should do it... If it does not, just use multiple ) I'll bet the older drive is not "green" Quote Link to comment
axeman Posted June 7, 2011 Share Posted June 7, 2011 lol it's not green by a long shot. Newegg has 10% off on laptop drives. the 250gb wd scorpio blue and black work out to about the same $50 - $5. The black has $5 shipping, but i have shoprunner so effective price is same. i'm hoping the pre-clear finishes soon. if anything looks like it's going bad, i'll get a scorpio... any votes on blue (5400) vs. black (7200)? Quote Link to comment
Joe L. Posted June 7, 2011 Share Posted June 7, 2011 lol it's not green by a long shot. Newegg has 10% off on laptop drives. the 250gb wd scorpio blue and black work out to about the same $50 - $5. The black has $5 shipping, but i have shoprunner so effective price is same. i'm hoping the pre-clear finishes soon. if anything looks like it's going bad, i'll get a scorpio... any votes on blue (5400) vs. black (7200)? unless you have an absolute need for a 2.5 inch drive, I'd get one of the 2TB drives for only a small amount more money. $59, free shipping, 1.5TB http://www.newegg.com/Product/Product.aspx?Item=N82E16822148725&cm_sp=DailyDeal-_-22-148-725-_-Homepage $59 after rebate, $69 if you forget to send in the rebate form, free shipping 2TB Hitachi... (one of my favorite brands) http://www.newegg.com/Product/Product.aspx?Item=N82E16822145475 http://www.newegg.com/Product/Product.aspx?Item=N82E16822145475 Quote Link to comment
axeman Posted June 7, 2011 Share Posted June 7, 2011 don't absolutely need one, really. just that the case is crowded. the 2.5" is in a different bay. sad thing is, even the 250 is too much... all i'm going to use it for is the ESXi datastore (trying that esxi+unraid combo box). but you are right, for just a bit more, i can get a whole 2TB. maybe i should just do that.. grrr decisions decisions. Quote Link to comment
dark_avenger Posted June 7, 2011 Share Posted June 7, 2011 don't absolutely need one, really. just that the case is crowded. the 2.5" is in a different bay. sad thing is, even the 250 is too much... all i'm going to use it for is the ESXi datastore (trying that esxi+unraid combo box). but you are right, for just a bit more, i can get a whole 2TB. maybe i should just do that.. grrr decisions decisions. Could always use the rest of the 2TB drive as cache? Quote Link to comment
axeman Posted June 7, 2011 Share Posted June 7, 2011 don't absolutely need one, really. just that the case is crowded. the 2.5" is in a different bay. sad thing is, even the 250 is too much... all i'm going to use it for is the ESXi datastore (trying that esxi+unraid combo box). but you are right, for just a bit more, i can get a whole 2TB. maybe i should just do that.. grrr decisions decisions. Could always use the rest of the 2TB drive as cache? ooooh? cache for UR? i'm listening intently . i thought the cache drive had to be a full-on dedicated to UR drive. i guess it's time to hit the wiki. Quote Link to comment
dark_avenger Posted June 7, 2011 Share Posted June 7, 2011 As far as I know you can assign just a partition for cache from what people have said but don't quote me on that Quote Link to comment
Joe L. Posted June 7, 2011 Share Posted June 7, 2011 As far as I know you can assign just a partition for cache from what people have said but don't quote me on that You can as long as you are not using 5.0beta6a. There is a bug in that version that will refuse to identify a multi-partitioned cache drive as valid, so it re-partitions it in error back to a single partition. For earlier versions, unRAID will use the 1st partition for cache, leaving the others for your use. Joe L. Quote Link to comment
dark_avenger Posted June 7, 2011 Share Posted June 7, 2011 Hi, I've had a 1.5tb drive in my array for ~6 months and the other day unraid flagged it as having an error so I've swapped the drive out with another 1.5tb drive. I plugged the old drive into a test unraid machine and ran 2 passes of preclear on it to check SMART status, etc. I've attached the preclear log, are any of the SMART attributes bad enough for RMA? Thanks in advance, David EDIT: Attached the other 2 log files Seems drive was failing. "5 Reallocated_Sector_Ct 0x0033 001 001 036 Pre-fail Always FAILING_NOW 4095" Quote Link to comment
vinnie Posted June 7, 2011 Share Posted June 7, 2011 Hmmm, OK, I awoke this morning to these results for the 5th cycle on my possibly dodgy WD20EARS: ========================================================================1.11 == invoked as: ./preclear_disk.sh /dev/sdf == WDC WD20EARS-00MVWB0 WD-WCAZA2953831 == Disk /dev/sdf has been successfully precleared == with a starting sector of 64 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 5:58:06 (93 MB/s) == Last Cycle's Zeroing time : 6:08:02 (90 MB/s) == Last Cycle's Post Read Time : 19:02:36 (29 MB/s) == Last Cycle's Total Time : 31:09:52 == == Total Elapsed Time 31:09:52 == == Disk Start Temperature: 27C == == Current Disk Temperature: 29C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdf /tmp/smart_finish_sdf ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 187 186 51 ok 7276 Temperature_Celsius = 121 123 0 ok 29 No SMART attributes are FAILING_NOW 44 sectors were pending re-allocation before the start of the preclear. 45 sectors were pending re-allocation after pre-read in cycle 1 of 1. 65535 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 20 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. ============================================================================ Not looking good. I think I'll start packing this one up and RMA it. No sense in carrying on with more preclears. Quote Link to comment
MacDaddy Posted June 9, 2011 Share Posted June 9, 2011 I've used this script for reclaiming two of my older 1TB disks from other equipment in to my unRaid server. It was great to still be able to use the existing array with all of my normal shares still in a protected state while the new drives were clearing. I am now in the process of preclearing a 2TB WD EARS drive and got some interesting syslog entries. I'm a Linus newb, so would appreciate any insight on this. By the way, this is on one of the Limetech MD1510 machines and this particular disk is the first (and only) on the second SAS. Right after the login at 23:21:36 I kicked off the preclear and went to bed. The hard resetting of the link worries me. Jun 8 23:19:47 Tower unmenu-status: Starting unmenu web-server Jun 8 23:21:36 Tower login[3702]: ROOT LOGIN on `tty1' Jun 8 23:22:24 Tower kernel: sda: unknown partition table Jun 8 23:47:56 Tower sSMTP[7314]: Creating SSL connection to host Jun 8 23:47:57 Tower sSMTP[7314]: SSL connection using DHE-RSA-AES256-SHA Jun 8 23:47:58 Tower sSMTP[7314]: Sent mail for root@localhost (221 2.0.0 omta04.emeryville.ca.mail.comcast.net comcast closing connection) Jun 8 23:51:52 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Jun 8 23:51:52 Tower kernel: ata4.00: failed command: IDENTIFY DEVICE Jun 8 23:51:52 Tower kernel: ata4.00: cmd ec/00:00:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in Jun 8 23:51:52 Tower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) Jun 8 23:51:52 Tower kernel: ata4.00: status: { DRDY } Jun 8 23:51:52 Tower kernel: ata4: hard resetting link Jun 8 23:51:58 Tower kernel: ata4: link is slow to respond, please be patient (ready=0) Jun 8 23:52:02 Tower kernel: ata4: SRST failed (errno=-16) Jun 8 23:52:02 Tower kernel: ata4: hard resetting link Jun 8 23:52:06 Tower kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jun 8 23:52:06 Tower kernel: ata4.00: configured for UDMA/133 Jun 8 23:52:06 Tower kernel: ata4: EH complete Jun 9 00:00:55 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6 frozen Jun 9 00:00:55 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED Jun 9 00:00:55 Tower kernel: ata4.00: cmd 60/00:00:00:5b:10/02:00:00:00:00/40 tag 0 ncq 262144 in Jun 9 00:00:55 Tower kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jun 9 00:00:55 Tower kernel: ata4.00: status: { DRDY } Jun 9 00:00:55 Tower kernel: ata4: hard resetting link Jun 9 00:01:01 Tower kernel: ata4: link is slow to respond, please be patient (ready=0) Jun 9 00:01:05 Tower kernel: ata4: SRST failed (errno=-16) Jun 9 00:01:05 Tower kernel: ata4: hard resetting link Jun 9 00:01:11 Tower kernel: ata4: link is slow to respond, please be patient (ready=0) Jun 9 00:01:15 Tower kernel: ata4: SRST failed (errno=-16) Jun 9 00:01:15 Tower kernel: ata4: hard resetting link Jun 9 00:01:21 Tower kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jun 9 00:01:21 Tower kernel: ata4.00: configured for UDMA/133 Jun 9 00:01:21 Tower kernel: ata4.00: device reported invalid CHS sector 0 Jun 9 00:01:21 Tower kernel: ata4: EH complete Jun 9 00:19:20 Tower kernel: mdcmd (394): spindown 9 Jun 9 00:45:02 Tower kernel: mdcmd (548): spindown 0 Jun 9 00:45:03 Tower kernel: mdcmd (549): spindown 2 Jun 9 00:45:03 Tower kernel: mdcmd (550): spindown 5 Jun 9 00:45:03 Tower kernel: mdcmd (551): spindown 8 Jun 9 00:45:13 Tower kernel: mdcmd (553): spindown 2 Jun 9 00:47:40 Tower sSMTP[12676]: Creating SSL connection to host Jun 9 00:47:41 Tower sSMTP[12676]: SSL connection using DHE-RSA-AES256-SHA Jun 9 00:47:42 Tower sSMTP[12676]: Sent mail for root@localhost (221 2.0.0 omta17.westchester.pa.mail.comcast.net comcast closing connection) Jun 9 04:00:17 Tower kernel: mdcmd (1719): spindown 0 Jun 9 04:00:17 Tower kernel: mdcmd (1720): spindown 8 Jun 9 05:02:12 Tower kernel: mdcmd (2090): spindown 0 Jun 9 07:40:07 Tower kernel: usb 4-1: USB disconnect, address 2 Jun 9 07:40:07 Tower kernel: usb 4-1.1: USB disconnect, address 3 Jun 9 07:40:07 Tower kernel: usb 4-1.3: USB disconnect, address 4 Jun 9 07:41:47 Tower unmenu[3699]: Disk /dev/sda doesn't contain a valid partition table Jun 9 07:44:03 Tower kernel: mdcmd (3068): spindown 8 Jun 9 07:44:13 Tower kernel: mdcmd (3070): spindown 8 Jun 9 07:44:13 Tower kernel: mdcmd (3071): spindown 9 Jun 9 07:44:24 Tower kernel: mdcmd (3073): spindown 0 Jun 9 07:44:35 Tower kernel: mdcmd (3075): spindown 0 Jun 9 07:44:35 Tower kernel: mdcmd (3076): spindown 2 Jun 9 07:44:45 Tower kernel: mdcmd (3078): spindown 5 I'll attach the full syslog if there is any further information that might help in explaining. thanks for your help. syslog-2011-06-09.txt Quote Link to comment
Superorb Posted June 9, 2011 Share Posted June 9, 2011 I've had problems where my SATA link was down/up and reset before, and it was almost always due to loose cables. Also, pulling the drives out/in of their backplanes several times seemed to fix all my problems. Quote Link to comment
MacDaddy Posted June 9, 2011 Share Posted June 9, 2011 Good point. This is the first drive on the SAS card and the first time the slot in this particular cage has been used. I'm not sure if it's really impacting the preclear right at the moment. I'm getting about 98.3 MB/s and 21% through the first step at 8:13 hours in. I think I should let it finish and then try to address the cable/card/backplane items when it completes. Quote Link to comment
Superorb Posted June 9, 2011 Share Posted June 9, 2011 Good point. This is the first drive on the SAS card and the first time the slot in this particular cage has been used. I'm not sure if it's really impacting the preclear right at the moment. I'm getting about 98.3 MB/s and 21% through the first step at 8:13 hours in. I think I should let it finish and then try to address the cable/card/backplane items when it completes. Let it complete. Then pull the drive in and out a few times. Unplug and replug the cables. Then run another preclear. Quote Link to comment
teamhood Posted June 10, 2011 Share Posted June 10, 2011 Question: I've used this script many times and I'm perplexed. I cd /boot preclear_disk.sh -A /dev/sdm, but all it does is bring up this: Why won't this run the preclear script? root@unraid:/boot# preclear_disk.sh -A /dev/sdm Usage: ./preclear_disk.sh [-t] [-n] [-c count] /dev/??? where = hda, hdb, sda, sdb, etc... -n = Do NOT perform preread and postread of entire disk to allow SMART firmware to reallocate bad blocks in the clearing proce -c count = perform count preread/clear/postread cycles where count is a number from 1 through 20 If not specified, default is 1 cycle. For large disks, 1 cyc can take 10 or more hours -t = Test if disk has pre-clear signature. This option may NOT be combined with the -c or -n options. The test does not write the disk. It makes no changes to a disk at all. It only read the first 512 bytes of the disk to verify a pre-clear signatu exists. Note: "-t" does not read the entire disk to verify i it pre-cleared as that could take hours for a large disk. sin the pre-clear-signature is written *after* a disk is entirely filled with zeros, if it exists, we assume the disk is cleare -v = print version of ./preclear_disk.sh -m [email protected] = optional recipient address. If blank an option is used, it will default to default e-mail address of -M 1 = Will send an e-mail message at the end of the final results (default if -m is used, but no other -M option given) -M 2 = Will send an e-mail same as 1 plus at the end of a cycle (i ple cycles are specified) -M 3 = Will send an e-mail same as 2 plus at the start and end of -read, zeroing, post-read -M 4 = Will send an e-mail same as 3 plus also at intervals of 25% during the long tests The -m, -M options requires that a valid working mail command is i d. One version that has worked (bashmail) is affilaited with the unra fy script. There are others that also will work. Any of these need to be configured to work with your mail server. The unraid_notify script will have instructions on how to configure this. See http://lime-technology.com/forum/index.php?top'>http://lime-technology.com/forum/index.php?top .0 for unraid_notify and http://lime-technology.com/forum/index.php?t 61.0 for the mail script. NOTE: The lastest verion of mail has to be arlier versions of the mail script affiliated with unraid_notify do not support the standard mail syntax needed. Unless the -n option is specified the disk will first have its ent set of blocks read, then, the entire disk will be cleared by writi zeros to it. Once that is done the disk will be partitioned with special signature that the unRAID software will recognize when the drive is added to the array. This special signature will allow th unraid software to recognize the disk has been pre-cleared and to an initial "clearing" step while the server remains off-line. The pre-read and post-read phases try their best to exercise the disk in a way to identify a drive prone to early failure. It perf reads of random blocks of data interspersed with reads of sequenti blocks on the disk in turn. This program also uses non-buffered r of the first and last cylinders on the disk, the goal is to perfor those reads in between the others, and to keep the disk head moving much more than if it just read each linear block in turn. Quote Link to comment
dark_avenger Posted June 10, 2011 Share Posted June 10, 2011 Question: I've used this script many times and I'm perplexed. I cd /boot preclear_disk.sh -A /dev/sdm, but all it does is bring up this: Looks like you might be using an older version of the script?, the -A option was only added in recent updates. Quote Link to comment
Joe L. Posted June 10, 2011 Share Posted June 10, 2011 Question: I've used this script many times and I'm perplexed. I cd /boot preclear_disk.sh -A /dev/sdm, but all it does is bring up this: Looks like you might be using an older version of the script?, the -A option was only added in recent updates. exactly. what do you get when you type preclear_disk.sh -v Quote Link to comment
Joe L. Posted June 10, 2011 Share Posted June 10, 2011 Question: I've used this script many times and I'm perplexed. I cd /boot preclear_disk.sh -A /dev/sdm, but all it does is bring up this: Looks like you might be using an older version of the script?, the -A option was only added in recent updates. exactly. I'll bet it is 10 or more versions old. what do you get when you type preclear_disk.sh -v Quote Link to comment
pmpj218 Posted June 10, 2011 Share Posted June 10, 2011 Hi. I'm new to this, so please let me know if there's any more info I need to provide... I just ran the script on four drives that I've previously used in another Windows system. Three were successful, and one wasn't. Can someone check to see if the three that passed are okay for me to add to my array? And what can I do about the one that didn't pass? Any advice/insight would be greatly appreciated. Thanks! Here are the reports that were generated for the drives that passed: ========================================================================1.11 == invoked as: ./preclear_disk.sh -A -M 4 /dev/sdf == WDC WD10EADS-00M2B0 WD-WMAV50178120 == Disk /dev/sdf has been successfully precleared == with a starting sector of 64 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 4:00:27 (69 MB/s) == Last Cycle's Zeroing time : 3:33:16 (78 MB/s) == Last Cycle's Post Read Time : 8:22:23 (33 MB/s) == Last Cycle's Total Time : 15:57:11 == == Total Elapsed Time 15:57:11 == == Disk Start Temperature: 27C == == Current Disk Temperature: 26C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdf /tmp/smart_finish_sdf ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 121 120 0 ok 26 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 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, 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. ============================================================================ ========================================================================1.11 == invoked as: ./preclear_disk.sh -A -M 4 /dev/sdh == WDC WD20EADS-00S2B0 WD-WCAVY1278318 == Disk /dev/sdh has been successfully precleared == with a starting sector of 64 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 10:22:55 (53 MB/s) == Last Cycle's Zeroing time : 6:30:27 (85 MB/s) == Last Cycle's Post Read Time : 17:22:20 (31 MB/s) == Last Cycle's Total Time : 34:16:47 == == Total Elapsed Time 34:16:47 == == Disk Start Temperature: 29C == == Current Disk Temperature: 27C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdh /tmp/smart_finish_sdh ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Seek_Error_Rate = 100 200 0 ok 0 Load_Cycle_Count = 164 165 0 ok 108209 Temperature_Celsius = 125 123 0 ok 27 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 23 sectors are pending re-allocation at the end of the preclear, a change of 23 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. ============================================================================ == invoked as: ./preclear_disk.sh -A -M 4 /dev/sdi == WDC WD20EADS-00S2B0 WD-WCAVY1312744 == Disk /dev/sdi has been successfully precleared == with a starting sector of 64 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 10:48:55 (51 MB/s) == Last Cycle's Zeroing time : 6:36:02 (84 MB/s) == Last Cycle's Post Read Time : 17:17:47 (32 MB/s) == Last Cycle's Total Time : 34:43:50 == == Total Elapsed Time 34:43:50 == == Disk Start Temperature: 29C == == Current Disk Temperature: 28C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdi /tmp/smart_finish_sdi ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 124 123 0 ok 28 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 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, 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. ============================================================================ And here's the one that didn't pass. ========================================================================1.11 == invoked as: ./preclear_disk.sh -A -M 4 /dev/sdg == == Disk /dev/sdg has NOT been successfully precleared == Postread detected un-expected non-zero bytes on disk== == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 11:13:12 (49 MB/s) == Last Cycle's Zeroing time : 6:53:20 (80 MB/s) == Last Cycle's Post Read Time : 17:43:03 (31 MB/s) == Last Cycle's Total Time : 35:50:40 == == Total Elapsed Time 35:50:40 == == Disk Start Temperature: 27C == == Current Disk Temperature: 27C, == ============================================================================ No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 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, 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. ============================================================================ Quote Link to comment
Joe L. Posted June 10, 2011 Share Posted June 10, 2011 /dev/sdh did not do too good. 23 sectors are pending re-allocation at the end of the preclear, a change of 23 in the number of sectors pending re-allocation. Run another pre-clear on it, and if the number of sectors pending re-allocation does not go to zero, consider an RMA for it too. Quote Link to comment
pmpj218 Posted June 10, 2011 Share Posted June 10, 2011 Okay. I will run one again on /dev/sdh and see what happens. Are the other two—/dev/sdf and /dev/sdi—good to go? How about /dev/sdg? Is there something I need to do to remedy this: "Postread detected un-expected non-zero bytes on disk". Is that even why it didn't pre-clear? Thanks again. Quote Link to comment
Joe L. Posted June 10, 2011 Share Posted June 10, 2011 Okay. I will run one again on /dev/sdh and see what happens. Are the other two—/dev/sdf and /dev/sdi—good to go?They looked fine. How about /dev/sdg? Is there something I need to do to remedy this: "Postread detected un-expected non-zero bytes on disk". Is that even why it didn't pre-clear? You can try another pre-clear. Basically, after being cleared, the whole disk should be read back as zeros. If not, something is wrong. Of course, it could be bad memory or a bad power supply, or a bad disk controller... no way to know until you isolate it. These types of errors cause hair loss, and random parity errors as disk returns different than expected. If it is the disk, it is best next tested as a wheel chock. (You can test how effective it is in impeding the forward and backward motion of your car as you drive over it repeatedly ) Thanks again.You are welcome. Quote Link to comment
pfp Posted June 12, 2011 Share Posted June 12, 2011 Not sure what to make of this: =========================================================================== = unRAID server Pre-Clear disk /dev/sdk = cycle 1 of 1 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Testing if the clear has been successful. DONE = Disk Temperature: 33C, Elapsed Time: 9:10:05 ============================================================================ == == SORRY: Disk /dev/sdk MBR could NOT be precleared == == out4= 00092 == out5= 00092 ============================================================================ 0000000 0000 0000 0000 0000 0000 0000 0000 0000 * 0000700 0000 0000 0000 003f 0000 7af1 aea8 0000 0000720 0000 0000 0000 0000 0000 0000 0000 0000 * 0000760 0000 0000 0000 0000 0000 0000 0000 5c5c 1+0 records in 1+0 records out 512 bytes (512 B) copied, 0.000395119 s, 1.3 MB/s 0001000 Quote Link to comment
BRiT Posted June 12, 2011 Share Posted June 12, 2011 You're using a really old version of preclear, one which has an issue with some versions of 'echo'. Upgrade to the current version. 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.