Joe L.

Yes, you can continue. I just need to not let those warning messages end up in the output. They are a result of me testing for drives already assigned to the array. The messages are harmless. The files they are testing for only exist in some versions of unRAID. Joe L.

"" instead of 00000 to me indicates nothing was returned, not an invalid value. (equally suspicious as a returned value though)

Basically because not enough people have confirmed that it works as desired and that is a good candidate to be included as currently defined. Have you used the package.conf file? Did it work as expected? Does it need any changes/improvements? Joe L. No, I have not. I was about to embark on an experiment since I have not used handbrake before, and thought I would check its level of integration with the package manager before I installed it manually. A properly defined package.conf file just needs to be put in the /boot/packages directory, or in the unmenu directory (and the package manager will then move it to the /boot/packages directory) Once there, the package manager buttons should then just function.

Basically because not enough people have confirmed that it works as desired and that is a good candidate to be included as currently defined. Have you used the package.conf file? Did it work as expected? Does it need any changes/improvements? Joe L.

Your three cycle preclear looks great to me. The Normalized raw-read-error-rate actually improved during the process from 100 to 119. There were a few seek errors, but still well above failure threshold. Joe L.

Looks OK to me.

It is telling you the sector relative to the start of the partition where the parity error was detected. The unRAID software has absolutely no way to know which bit(s) are wrong. Just that an exclusive or of all the bits of some word in the sector did not end up with an even number of bits set to a "1" It could be a but set to zero when it should be a one, or a bit set to one when it should be zero, and it could be on any of your disks, or it could be transposed in RAM if memory is flaky, or in the disk controller chipset, or on the motherboard itself. It is VERY hard to diagnose. It is one reason why old Nforce4 chipsets are to be avoided. They exhibited random parity errors that caused some to lose their hair. Many time is is a single disk, and repeated md5sums of the same data on a single disk result in different results. The fix, replace the disk. These disks often show no errors otherwise. Joe L.

Unless you've powered down without first stopping the array, where the disks could not be written before the power was lost, NO parity errors are normal. I've had my server for over 5 years, other than a un-expected powerdown before I had a UPS, never have seen a parity error.

I believe the drive is supposed to do pre-emptive reallocations when it has trouble reading data but is ultimately successful. Without such a feature, a parity check would almost never result in a reallocated sector. Am I missing something? Yes, a "feature" of the "md" driver is to re-construct the failed "read" (by use of the other disks in the array), supply it to the OS program requesting the data, and then write the same sector back to the disk. It is that "write" that allows the sector pending-reallocation to be re-allocated. The block of code is in unraid.c /* If we're trying to read a failed disk, then we must read * parity and all the "other" disks and compute it. */ if ((col->read_bi || (failed && sh->col[failed_num].read_bi)) && !buff_uptodate(col) && !buff_locked(col)) { if (disk_valid( col)) { dprintk("Reading col %d (sync=%d)\n", i, syncing); set_buff_locked( col); locked++; set_bit(MD_BUFF_READ, &col->state); } else if (uptodate == disks-1) { dprintk("Computing col %d\n", i); compute_block(sh, i); /* also sets it Uptodate */ uptodate++; /* if failed disk is enabled, write it */ if (disk_enabled( col)) { dprintk("Writing reconstructed failed col %d\n", i); set_buff_locked( col); locked++; set_bit(MD_BUFF_WRITE, &col->state); } /* this stripe is also now in-sync */ if (syncing) set_bit(STRIPE_INSYNC, &sh->state); } } Without a subsequent write, or a successful read, I see no way a sector can be re-allocated with the correct contents.

