fonzie Posted December 11, 2011 Share Posted December 11, 2011 I ran a preclear on my drive and it seems to have passed...I just need someone to verify that all is well. thanks preclear_results.txt Quote Link to comment
Joe L. Posted December 11, 2011 Share Posted December 11, 2011 I ran a preclear on my drive and it seems to have passed...I just need someone to verify that all is well. thanks looks good Quote Link to comment
fonzie Posted December 11, 2011 Share Posted December 11, 2011 Awesome. Thanks Joe! Quote Link to comment
mrcsx Posted December 17, 2011 Share Posted December 17, 2011 I just ran a preclear on a Hitachi 3TB drive. All went well, but the pre clear report at the end said it has the partition starting on sector 1? I thought the partition would always start on sector 64 since it's an advanced format drive. Is this something I should worry about? Report is attached. preclear_3tb.txt Quote Link to comment
Joe L. Posted December 17, 2011 Share Posted December 17, 2011 I just ran a preclear on a Hitachi 3TB drive. All went well, but the pre clear report at the end said it has the partition starting on sector 1? I thought the partition would always start on sector 64 since it's an advanced format drive. Is this something I should worry about? Report is attached. You are misinformed. On drives > 2.2TB, a different partitioning scheme is used. It is a GPT partition, and it indeed is aligned to a 4k boundary, so it is compatible even with those drives whose performance suffers when a partition is not aligned with a 4k boundary. To keep older utilities from thinking the drive is not partitioned, since the GPT partition does not use the MBR, a "protective partition" is defined in the MBR. That "protective partition" is defined as starting on partition 1 and extending the full 2.2TB that was possible using an MBR partition table. IT is there only to make older utilities (such as "fdisk") happy. To them, the entire drive is allocated and no further partitioning is possible. You need not worry. Everything is as it should be. One more thing... your drive is NOT an "advanced format" drive that needs to be handled specially. It presents 512 byte sectors to the OS and hitachi drives do not suffer regardless of the alignment of partitions. Also, as far as I know, no drive uses 4096 byte sectors when communicating with the OS. The WD EARS drives were the only ones where performance suffered if not accessed on a 4k alignment. (But even they work perfectly fine in unRAID, regardless of how they are jumpered or partitioned.) Even un-aligned, they have more than sufficient performance to serve up movies, since most media access is linear, and we typically read large numbers of contiguous blocks from the disks. Joe L. Quote Link to comment
Frank1940 Posted December 20, 2011 Share Posted December 20, 2011 I have a test bed using unRAID Basic and I have three hard drives in the array. I have been using this system to evaluate unRAID and intend to upgrade my FreeNAS system as soon as hard drive prices return back to normal. I recently purchased a Monoprice PCI SATA card (SA3114) for this test bed to permit me to preclear drives prior to the changeover. I connected up an ESATA external drive to this test bed. (I don't want to actually do anything to this drive as it contains backups.) This drive can not be seen in the standard unRAID Web interface (Simple Features installed). However, using unMenu, the ESATA drive, and its properties, is listed as not being in the array with the device designation--- /dev/sda. From this, I am certain that the card is working properly. My question is: Can I preclear drives in the current configuration without removing one of the drives in the array which would bring the drive count below three for the Basic version? Quote Link to comment
wsume99 Posted December 20, 2011 Share Posted December 20, 2011 My question is: Can I preclear drives in the current configuration without removing one of the drives in the array which would bring the drive count below three for the Basic version?With the basic version you are limited to three drives in the array but you can have an unlimited number of drives outside of the array. So since any drive you would be preclearing would not be assigned to the array you can do this without any problem. I have done this myself so I can confirm that it works just fine. Quote Link to comment
joelones Posted December 20, 2011 Share Posted December 20, 2011 Hi All, I am in need of some desperate help. This is a new build with only one disk and I am getting errors in the syslog Drive: ST2000DL003 Case: NORCO RPC-4020 MB: supermicro x8sil-f The drive is connected to a sata port on the motherboard and I am using the supplied sata cable that came with the motherboard: Syslog: Dec 20 20:59:34 tonyunraid kernel: ata4: hard resetting link Dec 20 20:59:34 tonyunraid kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Dec 20 20:59:34 tonyunraid kernel: ata4.00: configured for UDMA/33 Dec 20 20:59:34 tonyunraid kernel: sd 6:0:0:0: [sdb] Result: hostbyte=0x00 driverbyte=0x08 Dec 20 20:59:34 tonyunraid kernel: sd 6:0:0:0: [sdb] Sense Key : 0xb [current] [descriptor] Dec 20 20:59:34 tonyunraid kernel: Descriptor sense data with sense descriptors (in hex): Dec 20 20:59:34 tonyunraid kernel: 72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00 Dec 20 20:59:34 tonyunraid kernel: 20 32 c6 67 Dec 20 20:59:34 tonyunraid kernel: sd 6:0:0:0: [sdb] ASC=0x47 ASCQ=0x0 Dec 20 20:59:34 tonyunraid kernel: sd 6:0:0:0: [sdb] CDB: cdb[0]=0x2a: 2a 00 20 32 c6 48 00 04 00 00 Dec 20 20:59:34 tonyunraid kernel: end_request: I/O error, dev sdb, sector 540198472 Dec 20 20:59:34 tonyunraid kernel: __ratelimit: 246 callbacks suppressed Dec 20 20:59:34 tonyunraid kernel: Buffer I/O error on device sdb, logical block 67524809 Dec 20 20:59:34 tonyunraid kernel: lost page write due to I/O error on sdb Dec 20 20:59:34 tonyunraid kernel: Buffer I/O error on device sdb, logical block 67524810 Dec 20 20:59:34 tonyunraid kernel: lost page write due to I/O error on sdb Dec 20 20:59:34 tonyunraid kernel: Buffer I/O error on device sdb, logical block 67524811 Dec 20 20:59:34 tonyunraid kernel: lost page write due to I/O error on sdb Dec 20 20:59:34 tonyunraid kernel: Buffer I/O error on device sdb, logical block 67524812 Dec 20 20:59:34 tonyunraid kernel: lost page write due to I/O error on sdb Dec 20 20:59:34 tonyunraid kernel: Buffer I/O error on device sdb, logical block 67524813 Dec 20 20:59:34 tonyunraid kernel: lost page write due to I/O error on sdb Dec 20 20:59:34 tonyunraid kernel: Buffer I/O error on device sdb, logical block 67524814 Dec 20 20:59:34 tonyunraid kernel: lost page write due to I/O error on sdb Dec 20 20:59:34 tonyunraid kernel: Buffer I/O error on device sdb, logical block 67524815 Dec 20 20:59:34 tonyunraid kernel: lost page write due to I/O error on sdb Dec 20 20:59:34 tonyunraid kernel: Buffer I/O error on device sdb, logical block 67524816 Dec 20 20:59:34 tonyunraid kernel: lost page write due to I/O error on sdb Dec 20 20:59:34 tonyunraid kernel: Buffer I/O error on device sdb, logical block 67524817 Dec 20 20:59:34 tonyunraid kernel: lost page write due to I/O error on sdb Dec 20 20:59:34 tonyunraid kernel: Buffer I/O error on device sdb, logical block 67524818 Dec 20 20:59:34 tonyunraid kernel: lost page write due to I/O error on sdb Dec 20 20:59:34 tonyunraid kernel: ata4: EH complete Dec 20 20:59:34 tonyunraid kernel: ata4.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 Dec 20 20:59:34 tonyunraid kernel: ata4.00: BMDMA stat 0x26 Dec 20 20:59:34 tonyunraid kernel: ata4: SError: { UnrecovData Handshk } Dec 20 20:59:34 tonyunraid kernel: ata4.00: failed command: WRITE DMA EXT Dec 20 20:59:34 tonyunraid kernel: ata4.00: cmd 35/00:00:48:ca:32/00:04:20:00:00/e0 tag 0 dma 524288 out Dec 20 20:59:34 tonyunraid kernel: res 51/84:b1:97:ca:32/84:03:20:00:00/e0 Emask 0x30 (host bus error) Dec 20 20:59:34 tonyunraid kernel: ata4.00: status: { DRDY ERR } Dec 20 20:59:34 tonyunraid kernel: ata4.00: error: { ICRC ABRT } Dec 20 20:59:34 tonyunraid kernel: ata4: hard resetting link This errors keep on repeating. The syslog is 30MBs! The drive is 6.0Gbs but the board is 3.0Gbs, I doubt that could be the problem. Could it be the backplane in the Norco? I did however try preclearing a 1.5 seagate (ST1500DL003) in the same port (it's a 6Gbs too), same types of messages. It appears that the preclear has froze at the following point: Please help. Thanks Quote Link to comment
RobJ Posted December 21, 2011 Share Posted December 21, 2011 I am in need of some desperate help. This is a new build with only one disk and I am getting errors in the syslog The drive is connected to a sata port on the motherboard and I am using the supplied sata cable that came with the motherboard: Syslog: Dec 20 20:59:34 tonyunraid kernel: ata4: hard resetting link Dec 20 20:59:34 tonyunraid kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Dec 20 20:59:34 tonyunraid kernel: ata4.00: configured for UDMA/33 ... Dec 20 20:59:34 tonyunraid kernel: end_request: I/O error, dev sdb, sector 540198472 Dec 20 20:59:34 tonyunraid kernel: __ratelimit: 246 callbacks suppressed Dec 20 20:59:34 tonyunraid kernel: Buffer I/O error on device sdb, logical block 67524809 Dec 20 20:59:34 tonyunraid kernel: lost page write due to I/O error on sdb ... Dec 20 20:59:34 tonyunraid kernel: ata4: EH complete Dec 20 20:59:34 tonyunraid kernel: ata4.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 Dec 20 20:59:34 tonyunraid kernel: ata4.00: BMDMA stat 0x26 Dec 20 20:59:34 tonyunraid kernel: ata4: SError: { UnrecovData Handshk } Dec 20 20:59:34 tonyunraid kernel: ata4.00: failed command: WRITE DMA EXT Dec 20 20:59:34 tonyunraid kernel: ata4.00: cmd 35/00:00:48:ca:32/00:04:20:00:00/e0 tag 0 dma 524288 out Dec 20 20:59:34 tonyunraid kernel: res 51/84:b1:97:ca:32/84:03:20:00:00/e0 Emask 0x30 (host bus error) Dec 20 20:59:34 tonyunraid kernel: ata4.00: status: { DRDY ERR } Dec 20 20:59:34 tonyunraid kernel: ata4.00: error: { ICRC ABRT } Dec 20 20:59:34 tonyunraid kernel: ata4: hard resetting link This errors keep on repeating. The syslog is 30MBs! The drive is 6.0Gbs but the board is 3.0Gbs, I doubt that could be the problem. Could it be the backplane in the Norco? There are at least 4 indicators of bad communications to the drive - degraded SATA link speed ("SATA link up 1.5 Gbps"), degraded UDMA speed ("configured for UDMA/33"), SATA error flag ("Handshk"), and drive error flag ("ICRC"). This is most likely caused by a bad SATA cable, but could also be bad power to the drive. Replace the cable ASAP, with a known good SATA cable, and test again. Just a note, what is usually most helpful from the syslog is either all of it in a zipped file, or at least the section that includes the very first occurrences of the error. The 6gbps vs 3gbps SATA speed difference should not be a problem. Quote Link to comment
joelones Posted December 21, 2011 Share Posted December 21, 2011 I am in need of some desperate help. This is a new build with only one disk and I am getting errors in the syslog The drive is connected to a sata port on the motherboard and I am using the supplied sata cable that came with the motherboard: Syslog: Dec 20 20:59:34 tonyunraid kernel: ata4: hard resetting link Dec 20 20:59:34 tonyunraid kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Dec 20 20:59:34 tonyunraid kernel: ata4.00: configured for UDMA/33 ... Dec 20 20:59:34 tonyunraid kernel: end_request: I/O error, dev sdb, sector 540198472 Dec 20 20:59:34 tonyunraid kernel: __ratelimit: 246 callbacks suppressed Dec 20 20:59:34 tonyunraid kernel: Buffer I/O error on device sdb, logical block 67524809 Dec 20 20:59:34 tonyunraid kernel: lost page write due to I/O error on sdb ... Dec 20 20:59:34 tonyunraid kernel: ata4: EH complete Dec 20 20:59:34 tonyunraid kernel: ata4.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 Dec 20 20:59:34 tonyunraid kernel: ata4.00: BMDMA stat 0x26 Dec 20 20:59:34 tonyunraid kernel: ata4: SError: { UnrecovData Handshk } Dec 20 20:59:34 tonyunraid kernel: ata4.00: failed command: WRITE DMA EXT Dec 20 20:59:34 tonyunraid kernel: ata4.00: cmd 35/00:00:48:ca:32/00:04:20:00:00/e0 tag 0 dma 524288 out Dec 20 20:59:34 tonyunraid kernel: res 51/84:b1:97:ca:32/84:03:20:00:00/e0 Emask 0x30 (host bus error) Dec 20 20:59:34 tonyunraid kernel: ata4.00: status: { DRDY ERR } Dec 20 20:59:34 tonyunraid kernel: ata4.00: error: { ICRC ABRT } Dec 20 20:59:34 tonyunraid kernel: ata4: hard resetting link This errors keep on repeating. The syslog is 30MBs! The drive is 6.0Gbs but the board is 3.0Gbs, I doubt that could be the problem. Could it be the backplane in the Norco? There are at least 4 indicators of bad communications to the drive - degraded SATA link speed ("SATA link up 1.5 Gbps"), degraded UDMA speed ("configured for UDMA/33"), SATA error flag ("Handshk"), and drive error flag ("ICRC"). This is most likely caused by a bad SATA cable, but could also be bad power to the drive. Replace the cable ASAP, with a known good SATA cable, and test again. Just a note, what is usually most helpful from the syslog is either all of it in a zipped file, or at least the section that includes the very first occurrences of the error. The 6gbps vs 3gbps SATA speed difference should not be a problem. Your response is much appreciated. I have changed the sata cable and will begin the preclear process again, unfortunately it's only at step 2 of the preclear process that the errors appear, so I will have to wait and see. I have attached the syslog which details the first occurrence of the error. Many thanks. syslog_1.zip Quote Link to comment
RobJ Posted December 21, 2011 Share Posted December 21, 2011 Syslog essentially confirms the previous comments, so hoping that the newer cable works better for you. An additional comment, you are running UnRAID v4.7 and your syslog shows some issues setting up the SAS support (not uncommon). V4.7 is still the official released version, but the included SAS card support was very young. For your hardware, I recommend moving to the later betas, because I believe the SAS support is better, more stable. Quote Link to comment
joelones Posted December 21, 2011 Share Posted December 21, 2011 Syslog essentially confirms the previous comments, so hoping that the newer cable works better for you. An additional comment, you are running UnRAID v4.7 and your syslog shows some issues setting up the SAS support (not uncommon). V4.7 is still the official released version, but the included SAS card support was very young. For your hardware, I recommend moving to the later betas, because I believe the SAS support is better, more stable. Hi RobJ, Woke up this morning to the same errors. I need to somehow verify if this is a backplane problem or not. It could be power related too, however, each backplane has 4 sata connectors and two molex connectors and as far as I can tell, the connectors are seated properly. I am however using one molex to sata power connector for this backplane, (btw the PSU is 750W), I will try using two molexes. I have been testing the same backplane and same sata connector, I will try the next backplane connector and then without the backplane at all (seeing how two disks exhibit this problem, I doubt it's related to the disks. Could it be a motherboard problem, I don't think anything needs to be set in the Bios?). Do you know of a way testing this without using preclear, as each time I test, I have to wait until until "Step 2 of 10" before these errors appear in the log??? It makes this process more difficult, waiting 5-10hrs before I see the errors. Thanks again. Quote Link to comment
evans036 Posted December 21, 2011 Share Posted December 21, 2011 perhaps a reiserfsck would be faster? Quote Link to comment
joelones Posted December 21, 2011 Share Posted December 21, 2011 perhaps a reiserfsck would be faster? thanks for the suggestion, but doesn't there have to be a filesystem on the disk for this? these are new disks. Quote Link to comment
evans036 Posted December 21, 2011 Share Posted December 21, 2011 sorry: brain fart here. steve. Quote Link to comment
evans036 Posted December 21, 2011 Share Posted December 21, 2011 try #2 how about something like: dd if=/dev/sde bs=8k of=/dev/null where /dev/sde is replaced by your device steve Quote Link to comment
Joe L. Posted December 21, 2011 Share Posted December 21, 2011 try #2 how about something like: dd if=/dev/sde bs=8k of=/dev/null where /dev/sde is replaced by your device steve Since he says it is in the "writing" of the disk where errors occur, reading from it using "dd" as you described will probably not help. Instead, for a quicker test, simply use the "-W" option to the preclear script to ask it to skip the initial "reading" of the disk. It will then start with the "writing" of zeros. preclear_disk.sh -W /dev/sdX Quote Link to comment
joelones Posted December 21, 2011 Share Posted December 21, 2011 try #2 how about something like: dd if=/dev/sde bs=8k of=/dev/null where /dev/sde is replaced by your device steve Since he says it is in the "writing" of the disk where errors occur, reading from it using "dd" as you described will probably not help. Instead, for a quicker test, simply use the "-W" option to the preclear script to ask it to skip the initial "reading" of the disk. It will then start with the "writing" of zeros. preclear_disk.sh -W /dev/sdX Thanks for this JoeL., this will surely save some time. I just tried the second backplane and no errors. So I guess I can conclude that the first backplane is damaged, come to think of it, I did notice it being loose upon touch. It should of occurred to me to check that first as a root cause. I notice that the backplanes have two thumb screws, should I bother to loosen and inspect it further? Now, having it bought at Newegg.ca, what would be the process? Contact newegg and ask for a RMA (could only imagine the shipping from Canada) or the manufacturer for a replacement backplane? EDIT: Will probably just call norco and ask for a replacement. I'm now worried about the other backplanes. Will need to test each I guess. Quote Link to comment
joelones Posted December 22, 2011 Share Posted December 22, 2011 So I finally narrowed it down to the first SATA port on the first backplane. Thanks for all the help guys! I pulled out the backplane to take a look and notice that the backplane looked "used" in many respects (scratches, discoloring, etc...). It just didn't look like a new circuit board. Countless wasted hours later, I contacted Norco via telephone, I was told to send an email to their customer service address by some individual who had difficulties with the English language. A fellow got back to me, he wanted pictures, then said I was responsible for buying the replacement and shipping back the defective unit, shipping of which would not be reimbursed. Build quality of the case and customer service are subpar in my book, will not be buying Norco again. Live and learn I guess. Again, thanks for all the suggestions. Quote Link to comment
Boltron Posted December 22, 2011 Share Posted December 22, 2011 Repost: Put in the wrong place first time... I am building a new array. I am using preclear_disk.sh 1.13 and unRAID 5 b14. I am starting out with a mix of Green and Black WD drives. All drives (except the parity which is a new 2TB Black) were in use on Windows systems before and none have ever had jumpers. I am running preclears on 4 drives at the moment. On two of the Greens I used preclear with -A. One is a WD15EARS, the other a WD20EARX. Below are the details of preclear -t for both after the successful preclear completed. My question/concern is that I have different Sector and I/O size for both. One shows 4k, the other 512b. Is something wrong here? Pre-Clear unRAID Disk /dev/sdc ################################################################## 1.13 Model Family: Western Digital Caviar Green (Adv. Format) family Device Model: WDC WD15EARS-00MVWB0 Serial Number: WD-WMAZA2511856 Firmware Version: 51.0AB51 User Capacity: 1,500,301,910,016 bytes Disk /dev/sdc: 1500.3 GB, 1500301910016 bytes 255 heads, 63 sectors/track, 182401 cylinders, total 2930277168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdc1 64 2930277167 1465138552 0 Empty Partition 1 does not end on cylinder boundary. ######################################################################## ======================================================================== == == DISK /dev/sdc IS PRECLEARED with a starting sector of 64 == ============================================================================ Pre-Clear unRAID Disk /dev/sdd ################################################################## 1.13 Device Model: WDC WD20EARX-00PASB0 Serial Number: WD-WCAZA8415922 Firmware Version: 51.0AB51 User Capacity: 2,000,398,934,016 bytes Disk /dev/sdd: 2000.4 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdd1 64 3907029167 1953514552 0 Empty Partition 1 does not end on cylinder boundary. ######################################################################## ========================================================================1.13 == == DISK /dev/sdd IS PRECLEARED with a starting sector of 64 == ============================================================================ Quote Link to comment
Joe L. Posted December 22, 2011 Share Posted December 22, 2011 My question/concern is that I have different Sector and I/O size for both. One shows 4k, the other 512b. Is something wrong here? Nothing wrong... Just different drives. Quote Link to comment
graywolf Posted December 28, 2011 Share Posted December 28, 2011 Tons of mvsas messages syslog attached. ESXi 5.0 + unRaid 5b12a + drives on MV8 Need to be concerned or not? The 2 pre-clears still seem to be running syslog-20111228.zip Quote Link to comment
Point7 Posted December 31, 2011 Share Posted December 31, 2011 Is it save to use following disk ? I'm worried about the re-allocation sectors. first run of pre-clear ========================================================================1.13 == invoked as: ./preclear_disk.sh -A /dev/sda == SAMSUNG HD154UI S1Y6J90SA57135 == Disk /dev/sda 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:33:51 (74 MB/s) == Last Cycle's Zeroing time : 5:39:43 (73 MB/s) == Last Cycle's Post Read Time : 10:30:29 (39 MB/s) == Last Cycle's Total Time : 21:45:02 == == Total Elapsed Time 21:45:02 == == Disk Start Temperature: 17C == == Current Disk Temperature: 13C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sda /tmp/smart_finish_sda ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Airflow_Temperature_Cel = 87 83 0 ok 13 Temperature_Celsius = 87 84 0 ok 13 No SMART attributes are FAILING_NOW 13 sectors were pending re-allocation before the start of the preclear. 21 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. 2 sectors are pending re-allocation at the end of the preclear, a change of -11 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. ============================================================================ second run: ========================================================================1.13 == invoked as: ./preclear_disk.sh -A /dev/sda == SAMSUNG HD154UI S1Y6J90SA57135 == Disk /dev/sda 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:36:20 (74 MB/s) == Last Cycle's Zeroing time : 4:59:05 (83 MB/s) == Last Cycle's Post Read Time : 10:31:55 (39 MB/s) == Last Cycle's Total Time : 21:08:19 == == Total Elapsed Time 21:08:19 == == Disk Start Temperature: 14C == == Current Disk Temperature: 13C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sda /tmp/smart_finish_sda ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Airflow_Temperature_Cel = 87 86 0 ok 13 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 16 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. 9 sectors are pending re-allocation at the end of the preclear, a change of 9 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. ============================================================================ 3th run: ========================================================================1.13 == invoked as: ./preclear_disk.sh -A /dev/sda == SAMSUNG HD154UI S1Y6J90SA57135 == Disk /dev/sda 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 : 14:07:24 (29 MB/s) == Last Cycle's Zeroing time : 5:21:18 (77 MB/s) == Last Cycle's Post Read Time : 11:04:59 (37 MB/s) == Last Cycle's Total Time : 30:34:41 == == Total Elapsed Time 30:34:41 == == Disk Start Temperature: 22C == == Current Disk Temperature: 13C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sda /tmp/smart_finish_sda ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 99 99 51 In_the_past 16799 Airflow_Temperature_Cel = 87 78 0 ok 13 Temperature_Celsius = 87 79 0 ok 13 Current_Pending_Sector = 98 71 0 ok 67 No SMART attributes are FAILING_NOW 1198 sectors were pending re-allocation before the start of the preclear. 2306 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. 67 sectors are pending re-allocation at the end of the preclear, a change of -1131 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. ============================================================================ 4th run: ========================================================================1.13 == invoked as: ./preclear_disk.sh -A /dev/sda == SAMSUNG HD154UI S1Y6J90SA57135 == Disk /dev/sda 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:43:46 (72 MB/s) == Last Cycle's Zeroing time : 4:52:19 (85 MB/s) == Last Cycle's Post Read Time : 10:23:24 (40 MB/s) == Last Cycle's Total Time : 21:00:27 == == Total Elapsed Time 21:00:27 == == Disk Start Temperature: 11C == == Current Disk Temperature: 22C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sda /tmp/smart_finish_sda ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 99 99 51 In_the_past 4433 Airflow_Temperature_Cel = 78 89 0 ok 22 Temperature_Celsius = 78 88 0 ok 22 Current_Pending_Sector = 100 98 0 ok 0 No SMART attributes are FAILING_NOW 67 sectors were pending re-allocation before the start of the preclear. 77 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, a change of -67 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. ============================================================================ Quote Link to comment
Joe L. Posted December 31, 2011 Share Posted December 31, 2011 I'm worried about the re-allocation sectors. me too. They seem to always be re-written into place, so I'd suspect the power supply as an additional thing to check. (poor quality power might contribute to a poor quality write of the disk) In general, I'd not trust my data on it. Joe L. 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.