Preclear.sh results - Questions about your results? Post them here.


Recommended Posts

Looks good to me.

 

Couldn't tell you exactly why it slows down on post-read, but that's normal (remember I told you post-read would take twice as long?).

 

Here's my results from a couple 6 TB drives which shows something similar.

 

Preclear Successful

... Total time 54:43:12

... Pre-Read time 13:55:07 (119 MB/s)

... Zeroing time 12:46:33 (130 MB/s)

... Post-Read time 28:00:32 (59 MB/s)

 

  Preclear Successful

... Total time 54:50:58

... Pre-Read time 14:02:36 (118 MB/s)

... Zeroing time 12:46:51 (130 MB/s)

... Post-Read time 28:00:32 (59 MB/s)

Link to comment

@Traxxus

Cool i though that was just my drives and controller setup doing tha, phew!!

 

Q for devs, is there a way to speed this preclear process up? I don't pretend to understand any of the mechanics behind but damn, imagine how long it would take for 8TB / 10TB HDD & possibly larger ones :o

 

Seem you would need a spare machine just for preclear process if your going to be adding in large amounts of huge sized HDD :P

 

Cheers

Kosti

Link to comment

So,  I just finished preclearing 2 drives.  In both cases, the result was such as "Disk /dev/sdk has NOT been successfully precleared".  I don't fully understand why.  I tried adding one of the precleared drives to my array and there was no issue.  I've attached the preclear logs. 

 

I'm using preclear_disk.sh v1.15 on unRAID v6b12.

 

If I'm able to add the drives to my array with no problem, should I be Okay?

Well... maybe... but maybe not.

 

 

The preclear report said:

== Disk /dev/sdi has NOT been successfully precleared

== Postread detected un-expected non-zero bytes on disk==

 

Basically, it wrote all zeros to the disk, but when it went to read them back to verify the write was successful, there were some bytes that were not zero.

 

That is a very bad thing, since you cannot rely on the disk to store your data accurately.  Nor can you rebuild any other failed disk accurately if one were to fail.

 

I would try a parity check at this point.  It might have an error or two as it expected all zeros...

 

Joe L.

 

I completed a parity check.  Almost as quickly as i started the check it found and corrected 1 error.  It completed in 14 hours without finding any more errors.  I'm thinking 1 error is nothing to worry about.  I'm not sure how to get any more assurance that my drives are okay.

 

These were the first pre-clears that I performed on v6b12.  I find it strange that I got the same result on two different brand new drives.

Link to comment

is there a way to speed this preclear process up?

 

There is an improved preclear script by bjp999.

It speeds up the post read process.

 

You can also skip the pre-read and post-read of the preclear process (check the --help for the specifics) to save time. However, those were added in for safety to help test out the drive to ensure it doesn't suffer from an early death once it's got your valuable info stored on it.

 

It's a bit of a bother to run it and wait, but it's better than losing data. There's a discussion around here somewhere of how many times to run the preclear - some do 3 or 4 complete cycles.

Link to comment

Hi,  Can someone kindly analyse my results. I was only looking for the  # of sectors pending re-allocation. But then I noticed some info under changed attributes just now. Anything I should be concerned about. This was a brand new seagate from newegg.ca bought during boxing day. I already put it in an array and dumped some data on it.  Didnt have any issues doing that.

 

If the whole .txt file is needed, i can upload.

 

Thanks in advance.

 

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: ========================================================================1.15

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == invoked as: ./preclear_disk.sh -A -c 2 /dev/sdb

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == ST4000VN000-1H4168  Z302ETV6

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == Disk /dev/sdb has been successfully precleared

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == with a starting sector of 1

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == Ran 2 cycles

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: ==

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == Using :Read block size = 8388608 Bytes

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == Last Cycle's Pre Read Time  : 8:49:25 (125 MB/s)

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == Last Cycle's Zeroing time  : 8:05:33 (137 MB/s)

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == Last Cycle's Post Read Time : 17:43:19 (62 MB/s)

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == Last Cycle's Total Time    : 25:49:52

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: ==

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == Total Elapsed Time 60:29:15

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: ==

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == Disk Start Temperature: 28C

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: ==

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == Current Disk Temperature: 27C,

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: ==

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: ============================================================================

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: ** Changed attributes in files: /tmp/smart_start_sdb  /tmp/smart_finish_sdb