The disk finally died... Interestingly, it stopped responding to SMART reports, or just about anything. I powered down, swapped it to a different disk controller, (for those who suspected it might be a disk controller thing) and after powering up got this smart report: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 072 070 006 Pre-fail Always - 66340428 3 Spin_Up_Time 0x0003 100 100 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 5 5 Reallocated_Sector_Ct 0x0033 [color=red][b] 036 036 036[/b][/color] Pre-fail Always [b][color=red] FAILING_NOW 2625[/color][/b] 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 31627 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - [b][color=red]18[/color][/b] 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 5 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 15308 188 Command_Timeout 0x0032 099 098 000 Old_age Always - 60130459662 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 072 064 045 Old_age Always - 28 (Lifetime Min/Max 28/28) 194 Temperature_Celsius 0x0022 028 040 000 Old_age Always - 28 (0 26 0 0) 195 Hardware_ECC_Recovered 0x001a 049 046 000 Old_age Always - 66340428 197 Current_Pending_Sector 0x0012 068 068 000 Old_age Always - [b][color=red]1350[/color][/b] 198 Offline_Uncorrectable 0x0010 068 068 000 Old_age Offline - [b][color=red]1350[/color][/b] 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 10423885627416 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 0 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 3599756433 I don't like that it re-allocated the sectors without them being written to... To me, that is a mistake in the disks's firmware. I'll just go through the RMA process now. Joe L.

I would doubt it had been used before I put it in service since the initial SMART report showed zero hours run-time. Now, it might have been drop-kicked by the shipping company on its trip from newegg to my house. Used, no... Abused, possibly. It is now at 15 hours of run-time. I do not know if anybody has seen a disk slowly fail like this, so I'm just letting it run. It is still VERY SLOWLY reading the disk. After 15 hours it is still only at 1% in the pre-read. I figure in a few more hours the re-allocated sectors will have reached the failure threshold and the disk will be considered as failing SMART tests. As far as suspecting the new disk controller card. No... I do not suspect it at all, nothing on it would cause the SMART data and everything else to continuously report media errors. Cable problems would show as timeouts, or ICRC errors. Once the SMART data shows FAILING_NOW I'll swap cables around, but for now, as far as I can see, the disk controller is working exactly as it should. (Oh yes, the disk made a lot of clicking noises when I first powered the server on after installing it... even before it was being accessed by the Linux OS. I had a bad feeling even then.) Joe L. Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 071 070 006 Pre-fail Always - 57557914 3 Spin_Up_Time 0x0003 100 100 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 4 5 Reallocated_Sector_Ct 0x0033 046 046 036 Pre-fail Always - [b][color=red] 2238[/color][/b] 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 27314 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - [color=red][b]15[/b][/color] 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 4 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 13219 188 Command_Timeout 0x0032 100 098 000 Old_age Always - 42950328330 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 073 064 045 Old_age Always - 27 (Lifetime Min/Max 26/36) 194 Temperature_Celsius 0x0022 027 040 000 Old_age Always - 27 (0 26 0 0) 195 Hardware_ECC_Recovered 0x001a 048 046 000 Old_age Always - 57557914 197 Current_Pending_Sector 0x0012 072 072 000 Old_age Always - [color=red][b]1166[/b][/color] 198 Offline_Uncorrectable 0x0010 072 072 000 Old_age Offline - [color=red][b]1166[/b][/color] 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 209435490254866 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 0 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 3591162722

I figure some of you might get a kick out of this... I purchased a 2TB drive just before Christmas and had never un-packed it. I did not have a spare port in the server to connect it to, and I did not need the space. I just put the disk on the shelf as a spare. It is/was a 2TB ST32000542AS drive... Recently I had ordered some of the very cheap 2 port SATA disk controllers from e-bay, (see here) they arrived the other day from China and I finally installed the 2TB drive in my newer server. The good news, the 2 port disk controller seems to work just fine, and 6 ports for under $25 is a pretty good deal. It connects at 3Gb/s. Feb 25 16:11:56 Tower2 kernel: ata9: SATA max UDMA/133 abar m8192@0xfe9fe000 port 0xfe9fe100 irq 16 Feb 25 16:11:56 Tower2 kernel: ata9: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Feb 25 16:11:56 Tower2 kernel: ata9.00: ATA-8: ST32000542AS, CC34, max UDMA/133 Feb 25 16:11:56 Tower2 kernel: ata9.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32) Feb 25 16:11:56 Tower2 kernel: ata9.00: configured for UDMA/133 The bad news... the Seagate disk is not doing so well in its initial pre-clear. In the syslog is a constant series of messages like this: Feb 25 18:55:09 Tower2 kernel: ata9.00: error: { UNC } Feb 25 18:55:09 Tower2 kernel: ata9.00: configured for UDMA/133 Feb 25 18:55:09 Tower2 kernel: ata9: EH complete Feb 25 18:55:13 Tower2 kernel: ata9.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 Feb 25 18:55:13 Tower2 kernel: ata9.00: irq_stat 0x48000000 Feb 25 18:55:13 Tower2 kernel: ata9.00: failed command: READ FPDMA QUEUED Feb 25 18:55:13 Tower2 kernel: ata9.00: cmd 60/08:00:b8:93:ad/00:00:00:00:00/40 tag 0 ncq 4096 in Feb 25 18:55:13 Tower2 kernel: res 41/40:08:b8:93:ad/00:00:00:00:00/00 Emask 0x409 (media error) <F> Feb 25 18:55:13 Tower2 kernel: ata9.00: status: { DRDY ERR } Feb 25 18:55:13 Tower2 kernel: ata9.00: error: { UNC } Feb 25 18:55:13 Tower2 kernel: ata9.00: configured for UDMA/133 Feb 25 18:55:13 Tower2 kernel: ata9: EH complete Feb 25 18:55:17 Tower2 kernel: ata9.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 Feb 25 18:55:17 Tower2 kernel: ata9.00: irq_stat 0x48000000 Feb 25 18:55:17 Tower2 kernel: ata9.00: failed command: READ FPDMA QUEUED Feb 25 18:55:17 Tower2 kernel: ata9.00: cmd 60/08:00:b8:93:ad/00:00:00:00:00/40 tag 0 ncq 4096 in Feb 25 18:55:17 Tower2 kernel: res 41/40:08:b8:93:ad/00:00:00:00:00/00 Emask 0x409 (media error) <F> Feb 25 18:55:17 Tower2 kernel: ata9.00: status: { DRDY ERR } Feb 25 18:55:17 Tower2 kernel: ata9.00: error: { UNC } Feb 25 18:55:17 Tower2 kernel: ata9.00: configured for UDMA/133 Feb 25 18:55:17 Tower2 kernel: ata9: EH complete Feb 25 18:55:20 Tower2 kernel: ata9.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 Feb 25 18:55:20 Tower2 kernel: ata9.00: irq_stat 0x48000000 Feb 25 18:55:20 Tower2 kernel: ata9.00: failed command: READ FPDMA QUEUED Feb 25 18:55:20 Tower2 kernel: ata9.00: cmd 60/08:00:b8:93:ad/00:00:00:00:00/40 tag 0 ncq 4096 in Feb 25 18:55:20 Tower2 kernel: res 41/40:08:b8:93:ad/00:00:00:00:00/00 Emask 0x409 (media error) <F> Feb 25 18:55:20 Tower2 kernel: ata9.00: status: { DRDY ERR } Feb 25 18:55:20 Tower2 kernel: ata9.00: error: { UNC } Feb 25 18:55:20 Tower2 kernel: ata9.00: configured for UDMA/133 Feb 25 18:55:20 Tower2 kernel: sd 9:0:0:0: [sdj] Unhandled sense code Feb 25 18:55:20 Tower2 kernel: sd 9:0:0:0: [sdj] Result: hostbyte=0x00 driverbyte=0x08 Feb 25 18:55:20 Tower2 kernel: sd 9:0:0:0: [sdj] Sense Key : 0x3 [current] [descriptor] Feb 25 18:55:20 Tower2 kernel: Descriptor sense data with sense descriptors (in hex): Feb 25 18:55:20 Tower2 kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 Feb 25 18:55:20 Tower2 kernel: 00 ad 93 b8 Feb 25 18:55:20 Tower2 kernel: sd 9:0:0:0: [sdj] ASC=0x11 ASCQ=0x4 Feb 25 18:55:20 Tower2 kernel: sd 9:0:0:0: [sdj] CDB: cdb[0]=0x28: 28 00 00 ad 93 b8 00 00 08 00 Feb 25 18:55:20 Tower2 kernel: end_request: I/O error, dev sdj, sector 11375544 Feb 25 18:55:20 Tower2 kernel: Buffer I/O error on device sdj, logical block 1421943 Feb 25 18:55:20 Tower2 kernel: ata9: EH complete The initial smart report looked like this (Note... 0 Power_on_hours, no re-allocated sectors, no sectors pending re-allocation): [color=maroon]SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 100 100 006 Pre-fail Always - 28166 3 Spin_Up_Time 0x0003 100 100 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 4 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 74 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 0 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 4 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 253 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 068 068 045 Old_age Always - 32 (Lifetime Min/Max 26/32) 194 Temperature_Celsius 0x0022 032 040 000 Old_age Always - 32 (0 26 0 0) 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 28166 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 20 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 20 199 UDMA_CRC_Error_Count 0x003e 200 253 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 141815525146627 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 0 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 2407[/color] The disk has been pre-clearing for about 2 hours now... The smart report shows this: [color=maroon]ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 072 070 006 Pre-fail Always - 9462713 3 Spin_Up_Time 0x0003 100 100 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 4 5 Reallocated_Sector_Ct 0x0033 094 094 036 Pre-fail Always - [b][color=red]282[/color][/b] 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 4727 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 2 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 4 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 2204 188 Command_Timeout 0x0032 099 099 000 Old_age Always - 8590065666 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 069 064 045 Old_age Always - 31 (Lifetime Min/Max 26/36) 194 Temperature_Celsius 0x0022 031 040 000 Old_age Always - 31 (0 26 0 0) 195 Hardware_ECC_Recovered 0x001a 048 046 000 Old_age Always - 9462713 197 Current_Pending_Sector 0x0012 095 095 000 Old_age Always - [b][color=red]209[/color][/b] 198 Offline_Uncorrectable 0x0010 095 095 000 Old_age Offline - [b][color=red]209[/color][/b] 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 12854837116933 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 0 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 3544051280[/color] What I find interesting is not that there are 209 sectors pending re-allocation, but that 282 have already been re-allocated? I cannot figure out how that has happened, since I've not written to the disk at all. The pre-read has not even read 1% of the disk. ================================================================== 1.7 = unRAID server Pre-Clear disk /dev/sdj = cycle 1 of 1, partition start on sector 63 = Disk Pre-Read in progress: 0% complete = ( 4,935,168,000 bytes of 2,000,398,934,016 read ) = Disk Temperature: 31C, Elapsed Time: 2:16:22 I've got nothing to lose if I let the preclear run its course. One thing for sure, by the time it is done, Ill be looking at an RMA. My big mistake... putting the disk on the shelf rather than installing it right away... so much for returning it to newegg. Now it will have to go back to Seagate... In the time it has taken me to write this post I now have [color=red] 5 Reallocated_Sector_Ct 0x0033 092 092 036 Pre-fail Always - [b]333[/b] 197 Current_Pending_Sector 0x0012 095 095 000 Old_age Always - [b]238[/b] 198 Offline_Uncorrectable 0x0010 095 095 000 Old_age Offline - [b]238[/b][/color] I wish I knew how it is figuring out what to put in the sectors it has already re-allocated. I've still never written to the disk at all. It is still less than 1% through the pre-read having read about 6Gig out of the 2000Gig. = Disk Pre-Read in progress: 0% complete = ( 6,580,224,000 bytes of 2,000,398,934,016 read ) Ouch... Edit: It has been 10 hours. it is now 1% through the pre-read. I've still not written to the drive at all.... ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 072 070 006 Pre-fail Always - 38629196 3 Spin_Up_Time 0x0003 100 100 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 4 5 Reallocated_Sector_Ct 0x0033 065 065 036 Pre-fail Always - [b][color=red] 1440[/color][/b] 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 18372 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - [b][color=red]10[/color][/b] 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 4 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 8932 188 Command_Timeout 0x0032 099 099 000 Old_age Always - 30065229831 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 073 064 045 Old_age Always - 27 (Lifetime Min/Max 26/36) 194 Temperature_Celsius 0x0022 027 040 000 Old_age Always - 27 (0 26 0 0) 195 Hardware_ECC_Recovered 0x001a 048 046 000 Old_age Always - 38629196 197 Current_Pending_Sector 0x0012 081 081 000 Old_age Always - [b][color=red]794[/color][/b] 198 Offline_Uncorrectable 0x0010 081 081 000 Old_age Offline - [b][color=red]794[/color][/b] 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 66559108186125 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 0 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 3572622799 Still have no idea how it is re-allocating sectors... it cannot know what to put in the re-allocated sector, no writes have been made to the drive at all. Joe L.