Jan 10 12:06:22 Tower preclear_disk-diff[10878]:                ATTRIBUTE  NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE

Jan 10 12:06:22 Tower preclear_disk-diff[10878]:      Raw_Read_Error_Rate =  102    119            6        ok          3878896

Jan 10 12:06:22 Tower preclear_disk-diff[10878]:          Spin_Retry_Count =  100    100          97        near_thresh 0

Jan 10 12:06:22 Tower preclear_disk-diff[10878]:          End-to-End_Error =  100    100          99        near_thresh 0

Jan 10 12:06:22 Tower preclear_disk-diff[10878]:  Airflow_Temperature_Cel =    73      72          45        ok          27

Jan 10 12:06:22 Tower preclear_disk-diff[10878]:      Temperature_Celsius =    27      28            0        ok          27

Jan 10 12:06:22 Tower preclear_disk-diff[10878]:  No SMART attributes are FAILING_NOW

Jan 10 12:06:22 Tower preclear_disk-diff[10878]:

Jan 10 12:06:22 Tower preclear_disk-diff[10878]:  0 sectors were pending re-allocation before the start of the preclear.

Jan 10 12:06:22 Tower preclear_disk-diff[10878]:  0 sectors were pending re-allocation after pre-read in cycle 1 of 2.

Jan 10 12:06:22 Tower preclear_disk-diff[10878]:  0 sectors were pending re-allocation after zero of disk in cycle 1 of 2.

Jan 10 12:06:22 Tower preclear_disk-diff[10878]:  0 sectors were pending re-allocation after post-read in cycle 1 of 2.

Jan 10 12:06:22 Tower preclear_disk-diff[10878]:  0 sectors were pending re-allocation after zero of disk in cycle 2 of 2.

Jan 10 12:06:22 Tower preclear_disk-diff[10878]:  0 sectors are pending re-allocation at the end of the preclear,

Jan 10 12:06:22 Tower preclear_disk-diff[10878]:    the number of sectors pending re-allocation did not change.

Jan 10 12:06:22 Tower preclear_disk-diff[10878]:  0 sectors had been re-allocated before the start of the preclear.

Jan 10 12:06:22 Tower preclear_disk-diff[10878]:  0 sectors are re-allocated at the end of the preclear,

Jan 10 12:06:22 Tower preclear_disk-diff[10878]:    the number of sectors re-allocated did not change.

Link to comment

Hi,  Can someone kindly analyse my results. I was only looking for the  # of sectors pending re-allocation. But then I noticed some info under changed attributes just now. Anything I should be concerned about. This was a brand new seagate from newegg.ca bought during boxing day. I already put it in an array and dumped some data on it.  Didnt have any issues doing that.

 

If the whole .txt file is needed, i can upload.

 

Thanks in advance.

 

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: ========================================================================1.15

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == invoked as: ./preclear_disk.sh -A -c 2 /dev/sdb

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == ST4000VN000-1H4168  Z302ETV6

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == Disk /dev/sdb has been successfully precleared

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == with a starting sector of 1

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == Ran 2 cycles

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: ==

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == Using :Read block size = 8388608 Bytes

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == Last Cycle's Pre Read Time  : 8:49:25 (125 MB/s)

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == Last Cycle's Zeroing time  : 8:05:33 (137 MB/s)

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == Last Cycle's Post Read Time : 17:43:19 (62 MB/s)

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == Last Cycle's Total Time    : 25:49:52

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: ==

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == Total Elapsed Time 60:29:15

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: ==

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == Disk Start Temperature: 28C

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: ==

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == Current Disk Temperature: 27C,

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: ==

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: ============================================================================

Jan 10 12:06:22 Tower preclear_disk-diff[10878]: ** Changed attributes in files: /tmp/smart_start_sdb  /tmp/smart_finish_sdb

Jan 10 12:06:22 Tower preclear_disk-diff[10878]:                ATTRIBUTE  NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE

Jan 10 12:06:22 Tower preclear_disk-diff[10878]:      Raw_Read_Error_Rate =  102    119            6        ok          3878896

Jan 10 12:06:22 Tower preclear_disk-diff[10878]:          Spin_Retry_Count =  100    100          97        near_thresh 0

Jan 10 12:06:22 Tower preclear_disk-diff[10878]:          End-to-End_Error =  100    100          99        near_thresh 0

Jan 10 12:06:22 Tower preclear_disk-diff[10878]:  Airflow_Temperature_Cel =    73      72          45        ok          27

Jan 10 12:06:22 Tower preclear_disk-diff[10878]:      Temperature_Celsius =    27      28            0        ok          27

Jan 10 12:06:22 Tower preclear_disk-diff[10878]:  No SMART attributes are FAILING_NOW

Jan 10 12:06:22 Tower preclear_disk-diff[10878]:

Jan 10 12:06:22 Tower preclear_disk-diff[10878]:  0 sectors were pending re-allocation before the start of the preclear.

Jan 10 12:06:22 Tower preclear_disk-diff[10878]:  0 sectors were pending re-allocation after pre-read in cycle 1 of 2.

Jan 10 12:06:22 Tower preclear_disk-diff[10878]:  0 sectors were pending re-allocation after zero of disk in cycle 1 of 2.

Jan 10 12:06:22 Tower preclear_disk-diff[10878]:  0 sectors were pending re-allocation after post-read in cycle 1 of 2.

Jan 10 12:06:22 Tower preclear_disk-diff[10878]:  0 sectors were pending re-allocation after zero of disk in cycle 2 of 2.

Jan 10 12:06:22 Tower preclear_disk-diff[10878]:  0 sectors are pending re-allocation at the end of the preclear,

Jan 10 12:06:22 Tower preclear_disk-diff[10878]:    the number of sectors pending re-allocation did not change.

Jan 10 12:06:22 Tower preclear_disk-diff[10878]:  0 sectors had been re-allocated before the start of the preclear.

Jan 10 12:06:22 Tower preclear_disk-diff[10878]:  0 sectors are re-allocated at the end of the preclear,

Jan 10 12:06:22 Tower preclear_disk-diff[10878]:    the number of sectors re-allocated did not change.

It looks great.

 

Joe L.

Link to comment

Anyone have any idea for my issue yet of not being able to add a successfully precleared HDD to the array? Been happening on any new HDD I try to add. Preclear is successful, but the array says it needs to be cleared still when I try to add it.

 

Attached is my syslog after preclearing a disk again.

 

Thanks!

PRetty sure it says the same thing regardless if it is pre-cleared, or not.... but skips the lengthy clearing step it would normally perform if once it starts on the process of adding the drive to the array.

 

I did not see in your syslog any evidence of you actually adding the disk to the array.  Did you press the button to actually add the disk, or just stop because it says it will clear the disk?

 

Joe L.

Link to comment

Anyone have any idea for my issue yet of not being able to add a successfully precleared HDD to the array? Been happening on any new HDD I try to add. Preclear is successful, but the array says it needs to be cleared still when I try to add it.

 

Attached is my syslog after preclearing a disk again.

 

Thanks!

PRetty sure it says the same thing regardless if it is pre-cleared, or not.... but skips the lengthy clearing step it would normally perform if once it starts on the process of adding the drive to the array.

 

I did not see in your syslog any evidence of you actually adding the disk to the array.  Did you press the button to actually add the disk, or just stop because it says it will clear the disk?

 