If you want to avoid stopping your jobs (and also run several at the same time), you should look into the "screen" package in UnMenu, Lets you start virtual sessions and keep them running even if your telnet drops for some reason. Just saying... /Lars Olof Unfortunately, even "screen" will not help when you are changing BIOS options.

You want AHCI, Not "Native IDE" You'll know if you have it right when all the disks are showing as /dev/sdX

if it is being shown as /dev/hda, then it is IDE emulation mode. The BIOS has options for this, and possibly two different options, one for the first 4 port, the other for the remaining 2 disk controller ports. The reason is simple, Windows-XP and prior have no SATA drivers. If there was not an IDE emulation mode, you could not boot those OS. Emulated IDE will usually be much slower than native SATA. You can change the emulation mode at any time. It will not affect the disk assignments in unRAID of affect the disk contents. Joe L.

Could be, or, you might have the SATA controller set to an IDE/Legacy compatibility mode. Joe L.

Yes, there are two SMART attributes that are FAILING_NOW. Be thankful you learned of the failure before you trusted the disk with your data. There are 1265 sectors that have been re-allocated. In highly technical terms, the drive is "toast." I see an RMA in your future. Joe L.

Looks good to me too.

No, the current VALUE is above the affiliated FAILURE_THRESHOLD. The manufacturer just happened to put the FAILURE_THRESHOLD at a value close the the normalized starting value on a few of the attributes. Only they know how many errors are actually needed to fail. (and they aren't telling) I'm more concerned about the re-allocated sectors. If they've truly settled down, fine. If not, not so good. I've got one drive in my array with 100 re-allocated sectors and it has stayed that way no matter how many times I've pre-cleared it. It too was re-used from an old USB enclosure. All we know on your drive is it want through 1 cycle without re-allocation of any additional sectors, but the prior 2 re-allocated 133. My vote would be to preclear it for 2 or 3 more cycles, and if stable, use it. If it shows signs of re-allocating more sectors, RMA it. Joe L.

Everything looks fine. Two of the drives ( sdb, sdd ) had been exposed to high temperatures at some point in the past. If you look at the finish report for them you'll see the normalized WORST value is below the FAILURE_THRESHOLD for that attribute on both of those drives. They probably were used without any fans or cooling. The temperature looks fine now. Joe L.

First, that is not the most recent preclear_disk.sh. It is currently at version 1.6. The disk looks fine. There are no re-allocated sectors, nor any pending re-allocation. No other attributes are failing now. Enjoy your new disk, and always grab a new version of preclear_disk.sh before you clear a new disk. The final report on newer versions is much improved. Joe L.

Test should be completed now. But `smartctl -a /dev/sda` yields the same output, except for the timestamp and Raw_Read_Error_Rate, Power_On_Hours and Hardware_ECC_Recovered fields. I guess that's it then? Nothing else to try? The difference would only be one line towards the bottom of the report. Again, you're on your own... an SSD is a very different beast than a spinning disk and I doubt it implements SMART in the same way.

Correct. After waiting for it to complete. Joe L.

I did notice that. Strange. I couldn't find any other forum posts about using the preclear script with SSD. Does nobody do this? Is it not necessary (for a cache drive)? Is my only alternative to use "-n" to skip the pre and post read that would allow smart firmware to identify bad blocks? Edit: Just tried it, and that didn't work either. I think it is that most people do not have SSD devices, and they certainly do not have the same issues as physical media. You might be able to run the "long" test through smartctl. See if it is supported. Joe L.

I'm not sure I'd believe the SMART results anyway... It shows 3204045602843 hours operation. That might indicate you have one of the time-warp SSD devices. (indicating a manufacture date roughly 356 million years ago)