Joe L.

 

I stopped it because it just clears it again. I tried removing the Dynamix plugins and preclearing and then adding the drive, but have the same problem of it wanting to clear the drive again. No matter what I seem to do, it keeps saying wanting to clear the drive and never lets me get to the format drive.

Link to comment

Anyone have any idea for my issue yet of not being able to add a successfully precleared HDD to the array? Been happening on any new HDD I try to add. Preclear is successful, but the array says it needs to be cleared still when I try to add it.

 

Attached is my syslog after preclearing a disk again.

 

Thanks!

PRetty sure it says the same thing regardless if it is pre-cleared, or not.... but skips the lengthy clearing step it would normally perform if once it starts on the process of adding the drive to the array.

 

I did not see in your syslog any evidence of you actually adding the disk to the array.  Did you press the button to actually add the disk, or just stop because it says it will clear the disk?

 

Joe L.

 

I stopped it because it just clears it again. I tried removing the Dynamix plugins and preclearing and then adding the drive, but have the same problem of it wanting to clear the drive again. No matter what I seem to do, it keeps saying wanting to clear the drive and never lets me get to the format drive.

Are you sure you are using the latest version of preclear? Are you using unRAID v6? There was an issue with the preclear signature on v6 which has been fixed in the latest version of preclear
Link to comment

Anyone have any idea for my issue yet of not being able to add a successfully precleared HDD to the array? Been happening on any new HDD I try to add. Preclear is successful, but the array says it needs to be cleared still when I try to add it.

 

Attached is my syslog after preclearing a disk again.

 

Thanks!

PRetty sure it says the same thing regardless if it is pre-cleared, or not.... but skips the lengthy clearing step it would normally perform if once it starts on the process of adding the drive to the array.

 

I did not see in your syslog any evidence of you actually adding the disk to the array.  Did you press the button to actually add the disk, or just stop because it says it will clear the disk?

 

Joe L.

 

I stopped it because it just clears it again. I tried removing the Dynamix plugins and preclearing and then adding the drive, but have the same problem of it wanting to clear the drive again. No matter what I seem to do, it keeps saying wanting to clear the drive and never lets me get to the format drive.

Are you sure you are using the latest version of preclear? Are you using unRAID v6? There was an issue with the preclear signature on v6 which has been fixed in the latest version of preclear

 

I am 100% sure I am using the latest version. 1.15. If I do a preclear_disk.sh -v it outputs 1.15. I am on unRaid 5.0.6

 

SO I upgraded to unRaid 6 Beta 12 and tried preclear and then tried adding and getting the same exact problem. I am almost at capacity, what can I do?

Link to comment

Anyone have any idea for my issue yet of not being able to add a successfully precleared HDD to the array? Been happening on any new HDD I try to add. Preclear is successful, but the array says it needs to be cleared still when I try to add it.

 

Attached is my syslog after preclearing a disk again.

 

Thanks!

PRetty sure it says the same thing regardless if it is pre-cleared, or not.... but skips the lengthy clearing step it would normally perform if once it starts on the process of adding the drive to the array.

 

I did not see in your syslog any evidence of you actually adding the disk to the array.  Did you press the button to actually add the disk, or just stop because it says it will clear the disk?

 

Joe L.

 

I stopped it because it just clears it again. I tried removing the Dynamix plugins and preclearing and then adding the drive, but have the same problem of it wanting to clear the drive again. No matter what I seem to do, it keeps saying wanting to clear the drive and never lets me get to the format drive.

Are you sure you are using the latest version of preclear? Are you using unRAID v6? There was an issue with the preclear signature on v6 which has been fixed in the latest version of preclear

 

I am 100% sure I am using the latest version. 1.15. If I do a preclear_disk.sh -v it outputs 1.15. I am on unRaid 5.0.6

 

SO I upgraded to unRaid 6 Beta 12 and tried preclear and then tried adding and getting the same exact problem. I am almost at capacity, what can I do?

It is pretty obvious...

Does the disk still test as "precleared" when you invoke:

preclear_disk.sh -t /dev/sdX

(where X = your drive letter)

 

If that test says it is pre-cleared, it is... and you can add the disk to your array and let unRAID do as it wants, regardless of what the screen seems to say.

 

If I'm right, it will skip the step of writing zeros to the entire drive and add it to your array.  If I'm wrong, it will write zeros to the drive and then add it to your array. 

 

Either way, it ends up added to your array.

 

Joe L.

Link to comment

Anyone have any idea for my issue yet of not being able to add a successfully precleared HDD to the array? Been happening on any new HDD I try to add. Preclear is successful, but the array says it needs to be cleared still when I try to add it.

 

Attached is my syslog after preclearing a disk again.

 

Thanks!

PRetty sure it says the same thing regardless if it is pre-cleared, or not.... but skips the lengthy clearing step it would normally perform if once it starts on the process of adding the drive to the array.

 

I did not see in your syslog any evidence of you actually adding the disk to the array.  Did you press the button to actually add the disk, or just stop because it says it will clear the disk?

 

Joe L.

 

I stopped it because it just clears it again. I tried removing the Dynamix plugins and preclearing and then adding the drive, but have the same problem of it wanting to clear the drive again. No matter what I seem to do, it keeps saying wanting to clear the drive and never lets me get to the format drive.

Are you sure you are using the latest version of preclear? Are you using unRAID v6? There was an issue with the preclear signature on v6 which has been fixed in the latest version of preclear

 

I am 100% sure I am using the latest version. 1.15. If I do a preclear_disk.sh -v it outputs 1.15. I am on unRaid 5.0.6

 

SO I upgraded to unRaid 6 Beta 12 and tried preclear and then tried adding and getting the same exact problem. I am almost at capacity, what can I do?

It is pretty obvious...

Does the disk still test as "precleared" when you invoke:

preclear_disk.sh -t /dev/sdX

(where X = your drive letter)

 

If that test says it is pre-cleared, it is... and you can add the disk to your array and let unRAID do as it wants, regardless of what the screen seems to say.

 

If I'm right, it will skip the step of writing zeros to the entire drive and add it to your array.  If I'm wrong, it will write zeros to the drive and then add it to your array. 

 

Either way, it ends up added to your array.

 

Joe L.

 

The problem is the array never lets me add it. Here are the steps I have done IN ORDER:

 

Ran Preclear_disk.sh

Verified disk has been precleared

Stop Array

Add drive as Disk 9

Go to start array with newly added disk

unRaid says it needs to clear

Let clear run

unRaid then says it needs to clear it again

Let clear run

unRaid then says it needs to clear it again

 

It's an endless loop and it never allows me to start the array with the newly added disk.

Link to comment

The problem is the array never lets me add it. Here are the steps I have done IN ORDER:

 

Ran Preclear_disk.sh

Verified disk has been precleared

Stop Array

Add drive as Disk 9

Go to start array with newly added disk

unRaid says it needs to clear

Let clear run

unRaid then says it needs to clear it again

Let clear run

unRaid then says it needs to clear it again

 

It's an endless loop and it never allows me to start the array with the newly added disk.

Sounds like you may have a third party add-on installed that is interfering with setting up the new disk. Try booting in safe mode and try the operation again.
Link to comment

The problem is the array never lets me add it. Here are the steps I have done IN ORDER:

 

Ran Preclear_disk.sh

Verified disk has been precleared

Stop Array

Add drive as Disk 9

Go to start array with newly added disk

unRaid says it needs to clear

Let clear run

unRaid then says it needs to clear it again

Let clear run

unRaid then says it needs to clear it again

 

It's an endless loop and it never allows me to start the array with the newly added disk.

Sounds like you may have a third party add-on installed that is interfering with setting up the new disk. Try booting in safe mode and try the operation again.

 

Good idea. I tried this last night and into today. I renamed my /boot/extra and /boot/config/pulgins folder (don't have a /boot/plugin folder) to something else and did a reboot. I then had unRaid go through the clearing of the disk. When it completed, it said "Found new erased disk" and asked if I wanted to start array. So I did, but then it asked that the disk be cleared again.

 

So back to where I started, but appreciate the suggestion.

Link to comment

I am uploading a new syslog and preclear results. If someone believes I should move this question back to a general thread of it's own let me know. Just trying to solve thislong problem so I can add more space :(

 

Thanks in advance!

 

I noticed 4 items, but cannot say if any of them are directly related.  I can confirm what you have said, preclear of sdg is apparently successful, but is not identified as cleared.  I suspect the problem with the Parity drive is 'confusing' UnRAID.

 

* BIOS is a little old, from 2010.  Syslog shows a number of ACPI workarounds, a little more than normal.  If you can find a newer BIOS for that board, it *might* help.

 

* You have IDE emulation turned on for 2 of your SATA drives.  When you next boot, go into the BIOS settings and look for the SATA mode, and change it to a native SATA mode, preferably AHCI if available, anything but IDE emulation mode.  Performance to Disk 3 and your Cache drive should be slightly faster, and a little safer.

 

* You have stations all over the web attempting to connect to your machine, so I have to assume you have it set in the router's DMZ (sic?).  Most failed, but some telnet attempts appeared successful, both local and from outside your net.  A serious sniffing attempt was made from 42.116.99.53, using various user names and ports.  I'm not an expert here, but this sounds incredibly dangerous!

 

* Parity drive (sdh) is not configured correctly.  It is a 4tb drive but is configured for 2.1tb, as if >2tb support was not available when drive was prepared.  Usable space on it is 1.99tb, usable space on the true 2tb drives is 1.81tb.  On array start (each time), the system appears to recognize that something is wrong, and rewrites the GPT entries to the Parity drive, reports unknown partition on it, but does NOT proceed to build parity, apparently accepts it as correct!

 

When you added the new drive as Disk 9, the GPT entries were again written to sdh (the Parity drive), then an MBR written to sdg (new Disk 9).  It's possible the GPT writing to sdh caused an execution path that bypassed the already precleared test for sdg.  Perhaps the discovery of unknown partition on sdh set a flag that affected the testing of sdg.  You might email Tom and link this post.

Link to comment

I am uploading a new syslog and preclear results. If someone believes I should move this question back to a general thread of it's own let me know. Just trying to solve thislong problem so I can add more space :(

 

Thanks in advance!

 

I noticed 4 items, but cannot say if any of them are directly related.  I can confirm what you have said, preclear of sdg is apparently successful, but is not identified as cleared.  I suspect the problem with the Parity drive is 'confusing' UnRAID.

 

* BIOS is a little old, from 2010.  Syslog shows a number of ACPI workarounds, a little more than normal.  If you can find a newer BIOS for that board, it *might* help.

 

* You have IDE emulation turned on for 2 of your SATA drives.  When you next boot, go into the BIOS settings and look for the SATA mode, and change it to a native SATA mode, preferably AHCI if available, anything but IDE emulation mode.  Performance to Disk 3 and your Cache drive should be slightly faster, and a little safer.

 

* You have stations all over the web attempting to connect to your machine, so I have to assume you have it set in the router's DMZ (sic?).  Most failed, but some telnet attempts appeared successful, both local and from outside your net.  A serious sniffing attempt was made from 42.116.99.53, using various user names and ports.  I'm not an expert here, but this sounds incredibly dangerous!

 

* Parity drive (sdh) is not configured correctly.  It is a 4tb drive but is configured for 2.1tb, as if >2tb support was not available when drive was prepared.  Usable space on it is 1.99tb, usable space on the true 2tb drives is 1.81tb.  On array start (each time), the system appears to recognize that something is wrong, and rewrites the GPT entries to the Parity drive, reports unknown partition on it, but does NOT proceed to build parity, apparently accepts it as correct!

 

When you added the new drive as Disk 9, the GPT entries were again written to sdh (the Parity drive), then an MBR written to sdg (new Disk 9).  It's possible the GPT writing to sdh caused an execution path that bypassed the already precleared test for sdg.  Perhaps the discovery of unknown partition on sdh set a flag that affected the testing of sdg.  You might email Tom and link this post.

 

Rob, first most, thank you so much for all the information you have provided! I had no clue that the server was enabled through DMZ, so firstly I disabled that (stupid roommates). I will see if there is a BIOS update and get that updated.

 

I will also do everything else you mentioned and report back, though it'll take some time to get all that completed (especially redoing the parity).

 

Thank you so much for taking the time to read through my syslog!

Link to comment

Here's my situation: testing a new drive to see whether to keep it or return it. First two attempts, it crashed during the zeroing phase at about a day and a half in, both times. I was running the test on a new build, so I switched to my usual testing machine and successfully completed 3 passes. Despite passing, I see a lot of concerning results and am not sure whether to keep the drive.

 

1st preread shows 40 sectors pending reallocation

Final SMART stats show 12 uncorrectable errors (187), 5 runtime bad blocks (183), and what looks like multiple impact failures (?!?), among other things.

 

This drive is for backup/archive use and will spend most of its life offline and idle, so it doesn't have to be a tank, but I'm not looking to be a sucker, either. Any advice?

preclear_rpt_W4J06_2014-12-16.txt

preclear_rpt_W4J06_2014-12-08.txt

preclear_rpt_W4J06_2014-12-12.txt

preclear_finish_W4J06_2014-12-08.txt

Link to comment

hello there...

 

I have to ask this question... I currently have two new 5tb HDs preclearing but im a bit concerned with how long it's taking... it's now been 78 hours and im still at step two with 35% complete thus far...

 

I feel like that's a bit out of the norm...

 

suggestions???

 

PS... after looking at the stats a bit more... the script wasnt progressing at all... so I killed the script to try and rerun it again but the HD wasnt there.... I have restarted the computer and still the HD isnt listed in preclear or as an unassigned device in unraid's site...

 

Has the HD failed??? beyond reseating the device and doing what i have done i dont know what else to do in Linux...

 

Eep.... Help@!@

Link to comment

hello there...

 

I have to ask this question... I currently have two new 5tb HDs preclearing but im a bit concerned with how long it's taking... it's now been 78 hours and im still at step two with 35% complete thus far...

 

I feel like that's a bit out of the norm...

 

suggestions???

 

PS... after looking at the stats a bit more... the script wasnt progressing at all... so I killed the script to try and rerun it again but the HD wasnt there.... I have restarted the computer and still the HD isnt listed in preclear or as an unassigned device in unraid's site...

 

Has the HD failed??? beyond reseating the device and doing what i have done i dont know what else to do in Linux...

 

Eep.... Help@!@

Can your BIOS see the drive? If not then probably a connection problem.
Link to comment

hello there...

 

I have to ask this question... I currently have two new 5tb HDs preclearing but im a bit concerned with how long it's taking... it's now been 78 hours and im still at step two with 35% complete thus far...

 

I feel like that's a bit out of the norm...

 

suggestions???

 

PS... after looking at the stats a bit more... the script wasnt progressing at all... so I killed the script to try and rerun it again but the HD wasnt there.... I have restarted the computer and still the HD isnt listed in preclear or as an unassigned device in unraid's site...

 

Has the HD failed??? beyond reseating the device and doing what i have done i dont know what else to do in Linux...

 

Eep.... Help@!@

Can your BIOS see the drive? If not then probably a connection problem.

Wish I knew... Its a virtual setup running through a SAS controller...

Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.